<div dir="ltr">Resource I mean, the resource type as highlighted. <div><br><div><div>description: A simple lb pool test</div><div>heat_template_version: '2015-04-30'</div><div>resources:</div><div> my_listener:</div><div> type: OS::Neutron::<b>ListenerV2</b></div><div> properties:</div><div> protocol_port: 88</div><div> protocol: HTTP</div><div> loadbalancer_id: e3e0b1d2-12b2-4855-a5cb-6faf121b2d10</div><div> name: holy_listener</div><div> description: Just a listener man</div><div> </div></div></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:45 PM, Brandon Logan <span dir="ltr"><<a href="mailto:brandon.logan@rackspace.com" target="_blank">brandon.logan@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Forgive my ignorance on this, but by resources are we talking about API<br>
resources? If so I would hate V2 to be in the names because backwards<br>
compatibility means keeping that around. If they're not API resources,<br>
then if we named appended the resources with V2 right now, will we be<br>
able to remove the V2 once V1 gets removed?<br>
<br>
Thanks,<br>
Brandon<br>
<span class="">On Tue, 2015-09-22 at 16:40 -0700, Banashankar KV wrote:<br>
> Ok, sounds good. So now the question is how should we name the new V2<br>
> resources ?<br>
><br>
><br>
><br>
> Thanks<br>
> Banashankar<br>
><br>
><br>
><br>
> On Tue, Sep 22, 2015 at 4:33 PM, Fox, Kevin M <<a href="mailto:Kevin.Fox@pnnl.gov">Kevin.Fox@pnnl.gov</a>><br>
> wrote:<br>
> Yes, hence the need to support the v2 resources as seperate<br>
> things. Then I can rewrite the templates to include the new<br>
> resources rather then the old resources as appropriate. IE, it<br>
> will be a porting effort to rewrite them. Then do a heat<br>
> update on the stack to migrate it from lbv1 to lbv2. Since<br>
> they are different resources, it should create the new and<br>
> delete the old.<br>
><br>
> Thanks,<br>
> Kevin<br>
><br>
><br>
</span>> ______________________________________________________________<br>
<div class="HOEnZb"><div class="h5">> From: Banashankar KV [<a href="mailto:banveerad@gmail.com">banveerad@gmail.com</a>]<br>
> Sent: Tuesday, September 22, 2015 4:16 PM<br>
><br>
> To: OpenStack Development Mailing List (not for usage<br>
> questions)<br>
> Subject: Re: [openstack-dev] [neutron][lbaas] - Heat support<br>
> for LbaasV2<br>
><br>
><br>
><br>
><br>
> But I think, V2 has introduced some new components and whole<br>
> association of the resources with each other is changed, we<br>
> should be still able to do what Kevin has mentioned ?<br>
><br>
> Thanks<br>
> Banashankar<br>
><br>
><br>
><br>
> On Tue, Sep 22, 2015 at 3:39 PM, Fox, Kevin M<br>
> <<a href="mailto:Kevin.Fox@pnnl.gov">Kevin.Fox@pnnl.gov</a>> wrote:<br>
> There needs to be a way to have both v1 and v2<br>
> supported in one engine....<br>
><br>
> Say I have templates that use v1 already in existence<br>
> (I do), and I want to be able to heat stack update on<br>
> them one at a time to v2. This will replace the v1 lb<br>
> with v2, migrating the floating ip from the v1 lb to<br>
> 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">brandon.logan@RACKSPACE.COM</a>]<br>
> Sent: Tuesday, September 22, 2015 3:22 PM<br>
> To: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
> Subject: Re: [openstack-dev] [neutron][lbaas] - Heat<br>
> support for LbaasV2<br>
><br>
> Well I'd hate to have the V2 postfix on it because V1<br>
> will be deprecated<br>
> and removed, which means the V2 being there would be<br>
> 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<br>
> 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<br>
> 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">skraynev@mirantis.com</a>> wrote:<br>
> > Brandon.<br>
> ><br>
> ><br>
> > As I understand we v1 and v2 have<br>
> differences also in list of<br>
> > objects and also in relationships between<br>
> them.<br>
> > So I don't think that it will be easy to<br>
> upgrade old resources<br>
> > (unfortunately).<br>
> > I'd agree with second Kevin's suggestion<br>
> about implementation<br>
> > new resources in this case.<br>
> ><br>
> ><br>
> > I see, that a lot of guys, who wants to help<br>
> with it :) And I<br>
> > suppose, that me and Rabi Mishra may try to<br>
> help with it,<br>
> > because we was involvement in implementation<br>
> of v1 resources<br>
> > in Heat.<br>
> > Follow the list of v1 lbaas resources in<br>
> Heat:<br>
> ><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>
> ><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>
> ><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>
> ><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<br>
> during summit<br>
> > talks :)<br>
> > Will add to etherpad with potential<br>
> 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">brandon.logan@rackspace.com</a>> wrote:<br>
> > There is some overlap, but there was<br>
> some incompatible<br>
> > differences when<br>
> > we started designing v2. I'm sure<br>
> the same issues<br>
> > will arise this time<br>
> > around so new resources sounds like<br>
> the path to go.<br>
> > However, I do not<br>
> > know much about Heat and the<br>
> 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,<br>
> Fox, Kevin M wrote:<br>
> > > We're using the v1 resources...<br>
> > ><br>
> > > If the v2 ones are compatible and<br>
> can seamlessly<br>
> > upgrade, great<br>
> > ><br>
> > > Otherwise, make new ones please.<br>
> > ><br>
> > > Thanks,<br>
> > > Kevin<br>
> > ><br>
> > ><br>
> ><br>
> ______________________________________________________________________<br>
> > > From: Banashankar KV<br>
> [<a href="mailto:banveerad@gmail.com">banveerad@gmail.com</a>]<br>
> > > Sent: Tuesday, September 22, 2015<br>
> 10:07 AM<br>
> > > To: OpenStack Development Mailing<br>
> List (not for<br>
> > usage questions)<br>
> > > Subject: Re: [openstack-dev]<br>
> [neutron][lbaas] - Heat<br>
> > support for<br>
> > > LbaasV2<br>
> > ><br>
> > ><br>
> > ><br>
> > > Hi Brandon,<br>
> > > Work in progress, but need some<br>
> input on the way we<br>
> > want them, like<br>
> > > replace the existing lbaasv1 or we<br>
> 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,<br>
> Brandon Logan<br>
> > > <<a href="mailto:brandon.logan@rackspace.com">brandon.logan@rackspace.com</a>><br>
> wrote:<br>
> > > Hi Banashankar,<br>
> > > I think it'd be great if<br>
> you got this going.<br>
> > One of those<br>
> > > things we<br>
> > > want to have and people<br>
> ask for but has<br>
> > always gotten a lower<br>
> > > priority<br>
> > > due to the critical things<br>
> needed.<br>
> > ><br>
> > > Thanks,<br>
> > > Brandon<br>
> > > On Mon, 2015-09-21 at<br>
> 17:57 -0700,<br>
> > Banashankar KV wrote:<br>
> > > > Hi All,<br>
> > > > I was thinking of<br>
> starting the work on<br>
> > heat to support<br>
> > > LBaasV2, Is<br>
> > > > there any concerns about<br>
> that?<br>
> > > ><br>
> > > ><br>
> > > > I don't know if it is<br>
> the right time to<br>
> > bring this up :D .<br>
> > > ><br>
> > > > Thanks,<br>
> > > > Banashankar (bana_k)<br>
> > > ><br>
> > > ><br>
> > ><br>
> > > ><br>
> > ><br>
> ><br>
> __________________________________________________________________________<br>
> > > > OpenStack Development<br>
> Mailing List (not<br>
> > for usage questions)<br>
> > > > Unsubscribe:<br>
> > ><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>
> ><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<br>
> Mailing List (not for<br>
> > usage questions)<br>
> > > Unsubscribe:<br>
> > ><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>
> > ><br>
> ><br>
> __________________________________________________________________________<br>
> > > OpenStack Development Mailing List<br>
> (not for usage<br>
> > 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<br>
> (not for usage<br>
> > 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>
> __________________________________________________________________________<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>
> 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>
</div></div></blockquote></div><br></div>