<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" class="" style="word-wrap:break-word">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Ugg, That's news to me. :/ Hopefully there's a way around it.<br>
<br>
A different namespace sounds reasonable as a workaround.<br>
<br>
Also consider the use case where you have a newer heat then neutron. During upgrade there may be a time when we very well may want to support one different then the other. So the heat engine should be able to work with whichever is enabled on a particular cloud.<br>
<br>
Thanks,<br>
Kevin<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF467658"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Doug Wiegley [dougwig@parksidesoftware.com]<br>
<b>Sent:</b> Tuesday, September 22, 2015 4:53 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2<br>
</font><br>
</div>
<div></div>
<div>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.
<div class=""><br class="">
</div>
<div class="">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?</div>
<div class=""><br class="">
</div>
<div class="">(I still don’t like that I can’t run both at the same time, and would love to re-litigate that argument. :-) ).</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">doug</div>
<div class=""><br class="">
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Sep 22, 2015, at 5:40 PM, Banashankar KV <<a href="mailto:banveerad@gmail.com" class="" target="_blank">banveerad@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Ok, sounds good. So now the question is how should we name the new V2 resources ?
<div class=""><br class="">
</div>
</div>
<div class="gmail_extra"><br class="" clear="all">
<div class="">
<div class="gmail_signature">
<div dir="ltr" class="">Thanks
<div class="">Banashankar</div>
<div class=""><br class="">
</div>
</div>
</div>
</div>
<br class="">
<div class="gmail_quote">On Tue, Sep 22, 2015 at 4:33 PM, Fox, Kevin M <span dir="ltr" class="">
<<a href="mailto:Kevin.Fox@pnnl.gov" class="" target="_blank">Kevin.Fox@pnnl.gov</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div class="">
<div class="" style="direction:ltr; font-family:Tahoma; font-size:10pt">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.<br class="">
<br class="">
Thanks,<br class="">
Kevin<br class="">
<br class="">
<div class="" style="font-family:'Times New Roman'; font-size:16px">
<hr class="">
<div class="" style="direction:ltr"><font class="" face="Tahoma" size="2"><b class="">From:</b> Banashankar KV [<a href="mailto:banveerad@gmail.com" class="" target="_blank">banveerad@gmail.com</a>]<br class="">
<b class="">Sent:</b> Tuesday, September 22, 2015 4:16 PM
<div class="">
<div class="h5"><br class="">
<b class="">To:</b> OpenStack Development Mailing List (not for usage questions)<br class="">
<b class="">Subject:</b> Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2<br class="">
</div>
</div>
</font><br class="">
</div>
<div class="">
<div class="h5">
<div class=""></div>
<div class="">
<div dir="ltr" class="">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 ?</div>
<div class="gmail_extra"><br class="" clear="all">
<div class="">
<div class="">
<div dir="ltr" class="">Thanks
<div class="">Banashankar</div>
<div class=""><br class="">
</div>
</div>
</div>
</div>
<br class="">
<div class="gmail_quote">On Tue, Sep 22, 2015 at 3:39 PM, Fox, Kevin M <span dir="ltr" class="">
<<a href="mailto:Kevin.Fox@pnnl.gov" class="" target="_blank">Kevin.Fox@pnnl.gov</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
There needs to be a way to have both v1 and v2 supported in one engine....<br class="">
<br class="">
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.<br class="">
<br class="">
Thanks,<br class="">
Kevin<br class="">
________________________________________<br class="">
From: Brandon Logan [<a href="mailto:brandon.logan@RACKSPACE.COM" class="" target="_blank">brandon.logan@RACKSPACE.COM</a>]<br class="">
Sent: Tuesday, September 22, 2015 3:22 PM<br class="">
To: <a href="mailto:openstack-dev@lists.openstack.org" class="" target="_blank">openstack-dev@lists.openstack.org</a><br class="">
<div class="">
<div class="">Subject: Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2<br class="">
<br class="">
Well I'd hate to have the V2 postfix on it because V1 will be deprecated<br class="">
and removed, which means the V2 being there would be lame. Is there any<br class="">
kind of precedent set for for how to handle this?<br class="">
<br class="">
Thanks,<br class="">
Brandon<br class="">
On Tue, 2015-09-22 at 14:49 -0700, Banashankar KV wrote:<br class="">
> So are we thinking of making it as ?<br class="">
> OS::Neutron::LoadBalancerV2<br class="">
><br class="">
> OS::Neutron::ListenerV2<br class="">
><br class="">
> OS::Neutron::PoolV2<br class="">
><br class="">
> OS::Neutron::PoolMemberV2<br class="">
><br class="">
> OS::Neutron::HealthMonitorV2<br class="">
><br class="">
><br class="">
><br class="">
> and add all those into the loadbalancer.py of heat engine ?<br class="">
><br class="">
> Thanks<br class="">
> Banashankar<br class="">
><br class="">
><br class="">
><br class="">
> On Tue, Sep 22, 2015 at 12:52 PM, Sergey Kraynev<br class="">
> <<a href="mailto:skraynev@mirantis.com" class="" target="_blank">skraynev@mirantis.com</a>> wrote:<br class="">
> Brandon.<br class="">
><br class="">
><br class="">
> As I understand we v1 and v2 have differences also in list of<br class="">
> objects and also in relationships between them.<br class="">
> So I don't think that it will be easy to upgrade old resources<br class="">
> (unfortunately).<br class="">
> I'd agree with second Kevin's suggestion about implementation<br class="">
> new resources in this case.<br class="">
><br class="">
><br class="">
> I see, that a lot of guys, who wants to help with it :) And I<br class="">
> suppose, that me and Rabi Mishra may try to help with it,<br class="">
> because we was involvement in implementation of v1 resources<br class="">
> in Heat.<br class="">
> Follow the list of v1 lbaas resources in Heat:<br class="">
><br class="">
><br class="">
> <a href="http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::LoadBalancer" rel="noreferrer" class="" target="_blank">http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::LoadBalancer</a><br class="">
> <a href="http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::Pool" rel="noreferrer" class="" target="_blank">http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::Pool</a><br class="">
><br class="">
> <a href="http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::PoolMember" rel="noreferrer" class="" target="_blank">http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::PoolMember</a><br class="">
><br class="">
> <a href="http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::HealthMonitor" rel="noreferrer" class="" target="_blank">http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutron::HealthMonitor</a><br class="">
><br class="">
><br class="">
><br class="">
> Also, I suppose, that it may be discussed during summit<br class="">
> talks :)<br class="">
> Will add to etherpad with potential sessions.<br class="">
><br class="">
><br class="">
><br class="">
> Regards,<br class="">
> Sergey.<br class="">
><br class="">
> On 22 September 2015 at 22:27, Brandon Logan<br class="">
> <<a href="mailto:brandon.logan@rackspace.com" class="" target="_blank">brandon.logan@rackspace.com</a>> wrote:<br class="">
> There is some overlap, but there was some incompatible<br class="">
> differences when<br class="">
> we started designing v2. I'm sure the same issues<br class="">
> will arise this time<br class="">
> around so new resources sounds like the path to go.<br class="">
> However, I do not<br class="">
> know much about Heat and the resources so I'm speaking<br class="">
> on a very<br class="">
> uneducated level here.<br class="">
><br class="">
> Thanks,<br class="">
> Brandon<br class="">
> On Tue, 2015-09-22 at 18:38 +0000, Fox, Kevin M wrote:<br class="">
> > We're using the v1 resources...<br class="">
> ><br class="">
> > If the v2 ones are compatible and can seamlessly<br class="">
> upgrade, great<br class="">
> ><br class="">
> > Otherwise, make new ones please.<br class="">
> ><br class="">
> > Thanks,<br class="">
> > Kevin<br class="">
> ><br class="">
> ><br class="">
> ______________________________________________________________________<br class="">
> > From: Banashankar KV [<a href="mailto:banveerad@gmail.com" class="" target="_blank">banveerad@gmail.com</a>]<br class="">
> > Sent: Tuesday, September 22, 2015 10:07 AM<br class="">
> > To: OpenStack Development Mailing List (not for<br class="">
> usage questions)<br class="">
> > Subject: Re: [openstack-dev] [neutron][lbaas] - Heat<br class="">
> support for<br class="">
> > LbaasV2<br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> > Hi Brandon,<br class="">
> > Work in progress, but need some input on the way we<br class="">
> want them, like<br class="">
> > replace the existing lbaasv1 or we still need to<br class="">
> support them ?<br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> > Thanks<br class="">
> > Banashankar<br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> > On Tue, Sep 22, 2015 at 9:18 AM, Brandon Logan<br class="">
> > <<a href="mailto:brandon.logan@rackspace.com" class="" target="_blank">brandon.logan@rackspace.com</a>> wrote:<br class="">
> > Hi Banashankar,<br class="">
> > I think it'd be great if you got this going.<br class="">
> One of those<br class="">
> > things we<br class="">
> > want to have and people ask for but has<br class="">
> always gotten a lower<br class="">
> > priority<br class="">
> > due to the critical things needed.<br class="">
> ><br class="">
> > Thanks,<br class="">
> > Brandon<br class="">
> > On Mon, 2015-09-21 at 17:57 -0700,<br class="">
> Banashankar KV wrote:<br class="">
> > > Hi All,<br class="">
> > > I was thinking of starting the work on<br class="">
> heat to support<br class="">
> > LBaasV2, Is<br class="">
> > > there any concerns about that?<br class="">
> > ><br class="">
> > ><br class="">
> > > I don't know if it is the right time to<br class="">
> bring this up :D .<br class="">
> > ><br class="">
> > > Thanks,<br class="">
> > > Banashankar (bana_k)<br class="">
> > ><br class="">
> > ><br class="">
> ><br class="">
> > ><br class="">
> ><br class="">
> __________________________________________________________________________<br class="">
> > > OpenStack Development Mailing List (not<br class="">
> for usage questions)<br class="">
> > > Unsubscribe:<br class="">
> ><br class="">
> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> > ><br class="">
> ><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
> ><br class="">
> ><br class="">
> __________________________________________________________________________<br class="">
> > OpenStack Development Mailing List (not for<br class="">
> usage questions)<br class="">
> > Unsubscribe:<br class="">
> ><br class="">
> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> ><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> ><br class="">
> __________________________________________________________________________<br class="">
> > OpenStack Development Mailing List (not for usage<br class="">
> questions)<br class="">
> > Unsubscribe:<br class="">
> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> ><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
><br class="">
> __________________________________________________________________________<br class="">
> OpenStack Development Mailing List (not for usage<br class="">
> questions)<br class="">
> Unsubscribe:<br class="">
> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
><br class="">
><br class="">
><br class="">
><br class="">
> __________________________________________________________________________<br class="">
> OpenStack Development Mailing List (not for usage questions)<br class="">
> Unsubscribe:<br class="">
> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
><br class="">
><br class="">
><br class="">
> __________________________________________________________________________<br class="">
> OpenStack Development Mailing List (not for usage questions)<br class="">
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="" target="_blank">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</body>
</html>