Container Component Settings

Name

Enter a name for your container component in the blueprint.

Description

Summarize your container component for the benefit of other architects.

Image

Enter the full name of an image in a managed registry such as a private registry or Docker Hub registry, for example registry.hub.docker.com/library/python.

Commands

Enter a command that applies to the specified image, such as python app.py. The command is run when the container provisioning process is started.

Links

Links provide another way to connect containers on a single host or across hosts. Enter one or more services to which this container is to be linked, such as redis or datadog.

Networks

Specify the existing networks that are defined for the selected image. You can also create a new network.

When you add a network container component to the design form, the networks that you specify here are listed as available options for selection.

Port bindings

Specify the port bindings for the selected network. Point bindings consist of protocol host, host port, and container port.

Publish All Ports

Select the check mark box to expose the ports that are used in the container image to all users.

Host name

Specify the container host name. If no name is specified, the value defaults to the name of the container component in the blueprint.

Network mode

Specify the networking stack of the container. If no value is specified, the container is configured in Bridge network mode.

Volumes

Specify the storage volumes that are mapped from the host to be used by the container.

Volumes from

Specify the storage volumes to be inherited from another container.

Working directory

Specify the directory from which to run commands.

Deployment policy

Specify a deployment policy to set preferences for which set of hosts to use for deploying this container. You can associate deployment policies to hosts, policies, and container definitions to set a preference for hosts, policies, and quotas when deploying a container.

You can add a deployment policy by using the Containers tab in vRealize Automation.

Cluster size

Specify the number of instances to generate as a cluster from this container.

Restart policy

Specify a restart policy for how a container is restarted on exit.

Max restart

If you selected on-failure as a restart policy, you can specify the maximum number of restarts.

CPU shares

Specify the number of CPU shares allocated for the provisioned resource.

Memory limit

Specify a number between 0 and the memory available in the placement zone. This is the total memory available for resources in this placement. 0 means no limit.

Memory swap

Total memory limit.

Affinity constraints

Defines rules for provisioning of containers on the same or different hosts.

• Affinity type

  For anti-affinity, the containers are placed on different hosts, otherwise they are placed on the same host .

• Service

  The service name that is available from the drop-down menu matches the container component name specified in the Name field on the General tab.

• Constraint

  A hard constraint specifies that if the constraint cannot be satisfied, provisioning should fail. A soft constraint specifies that if the constraint cannot be satisfied, provisioning should continue.

Name

The variable name.

Binding

Bind the variable to another property, that is a part of the template. When you select binding, you must input a value in the _resource~TemplateComponent~TemplateComponentProperty syntax.

Value

The value of the environment variable or if you selected binding, the value of the property you want to bind.

Name

Enter the name of a custom property or select an available custom property from the drop-down menu.

Value

Enter or edit a value to associate with the custom property name.

Encrypted

You can choose to encrypt the property value, for example, if the value is a password.

Overridable

You can specify that the property value can be overridden by the next or subsequent person who uses the property. Typically, this is another architect, but if you select Show in request, your business users are able to see and edit property values when they request catalog items.

Show in Request

If you want to display the property name and value to your end users, you can select to display the property on the request form when requesting machine provisioning. You must also select Overridable if you want users to provide a value.

None

Default. No health checks are configured.

HTTP

If you select HTTP, you must provide an API to access and an HTTP method and version to use . The API is relative and you do not need to enter the address of the container. You can also specify a timeout period for the operation and set health thresholds.

For example, a healthy threshold of 2 means that two consecutive successful calls must occur for the container to be considered healthy and in the RUNNING status. An unhealthy threshold of 2 means that two unsuccessful calls must occur for the container to be considered unhealthy and in the ERROR status. For all the states in between the healthy and unhealthy thresholds, the container status is DEGRADED.

TCP connection

If you select TCP connection, you must only enter a port for the container. The health check attempts to establish a TCP connection with the container on the provided port. You can also specify a timeout value for the operation and set healthy or unhealthy thresholds as with HTTP.

Command

If you select Command, you must enter a command to be executed on the container. The success of the health check is determined by the exit status of the command.

Ignore health check on provision

Uncheck this option to force health check on provision. By forcing it, a container is not considered provisioned until one successful health check passes.

Autodeploy

Automatic redeployment of containers when they are in ERROR state.

Driver

Select a logging format from the drop-down menu.

Options

Enter driver options using a name and value format that adheres to the logging format.