Creating and managing Environments

Environments are logical representation of the deployment of your Application. An environment is created as a result of executing Tasks that are part of the Template you applied to setup your Application on CloudMunch. These Tasks can be either

  1. Provision task that automatically creates the environment, or
  2. Build task with specific steps that create an environment

Environments have the following key properties

  • Name: The name is set either by an executing the task or taken as input. For example, in the "Single Container Service for Docker Host" template, the build task uses a pattern like <stage>_<application-name>-<creating_task>-<build#> for the name. When a provision task is executed, the name is a user input.
  • Status: The initial status of the environment is set by the task that creates the environment. The subsequent status is set by any action is performed.
  • Roles: Roles are a group of nodes in an environment that perform common function for a given application. These can be created dynamically as part of provisioning or pre-configured while creating application. 
  • Assets: Assets are various resources that are involved in the application deployment and monitoring.
  • Variables: Variables are the context of the environment when it was created. These can be system context or user context depending on what variables have been configured within.
  • Created by Task: This shows the task that created the environment. Task without the run of the task does not provide a complete picture. In this case, Creating task is provided both with the name of the task and the run number that created this instance of the environment.
  • Updated by Task: This shows the task that updated the environment. Typically the tasks that updates are the environment actions tasks.
  • URL: The url is your Application url that can be used the access the Application running in thisEenvironment. This is typically filled by the Task that creates the Environment.
  • History: Shows all the actions performed on the environment. This serves as an audit log.

 You can learn how to create and execute Tasks that create Environments here.