Ping @ataxyanetwork to the rescue 
CEO
Private
Posts
-
RE: [dedicated thread] Dell Open Manage Appliance (OME)
-
RE: 14 VMs Running: After Pool patch update - message states I need to restart to take effect?
Hi,
So it seems you are in a case you don't have a pool to avoid a VM reboot with your host reboot.
In that case, you need to have auto power on enabled to make sure after host reboot, they all start.
-
RE: Tesco and XCP-ng
I'm not sure it's a great idea, because even 64 hosts is huge in terms of VMs and fallout if you have a problem on your pool DB. Even if you drastically improve the current mechanism, the impact of a problem pool wide is far bigger with 64 hosts than 24 for example.
It's more than purely tech, it's also a tech design/choice.
-
RE: Tesco and XCP-ng
Even with existing customer with that many VMs or host, absolutely nobody will do a giant pool. And in the ROBO/edge world, it's mostly 2 or 3 machines per shop.
Even large DC deployments tend to use around 10 hosts per pool (a good sweetspot between convenience and fallout protection in case you have a problem on a pool).
-
RE: Tesco and XCP-ng
I won't be against it obviously. But I'm not the one making the choice
-
RE: Slow response between XCP-NG and cloud stack syncing
Hi,
XCP-ng got an event system that will propagate things like this instantly, at least that's the way it works normally
- Do you have the same behaviour in Xen Orchestra?
- Have you reported the issue to CloudStack?
- If you have an XCP-ng support subscription, you can also open a ticket so we can take a look on XCP-ng status to catch any obvious issue.
