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