ImageURI in UpdateService

geissonator
Minnow

Posts: 17

ImageURI in UpdateService May 10, 2019 19:06:30 GMT

Quote

Post by geissonator on May 10, 2019 19:06:30 GMT

I'm looking to implement the SimpleUpdate object within the UpdateService. Within it is a parameter, "ImageURI" of type string. I'm looking for more details on what the format of that parameter should be.

In searching for documentation on URI's within Redfish, I only seem to find references to it in regards to redfish object URI paths.

I took a stab at implementation over in gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/20884 but there is a question on whether my URI is really correct for TFTP based updates:

<TFTP server IP>/<firmware image>

jautor
Administrator

Posts: 519

ImageURI in UpdateService May 14, 2019 21:42:01 GMT

Quote

Post by jautor on May 14, 2019 21:42:01 GMT

The format is a "URI" from the RFC definition. There is some additional info in the description of "TransferProtocol" that we should copy into the description, here, too, to better explain it. And we should probably add the "format" attribute in the schema so it can be validated as a URI as well.

If the scheme is omitted from the URI, it is specified by the "TransferProtocol" parameter. If that parameter isn't supplied, the scheme is assumed to be "http".

So for a TFTP transfer, the value(s) can be either:

"ImageURI": "tftp://<server ip>/<firmware image>"

or

"ImageURI": "<server ip>/<firmware image>",
"TransferProtocol": "TFTP",

geissonator Minnow Posts: 17	ImageURI in UpdateService May 17, 2019 19:29:08 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by geissonator on May 17, 2019 19:29:08 GMT Perfect, thanks a lot Jeff!

Post by geissonator on May 10, 2019 19:06:30 GMT

Post by jautor on May 14, 2019 21:42:01 GMT

Post by geissonator on May 17, 2019 19:29:08 GMT