Abstract: Examples herein relate to identifying a soft failure at member within a cluster dedicated to a microservice. Examples disclose identifying a statistical evaluation for each member within the cluster. Based on the statistical evaluation, identifying a soft failure among one of multiple members within the cluster. In response to the identification of the soft failure at one of the members within the cluster, performing an action.

Abstract: Examples herein relate to identifying a soft failure at member within a cluster dedicated to a microservice. Examples disclose identifying a statistical evaluation for each member within the cluster. Based on the statistical evaluation, identifying a soft failure among one of multiple members within the cluster. In response to the identification of the soft failure at one of the members within the cluster, performing an action.

Abstract: Examples relate to cloud models based on network definition data. Some examples disclosed herein may enable obtaining first cloud definition data that describes a first cloud infrastructure. The first cloud definition data may comprise network definition data that describes a first server node to be included in the first cloud infrastructure and a first set of network interfaces to be enumerated on a bus of the first server node. Some examples may further enable generating a first cloud model based on the first cloud definition data. The first cloud model may comprise first cloud configuration data that, when executed, causes the first cloud infrastructure to be deployed. Some examples may further enable storing a first checkpoint image of the first cloud model. The first checkpoint image may comprise at least a portion of the first cloud configuration data.

Abstract: Examples disclosed herein relate to cloud images. The examples enable generating a first cloud image to configure a first node to serve a first role in a cloud infrastructure. The first cloud image comprising a first set of packages may be stored in a first local repository of the first cloud image. The examples further enable generating a second cloud image to configure a second node to serve a second role in the cloud infrastructure where the second cloud image comprises a second set of packages stored in a second local repository of the second cloud image. The examples further enable causing the first cloud image to be deployed to the first node in the cloud infrastructure and causing the second cloud image to be deployed to the second node in the cloud infrastructure.

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

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

Abstract: Examples relate to cloud models based on logical network interface data. Some examples disclosed herein may enable obtaining first cloud definition data that describes a first cloud infrastructure. The first cloud definition data may comprise logical network interface data that describes a first set of network interfaces to be bonded to form a first logical network interface for the first cloud infrastructure. Some examples further enable generating a first cloud model based on the first cloud definition data. The first cloud model may comprise first cloud configuration data that, when executed, causes the first cloud infrastructure to be deployed. Some examples further enable storing a first checkpoint image of the first cloud model. The first checkpoint image may comprise at least a portion of the first cloud configuration data.

Abstract: Examples disclosed herein relate to naming of cloud components. The examples enable generating, for a first node of a cloud infrastructure comprising a plurality of nodes, a first node name associated with a first fixed Internet Protocol (IP) address that is assigned to the first node, the first node name identifying the cloud infrastructure and a first control plane to which the first node belongs; generating, for a second node of the cloud infrastructure, a second node name associated with a second fixed IP address that is assigned to the second node, the second node name identifying the cloud infrastructure and a second control plane to which the second node belongs; and causing information related to the cloud infrastructure to be published to the plurality of nodes of the cloud infrastructure, the information related to the cloud infrastructure comprising the first node name and the second node name.

Abstract: Examples relate to cloud models based on network definition data. Some examples disclosed herein may enable obtaining first cloud definition data that describes a first cloud infrastructure. The first cloud definition data may comprise network definition data that describes a first server node to be included in the first cloud infrastructure and a first set of network interfaces to be enumerated on a bus of the first server node. Some examples may further enable generating a first cloud model based on the first cloud definition data. The first cloud model may comprise first cloud configuration data that, when executed, causes the first cloud infrastructure to be deployed. Some examples may further enable storing a first checkpoint image of the first cloud model. The first checkpoint image may comprise at least a portion of the first cloud configuration data.

Abstract: Examples relate to cloud models based on logical network interface data. Some examples disclosed herein may enable obtaining first cloud definition data that describes a first cloud infrastructure. The first cloud definition data may comprise logical network interface data that describes a first set of network interfaces to be bonded to form a first logical network interface for the first cloud infrastructure. Some examples further enable generating a first cloud model based on the first cloud definition data. The first cloud model may comprise first cloud configuration data that, when executed, causes the first cloud infrastructure to be deployed. Some examples further enable storing a first checkpoint image of the first cloud model. The first checkpoint image may comprise at least a portion of the first cloud configuration data.

Abstract: Examples disclosed herein relate to naming of cloud components. The examples enable generating, for a first node of a cloud infrastructure comprising a plurality of nodes, a first node name associated with a first fixed Internet Protocol (IP) address that is assigned to the first node, the first node name identifying the cloud infrastructure and a first control plane to which the first node belongs; generating, for a second node of the cloud infrastructure, a second node name associated with a second fixed IP address that is assigned to the second node, the second node name identifying the cloud infrastructure and a second control plane to which the second node belongs; and causing information related to the cloud infrastructure to be published to the plurality of nodes of the cloud infrastructure, the information related to the cloud infrastructure comprising the first node name and the second node name.

Abstract: Examples disclosed herein relate to cloud images. The examples enable generating a first cloud image to configure a first node to serve a first role in a cloud infrastructure. The first cloud image comprising a first set of packages may be stored in a first local repository of the first cloud image. The examples further enable generating a second cloud image to configure a second node to serve a second role in the cloud infrastructure where the second cloud image comprises a second set of packages stored in a second local repository of the second cloud image. The examples further enable causing the first cloud image to be deployed to the first node in the cloud infrastructure and causing the second cloud image to be deployed to the second node in the cloud infrastructure.

Abstract: Examples relate to cloud models. The examples disclosed herein enable obtaining first cloud definition data that describe a first cloud infrastructure. A first cloud model may be generated based on the first cloud definition data. The first cloud model may comprise first cloud configuration data that, when executed, cause the first cloud infrastructure to be deployed. The examples further enable storing a first checkpoint image of the first cloud model. The first checkpoint image may comprise at least a portion of the first cloud definition data and the first cloud configuration data.

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

Abstract: Automated cloud set up may include collecting compute resources available for setting up a cloud, identifying packages available to apply to the compute resources, and determining which subsets of the packages to apply to which compute resource.

Abstract: Automated cloud set up may include collecting compute resources available for setting up a cloud, identifying packages available to apply to the compute resources, and determining which subsets of the packages to apply to which compute resource.

Abstract: Building a realized topology with a binding document includes generating a binding document based on user input, assigning values to the binding document, and building a realized topology based on the binding document such that a user interface to the realized topology is tied to the binding document and is independent of a cloud.

Abstract: Automated cloud set up may include collecting compute resources available for setting up a cloud, identifying packages available to apply to the compute resources, and determining which subsets of the packages to apply to which compute resource.

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

Abstract: An enterprise component-based software development system includes a component platform with a number of development tools and services that enable rapid and straightforward development of component-based systems. The component platform describes a middle tier architecture for a multi-tier, multi-user application. It defines the services and facilities as well as the structure in which components can execute. It helps to provide an extensible platform for the construction, management and execution of component-based software. A messaging platform facilitates communication between different computers. When a component requests a service from another component, the request is serialized and encoded into a platform-independent language such as XML. The XML-encoded message is transmitted over the Internet using an HTTP protocol to a receiving computer, which validates the message and delivers it to the component providing the requested service.