This example uses Minuteman on Marathon on DC/OS Vagrant with an example application Helloworld.
Minuteman, in this example will route the VIP 1.2.3.4:5000. Although this is not an IP that actually exists in the cluster, if you try to make a TCP connection from any host in the cluster to this IP, it'll automatically be connected to the backend application.
The backend application we're using in our example is Helloworld. It has two endpoints, /, and /stream. / outputs an example string, as well as the machine, and port that instance of the application is running on. The stream endpoint makes a long-lived TCP, streaming connection.
Remember, the Minuteman VIPs are only accessible from other machines running Minuteman, and not the cluster as a whole!
-
Follow the dcos-vagrant setup steps to configure your installation.
-
Use vagrant to deploy a cluster with 1 private agent node and 1 public agent node (requires 9.5GB free memory):
cp VagrantConfig-1m-1a-1p.yaml VagrantConfig.yaml vagrant up -
Wait for DC/OS to come up. Check the dashboard: http://m1.dcos/.
-
Install the DC/OS CLI
curl https://raw.githubusercontent.com/dcos/dcos-vagrant/master/ci/dcos-install-cli.sh | bash
-
Create the example app:
dcos marathon app add examples/minuteman/minuteman.json -
Wait for Marathon to deploy 3 app instances.
dcos marathon app show minuteman | jq -r '"\(.tasksHealthy)/\(.tasksRunning)/\(.instances)"' -
Visit the load balanced endpoint from any of the master or agent nodes in the cluster. You can do this by running the following commands:
vagrant ssh a1 curl http://1.2.3.4:5000If you invoke multiple curl requests, you should see different backends responding.
Add a label in the format vip_PORT${IDX} -> tcp://1.2.3.4:5000. Where, 1.2.3.4:5000 is the VIP. ${IDX} should be replaced by the index for the port, beginning from 0 in the resource allocations.