Excerpts from Alexandr Porunov's message of 2016-09-30 18:51:02 +0300:
> > 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
> toke
> 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
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
On Sep 21, 2016, at 6:48 AM, Van Leeuwen, Robert wrote:
> If I had these constraints I would add a loadbalancer-config on the same
> machine that runs the OpenStack apis.
Now that I have multiple Neutron instances, how do I make my routers
HA?
I managed to make the router 'distributed', but the
Also, if you haven't changed default parameter for token cache time then it
has 5 min of cache (you can increase this time if you want). So, your 15-16
machines (or less if some of them doesn't use keystone like swift object,
container, account nodes) will use requests to keystone only once in 5
mi
> That is more like a hot-standby (only one server is used at any one time)
> and I guess that's an option as well. But because I have limited
resources,
> I'd prefer, if possible, to use all of them all the time.
Wrong. It depends on how you configured you cluster. You can point half of
your mach
>> Also you can use peacemaker and other stuff to reach high availability
>Yes, but I'm guessing those need _another_ machine in front of the ones
> I want to load balance. And if that goes down, EVERYTHING stops working.
> Unless they are clustered, which require _even more_ machines!
If
On Sep 20, 2016, at 10:06 PM, Alexandr Porunov wrote:
> If you care about high availability (as I do) then you need to have
> additional keystone instance which will prevent your cluster from SPOF.
That was the idea. One node is already dedicated for that, but I haven't
installed it yet, because
I think that I haven't understood your situation correctly but I will try
to suggest something:
If you have a big load on your keystone server you can spread the load
between two or more servers by using load balancers like HAProxy. But it
wouldn't work if keystone instances not shared tokens with
On Sep 20, 2016, at 3:09 PM, Alexandr Porunov wrote:
> So, I decided just to use two keystone servers with the same virtual IP
> address.
Now that you've made your decision, I'd like to ask some
followup questions for my own decision if I may.
Most everyone have talked about some kind of load
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
>
> Hello,
>
> I am thinking about using the keystone as an authentication system but I am
> afraid about failures which can affect all the cluster. In fact if the
> keystone server dies then our full cluster will stop. It would be better if
> we could use HA with the keystone. Then if > our pri
Excerpts from Alexandr Porunov's message of 2016-09-19 21:46:54 +0300:
> Hello,
>
> I am thinking about using the keystone as an authentication system but I am
> afraid about failures which can affect all the cluster. In fact if the
> keystone server dies then our full cluster will stop. It would
If you'd like to avoid the pain of configuring this manually, Helion
OpenStack has many HA features enabled by default:
http://docs.hpcloud.com/#3.x/helion/planning/high_availability.html
On Mon, Sep 19, 2016 at 2:10 PM, Alexandr Porunov
wrote:
> Thank you for pointing on it. I haven't yet use p
Thank you for pointing on it. I haven't yet use pacemaker but I will try to
configure it.
Sincerely,
Alexandr
On Mon, Sep 19, 2016 at 10:23 PM, Remo Mattei wrote:
> There is already ha options with pacemaker and corosync. Have you looked
> at that?
>
> Inviato da iPhone
>
> Il giorno 19 set 201
There is already ha options with pacemaker and corosync. Have you looked at
that?
Inviato da iPhone
> Il giorno 19 set 2016, alle ore 11:46, Alexandr Porunov
> ha scritto:
>
> Hello,
>
> I am thinking about using the keystone as an authentication system but I am
> afraid about failures whi
16 matches
Mail list logo
