Technologies for providing manifest-based asset representation

Abstract

Technologies for generating manifest data for a sled include a sled to generate manifest data indicative of one or more characteristics of the sled (e.g., hardware resources, firmware resources, a configuration of the sled, or a health of sled components). The sled is also to associate an identifier with the manifest data. The identifier uniquely identifies the sled from other sleds. Additionally, the sled is to send the manifest data and the associated identifier to a server. The sled may also detect a change in the hardware resources, firmware resources, the configuration, or component health of the sled. The sled may also generate an update of the manifest data based on the detected change, where the update specifies the detected change in the hardware resources, firmware resources, the configuration, or component health of the sled. The sled may also send the update of the manifest data to the server.

1 . A sled, comprising:
 a compute engine to:
 generate manifest data indicative of one or more characteristics of the sled; 
 associate an identifier with the manifest data, wherein the identifier identifies the sled from each of a plurality of sleds; and 
 send the manifest data and the associated identifier to an orchestrator server. 
   
     
     
         2 . The sled of  claim 1 , wherein the compute engine is further to:
 detect a change in at least one or more of the characteristics of the sled;   update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the sled; and   send the update of the manifest data to the orchestrator server.   
     
     
         3 . The sled of  claim 2 , wherein to update the manifest data comprises to:
 determine which of the manifest data to update based on the change; and   modify the determined manifest data based on the change.   
     
     
         4 . The sled of  claim 2 , wherein the change is at least one of an addition of a first resource or a removal of a second resource. 
     
     
         5 . The sled of  claim 2 , wherein the update sent to the orchestrator server is an indication of the change to the manifest data. 
     
     
         6 . The sled of  claim 1 , wherein the manifest data includes at least one hardware manifest, firmware manifest, configuration manifest, or health manifest. 
     
     
         7 . The sled of  claim 7 , wherein the hardware manifest specifies at least one of a processor count, a processor model, dual in-line memory module (DIMM) types, population locations, capacity, or I/O devices. 
     
     
         8 . The sled of  claim 7 , wherein the firmware manifest specifies at least one of a BIOS version, baseboard management controller (BMC) version, DIMM firmware version, or solid state drive (SSD) version. 
     
     
         9 . The sled of  claim 7 , wherein the configuration manifest of the sled comprises at least one of an indication of whether an ability to operate a processor core as multiple virtual cores is enabled, a DIMM speed setting, a CPU core frequency, or a boot device order. 
     
     
         10 . The sled of  claim 7 , wherein to generate the manifest data indicative of the one or more characteristics of the sled comprises to:
 determine hardware resources and firmware resources present in the sled;   determine a configuration of the sled;   determine a health of the hardware resources of the sled; and   create the hardware manifest based on the hardware resources present, the firmware manifest based on the firmware resources present, the configuration manifest based on the determined configuration, and the health manifest based on the health of the hardware resources of the sled.   
     
     
         11 . The sled of  claim 7 , wherein to associate the identifier with the manifest data comprises to:
 determine a first identifier for the hardware manifest, a second identifier for the firmware manifest, and a third identifier for the configuration manifest; and   tag the first identifier to the hardware manifest, the second identifier to the firmware manifest, and the third identifier to the configuration manifest.   
     
     
         12 . The sled of  claim 1 , wherein to send the manifest data and the associated identifier comprises to send the manifest data and the associated identifier in response to a request from the orchestrator server for the manifest data. 
     
     
         13 . The sled of  claim 1 , wherein the system includes a node comprising at least the sled, wherein the node is composed based, in part, on the manifest data and wherein the compute engine is further to generate the manifest data for the composed node. 
     
     
         14 . One or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a sled to:
 generate manifest data indicative of one or more characteristics of the sled, wherein the sled is one of a plurality of sleds in a system;   associate an identifier with the manifest data, wherein the identifier identifies the sled from each of the plurality of sleds; and   send the manifest data and the associated identifier to an orchestrator server.   
     
     
         15 . The one of more machine-readable storage media of  claim 14 , wherein the plurality of instructions, when executed, further cause the sled to:
 detect a change in at least one or more of the characteristics of the sled;   update the manifest data based on the detected change, wherein the update specifies the detected change in the one or more characteristics of the sled; and   send the update of the manifest data to the orchestrator server.   
     
     
         16 . The one of more machine-readable storage media of  claim 15 , wherein the update sent to the orchestrator server is an indication of the change to the manifest data. 
     
     
         17 . The one of more machine-readable storage media of  claim 14 , wherein the manifest data includes at least one hardware manifest, a firmware manifest, configuration manifest, or health manifest. 
     
     
         18 . The one of more machine-readable storage media of  claim 17 , wherein the hardware manifest specifies at least one of a processor count, a processor model, dual in-line memory module (DIMM) types, population locations, capacity, or I/O devices, wherein the firmware manifest specifies at least one of a BIOS version, baseboard management controller (BMC) version, DIMM firmware version, or solid state drive (SSD) version, and wherein the configuration manifest of the sled comprises at least one of an indication of whether an ability to operate a processor core as multiple virtual cores is enabled, a DIMM speed setting, a CPU core frequency, or a boot device order. 
     
     
         19 . The one of more machine-readable storage media of  claim 17 , wherein to generate the manifest data indicative of the one or more characteristics of the sled comprises to:
 determine hardware resources and firmware resources present in the sled;   determine a configuration of the sled; and   create the hardware manifest based on the hardware resources present, the firmware manifest based on the firmware resources present, and the configuration manifest based on the determined configuration.   
     
     
         20 . The one of more machine-readable storage media of  claim 17 , wherein to associate the at least the identifier with the manifest data comprises to:
 determine a first identifier for the hardware manifest, a second identifier for the firmware manifest, and a third identifier for the configuration manifest; and   tag the first identifier to the hardware manifest, the second identifier to the firmware manifest, and the third identifier to the configuration manifest.