You can add predefined property groups to a containers component in a vRealize Automation blueprint. When machines are provisioned by using a blueprint that contain these properties, the provisioned machine is registered as a Docker Container host machine.

Containers for vRealize Automation supplied the following two property groups of container-specific custom properties. When you add a container component to a blueprint you can add these property groups to the container to register provisioned machines as container hosts.

  • Container host properties with certificate authentication

  • Container host properties with user/password authentication

These property groups are visible in vRealize Automation when you select Administration > Property Dictionary > Property Groups.

Because property groups are shared by all tenants, if you are working in a multi-tenant environment, consider cloning and customizing your properties. By uniquely naming property groups and properties in the groups, you can edit them to define custom values for use in a specific tenant.

The most commonly used properties are Container.Auth.PublicKey and Container.Auth.PrivateKey in which the container administrator provides the client certificate for authenticating with the container host.

Table 1. Containers Custom Properties

Property

Description

containers.ipam.driver

For use with containers only. Specifies the IPAM driver to be used when adding a Containers network component to a blueprint. The supported values depend on the drivers that are installed in the container host environment in which they are used. For example, a supported value might be infoblox or calico depending on the IPAM plug-ins that are installed on the container host.

containers.network.driver

For use with containers only. Specifies the network driver to be used when adding a Containers network component to a blueprint. The supported values depend on the drivers that are installed in the container host environment in which they are used. By default, Docker-supplied network drivers include bridge, overlay, and macvlan, while Virtual Container Host (VCH)-supplied network drivers include the bridge driver. Third-party network drivers such as weave and calico might also be available, depending on what networking plug-ins are installed on the container host.

Container

For use with containers only. The default value is App.Docker and is required. Do not modify this property.

Container.Auth.User

For use with containers only. Specifies the user name for connecting to the Containers host.

Container.Auth.Password

For use with containers only. Specifies either the password for the user name or the public or private key password to be used. Encrypted property value is supported.

Container.Auth.PublicKey

For use with containers only. Specifies the public key for connecting to the Containers host.

Container.Auth.PrivateKey

For use with containers only. Specifies private key for connecting to the Containers host. Encrypted property value is supported.

Container.Connection.Protocol

For use with containers only. Specifies the communication protocol. The default value is API and is required. Do not modify this property.

Container.Connection.Scheme

For use with containers only. Specifies the communication scheme. The default is https.

Container.Connection.Port

For use with containers only. Specifies the Containers connection port. The default is 2376.

Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.MachineActivated

For use with containers only. Specifies the event broker property to expose all Containers properties and is used for registering a provisioned host. The default value is Container and is required. Do not modify this property.

Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.Disposing

For use with containers only. Specifies the event broker property to expose all Containersproperties above and is used for unregistering a provisioned host. The default value is Container and is required. Do not modify this property.