Abstract: Techniques are provided for performing server device updates using update baselines that are tagged across multiple management consoles. One method comprises obtaining, by a first management console of multiple management consoles associated with a server device, a first update baseline comprising a first tag identifier, of multiple tag identifiers, that identifies a first update of a component of the server device across the multiple management consoles; and applying the first update baseline to the server device in a maintenance mode to update the component of the server device, wherein the server device is maintained in the maintenance mode when two or more of the tag identifiers are active in the server device following the application of the first update baseline. The server device can be restored from the maintenance mode when only one tag identifier is active in the server device following the application of the first update baseline.

Abstract: A system update appliance includes a processor and a memory device with a Content Addressable Storage (CAS) space and a location addressable storage space. The location addressable storage space partitioned into an object storage space and a device storage space. The processor stores a device entry in the device storage space. The device entry is associated with a device external to the system update appliance and includes a component entry for a component of the device. The component operates based on an update. The component entry includes a description of the component and a pointer to a record stored in the CAS space. The processor stores the record in the CAS space. The record is associated with a combination of the component and the first update. The record includes the description, a second pointer to an update repository, and a third pointer to the object storage space.

Abstract: A module optimizes active and inactive components and resources of a hybrid computing system to optimize a combination of private and public resources to minimize cost and maximize performance of the hybrid computing system. A learning model may analyze past usage and present usage metrics of one or more components with respect to performance criteria or cost criteria. Cost factors associated with components of the private system may be based on wear—the higher the wear the less desirable a component's use becomes due to lower reliability and higher warranty costs. When activating a component of the private system, a deactivation of a higher wear component may be delayed allowing time for a recently activated component to be integrated with the private system. A resource of a public system may be used while deactivation of a high wear component is delayed.

Abstract: Techniques are provided for semantic-aware workflow creation and execution. One method comprises obtaining a semantic-aware workflow; identifying objects specified in the semantic-aware workflow; performing the following steps for at least one of the identified objects: extracting parameters corresponding to the at least one identified object using an attribute registry associated with the semantic-aware workflow; selecting, using the attribute registry, an extracted parameter that takes, as a value, another identified object; and adding an operation to the semantic-aware workflow using the at least one identified object, and the corresponding selected extracted parameter that takes, as a value, the other identified object.

Abstract: Techniques are provided for identifying and mitigating security vulnerabilities in multi-layer infrastructure stacks. One method comprises obtaining vulnerability information associated with a security vulnerability for a component in a server device, wherein the server device is associated with a multi-layer infrastructure stack, and wherein the vulnerability information is obtained from a vulnerability catalog that identifies the security vulnerability for the component; exchanging at least portions of the vulnerability information among at least some layers of the multi-layer infrastructure stack; identifying a remedial action to mitigate the security vulnerability using an update catalog that identifies a remedial action for the component to mitigate a corresponding security vulnerability; and automatically initiating the remedial action.

Abstract: Techniques are provided for performing server device updates using update baselines that are tagged across multiple management consoles. One method comprises obtaining, by a first management console of multiple management consoles associated with a server device, a first update baseline comprising a first tag identifier, of multiple tag identifiers, that identifies a first update of a component of the server device across the multiple management consoles; and applying the first update baseline to the server device in a maintenance mode to update the component of the server device, wherein the server device is maintained in the maintenance mode when two or more of the tag identifiers are active in the server device following the application of the first update baseline. The server device can be restored from the maintenance mode when only one tag identifier is active in the server device following the application of the first update baseline.

Abstract: Techniques are provided for generating multi-layer configuration templates for deployment across multiple infrastructure stack layers.

Abstract: A deployment manager includes storage for storing a state repository including a state transitions associated with event descriptions generated by a computing device and a computing device manager. The computing device manager obtains a new event description associated with the computing device, and a workload performed by the computing device; in response to obtaining the new event description: matches the new event description to a state transition of the state transitions; and manages the workload based on a predicted next state associated with the state transition.

Abstract: A system update appliance includes a processor and a memory device with a Content Addressable Storage (CAS) space and a location addressable storage space. The location addressable storage space partitioned into an object storage space and a device storage space. The processor stores a device entry in the device storage space. The device entry is associated with a device external to the system update appliance and includes a component entry for a component of the device. The component operates based on an update. The component entry includes a description of the component and a pointer to a record stored in the CAS space. The processor stores the record in the CAS space. The record is associated with a combination of the component and the first update. The record includes the description, a second pointer to an update repository, and a third pointer to the object storage space.

Abstract: A system update appliance includes a processor and a memory device with a Content Addressable Storage (CAS) space and a location addressable storage space. The location addressable storage space partitioned into an object storage space and a device storage space. The processor stores a device entry in the device storage space. The device entry is associated with a device external to the system update appliance and includes a component entry for a component of the device. The component operates based on an update. The component entry includes a description of the component and a pointer to a record stored in the CAS space. The processor stores the record in the CAS space. The record is associated with a combination of the component and the first update. The record includes the description, a second pointer to an update repository, and a third pointer to the object storage space.

Abstract: A system update appliance includes a processor and a memory device with a Content Addressable Storage (CAS) space and a location addressable storage space. The location addressable storage space partitioned into an object storage space and a device storage space. The processor stores a device entry in the device storage space. The device entry is associated with a device external to the system update appliance and includes a component entry for a component of the device. The component operates based on an update. The component entry includes a description of the component and a pointer to a record stored in the CAS space. The processor stores the record in the CAS space. The record is associated with a combination of the component and the first update. The record includes the description, a second pointer to an update repository, and a third pointer to the object storage space.

Abstract: An information handling system determines zones within a datacenter that exhibit poor component life. Components of the information handling system provide error indications and have error thresholds and warranty durations. The components organized into zones.

Abstract: A deployment manager includes storage for storing a state repository including a state transitions associated with event descriptions generated by a computing device and a computing device manager. The computing device manager obtains a new event description associated with the computing device, and a workload performed by the computing device; in response to obtaining the new event description: matches the new event description to a state transition of the state transitions; and manages the workload based on a predicted next state associated with the state transition.

Abstract: A deployment consistency orchestrator includes storage for storing a manual update practice repository and a deployment characteristics repository. The orchestrator further includes an automated update practices manager that identifies a change in update practice event for a deployment; in response to identifying the change in update practice event: identifies, using the deployment characteristics repository, a portion of deployments having a classification that is similar to a classification of the deployment; identifies a portion of the manual update practices repository associated with the portion of the deployments; performs a commonality analysis using the portion of the manual update practices to identify consistent update practices associated with the classification of the deployment; and enforces the consistent update practices associated with the classification on the deployment.

Abstract: An information handling system determines zones within a datacenter that exhibit poor component life. Components of the information handling system are organized into zones, and provide error indications and have error thresholds and warranty durations. A component life manager receives the error indications, fits the error indications to curves, determines end of life estimates based upon the curves and the error thresholds, determines end of life dates based upon the end of life estimates and dates that the first error indication is received, determines losses of life based on the end of life estimates and the warranty durations, determines component life scores based upon the losses of life and the warranty durations, determines zone life scores based upon an average of the component life scores, determines a datacenter life score based upon an average of the component life scores, and provides an indication when a zone life score is below the datacenter life score by more than a threshold.

Abstract: An information handling system includes a component and a component life manager. The component provides error indications associated with aging of the component, and has a predefined error threshold and a predefined warranty duration. The component life manager receives the error indications, fits the received error indications to a curve, determines an end of life estimate based upon the curve and the error threshold, determines an end of life date based upon the end of life estimate and a date that the first error indication is received, determines a loss of life based on the end of life estimate and the warranty duration, and determines a component life score for the component.

Abstract: A method and data processing device for detecting connection of a second device at an interface of an IHS. The method includes receiving a request to modify at least one secure functionality associated with the IHS, the request comprising identification input. The method includes generating security credentials that correspond to a predetermined level of security that is assigned to the identification input. The method includes triggering the service processor to establish a secure communication link to the second device for communicatively connecting a digitally generated keyboard. The method includes autonomously inputting the security credentials to the digitally generated keyboard. The method includes signaling to the digitally generated keyboard to write the security credentials to the second device for use to obtain access to the IHS according to the predetermined level of security.

Abstract: An information handling system includes a component and a component life manager. The component provides error indications associated with aging of the component, and has a predefined error threshold and a predefined warranty duration. The component life manager receives the error indications, fits the received error indications to a curve, determines an end of life estimate based upon the curve and the error threshold, determines an end of life date based upon the end of life estimate and a date that the first error indication is received, determines a loss of life based on the end of life estimate and the warranty duration, and determines a component life score for the component.

Abstract: An information handling system determines zones within a datacenter that exhibit poor component life. Components of the information handling system provide error indications and have error thresholds and warranty durations. The components organized into zones.

Abstract: An information handling system determines zones within a datacenter that exhibit poor component life. Components of the information handling system are organized into zones, and provide error indications and have error thresholds and warranty durations. A component life manager receives the error indications, fits the error indications to curves, determines end of life estimates based upon the curves and the error thresholds, determines end of life dates based upon the end of life estimates and dates that the first error indication is received, determines losses of life based on the end of life estimates and the warranty durations, determines component life scores based upon the losses of life and the warranty durations, determines zone life scores based upon an average of the component life scores, determines a datacenter life score based upon an average of the component life scores, and provides an indication when a zone life score is below the datacenter life score by more than a threshold.