"D"- <<SMO>> VirtualInventory
The Virtual Inventory provides access to other existing deployments. It is expected to be a distributed catalog and domain areas with their own Life Cycle and versions would have different domain roots.
This might be implemented by two separate objects as O-Clouds may be inventoried and managed independent of deployments which span them. Therefore O-Clouds and Deployments have two separate domain roots for the inventory created by a "deployment".
For the purposes of this implementation we will assume the following:
The Controller for inventory will be RESTful. The service endpoints will be used:
O-Clouds - {apiRoot}/OCloud/v1.
Deployments - {apiroot}/deployment/v1
The O-Cloud Inventory Model is represented in the class diagram below
The deployment Inventory Model is represented in the class diagram below