Hi,
that's how we usually set up our Openstack cluster(s). We bootstrap
our first node so we have a single-node pacemaker cluster running all
Openstack control services, then "join" the other control nodes,
expanding the cluster.
I'd recommend to practice in a test cluster, that has helped me a lot!
Regards,
Eugen
Zitat von Tomas Jelinek <tojel...@redhat.com>:
Hi Andreas,
From the point of view of pcs, pacemaker and corosync, it is
possible to create a one-node cluster, run resources in it, and add
another node afterwards. Obviously, when the single node is lost for
whatever reason, there is no other node to run the resources.
You should also consider whether the cluster's workload supports
this and what steps are necessary to make it work in this scenario.
Regards,
Tomas
Dne 31. 07. 25 v 8:46 Andreas Mock napsal(a):
Hi all,
I have to upgrade an old pacemaker cluster consisting of two nodes.
(There is no chance of rolling update).
Is it possible to create a pacemaker “cluster” starting with only
one node and afterwards attach the second node?
Best regards
Andreas
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/