Cloud Providers and Host Groups

A Cloud Provider is used to enable Nirmata access to your public or private cloud resources.

A Host Group allows you to create pools of identical resources. You can create a single Host Group, or separate Host Groups for services, classes of services, teams, or any other classification, and then use Resource Selection. policies to control how the Host Group is used.

The setup for any public Cloud Provider type has the following general steps:
  1. Prepare a VM template, or similar, as detailed in the Host Setup section.
  2. Create the Cloud Provider in Nirmata
  3. Create one or more Host Groups in Nirmata

The setup for private clouds, has an additional step. You will first need run the Nirmata Private Cloud Agent and then configure a Cloud Provider. See details in the Private Cloud. setup section.

Host Setup

Here are the general requirements for a Host that is managed by Nirmata.

  1. Can be any Linux flavor that can run Docker.
  2. Requires Docker 1.10+ (see Docker installation guide.)
  3. The Nirmata agent must be installed (see Using cloud-init.)

Using cloud-init

If your OS provisioning system supports cloud-init (sometimes called Cloud-Config), or other post provisioning mechanisms, you can easily install Docker and the Nirmata Agent as follows (example shown is for Ubuntu and the Direct Connect Host Group):

#!/bin/bash -x
# Install Docker
wget -qO- https://get.docker.com/ | sh

# Install Nirmata Agent
sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud other --hostgroup <key>

Nirmata Agent Setup

To setup the Nirmata agent on the host instance

  1. Run the Nirmata Agent configuration script:

    sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud <CloudProvider> --hostgroup <HostGroupId>
    
            where:
              CloudProvider = [aws | azure | oraclecs | openstack | vsphere | google | digitalocean | other]
              HostGroupId = unique ID for the Host Group. Only required for the 'Direct Connect' container hosts
    
  2. Verify that Nirmata Agent has started:

    sudo docker ps
    

Note: setup-nirmata-agent.sh uses upstart/systemd to enable management of nirmata-agent as a service. If upstart or systemd is not available on your host instance, you can directly run nirmata-agent container using docker.

To start/stop Nirmata agent you can use:

Upstart:

sudo start nirmata-agent
sudo stop nirmata-agent

Systemd:

systemctl start nirmata-agent
systemctl stop nirmata-agent

To setup the Nirmata agent on any host instance using commandline (for ‘other’ cloud provider):

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v /var/log/nirmata-agent:/var/log/supervisor \
           -v /opt/nirmata/conf:/usr/share/nirmata/conf -v /opt/nirmata/db:/usr/share/nirmata/db --name=nirmata-agent \
           -v /sys:/sys:ro -e NIRMATA_HOST_ADDRESS=<HostName> -e NIRMATA_CLOUD_PROVIDER_TYPE=other -e NIRMATA_USE_HTTP=false\
           -e NIRMATA_HOST_GATEWAY=www.nirmata.io/host-gateway/manager -e NIRMATA_LABELS=<HostLabels> -e NIRMATA_HOST_GROUP_ID=<HostGroupId> nirmata/nirmata-agent:latest

