[openstack-dev] [neutron][lbaas] - Heat support for LbaasV2
Brandon Logan
brandon.logan at RACKSPACE.COM
Wed Sep 23 00:36:10 UTC 2015
I do like Doug's suggestion of namespace change. One day lbaas will no
longer be an extension of neutron (at least that is my hope and it seems
to be going in that direction), and thus the only reason to be
considered part of neutron is just a logical grouping of networking
services.
Cutting the rant short, is that namespace change enough to avoid all
naming collisions between v1 and v2?
Thanks,
Brandon
On Tue, 2015-09-22 at 17:00 -0700, Banashankar KV wrote:
> But whatever it is, I think we can't run the current heat template as
> it is for v2, those things must be ported no matter what.
> So I think our main concern here is coexistence of v1 and v2 heat
> support.
>
>
> Please correct me if I am wrong.
>
> Thanks
> Banashankar
>
>
>
> On Tue, Sep 22, 2015 at 4:53 PM, Doug Wiegley
> <dougwig at parksidesoftware.com> wrote:
> The other option would be to change the namespace. (Os::Lbaas
> instead of Os::Neutron). The neutron CLI does something
> similar with neutron-lb-* versus neutron-lbaas-*, e.g.
>
>
> One wrinkle with heat supporting both is that neutron doesn’t
> support both running at the same time, which certainly hurts
> the migration strategy. I think the answer at the time was
> that you could have different api servers running each
> version. Is that something that heat can deal with?
>
>
> (I still don’t like that I can’t run both at the same time,
> and would love to re-litigate that argument. :-) ).
>
>
> Thanks,
> doug
>
>
>
>
> > On Sep 22, 2015, at 5:40 PM, Banashankar KV
> > <banveerad at gmail.com> wrote:
> >
> > Ok, sounds good. So now the question is how should we name
> > the new V2 resources ?
> >
> >
> >
> > Thanks
> > Banashankar
> >
> >
> >
> > On Tue, Sep 22, 2015 at 4:33 PM, Fox, Kevin M
> > <Kevin.Fox at pnnl.gov> wrote:
> > Yes, hence the need to support the v2 resources as
> > seperate things. Then I can rewrite the templates to
> > include the new resources rather then the old
> > resources as appropriate. IE, it will be a porting
> > effort to rewrite them. Then do a heat update on the
> > stack to migrate it from lbv1 to lbv2. Since they
> > are different resources, it should create the new
> > and delete the old.
> >
> > Thanks,
> > Kevin
> >
> >
> > ____________________________________________________
> > From: Banashankar KV [banveerad at gmail.com]
> > Sent: Tuesday, September 22, 2015 4:16 PM
> >
> > To: OpenStack Development Mailing List (not for
> > usage questions)
> > Subject: Re: [openstack-dev] [neutron][lbaas] - Heat
> > support for LbaasV2
> >
> >
> >
> >
> > But I think, V2 has introduced some new components
> > and whole association of the resources with each
> > other is changed, we should be still able to do what
> > Kevin has mentioned ?
> >
> > Thanks
> > Banashankar
> >
> >
> >
> > On Tue, Sep 22, 2015 at 3:39 PM, Fox, Kevin M
> > <Kevin.Fox at pnnl.gov> wrote:
> > There needs to be a way to have both v1 and
> > v2 supported in one engine....
> >
> > Say I have templates that use v1 already in
> > existence (I do), and I want to be able to
> > heat stack update on them one at a time to
> > v2. This will replace the v1 lb with v2,
> > migrating the floating ip from the v1 lb to
> > the v2 one. This gives a smoothish upgrade
> > path.
> >
> > Thanks,
> > Kevin
> > ________________________________________
> > From: Brandon Logan
> > [brandon.logan at RACKSPACE.COM]
> > Sent: Tuesday, September 22, 2015 3:22 PM
> > To: openstack-dev at lists.openstack.org
> > Subject: Re: [openstack-dev]
> > [neutron][lbaas] - Heat support for LbaasV2
> >
> > Well I'd hate to have the V2 postfix on it
> > because V1 will be deprecated
> > and removed, which means the V2 being there
> > would be lame. Is there any
> > kind of precedent set for for how to handle
> > this?
> >
> > Thanks,
> > Brandon
> > On Tue, 2015-09-22 at 14:49 -0700,
> > Banashankar KV wrote:
> > > So are we thinking of making it as ?
> > > OS::Neutron::LoadBalancerV2
> > >
> > > OS::Neutron::ListenerV2
> > >
> > > OS::Neutron::PoolV2
> > >
> > > OS::Neutron::PoolMemberV2
> > >
> > > OS::Neutron::HealthMonitorV2
> > >
> > >
> > >
> > > and add all those into the loadbalancer.py
> > of heat engine ?
> > >
> > > Thanks
> > > Banashankar
> > >
> > >
> > >
> > > On Tue, Sep 22, 2015 at 12:52 PM, Sergey
> > Kraynev
> > > <skraynev at mirantis.com> wrote:
> > > Brandon.
> > >
> > >
> > > As I understand we v1 and v2 have
> > differences also in list of
> > > objects and also in relationships
> > between them.
> > > So I don't think that it will be
> > easy to upgrade old resources
> > > (unfortunately).
> > > I'd agree with second Kevin's
> > suggestion about implementation
> > > new resources in this case.
> > >
> > >
> > > I see, that a lot of guys, who
> > wants to help with it :) And I
> > > suppose, that me and Rabi Mishra
> > may try to help with it,
> > > because we was involvement in
> > implementation of v1 resources
> > > in Heat.
> > > Follow the list of v1 lbaas
> > resources in Heat:
> > >
> > >
> > >
> > http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::LoadBalancer
> > >
> > http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::Pool
> > >
> > >
> > http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::PoolMember
> > >
> > >
> > http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::HealthMonitor
> > >
> > >
> > >
> > > Also, I suppose, that it may be
> > discussed during summit
> > > talks :)
> > > Will add to etherpad with
> > potential sessions.
> > >
> > >
> > >
> > > Regards,
> > > Sergey.
> > >
> > > On 22 September 2015 at 22:27,
> > Brandon Logan
> > > <brandon.logan at rackspace.com>
> > wrote:
> > > There is some overlap, but
> > there was some incompatible
> > > differences when
> > > we started designing v2.
> > I'm sure the same issues
> > > will arise this time
> > > around so new resources
> > sounds like the path to go.
> > > However, I do not
> > > know much about Heat and
> > the resources so I'm speaking
> > > on a very
> > > uneducated level here.
> > >
> > > Thanks,
> > > Brandon
> > > On Tue, 2015-09-22 at
> > 18:38 +0000, Fox, Kevin M wrote:
> > > > We're using the v1
> > resources...
> > > >
> > > > If the v2 ones are
> > compatible and can seamlessly
> > > upgrade, great
> > > >
> > > > Otherwise, make new ones
> > please.
> > > >
> > > > Thanks,
> > > > Kevin
> > > >
> > > >
> > >
> > ______________________________________________________________________
> > > > From: Banashankar KV
> > [banveerad at gmail.com]
> > > > Sent: Tuesday, September
> > 22, 2015 10:07 AM
> > > > To: OpenStack
> > Development Mailing List (not for
> > > usage questions)
> > > > Subject: Re:
> > [openstack-dev] [neutron][lbaas] - Heat
> > > support for
> > > > LbaasV2
> > > >
> > > >
> > > >
> > > > Hi Brandon,
> > > > Work in progress, but
> > need some input on the way we
> > > want them, like
> > > > replace the existing
> > lbaasv1 or we still need to
> > > support them ?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Thanks
> > > > Banashankar
> > > >
> > > >
> > > >
> > > > On Tue, Sep 22, 2015 at
> > 9:18 AM, Brandon Logan
> > > >
> > <brandon.logan at rackspace.com> wrote:
> > > > Hi Banashankar,
> > > > I think it'd be
> > great if you got this going.
> > > One of those
> > > > things we
> > > > want to have and
> > people ask for but has
> > > always gotten a lower
> > > > priority
> > > > due to the
> > critical things needed.
> > > >
> > > > Thanks,
> > > > Brandon
> > > > On Mon,
> > 2015-09-21 at 17:57 -0700,
> > > Banashankar KV wrote:
> > > > > Hi All,
> > > > > I was thinking
> > of starting the work on
> > > heat to support
> > > > LBaasV2, Is
> > > > > there any
> > concerns about that?
> > > > >
> > > > >
> > > > > I don't know
> > if it is the right time to
> > > bring this up :D .
> > > > >
> > > > > Thanks,
> > > > > Banashankar
> > (bana_k)
> > > > >
> > > > >
> > > >
> > > > >
> > > >
> > >
> > __________________________________________________________________________
> > > > > OpenStack
> > Development Mailing List (not
> > > for usage questions)
> > > > > Unsubscribe:
> > > >
> > >
> > OpenStack-dev-request at 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://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://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://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://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://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://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://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://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://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://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://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list