Build & Release / Infrastructure as a Code (BOSH (IaaS Supported…
Build & Release / Infrastructure as a Code
The configuration files can be written in
HashiCorp Configuration Language
Physical machines, VMs, network switches, containers - treated as resources
: is responsible for understanding API interactions and exposing resources
: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.
: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.
Infrastructure as Code
: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors."
Open source tool for release engineering, deployment, lifecycle management, and monitoring of distributed systems
Primarily developed to deploy the Cloud Foundry PaaS
Can also deploy Hadoop, etc.
Creates VMs on top of
, configures them to suit the requirements, and then deploys the applications on them
IaaS Supported Providers
Cloud Provider Interface (CPI)
is placed on top of a
, and consists of a versioned collection of configuration properties, templates, scripts, source code, etc., to build and deploy software.
is a collection of VMs which are built from
, populated with specific
on top of them and having disks to keep persistent data.
is a versioned, IaaS-specific, Operating System image with some pre-installed utilities (e.g. BOSH Agent). Stemcells do not contain any application-specific code. The BOSH team is in charge of releasing stemcells.
is the orchestrator component of BOSH, which controls the VM creation and deployment. It also controls software and service lifecycle events. We need to upload
manifest files to the
processes the manifest file and does the deployment.