I've heard of people using the seed feature of rebalance to try make it repeatable enough to seem deterministic.
But I always found the idea bonkers. Maybe just upload them into swift? Let the provisioning of a new node checkout the builders - add itself - rebalance - upload modified builder and new rings. Always be having all the nodes download the newest ring on cron. Or a million other things not with the trying to have 100 nodes come up with 1 and only 1 answer. -clay On Sun, Jan 22, 2017 at 4:12 AM Alexandr Porunov <alexandr.poru...@gmail.com> wrote: > Hello, > > I read different articles about how to add a new node and they all says > this: > 1) Add a node to ring builder > 2) Rebalance ring > 3) Copy ring to each node. > > Is it possible to skip "copy" step by doing first and second step on each > node? Will then all nodes have the same ring? > I.e. I mean to do like this: > 1) Add a node to the ring builder (Execute this step on each node) > 2) Rebalance the ring (Execute this step on each node) > > Will the ring be the same or we still have to copy the ring from one node > to all others? > > Best regards, > Alexandr > > > _______________________________________________ > > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > Post to : openstack@lists.openstack.org > > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
