Skip to content
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

Component upgrade state information #1241

Open
ejbrever opened this issue Jan 3, 2025 · 0 comments
Open

Component upgrade state information #1241

ejbrever opened this issue Jan 3, 2025 · 0 comments

Comments

@ejbrever
Copy link
Contributor

ejbrever commented Jan 3, 2025

I'd like to propose adding upgrade state information for components. This will allow details regarding upgrades to be exposed to users as an upgrade process can take many minutes to hours. This would be read-only information.

This could support components such as transceivers (i.e. ZR transceivers) or the device operating system.

These could be placed under a new grouping such as:
openconfig/platform/component/state/upgrade/

Proposed leaves would be:
new-firmware-version: string, the new firmware package version.
new-firmware-version-service-impacting: bool, true if the firmware would require a service impacting upgrade to take effect.
status: identityref (sw loading, in-progress, fail, complete)
step: string, describing the step the device is attempting to do.
step-percent-complete: oc-types:percentage, the percent of the step that is completed.
total-percent-complete: oc-types:percentage, the percent of the total upgrade that is completed.
start-time: timeticks64, the time when the upgrade was initiated.
duration: yang:counter64, the time elapsed since the upgrade was initiated.
stop-time: timeticks64, the time when the upgrade was initiated.
last-known-failure: string, describing the last known failure encountered.

@robshakir @ahsaanyousaf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant