Hewlett Packard Enterprise Development LP

Hewlett-packard Development Company, L.P.

Mark Perreira

Bryan P Murray

Jayashree Sundarachar Beltur

Jeffrey Joel Walls

Stephane Herman Maes

Rajeev Bharadhwaj

Mark Potts

Scott Wulf

Haris Rasheed Farooqui

David Stanton

Vijay Misra

Sameer Vaidya

Examples described herein relate to providing pool-based automated lifecycle management of infrastructure via abstracted resources. According to an example, a consumption model is maintained in which heterogeneous infrastructure is represented in a generalized form as logical resource objects, including nodes and pools of the nodes. The nodes have respective node roles indicative of specific functionality the nodes are operable to provide to a workload based on the respective attributes/qualities of the nodes. A state model is maintained through which the logical resource objects are transitioned among states and responsive to which notifications are provided to an application orchestration tool associated with the workload. Interactions by the application orchestration tool with heterogeneous infrastructure utilized by the workload are abstracted by providing an API through which requests to manage a lifecycle of the heterogeneous infrastructure are expressed with reference to the logical resource objects.

Lifecycle management for workloads on heterogeneous infrastructure

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.

Identification of a soft failure at a member

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.

Cloud models based on network definition data

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.

Cloud images

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.

Orchestrating hybrid cloud services

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.

Asynchronous framework for management of IaaS

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.

Cloud models based on logical network interface data

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.

Naming of cloud components

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.

Automated cloud set up

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. Since XML is a platform and architecture independent language, requests processed in this way can be used by a wide variety of disparate systems.

Growing community of inventors

Sunnyvale, CA, United States of America

Mark Perreira