Synchronizing network pods
You can update a pod after it has been onboarded. This capability enables you to scale a pod when necessary.
For example, a pod might be running out of virtual ports for virtual machine (VM) provisioning, because the pod was originally configured with one vswitch and a maximum of 120 virtual ports. You can update the pod with an additional access switch, which will provide more virtual ports for any new network containers that are created for the pod.
Other scenarios for updating a pod include adding new load balancer nodes or firewalls into the pod.
This topic contains the following sections:
To update an onboarded pod
- In BMC Network Automation, update the pod. See Editing-a-pod.
- 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.
Select the pod you want to synchronize.
- Click the Synchronize Pod icon
to synchronize the network pod with any changes to the pod since it was onboarded.
- After the pod is synchronized, the associated virtual cluster must also has to be synchronized, as described in the section below.
To update a virtual cluster
To update the virtual hosts, virtual resource pools, and virtual disk repositories associated with a virtual cluster, complete the following steps:
- Under Quick Links on the left, click Resources under the Compute section.
- Select the virtual cluster you want to refresh from the table.
- Click the Synchronize Virtual Cluster icon
.
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 onboarded resources appear in the table.