Deploy your first blueprint

If everything went to plan, you should have your Vamp installation up and running. If not, please follow the Vamp hello world quick setup steps. Now we’re ready to check out some of Vamp’s features. In this tutorial we will:

  1. Deploy a monolith, using either the Vamp UI or the Vamp API
  2. Check out the deployed application
  3. Get some metrics on the running application
  4. Change the scale and load-balancing
  5. Chaos monkey!

Deploy a monolith

Imagine you or the company you work for still use monolithic applications. I know, it sounds far fetched… This application is conveniently called Sava monolith and is at version 1.0.

You’ve managed to wrap your monolith in a Docker container, which lives in the Docker hub under magneticio/sava:1.0.0. Your app normally runs on port 8080 but you want to expose it under port 9050 in this case. Let’s deploy this through Vamp using the following simple blueprint. Don’t worry too much about what means what: we’ll get there. You can choose to deploy this blueprint either using the Vamp UI or using the Vamp API.

name: sava:1.0
  9050: sava/webport
        name: sava:1.0.0
        deployable: magneticio/sava:1.0.0
          webport: 8080/http
        cpu: 0.2       
        memory: 64MB
        instances: 1

Deploy using the Vamp UI

In the Vamp UI, go to the Blueprints page and click Add new button (top right). Paste in the above blueprint and click Save. Vamp will store the blueprint and make it available for deployment. Now click Deploy as. You’ll be prompted to give your deployment a name, let’s call it sava, then click Deploy to start the deployment.

Deploy using the Vamp API

You could also use your favourite tools like Postman (, HTTPie ( - httpie) or Curl to post this blueprint directly to the api/v1/deployments endpoint of Vamp.

Take care to set the correct Content-Type: application/x-yaml header on the POST request. Vamp is kinda strict with regard to content types, because we support JSON and YAML so we need to know what you are sending.
If you run on Docker machine, use docker-machine ip default instead of localhost.

  • Using curl

    curl -v -X POST --data-binary @sava_1.0.yaml -H "Content-Type: application/x-yaml" http://localhost:8080/api/v1/deployments
  • Using httpie

    http POST http://localhost:8080/api/v1/deployments Content-Type:application/x-yaml < sava_1.0.yaml

After POST-ing, Vamp should respond with a 202 Accepted message and return a JSON blob. This means Vamp is trying to deploy your container. You’ll notice some parts are filled in for you, like a default scale, a default routing and of course a UUID as a name. You can also use the RESTful API to create a deployment with a custom name - simple PUT request to http://localhost:8080/api/v1/deployments/DEPLOYMENT_CUSTOM_NAME

Check out the deployed application

You can follow the deployment process of our container by checking the /api/v1/deployments endpoint and checking when the state field changes from ReadyForDeployment to Deployed. You can also check Marathon’s GUI.

When the application is fully deployed, you can check it out at Vamp host address + the port that was assigned in the blueprint, e.g: It should report a refreshing hipster lorem ipsum ( upon each reload.

See check Vamp is up and running for a full ist of all services exposed in the hello world setup.

Get some metrics on the running application

We can use a simple tool like Apache Bench (apache - ab) to put some load on our application and see some of the metrics flowing into the dashboard. Use the following command to send 10000 requests using 15 threads to our Sava app.

ab -k -c 15 -n 10000 http://localhost:9050/


ab -k -c 15 -n 10000 http://`docker-machine ip default`:9050/

You should see the metrics spike and some pretty charts being drawn on the sava/9050 gateway page:

Change scale and load-balancing

Vamp will automatically load-balance services. Let’s change the scale of the service. Go back to the Deployments page and open the sava deployment. Click the edit icon under SCALE and enter 3 in the instances field. Click Save and Vamp will automatically scale up the number of running instances (of course permitting underlying resources) and load-balance these to the outside world using the gateway feature.

Chaos monkey

Now let’s try something fun. Go to the Marathon UI (on port 9090) and find the Sava container running. Now select destroy to kill the container. Watch Vamp detecting that issue and making sure that the defined number of instances is spun up again as soon as possible, while making sure the loadbalancing routing rules are also updated to reflect the changed IPs and ports of the instances.