AdiF
Minnow
Posts: 15
|
Post by AdiF on Jul 6, 2023 9:47:33 GMT
I'm currently working on implementing a Redfish profiles management system. I'm looking to create a schema that allows users to perform various actions on profiles, such as adding, removing, and setting profile types. Additionally, I want to provide functionality for retrieving pending profiles and activating them once changes have been applied.
A possible solution is utilizing OEM actions under the "Manager" or "System computer". However, I'm unsure about the best approach and would appreciate any examples or similar implementations that I could reference to kickstart this project.
|
|
|
|
Post by jautor on Jul 6, 2023 23:46:42 GMT
So "Profiles" is a heavily overloaded term (and we unfortunately also use it in Redfish as there just wasn't a better word, but I don't think you're referring to the Redfish Interoperability Profile in this case) - so without some context of what that means in this case, this is only general thinking...
Assuming this is something where a "profile" is created/deleted/updated by an end user, you would probably create a collection of those, and then provide a "ProfileService" resource that would show how those are being used. See the "AccountService" and "ManagerAccount" schemas for an example. You might need an Action to perform something like "Apply Profile" if a PATCH on a single property "ProfileApplied": <URI of profile> wouldn't suffice...
If you can give us an example of what "profile" means in your case, we might be able to give more guidance...
Jeff
|
|
AdiF
Minnow
Posts: 15
|
Post by AdiF on Jul 9, 2023 10:32:05 GMT
Hi Jeff,
The profile in our case is a full set of parameters needed to configure the entire device. The user can save a set of profiles including a default one.
Thanks
|
|
|
|
Post by jautor on Jul 10, 2023 17:54:57 GMT
Ok, good. There is an example of this called "OperatingConfig" which provides a 'profile' of settings for a Processor instance. You will see a collection of OperatingConfig resources, and on each processor there is a property called "AppliedOperatingConfig" which points to the member of the collection that is currently in use (applied) to that particular processor.
So you would perform POST (create) and DELETE operations on a collection of "profiles" and make some property where appropriate to allow the configuration of which profile to actually use.
Jeff
|
|
