Hi folks,
At last group meeting we decided upon a new meeting time for our
bi-weekly meetings - new meeting time is: *Thursdays 1400 UTC odd weeks
in IRC channel #openstack-publiccloud*
Wiki and official calendar file are updated accordingly.
During last meeting we touched on the subject "Fo
Looping the list back in since I accidentally dropped it yet again :/
On Mon, Mar 19, 2018 at 8:45 AM, Torin Woltjer
wrote:
> That's good to know, thank you. Out of curiousity, without
> pacemaker/chorosync, does haproxy have the capability to manage a floating
> ip and failover etc?
>
HAProxy c
As far as that goes, if you have 2 haproxies you might as well use both. Use 2
VIPs and DNS round robin between them, configure keepalived to have each
haproxy node take one VIP as primary with the other node’s VIP as backup. This
has worked well for me for the past couple of years.
vrrp_inst
Erik McCormick wrote:
Looping the list back in since I accidentally dropped it yet again :/
On Mon, Mar 19, 2018 at 8:45 AM, Torin Woltjer
wrote:
That's good to know, thank you. Out of curiousity, without
pacemaker/chorosync, does haproxy have the capability to manage a floating
ip and failov
Hi all,
This has turned into a bit of a screed I'm afraid...
Last week I had pings from both the folks at CERN and Catalyst Cloud about
GPU-accelerated OpenStack instances with PCI passthrough, specifically
asking about the security issues I've mentioned in community forums
previously, and any ot
