A processing system comprises a first subsystem comprising at least one host processor and one or more storage units, and a second subsystem comprising at least one second processor. Each second processor comprises a plurality of tiles. Each tile comprises a processing unit and memory. At least one storage unit stores bootloader code for each of first and second subsets of the plurality of tiles of at least one second processor. The first subsystem writes bootloader code to each of the first subset of tiles of the at least one second processor. At least one of the first subset of tiles requests at least one of the storage units to return the bootloader code to the second subset of the plurality of tiles. Each tile to which the bootloader code is written retrieves boot code from the storage unit and then runs said boot code.

Bootstrapping a microservices container registry. A computing system node receives an installation package. The receiving computing system node bootstraps an initial invocation of the microservice by first installing a local container registry from the installation package and then by installing the microservice from the installation package. The installation package contains additional components that can be extracted, installed and invoked by executing the microservice at the computing system node after extracting from the local container registry. The installation package is generated by any node of the computing system and contains code corresponding to infrastructure microservices that are installed before invoking microservices that depend on the infrastructure. Temporary domain name services are installed from the installation package at a node-local IP address. The temporary domain name services are switched over to a different domain name service at a different IP address. A second computing system node is designated as a failover node.

A system for controlling a processor, comprising a processor configured to load one or more instructions into a register for execution, a non-volatile memory coupled to the processor and configured to store data in a format that can be read by the processor and a description file stored in the non-volatile memory, the description file further comprising a plurality of information files, wherein each information file includes two or more types of predetermined data.

A network initialization monitoring system includes a host device coupled to a storage system and a monitoring system via a network, and including an initialization subsystem coupled to ports. During network initialization of the host device via the storage system, the initialization subsystem provides a first instance of a communication protocol for monitored port(s), and provides a second instance of the communication protocol for a monitoring port. During the network initialization of the host device via the storage system, the first instance of the communication protocol provided for each monitored port provides copies of network initialization communications transmitted via that monitored port and the network to the second instance of the communication protocol provided for the monitoring port, and the second instance of the communication protocol provided for the monitoring port provides the copies of the network initialization communications to the monitoring system.

A processor may detect a risk on a local machine. The processor may determine that the risk warrants a heightened-level remediation. The processor may connect the local machine to a cloud-based desktop environment. The processor may perform the heightened-level remediation on the local machine. The processor may merge data from the cloud-based desktop environment to the local machine in response to the heightened-level remediation being performed.

Systems, apparatuses, and methods related to a hypervisor status register in a computer processor are described. For example, a memory coupled to the computer processor can store instructions of routines of predefined, non-hierarchical domains. The computer processor can store a value in the hypervisor status register during a power up process of the computer system. The value stored in the hypervisor status register that identifies whether or not an operating hypervisor is present in the computer system. The computer processor can configure its operations (e.g., address translation) based on the value stored in the hypervisor status register.

A system, method, and computer-readable medium are disclosed for performing a customer operating system installation operation. The customer operating system installation operation includes performing a customer operating system installation operation onto an information handling system, comprising: performing a customer operating system installation operation; and, performing a UEFI boot entry operation, the UEFI boot entry operation accessing a UEFI boot entry when performing the customer operating system installation operation, the UEFI boot entry operation providing a communication abstraction between a manufacturing operating system and the customer operating system.

Systems and methods for performing security event mitigation with firmware are discussed. A firmware-based security event framework receives notifications of security events occurring in a firmware-controlled operating environment on a computing platform, logs information related to the event and optionally performs mitigation operations to address the security event.

In one or more embodiments, one or more systems, one or more methods, and/or one or more processes may determine that the staged job needs to be executed by a baseboard management controller (BMC) while an information handling system (IHS) is held in a power-on self-test; create a hybrid job associated with the staged job; reboot the IHS; launch an IHS firmware application in a pre-boot IHS firmware environment; provide, to the BMC, a command to execute a first portion of the hybrid job; obtain, by the BMC, an authentication key; provide, by the BMC, the authentication key to the non-volatile storage device; execute, by the BMC, the first portion of the hybrid job to configure the non-volatile storage device; and execute, by the IHS firmware application, the second portion of the hybrid job to poll the baseboard management controller for a result status of configuring the non-volatile storage device.

A method includes automatically configuring a cluster using pre-defined templates of one or more servers positioned in an edge location. The method also includes creating a plurality of configuration profile templates. The method also includes obtaining one or more parameter values. The method also includes defining a plurality of parameters in each of the plurality of configuration profile templates based upon the one or more parameter values obtained. The method also includes creating a master template based on the plurality of configuration profile templates. The method also includes storing the master template in a repository. The method also includes automatically creating a planned inventory file based on the master template. The method also includes configuring the cluster of the one or more servers based on the planned inventory.