Patent Grant
11722376
An increasingly larger number of business entities and individuals are turning to cloud computing and the services provided through a cloud computing system in order to, for example, sell goods or services, maintain business records, and provide individuals with access to computing resources, among other cloud-related objectives. Cloud computing provides consumers of the cloud with scalable and pooled computing, storage, and networking capacity as a service or combinations of such services built on the above. A cloud may be designed, provisioned, deployed, and maintained by or for the entity for which the cloud computing system is created. Designing, provisioning, deploying, and maintaining a cloud computing system may be a difficult task.
The accompanying drawings illustrate various examples of the principles described herein and are a part of the specification. The illustrated examples are given merely for illustration, and do not limit the scope of the claims.
Throughout the drawings, identical reference numbers designate similar, but not necessarily identical, elements.
Cloud computing provides services for a user's data, software, and computation. Applications deployed on resources within the cloud service may be manually deployed. This manual deployment consumes considerable administrative time. The manual steps of deploying an application may include the provisioning and instantiation of the infrastructure. This may include linking the installation of an application or a platform such as middleware and DB, applications or deployment of an image with or without the full knowledge of the deployed infrastructure. Manual deployment may further include numerous sequences of steps launched by a user who attempts to deploy the application. Thus, the manual linking of an application to a deployed infrastructure consumes large amounts of computing and personnel resources, and may lead to mistakes and irreconcilable issues between the application and the underlying infrastructure. Linking of an application to a deployed infrastructure may be automated with a number of tools, scripts, and executables, with orchestrators automating the sequence of execution of these processes. A number of devices used in the designing, provisioning, deploying, and maintaining of applications deployed on resources within the cloud service may include data centers, private clouds, public clouds, managed clouds, hybrid clouds, and combinations thereof.
More specifically, cloud services provided to users over a network may be designed, provisioned, deployed, and managed using a cloud service manager. The cloud service provider or other entity or individual designs, provisions, deploys, and manages such a cloud service that appropriately consists of a number of services, applications, platforms, or infrastructure capabilities deployed, executed, and managed in a cloud environment. These designs may then be offered to user who may order, request, and subscribe to them from a catalog via a market place or via an API call, and then manage the lifecycles of a cloud service deployed based on the designs through the same mechanism. The service designs in a cloud service manager such as CLOUD SERVICE AUTOMATION (CSA 3.2) designed and distributed by Hewlett Packard Corporation, described in more detail below, are expressed with “blueprints.”
Blueprints describe services in terms of the collections of workflows that are to be executed to provision or manage all the components that make up the service in order to perform a particular lifecycle management action. Some of the functions of the workflows defined by blueprints are actual life cycle management actions that are then performed as calls to a resource provider. The resource provider converts the calls into well formed and exchanged instructions specific to the particular resource or instance offered by a resource provider.
Further, the structures of blueprints (100), for the same reason, are difficult to use as models of applications or templates of infrastructures as HP CONTINUOUS DELIVERY AUTOMATION (CDA) does. HP CDA is system tool utilized within a topology designer that independently models infrastructure and application requirements while managing versions, configurations, and other application components. HP CDA 1.2 is also developed and distributed by Hewlett Packard Corporation. The structures of blueprints (100), for the same reason given above, are difficult to use as models of applications because blueprints do not describe the architecture of the application. Further, blueprints are difficult to use as templates of an infrastructure because they also do not describe the architecture of the infrastructure. As a result, systems aiming at modeling application models and infrastructure or platform templates, and mapping the application models and infrastructure or platform templates to each other are not easily reconciled with the blueprints because they are based on different methods of modeling these services.
The present systems and methods describe architecture-descriptive topologies that define the physical architecture of a system that constitutes a cloud service.
For example, the load balancer (201), web server service (202), application enterprise archive (203), and the database (204) are associated with one another. The web server service (202) is aggregated with a web virtual machine (205) and its security group (213) as well as a web virtual local area network (209). Similarly, the application enterprise archive (203) is aggregated with an application server service such as the JavaBeans Open Source Software Application Server (JBoss) service (206), a JBoss virtual machine (208) and its associated security group (214), and a secure application virtual local area network (210). Again, similarly, the database (204) is associated with a database virtual machine (207) and its security group (215), and a secure database virtual local area network (211). The web virtual local area network (209), secure application virtual local area network (210), and secure database virtual local area network (211) are then associated with a router (212).
Thus, a cloud service based on an instantiation of the architecture derived topology (200) may be expressed as a topology of nodes with a number of relationships defined between a number of nodes within the topology. A number of properties and actions are associated with a number of the nodes, a number of groups of nodes, a portion of the topology, the topology as a whole, or combinations thereof. Further, a number of policies are associated with the number of the nodes, a number of groups of nodes, a portion of the topology, the topology as a whole, or combinations thereof. Still further, a number of lifecycle management actions (LCMAs) are associated with the number of the nodes, a number of groups of nodes, a portion of the topology, the topology as a whole, or combinations thereof.
Thus, the present systems and methods describe cloud service broker or manager that supports both topologies and blueprints while using the same lifecycle management engine. The lifecycle management engine supports lifecycle management of cloud services, and mapping of application models with infrastructure templates. The present systems and methods also describe a policy-based framework for managing the provisioning, deployment, monitoring, and remediation processes within a cloud service. Further, the present systems and methods provide support for usage models supported by CSA, CDA, and blueprints as will be described in more detail below.
The present systems and methods further describe execution of topologies and blueprints using the same lifecycle management (LCM) engine. In the case of blueprints, the blueprints may be first converted into topologies or a topology may be derived from a blueprint. Further, the blueprint may be directly executed by the LCM engine described herein to produce an instantiated service without first converting the blueprint into a topology, or deriving a topology from the blueprint. The topologies executed by the LCM engine may be generated de novo, generated from a stitching method performed on an application model and an infrastructure template, or from a blueprint-derived topology. The blueprints may directly be executed by the LCM engine. A number of scripts or executable logic may be derived from the topologies. The executable logic is converted into an execution plan. Instantiation may take place by calling a number of resource providers to provision a number of devices, and instantiate the topology or blueprint based on the executable logic and execution plan.
As used in the present specification and in the appended claims, the term “broker” is meant to be understood broadly as any computing device or a collection of computing devices in a network of computing devices that manages the designing, provisioning, deployment of a topology within the cloud, and the maintenance and life cycle management of (an) instantiated service based on that topology.
As used in the present specification and in the appended claims, the term “cloud service” is meant to be understood broadly as any number of services provided over a number of computing devices that are connected through a real-time communication network. Cloud services may include services provided on a distributed system implementing distributed hardware and software resources. In one example, a cloud service may be any service offered on a private cloud, public cloud, managed cloud, hybrid cloud, or combinations thereof. In another example, a cloud service may be services provided on physically independent machines such as, for example, a data center.
Further, as used in the present specification and in the appended claims, the terms “node or “computing device” are meant to be understood broadly as any hardware device, virtual device, group of hardware devices, group of virtual devices, or combination thereof within a network. Nodes may include, for example, servers, switches, data processing devices, data storage devices, load balancers, routers, and virtual embodiments thereof, among many other types of hardware and virtual devices. Further, nodes may be representations of the above hardware and virtual devices before execution and instantiation of a topology of which the node is a part.
Still further, as used in the present specification and in the appended claims, the term “topology” is meant to be understood broadly as data representing a graph of nodes where branches between the nodes represent relationships between the nodes. The nodes may comprise any number of computing devices located within a network. Thus, the topology of the network may comprise the physical and logical layout of networked computing devices, and definitions of the relationships between the computing devices. A number of policies and lifecycle management actions (LCMA) may be associated with the topologies, portions of the topologies, nodes within the topologies, groups of nodes within the topologies, and combinations thereof.
Still further, as used in the present specification and in the appended claims, the term “blueprint” is meant to be understood broadly as an execution flow for allowing automation of cloud service deployment and life cycle management of cloud services. A blue print may include a functional description of a number of hardware and/or virtualized components included within a service such as, for example, operating systems, application stacks, databases. A blueprint may further include a functional description of the configuration and connectivity between the hardware and virtualized components. The blueprints may also include a number of deployment models to enable the functional description to be deployed. The blueprints may further include a set of user-configurable options to allow a user to configure a number of optional aspects of the deployed service. Blueprints are an example of non architecture derived executable topologies.
Still further, in addition to the blueprints described above, the present disclosure provides for the utilization of executable topologies. Thus, the present systems and methods provide for the execution and instantiation of both blueprint- and architecture-derived topologies. Both blueprint- and architecture-derived topologies are executable. Thus, as used in the present specification and in the appended claims, the term “topology” is meant to be understood broadly as any set of executable logic or interpretable logic that may be expressed as executable logic that defines the characteristics of the network to be instantiated. The topology may define a number of nodes. Further, the topology may define and a number of policies and lifecycle management actions associated with the nodes as a number of groups, individually, or a combination thereof. In one example, blueprints may be expressed as topologies. In this example, the blueprint-derived topologies may also define a number of nodes and a number of policies and lifecycle management actions associated with the nodes within the topologies, groups of nodes within the topologies, portions of the topologies, the topology as a whole, and combinations thereof.
Still further, as used in the present specification and in the appended claims, the term “policy” is meant to be understood broadly as any data or metadata used to assist in the management of the provisioning, deploying, monitoring, enforcement, and remediation within a cloud service. The policies may represent a number of rules or sets of rules that are applicable to the provisioning, deploying, monitoring, enforcement, and remediation tasks associated with a number of computing devices within a cloud service environment.
Still further, as used in the present specification and in the appended claims, the term “user” is meant to be understood broadly as any individual or entity for whom or by whom a cloud service is designed, provisioned, deployed, monitored, policy enforced, incident remediated, otherwise managed, or combinations thereof. In one example, the user may purchase use of the cloud service at a cost. For example, the user may pay a subscription to use the cloud resources and services, and, in this case, also be classified as a subscriber. In another example, a user may be a designer or administrator of the cloud service. In still another example, a user may be any individual who manages the cloud service.
Even still further, as used in the present specification and in the appended claims, the term “a number of” or similar language is meant to be understood broadly as any positive number comprising 1 to infinity; zero not being a number, but the absence of a number.
In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present systems and methods. It will be apparent, however, to one skilled in the art that the present apparatus, systems, and methods may be practiced without these specific details. Reference in the specification to “an example” or similar language means that a particular feature, structure, or characteristic described in connection with that example is included as described, but may not be included in other examples.
The present systems may be utilized in any data processing scenario including, for example, within a network including the design, provisioning, deployment, and management of a number of computing devices within the network. For example, the present systems may be utilized in a cloud computing scenario where a number of computing devices, real or virtual, are designed, provisioned, deployed, and managed within a service-oriented network. In another example, the present systems may be utilized in a stand alone data center or a data center within a cloud computing scenario. The service oriented network may comprise, for example, the following: a Software as a Service (SaaS) hosting a number of applications; a Platform as a Service (PaaS) hosting a computing platform comprising, for example, operating systems, hardware, and storage, among others; an Infrastructure as a Service (IaaS) hosting equipment such as, for example, servers, storage components, network, and components, among others; application program interface (API) as a service (APIaaS), other forms of cloud services, or combinations thereof. The present systems may be implemented on one or multiple hardware platforms, in which the modules in the system are executed on one or across multiple platforms. Such modules may run on various forms of cloud technologies and hybrid cloud technologies or offered as a SaaS (Software as a service) that may be implemented on or off the cloud.
Further, the present systems may be used in a public cloud network, a private cloud network, a hybrid cloud network, other forms of networks, or combinations thereof. In one example, the methods provided by the present systems are provided as a service over a network by, for example, a third party. In another example, the methods provided by the present systems are executed by a local administrator. In still another example, the present systems may be utilized within a single computing device. In this data processing scenario, a single computing device may utilize the devices and associated methods described herein to deploy cloud services and manage life cycles of the cloud services. In the above examples, the design of the cloud service, provisioning of a number of computing devices and associated software within the cloud service, deployment of the designed and provisioned cloud resources and services, management of the cloud resources and services, and combinations thereof may be provided as the service.
Aspects of the present disclosure may be embodied as a system, method, or computer program product, and may take the form of an entirely hardware embodiment, or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in a number of computer readable mediums comprising computer readable program code embodied thereon. Any combination of one or more computer readable mediums may be utilized.
A computer readable medium may be a computer readable storage medium in contrast to a computer readable signal medium. A computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Throughout the present disclosure, various computing devices are described. The computing devices may comprise real or virtual computing elements including data processing devices, data storage devices, and data communication devices. Although these various devices may be described in connection with real and physical devices, any number of the devices may be virtual devices. The virtual devices, although describing a software-based computer that is based on specifications of emulated computer architecture and functions of a real world computer, the virtual devices comprise or are functionally connected to a number of associated hardware devices. Accordingly, aspects of the present disclosure may be implemented by hardware elements, software elements (including firmware, resident software, micro-code, etc.), or a combination of hardware and software elements.
The subsystem depicted in
Further, the subsystem depicted in
In this manner, the subsystems of
As depicted in
The LCM topology (302) may define a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), and a number of relationships between the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7). Although in
In
Further, in one example, the addition of a policy (303) to the topology or portions thereof may cause the design of the topology to change. In this example, a policy (303) added to an element of the topology (302) may effect a number of other policies. For example, associating with a topology (302) a policy that indicates that a node be highly available may evolve the policies (303) and topology (302) as a whole to require, for example, a cluster of nodes. In this manner, policies may drive the design of the topology (302).
Each of the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), the entire topology (302), a group of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), portions of the topology (302), or combinations thereof are further associated with a number of lifecycle management actions (LCMAs) (304). In examples where LCMAs (304) are associated with the nodes, a single LCMA is associated with a given node. In examples where a number of LCMAs are associated with portions of the topology (302) or the topology (302) as a whole, the LCMAs are subjected to an orchestration of resource providers.
LCMAs are expressed as a number of application programming interfaces (APIs), wherein the LCMAs are called during execution of the topology (302), and a number of computing resources are provisioned for purposes of managing the lifecycle of a given cloud capability. In one example, the LCMAs may be accessed via uniform resource identifiers (URIs) of application programming interfaces (APIs) to perform calls in order to execute the APIs. In one example, the LCMAs are provided by reference within the file comprising the data or metadata described above in connection with the policies (303).
In one example, the LCMAs are associated with the aspects of the topology by default by virtue of what computing device the node or nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) represent. In another example, the LCMAs are associated with the aspects of the topology by explicitly providing a number of functions, FAction, that define how to select a resource provider to implement the action based on the policies associated with the aspects of the topology and the policies of the different relevant resource providers. These functions define how a resource provider is selected to implement the action based on the policies associated with the aspect of the topology and the policies of the different relevant resource providers.
The policies and LCMAs will be denoted herein by elements 303 and 304, respectively, to denote that the policies (303) and LCMAs (304) are associated with the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), the entire topology (302), a group of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), portions of the topology (302), or combinations thereof. In one example, the association of the policies and LCMAs with aspects of the topology is performed via the topology designer (301).
In one example, although not depicted, a subset of nodes making up a group may also be associated with a number of policies (303) and a number of LCMAs (304). In this example, a number of nodes, for example, nodes (302-2, 302-3, 302-4, 302-6, 302-7), may be associated as a group with a number of policies (303) and a number of LCMAs (304) associated therewith. Several groupings of the nodes may be present within the entire topology (302). In one example, the groups of nodes may overlap, in which a single node in a first group of nodes may also belong to a second group of nodes, and be subjected to both the first and second groups of nodes' policies (303) and LCMAs (304). Policies and their associations with individual nodes and groups of nodes will be described in more detail below.
The policies (303) associated with the nodes may be expressed and attached with the nodes in any manner (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7). In one example, the policies (303) are associated with the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) by defining properties of the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7). In another example, the policies (303) are associated with the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) by metalanguage expressions.
The policies (303) are a number of descriptions, metadata, workflows, scripts, rules, or sets of rules that are applicable to guiding the provisioning, monitoring, enforcement, governance, and remediation tasks associated with the lifecycle management of a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within a cloud service environment in which the topology (302) is to be or has been implemented. The policies (303) define the access control and usage control of the APIs of the topology-based management broker (200). Further, policies (303) define the access control and usage control of the APIs used to manage or use the instantiated services. For example, when a security threat is detected by a monitoring system (313), a remediation option may comprise making changes to a number of access control policies.
The policies (303) may be associated with and operable against a number of individual nodes, a number of groups of nodes, a number of nodes of a class of nodes, a subset of the nodes within the entire topology of the cloud service; the entire topology of the cloud service as a whole, or combinations thereof. If the policies (303) are initiated on the individual nodes, groups of nodes, or the entire topology of the cloud service as a whole, the policies will guide how life cycle management actions are taken with respect to, or performed on the individual nodes, groups of nodes, nodes of a class of nodes, a subset of the nodes within the entire topology of the cloud service, or the entire topology of the cloud service as a whole.
On example of a type of policy is a provisioning policy. Provisioning policies may, if implemented, define the characteristics of the computing devices that comprise the cloud when the topology is provisioned, deployed, and executed. This provisioning can include the infrastructure and platform of the topology (302). The provisioning policies may include definitions of characteristics such as, for example, the physical location of a node. Provisioning policies may also include definitions of characteristics such as, for example, a geographical or deployment type location such as a network zone with or without access to an internet or behind or not behind a firewall, among other geographical or deployment type provisioning policies. In this example, a policy may have a provisioning policy component that may be associated with a server device that requires the server device to be located in a particular geographic area of a country, a particular region such as, for example, the east coast of the United States versus the west Coast, a particular server facility, or any other geographic location.
As to a provisioning policy that defines a physical location of the computing device, other characteristics may include, for example, the level of security of the location or access to the internet at which the node is located. Other provisioning policies may also include, for example, the speed in, for example, bandwidth of the network to which the node is coupled, whether the node is to be connected to an internet or intranet such as, for example, a demilitarized zone (DMZ) or perimeter network, whether the node is firewalled, whether the node has access to an internet, whether the node is to be located on top of another node, and whether the node is to be located on top of another node using a particular infrastructure element or platform, among other provisioning policies.
Provisioning policies may also, if implemented, rely on the requirements and capabilities of the nodes within the proposed cloud service that is based on the topology (302). Requirements define the needs of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) such as, for example, server or network needs in relation to processing, memory, and operating system (OS) needs, among other forms of needs. For example, the requirements policies may indicate that a node requires particular software or a particular software version associated with it such as a particular operating system. As another example, a requirements policy may also indicate that a particular node may require additional hardware devices associated with it such as, for example, a server device, a server group, or a high availability configuration, among others.
Capabilities such as the nature of the processors, memory, capacity, OS, middleware type and version, among others, define what each node (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) offers. Thus, in one example, capabilities policies may indicate that a node is capable of processing data at a certain rate. In another example, a capabilities policy may indicate that a memory device may have a terabyte (TB) of data storage space.
In still another example, the requirements policies may indicate that a node requires a particular computing platform. When designing a topology (302), the topology or association of metadata supports capturing data defining a number of hardware devices within the computing platform including hardware architecture and a software framework (including application frameworks). When the metadata is presented or associated, it is used to guide provisioning policies in order to better select appropriate elements within the computing platform such as, for example, a suitable data center. The metadata, when presented or associated, may also be used to guide matching fragments of topologies to other fragments as will be discussed in more detail below in connection with stitching of application models to infrastructure templates.
With regard to capability policies, the nodes may define what kind of device they are, what versions of software they capable of, or are executing, and what they can do. An example, of a capability policy may include a definition associated with the node that defines it as an application server, that it provides a Java Platform, Enterprise Edition (J2EE) environment, that it runs a particular operating system, a version of an operating system, or a particular release of a version of the operating system, among many other capabilities. As described above, this may be used to determine, for example, what else may be deployed or what other devices may use the cloud services.
Another type of policy (303) that may be assigned includes monitoring policies. Monitoring policies are policies that, if implemented, define the operational monitoring of the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), the security monitoring of the nodes, the compliance monitoring of the nodes, analytics among the nodes and groups of nodes, usage monitoring of the nodes, performance monitoring, and intelligence monitoring such as, for example, collection of metrics, business intelligence (BI) and business activity monitoring (BAM) and analytics/big data integration, among other types monitoring-related policies.
The monitoring policies may also define what kind of monitoring is expected and how the monitoring is to be implemented. Examples of monitoring policies regarding node operations include performance, monitoring CPU levels and loads of the various nodes within the network, monitoring the speed at which data is processed through a node or a number of nodes or exchanged between nodes, and monitoring the operational state of applications running on a node or nodes at any level of the network, among many other operations parameters of the nodes, group of nodes, and the cloud service as a whole.
In another example, the monitoring policies also define how monitored events that occur in an instantiated topology are handled. In this example, the monitoring policies assist an event handler (316) in receiving and processing the events, and in making decisions regarding remediation of incidents resulting from the events, and in sending notification messages regarding the incidents. The handling of events within the topology-based management broker (200) will be described in more detail below. As will be described in more detail below, the monitoring policies include a portion that defines what to do with the monitored events that result from the monitoring such as, for example, how to handled the events, where the events are sent, what devices or individuals address the events, how incidents resulting from the processing of the events are handled, how the events and incidents are processed (e.g., processed as aggregated, filtered, or correlated events, among other forms of processing), and how the resulting incidents are handled.
Monitoring policies also include monitoring policies regarding security. Security policies define how to monitor for abnormal behaviors or behaviors known as being associated with known or suspected security issues. Examples of monitoring policies regarding security include monitoring whether a node or a group of nodes is experiencing an attack, whether there is strange behavior occurring within the cloud service or interactions with the cloud service, and whether there is a virus or other anomaly with a node or group of nodes, among other security-related monitoring policies.
Monitoring policies also include monitoring policies regarding compliance. Examples of monitoring policies regarding compliance include, determinations as to whether the nodes or group of nodes are running an appropriate version of an operating system, determining whether the most recent patch associated with the release of a software program running on the nodes has been installed, determining if an installed patch is a correct patch, checking that a code or artifacts that have been used to provision the node and cloud service have been appropriately checked and vetted for any weakness or problem, if governance and access control to the node and cloud service or the node and cloud service management is appropriate, and if settings of a provisioned system match provisioning, security, or other compliance requirements such as correct logging levels, correct setup for access controls, and correct setup for passwords, among other compliance-related monitoring policies.
Monitoring policies also include monitoring policies regarding usage. Examples of monitoring policies regarding usage include, determining how much a user has been using CPUs of a node or group of nodes, determining how much memory a user has utilized, determining how much money has been charged to the user, and determining whether the user has paid for the services provide through the designing, provisioning, deploying, and monitoring of the network topology, among other usage-related monitoring policies.
The policies (303) may further comprise governance policies that, if implemented, define access controls of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) or groups of nodes within the topology (302) or the cloud service. For example, governance policies may include policies that define who may access the nodes within the topology (302) or the cloud service, and under what conditions may those individuals obtain such access.
The policies (303) may further comprise analytics policies that, if implemented, define what is needed to ensure analytics and big data monitoring within or among the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) or groups of nodes within the topology (302), and ensure that this is occurring as expected. For example, the analytics policies may define a number of workflows by which the monitoring system (313) may operate to configure the cloud service, provide analytics, collect big data, and process the data.
Still further, the policies (303) may comprise remediation policies that define what actions are to take place within the topology (302) should a problem arise or an incident be raised during deployment and execution of the topology (302). Remediation policies may include policies that define a number of actions taken by the topology-based management broker (200) during remediation processes, and include: (1) providing notifications to a user, consumer, or administrator; (2) obtaining instructions from the user, consumer, or administrator; (3) taking manual actions input by the user, consumer, or administrator; (4) taking autonomous actions after receiving instructions from the user, consumer, or administrator; (5) taking autonomous actions without receiving instructions from the user, consumer, or administrator; (6) taking autonomous actions without notifying the user, consumer, or administrator or receiving instructions from the user, consumer, or administrator; (7) proposing a remediation action to a user or administrator for approval, and performing the proposed remediation action if approved by the user or administrator, or combinations thereof.
As an example, a failure of the cloud service as instantiated or realized by the topology (302) may occur, and the remediation policies may define how that failure may be handled based on the above potential scenarios. In addition, the remediation policies provide the actual rules and workflows of actions to perform to remediate the incidents under any number of conditions or indicate to whom or which device to delegate the decision making and orchestration and fulfillment of these remediation actions. Another remediation example may regard a potential need to maintain a level of service based on, for example, a service level agreement (SLA), or a quality of service (QoS) within the cloud service that is realized based on the topology (302). In this example, the addition of resources to support the increase in demand for resources may be handled based on the above potential scenarios. More details regarding monitoring of the deployed topology and event handling therein will be described in more detail below.
As described above, the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) may include a number of lifecycle management actions (LCMA) (304) associated with the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7). The LCMAs (304) are a number of actions associated with the policies (303) that are executed by a processor when triggered by the policies (303) within a cloud service environment in which the topology (302) is implemented. The LCMAs may be associated with and operable against a number of individual nodes, a number of groups of nodes, a number of nodes of a class of nodes, a subset of the nodes within the entire topology of the cloud service; the entire topology of the cloud service as a whole, or combinations thereof. If the LCMAs are executed with respect to the individual nodes, groups of nodes, or the entire topology of the cloud services as a whole, the LCMAs will take an action with respect to the individual nodes, groups of nodes, the nodes of a class of nodes, a subset of the nodes within the entire topology of the cloud service, or the entire topology of the cloud service as a whole as defined within the LCMAs. LCMAs (304) include actions such as, for example, provisioning of computing resources within the topology, updating the topology, copying all or portions of the topology, modifying computing resources within the topology, moving computing resources within the topology, destroying or deleting resources within the topology, among other lifecycle management actions.
The various policies described herein define what actions are to be performed throughout the lifecycle of the topology (302) before, during, and after instantiation of a service based on the topology (302). Further, the various policies described herein define how these actions are to be performed. Still further, the various policies described herein define which device, individual, or combination thereof to which the actions are to be delegated. Even still further, the various policies described herein define combinations of the above. For example, any of the monitoring policies used in event handling and processing, or remediation may define what devices or portions of the cloud service are to be monitored or remediated, how to execute such monitoring and remediation, to whom or what devices to delegate the roles of monitoring and remediation, or a combination thereof.
Different policies play different roles at different times within the lifecycle of a topology. Further, the different policies may be executed at different times of the lifecycle of the cloud service and throughout the flows of the topology-based management broker (200).
The policy provisioning engine (402) may be a stand alone device or incorporated into a device of
Resource provider policies (308-1) may be any policies that associated with a number of resource providers' offerings that guide the selection of a number of resources. In one example, the resource provider policies (308-1) may be dynamic functions that define the computing abilities of a computing resource. In this example, a computing resource that provides a defined level of computing resources such as, for example, processing power may be provisioned by the LCM engine (311) and resource offering manager (308) if the defined level of that computing resource meets a number of requirements within the topology (302).
Further, in one example, the addition of a policy (303, 308-1) to the topology or portions thereof may cause the design of the topology to change. In this example, a policy (303, 308-1) added to an element of the topology (302) may effect a number of other policies (303, 308-1). For example, associating with a topology (302) a policy that indicates that a node be highly available may evolve the policies (303) and topology (302) as a whole to require, for example, a cluster of nodes. In this manner, policies may drive the design of the topology (302).
Accordingly, a designed topology such as, for example, an architecture topology generated, for example, by an automated or manual matching process with policies and LCMAs associated with the nodes of the topology (302) is modified at the time of provisioning. This may be performed by executing, with the provisioning policy engine (402) or the resource offering manager (308), the provisioning policies to determine a topology that satisfies the provisioning policies perfectly or in the best obtainable manner. Obtaining a best fit topology may involve a number of resource provider policies (308-1) provided by the resource offering manager (308) which describe the capabilities and selection criteria of a resource provider. The resource offering manager (308) selects, for example, the resource provider from which the resource is to be obtained, and may also make other modifications to the topology (302).
At block 411, a number of monitoring, event handling, and remediation policies may also be added to support a number of additional topology systems such as, for example, the monitoring system (313), the event handler (316), and the remediation engine (317). These additional policies (411) will then be used to define how these additional topology systems (313, 316, 317) are provisioned, deployed, and utilized within the to-be-instantiated service. Thus, as depicted in
In one example, context (410) in which a service is to be instantiated may be used by the policies associated with the topology (302) to make a number of policy decisions. Examples of context may include the current load on a system or instantiated service, the identity of a user of the instantiated service, the time of year in which the service is to be instantiated or modified, among other types of contexts in which the present systems and methods are employed. The context may then be used to make policy decisions. For example, in the case of the current load on a system or instantiated service, the policies associated with the topology (302) may cause one or more policy decisions to be made such as, for example, the scaling in or out of the instantiated service. Thus, the context (410) is used by the policies to make policy decisions. Context (410) may be provided to the provisioning policy engine (402) and/or at block 411 where a number of monitoring, event handling, and remediation policies are added.
As depicted in the examples of
The topology (302) is modified per the received provisioning policies (308-1) by the provisioning policy engine (402) as indicated by arrow 407, and sent to an interpreter (403). The interpreter (403) is any hardware device or a combination of hardware and software that interprets the provisioning policies to create an execution plan as indicted by arrow 408. The result is then interpreted and converted into an execution plan (408) that comprises a workflow or sequence of serial and/or parallel scripts in order to create an instance of the topology (
With the above-described sequence based topology, an execution plan (408) may be represented as a blueprint. Conversely, a blueprint may be expressed as an execution plan (408). A blueprint with nodes expanded by policies (303) and LCMAs (304) may be similarly processed, instead, in a manner similar to the processing of an infrastructure topology. In this example, the blueprint in the form of a sequential service design (406) is input to the interpreter for processing as described above in connection with
The execution of the execution plan (408) by the topology life cycle management engine (311) results in an instantiation of the cloud services including the provisioning of devices for monitoring, event handling, and processing and remediation of events and incidents as will be described in more detail below. The result of the topology life cycle management engine (311) executing the workflow or sequence of serial and/or parallel scripts as defined by the execution plan (408) is an instantiated service (312) as indicated by block 405. Further, a realized topology (314) may be created based on the instantiated service (312), and stored as will also be described in more detail below.
As a result of initial execution as described herein in connection with
Resource provider policies (308-1) may be any policies that are associated with a number of resource providers' offerings that guide the selection of a number of resources. In one example, the resource provider policies (308-1) may be dynamic functions that define the computing abilities of a computing resource. In this example, a computing resource that provides a defined level of computing resources such as, for example, processing power may be provisioned by the LCM engine (311) and resource offering manager (308) if the defined level of that computing resource meets a number of requirements within the topology (302).
In some examples, a realized topology is modified at the time of provisioning. This may be performed by executing, with the provisioning policy engine (502) or the resource offering manager (308), the provisioning policies to determine a topology that satisfies the provisioning policies perfectly or in the best obtainable manner. Obtaining a best fit topology may involve a number of resource provider policies (308-1) provided by the resource offering manager (308) which describe the capabilities and selection criteria of a resource provider. The resource offering manager (308) selects, for example, the resource provider from which the resource is to be obtained, and may also make other modifications to the topology (302).
The topology (302) is modified per the received provisioning policies (308-1) by the provisioning policy engine (502) as indicated by arrow 507, and sent to an interpreter (503). The interpreter (503) is any hardware device or a combination of hardware and software that interprets the provisioning policies to create an execution plan as indicted by arrow 508. In some examples, the execution plan (508) may include an indication as to whether the application is self-managing or auto-managing. For example, the execution plan (508) may include code within the application that carries out provisioning, remediation, event handling, or combinations thereof. Alternatively, the execution plan (508) may provision, remediate, handle events, or combinations thereof based on policies.
The result is then interpreted and converted into an execution plan (508) that comprises a workflow or sequence of serial and/or parallel scripts in order to create an instance of the topology (
The execution of the execution plan (508) by the topology life cycle management engine (311) results in an instantiation of the cloud services including the provisioning of devices for monitoring, event handling, and processing and remediation of events and incidents as will be described in more detail below. The topology LCM engine (311) may update a realized topology with policies and LCMAs as indicated by the arrow (514), which may be passed to the realized topology engine (513) to update a realized topology based on the policies and updates.
As to the monitoring and remediation policies described herein, the same type of process may be applied, but with a number of realized policies defined within an instantiated service (312) and its realized topology (314) as input. In this process, additional LCMAs (304) may be created and used to assist in provisioning resources in an updated instantiated service (312). The explanation below across CSA/CDA use cases with architecture topologies or with blueprints shows the notion of common engine, pattern, and platform across all these cases.
The present systems and methods may be used in conjunction with any third party modeling such as, for example, HEAT command language interpreter that is an open source software developed and distributed by the OpenStack Foundation and released under the terms of the Apache License. Although HEAT may assist in the creation of a set of scripts fitting in the space of the execution plan, HEAT may provide support by interpreting or translating data, and converting the data into scripts. The present systems and methods may add the policies (303) and LCMAs (304) to the HEAT interpreter, and execute as described above.
Further, the present systems and methods may use topology and orchestration OASIS specification for cloud applications (TOSCA), a cloud computing standard to express topologies. In this example, the policies (303) and LCMAs (304) are added to a TOSCA-based topology.
Thus, the policies (303) and the LCMAs (304) may be implemented as function calls (305) or scripts in order to provision and deploy the topology (302) when the policies (303) and the LCMAs (304) trigger such provisioning and deployment. A resource offering manager (308) may be provided within the topology-based management broker (200) to manage and provide computing resources within the topology (302) based on the policies (302) and LCMAs (304).
The resource offering manager (308) provides a number of plug-ins to execute the life cycle manager (311). As described above, the resource offering manager (308) associates a number of resource policies (308-1) to the plug-ins of a number of resource providers so that the resource providers may assist in guiding the selection process of a number of the resource providers. The non-resource provider policies such as policies (103) associated to the nodes are different in that they are associated with the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) during the designing of a topology (302).
The resource offering manager (308) may be operated by, for example, an administrator, or a service provider in order to provision the resources within the cloud service to be created via the deployment of the topology (302). As discussed above, the resource offering manager (308) comprises the hardware and software to define a number of resource provider policies (308-1), associate a number of those resource provider policies (308-1) with a number of the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), the topology (302), or portions of the topology (302). When the topology (302) is deployed, the resource offering manager (308) provides the computing resources to the user that will implement the topology (302) based on the policies (303), the LCMAs (304), and the resource provider policies (308-1). As a result, the LCMAs are functions of the policies (303) associated with the topology (302), and the resource provider policies (308-1).
Thus, in one example, the resource offering manager (308) may implement a number of resource provider policies (308-1) that define under which conditions a computing resource from a number of service providers may be selected for deployment within the topology (302). In this example, the policies (303) associated with a node as well as the resource provider policies (308-1) define which resource offering from the resource offering manager (308) is selected for provisioning within the to-be-deployed instantiated topology (312). For example, if a policy associated with node (302-1) requires that the provisioned computing resource be located in a secure facility, and the policies of the resources offered by the resource offering manager (308) indicate that those available computing resources are not located in a secure facility, then that non-secure computing resource provided by that particular service provider will not be selected. In this manner, the policies associated with the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) and the policies associated with the resource offering manager (308) determine which computing resources may be provisioned and deployed within the topology (302).
The topology-based management broker (200) may store the topology (302) in a catalog (310). In one example, the topologies (302) designed and stored in the catalog (310) may be made available to any interested party via a self-service portal (309). In another example, an application program interface (API) may be provided instead of or in addition to the self-service portal (309). In this example, the API may be used by an application executing within the topology-based management broker (200) which may make a request from the catalog (310) for a number of topologies (302).
In another example, the user may be given the opportunity to view the catalog (310) of stored topologies to obtain a topology that was created for a first user or organization, and use a number of those topologies as the user's topology by ordering or subscribing to a topology (302). In still another example, the user may be given the opportunity to view the catalog (310) of stored topologies to obtain a topology that was created for a first user or organization, obtain a number of those topologies, and add a number of other topologies to it such as in an example where an application model is built on an infrastructure template using stitching processes described below.
In still another example, the user may be given the opportunity to view the catalog (310) of stored topologies to obtain topologies that were created for a first user or organization, obtain a number of those topologies, and add a number of other topologies to it such as topologies designed de novo or stored within the catalog (310). In still another example, the user may be given the opportunity to view the catalog (310) of stored topologies to obtain topologies that were created for a first user or organization, obtain a number of those topologies, and build a new cloud service that comprises aspects of all the predefined topologies and the respective services described by the pre-defined topologies.
In another example, the user, a service designer, or a combination thereof may design the topology anew, design a topology based on a topology stored in the catalog (310), or design a topology based partially on a topology stored in the catalog (310). Design of a topology (302) may be split among a number of users, designers, and administrators. The designing of the topology (302) may include separating the design of the topology into a number of topologies and attaching to the separate pieces of the individual topologies and the topology as a whole a number of properties, LCMAs, and policies. The user may also order a desired topology, be given an opportunity to approve of the chosen topology, and view and operate the topology by executing a number of applications on the resultant cloud service.
In another example, an application program interface (API) may be made available that invokes the call functions associated with the desired topology (302). In the self-service portal (309) example, the catalog (310) may be made available to the user, may identify to the user the item or items associated with the desired topology (302), may provide the ability for the user to order a number of services, and provide for the deployment of the selected topology (302). In one example, the deployment of the topology (302) may be approved by the user or a manager as defined by an approval workflow before deployment based on, for example, a service level agreement (SLA), cost of the cloud services, and the policies, among other considerations. In still another example, once the topologies (302) are designed and stored in the catalog (310), the topologies (302) may be identified by commercial terms and associated descriptions of how the topology (302) may be used.
When a topology (302) has been designed, the topology (302) may be provisioned on behalf of the user to create a subscription within the SLA. The topology lifecycle management (LCM) engine (311) is a data processing device that will execute the topology (302) to provision and deploy computing resources to form the cloud service for use by the user. The topology LCM engine (311) analyzes the topology (302) created, and creates a set of scripts that form execution logic in the form of the execution plan to instantiate and realize the topology (302). In one example, the set of scripts define a sequence of provisioning and deployment of computing resources. The topology LCM engine (311) applies the policies associated with the topology (302) and the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) of the topology (302) as well as the policies set for the resources managed by the resource offering manager (308).
As a result of the above systems and methods, an instantiated service (312) is provided to the user for use. The instantiated service (312) comprises a number of computing devices that match the designed topology (302) and the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within the topology (302). The instantiated service (312) functions based on the policies described above. The computing devices that make up the instantiated service (312) may comprise, for example, servers, switches, client devices, and databases, among many other computing devices. A realized topology (314) is derived by the LCM engine (311) or other device based on the instantiated service (312).
In addition to the instantiated service (312), a monitoring system (313) is also deployed if not already existent, or setup and configured if already available in order to monitor the instantiated service (312). With the inclusion of a monitoring system (313) within the topology-based management broker (200), the topology-based management broker (200) provides for a converged management and security (CM&S) environment. In one example, the CM&S environment may be the CM&S environment developed and distributed by Hewlett Packard Corporation. In another example, the CM&S environment may be the CM&S environment described in International Patent App. Pub. No. PCT/US2012/059209, entitled “Hybrid Cloud Environment” to Maes et al., which is hereby incorporated by reference in its entirety. The CM&S environment provides for template- and model-based approaches to application and service development and deployment, with the ability to bind management and security capabilities to service models at deployment time in order to ensure common capabilities across hybrid cloud environments. CM&S also provides portability across private and public cloud environments, which may include heterogeneous infrastructures, management, and security tools. Further, CM&S provides efficient delivery and management of the application release, whether the infrastructure resources are on premise, in the public cloud or in a hybrid environment across public and private clouds. CM&S also provides role-based, predictive, and real-time performance and risk insights, and analytics such as, Business Intelligence (BI), Business Activity Monitoring (BAM), and big data analyses across heterogeneous systems, networks, and cloud environments.
In one example, the monitoring system (313) operates based on the monitoring policies associated with the topology (302) and the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) of the topology (302) as described above. In this example, the monitoring system (313) is used to monitor the operations, the security, the compliance, and the usage of the topology (302) and the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) of the topology (302), among other items to monitor within the instantiated service (312).
In one example, the monitoring system (313) is deployed to monitor the instantiated service (312) in cases where the monitoring system (313) already exists. In this example, a number of existing monitoring devices may be used to monitor the instantiated service (312) autonomously, through human intervention, or a combination thereof by configuring the existing monitoring system (313) to match the monitoring policies defined when designing the topology (302). In this example, the monitoring system (313) already existent may be configured based on the monitoring policies associated with the topology (302) and the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) of the topology (302) as described above, configured based on input from a user, or combinations thereof.
In another example, a previously non-existent monitoring system (313) may be provisioned and deployed based on the monitoring policies defined when designing the topology (302). In this example, the monitoring system (313) is provisioned and deployed at the same time as the provisioning and deployment of the instantiated service (312). Further, the monitoring system (313), in this example, is deployed and managed based on the monitoring policies associated with the topology (302) and the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) of the topology (302) as described above. In any of the above examples, a complete service as outlined by the topology (302) is created, including the instantiated system (312) and the monitoring system (313).
The topology-based management broker (200) further comprises a realized topology system management (RTSM) database (315). The RTSM database (315) is a logical system repository of realized topologies (314), and may be any form of data repository. In one example, the RTSM database (315) comprises a database management system (DBMS). The DBMS is a combination of hardware devices and software modules that interact with a user, other applications, and the database itself to capture and analyze data. In one example, the RTSM database (315) is a configuration management database (CMDB). A CMDB is a repository of information related to all the components of a realize topology (314).
The DBMS of the RTSM database (315) is designed to allow the definition, creation, querying, update, and administration of a database of realized topologies (314). Realized topologies are a model of the topologies (302) with the policies described above associated therewith. Thus, the realized topology (314) comprises a model of the topology (302), with the policies applied to the various nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7). A number of properties of the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) of the realized topology (314) are defined within the realized topology (314). These properties include any details of any instantiated service (312) that is created or updated via the topology-based management broker (200), and may include, for example, the internet protocol (IP) address of the nodes, and characteristics and computing parameters of the nodes, among many other properties.
The RTSM (315) is a repository that stores each instance of a realized topology (314). In this manner, every time a topology (302) is designed, provisioned, and deployed, the topology-based management broker (200) captures the realized topology (314) of that topology (302). Thus, the RTSM (315) contains a realized topology (314) of every topology (302) that has been instantiated within the topology-based management broker (200) or, through the below-described remediation processes, stores a modification of a realized topology or an instantiated service (312). Thus, in one example, in every instance of the modification of an existing topology (302), the realized topology (314) resulting from that modification is also stored within the RTSM (315). The remediation processes will now be described in more detail.
As may happen within the topology-based management broker (200), a number of events may occur within the topology-based management broker (200). These events may include, for example, a policy failure within a node of the instantiated service (312), a failure of one or more hardware or software components within the instantiated service (312), and an unauthorized access of the instantiated service (312), among many other computing-related events. Further, the monitoring system (313) monitors a number of performance- and utilization-related events that may occur within the instantiated service (312). These performance- and utilization-related events may include, for example, processor utilization within a number of the nodes, utilization of a number of the nodes by, for example, customers of the user's business, and levels of remaining data storage space within a data storage device, among many other performance- and utilization-related events.
In one example, the monitoring system (313) informs the event handler (316) of any events detected by the monitoring system (313). The event handler (316) is any computing device that receives data associated with detected events from the monitoring system (313), and processes the data in order to create a number of incidents that may arise from the detected events.
Thus, the topology-based management broker (200) processes the events that are detected by the monitoring system (313). Processing of events detected by the monitoring system (313) may be performed by the event handler (316). The event handler (316) may receive any kind or amount of data from the monitoring system (313). As described above, the data received from the monitoring system (313) by the event handler (316) may include any data associated with the operation and usage of the instantiated service (312) as a whole, and the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within the instantiated service (312) as groups of nodes and as individual nodes. In one example, the event handler (316) performs a number of requests for the event data. In this example, the event handler (316) may poll the monitoring system (313) for the event data after a predefined time period, randomly, when triggered by another event, or a combination thereof. As described above, event handling and processing may, in one example, be delegated to another system or third party service. For example, event handling such as correlation and filtering of events and incidents and incident identification may be delegated to HP BUSINESS SERVICE MANAGEMENT; a suite of service management software tools developed and distributed by the Hewlett Packard Corporation. Remediation processes may be delegated to HP OPERATIONS MANAGER I (HP OMi) or SITESCOPE; both comprising a suite of software tools developed and distributed by the Hewlett Packard Corporation. Security event notification, processing, and remediation may be delegated to HP ARCSIGHT; a suite of service management software tools developed and distributed by the Hewlett Packard Corporation. In one example, HP ARCSIGHT may reference the service agreement (SA) associated with the instantiated service (312) to comply with the SA.
The data received from the monitoring system (313) is processed by the event handler (316), and the event handler (316) determines whether an event requires a remediation action, and whether and how to present a notification of the event to a user, administrator, third party, or other user of the topology-based management broker (200) or instantiated service (312). If the event handler (316) determines that a remediation action is to be taken in connection with an event, the event handler (316) generates an incident based on the event, and the data associated with the event is sent to a remediation engine (317). In one example, the event handler (316) may process the events received from the monitoring system (313) using a number of processing types. Types of processing that the event handler (316) may perform include filtering, correlation, and aggregation of the events, among other forms of event processing, and combinations thereof. In one example, a number of events may collectively be subjected to a number of forms of event processing in order to create an incident. In this example, the events may individually not support the creation of an incident that requires remediation, but a number of events, when analyzed by the event handler (316), may indicate that an issue within the instantiated topology (312) is not in agreement with the policies (303), or is otherwise in need of remediation.
In another example, incidents may be identified from a number of ticket support systems. For example, an information technology (IT) service management system (ITSM) (316-1) may also be a source of incidents. An ITSM system (316-1) implements and manages the quality of IT services that meet the needs of the user. In one example, the ITSM system (316-1) is managed by the user, a service provider, a third party, or combinations thereof, in which a service ticket is opened by one of these groups or individuals. In another example, the ITSM system (316-1) may automatically enter a service ticket based on the events detected by the monitoring system. If the ITSM system (316-1) determines that the instantiated system (312) or a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) thereof are not appropriately provisioned, are wrongly provisioned, or are otherwise unfit for the instantiated system (312), the ITSM system (316-1) may, like the event handler (316), provide a remediation determination in the form of an incident sent to the remediation engine (317).
The incidents generated by the event handler (316) and the ITSM system (316-1) may be brought to the attention of a user, administrator, third party, or other user of the topology-based management broker (200) or instantiated service (312) in the form of a notification. As described above, the remediation policies define how a remediation action is to be performed, and may include: (1) providing notifications to a user, consumer, or administrator; (2) obtaining instructions from the user, consumer, or administrator; (3) taking manual actions input by the user, consumer, or administrator; (4) taking autonomous actions after receiving instructions from the user, consumer, or administrator; (5) taking autonomous actions without receiving instructions from the user, consumer, or administrator; (6) taking autonomous actions without notifying the user, consumer, or administrator or receiving instructions from the user, consumer, or administrator; or combinations thereof. In this manner, the issuance of notifications within the system is defined by the remediation policies.
The remediation engine (317) executes, via a processor, logic to correct the incidents reported by the event handler (316) and/or ITSM system (316-1). Remedies issued by the remediation engine (317) may include, for example, allocation of additional computing resources, allocation of different computing resources, and reallocation of computing resources from one geographical area to another, among many other remediation actions. In one example, the remediation actions taken by the remediation engine (317) are implemented to remedy a misallocation of computing resources that does not comply with the policies associated with the topology (302) designed. In another example, the remediation actions taken by the remediation engine (317) are implemented to remedy a failure of a number of computing resources within the instantiated service (312). In still another example, the remediation actions taken by the remediation engine (317) are implemented to adjust the security levels of the instantiated service (312) and the groups and individual computing resources therein. Any number of other remediation actions may be implemented by the remediation engine (317) for any number of reasons.
In one example, the remediation actions taken by the remediation engine (317) are implemented with or without notification to a user, administrator, third party, or other user as described above. Further, in another example, the remediation actions taken by the remediation engine (317) are implemented autonomously, without user interaction or confirmation from a user.
In still another example, the remediation actions taken by the remediation engine (317) are implemented with user interaction from the consumer, administrator, third party, or other user. In this example, the remediation engine (317) sends data to a self-service subscription management engine (318). The self-service subscription management engine (318) executes, via a processor, logic to present information to a user regarding the events detected by the monitoring system (313) and the incidents generated by the event handler (316) and ITSM system (316-1). The self-service subscription management engine (318) also executes, via a processor, logic to present to a user a number of recommendations for remediation of the events and incidents.
In one example, the self-service subscription management engine (318) executes, via a processor, logic to present a number of graphical user interfaces (GUIs) (318-1) to a user. In this example, the GUIs (318-1) allow a user to view the realized topology (314), and the events detected by the monitoring system (313) and the incidents generated by the event handler (316) and ITSM system (316-1). In this manner, the user is able to identify the problems within the realized topology (314) via the GUIs (318-1) produced by the self-service subscription management engine (318). Further, the GUIs (318-1) allow the user to select a recommended remediation action and define how the remediation action may be executed.
In another example, the self-service subscription management engine (318) may execute, via a processor, an API to provide to a user a number of indicators within a representation of the realized topology (314) that represent the problem within the realized topology (314) paired with information regarding the problem and which nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) in the realized topology (314) the problem is associated with.
When the remediation engine (317) executes its logic to correct the incidents reported by the event handler (316) and ITSM system (316-1), and/or when a user, via the self-service subscription management engine (318), selects a remediation action to be taken, the topology-based management broker (200) executes a number of calls to a number of lifecycle management actions (LCMAs) to remediate the incidents. LCMAs may include, for example, duplication, moving, copying, or killing of a number of computing resources including all or portions of the realized topology (314), among other LCMAs.
The topology LCM engine (311) executes a new topology (302) created through the remediation processes to provision and deploy computing resources to form a new instantiated service (312). Thus, the topology LCM engine (311) iteratively applies the LCMAs received from the self-service subscription management engine (318) and the remediation engine (317) to the realized topology (314) to create the new and subsequent instantiated service (312).
The remediation processes comprises all of the functionality of the monitoring system (313), the event handler (316), the ITSM system (316-1), the remediation engine (317), the self-service subscription management engine (318), the topology LCM engine (311), and combinations thereof. Any number of iterations of this remediation process may be applied to successive realized topologies (314) to create successively new instantiated services (312). In this manner, the new instantiated service (312) will comprise a number of computing resources that match the designed topology (302) as well as the changes made by the executed LCMAs via the remediation process. Thus, the topology-based management broker (200), with the topology LCM engine (311), derives a new and subsequent realized topology from the new and subsequent instantiated service (312), and stores the subsequent realized topology in the RTSM (315).
Based on the above, the topology-based management broker (200) is able to provision, deploy, and maintain an instantiated service (312) autonomously with or without user interaction. Thus, in this manner, a number of applications being executed on the instantiated service (312) are able to be self-executing on the instantiated service (312) by, for example, calling an API.
As described above, the structures of blueprints (100) are difficult to use as models of applications or templates of infrastructures as CONTINUOUS DELIVERY AUTOMATION (CDA) does. CDA is system tool utilized within a topology designer that independently models infrastructure and application requirements while managing versions, configurations, and other application components. CDA 1.2 is also developed and distributed by Hewlett Packard Corporation. The structures of blueprints (100), for the same reason given above, are difficult to use as models of applications because blueprints do not describe the architecture of the application. Further, blueprints are difficult to use as templates of an infrastructure because they also do not describe the architecture of the infrastructure. As a result, systems aiming at modeling application models and infrastructure or platform templates, and mapping the application models and infrastructure or platform templates to each other are not easily reconciled with the blueprints because they are based on different methods of modeling these services. The reconciliation between the models of a number of applications executed on the deployed service with the infrastructure templates of the service will now be described.
As depicted in
The subsystem of the topology-based management broker (200) depicted in
A topology designer (301) may be used to design and create an application model (319). The application model (319) is defined by a lifecycle management topology. As described above in connection with the LCM topology (302), the application model (319) comprises a number of nodes (319-1, 319-2, 319-3). A number of policies and lifecycle management actions (LCMA) are associated with each of the nodes (319-1, 319-2, 319-3) of the application model (319).
A topology designer (301) may also be used to create a number of infrastructure and/or platform templates (320). The templates (320) are defined by a lifecycle management topology. As described above in connection with the LCM topology (302), the templates (320) comprise a number of nodes (320-1, 320-2, 320-3, 320-4, 320-5). A number of policies and lifecycle management actions (LCMA) are also associated with each of the nodes (320-1, 320-2, 320-3, 320-4, 320-5) of the templates (320).
In one example, the topology designers (301), self-service portal (309), and resource offering manager (308), alone or in combination, may associate a number of policies (303) and LCMAs (304) with the nodes (319-1, 319-2, 319-3, 320-1, 320-2, 320-3, 320-4, 320-5) of the application model (319) and infrastructure template (320). In another example, a separate policy engine and LCMA engine may be provided to associate the nodes (319-1, 319-2, 319-3, 320-1, 320-2, 320-3, 320-4, 320-5) of the application model (319) and infrastructure template (320) with the policies and LCMAs as described above.
As depicted in
Similarly, as depicted in
The CDA subsystem described in
Another method the stitching engine (321) may use to stitch the application model (319) to the infrastructure template (320) may comprise an algorithmic matching method. In this method, the stitching engine (321) determines a match mathematically via algorithms that employ the policies in performing the matching decisions. In one example, this may include inference methods in which requirements in the application level are tagged or otherwise associated with components that support them in a library of infrastructure topologies called a DSL database (323), wherein the overall infrastructure template (320) is aggregated first before the aggregation is extended to the application model (319).
A definitive software library (DSL) is a secure storage device, consisting of physical media or a software repository located on a network file server. Definitive authorized versions of all software configuration items (CIs) or artifacts that may be required to deploy the application designed in the application model (319) may be stored and protected in a DSL. In the present example, a number of infrastructure topologies (320) are stored in the DSL. Thus, the DSL contains master copies of a number of infrastructure topologies (320) developed using the present systems and methods or purchased from an third party. All related documentation related to the infrastructure topologies (320) is also stored in the DSL. The DSL database (323) of the present topology-based management broker (200) comprises a number of objects used in the deployment of the application after the application model (319) has been developed and is ready for deployment on the infrastructure template (320). In one example, a topology designer (301) may also provide additional design elements within the topology before, during, and/or after the stitching engine (321) processes the application model (319) and the infrastructure template (320) to create the topology (302) with a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7).
Once the stitching engine (321) has completed the stitching process as described above, a complete topology (302) is created. The topology created by the subsystem of
In one example, an application lifecycle management (ALM) device (322) depicted in
In one example, topologies (302) may be generated by designing a topology (302) de novo via a number of topology designers (301). In another example, the topology may be generated (block 601) by stitching a number of applications models (
The method may continue by associating (block 602) a number of LCMAs (304) with a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within the topology (302). In one example, block 602 may be performed with the resource offering manager (
In one example, policies (
The topology (302) may be executed (block 603). In one example, the topology (302) is executed (block 603) based on the LCMAs (304) associated (block 602) with a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within the topology (302). Further, in another example, the topology (302) is executed (block 603) based on the policies (303) associated with a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within the topology (302).
In still another example, a number of scripts may be created for execution (block 603) of the topology (302). The scripts define executable logic for instantiating a cloud service based on the topology (
In one example, topologies (302) may be generated by designing a topology (302) de novo via a number of topology designers (301). In another example, the topology may be generated (block 601) by stitching a number of applications models (
In one example, a number of persons may use the topology designers (301) to design the topologies (302) in accordance with the method of
The method may continue by associating (block 702) a number of policies (
At block 703, a number of lifecycle management actions (LCMAs) (
In one example, the policies (
In another example, the LCMAs are associated with the aspects of the topology by explicitly providing a number of functions, FAction, that define how to select a resource provider to implement the action based on the policies associated with the aspects of the topology and the policies of the different relevant resource providers. These functions define how a resource provider is selected to implement the action based on the policies associated with the aspect of the topology and the policies of the different relevant resource providers. In one example, the processes of blocks 702 and 703 may be performed in any order serially, or in parallel. Further, in one example, a number of persons may use the topology designers (301) to design the topologies (302) in accordance with the method of
A number of resource provider policies (308-1) may be associated (block 704) with a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within the topology (302). Resource provider policies (308-1) are any policies associated with a number of resource providers' offerings that guide the selection of a number of resources. In one example, the resource provider policies (308-1) may be dynamic functions that define the computing abilities of a computing resource. In this example, a computing resource that provides a defined level of computing resources such as, for example, processing power, may be provisioned by the LCM engine (311) and resource offering manager (308) if the defined level of that computing resource meets a number of requirements within the topology (302).
The topology (302) may be executed (block 705). In one example, the topology (302) is executed (block 705) based on the policies, (303), LCMAs (304), resource provider policies (308-1), or combinations thereof. In one example, a number of scripts may be created for execution (block 705). The scripts define executable logic for instantiating a cloud service based on the topology (
A topology LCM engine (
A number of realized topologies (
In one example, the RTSM database (
The RTSM (
The remediation method of
The monitoring system (313) sends data representing a number of the events to the event handler (313) based on a number of the policies associated with the designed topology (302) and the instantiated service (312). For example, as described above, the monitoring policies include a portion that defines what to do with the monitored events that result from the monitoring such as, for example, how to handled the events, where the events are sent, what devices or individuals address the events, how incidents resulting from the processing of the events are handled, how the events and incidents are processed (e.g., processed as aggregated, filtered, or correlated events, among other forms of processing), and how the resulting incidents are handled.
A number of events detected by the monitoring system (313) may be processed by the event handler (316) based on a number of the policies described above. Handling (block 802) of events may include, for example, processing the events as aggregated, filtered, or correlated events, among other forms of processing. Further, based on the above-described policies, the event handler (313) may handle (block 802) the events by determining whether the events should be processed into incidents, or whether to notify a number of users of the system (200), for example.
A number of incidents are generated (block 802). In one example, the incidents are created by the event handler (
The incidents generated by the event handler (316) and the ITSM system (316-1) may be brought to the attention of a user, administrator, third party, or other user of the topology-based management broker (200) or instantiated service (312) in the form of a notification. A number of notifications are sent (block 804) regarding the incidents created by the event handler (313). These notifications may be sent (block 804) to a number of devices and users within the system (200). For example, a number of notifications may be sent to the self-service subscription management engine (318). The self-service subscription management engine (318) may present the notifications to a user via, for example, the GUI (318-1) associated with the self-service subscription management engine (318). Thus, a number of notifications are presented (block 804) to a user regarding the incidents.
In one example, the process defined by block 804 is optional. As described above, the event handler (
At block 805, a number of function calls are generated. The function calls issued to the LCM engine (311) by the remediation engine (317) to remediate the incidents may be based on a number of LCMAs associated with the elements of the instantiated topology (312), the incidents to be remediated, and the policies associated with the elements of the topology (302). In this manner, the remediation engine (317) executes, via a processor, logic to correct the incidents reported by the event handler (316) and/or ITSM system (316-1) in order to generate (block 805) the function calls.
Using the function calls generated by the remediation engine (317), the topology LCM engine (
A subsequent realized topology (
A determination (block 809) may be made as to whether monitoring of an instantiated topology (
A number of infrastructure templates (
A number of application models (
The stitching engine (
Another method the stitching engine (
A number of policies and lifecycle management actions (LCMAs) are associated (blocks 704 and 705) with each of the nodes (
In one example, the processes of blocks 704 and 705 of associating policies (303) and lifecycle management actions (LCMAs) (304) with each of the nodes (
The above processes described in
Relationships between nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within the topology (302) may also be expressed as logic that interacts with the lifecycle management of each node. One type of relationship includes conditions regarding the order by which computing resources from the resource providers are provisioned at the time of execution and instantiation of the topology (302). For example, the provisioning of a particular computing device such as a server may need to be performed before another device within the cloud service. Other forms of relationships between nodes include actions that interact with the lifecycle management of the nodes including, for example, provisioning, duplicating, destroying, pausing, saving, copying, modifying, and moving, of the nodes, among other lifecycle management actions.
In one example, the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) may be defined by the logic of their lifecycle management. In this example, the logic decorating the nodes perform the same function. In another example, the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) may be defined using a standard data type such as, for example, TOSCA. In this example, the node types are associated with different resource providers that implement the types.
The relationships between the nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within a topology (302) may also be associated with lifecycle management actions or logic. These lifecycle management actions associated with the relationships between nodes dictate the provisioning and instantiation of the topology, and management of the lifecycle of the nodes and topology after provisioning and instantiation.
Topologies (302) to be executed and instantiated via the present systems and methods may be designed de novo via a number of topology designers and/or via a application model and infrastructure template stitching process as described above, or any other methods of creating or obtaining a topology with associated LCMAs and policies. Further, as will be described in more detail below, the LCM engine (311) may also directly execute a blueprint. With regard to blueprints, blueprints describe services in terms of the collections of workflows that are to be performed on all the components that make up the service in order to perform a particular lifecycle management action. Blueprints may be expressed as comprising a number of objects within a hierarchy of objects.
Still further, topologies may also be generated by transforming a blueprint into a topology. The transformation of a blueprint into a topology may begin by obtaining a blueprint (100) from a blueprint source, and deriving a number of containment relationships from the blueprint (100). This may be performed by the blueprint analysis module (1012). The containment relationships define a number of hierarchical relationships between a number of objects within the blueprint (100). A number of temporal dependency relationships may also be derived from the blueprint (100), the temporal dependency relationships defining a number of provisioning relationships between objects within the blueprint (100). For example, the temporal dependency relationships may define in what order various devices represented by the objects in the blueprint are to be provisioned. A number of objects may be required to be provisioned or instantiated before other objects. For example, temporal dependency relationships may define that a number of infrastructure elements are first deployed, and then a number of application elements deployed on top of the infrastructure elements. In one example, the temporal dependency relationships may be defined using a UML metamodel (M2-model); an example of a Layer 2 Meta-Object Facility model developed by the Object Management Group (OMG).
A number of additional relationships between a number of the objects within the blueprints (100) may also be derived. The additional relationships comprise a number of parameters derived by the topology LCM engine (311) from a number of the containment relationships, a number of the temporal dependency relationships, a number of objects, or combinations thereof. Knowing of these additional relationships assists the topology designer (301) in creating a topology that appropriately fits an intended use and will work with a number of applications intended to run on an instantiated service (312) derived from the topology (302). A topology may be created based on the number of objects within the blueprint (100), a number of the containment relationships, a number of the temporal dependency relationships, a number of the additional relationships, or a combination thereof. Any format may be used to describe topologies (302) derived from blueprints (100). In one example, TOSCA may be used to describe topologies (302) derived from the blueprints (100).
A lifecycle management topology derived from a blueprint may comprise a number of nodes and relationships associated to a combination of conditions and actions for each life cycle management operation: The different elements of infrastructure, platforms, applications, and services are described in the lifecycle management topologies (302). In the topologies (302), elements in each layer are defined as nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) as described above. A number of policies and LCMAs may also be associated with the blueprint-derived topology (302). The association of the policies (303) and LCMAs (304) with the topology (302) may be performed as described above. In this manner, even though a number of policies and LCMAs may be derived from the blueprint (100) by way of derivation of the containment relationships, the temporal dependency relationships, and the additional relationships from the blueprint, a number of additional policies and LCMAs may be added to the blueprint-derived topology (302). For example, the topology designer (301) and the resource offering manager (308) may associate an additional number of policies (303) and LCMAs (304) in order to create a topology (302) that, when instantiated, will perform as desired or expected. Execution of the policies (303) provides for a way to provision the topology (302) with a configuration that is identical or approximately identical to an instantiated service that is instantiated based on the blueprint. In this manner, a LCM topology (302) is derived from a blueprint. The LCM topology (302) derived from the blueprint may be provisioned and instantiated as described above in connection with
The topology LCM engine (311) may be utilized in any data processing scenario including, hardware, mobile application, a network, or combinations thereof. Further, the topology LCM engine (311) may be used in a computing network, a public cloud network, a private cloud network, a hybrid cloud network, other forms of networks, or combinations thereof. In one example, the methods provided by the topology LCM engine (311) are provided as a service over a network by, for example, a third party. In this example, the service may comprise, for example, the following: a Software as a Service (SaaS) hosting a number of applications; a Platform as a Service (PaaS) hosting a computing platform comprising, for example, operating systems, hardware, and storage, among others; an Infrastructure as a Service (IaaS) hosting equipment such as, for example, servers, storage components, network, and components, among others; application programming interface (API) as a service (APIaaS), other forms of network services, or combinations thereof. The present systems may be implemented on one or multiple hardware platforms, in which the modules in the system can be executed on one or across multiple platforms. Such modules can run on various forms of cloud technologies and hybrid cloud technologies or offered as a SaaS (Software as a service) that can be implemented on or off the cloud. In another example, the methods provided by the topology LCM engine (311) are executed by a local administrator.
To achieve its desired functionality, the topology LCM engine (311) comprises various hardware components. Among these hardware components may be a number of processors (1001), a number of data storage devices (1002), a number of peripheral device adapters (1003), and a number of network adapters (1004). These hardware components may be interconnected through the use of a number of busses and/or network connections. In one example, the processor (1001), data storage device (1002), peripheral device adapters (1003), and a network adapter (1004) may be communicatively coupled via a bus (1005).
The processor (1001) may include the hardware architecture to retrieve executable code from the data storage device (1002) and execute the executable code. The executable code may, when executed by the processor (1001), cause the processor (1001) to implement at least the functionality of topology and blueprint execution, and instantiation of cloud services therefrom, according to the methods of the present specification described herein. In the course of executing code, the processor (1001) may receive input from and provide output to a number of the remaining hardware units within the topology LCM engine (311), the topology-based management broker (100), or other internal or external computing devices.
The data storage device (1002) may store data such as executable program code that is executed by the processor (1001) or other processing device. As will be described in more detail below, the data storage device (1002) may specifically store a number of application modules that the processor (1001) executes to implement at least the functionality described herein.
The data storage device (1002) may include various types of memory modules, including volatile and nonvolatile memory. For example, the data storage device (1002) of the present example includes Random Access Memory (RAM) (1006), Read Only Memory (ROM) (1007), and Hard Disk Drive (HDD) memory (1008). Many other types of memory may also be utilized, and the present specification contemplates the use of many varying type(s) of memory in the data storage device (1002) as may suit a particular application of the principles described herein. In certain examples, different types of memory in the data storage device (1002) may be used for different data storage needs. For example, in certain examples the processor (1001) may boot from Read Only Memory (ROM) (1007), maintain nonvolatile storage in the Hard Disk Drive (HDD) memory (1008), and execute program code stored in Random Access Memory (RAM) (1006).
Generally, the data storage device (1002) may comprise a computer readable medium, a computer readable storage medium, or a non-transitory computer readable medium, among others. For example, the data storage device (1002) may be, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium may include, for example, the following: an electrical connection having a number of wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In another example, a computer readable storage medium may be any non-transitory medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The peripheral device adapters (1003) in the topology LCM engine (311) enable the processor (1001) to interface with various other hardware elements, external and internal to the topology LCM engine (311). For example, peripheral device adapters (103) may provide an interface to input/output devices, such as, for example, a display device, a mouse, or a keyboard. The peripheral device adapters (103) may also provide access to other external devices such as a number of external storage devices. The display device may be provided to allow an individual to interact with and implement the functionality of the topology LCM engine (311). The peripheral device adapters (103) may also create an interface between the processor (1001) and a printer, the display device, or other media output device. The network adapter (1004) may provide an interface to other computing devices within, for example, a network, thereby enabling the transmission of data between the topology LCM engine (311) and other devices located within the network.
The topology LCM engine (311) further comprises a number of modules used in the execution and implementation of topologies and blueprints. The various modules within the topology LCM engine (311) may be executed separately. In this example, the various modules may be stored as separate computer program products. In another example, the various modules within the topology LCM engine (311) may be combined within a number of computer program products; each computer program product comprising a number of the modules.
The topology LCM engine (311) may include a regime determination module (1009) to, when executed by the processor (1001), determine whether a topology or blueprint is to be executed in connection with
The LCM engine (311) and the below described blueprint analysis engine (1012) co-exist by determining, via the regime determination module (1009), which content or data is associated with the blueprint regime, and which content or data is associated with the topology regime. The content or data associated with the blueprint engine may be directly executed by the script execution module (1013) or transformed into a topology and executed as a topology. Content or data associated with a topology or a blueprint-derived topology is executed by transforming the topology into executable logic like a blueprint, and executing the executable logic using the same engine. Thus, the present LCM engine (300) is capable of executing and instantiating both topologies and blueprints. This has the advantage of providing a system that can accommodate for all forms of cloud service instantiation.
Thus, in one example, a topology (302) may be designed using the stitching engine (121) to stitch a number of application models (119) to a number of infrastructure templates (120) as described above in connection with
Blueprints describe services in terms of the collections of workflows that are to be performed on all the components that make up the service in order to perform a particular lifecycle management action. Similarly, the topologies to be executed by the LCM engine may be converted into blueprint-like workflows that are to be executed to provision, instantiate and manage all the components that make up the service. During provisioning and instantiation of a topology, the LCMAs associated with a topology are performed as calls to a resource provider. The resource provider converts the calls into instructions specific to a particular resource offered by a resource provider. Similarly, each object in a blueprint may be associated with action workflows that call resource providers.
The topology LCM engine (311) may include a blueprint analysis module (1012) to, when executed by the processor (1001), convert a blueprint (100) to a topology (302) and execute the blueprint (100). As described above, the topology LCM engine (311) may process a blueprint to obtain a number of containment relationships for use in designing a topology. Further, a number of temporal dependency relationships may also be derived from the blueprint in order to design the topology (302). Still further, the topology LCM engine (311) may process the blueprint to obtain a number of additional relationships for use in designing a topology.
Further, the blueprint analysis module (1012) analyzes a blueprint (100) in anticipation for direct execution as described above. In this example, a blueprint (100) may be obtained and executed without first converting the blueprint into a topology (302). Blueprints are already expressed as an orchestration of serial and parallel scripts or executable logic. In this example, the blueprint's (100) collection of workflows are executed by calling resource providers to provision all the components that make up the service. In this manner, the LCM engine (311) is capable of executing a blueprint and instantiating a service directly from the blueprint (100).
Topologies, however, are executed by the LCM engine (311) differently. As will be described in more detail below, the execution and instantiation of topologies is performed by first transforming the topologies (302) into a number of serial and parallel scripts with the scripting module (1011). This transformation of a topology (302) into a series of scripts that are executed is equivalent to the manner in which a blueprint is expressed. Further, a topology's execution and instantiation is equivalent to a blueprint. Thus, the LCM engine (311) may execute a topology by additionally transforming the topology into a combination of serial and parallel scripts like those in a blueprint as will be described in more detail below. Thus, the LCM engine comprises the scripting module (1011) to add the transformation of the topology to a number of serial and parallel scripts in front of the LCM engine's instantiation processes.
Having described several sources of designed topologies including de novo designs, designs from a stitching method, and designs based on blueprints and the use of the regime determination module (1009) and the blueprint analysis module (1012), a method of executing lifecycle management topologies (302) using a number of sets of serial and parallel lifecycle management logics will now be described. The topology LCM engine (311) may include a policy evaluation module (1010) to, when executed by the processor (1001), identify and execute a number of the policies associated with a topology (302) to guide provisioning of a number of computing resources from a number of resource providers. As described above, policies (303) are a number of descriptions, metadata, workflows, scripts, rules, or sets of rules that are applicable to guiding the provisioning, monitoring, enforcement, governance, access control, usage, and remediation tasks associated with the lifecycle management of a number of nodes (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) within a cloud service environment in which the topology (302) is to be or has been implemented. The policies (303) may be associated with and operable against a number of individual nodes, a number of groups of nodes, a number of nodes of a class of nodes, a subset of the nodes within the entire topology of the cloud service; the entire topology of the cloud service as a whole, or combinations thereof. If the policies (303) are initiated, the policies will guide how life cycle management actions LCMAs (304) are taken with respect to, or performed on the individual nodes, groups of nodes, nodes of a class of nodes, a subset of the nodes within the entire topology of the cloud service, or the entire topology of the cloud service as a whole.
The topology LCM engine (311) may further include the above-described scripting module (1011) to, when executed by the processor (1001), derive a number of serial and parallel scripts from the topology (302) or blueprint (100) for execution by the LCM engine (311). Scripts are a series of commands or executable logic, combined in a file, which carry out a number of functions when the file is executed. Scripts are interpreted as they are executed. All scripts can be executed serially during the instantiation of a topology (302) or blueprint (100), However, some scripts derived from the topologies (302) and blueprints (100) may be executed in parallel due to the non-dependent nature of the to-be-provisioned computing resources. In this manner, parallelization of scripts where possible speeds up the execution and instantiation of the topologies (302) and blueprints (100).
A number of scripts may be derived by the scripting module (1011) for execution. The scripts define executable logic for instantiating a cloud service based on a topology (
If, however, the blueprint is to be converted into a topology (block 1202, determination YES), then conversion of the blueprint (100) into a topology (302) may proceed by following element B to
At block 1206, the blueprint analysis module (1012), topology designer (301), or other device derives a number of temporal dependency relationships from the blueprint, the temporal dependency relationships defining a number of provisioning relationships between objects within the blueprint (100). In one example, the temporal dependency relationships are explicit parameters of the blueprint (100). In another example, the temporal dependency relationships are characteristics of the blueprint (100). In this example, a device such as, for example, the blueprint analysis module (1012) or the topology designer (301), derives the temporal dependency relationships from the blueprints (100) using logic of the topology designer (301).
A number of additional relationships between a number of the objects within the blueprints (100) may also be derived (block 1207) using the blueprint analysis module (1012), topology designer (301), or other device. A number of parameters can also be derived by the topology designer (301) from a number of the containment relationships, a number of the temporal dependency relationships, a number of objects, or combinations thereof. In one example, the parameters may be expressed as these additional relationships between a number of the objects within the blueprints (100). Knowing of these additional relationships assists the topology designer (301) in creating a topology that appropriately fits an intended use and will work with a number of applications intended to run on an instantiated service (112) derived from the topology (302).
The method of
The method of
At block 1210, a number of LCMAs may be associated with a number of nodes within the topology (302) formed from the blueprint (100). The association of the policies (303) and LCMAs (304) with the topology (302) may be performed as described above. In this manner, even though a number of policies and LCMAs may be derived from the blueprint (100) by way of derivation of the containment relationships, the temporal dependency relationships, and the additional relationships from the blueprint (100), a number of additional policies and LCMAs may be added to the topology (302) in order to create a topology (302) that, when instantiated, will perform as desired or expected. In this manner, a blueprint is converted into a topology, and the method returns via element C to
Turning again to block 1201, if the input is a topology (302) (block 1201, determination TOPOLOGY), or if a blueprint (100) is converted into a topology via blocks 1202 through 1210, the execution of the topology may be described in connection with both
The topology LCM engine (311) obtains the workflows or sequences of serial and/or parallel scripts, and calls (block 1213) a number of resource providers via the resource offering manager (308) as indicated by arrow 409 of
Assuming the workflow or sequence of serial and/or parallel scripts is executable, the actions associated with the workflow or sequence of serial and/or parallel scripts are executed by the LCM engine (311). For example, if a node (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7) is required to be provisioned before another node (302-1, 302-2, 302-3, 302-4, 302-5, 302-6, 302-7), the topology may not be realizable if the serial or parallel scripts did not account for this prerequisite provisioning. In this example, an exception is raised and an error is returned and/or logged. Further, in one example, parallel scripts may be used in situations were no order relationships between nodes are implied.
With the above-described sequence based topology, an execution plan (408) may be represented as a blueprint. Conversely, a blueprint may be expressed as an execution plan (408). A blueprint with nodes expanded by policies (303) and LCMAs (304) may be similarly processed, instead, in a manner similar to the processing of a topology. In this example, the blueprint in the form of a sequential service design (406) is input to the interpreter for processing as described above in connection with
The execution of the execution plan (408) by the topology life cycle management engine (311) results in an instantiation (block 1214) of the cloud services including the provisioning of devices for monitoring, event handling, and processing and remediation of events and incidents as described herein. The result of the topology life cycle management engine (311) executing the workflow or sequence of serial and/or parallel scripts as defined by the execution plan (408) is an instantiated service (312) as indicated by block 405 of
As described above,
Resource provider policies (308-1) may be any policies that are associated with a number of resource providers' offerings that guide the selection of a number of resources. In one example, the resource provider policies (308-1) may be dynamic functions that define the computing abilities of a computing resource. In this example, a computing resource that provides a defined level of computing resources such as, for example, processing power may be provisioned by the LCM engine (311) and resource offering manager (308) if the defined level of that computing resource meets a number of requirements within the topology (302).
In some examples, a realized topology is modified at the time of provisioning. This may be performed by executing, with the provisioning policy engine (502) or the resource offering manager (308), the provisioning policies to determine a topology that satisfies the provisioning policies perfectly or in the best obtainable manner. Obtaining a best fit topology may involve a number of resource provider policies (308-1) provided by the resource offering manager (308) which describe the capabilities and selection criteria of a resource provider. The resource offering manager (308) selects, for example, the resource provider from which the resource is to be obtained, and may also make other modifications to the topology (302).
The topology (302) is modified per the received provisioning policies (308-1) by the provisioning policy engine (502) as indicated by arrow 507, and sent to an interpreter (503). The interpreter (503) is any hardware device or a combination of hardware and software that interprets the provisioning policies to create an execution plan as indicted by arrow 508. In some examples, the execution plan (508) may include an indication as to whether the application is self-managing or auto-managing. For example, the execution plan (508) may include code within the application that carries out provisioning, remediation, event handling, or combinations thereof. Alternatively, the execution plan (508) may provision, remediate, handle events, or combinations thereof based on policies.
The result is then interpreted and converted into an execution plan (508) that comprises a workflow or sequence of serial and/or parallel scripts in order to create an instance of the topology (
The execution of the execution plan (508) by the topology life cycle management engine (311) results in an instantiation of the cloud services including the provisioning of devices for monitoring, event handling, and processing and remediation of events and incidents as will be described in more detail below. The topology LCM engine (311) may update a realized topology with policies and LCMAs as indicated by the arrow (514), which may be passed to the realized topology engine (513) to update a realized topology based on the policies and updates
Aspects of the present system and method are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to examples of the principles described herein. Each block of the flowchart illustrations and block diagrams, and combinations of blocks in the flowchart illustrations and block diagrams, may be implemented by computer usable program code. The computer usable program code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the computer usable program code, when executed via, for example, the a number of processors within the devices comprising the topology-based management broker (200) or other programmable data processing apparatus, implement the functions or acts specified in the flowchart and/or block diagram block or blocks. In one example, the computer usable program code may be embodied within a computer readable storage medium; the computer readable storage medium being part of the computer program product. In one example, the computer readable storage medium is a non-transitory computer readable medium.
The specification and figures describe methods and systems of managing the lifecycle of cloud service modeled as a topology. These systems and methods include, 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.
This management of the lifecycle of a cloud service modeled as a topology may have a number of advantages, including: (1) providing a common stack along with common use of topologies, realized topologies, and policies may be used to support all use cases for both cloud service automation (CSA) and continued delivery automation (CDA) platforms and services to construct topologies while utilizing the same technology and supporting multiple providers' associated technologies; (2) providing a computing environment in which CSA and CDA use the same topology representations such as, for example, extensible mark-up language (XML) or JavaScript object mutation (JSON); (3) providing a method of managing migration of content for CSA by reusing existing CSA content, creating a path to migrate resource providers, and reusing providers; (4) avoiding or alleviating the risk of perpetuating a CSA/CDA confusion, duplication of efforts and endangering future CSA opportunities; (5) complex applications may be automatically deployed on requested infrastructure without also requiring users to understand how to perform such operations, and (6) supports a CM&S environment, among many other advantages.
The preceding description has been presented to illustrate and describe examples of the principles described. This description is not intended to be exhaustive or to limit these principles to any precise form disclosed. Many modifications and variations are possible in light of the above teaching.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7512578 | Abnous et al. | Mar 2009 | B2 |
| 7979245 | Bourlatchkov et al. | Jul 2011 | B1 |
| 8032557 | Vijendra et al. | Oct 2011 | B1 |
| 8082337 | Davis et al. | Dec 2011 | B1 |
| 8132260 | Mayer et al. | Mar 2012 | B1 |
| 8175987 | Fickie et al. | May 2012 | B2 |
| 8244777 | Vijendra et al. | Aug 2012 | B1 |
| 8250213 | Glover et al. | Aug 2012 | B2 |
| 8266321 | Johnston-Watt et al. | Sep 2012 | B2 |
| 8275724 | Hinchey et al. | Sep 2012 | B2 |
| 8291378 | Arnold et al. | Oct 2012 | B2 |
| 8312419 | Wilcock et al. | Nov 2012 | B2 |
| 8320381 | Lange | Nov 2012 | B2 |
| 8335851 | Vendrow | Dec 2012 | B1 |
| 8341427 | Auradkar et al. | Dec 2012 | B2 |
| 8412810 | Tompkins | Apr 2013 | B1 |
| 8417938 | Considine et al. | Apr 2013 | B1 |
| 8423731 | Nadathur et al. | Apr 2013 | B1 |
| 8488646 | Chang-Hasnain et al. | Jul 2013 | B2 |
| 8983987 | Ravi et al. | Mar 2015 | B2 |
| 9578063 | Iyer et al. | Feb 2017 | B1 |
| 9628360 | Nagai et al. | Apr 2017 | B2 |
| 9634965 | Mehta et al. | Apr 2017 | B2 |
| 9791908 | Grehan et al. | Oct 2017 | B2 |
| 9843487 | Mordani et al. | Dec 2017 | B2 |
| 9876684 | Gomadam et al. | Jan 2018 | B2 |
| 20040162741 | Flaxer et al. | Aug 2004 | A1 |
| 20060080412 | Oprea et al. | Apr 2006 | A1 |
| 20070156650 | Becker | Jul 2007 | A1 |
| 20080077970 | Hares | Mar 2008 | A1 |
| 20080161941 | Strassner et al. | Jul 2008 | A1 |
| 20080216006 | Jordan et al. | Sep 2008 | A1 |
| 20080244595 | Eilam et al. | Oct 2008 | A1 |
| 20080306798 | Anke | Dec 2008 | A1 |
| 20080307104 | Amini et al. | Dec 2008 | A1 |
| 20090157419 | Bursey | Jun 2009 | A1 |
| 20090172689 | Bobak et al. | Jul 2009 | A1 |
| 20090204458 | Wiese et al. | Aug 2009 | A1 |
| 20100027552 | Hill | Feb 2010 | A1 |
| 20100115490 | Wilcock et al. | May 2010 | A1 |
| 20100142409 | Fallon et al. | Jun 2010 | A1 |
| 20100169860 | Biazei et al. | Jul 2010 | A1 |
| 20100175060 | Boykin et al. | Jul 2010 | A1 |
| 20100223385 | Gulley et al. | Sep 2010 | A1 |
| 20100250744 | Hadad | Sep 2010 | A1 |
| 20100274635 | Flinn et al. | Oct 2010 | A1 |
| 20100325496 | Kumar | Dec 2010 | A1 |
| 20110022564 | Flinn et al. | Jan 2011 | A1 |
| 20110029810 | Jaisinghani | Feb 2011 | A1 |
| 20110029882 | Jaisinghani | Feb 2011 | A1 |
| 20110055707 | Kimmet | Mar 2011 | A1 |
| 20110066719 | Miryanov et al. | Mar 2011 | A1 |
| 20110072486 | Hadar et al. | Mar 2011 | A1 |
| 20110072487 | Hadar et al. | Mar 2011 | A1 |
| 20110075674 | Li et al. | Mar 2011 | A1 |
| 20110145035 | Franke et al. | Jun 2011 | A1 |
| 20110161696 | Fletcher | Jun 2011 | A1 |
| 20110196940 | Martinez et al. | Aug 2011 | A1 |
| 20110213765 | Cui et al. | Sep 2011 | A1 |
| 20110231899 | Pulier et al. | Sep 2011 | A1 |
| 20110238805 | Signori | Sep 2011 | A1 |
| 20110252096 | Ramaswamy et al. | Oct 2011 | A1 |
| 20110276583 | Stone et al. | Nov 2011 | A1 |
| 20110276685 | De et al. | Nov 2011 | A1 |
| 20110289119 | Hu et al. | Nov 2011 | A1 |
| 20110296021 | Dorai et al. | Dec 2011 | A1 |
| 20120011077 | Bhagat | Jan 2012 | A1 |
| 20120054626 | Jens | Mar 2012 | A1 |
| 20120102180 | Jaisinghani | Apr 2012 | A1 |
| 20120124211 | Kampas et al. | May 2012 | A1 |
| 20120151402 | Durham et al. | Jun 2012 | A1 |
| 20120173691 | Kothe et al. | Jul 2012 | A1 |
| 20120185913 | Martinez et al. | Jul 2012 | A1 |
| 20120191852 | Carter | Jul 2012 | A1 |
| 20120203888 | Balakrishnan et al. | Aug 2012 | A1 |
| 20120203908 | Beaty et al. | Aug 2012 | A1 |
| 20120204169 | Breiter et al. | Aug 2012 | A1 |
| 20120204187 | Breiter et al. | Aug 2012 | A1 |
| 20120215923 | Mohindra et al. | Aug 2012 | A1 |
| 20120239792 | Banerjee et al. | Sep 2012 | A1 |
| 20120246126 | Rodriguez et al. | Sep 2012 | A1 |
| 20120266156 | Spivak et al. | Oct 2012 | A1 |
| 20120271937 | Cotten et al. | Oct 2012 | A1 |
| 20120272249 | Beaty et al. | Oct 2012 | A1 |
| 20120311012 | Mazhar et al. | Dec 2012 | A1 |
| 20130007710 | Vedula et al. | Jan 2013 | A1 |
| 20130014107 | Kirchhofer | Jan 2013 | A1 |
| 20130042003 | Franco et al. | Feb 2013 | A1 |
| 20130051419 | Chang-Hasnain et al. | Feb 2013 | A1 |
| 20130073724 | Parashar et al. | Mar 2013 | A1 |
| 20130080902 | Jaisinghani | Mar 2013 | A1 |
| 20130086249 | White et al. | Apr 2013 | A1 |
| 20130086551 | Archer et al. | Apr 2013 | A1 |
| 20130132850 | Subramanian et al. | May 2013 | A1 |
| 20130185667 | Harper et al. | Jul 2013 | A1 |
| 20130191539 | Sailer et al. | Jul 2013 | A1 |
| 20130198346 | Jubran et al. | Aug 2013 | A1 |
| 20130232463 | Nagaraja et al. | Sep 2013 | A1 |
| 20130232480 | Winterfeldt et al. | Sep 2013 | A1 |
| 20130232497 | Jalagam et al. | Sep 2013 | A1 |
| 20130232498 | Mangtani et al. | Sep 2013 | A1 |
| 20130263209 | Panuganty | Oct 2013 | A1 |
| 20130268638 | Anderson et al. | Oct 2013 | A1 |
| 20130283174 | Faridian et al. | Oct 2013 | A1 |
| 20130297772 | Ashok et al. | Nov 2013 | A1 |
| 20140007079 | Whitney et al. | Jan 2014 | A1 |
| 20140052877 | Mao | Feb 2014 | A1 |
| 20140074973 | Kumar et al. | Mar 2014 | A1 |
| 20140075426 | West et al. | Mar 2014 | A1 |
| 20140165060 | Muller et al. | Jun 2014 | A1 |
| 20140165138 | Maida-Smith et al. | Jun 2014 | A1 |
| 20140278623 | Martinez et al. | Sep 2014 | A1 |
| 20140282586 | Shear et al. | Sep 2014 | A1 |
| 20140344006 | Biazetti et al. | Nov 2014 | A1 |
| 20140372533 | Fu et al. | Dec 2014 | A1 |
| 20140380308 | Hassine et al. | Dec 2014 | A1 |
| 20150007169 | Li et al. | Jan 2015 | A1 |
| 20150067171 | Yum et al. | Mar 2015 | A1 |
| 20150074279 | Maes et al. | Mar 2015 | A1 |
| 20150089041 | Mehta et al. | Mar 2015 | A1 |
| 20150089068 | Islam et al. | Mar 2015 | A1 |
| 20150304231 | Gupte et al. | Oct 2015 | A1 |
| 20160057234 | Parikh et al. | Feb 2016 | A1 |
| 20160156661 | Nagaratnam et al. | Jun 2016 | A1 |
| 20160179600 | Joshi et al. | Jun 2016 | A1 |
| 20160205037 | Gupte et al. | Jul 2016 | A1 |
| 20160219097 | Gupte et al. | Jul 2016 | A1 |
| 20160254943 | Maes | Sep 2016 | A1 |
| 20160254957 | Maes | Sep 2016 | A1 |
| 20160254961 | Maes | Sep 2016 | A1 |
| 20160269249 | Maes | Sep 2016 | A1 |
| 20160277250 | Maes | Sep 2016 | A1 |
| 20160285694 | Maes | Sep 2016 | A1 |
| 20170048314 | Aerdts et al. | Feb 2017 | A1 |
| 20170063615 | Yang et al. | Mar 2017 | A1 |
| 20170171020 | Wei et al. | Jun 2017 | A1 |
| 20170257432 | Fu et al. | Sep 2017 | A1 |
| 20170302532 | Maes | Oct 2017 | A1 |
| 20170302537 | Maes | Oct 2017 | A1 |
| 20180046438 | Boutier et al. | Feb 2018 | A1 |
| 20180309646 | Mustafiz et al. | Oct 2018 | A1 |
| 20180322558 | Padmanabh et al. | Nov 2018 | A1 |
| 20190026175 | Shelke et al. | Jan 2019 | A1 |
| 20190028400 | Kommula et al. | Jan 2019 | A1 |
| 20190098082 | Hansen et al. | Mar 2019 | A1 |
| 20190102384 | Hung et al. | Apr 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2005065368 | Jul 2005 | WO |
| 2008024539 | Feb 2008 | WO |
| 2011014830 | Feb 2011 | WO |
| 2012062385 | May 2012 | WO |
| 2012082726 | Jun 2012 | WO |
| 2013006708 | Jan 2013 | WO |
| 2013055538 | Apr 2013 | WO |
| 2013184134 | Dec 2013 | WO |
| 2014007811 | Jan 2014 | WO |
| 2014058411 | Apr 2014 | WO |
| 2014088537 | Jun 2014 | WO |
| 2015065350 | May 2015 | WO |
| 2015065355 | May 2015 | WO |
| 2015065356 | May 2015 | WO |
| 2015065359 | May 2015 | WO |
| 2015065368 | May 2015 | WO |
| 2015065370 | May 2015 | WO |
| 2015065374 | May 2015 | WO |
| 2015065382 | May 2015 | WO |
| 2015065389 | May 2015 | WO |
| 2015065392 | May 2015 | WO |
| Entry |
|---|
| GuanYu, Lin, Heat: OpenStack Orchestration, available online at <https://wiki.openstack.org/w/index.php?oldid=162872>, Jul. 18, 2018, 5 pages. |
| AWS, “AWS Cloud Formation” available online at <https://web.archive.org/web/20181230193715/https://aws.amazon.com/cloudformation/>, retrieved on Dec. 30, 2018, 14 pages. |
| Baryannis et al., “Lifecycle Management of Service-based Applications on Multi-Clouds: A Research Roadmap”, MultiCloud'13, Apr. 22, 2013, 8 pages. |
| BMC Software, “BMC Cloud Lifecycle Management: Managing Cloud Services from Request to Retirement,” Solution White Paper, 2011, 16 pages. |
| BMC Software, “BMC Cloud Management Functional Architecture Guide”, Technical White Paper, 2011, 14 pages. |
| ENTERASYS Secure Networks, “Enterasys Network Access Control: Executive Summary”, Network Access Control Whitepaper, 2008, 23 pages. |
| Extended European Search Report received for EP Patent Application No. 13896362 4, dated May 17, 2017, 10 pages. |
| Extended European Search Report received for EP Patent Application No. 13896706.2, dated Mar. 17, 2017, 8 pages. |
| Extended European Search Report received for EP Patent Application No. 13896252.7, dated May 12, 2017, 9 pages. |
| Extended European Search Report received for EP Patent Application No. 13896317.8, dated Apr. 25, 2017, 10 pages. |
| Extended European Search Report received for EP Patent Application No. 13896357.4, dated May 12, 2017, 9 pages. |
| Extended European Search Report received for EP Patent Application No. 13896441.6, dated May 23, 2017, 7 pages. |
| Extended European Search Report received for EP Patent Application No. 13896489.5, dated Mar. 22, 2017, 9 pages. |
| Extended European Search Report received for EP Patent Application No. 13896558.7, dated Aug. 10, 2017, 14 pages. |
| Extended European Search Report received for EP Patent Application No. 13896575.1, dated May 19, 2017, 9 pages. |
| Extended European Search Report received for EP Patent Application No. 13896812.8, dated May 2, 2017, 9 pages. |
| Extended European Search Report received for EP Patent Application No. 13896816.9, dated Aug. 2, 2017, 13 pages. |
| Github, “Provisioning and Managing a GP Instance”, available online at <https://github.com/globusonline/provision/blob/master/doc/instance_operations.rst>, 2012, 11 pages. |
| GLOBUS, “Provision Documentation 0.4.0”, available online at <https://web.archive.org/web/20130518090635/http://www.globus.org/provision/singlehtml/docs.html>, May 18, 2013, 66 pages. |
| IBM Cloud Education, “DevOps”, available online at <http://www-01.IBM.com/software/rational/devops/>, Oct. 2, 2019, 15 pages. |
| Maes, S. H., “Notice of Allowance issued in U.S. Appl. No. 15/028,728” dated Sep. 24, 2018; 7 pages. |
| Maes, S. H.; “3mo. Non-final office action” cited in U.S. Appl. No. 15/028,510 dated Feb. 16, 2018; 26 pages. |
| Nguyen et al., “Blueprint Template Support for Engineering Cloud-Based Services”, Oct. 2011, pp. 26-37. |
| Nguyen et al., “Blueprinting Approach in Support of Cloud Computing”, Future Internet, Mar. 21, 2012, vol. 4, No. 4, pp. 322-346. |
| Office Action received for European Application No. 13896252.7, dated Jul. 11, 2018, 5 pages. |
| Office Action received for European Application No. 13896357.4, dated Jul. 11, 2018, 5 pages. |
| Office Action received for European Application No. 13896362.4, dated Jul. 26, 2018, 5 pages. |
| Office Action received for European Application No. 13896489.5, dated Jul. 24, 2018, 5 pages. |
| Office Action received for European Application No. 13896706.2, dated Apr. 17, 2018, 5 pages. |
| Office Action received for European Application No. 13896816.9, dated Mar. 9, 2018, 9 pages. |
| Porus Homi Havewala, “Overview of Oracle Enterprise Manager Management Packs”, available online at <https://www.oracle.com/technical-resources/articles/enterprise-manager/oem-packs-overview.html>, Dec. 2010, 28 pages. |
| Radu Calinescu, “General-purpose Autonomic Computing,” (Research Paper), Sep. 8, 2008, pp. 1-25. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067397, dated Jul. 17, 2014, 13 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067406, dated Jul. 17, 2014, 13 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067414, dated Jul. 17, 2014, 10 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067423, dated Jul. 24, 2014, 11 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067492, dated Jul. 17, 2014, 11 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067513, dated Jul. 24, 2014, 11 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067542, dated Jul. 17, 2014, 11 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067439, dated Jul. 28, 2014, 8 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067531, dated Jul. 17, 2014, 10 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067570, dated Jul. 17, 2014, 11 pages. |
| Search Report and Written Opinion received for PCT Application No. PCT/US2013/067574, dated Jul. 23, 2014, 9 pages. |
| Srivastava et al., “A Comparison of Topology Control Algorithms for Ad-hoc Networks”, (Research Paper), 2003, 5 pages. |
| Stefanov et al., “Algorithmic transformation techniques for efficient exploration of alternative application instances”, Proc. 10th Int. Symposium on Hardware/Software Codesign (CODES'02), May 6-8, 2002, 6 pages. |
| U.S. Appl. No. 15/028,460, Final Rejection dated Jun. 15, 2018, pp. 1-11 and attachments. |
| U.S. Appl. No. 15/028,460, Non Final Rejection dated Nov. 3, 2017, pp. 1-9 and attachments. |
| Vmware, “Transform Your Datacenter Into an Agile Cloud”, available online at <http://www.vmware.com/uk/products/datacenter-virtualization/vcloud-suite/features html, 2013, 5 pages. |
| Waizenegger et al., “Policy 4TOSCA: A Policy-Aware Cloud Service Provisioning Approach to Enable Secure Cloud Computing”, 2013, pp. 360-376. |
| WSO2, “WSO2 App Factory,” available online at <https://web.archive.org/web/20190923015300/https://wso2.com/cloud/app-factory/>, retrieved on Sep. 23, 2019, 8 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20200169467 A1 | May 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15028466 | US | |
| Child | 16775218 | US |
