Merge branch 'NFVSOL(26)000052_SOL026_Clause_5_Inventory_related_object_mapping' into 'main'

|-|-|-|

|ResourceBlock|/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}|Represents a resource block, its components and affinity to composed devices.|

### 5.3.4 NFVI-PoP object

Table 5.3.4-1 lists down the Redfish® objects that map to the NFVI-PoP information model specified as NfviPopInfo in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1). Since the NFVI-PoP information model contains a lot of information about various aspects of physical resources in the NFVI, a combination of Redfish objects is needed to provide the corresponding information. 

**Table 5.3.4-1: Redfish&reg; resource objects mapped to NFV's NFVI-PoP information model**<a name="table_5.3.4-1"></a>

|Redfish® resource object|Redfish® resource URI|Redfish® resource object description|

|-|-|-|

|Chassis Collection|/redfish/v1/Chassis|Represents a collection of all the available chassis managed by the Redfish® service. Each chassis is represented by the Chassis schema in the Redfish® data model. The Chassis schema represents the sheet-metal confined spaces and logical zones such as racks, enclosures, chassis and all other containers. It also contains information about thermal subsystems, fans, sensors, power supplies, and information about computer systems contained within said Chassis, equipment related to compute, network, storage hardware resources, etc. |

|Systems Collection|/redfish/v1/Systems|Represents a collection of all the available systems managed by the Redfish® service. Each system is represented by the ComputerSystem schema in the Redfish® data model, which contains information about the computer system itself as well as its various subsystems, such as memory, CPU, storage and network devices that make up said computer system.|

|Managers Collection|/redfish/v1/Managers|Represents a collection of all the available managers in the Redfish® service. Each manager is represented by the Manager schema in the Redfish® data model, which contains information about the firmware version of the manager, it's current software version etc. Examples of managers are BMCs (baseboard management controllers), enclosure managers, management controllers, and other subsystems that are assigned manageability functions.|

|Software inventory Collection|/redfish/v1/UpdateService/FirmwareInventory /redfish/v1/UpdateService/LocalImageStore /redfish/v1/UpdateService/SoftwareInventory (see note)|Represents a collection of the software inventory kept by the Redfish® service. Each software inventory represented by the SoftwareInventory schema in the Redfish® data model. The SoftwareInventory schema contains an inventory of software components. This can include software components such as BIOS, BMC firmware, firmware for other devices, system drivers, or provider software.|

|Power Equipment Collection|/redfish/v1/PowerEquipment|Represents a collection of all the power equipments managed by the Redfish® service. Each power equipment is represented by the The PowerEquipment schema the Redfish® data model.|

|Cables Collection|/redfish/v1/Cables|Represents a collection of all the cables managed by the Redfish® service. Each cable is represented by the Cable schema in the Redfish® data model, which contains properties that describe a cable connecting endpoints of a chassis, port, or any other cable-compatible endpoint.|

NOTE: The software inventory collections available at all the listed Redfish® resource URIs shall be considered for the overall software inventory collection associated with an NFVI-PoP. 

<mark>Editor's Note:    The above list to be updated if more relevant Redfish&reg; objects are identified to be mapped against the IFA053 NfviPopInfo object.</mark>

### 5.3.5 Physical resource inventory object

The physical resource inventory object, specified as PhysicalResourceInventory in ETSI GS NFV-IFA 053 [\[1\]](#_ref_1), does not correspond to any specific object in the Redfish® data model specification. However, it can be related with the NFVI-PoP object as specified in table 5.3.5-1.

**Table 5.3.5-1: Definition of the Physical resource inventory object**<a name="table_5.3.5-1"></a>

|Attribute Name|Data Type|Cardinality|Description|

|-|-|-|-|

|id|Identifier|1|Identifier of the resource.|

|nfviPops|NFVI-PoP|1..N|List of relevant NFVI-PoP data objects.|

In a distributed scenario where each NFVI-PoP is managed by its own Redfish® service, the collective physical resource inventory information can be represented as a collection of the respective NFVI-PoP data objects.

<mark>Editor's Note:    The physical resource inventory object is candidate to be omitted from this version of the present document to avoid any confusion. It can be included once it is clear how to aggregate the overall physical resource inventory belonging to different NFVI-PoPs.</mark>

## 5.4 Performance management related objects

### 5.4.1 PMJob