[openstack-dev] [Magnum] Bug 1541105 options
Hongbin Lu
hongbin.lu at huawei.com
Wed Feb 3 21:25:36 UTC 2016
I would vote for a quick fix + a blueprint.
BTW, I think it is a general consensus that we should move away from Atomic for various reasons (painful image building, lack of document, hard to use, etc.). We are working on fixing the CoreOS templates which could replace Atomic in the future.
Best regards,
Hongbin
From: Corey O'Brien [mailto:coreypobrien at gmail.com]
Sent: February-03-16 2:53 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Bug 1541105 options
As long as configurations for 2.2 and 2.0 are compatible we shouldn't have an issue I wouldn't think. I just don't know enough about etcd deployment to be sure about that.
If we want to quickly improve the gate, I can patch the problematic areas in the templates and then we can make a blueprint for upgrading to Atomic 23.
Corey
On Wed, Feb 3, 2016 at 1:47 PM Vilobh Meshram <vilobhmeshram.openstack at gmail.com<mailto:vilobhmeshram.openstack at gmail.com>> wrote:
Hi Corey,
This is slowing down our merge rate and needs to be fixed IMHO.
What risk are you talking about when using newer version of etcd ? Is it documented somewhere for the team to have a look ?
-Vilobh
On Wed, Feb 3, 2016 at 8:11 AM, Corey O'Brien <coreypobrien at gmail.com<mailto:coreypobrien at gmail.com>> wrote:
Hey team,
I've been looking into https://bugs.launchpad.net/magnum/+bug/1541105 which covers a bug with etcdctl, and I wanted opinions on how best to fix it.
Should we update the image to include the latest version of etcd? Or, should we temporarily install the latest version as a part of notify-heat (see bug for patch)?
I'm personally in favor of updating the image, but there is presumably some small risk with using a newer version of etcd.
Thanks,
Corey O'Brien
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160203/07967e35/attachment.html>
More information about the OpenStack-dev
mailing list