[openstack-dev] [magnum] High Availability
hongbin.lu at huawei.com
Thu Mar 17 18:59:45 UTC 2016
The problem of missing Barbican alternative implementation has been raised several times by different people. IMO, this is a very serious issue that will hurt Magnum adoption. I created a blueprint for that  and set the PTL as approver. It will be picked up by a contributor once it is approved.
From: Ricardo Rocha [mailto:rocha.porto at gmail.com]
Sent: March-17-16 2:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] High Availability
We're on the way, the API is using haproxy load balancing in the same way all openstack services do here - this part seems to work fine.
For the conductor we're stopped due to bay certificates - we don't currently have barbican so local was the only option. To get them accessible on all nodes we're considering two options:
- store bay certs in a shared filesystem, meaning a new set of credentials in the boxes (and a process to renew fs tokens)
- deploy barbican (some bits of puppet missing we're sorting out)
More news next week.
On Thu, Mar 17, 2016 at 6:46 PM, Daneyon Hansen (danehans) <danehans at cisco.com> wrote:
> Does anyone have experience deploying Magnum in a highly-available fashion?
> If so, I’m interested in learning from your experience. My biggest
> unknown is the Conductor service. Any insight you can provide is
> greatly appreciated.
> Daneyon Hansen
> ____ OpenStack Development Mailing List (not for usage questions)
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev