Add upgrade documentation for XOSTOR #319
Conversation
Wescoeur
commented
Feb 15, 2025
Wescoeur
commented
|
|
||
| Then finally open the ports and enable the LINSTOR services using the `<GROUP_NAME>` and `<HOST_UUID>` obtained above: | ||
| ``` | ||
| xe host-call-plugin host-uuid=<HOST_UUID> plugin=linstor-manager fn=addHost args:groupName=<GROUP_NAME> |
There was a problem hiding this comment.
Is it wise to wait a little after the toolstack restart, or maybe to grep the logs for the line which indicates that startup has completed?
There was a problem hiding this comment.
I would say that waiting for the previous command to return is enough to use the plugins API.
There was a problem hiding this comment.
Isn't that the job of xapi-wait-init-complete?
There was a problem hiding this comment.
At first sight it would look like a better idea to get the installer to install the extra packages with the rest of the system, rather than doing that after installation, so:
- the rpm can be obtained from the same repo as the rest of the system
- no need to mess with a XAPI restart
Or is there any problem with this? Making sure we have a properly-compatible linstor version?
There was a problem hiding this comment.
I don't see a problem with that. In this case, we can wait for XAPI to start, and then calling the plugin is enough.
We just need to be sure to have installed in 8.3 the same RPMs of LINSTOR controller/satellite as the hosts in 8.2.
| linstor advise r # Give possible fix commands in case of problems. | ||
| ``` | ||
|
|
||
| Finally check in XOA that the PBD of the SR of this host is connected. If not, do so. |
There was a problem hiding this comment.
You can't plug the PBD without the LINSTOR packages (before this point it was not the case), so I guess most of the time you have to manually connect the PBD unless the XAPI tries again on its own, which to my knowledge is not the case.
There was a problem hiding this comment.
So this won't be necessary if the installer takes care of the packages before we reboot, right?
What will be left then?
There was a problem hiding this comment.
You must be sure to execute addHost before the initial PBD plug. Otherwise, the master will not be able to plug in properly (as a reminder, each SR during the master PBD attach calls runs a scan).
There was a problem hiding this comment.
You must be sure to execute addHost before the initial PBD plug
Oh, that's somewhat "persisting a linstor state", right?
Wescoeur
force-pushed
the
xostor-upgrade
branch
2 times, most recently
from
662ee0e to
be88424
Compare
If the LINSTOR packages are newer on the new XCP-ng version, it won't work. I honestly have no idea how to handle this case without waiting several months before updating the LINSTOR packages in our repos to not break the migration.
No issue on this side. We can handle that like a classic upgrade. |
|
To handle upgrade with different versions on 8.2 to 8.3: |
Signed-off-by: Ronan Abhamon <[email protected]>
| ## Upgrade | ||
|
|
||
| If you are reading this documentation, we assume that you want to upgrade a pool on which XOSTOR is deployed, i.e. change the version of XCP-ng, for example from 8.2 to 8.3. | ||
| For updates that don't change the version numbers (bugfixes, security fixes), see [the update section](#update). |
There was a problem hiding this comment.
"updates that don't change the version numbers" is a strange concept, this might need rewording
There was a problem hiding this comment.
"updates that don't change the version number of XCP-ng" ?
| linstor adv r | ||
| ``` | ||
|
|
||
| ### 2. Information to retrieve before upgrading |
There was a problem hiding this comment.
Do we want to keep this section once we have an ISO that makes the process simpler?
