Feature #10561
closed
Klever Python package is not updated when updating Klever instances locally
Added by Evgeny Novikov about 4 years ago.
Updated almost 4 years ago.
Description
After recent refactoring of deployment scripts the Klever package is not updated when updating Klever instances locally. Scripts deploy new configurations/specifications, but software remains the same as after installation. One can try to mitigate the issue by using option "-e" during initial installation of the Klever package, but it is not reliable. The issue does not exist for OpenStack Klever instances.
Klever Python package must be installed manually before local deployment, and also must be updated manually and separately, as noted in the Documentation. Local deployment scripts are part of the Klever Python package, and it is really not a very good idea for package code to try to update itself. These scripts also do not know how the Klever Python package was installed (with or without -e option, for example), so they can mess everything up when trying to update it.
So, this is not a bug, but a design decision. I am not yet sure that we should try to change it.
- Category changed from Deployment to Documentation
Thank you for the detailed explanation. I suggest to explicitly and noticeably mention about necessity to update the Klever Python package at the corresponding place within the documentation, that is here, since people including even Klever developers forgot notes provided at the parent page.
- Tracker changed from Bug to Feature
- Priority changed from Immediate to Urgent
- Detected in build deleted (
git)
- Status changed from New to Resolved
Some clarifications to documentation were added in feature-10561 branch.
- Status changed from Resolved to Closed
After small improvements I merged the branch to master in b07aee9d1. Let's hope that users including me will not forget to update Klever Python package anymore.
Also available in: Atom
PDF