Abstract: A distributed LCS configuration system includes a BMS with a processing/memory system providing a microvisor including a microvisor agent, and a BMS SCP device including a BMS SCP agent. A resource SCP device is coupled to a resource device and includes a resource SCP agent. A resource management system coupled to the BMS and the resource SCP device includes a resource management agent. The resource management system composes an LCS based on a workload intent using the processing/memory system and the resource device, provides LCS resource configuration information to the resource SCP agent, and provides LCS configuration information to the BMS SCP agent. The BMS SCP agent then configures the first resource device with the first resource SCP agent using the LCS first resource configuration information, and configures the processing/memory system with a microvisor agent using the LCS configuration information to provide the LCS that operates with the resource device.

Abstract: A Logically Composed System (LCS) resource device functionality provisioning system includes an orchestrator device coupled to resource devices and a resource management system. The orchestrator device identifies functionality available from the resource devices via at least one resource device communication protocol, and advertises logical functions that correspond to the functionality available from the resource devices to the resource management system via a resource management system communication protocol that is different than the at least one resource device communication protocol. When the orchestrator device receives a request from the resource management system via the resource management system communication protocol to utilize a subset of the logical functions to provide an LCS, it configures the subset of the logical functions to provide the LCS via the at least one resource device communication protocol, and provides the LCS to a client device using the subset of the logical functions.

Abstract: Methods and systems for managing a data processing system are disclosed. Based on an occurrence of a power management event for the data processing system, the data processing system may use a multi-function connection to exchange power information with a power distribution unit (PDU) that supplies power to the data processing system via the multi-function connection. Using the power information, a power management process may be performed to obtain a new powered state for the data processing system. The new powered state may be enforced on hardware resources of the data processing system to obtain an updated processing system usable for providing computer-implemented services.

Abstract: Methods and systems for managing a data processing system are disclosed. The data processing system may obtain first power from a power distribution unit (PDU) via a multi-function connection. Based on a magnitude of the first power, a validation process may need to be performed before other power is made available to the data processing system from the PDU. During the validation process, the data processing system may, via the multi-function connection, provide identification information to and receive a response from the PDU. The response may indicate characteristics of power that the PDU believes is warranted for the data processing system based on the identification information. The data processing system may be placed in a new power state based on the characteristics of the power in order to provide computer-implemented services.

Abstract: Methods and systems for managing a data processing system are disclosed. A power distribution unit (PDU) may supply power to the data processing system via a multi-function connection adapted to facilitate communication between the data processing system and the PDU. Based on an identification of an occurrence of a power budgeting event for the data processing system, the data processing system may use the multi-function connection to provide a power cap request to the PDU, and to obtain a response to the power cap request from the PDU. The response may be based on a mapping of a power distribution system that includes the PDU, and the response may indicate a new power state for the data processing system. The data processing system may enforce the power state on at least hardware resources of the data processing system in order to provide computer-implemented services.

Abstract: Methods and systems for managing a data processing system are disclosed. The data processing system (DPS) may identify that a power distribution unit (PDU) is operably connected via a multi-function connection adapted to both supply power to the DPS and facilitate communication between the DPS and the PDU. The DPS may identify a pairing state for the PDU that indicates whether the PDU is paired or unpaired. If the PDU is unpaired, a pairing process may be performed to attempt to change the pairing state for the PDU to paired. If the pairing state for the PDU is changed to paired, then a new power state for the DPS may be collaboratively enforced by the DPS with the PDU to obtain an updated DPS. The updated DPS may provide a computer-implemented service.

Abstract: A Logically Composed System (LCS) life-cycle management system includes an orchestrator device coupled to resource devices. The orchestrator device configures the resource devices to provide an LCS to a client device. The orchestrator device also identifies interdependencies between the resource devices and, based on those interdependencies, determines life-cycle management operations available for the LCS and presents the life-cycle management operations to the client device. When the orchestrator device receives a request to perform a first life-cycle management operation on the LCS, it performs the first life-cycle management operation on the first LCS based on the interdependencies identified between the resource devices.

Abstract: A secure LCS provisioning system includes a resource system coupled to a resource management system and including a resource system operating system and an SCP device. The SCP device receives LCS initialization information for an LCS from the resource management system and provides it to the resource system operating system. The SCP device also receives vTPM information for the LCS from the resource management system and uses it to provide an LCS vTPM for the LCS in a secure SCP storage subsystem. The SCP device then provides a secure communication channel between the resource system operating system and the secure SCP storage subsystem, and identifies a location of the LCS vTPM in the secure SCP storage subsystem to the resource system operating system, allowing the resource system operating system to access the LCS vTPM and use it with the LCS initialization information to provide an LCS.

Abstract: A workload resource device Service Level Agreement (SLA) failure remediation system includes a resource management system coupled to resource devices. The resource management system receives a workload intent for performing a workload associated with SLA(s), and generates a Directed Acyclic Graph (DAG) that identifies a first resource device and second resource device(s) for performing the workload. Based on the DAG, the resource management system configures the first resource device and the second resource device(s) to perform the workload, and stores the DAG in at least one database. If the resource management system determines that the first resource device is not satisfying the SLA(s) during the performance of the workload, it uses s portion of the DAG associated with the first resource device to configure at least one of the resource devices to operate with the second resource device(s) to subsequently perform the workload such that the SLA(s) are satisfied.

Abstract: A workload resource device Service Level Agreement (SLA) failure remediation system includes a resource management system coupled to resource devices. The resource management system receives a workload intent for performing a workload associated with SLA(s), and generates a Directed Acyclic Graph (DAG) that identifies a first resource device and second resource device(s) for performing the workload. Based on the DAG, the resource management system configures the first resource device and the second resource device(s) to perform the workload, and stores the DAG in at least one database. If the resource management system determines that the first resource device is not satisfying the SLA(s) during the performance of the workload, it uses a portion of the DAG associated with the first resource device to configure at least one of the resource devices to operate with the second resource device(s) to subsequently perform the workload such that the SLA(s) are satisfied.

Abstract: A workload Service Level Agreement (SLA) satisfaction system includes a resource management system that is coupled to a client device and each of a plurality of resource devices. The resource management system receives a workload intent that identifies workload capabilities of a first workload, generates a Directed Acyclic Graph (DAG) that maps the workload capabilities to a first subset of the plurality of resource devices that are configured to provide the workload capabilities and to Service Level Agreement (SLA) monitoring functionality, configures the first subset of the plurality of resource devices to perform the first workload and report SLA information according to the SLA monitoring functionality, and configures an SLA monitoring subsystem based on the SLA monitoring functionality to receive the SLA information during performance of the first workload by the first subset of the plurality of resource devices, and perform a management operation based on the SLA information.

Abstract: A workload provisioning system includes a resource management system coupled to a client device and resource devices. The resource management system retrieves respective resource capability information and a respective resource/workload configuration template from each resource device. The resource management system then receives a workload intent from the client device with workload intent tag(s) defining respective workload capabilities desired for a workload, and uses it with the respective resource capability information to identify a subset of the resource devices to provide the respective workload capabilities.

Abstract: A workload-intent-based LCS resource capability configuration system includes a resource management system coupled to resource devices. The resource management system receives a request to provide an LCS that includes workload intent identifying requirements of a workload the LCS will perform, and identifies a subset of the resource devices for providing the LCS to perform the workload. The resource management system then determines resource capabilities required from the subset of the resource devices to satisfy the workload intent, determines driver(s) required for the subset of the resource devices, and provides configuration information for driver(s) that is configured to limit driver-enabled capabilities available from the driver(s) for the subset of the resource devices to the resource capabilities required from the subset of the resource devices to satisfy the workload intent. The resource management system then provides the driver(s) for the subset of the resource devices.

Abstract: A Logically Composed System (LCS) resource policy enforcement system includes resource devices coupled to an LCS provisioning administrator device, a client system, and an orchestrator device coupled to the resource devices and the client system. The orchestrator device uses a first subset of the resource devices to provide an LCS to the client system based on a workload intent provided by the client system, associates the LCS with a client identifier for the client system, and tags each of the first subset of the resource devices being used to provide the LCS with the client identifier. The orchestrator device then identifies a LCS policy for the LCS and applies the LCS policy to each of the first subset of the resource devices tagged with the client identifier to cause the LCS policy to be enforced on the client system and the LCS provisioning administrator device.

Abstract: Techniques described herein relate to a method for instantiating composed information handling systems. The method includes obtaining, by a system control processor manager, a composition request to instantiate a composed information handling system; in response to obtaining the composition request: identifying at least one compute resource set having computing resources specified by the composition request; identifying at least one hardware resource set having the hardware resources specified by the composition request; setting up management services based on plugin requirements associated with the composition request using an at least one control resource set; and initiating the instantiation of the composed information handling system using the management services.

Abstract: A Logically Composed System (LCS) resource policy enforcement system includes resource devices coupled to an LCS provisioning administrator device, a client system, and an orchestrator device coupled to the resource devices and the client system. The orchestrator device uses a first subset of the resource devices to provide an LCS to the client system based on a workload intent provided by the client system, associates the LCS with a client identifier for the client system, and tags each of the first subset of the resource devices being used to provide the LCS with the client identifier. The orchestrator device then identifies a LCS policy for the LCS and applies the LCS policy to each of the first subset of the resource devices tagged with the client identifier to cause the LCS policy to be enforced on the client system and the LCS provisioning administrator device.

Abstract: A Logically Composed System (LCS) resource device functionality provisioning system includes an orchestrator device coupled to resource devices and a resource management system. The orchestrator device identifies functionality available from the resource devices via at least one resource device communication protocol, and advertises logical functions that correspond to the functionality available from the resource devices to the resource management system via a resource management system communication protocol that is different than the at least one resource device communication protocol. When the orchestrator device receives a request from the resource management system via the resource management system communication protocol to utilize a subset of the logical functions to provide an LCS, it configures the subset of the logical functions to provide the LCS via the at least one resource device communication protocol, and provides the LCS to a client device using the subset of the logical functions.

Abstract: A Logically Composed System (LCS) life-cycle management system includes an orchestrator device coupled to resource devices. The orchestrator device configures the resource devices to provide an LCS to a client device. The orchestrator device also identifies interdependencies between the resource devices and, based on those interdependencies, determines life-cycle management operations available for the LCS and presents the life-cycle management operations to the client device. When the orchestrator device receives a request to perform a first life-cycle management operation on the LCS, it performs the first life-cycle management operation on the first LCS based on the interdependencies identified between the resource devices.

Abstract: Restore operations in containerized environments are disclosed. An ephemeral instance of an application is created and a datastore is mounted to the ephemeral instance. The ephemeral instance is not accessible to users or application. The backup data is restored to the datastore. Once restored, the datastore is then mounted to a production instance and production resumes.

Abstract: Restore operations in containerized environments are disclosed. An ephemeral instance of an application is created and a datastore is mounted to the ephemeral instance. The ephemeral instance is not accessible to users or application. The backup data is restored to the datastore. Once restored, the datastore is then mounted to a production instance and production resumes.