@olivierlambert Hi, thanks for the feedback 🙂

Yes, you should stay updated often 🙂

@olivierlambert Thx, will check this out.

@olivierlambert Im confident it will all come together in the future!

@john-c dunno about how that script should work, but you can execute anything with ansible.builtin.shell

Thanks for your feedback @erlicthemad !

@jubin3 As this is totally unrelated to XOA and XCP-ng, you'll (hopefully) get a better response in the cloud-init community, as it's their project which has (once again) been broken by an OS update. I gave up chasing them some time ago, especially with brand new OS releases.

@MathieuRA

Thanks for doing the fix, I have tested this and I confirm it is working. I am able to migrate VMGuest to a different host by ticking the check box in the vmlist.

29d4f92f-f074-488d-b2b3-27b74c2e0ae4-image.png

0b61a637-4dac-41a4-9aba-ba7c6db85c8b-image.png

Yes, that's pretty much it 🙂 Then, if your old master is dead for good (ie reinstall needed), you need to "forget" it (ie it will be removed from the database).

it's pretty simple because XAPI is replicated to all pool member while the master is running (but all other members got it in read only). If the master dies, then promote another member and you are done.

If other people get the UNABLE_TO_VERIFY_LEAF_SIGNATURE error, check that your XMPP server provides the correct certificate chain.

You can use OpenSSL for this:

$ openssl s_client -connect $domain:$port -starttls xmpp -showcerts </dev/null CONNECTED(00000003) depth=0 CN = $domain verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 CN = $domain verify error:num=21:unable to verify the first certificate verify return:1 depth=0 CN = $domain verify return:1

@olivierlambert

Thank you very much Olivier, this is exactly what I want to do!

Hi,

You can use the warm migration in your case, yes 🙂 To me, that's one of the use case where it's safer than a live/hot one.

Hi,

Thanks for the feature request 🙂

This is very very likely a request for a production environment (this level of Netbox customization). It's almost taking 100% of @pdonias' time, so we need to start rationalizing stuff in order to keep some resources to move forward on XO 6.

If you have a pro subscription, can you open a feature request ticket? If you don't, it might worth to create an issue on our public Github repo (with all the details) so we can see/discuss there 🙂 Thank you!

@pdonias ok I get a correct answer from inside but from outside I'm getting this bad request. The curl gets to the ssl certificate on the net box host, but throws the 400 bad request, when doing from outside the firewall.

When testing locally, it works.

Let me look this over! Thanks!

Hopefully someone in the community will guide you, personally I never played with jobs 🙂

Hi!

In theory, you just need to get the Kubernetes key to connect with whatever tool you want to play with the k8s cluster, that's pretty much everything 🙂

What do you have in mind exactly?

@pdonias thanks for the update! I took a look at the latest commit and apparently I was right even though it didn't feel right. 😂

Thanks again to you all for this amazing set of FOSS tools!