|
Post by rpajak on Feb 14, 2017 8:06:45 GMT
Could you, please, clarify where the oem action should be added if there is no Action property in the DMTF resource schema - like Thermal resource.
If there is an Action property in the resource, it is clear that oem action should be in Actions->Oem. But if there is no Action property in the resource there are following possibilities:
1) Add MyNew.Action to Action->Oem property of the resource { Actions:{ Oem:{ MyNew.Action: {} } } }
2) Add MyNew.Action to Oem->Action->Oem property of the resource {
Oem: { Actions:{
Oem:{
MyNew.Action: {}
} } }
}
3) Add MyNew.Action to Oem->Action- property of the resource
{
Oem: {
Actions:{
MyNew.Action: {}
}
}
}
Which one is correct?
|
|
|
Post by jautor on Feb 17, 2017 22:40:28 GMT
Could you, please, clarify where the oem action should be added if there is no Action property in the DMTF resource schema - like Thermal resource. If there is an Action property in the resource, it is clear that oem action should be in Actions->Oem. But if there is no Action property in the resource there are following possibilities: We were supposed to define the "Actions" property in all (or at least most) of the Redfish schemas to allow for OEM's to add their own Actions, and keep them collected up in one, easily discovered location. Looks like we missed 'Thermal', I've marked that as a high priority bug, we'll revise the schema and get it released in the next bundle (which should come in March). So your #1 is correct. Jeff
|
|
|
Post by andruszamojski on Feb 21, 2017 14:25:36 GMT
Isn't it the same case with ManagerAccount schema?
|
|
|
Post by jautor on Feb 26, 2017 23:19:07 GMT
Isn't it the same case with ManagerAccount schema? Yes, it is... We'll make a full pass through the existing schemas to correct any of them that are missing an Actions object. Jeff
|
|
|
Post by francine on May 18, 2018 8:33:20 GMT
Could you, please, clarify again the OEM Action, because now there is an OEMActions part:
So what is the solution for OEM Actions and OEM Action ?
1 ) {
"@odata.type": "#Manager.v1_1_0.Manager",
... "Oem": {}
},
"Actions": {
"Oem": {
"MyOEMAction": { .....
2 ) {
"@odata.type": "#Manager.v1_1_0.Manager",
...
"Oem": {}
},
"Actions": {
"Oem": {
} } "OemActions": {
"MyAction": {
}
}
..... or something else ....
Thanks for any help, Francine
|
|
|
Post by mraineri on May 18, 2018 18:57:56 GMT
#1 is the correct method. As of last summer, we've provisioned all of our resources to support an Actions property, so OEM actions belong inside of "Oem" within the Actions property. We have an example of this in our mockups for a ComputerSystem.
Here's the sample
"Actions": { "#ComputerSystem.Reset": { <Standard ComputerSystem Reset Action> }, "Oem": { "#Contoso.Reset": { "target": "/redfish/v1/Systems/437XR1138R2/Oem/Contoso/Actions/Contoso.Reset" } } },
|
|
|
Post by francine on May 30, 2018 6:53:50 GMT
Ok, nice, mraineri, I guess I missed "#Contoso.Reset" example. Regards, Francine
|
|