The first cloud environment configured in Avi Load Balancer is named Default-Cloud. This section describes how to correctly remove and reset the configured default cloud, Default-Cloud, from Avi Load Balancer, when the default cloud is OpenStack.

Reset Default Cloud

When creating a new cloud connector in Avi Load Balancer, other objects are created to support the configuration, both on the Avi Load Balancer Controller and in the target cloud environment (OpenStack, VMware vCenter, AWS, and so on).

For a non-default cloud, you can delete entire cloud, once it is no longer in use. This delete action triggers a cleanup of related objects in the cloud environment. For instance, deleting a custom OpenStack cloud connector deletes all Service Engines, Neutron security groups, Nova anti-affinity groups, Neutron ports, and glance images in OpenStack that were created as part of Avi Load Balancer installation and operation.

Since the Avi Load Balancer default cloud cannot be deleted, this creates challenges for cleaning up OpenStack objects when removing Avi Load Balancer from OpenStack. Though the configuration can be converted to no access mode, this leaves all objects in the cloud intact for manual control.

Steps for Resetting the Default Cloud

To remove the OpenStack cloud connector for the default cloud, use the following steps.

  • Delete all virtual services and pools from the cloud. The cloud cannot be deleted if it still contains any of these resources.

  • Connect to the Avi Load Balancer Controller through SSH or the console.

  • Connect to the CLI shell.

  • Run exec cloud Default-Cloud gc force cleanup command.

  • Exit the shell.