Creating network containers


Failed to execute the [bmc-contextid] macro. Cause: [Missing macro content: this macro requires content (a body)]. Click on this message for details.

A network container is a VLAN that provides network isolation for tenants in the cloud. You must have at least one network container, and 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 BladeLogic Network Automation.

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

Before you begin

  • BMC BladeLogic Network Automation (BBNA) must be registered as a provider.
  • One or more pods, created by the registered BMC BladeLogic Network Automation provider, must exist on the network.
  • One or more network blueprints must exist within the registered BMC BladeLogic Network Automation provider.
  • One or more network blueprints must have been imported, as described in Importing-network-container-blueprints.

To create a network container

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

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

You can now:

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

After the activity is marked as complete, you can click the Refresh icon refreshbtn.gifin 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.

Related topics

Network-resources-overview

Editing-and-removing-resources

Adding-compute-resources-to-compute-resource-pools

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*