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

Feature: Support command to upgrade Jiva Volumes #81

Closed
4 tasks done
kmova opened this issue Aug 16, 2021 · 0 comments
Closed
4 tasks done

Feature: Support command to upgrade Jiva Volumes #81

kmova opened this issue Aug 16, 2021 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@kmova
Copy link
Member

kmova commented Aug 16, 2021

Once OpenEBS control plane is upgraded to latest version, user/admin will have to initiate the upgrade of the jiva volumes by creating a Kubernetes Job YAML. This is a request to automate the steps by doing the following:

  • Enhance openebs version command with installed component versions #83
  • Enhance: Missing details about Jiva Replicas #82
  • Enhance the Jiva Volume Describe command to auto-determine the openebs namespace where jiva volume-related artifacts are deployed.
  • Add support for a new command - openebs upgrade volume [--cas-type=jiva] [<volume-name(s)>] that will perform the following:
    • Check if the jiva volume is running a version older than the jiva operator version
    • If yes and then check if there is already an upgrade job in progress. If yes, then show the status of the upgrade process.
    • If specific volume name(s) is specified, verify it can be upgraded and launch the Upgrade Job
    • If cas-type=jiva is specified, get list of all jiva volumes and launch the Upgrade Jobs for the volumes that need to be upgraded.
    • once the upgrade job is launched, show the status of the upgrade. the command can be exited with user can come back and run the same command to check the status.

The upgrade job yaml format is at: https://github.com/openebs/upgrade/blob/master/docs/upgrade.md#running-the-upgrade-job-2

Related: #43

Notes:

  • The command should be introduced in such a way that it can be extended to other engines as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants