|
Post by manishg4 on Jun 4, 2018 7:53:54 GMT
Hello,
I understand that some there is some work in progress by some vendors to expand the Redfish functionality to support their desired implementations over and above Redfish like the Intel PSME REST API Spec, and the Chinook spec by Dell, HPE etc.
Queries: 1. I understand that Redfish spec by itself is pretty liberal i.e. a set of URIs are defined where desired objects can be retrieved from, and within the URI very few params are mandatory by spec. 2. To standardise the params supported by a Chassis, Redfish has a concept of PROFILES where the set of URIs, and params within the URI are specified (like if vendors say they support the OCP Profile, then all params : URIs + params within that URI that the OCP profile requires are supported by the Chassis). 3. So, when the Intel PSME Spec defines a spec of REST APIs, does it mean a new PROFILE? Is the Intel PSME REST API Profile again to check / maintain operability? 4. Are the Intel PSME Spec, and the Chinook Spec just a further standardisation of Redfish APIs just like a Redfish Profile? 5. Are the Intel PSME Spec, and the Chinook Spec just applicable for Application Platform servers, or also applicable for Storage Chassis Boxes as well? 6. I see very little of the Swordfish spec integrated with the Intel PSME Spec, and the Chinook spec - is this work in progress at the moment ?
Thanks in advance,
Regards, Manish
|
|
|
Post by mraineri on Jun 5, 2018 14:32:14 GMT
With regards to Chinook, Chinook was a submission to extend the Redfish data model. The Redfish Forum took the submission and modified it further to cover the gaps for how a service can express Memory, Storage, and Fabrics. These extensions were made part of the standard towards the end of 2016.
However, this is not to be confused with a profile. Chinook was a proposed data model. A profile may be used by an organization to specify requirements on a service for what elements of the data model are made available, such as requiring Memory, Storage, and Fabrics resources being exposed (and which properties in those resources are required).
|
|
|
Post by jautor on Jun 5, 2018 18:20:17 GMT
By the way, if you work for a member of the DMTF Redfish Forum (working group), I'd suggest you contact your company representative to get clarification of all of this. But if not, we'll certainly help you work through the questions...
Jeff
|
|
|
Post by manishg4 on Jun 6, 2018 18:24:46 GMT
Thanks for the inputs. I now get the get the difference between a "Profile", and what was meant by "Chinook".
On the Intel PSME REST API front, my understanding is that it is more of a Profile (consisting of standard properties in a service, aliongwith a few Vendor specific options. Is this understanding correct?
Thanks in advance, Manish
|
|
|
Post by jleung on Jun 7, 2018 20:44:48 GMT
Your understanding is correct. A profile is created by an organization to specify the resources and resource properties that must exist on an implementation, for the implementation to claim conformance to that organization's API specification.
|
|
|
Post by manishg4 on Jun 8, 2018 7:43:55 GMT
Thank you all.
|
|
fish
Guppy
Posts: 65
|
Post by fish on Jun 26, 2018 8:17:14 GMT
Thanks for the inputs. I now get the get the difference between a "Profile", and what was meant by "Chinook". On the Intel PSME REST API front, my understanding is that it is more of a Profile (consisting of standard properties in a service, aliongwith a few Vendor specific options. Is this understanding correct? Thanks in advance, Manish Regarding Intel PSME (part of Intel RSD), I would denote this as an "OEM extension" of Redfish, and not a profile of Redfish. This was at least the case last time I looked. Intel PSME typically adds OEM specific properties to Redfish resources, and possibly some OEM specific resources. Intel PSME is not defined using the new profile constructs of Redfish.
|
|