Abstract: This disclosure relates to a method, system, and medium to exchange service management contents with a cloud entity via a self-contained cloud content package. The device retrieves a plurality of service management contents for a first cloud controller that offers a cloud service. Also, the device generates a self-contained cloud content package including a plurality of service management contents and a plurality of associated dependencies and configurations. The self-contained cloud content package includes elements for provisioning and managing the cloud service offered by the first cloud controller. Moreover, the device exchanges the plurality of service management contents with a second cloud controller in a cloud entity to support the second cloud controller to deploy and manage the cloud service.

Abstract: A technique includes providing a first interface to manage a plurality of cloud services that are provided by a plurality of cloud resources that form a hybrid cloud. Each of the cloud resources is associated with an application programming interface. The technique includes using the first interface to orchestrate the cloud services, where the orchestration includes using the first interface to orchestrate the application programming interfaces to allow at least one cloud resource management function provided by the first interface to be performed across at least two of the cloud resources.

Abstract: A system includes an infrastructure as a service (IaaS) layer to provide a set of infrastructure services to manage computing resources in a cloud computing environment. The system includes a service framework layer, separate from the IaaS layer, the service framework layer comprising an asynchronous interface to communicate with the IaaS layer and to create a framework service to extend the IaaS layer in response to a command from an upper tier service, the framework service to employ the asynchronous interface to utilize an infrastructure service from the set of infrastructure services.

Abstract: A microservice may be developed comprising application programming interfaces (APIs), a user interface, logic, and data received from at least one backend system, wherein the APIs and the user interface are decoupled from the logic and the at least one backend system, and the user interface, the logic and the data are decomposable into modules that may be shared with a different microservice. The microservice may expose a set of functions sufficient to support a target use case and Recycle management of the microservice, comprising at least one of exposing lifecycle management APIs and providing lifecycle self-management functionality.

Abstract: In some examples, a service controller provisions an instance of a cloud service in response to receiving a request, where the service controller is provided with content including a call to be issued by the service controller to a compliance/monitoring service that performs a task selected from among monitoring the provisioned instance and determining compliance of the provisioned instance. The service controller issues the call to the compliance/monitoring service, the call including information regarding the provisioned instance, wherein the information is useable by the compliance/monitoring service in performing the task.

Abstract: A method of managing the lifecycle of cloud service modeled as a topology includes, with a processor, generating a topology, the topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology, associating a number of policies with a number of nodes within the topology, the policies guiding the lifecycle management of the nodes, and with a lifecycle management engine, executing the topology.

Abstract: Managing the lifecycle of a cloud service modeled as a topology decorated by a number of policies includes with a processor, generating a topology or the realized topology, the topology or the realized topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology or the realized topology, and with a lifecycle management engine, updating the topology or the realized topology by associating a number of policies with the number of nodes within the topology or the realized topology.

Abstract: A topology remediation method includes with a remediation engine, deriving a number of remediation actions based on a number of incidents within an instantiated topology, and with a lifecycle management engine, modifying the instantiated topology based on a number of lifecycle management actions (LCMAs) determined to remediate the incidents.

Abstract: A realized topology system management (RTSM) database, comprising a database, a number of stored realized topologies, and in which the realized topologies within the DBMS are searchable. A method of generating and tracking a realized topology, comprising deriving a realized topology from an instantiated topology, storing the realized topology in a realized topology system management (RTSM) database, and storing a data file representing an association of the realized topology with data describing attributes of a number of nodes on the realized topology and relationships between the nodes.

Abstract: A method of executing a topology includes deriving executable logic from the topology. The method of executing the topology further includes, with an LCM engine, executing the topology based on the executable logic.

Abstract: A method of facilitating autonomous computing within a cloud service includes generating a cloud service based on a lifecycle management topology, in which the cloud service is an autonomous management service, a self-management service, or combinations thereof. The method also includes establishing a number of management processes to be performed within the cloud service, in which the number of management processes comprise autonomous management processes, self-management processes, or combinations thereof. The cloud service includes an instantiation of the topology and a number of applications executable on the instantiation of the topology.

Abstract: A method for aggregating, presenting, and fulfilling a number of catalogs is described. The method includes designating a server from a number of servers as a central server, receiving, at the central server, a number of catalogs from the number of servers, obtaining catalog information for the number of catalogs from the number of servers, and grouping the catalog information for the number of catalogs into an aggregated catalog.

Abstract: A method of monitoring a cloud service modeled as a topology with a processor includes establishing a number of monitoring policies to monitor an instantiated topology, detecting an event at a node based on the number of monitoring policies, and processing the detected event based on the number of monitoring policies.

Abstract: A method of stitching an application model to an infrastructure template, comprising identifying patterns in the application model, identifying patterns in the infrastructure topology, and matching the patterns in the application model and infrastructure topology using policies associated with the application model. A system for stitching an application model to an infrastructure topology, comprising a stitching engine, and a number of infrastructure topology sources, in which the stitching engine, identifies patterns in the application model, identifies patterns in the infrastructure topology, and matches the patterns in the application model and infrastructure topology using policies associated with the application model.

Abstract: A method of instantiating a topology-based service using a blueprint, includes, with a topology designer, modeling the blueprint as a topology, with a resource offering manager, associating a number of policies and a number of lifecycle management actions (LCMAs) with a number of nodes within the topology, and with a lifecycle management (LCM) engine, instantiating the topology based on the policies and LCMAs.

Abstract: A method of managing the lifecycle of cloud service modeled as a topology includes, with a processor, generating a topology, the topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology, and with a lifecycle management engine, executing the topology.

Abstract: A method of managing a number of secondary clouds by a master cloud service manager includes coupling a first cloud including a master cloud service manager to a secondary cloud including a child cloud service manager, and controlling, by the master cloud service manager, the child cloud service manager of the secondary cloud and a number of instantiated services offered on the secondary cloud.

Abstract: A method of updating and editing realized topologies, comprising presenting a realized topology to a user, receiving input indicating modification of portions of the realized topology, and with a processor, executing logic associated with the modified portions based on a number of lifecycle management actions (LCMAs) of the realized topology. A system to update and edit a realized topology, comprising a processor and a graphical user interface (GUI) communicatively coupled to the processor, in which the GUI presents to a user a graphical representation of the realized topology, and in which the system receives input indicating modification of portions of the realized topology, and with a processor, executes logic associated with the modified portions based on a number of lifecycle management actions (LCMAs) of the realized topology.

Abstract: Providing services can include receiving a request for a first service provided by a resource provider and provide a reference to an instantiated first resource that the resource provider instantiated. Providing services can include receiving a request for a second service provided by the resource provider. Providing services can include partitioning the instantiated first resource to create an instantiated second resource if the instantiated first resource is capable of providing the second service. Providing services can include registering an availability of the resource provider and the instantiated first resource for further partitioning in a chain of building blocks. Providing services can include updating one of the chain of building blocks and propagate the update to the chain of building blocks.

Abstract: Providing resources to a customer can include providing a node-relationship model based on a realized service offering. The node relationship model can include an instantiated first resource provided by a resource provider; an instantiated second resource provided by the instantiated first resource; and a plurality of defined relationships among the resource provider, the instantiated first resource, and the instantiated second resource. Providing resources to a customer can include creating a deployment plan for a new service offering based on the node-relationship model.