Cloud service and provider classes
The CloudService and Provider classes define providers and installation of the OSGi nodes. The following diagram illustrates these classes and how they relate to each other.
Cloud service and provider classes
CloudServiceDefinition is the superclass for ProviderDefinition. A CloudServiceDefinition holds metadata about a CloudService, including related AccessAttribute objects and its InstallationProfile.
ProviderDefinition has relationships with itself for parent-child and peer relationships. Although they are defined, peer relationships are not used in BMC Cloud Lifecycle Management.
Each ProviderDefinition supports one or more operations. These operations are modeled in the ProvidedOperation class. The ProviderDefinition to ProvidedOperation mapping is used in the provider registry.
Each ProvidedOperation can have multiple callouts associated with it. A Callout is specified to execute either before or after the operation. Each Callout can have Parameter objects associated with it (the same parameter list as the provided operation) and has a designated CalloutType.
A CloudServiceDefinition is transformed into a CloudService. CloudService defines AccessAttribute values using AccessAttributeValue objects. CloudService runs on a Node, which may have one or more InstallationProfile objects associated with it.
Provider is a subclass of CloudService and is an instantiation of a ProviderDefinition.
CoreCloudService is a subclass of CloudService.
Related topics
AccessAttribute-class
AccessAttributeValue-class
Callout-class
CalloutType-class
CloudService-class
CloudServiceDefinition-class
CoreCloudService-class
InstallationProfile-class
Node-class
Parameter-class
Provider-class
ProvidedOperation-class
ProviderDefinition-class