Creating network containers

A network container is a data object that provides network isolation for tenants in the cloud. You must create and onboard a pod before you create a network container. You must have at least one network container in a pod. If you have multiple tenants, you might want to create a network container for each tenant. See Network-resources-overview for more information.

The configuration of a network container is specified in a network container blueprint. Network container blueprints are created in BMC Network Automation, as described in Creating-network-container-blueprints.

You must create at least one network container in BMC Cloud Lifecycle Management.

• • Before you begin
  • To create a new network container
  • Where to go from here

Before you begin

• BMC Network Automation (BBNA) must be registered as a provider.
• One or more pods, created in BMC Network Automation, must exist on the network.
• One or more network container blueprints must exist within the registered BMC Network Automation provider.
• One or more network blueprints must have been imported, as described in Importing-network-container-blueprints.
• The cloud administrator should be sufficiently familiar with the network container blueprints to know which ones support dynamic network containers and Network Address Translation (NAT).

To create a new network container

To create a new network container, you launch a wizard that contains three dialog boxes. In the first dialog box, you specify the unique name of the container, its pod, network container blueprint, NAT range (if applicable), and any tags. In the second dialog, you specify networks, firewalls, and associated load balancers. In the third dialog, you enter any additional parameters.

1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
2. Under Quick Links on the left, click Network Containers under the Network section.
3. Click the Create Network Container icon .
    The Create Network Container wizard is displayed.
   
   
   
4. Complete the following fields:
   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
5. Click Next to open the Dynamic Components dialog box. It displays the available networks and corresponding load balancers. See Managing-dynamic-components-for-network-containers.

The container will be provisioned on the network by BMC Network Automation using the specified network container blueprint.

After the activity is marked as complete, you can click the Refresh icon in the upper-right corner of the window to refresh the Resources table so that the newly created network containers appear in the list of network containers.

Where to go from here

To continue with the next step of the wizard when creating or editing a network container, see Managing-dynamic-components-for-network-containers.

You can now:

• Onboard compute resources, as described Onboarding-compute-resources.
• Manage firewalls, as described in Managing firewall rules. 
• Manage load balancers, as described in Managing virtual load balancers.

To view, create, or update network paths, see Managing-network-paths.