Creating network containers
Failed to execute the [bmc-contextid] macro.
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
- BMC Network Automation 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
The container will be provisioned on the network by BMC Network Automation using the specified network container blueprint.
Where to go from here
You can now:
- Onboard compute resources, as described Onboarding-compute-resources.
- Manage firewalls, as described in Managing-virtual-firewall-rules.
- Manage load balancers, as described in Managing virtual load balancers.
To continue with the next step of the wizard when creating or editing a network container, see Managing-dynamic-components-for-network-containers.
To view, create, or update network paths, see Managing-network-paths.
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.