If a suitable network configuration is not available, you can create a new one in vRealize Automation.

Before you begin

  • Verify that you have container administrator, container architect, or IaaS administrator role privileges.

  • Verify that at least one host is configured and available for container network configuration.

Procedure

  1. Log in to vRealize Automation.
  2. Click the Containers tab.
  3. Select Resources > Networks in the left pane.

    The main panel displays the existing network configurations that can be provisioned as part of container deployment. The network configurations include both those collected from added Docker hosts and those created in vRealize Automation. The icons representing the network configurations display the network and IPAM drivers; subnet, gateway, and IP range information; the number of containers using the network configuration; and the number of hosts.

  4. In the Name field, enter any string value.

    When you finish creating the new configuration, the name value will be appended with a unique identifier.

  5. (Optional) : To add more detailed configuration settings, click the Advanced check box.

    Additional network configuration settings appear in the Add Network panel.

  6. Complete the network configuration settings.

    Option

    Description

    IPAM configuration

    Subnet

    Provide subnet and gateway values that are unique to this network configuration. They must not overlap with any other networks on the same container host.

    Custom properties

    Optionally, specify custom properties for the new network configuration.

    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.

    This property name and value are case-sensitive. The property value is not validated when you add it. If the specified driver does not exist on the container host at provisioning time, an error message is returned and provisioning fails.

    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.

    This property name and value are case-sensitive. The property value is not validated when you add it. If the specified driver does not exist on the container host at provisioning time, an error message is returned and provisioning fails.

    Hosts

    Specify the network hosts, as applicable.

    Note:

    If you create the network without advanced settings, vRealize Automation supplies the settings automatically.

  7. Click Create Network.

    The Add Network panel disappears and the added network appears as a horizontal icon below the container icons in the Edit Template page. A network connector icon also displays on the bottom border of the container icons.

  8. (Optional) : To connect a container to the newly added network, drag the network connector icon from the container to any point on the horizontal icon representing the network.