Abstract: Embodiments of the present invention provide systems and methods for constructing a plan for creating a cloud service. In one embodiment, a configurator receives a request for one or more services making up a cloud service, and a preliminary plan for the requested services is generated. A service provider determines that it is able to fulfill a requested service, and inserts a sub plan for fulfilling the requested service into the preliminary plan. A final plan is generated, which includes a sub plan from each service provider inserted into the preliminary plan.

Abstract: An order processing system can include an order processing container, a factory registry, a relationship registry, and synchronization function component. The order processing system can handle orders, which are build plans including a set of tasks. The tasks can specify programmatic actions which may include creation, deletion, and modification of resources and resource topologies. The order processing container can be central engine that programmatically drives order processing actions. The factory registry can support a creation and deletion of resource instances in a resource topology defined by at least one order. The relationship registry can maintain relationships among resources. The synchronization function component can permit transparent usage of shared resources in accordance with shared usage resource topology parameters specified within processed orders.

Abstract: Embodiments of the present invention provide systems and methods for constructing a plan for creating a cloud service. In one embodiment, a configurator receives a request for one or more services making up a cloud service, and a preliminary plan for the requested services is generated. A service provider determines that it is able to fulfill a requested service, and inserts a sub plan for fulfilling the requested service into the preliminary plan. A final plan is generated, which includes a sub plan from each service provider inserted into the preliminary plan.

Abstract: A system, and computer program product for managing cloud services are provided in the illustrative embodiments. A first set of management functions is instantiated external to a microkernel of a management system for managing a set of cloud services. The management system further includes a second set of management functions executing within the kernel of the management system. A subset of the first set of management functions is associated with a cloud service in the set of cloud services. A management task for the cloud service is handled using the subset of the first set of management functions. A usage information corresponding to the use of the subset of the first set of management functions for handling the management task for the cloud service is reported.

Abstract: A first set of management functions is instantiated external to a microkernel of a management system for managing a set of cloud services. The management system further includes a second set of management functions executing within the kernel of the management system. A subset of the first set of management functions is associated with a cloud service in the set of cloud services. A management task for the cloud service is handled using the subset of the first set of management functions. A usage information corresponding to the use of the subset of the first set of management functions for handling the management task for the cloud service is reported.

Abstract: A mechanism is provided for handling incidents occurring in a managed environment. An incident is detected in a resource in the managed environment. A set of incident handling actions are identified based on incident handling rules for an incident type of the incident. From the set of incident handling actions, one incident handling action is identified to be executed based on a set of impact indicators associated with the set of incident handling rules. The identified incident handling action is then executed to address the failure of the resource.

Abstract: A mechanism is provided for handling incidents occurring in a managed environment. An incident is detected in a resource in the managed environment. A set of incident handling actions are identified based on incident handling rules for an incident type of the incident. From the set of incident handling actions, one incident handling action is identified to be executed based on a set of impact indicators associated with the set of incident handling rules. The identified incident handling action is then executed to address the failure of the resource.

Abstract: A method for managing cloud services are provided in the illustrative embodiments. A first set of management functions is instantiated external to a microkernel of a management system for managing a set of cloud services. The management system further includes a second set of management functions executing within the kernel of the management system. A subset of the first set of management functions is associated with a cloud service in the set of cloud services. A management task for the cloud service is handled using the subset of the first set of management functions. A usage information corresponding to the use of the subset of the first set of management functions for handling the management task for the cloud service is reported.

Abstract: The invention is based on Orders specifically developed for and processed by an Order Processing Environment for creation or modification of resource topologies. The Order Processing Environment is partly replaced by a combination of an Order Transformation Environment and standard Workflow Engines in order to execute the Order by standard Workflow Engines. The Order Transformation Environment needs to get two inputs. The first input is the resource topology which is retrieved by using the Relationship Registry of the Order Processing Environment. The second input is the Order. Orders are resource topology independent and include resource specific tasks without arranging those in a sequence. Tasks provide actions for creating and/or modifying resource topologies. The transformation is based on above two inputs resulting in a static standard based workflow. The static, standards-based workflow (e.g. BPEL-based) can then be executed by standards-based process/workflow engines.

Abstract: A mechanism is provided for handling incidents occurring in a managed environment. An incident is detected in a resource in the managed environment. A set of incident handling actions are identified based on incident handling rules for an incident type of the incident. From the set of incident handling actions, one incident handling action is identified to be executed based on a set of impact indicators associated with the set of incident handling rules. The identified incident handling action is then executed to address the failure of the resource.

