Yellow alert:
1. Magnum depends on lbaasv1
2. lbaasv2 cannot be installed together with lbaasv1
3. lbaasv1 has serious design issues (Like: having multiple listener on the same ip)
4. magnum's lbaasv2 support is not ready [1]
5. The lbaasv1->lbaasv2 `upgrade`, is not invisible to the users [2],
and likely will causes issues with the existing bays or
to any heat stacks which, used the old lbaasv1.
IMHO before anyone would create a long term plan with magnum,
he should wait at least for [1] completion or have a good answer what
will he do when he upgrades to lbaasv2.
[1]
https://blueprints.launchpad.net/magnum/+spec/magnum-lbaasv2-support
[2]
https://review.openstack.org/#/c/289595/
----- Original Message -----
From: "David Moreau Simard" <dms(a)redhat.com>
To: "Chandan kumar" <chkumar246(a)gmail.com>
Cc: strigazi(a)gmail.com, "rdo-list" <rdo-list(a)redhat.com>
Sent: Tuesday, March 29, 2016 3:54:31 PM
Subject: Re: [Rdo-list] What magnum status in RDO Mitaka is supposed to be ?
On Tue, Mar 29, 2016 at 9:04 AM, Chandan kumar <chkumar246(a)gmail.com> wrote:
> curl -O
http://trunk.rdoproject.org/centos7/delorean-deps.repo
> curl -O
http://trunk.rdoproject.org/centos7/current-passed-ci/delorean.repo
Please note that "centos7" is newton and is untested right now.
centos7-mitaka should be used for the latest tested trunk repositories.
I posted to the list about it recently [1].
[1]:
https://www.redhat.com/archives/rdo-list/2016-March/msg00135.html
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com