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

Add upgrade documentation for XOSTOR #319

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

Wescoeur
Copy link
Member

Before submitting the pull request, you must agree with the following statements by checking both boxes with a 'x'.

  • "I accept that my contribution is placed under the CC BY-SA 2.0 license [1]."
  • "My contribution complies with the Developer Certificate of Origin [2]."

[1] https://creativecommons.org/licenses/by-sa/2.0/
[2] https://docs.xcp-ng.org/project/contributing/#developer-certificate-of-origin-dco

Copy link
Member

@stormi stormi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if the linstor and satellite versions are not the same in 8.2 and 8.3 when they proceed with the upgrade? Will it work?

The document doesn't talk about live migrating the VMs. Is it because it "just works" so there's no need to focus on it?


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>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say that waiting for the previous command to return is enough to use the plugins API.

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can it be not connected?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@Wescoeur
Copy link
Member Author

What if the linstor and satellite versions are not the same in 8.2 and 8.3 when they proceed with the upgrade? Will it work?

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.

The document doesn't talk about live migrating the VMs. Is it because it "just works" so there's no need to focus on it?

No issue on this side. We can handle that like a classic upgrade.

@Nambrok
Copy link
Contributor

Nambrok commented Feb 26, 2025

To handle upgrade with different versions on 8.2 to 8.3:
Installer detect XOSTOR version and write on disk in /etc/firstboot.d/.
firstboot script use this file to identify the correct version of linstor-satellite/controller on 8.3 to install to maintain VERSION compatibility.
Installer need to write a warning about needing internet access to repo.vates.tech to fetch the linstor package of the correct version. If they are airgap, they need to follow documentation.
TODO: What do we do if install fail?

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

Successfully merging this pull request may close these issues.

3 participants