|
Post by ericslandry on Sept 15, 2021 10:13:10 GMT
Hi! I'm looking for information on how to get started at creating a Redfish service (web API) for a network controller. Does a Redfish service need to implement every endpoint in redfish.dmtf.org/schemas/v1/openapi.yaml ? The various Redfish websites have great resources for steps 3 through 20, but I find lack the first two steps on G etting StartedAny pointers will be greatly appreciated!
|
|
|
Post by mraineri on Sept 15, 2021 13:39:06 GMT
No, most of what's in Redfish is optional. The openapi.yaml file we publish is a superset of all possible URIs we've standardized on, but the reality is large portions won't apply to certain classes of products. For example, a rack PDU type of product wouldn't implement the "/redfish/v1/Systems" hierarchy. We do have some examples for different classes of products on our mockups page here to give you an idea of the types of resources to consider: redfish.dmtf.org/redfish/v1However, something that is purely a network controller is not something I'm very familiar with. The "Advanced Communication Devices" mockup on the link above might have some of the building blocks you need though.
|
|
|
Post by ericslandry on Sept 16, 2021 12:42:10 GMT
|
|