@olivierlambert Yes, Vates is on another level of professionalism. Wow

@olivierlambert wow, We'll surely ask many things in this thread. Thank you.

@nathanael-h

this is my code to test console for vms but I am not able to access it. Actually I have to access the console but I do not know how do auth for this.

@MathieuRA

you saved my life bro, thank you so much. I got the right way.

@ph7 Thank you. It seems to work like that. I'll wait for this fix.

@olivierlambert Happy to hear

@olivierlambert you are not checking the typescript level traces that's why there's no errors happening at your end.

@olivierlambert PostgreSQL is good at scale, btw I'm opening an issue in the XO repo so that I'll be aware to any action to this feature either now or in future. Thank you.

@olivierlambert said in SQL Database support and XO HA:

wait for the next major modification

what about XO6 the full revamped version of XO?

Hello,

As we know, XO uses Redis as its database for data storage. If something goes wrong at the Redis level, everything goes dark. You mentioned that we can back up the XO configuration and re-import it, but that’s not a complete solution.

If we are fully dependent on XO to manage a large infrastructure, there should be proper persistence at the XO level. Additionally, there should be official documentation on XO HA (High Availability) so that we can implement load balancing and ensure redundancy.

@olivierlambert ack.

@olivierlambert please update.

I created a resourceSet and set the maximum RAM to 4 GiB. Then, I created a VM within this resourceSet and checked the RAM from inside the VM console. It showed the same value as set in XO. However, when I increased the RAM from XO, exceeding the limit defined in the resourceSet, XO allowed me to do so. Upon checking the VM console again, it reflected the new RAM allocation. This leads me to believe that the resourceSet is not enforcing the defined limit.

ss:

After Increament:

I am getting the red error and when I check the error it shows nothing.