|
|
Post by AMI_shirleyh on May 21, 2021 7:20:33 GMT
Hi,
If EventService is disabled, we would like to know if we need to
1. Delete the Subscriptions 2. Close SSE Connection and delete Subscriptions related to it
Current Behaviour
As there is no information in the SPEC or Schema , we are disabling only the events sent to the destination while keeping the subscriptions alive for now. If EventService is Enabled, then events will be sent to the Event Destinations(Subscriptions) already configured.
Please let us know if it depends on how we design it or are you planning to add it in the SPEC regarding the EventService Disable behaviour ?
Thanks Shirley
|
|
|
|
Post by mraineri on May 26, 2021 12:48:12 GMT
Generally speaking, I'd expect the configuration to remain as is; any subscriptions created via POST operations to the subscription collection would still be present. I agree that SSE connections would be closed (and the subscriptions representing those SSE connections would be deleted). Beyond that, the only thing to add is I would also expect that events would not be transmitted while the service is disabled. I can take this feedback and see if we can improve the spec language to clarify this behavior.
|
|
|
|
Post by AMI_shirleyh on May 26, 2021 13:22:48 GMT
Thanks for the confirmation. We will take it from there.
|
|
|
|
Post by sunitha on Jul 6, 2021 8:23:06 GMT
Is the new subscription creation via POST operation on /redfish/v1/EventService/Subscriptions allowed when the "ServiceEnabled" property is set to 'false' ?
|
|
|
|
Post by sunitha on Jul 6, 2021 8:39:28 GMT
If new subscription is not allowed when the "ServiceEnabled" property is set to 'false', we should send out a meaningful error message to the client which is subscribing to the events. I could not find a matching error response code at the Base.1.10.0.json.
Can we add a new registry as below?
"ServiceDisabled": {
"Description": "Indicates that the operation failed because the service is disabled and cannot accept additional requests.",
"LongDescription": "Indicates that the operation failed because the service is disabled and cannot accept additional requests.",
"Message": "The operation failed because the service is down and can no longer take incoming requests.",
"Severity": "Critical",
"MessageSeverity": "Critical",
"NumberOfArgs": 1,
"ParamTypes": [
"string"
],
"ArgDescriptions": [
"The url of the resource which is disabled."
],
"ArgLongDescriptions": [
"This argument shall contain the name of the resource to be enabled."
],
"Resolution": "Enable the service 'arg1' and resubmit the request if the operation failed."
},
|
|
|
|
Post by sunitha on Jul 9, 2021 9:54:22 GMT
mraineri - Can you please clarify the question: Is the new subscription creation via POST operation on /redfish/v1/EventService/Subscriptions allowed when the "ServiceEnabled" property is set to 'false' ?
|
|
|
|
Post by mraineri on Jul 9, 2021 12:22:39 GMT
We currently do not have behavior defined for whether or not new subscriptions can be created. However, if I were to take a guess, considering we have language in the account service that states "users cannot be created, deleted, or modified" when disabled, I would think we'd follow the same semantics here. We'd need to discuss this further if we want to apply the same methodology.
|
|
|
|
Post by sunitha on Jul 12, 2021 5:01:10 GMT
Thank you mraineri. I will wait for the DMTF discussion conclusion |
|
|
|
Post by sunitha on Jul 26, 2021 10:26:08 GMT
Is there any news on this ?
|
|
