Artifacts

The information on this page is written for Vamp v0.9.2

Vamp has a few basic entities or artifacts you can work with, these can be classed as static resource descriptions and dynamic runtime entities. Note that API actions on static resource descriptions are mostly synchronous, while API actions on dynamic runtime entities are largely asychronous.

Dynamic runtime entities

  • Deployments are running blueprints. You can have many deployments from one blueprint and perform actions on each at runtime. Plus, you can turn any running deployment into a blueprint. Read more…
  • Gateways are the “stable” routing endpoint - defined by a port (incoming) and routes (outgoing). Read more…
  • Workflows are apps (services) deployed on cluster, used for dynamically changing the runtime configuration (e.g. SLA, scaling, condition weight update). Read more…

Static resource descriptions

  • Blueprints are, well, blueprints! They describe how breeds work in runtime and what properties they should have. Read more…
  • Breeds describe single services and their dependencies. Read more…
  • Scales define the size of a deployed service Read more…

Working across multiple teams

In larger companies with multiple teams working together on a large project, all required information is often not available at the same time. To facilitate this style of working, Vamp allows you to set placeholders. Placeholders let you communicate with other teams using simple references and gradually build up a complicated deployment. Vamp will only check references at deployment time, this means:

  • Breeds can be referenced in blueprints before they exist
  • You do not need to know the contents of an SLA when you reference it.
  • You can reference a variable that someone else should fill in.

Read more about referencing artifacts and environment variables.

What next?