-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce 'qosStatus' and corresponding notification event to fix issue #38 #67
Introduce 'qosStatus' and corresponding notification event to fix issue #38 #67
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The deck I presented in the WG meeting associated to this PR: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @emil-cheung for addressing past comments. Now that I understand better your proposal I could review it with more context.
Co-authored-by: Jose Luis Urien <[email protected]>
Co-authored-by: Jose Luis Urien <[email protected]>
Co-authored-by: Jose Luis Urien <[email protected]>
Co-authored-by: Jose Luis Urien <[email protected]>
@hdamker shall I rebase this PR to the main branch? |
@emil-cheung sorry for the late answer (thought I had done it already): yes, please rebase the PR to main branch as this is now the branch for the latest changes. |
The base branch was changed.
@hdamker I have changed the base branch from dev-0.9.0 to main, please check. |
@emil-cheung Thanks a lot! LGTM, we are ready for a final review by those who have previously approved. |
@jlurien @jlurien @eric-murray Could you have a final view? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. A couple of cosmetic suggestions
Co-authored-by: Jose Luis Urien <[email protected]>
code/API_definitions/qod-api.yaml
Outdated
@@ -397,7 +397,10 @@ components: | |||
enum: | |||
- DURATION_EXPIRED | |||
- NETWORK_TERMINATED | |||
description: Currently statusInfo is only applicable when qosStatus is 'UNAVAILABLE'. | |||
description: | | |||
Reason for the new `qosStatus`. Currently `statusInfo` is only applicable when `osStatus` is 'UNAVAILABLE'. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
osStatus
-> qosStatus
Co-authored-by: Jose Luis Urien <[email protected]>
code/API_definitions/qod-api.yaml
Outdated
@@ -397,7 +397,10 @@ components: | |||
enum: | |||
- DURATION_EXPIRED | |||
- NETWORK_TERMINATED | |||
description: Currently statusInfo is only applicable when qosStatus is 'UNAVAILABLE'. | |||
description: | | |||
Reason for the new `qosStatus`. Currently `statusInfo` is only applicable when `osStatus` is 'UNAVAILABLE'. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: `osStatus` should be `qosStatus`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
A proposal to fix:
#38