Reprovisioning network containers
This topic describes how to reprovision a network container; it contains the following sections:
The reprovisioning operation allows you to update a network container structure by using a new revision of the network container blueprint. The capability to reprovision a network container enables you to scale the container by adding new components, such as NICs, load balancer interfaces, and firewall interfaces.
- The reprovision operation is limited to adding and updating existing components.
- You cannot add a firewall or load balancer node to an existing container. You can add a new firewall interface or a new load balancer interface to an existing network container, if that container has an existing firewall or load balancer node.
- Deletion of components in the network container blueprint is not allowed during reprovisioning. If a component is deleted in the network container blueprint used to reprovision a container, BMC Network Automation detects those deletions, issues an appropriate error message, and stops the reprovision attempt.
- Starting with BMC Cloud Lifecycle Management 3.1.01 patch 3, dedicated pod-level networks are supported in container reprovisioning. For an example, see Example of container reprovisioning - adding a new NIC.
For example, you might want to do any of the following modifications to a network container after it has been created:
- Expand the private data network
- Expand the NAT address pool
- Add a network
- Add a network interface
- Add a zone
- Enable or disable a distributed firewall
Before you begin
Container reprovisioning is a potentially complex operation because it involves modifying a production container in which there could be existing virtual machines (VMs). Therefore, BMC highly recommends that you test your reprovisioning process thoroughly in a local sandbox system before applying the process to a production system.
Also, BMC recommends that you build as much scalability into the original network container blueprint as possible. Toggling the dynamic components in the network container is preferable to adding entirely new components to the network container by using the reprovisioning process.
For detailed information about reprovisioning network containers, see Reprovisioning network containers in BMC Network Automation.
To reprovision a network container
In BMC Network Automation, make any required changes to the container blueprint. For information about reprovisioning network containers in BMC Network Automation, see Reprovisioning network containers in BMC Network Automation and Configuring a reprovisioning operation for network containers.
With the exception of a Network Address Translation (NAT) pool expansion, any networking component added to a blueprint targeted for container reprovisioning must be in a disabled state, otherwise the reprovisioning operation might fail.
- Import the new blueprint revision into BMC Network Automation by using the import script. See Creating network container blueprints.
- From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
- Under Quick Links on the left, click Pods under the General section.
- Click the Import Network Container Blueprints icon Importing network container blueprints. to import the blueprint. For details, see
- Under Quick Links on the left, click Network Containers under the General section.
- Select the network container you want to reprovision.
Click the Reprovision Network Container iconto launch the Reprovision Network Container dialog.
If there are no changes available for the network container, the following message is displayed:
There are no upgraded blueprints available to reprovision the network container. (ARERR 210442).
The Reprovision Network Container dialog is displayed.
- Select the blueprint version to which you want to reprovision the network container.
While a network container is being reprovisioned, you cannot modify or delete it. Also, no VMs on this network container can be provisioned or decommissioned during reprovisioning.
Where to go next
For an example of the end to end process for reprovisioning a network container with a new NIC, see Container reprovisioning example - adding a new NIC.
For an example of how you would expand the address pool for a network container, see Container reprovisioning example - expanding the private data network.