|
Post by jautor on Feb 16, 2017 22:40:58 GMT
I am new to redfish and swordfish. Not sure if this is the site to post Swordfish related questions. This is absolutely the right place to ask both Swordfish and Redfish questions. In fact, we'll be adding Swordfish-specific sub-forums ASAP. As to your actual question, I'll leave that for the storage experts to answer. Jeff
|
|
|
Post by jautor on Feb 16, 2017 22:37:58 GMT
This readme for Redfish references the patent disclosures- Is an implementation of Redfish *infringing* on these and other undisclosed patents?
- Is an implementation of Redfish entitled to *package* (e.g. included in the software / installable image etc.) and *distribute* the Redfish schema files ?
Hi Hramasub, The Redfish README is referring to a DMTF-wide disclosure list - the patents shown there may apply to any standard the DMTF has produced, but that list is not specific to Redfish. We're not lawyers here, though, so recommend you refer any legal questions to your legal staff... But that topic, and the answer about distribution of the schema files are both covered by the DMTF's Copyright policy, here: www.dmtf.org/about/policies/copyrightFor re-distribution, see the relevant statement from that page: "Members and non-members may reproduce DMTF specifications and documents for uses consistent with this purpose, provided that correct attribution is given. "
|
|
|
Post by jautor on Jan 6, 2017 2:44:25 GMT
|
|
|
Post by jautor on Jan 4, 2017 23:02:48 GMT
Will there be schema support for Virtual Machine (VM) management in Redfish? The ComputerSystem schema could allow for some basic VM management - the "SystemType" property has an enumeration defined for "Virtual" systems. But you're correct that more specific VM management would need additional resources (and schema definitions). If there's something you'd like to see, please feel free to make a proposal. Although the first step would more likely be to get your favorite VMM software to support a Redfish interface for management! Jeff
|
|
|
Post by jautor on Jan 4, 2017 22:47:31 GMT
Metadata and schema in Redfish context - are they same? They are related, as "schema" is metadata, but not delivered in the JSON payload. There are OData 'annotations' in Redfish, which can be metadata delivered in payload. It's best to just think of the "schema" as the data definitions and details/rules for each of the properties in a particular Redfish JSON payload (a "Resource"). Jeff
|
|
|
Post by jautor on Jan 4, 2017 22:44:34 GMT
1. How HTTP redirect is used in Redfish? 2. Is ETag required to provide consistency? 3. What is the relationship between redfish services and redfish resources? 1. HTTP Redirect is required for client software using a Redfish service, as the service may use this functionality. However, the only place a redirect is expected is at the "/redfish/v1" (no trailing slash) URI, which by spec should redirect to "/redfish/v1/" (with trailing slash). Although in that specific case the specification also allows the service to just return the /redfish/v1/ resource as if the trailing slash was there... 2. ETags are only required for the ManagerAccount resources, but otherwise, they are just recommended. 3. A "Redfish Service" is any product that implements the Redfish specification - that's the software/firmware that implements the specification. The "Redfish Resources" are the JSON payloads, defined by the Redfish schema, returned by a Redfish Service. Hope that helps, Jeff
|
|
|
Post by jautor on Oct 28, 2016 2:50:31 GMT
Another related question - OEM property of a resource will be filled with some OEM data (let's take an example from this thread 3 posts above). Should OEM section of initial schema file of the resource be updated or is it enough to have odata.type link ("@odata.type": "http://schemas.xyzzy.com/XyzzyProcessor.v1_0_0.XyzzyProcessor") to schema of the OEM field in the OEM resource and schema may be untouched then? So having in mind Processor example should we update OEM section of the resource schema or may it be untouched as in example below? "Processor": { ... "properties": { "@odata.context": { "$ref": "http://redfish.dmtf.org/schemas/v1/odata.4.0.0.json#/definitions/context" }, "@odata.id": { "$ref": "http://redfish.dmtf.org/schemas/v1/odata.4.0.0.json#/definitions/id" }, "@odata.type": { "$ref": "http://redfish.dmtf.org/schemas/v1/odata.4.0.0.json#/definitions/type" }, "Oem": { "$ref": "http://redfish.dmtf.org/schemas/v1/Resource.json#/definitions/Oem", "description": "This is the manufacturer/provider specific extension moniker used to divide the Oem object into sections.", "longDescription": "The value of this string shall be of the format for the reserved word *Oem*." }, You don't need to touch the existing Processor schema at all. As shown in J2Hilland's example above, the OEM section has it's own @odata.type (schema definition). So you create a new, separate schema file just for that OEM data. From your original question, that OEM schema would have two properties, "FrequencyScaling" (itself an embedded object with a "Status" property) and "StepValuePercentage". Hope that helps, Jeff
|
|
|
Post by jautor on Oct 28, 2016 2:45:22 GMT
Thank you for explanation. Regarding 2) Let's say I will limit BootSource enum elements. Am I right that my implementation should also return updated schema of the resource (with limited BootSource options) ? Or schema should be left untouched? While you could re-publish an edited (subset) schema, that isn't necessary nor something that would be expected. Redfish uses an "annotation" mechanism for properties like BootSourceOverrideTarget to inform the client what enumerations are supported by the implementation. This is done for certain read-write properties, so that the client can avoid trial-and-error PATCH requests. The annotation takes the form of a separate property with the same name and "@redfish.AllowableValues" appended. In this case, "BootSourceOverrideTarget@Redfish.AllowableValues". For example: "Boot": { "BootSourceOverrideEnabled": "Once", "BootSourceOverrideTarget": "Pxe", "BootSourceOverrideTarget@Redfish.AllowableValues": [ "None", "Pxe", "Cd", "Usb", "Hdd", "BiosSetup", "Utilities", "Diags", "SDCard", "UefiTarget" ] },
Cheers, Jeff
|
|
|
Post by jautor on Aug 16, 2016 19:52:06 GMT
Max,
Thanks for the suggestion. We'll investigate a bit and see what we can come up with. Providing client software (especially management consoles) with "frequently used" functions and data are a priority - we'll have to see if there's something we can do here that will provide interoperability. I think we would want a consistent solution for serial console / command line sessions as well for the same type of usage.
Cheers!
Jeff
|
|