I solved the problem: Cloudstack creates virsh pools during the initializing of cloudstack-agents. These Pools are hard defined until you release your hosts. So if you want the change the settings like in my case, you have to edit the pools with virsh pool-edit <id> and restart libvirtd. These step have to been made on every host in your cluster with the Ceph RBD config.
After that you need to migrate the VMs, which triggers an recreate of the virsh-template. best regards Sven On 2022/07/27 08:22:03 Sven Barczyk wrote: > Hello everyone, > > > > i caught myself beeing stupid. > While deploying my cluster, I've decided to use my mon1.ceph to be the main > RBD Host which leads now to the problem, that a restart of mon1 will be > hell. > > In despite, i changed the host to a round-robin dns (changed by sql ), which > is the suggested method of the documentation and thought all new Instances > will be deployed with this new host from the database. > But no , still uses the mon1.ceph while deploying new instances (checked > with virsh dumpxml on my hosts), instead of the new set host, mons.ceph > which round-robins through all my mons. > > Restart of Cloudstack-management did not help. > > Is there anyone who could give me an hint where this rbd hosts might be > hardcoded in the cloudstack-config ? > > > > Best regards, > Sven > > > >
smime.p7s
Description: S/MIME cryptographic signature
