Managing plugins and deployments

Plugins register themselves to Connect.

There are two types of plugins:

  • deployment-agnostic plugins: these support multiple cloud deployments and are not bound to a specific deployment. Deployments are created by the operator using the Admin API. The Nokia provided VMware plugin is a deployment-agnostic plugin.
  • deployment-specific plugins: can only support one Deployment, typically the Plugin runs within the cloud environment. Deployments are self reported to the Connect service. The Nokia provided Kubernetes and OpenStack plugins are deployment-specific plugins.

Deployments can be in AdminUp true or false state (AdminUp or AdminDown). The admin state of a deployment indicates whether changes can be made on the resources (tenants, subnets, …) within that deployment.

Deployment-specific plugins will create their deployment in the Admin Down state by default. The operator must then manually enable this deployment using the Admin API. This way the operator has full control over which plugins and deployments can actually create resources.

Figure 1. Deployment-specific plugin
Figure 2. Deployment-agnostic plugin