where:
  HostName = Host name or IP address of your host
  HostGroupId = unique ID for the Host Group. Required for the 'other' cloud provider type
  HostLabels = Host labels in json format without any spaces between keys and values. e.g. NIRMATA_LABELS={\"host-type\":\"SSD\",\"host-location\":\"us-east\"}

Host Labels

You can setup host labels when installing the Nirmata agent. Nirmata agent can detect host labels directly from docker-engine. Host labels can also be passed in to Nirmata agent using environment variables.

Docker engine:

Add the label option when start docker engine. Depending on your docker-engine installation, you can add the label option to DOCKER_OPTS
   e.g. --label environment-type=\"production\"

Environment variable:

You can add the labels to Nirmata agent as environment variables. For this, you can modify the Nirmata agent init script (/etc/init/nirmata-agent.conf) and update the HOST_LABELS field. The labels should be specified in json format without any whitespaces.
   e.g. HOST_LABELS={\"host-type\":\"SSD\",\"host-location\":\"us-east\"}

Once you setup the host labels, you will need to restart the Nirmata agent. The host labels should be detected and display in Nirmata console once the host connects. Now, you can use these labels to control the placement of your containers.

HTTP Proxy

You can setup Nirmata agent to use a HTTP proxy to communicate to the internet. Here are the instructions

Upstart:

Add the following to the docker run command in /etc/init/nirmata-agent.conf file:
    -e HTTPS_PROXY=<http(s) proxy address and port>

e.g. -e HTTPS_PROXY=https://192.162.11.11:443

Systemd:

Add the following to the docker run command in /opt/nirmata/bin/start-nirmata-agent.sh file:
    -e HTTPS_PROXY=<http(s) proxy address and port>

e.g. -e HTTPS_PROXY=https://192.162.11.11:443

Restart Nirmata agent using the appropriate command.

Host Networking

Nirmata does nor require any special networking setup, and works with your existing Host networking. Nirmata uses the Docker bridge network mode on each Host, so each application service is addressable using the Host IP address and an allocated (static or dynamic) port. Based on the cloud provider, Nirmata will detect the public and private IP addresses of your Host. When available, the Host’s private IP address will be used for communication between services.

Amazon Web Services

Setting up Amazon Web Services (AWS) consists of the following steps:
  1. Create an Amazon Machine Image (AMI).
  2. Setup AWS.
  3. Create a AWS Cloud Provider.
  4. Create a AWS Host Group.

Create an Amazon Machine Image (AMI)

You can create your own AMI with Docker running on it. The AMI has the following requirements:
  1. Can be any Linux flavor that can run Docker
  2. Requires Docker 1.10+ (download)

You will need to setup the Nirmata agent container on that instance by running the command:

sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud aws

Once the instance is setup, create an AMI via the AWS console. This AMI can be used with your Auto Scaling Group or Spot Fleet instances.

Setup AWS

Nirmata needs to know which host instances should be used to deploy applications. For AWS, you can choose to configure hosts using any of the following options:

Using Auto Scaling Groups (ASG)

Detailed information on creating and managing Auto Scaling groups can be found here:

The Launch Configuration of the ASG must use the AMI created earlier or you can use a standard Linux AMI and use Using cloud-init to install docker and Nirmata agent.

This will ensure that Docker and Nirmata Host Agent are pre installed.

_images/aws-launch-config.png

Using Spot Fleet Requests

You can use AWS Spot Fleet Requests with Nirmata to take advantage of discounted spot instance pricing. To use Spot Fleet Requests, you need to first create the Spot Fleet Requests using AWS console. Detailed information on creating and managing Spot Fleet Requests can be found here:

The Spot Fleet Request can use the AMI created earlier or you can use a standard Linux AMI and use Using cloud-init to install docker and Nirmata agent.

Using Launch Configurations

AWS Launch Configurations can be used with Nirmata in order to provision/deprovision EC2 instances from Nirmata. Detailed information on creating a Launch Configuration can be found here:

The Launch Configurations must use the AMI created earlier or you can use a standard Linux AMI and use Using cloud-init to install docker and Nirmata agent.

Create a AWS Cloud Provider

Nirmata requires read-only access to EC2 service if using ASGs or Spot Fleet Requests and full access to EC2 service if using Launch Configuration to provision your VMs. The secure way to provide access is by configuring an IAM role for Nirmata in your AWS account. To configure a role, you will need the Nirmata AWS account ID and an unique external ID. When the role is configured, you provide Nirmata the role ARN (Amazon Resource Name).

This process seems involved, but only takes a few minutes to set up! Here are the detailed steps:

  1. Launch the Add Cloud Provider Wizard and select AWS as the provider.
_images/AWS-IAM-Role-0.png
  1. The Settings page with show you the Nirmata Account ID (094919933512) and a unique external ID for the Cloud Provider. You will require these in a later step:
_images/AWS-IAM-Role-6.png
  1. Login to your AWS account. Select IAM and navigate to the option to create a new user role:
_images/AWS-IAM-Role-1.png _images/AWS-IAM-Role-2.png _images/AWS-IAM-Role-3.png
  1. Provide a name (e.g. ‘nirmata’) and go to the next page:
_images/AWS-IAM-Role-4-1.png
  1. Select the ‘Roles for Cross-Account Access’ option, and then select ‘Provide access to a 3rd party AWS account’ option:
_images/AWS-IAM-Role-5-1.png
  1. Enter in the Nirmata AWS Account ID (094919933512) and the unique Cloud Provider External ID shown in the Nirmata Cloud Provider wizard:
_images/AWS-IAM-Role-7-1.png
  1. On the next page, select the ‘AmazonEC2ReadOnlyAccess’ and ‘AmazonEC2AutomationRole’ to allow Nirmata to provision EC2 instances:
_images/AWS-IAM-Role-8-1.png

You can also create a new custom policy (e.g. NirmataAutomationPolicy) for more granular access control. Below is the Policy Document that can be used in the custom policy. This policy limits Start/Stop/TerminateInstance to the instances created by Nirmata with appropriate tag:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ec2:RunInstances",
                "ec2:CreateTags",
                "ec2:Describe*"
            ],
            "Resource": [
                "*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "ec2:StartInstances",
                "ec2:StopInstances",
                "ec2:TerminateInstances"
            ],
            "Resource": "arn:aws:ec2:<region>:<account>:instance/*",
            "Condition": {
                "StringEquals": {
                    "ec2:ResourceTag/com.nirmata.createdBy": "nirmata"
                }
            }
        },
        {
            "Effect": "Allow",
            "Action": "autoscaling:Describe*",
            "Resource": "*"
        }
    ]
}

NOTE: be sure to replace the <region> and <account> placeholders, with the allowed region or “*” to allow all regions, and your AWS account ID.

  1. Finish creating the AWS IAM role:
_images/AWS-IAM-Role-10-1.png
  1. Select the role you just created and copy the Role ARN:
_images/AWS-IAM-Role-11.png
  1. Paste the Role ARN into the Nirmata Add Cloud Provider Wizard. You can then click ‘Next’ and Nirmata will validate the settings:
_images/AWS-IAM-Role-12.png

Creating AWS Cloud Provider Video

Create a AWS Host Group

Create a Host Group by specifying the Host Group Name and selecting the Cloud Provider. Then you need to select the host instance type (ASG, Spot Fleet Request or Launch Configuration).

You can also update the Resource Selection Rule for this Host Group

_images/create-aws-host-group-1.png _images/create-aws-host-group-2.png

Troubleshooting AWS Host creation

In some cases, host creation on AWS may fail due to various reasons. Here are a few things to check when the host creation fails:

  1. Check if docker engine and Nirmata agent were successfully installed and started on the instances provisioned on AWS. To check if Nirmata agent is running, ssh to your AWS instance and use commad: sudo docker ps. This command will list all the running containers. Verify that the nirmata-agent container is running
  2. If Nirmata agent is running on your AWS instance but the state displaying on the Nirmata console is ‘Pending Connect’ or ‘Not Connected’, the Nirmata agent might be unable to connect back to Nirmata server. Verify that AWS security groups for your instance allow outbound HTTPS traffic. You can check be accessing a website e.g. www.google.com using curl or wget (e.g. curl -XGET http://www.google.com)
  3. When creating AWS instances using Launch Configuration mode, ensure that the network selected in Nirmata is the same as the network of security group configured for the launch configuration. If this is not the case, instance creation will fail.

Microsoft Azure

Settine up Microsoft Azure consists of the following steps:
  1. Create Azure Provider.
  2. Create Azure Host Group.

Create Azure Provider

Create an Azure Provider by entering the Subscription ID, Tenant ID, Client ID and Client Secret. Nirmata uses Azure Active Directory for authentication so you need to ensure that you have setup Azure Active Directory. For setting up Azure Active Directory, refer to the documentation (https://azure.microsoft.com/en-us/documentation/services/active-directory/)

Once you provide the required information, Nirmata will validate access to your account.

Create Azure Host Group

Nirmata integrates with Azure Resource Manager. Prior to creating a Host Group in Nirmata, you need to create a Resource Group in Azure. Within your resource group, you should also create a network, security group(s) and storage account. These will be using while creating the host group.

Create a host group by selecting the Azure provider, specifying the number of desired hosts and selecting the resource group. Select the image, instance type, virtual network, security group and the strage account. You can also select if you want to attach public IP addresses. Enter the username and password to access your instance.

You need to install docker engine and Nirmata agent using cloud-init by adding the installation script in User Data. Clicking on ‘Install Nirmata Agent’ will add the following script to User Data:

#!/bin/bash -x
# Install Docker
wget -qO- https://get.docker.com/ | sh

# Install Nirmata Agent
sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud azure

Once this is done, Nirmata will create and setup VMs. Once the VMs are powered on, they will connect to Nirmata SaaS. Now you can create applications and deploy them to your Azure resources.

Google Compute Engine

Setting up Google Compute Engine consists of the following steps:
  1. Create GCE Provider.
  2. Create GCE Host Group.

Create GCE Provider

Here are the detailed steps to create a cloud provider for Google Compute Engine:

Launch the Add Cloud Provider Wizard and select Google Compute Engine as the provider.

In the Settings page provide the service account key. This can be generated from Google Cloud Platform account.

Click Next to validate the settings and complete the wizard.

Create GCE Host Group

To create a Host Group, provide the name and select the Cloud Provider. Then select the desired host count.

In the Settings Tab enter value for:
  • Zone
  • Configuration Type:
    • Image: to use a pre-built image
    • Instance Group: to use the instance group

Provide additional settings based on the configuration type selected.

On the Tags tab enter the tags to apply to the instances.

On the StartUp Script Tab, click on checkbox to use a default script to install docker and Nirmata agent or provide your own script

Once all the information is provided and the wizard is completed, a host group will be created and the instances will be provisioned. Once the instances connect to Nirmata, they are ready to be used to deploy your application.

Oracle Public Cloud

Setting up Oracle Public Cloud consists of the following steps:
  1. Create Oracle Public Cloud Provider.
  2. Create Oracle Public Cloud Host Group.

Create Oracle Public Cloud Provider

Here are the detailed steps to create a cloud provider for Oracle Public Cloud:

Launch the Add Cloud Provider Wizard and select Oracle Public Cloud Services as the provider.

In the Settings page provide the endpoint URL, identity domain, username and password. The endpoint URL and identity domain can be found in your Oracle Public Cloud account.

_images/create-oracle-cp.png

Click Next to validate the settings and complete the wizard.

Create Oracle Public Cloud Host Group

To create a Host Group, provide the name and select the Cloud Provider.

In the Settings Tab select host instances:
  • Orchestration - to discover instances provisioned by the selected orchestration
  • Identity Domain - to discover all instances in the identity domain

Once all the information is provided and the wizard is completed, a host group will be created and the instances will be discovered. Once the instances connect to Nirmata, they are ready to be used to deploy your application.

_images/create-oracle-hg.png

Note: For Oracle Public Cloud, the instances need to be created directly using the Oracle Public Cloud Console or API. For the instance to be discovered by Nirmata, docker engine and Nirmata agent should be installed on running on the instance. See the Host Setup section.

Digital Ocean

Setting up Digital Ocean consists of the following steps:
  1. Create an Image.
  2. Create a Digital Ocean Provider.
  3. Create a Digital Ocean Host Group.

Create an Image

Create and launch a Linux droplet in Digital Ocean. Connect to the VM and setup Nirmata agent by running the following command:

sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud digitalocean

Now, power down the droplet and create an image snapshot from the Images page. This image should be selected when creating a host group for your Digital Ocean provider

_images/create-digital-ocean-image.png

Create a Digital Ocean Provider

Create an API key on the Digital Ocean console. You can create the API key here

_images/create-digital-ocean-api-key.png

In Nirmata, create a Digital Ocean cloud provider by providing the API Key.

_images/create-digital-ocean-provider-1.png _images/create-digital-ocean-provider-2.png

Create a Digital Ocean Host Group

Create a host group by selecting the Digital Ocean cloud provider, specifying the number of desired hosts, region and selecting the VM image created earlier. Select the droplet size. You can also update the Resource Selection Rule for this Host Group.

_images/create-digital-ocean-host-group-1.png _images/create-digital-ocean-host-group-2.png

Once this is done, Nirmata will create and setup droplets (VMs). Once the VMs are powered on, they will connect to Nirmata SaaS. Now you can create applications and deploy them to your Digital Ocean resources.

Cisco Metapod

Setting up Cisco Metapod consists of the following steps:
  1. Create a VM Template (Optional).
  2. Create a Cisco Metapod Provider.
  3. Create a Cisco Metapod Host Group.

Create a VM Template (Optional)

Create and launch a Linux VM using Metapod console. Connect to the VM, install docker engine and setup Nirmata agent by running the following command:

sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud openstack

Now you can create a template for the VM using Metapod Horizon. This template should be selected when creating a host group for your Metapod provider.

Note: You can skip this step by using cloud-init to install docker and Nirmata agent while creating the Cisco Metapod Hostgroup in Nirmata (Create a Cisco Metapod Host Group)

Create a Cisco Metapod Provider

Create a Cisco Metapod provider by providing the Keystone identity service URL (https://serviceaddress:5000/v2.0/), project name, and credentials. After entering the credentials, validate access to your cloud provider before closing the wizard.

_images/create-metapod-provider-1.png _images/create-metapod-provider-2.png

Create a Cisco Metapod Host Group

Create a host group by selecting the Metapod provider, specifying the number of desired hosts and selecting the template created earlier. Provide the resource information such as flavor, keypair, network and security group. You can install docker engine and Nirmata agent using cloud-init by adding the installation script in User Data. You can also update the Resource Selection Rule for this Host Group:

#!/bin/bash -x
# Install Docker
wget -qO- https://get.docker.com/ | sh

# Install Nirmata Agent
sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud openstack
_images/create-metapod-hg-0.png _images/create-metapod-hg-1.png _images/create-metapod-hg-2.png

Once this is done, Nirmata will create and setup VMs. Once the VMs are powered on, they will connect to Nirmata SaaS. Now you can create applications and deploy them to your Cisco Metapod resources.

VMware vSphere

To securely connect Nirmata to a vSphere in your Private Cloud or Data Center, first setup a Private Cloud.

Setting up VMware consists of the following steps:
  1. Setup a Resource Pool in vCenter.
  2. Create a vSphere template.
  3. Create a VMware vSphere Cloud Provider.
  4. Create a VMware vSphere Host Group.

Setup a Resource Pool in vCenter

Refer to VMWare vSphere documentation for instructions on setting up a Resource Pool.

Create a vSphere template

Create and launch a Linux VM using vSphere. Connect to the VM and setup Nirmata agent by running the following command:

sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud vsphere

Now you can create a template for the VM using vCenter. This template should be selected when creating a host group for your vSphere provider

Create a VMware vSphere Cloud Provider

Create a VMWare vSphere provider by providing the vCenter SDK URL (http://serveraddress/sdk) and credentials:

_images/create-vsphere-provider-1.png

After entering the credentials, validate access to your cloud provider before closing the wizard:

_images/create-vsphere-provider-2.png

Create a VMware vSphere Host Group

Create a host group by selecting the vSphere provider, specifying the number of desired hosts, providing the data center information and selecting the resource pool, image template, flavor, network and datastore. You can also update the Resource Selection Rule for this Host Group.

_images/create-vsphere-hg-0.png _images/create-vsphere-hg-1.png

Once this is done, Nirmata will create and setup VMs. Once the VMs are powered on, they will connect to Nirmata SaaS. Now you can create applications and deploy them to your VMWare vSphere resources.

OpenStack

To securely connect Nirmata to OpenStack in your Private Cloud or Data Center, first setup a Private Cloud.

Setting up OpenStack consists of the following steps:
  1. Create a VM Template.
  2. Create OpenStack Provider.
  3. Create OpenStack Host Group.

Create a VM Template

Create and launch a Linux VM using OpenStack. Connect to the VM and setup Nirmata agent by running the following command:

sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud openstack

Now you can create a template for the VM using OpenStack Horizon. This template should be selected when creating a host group for your OpenStack provider

Create OpenStack Provider

Create an OpenStack provider by providing Keystone identity service URL (https://serviceaddress:5000/v2.0/), project name and the credentials:

_images/create-openstack-provider-1.png

After entering the credentials, validate access to your cloud provider before closing the wizard:

_images/create-openstack-provider-2.png

Create OpenStack Host Group

Create a host group by selecting the OpenStack provider, specifying the number of desired hosts and selecting the template created earlier. Provide the resource information such as flavor, keypair, network and security group. You can also update the Resource Selection Rule for this Host Group.

_images/create-openstack-hg-0.png _images/create-vsphere-hg-1.png

Once this is done, Nirmata will create and setup VMs. Once the VMs start, they will connect to Nirmata SaaS. Now you can create applications and deploy them to your OpenStack resources.

Other Cloud Providers & Direct Connect Hosts

You can bring any (public or private cloud) server into Nirmata using the ‘Direct Connect’ cloud provider type. In this type of deployment you control which servers are made available in a Host Group. Auto Scaling and Auto Recovery of hosts is not enabled for this provider type.

To setup a Create a Host Group of type ‘Direct Connect’ by navigating to Host Groups -> Direct Connect -> Add Host Group. Give your Host Group a name and drill down into its details page. This will display an message as follows:

To connect a Host, run the Host Agent with Host Group ID: 9k1617f2-932d-4918-a6f8-e9863a27649f

To complete the setup, launch the Nirmata agent passing in the provider type and Host Group ID:

sudo curl -sSL http://www.nirmata.io/nirmata-host-agent/setup-nirmata-agent.sh | sudo sh -s -- --cloud other --hostgroup <HostGroupId>

        where HostGroupId is the unique Host Group ID for your Host Group

If your server is a Virtual Machine, you can also save it as a template or image to create additional Nirmata Host instances from it.

Note: Remove the file: /usr/share/nirmata/conf/host_agent.id and the directory: /opt/nirmata/db/ prior to saving the VM as a template.

Bare Metal Servers

You can use the Other Cloud Providers & Direct Connect Hosts. option to configure Host Groups for bare metal (physical) servers in Nirmata.

Private Cloud

Nirmata can securely manage your VMware and OpenStack cloud resources, and Docker Image Registries, in your Data Center. To connect your Private Cloud, you will need to run the Nirmata Private Cloud Agent, on a system within your Data Center that has connectivity to your cloud management system (e.g. VMware’s vCenter) and/or your private Docker Image Registry. Once the Nirmata Private Cloud Agent is connected, you can then provision Cloud Providers and Image Registries and select the appropriate private cloud for these systems.

Here are the steps to setup a Private Cloud:

  1. In Nirmata go to Settings -> Private cloud, select the option to add a private cloud, and provide a unique name.
_images/private-cloud-setup.png
  1. Setup a system in your Data Center for the Nirmata Private Cloud agent, and run the command to install the agent, using the unique ID for your Private Cloud:

    curl -sSL http://www.nirmata.io/nirmata-private-cloud-agent/setup-nirmata-private-cloud-agent.sh | sudo sh -s b71025b0-068f-40a1-8804-f03e52c598db
    

Once the Private Cloud is connected, you can select it when creating an Image Registry, a VMware vSphere Cloud Provider, or an OpenStack Cloud Provider. Here is an example:

_images/private-image-registry.png

Monitoring Cloud Resources

You can monitor your host groups by clicking on the host group name. You should see a list of all the hosts that are in your host group. The State column indicates whether the host is connected to Nirmata SaaS or not. In case the host is not connected follow the instructions to create a host group for your cloud provider. Containers will not be deployed to hosts that are not connected.

_images/host-monitoring-1.png

For each host, you can view additional information such as average CPU utilization, average memory utilization, per container CPU and memory utilization. You can also start, stop the containers and view container logs.

_images/host-monitoring-2.png _images/host-monitoring-3.png