Deploying and managing physical Assets

Assets can be managed using two options as below

1. Manual from UI

Asset Creation can be done from the UI by choosing "Asset" Nav in the Application overview Nav bar and then clicking the Add Asset button.

You will see a pop-up as below.


Select the type of asset to see more details. At the time of this writing there are two types of Assets as below. The asset types will be growing depending on various cloud and services we start integrating.

Server is a pre-configured server that need to be used as a target for your deployment needs.

Cluster is a ECS cluster that need to be used as a target ECS cluster for your ECS services and containers.

Assets can be edited by selecting the required asset and clicking on the same, and using the edit pop-up for the asset.


2. Automated via various plugins/templates

Each of the templates would create assets they need and link them to a role in the environment as part of the creation. These actions are performed by various plugins as needed. When these plugins are part of a task and then bundled in a template, templates get the ability to create assets.

For example: Template "Single Container Service for Docker Host" is used to configure a new Application on CloudMunch Platform, two types of Assets are added

  1. Docker Host - The details collected during the Application import/configuration path for a Docker Host becomes available as an Asset. If user wants to add a Docker Host outside of the Application import path, it can be done here. A new Asset is added only of type server.
  2. Containers - Every container of the Application that is created gets added as an Asset. During the import process if all available inputs are accurate, the first container is launched and you would see the container on this list. Subsequently, any container launched for the Application will be listed here.