Commit 59d2f2e1 authored by Hammad Zafar's avatar Hammad Zafar
Browse files

Merge branch... 

Merge branch 'NFVSOL(26)000025_SOL026_Clause_10_Physical_resource_fault_management_service_interface' into 'main'

NFVSOL(26)000025_SOL026_Clause_10_Physical_resource_fault_management_service_interface

See merge request !13
parents 3bf39682 08795941

GS_NFV-SOL_026.md

+26 −2
Original line number Diff line number Diff line
@@ -328,6 +328,18 @@ Table 5.5.2-1 lists down the properties of Redfish® object that is mapped to 


Possible URI paths for the LogEntry object are specified in the Redfish® data model specification [\[3\]](#_ref_3).



## 5.6 Fault management related objects



### 5.6.1 Alarm



Table 5.6.1-1 lists down the properties of Redfish® object that is mapped to Alarm data object.



**Table 5.6.1-1: Redfish&reg; resource object for Alarm**<a name="table_5.6.1-1"></a>



|Redfish&reg; resource object|Redfish&reg; resource object description|

|-|-|

|Event|Represents a notification containing the alarm, which is received by the consumer that has subscribed to receive alarms associated with physical resources.|





# 6 Physical resource provisioning and lifecycle management service interface
@@ -1691,11 +1703,23 @@ The request and response data structures of the physical resource performance ma 


## 10.1 Description



<mark>Editor's Note:    This sub-clause will add description of the service interface.</mark>

The physical resource fault management service interface allows the API consumers to invoke fault management operations related to physical resources. The Redfish&reg; interface [\[2\]](#_ref_2) endpoints profiled for this service interface allow consumers to manage API resources that are applicable for this service interface.



The operations supported over this service interface are the following:



- Receive information (via notifications) about faults and alarms associated with physical resources

- Subscribe to notifications related to faults and alarms

- Notify subscribers according to the subscriptions



<mark>Editor's Note:    It is unclear whether Redfish supports the consumers querying information about alarms via direct requests. In that case, this particular operation may not be supported over this service interface. </mark> 



## 10.2 API version



<mark>Editor's Note:    This sub-clause will add API version and API roots for the service interface.</mark>

The API {VERSION} for the profiled Redfish&reg; interface [\[2\]](#_ref_2) shall be set to \"v1\". Details about the API structure of the Redfish&reg; interface [\[2\]](#_ref_2) are provided in clause 4.3.2 of the present document.



The corresponding Redfish&reg; API roots are specified below:



- /redfish/v1/EventService/Subscriptions



## 10.3 Resource structure and HTTP methods