OpenNebula v.5.10.2 Hotfix Release is out! https://opennebula.org/hotfix-release-v-5-10-2-is-available/ Users with active support subscriptions: please check your private repositories for access to the new packages #opensource#cloud#cloudcomputing#edgecomputing#announcement#opennebula#release#hotfix
For some this may be the first time seeing communications about Hotfix releases, and you may be wondering how to get access to them. As part of the User Community, access to the OpenNebula software, and the Maintenance Releases that follow updates / upgrades is universal. Yet, in addition to leading the open source project, OpenNebula Systems provides Enterprise Support to subscribers of our commercial support subscriptions. One of the several benefits of being a subscriber is gaining access to packages to Hotfix releases. So, while these Hotfix packages are not generally available, we believe there is value in communicating the details about these releases and what is included - even if only to clarify the work being done and the issues continually being addressed. And everyone can create their own packages or build OpenNebula from the source code.
If you have any questions, donāt hesitate to reach out to me (@mabdou).
So the best course of action for those not paying for Enterprise Support is to stick to āoldstableā, i. e. the previous release, which most likely has all known bugs fixed for the general public?
While the packages from Hotfix incremental versions are not publicly released and are only available for users with an active commercial subscription, the code is publicly available in the GitHub repository, as are the templates to create packages for the different supported platforms. So, everyone can create their own packages or build OpenNebula from the source code, but only OpenNebula Systems customers have the convenience of pre-created packages for Hotfix incremental releases.
so if I feel bitten by something that is supposed to be fixed in a hotfix release, Iād just roll my own packages from the corresponding tag, i. e. release-5.10.2 in this case, and upgrade to those? Ok, thatās awesome indeed.
For users of the OpenNebula Community Edition, weāll regularly be producing CE Patch Releases (like the recent v.5.12.0.1), whose code and binary/source packages are available under Apache License v.2.0. As for requesting access to our private packages template repo, please refer to Towards a Stronger OpenNebula Community
ok thanks. But Iām a bit confused now. In the post above you wrote that migrators are only needed for minor/major releases.
Iām currently running 5.12.0.1 and I thought I might could just install the CE Patch with āapt upgradeā.
thanks for letting me know. So I can just install the patch with āapt upgradeā on all frontends and nodes and restart opennebula services? No database and configuration changes needed?
Sorry for being a so penetrative here, Iām just insecure here because I have never done it beforeā¦
Thanks a lot,
Thomas
The OpenNebula philosophy in non-major upgrades (i.e. for CE Patch Releases) is not to change configuration files or the database schema. For this reason, you donāt need to upgrade the database, you just need to stop all OpenNebula services, perform the apt upgrade command in all your servers, and then start again all the services.