Abstract: A mechanism is provided for handling incidents occurring in a managed environment. An incident is detected in a resource in the managed environment. A set of incident handling actions are identified based on incident handling rules for an incident type of the incident. From the set of incident handling actions, one incident handling action is identified to be executed based on a set of impact indicators associated with the set of incident handling rules. The identified incident handling action is then executed to address the failure of the resource.

Abstract: A scalable and fault tolerant finite state machine engine, for example, for use in an automated incident management system, logs or records data in persistent storage at different points or levels during various internal processing of an event associated with an information technology element, and action taken associated with the event, by executing a finite state machine instance that encodes policies for handling incidents on such types of information technology elements. In the event that the finite state machine engine is shutdown during processing, the finite state machine engine is able to pick up from where it left off when it was shutdown, for each abnormally terminated finite state machine instance, by using the data logged in the persistent storage and determining a point of processing from where it should continue its execution.

Abstract: A scalable and fault tolerant finite state machine engine, for example, for use in an automated incident management system, logs or records data in persistent storage at different points or levels during various internal processing of an event associated with an information technology element, and action taken associated with the event, by executing a finite state machine instance that encodes policies for handling incidents on such types of information technology elements. In the event that the finite state machine engine is shutdown during processing, the finite state machine engine is able to pick up from where it left off when it was shutdown, for each abnormally terminated finite state machine instance, by using the data logged in the persistent storage and determining a point of processing from where it should continue its execution.

Abstract: A system, and computer program product for managing cloud services are provided in the illustrative embodiments. A first set of management functions is instantiated external to a microkernel of a management system for managing a set of cloud services. The management system further includes a second set of management functions executing within the kernel of the management system. A subset of the first set of management functions is associated with a cloud service in the set of cloud services. A management task for the cloud service is handled using the subset of the first set of management functions. A usage information corresponding to the use of the subset of the first set of management functions for handling the management task for the cloud service is reported.

Abstract: A scalable and fault tolerant finite state machine engine, for example, for use in an automated incident management system, logs or records data in persistent storage at different points or levels during various internal processing of an event associated with an information technology element, and action taken associated with the event, by executing a finite state machine instance that encodes policies for handling incidents on such types of information technology elements. In the event that the finite state machine engine is shutdown during processing, the finite state machine engine is able to pick up from where it left off when it was shutdown, for each abnormally terminated finite state machine instance, by using the data logged in the persistent storage and determining a point of processing from where it should continue its execution.

Abstract: A scalable and fault tolerant finite state machine engine, for example, for use in an automated incident management system, logs or records data in persistent storage at different points or levels during various internal processing of an event associated with an information technology element, and action taken associated with the event, by executing a finite state machine instance that encodes policies for handling incidents on such types of information technology elements. In the event that the finite state machine engine is shutdown during processing, the finite state machine engine is able to pick up from where it left off when it was shutdown, for each abnormally terminated finite state machine instance, by using the data logged in the persistent storage and determining a point of processing from where it should continue its execution.

Abstract: A method and associated apparatus is provided for generating a machine-processable semantic description of a first manageable resource of an application domain. In accordance with an embodiment of the invention, the first manageable resource is characterized by a set of aspects. Accordingly, an ontology is provided for the application domain that provides a terminology and rules for describing the set of aspects of the first manageable resources of the application domain in a semantic way. The semantic description of the first manageable resource is then generated compliant to the terminology and the rules of the ontology to describe semantically the set of aspects.

Abstract: The present invention relates to method and system for accessing a resource implemented in a computer network, wherein a plurality of different runtime environments exist used by either one of the resources or by a systems management application accessing one of the resources, wherein the different runtime environments require the usage of a web service resource framework comprising a plurality of respective different, runtime-specific web service standards.

Abstract: A computer implemented method and a computer program product provide a provisioning system for automated provisioning of a computing infrastructure by providing relationship factories with resources of the computing infrastructure. The relationship factories include information necessary for establishing relationships within the computing infrastructure. The provisioning system ranks relationship factories according to suitability to provide for appropriate provisioning of new resources added to the computing infrastructure.

Abstract: A method and system for automatically cloning IT resource structure in stateful web services environments by employing a new approach for configuration management. The present new approach models the configurational state of each resource as a stateful web service. Configuration data are provided by this service's resource properties. Relationships between configurations of different resources are modeled as “stateful web services relationships” between web service instances. These relationships can be navigated, which allows exploring the configuration of a whole system in a standards-based way. Additionally a new web service interface is provided by the stateful web service encapsulating the resource. This interface provides two new operations: “getConfiguration” allows an exploiter to take a snapshot of a resource's and related resources' configurational state and “setConfiguration” allows for setting the configurational state of a resource to a previously saved state.