Post by igork on Sept 6, 2022 14:59:41 GMT
Hello,
I have one question regarding use of HttpBootUri attribute.
And according to schema:
"HttpBootUri": {
"description": "The URI to boot from when BootSourceOverrideTarget is set to `UefiHttp`.",
"format": "uri-reference",
"longDescription": "This property shall contain the URI to perform an HTTP or HTTPS boot when BootSourceOverrideTarget is set to `UefiHttp`.",
"readonly": false,
"type": [
"string",
"null"
],
"versionAdded": "v1_9_0"
}
In order to support it Redfish module has to create HttpBoot option with the URI specified by a user to let BDS know where to boot to.
At the same time there is a definition of the BootSourceOverrideEnabled in the schema:
"BootSourceOverrideEnabled": {
"anyOf": [
{
"$ref": "#/definitions/BootSourceOverrideEnabled"
},
{
"type": "null"
}
],
"description": "The state of the boot source override feature.",
"longDescription": "This property shall contain `Once` for a one-time boot override, and `Continuous` for a remain-active-until-cancelled override. If set to `Once`, the value is reset to `Disabled` after the BootSourceOverrideTarget actions have completed successfully. Changes to this property do not alter the BIOS persistent boot order configuration.",
"readonly": false
}
And here we have following:
"Changes to this property do not alter the BIOS persistent boot order configuration."
So, when Redfish module creates the HTTP boot option it is a temporary boot option which is deleted after BIOS boot to HTTP URI.
And this works good for the "Once" value of BootSourceOverrideEnabled.
But what to do if user specifies "Continuous"? We cannot create a permanent boot option since it will alter the BIOS persistent boot order configuration.
Should "Continuous" flag be supported if HttpBootUri attribute set?
Thank you,
Igor
I have one question regarding use of HttpBootUri attribute.
And according to schema:
"HttpBootUri": {
"description": "The URI to boot from when BootSourceOverrideTarget is set to `UefiHttp`.",
"format": "uri-reference",
"longDescription": "This property shall contain the URI to perform an HTTP or HTTPS boot when BootSourceOverrideTarget is set to `UefiHttp`.",
"readonly": false,
"type": [
"string",
"null"
],
"versionAdded": "v1_9_0"
}
In order to support it Redfish module has to create HttpBoot option with the URI specified by a user to let BDS know where to boot to.
At the same time there is a definition of the BootSourceOverrideEnabled in the schema:
"BootSourceOverrideEnabled": {
"anyOf": [
{
"$ref": "#/definitions/BootSourceOverrideEnabled"
},
{
"type": "null"
}
],
"description": "The state of the boot source override feature.",
"longDescription": "This property shall contain `Once` for a one-time boot override, and `Continuous` for a remain-active-until-cancelled override. If set to `Once`, the value is reset to `Disabled` after the BootSourceOverrideTarget actions have completed successfully. Changes to this property do not alter the BIOS persistent boot order configuration.",
"readonly": false
}
And here we have following:
"Changes to this property do not alter the BIOS persistent boot order configuration."
So, when Redfish module creates the HTTP boot option it is a temporary boot option which is deleted after BIOS boot to HTTP URI.
And this works good for the "Once" value of BootSourceOverrideEnabled.
But what to do if user specifies "Continuous"? We cannot create a permanent boot option since it will alter the BIOS persistent boot order configuration.
Should "Continuous" flag be supported if HttpBootUri attribute set?
Thank you,
Igor