Open Stack

> How do you handle database high availability and replication?

Especially in my case, I don't care about tokens which will be lost after
first keystone server dies. My services can authenticate again and get new
tokens. It isn't critical. But if in your case it isn't acceptable then I
would have used fernet tokens on your place (but they are a little bit
bigger than uuid tokens). If you need small tokens, fast checks and you
can't lose tokens then I would have used MariaDB Galera Cluster for the
token replication.


On Fri, Sep 30, 2016 at 3:41 PM, Clint Byrum <clint at fewbar.com> wrote:

> Excerpts from Alexandr Porunov's message of 2016-09-20 17:09:06 +0300:
> > Hello everyone,
> >
> > Thank you all for your advice!
> > In my case one keystone server can easily hold a load. I don't need to
> > balance a load between two or more keystone servers. However I need two
> > keystone servers for high availability. So, I decided just to use two
> > keystone servers with the same virtual IP address.
> > Pros:
> > - I can easily configure HA
> > - I don't need to use a master/master replication for a database.
>
> How do you handle database high availability and replication?
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160930/4e3a9a41/attachment.html>