Hi Vivek and LBaaS folks, I added [horizon] tag so that Horizon folks can be aware of this thread.
Before jumping into LBaaS specific topic, let me share the current effort As you may know, Horizon team itself is exploring a way how to make development of each panel fast and smooth. - One example is a separate repository like designate-dashboard as I mentioned in the last mail. This kind of repositories can be maintained by both the horizon team and the service team (designate-core for designate-dashboard). - Another example is 'contrib' directory in the horizon main repository. Sahara dashboard is being moved to contrib directory now. It is done by the same motivation as the first example. Honestly I don't fully understand how it works (subdirectory core reviewers). I think David, Horizon PTL, can explain more detail. - Of course, we have third option as you mentioned: a dedicated directory under neutron-lbaas repository. If we would like to maintain LBaaS dashboard repository separately for long term, First two options look good to me because Horizon developers are easy to find a repository. Now I return to LBaaS related topic I think we need to consider this from two perspective: technical perspective and release management perspective. Technically I don't see a problem so far. As far as I check LBaaS v1 dashboard, there is no references from outside of LBaaS panel so we can easily move it to a separate place. One exception is Floating IP panel. It is aware of Load balancer VIP port. Horizon does not have a way to customize existing forms at now, so we can need to change codes in Horizon repo for such case, but I think it is a special case and I hope it is not a burden. >From the release management and consumer perspective, If we move LBaaS dashboard to some other place, users need to install it separately though they don't need to do more previously. It may be a big problem but we need to keep it in my mind. Another thing is how to manage the release process. Who is responsible for the release, Neutron or Horizon? I don't have strong opinion on choices. I would like to hear David's opinion. I will ask him to join the discussion. Thanks, Akihiro 2015-07-15 2:22 GMT+09:00 Jain, Vivek <vivekj...@ebay.com>: > Thanks Akihiro. Currently lbaas panels are part of horizon repo. If > there is a easy way to de-couple lbaas dashboard from horizon? I think that > will simplify development efforts. What does it take to separate lbaas > dashboard from horizon? > > Thanks, > Vivek > > From: Akihiro Motoki <amot...@gmail.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Tuesday, July 14, 2015 at 10:09 AM > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Cc: "Balle, Susanne" <susanne.ba...@hp.com>, "Tonse, Milan" < > mto...@ebay.com> > > Subject: Re: [openstack-dev] [neutron][lbaas] Horizon support for > neutron-lbaas v2 > > Another option is to create a project under openstack. > designate-dashboard project takes this approach, > and the core team of the project is both horizon-core and designate-core. > We can do the similar approach. Thought? > > I have one question. > Do we have a separate place forever or do we want to merge horizon repo > once the implementation are available. > If we have a separate repo for LBaaS v2 panel, we need to release it > separately. > > I am not sure I am available at LBaaS meeting, but I would like to help > this efforts as a core from horizon and neutron. > > Akihiro > > > 2015-07-15 1:52 GMT+09:00 Doug Wiegley <doug...@parksidesoftware.com>: > >> I’d be good submitting it to the neutron-lbaas repo, under a horizon/ >> directory. We can iterate there, and talk with the Horizon team about how >> best to integrate. Would that work? >> >> Thanks, >> doug >> >> > On Jul 13, 2015, at 3:05 PM, Jain, Vivek <vivekj...@ebay.com> wrote: >> > >> > Hi German, >> > >> > We integrated UI with LBaaS v2 GET APIs. We have created all panels for >> > CREATE and UPDATE as well. >> > Plan is to share our code with community on stackforge for more >> > collaboration from the community. >> > >> > So far Ganesh from cisco has shown interest in helping with some work. >> It >> > will be great if we can get more hands. >> > >> > Q: what is the process for hosting in-progress project on stackforge? >> Can >> > someone help me here? >> > >> > Thanks, >> > Vivek >> > >> > On 7/10/15, 11:40 AM, "Eichberger, German" <german.eichber...@hp.com> >> > wrote: >> > >> >> Hi Vivek, >> >> >> >> Hope things are well. With the Midccyle next week I am wondering if you >> >> made any progress and/or how we can best help with the panels. >> >> >> >> Thanks, >> >> German >> >> >> >> From: "Jain, Vivek" <vivekj...@ebay.com<mailto:vivekj...@ebay.com>> >> >> Reply-To: "OpenStack Development Mailing List (not for usage >> questions)" >> >> <openstack-dev@lists.openstack.org<mailto: >> openstack-...@lists.openstack.or >> >> g>> >> >> Date: Wednesday, April 8, 2015 at 3:32 PM >> >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> <openstack-dev@lists.openstack.org<mailto: >> openstack-...@lists.openstack.or >> >> g>> >> >> Cc: "Balle Balle, Susanne" >> >> <susanne.ba...@hp.com<mailto:susanne.ba...@hp.com>>, "Tonse, Milan" >> >> <mto...@ebay.com<mailto:mto...@ebay.com>> >> >> Subject: Re: [openstack-dev] [neutron][lbaas] Horizon support for >> >> neutron-lbaas v2 >> >> >> >> Thanks German for the etherpad link. If you have any documentation for >> >> flows, please share those too. >> >> >> >> I will work with my team at ebay to publish wireframes for design we >> are >> >> working on. It will be mostly along the lines I demo’ed in Paris. >> >> >> >> Thanks, >> >> Vivek >> >> >> >> From: <Eichberger>, German >> >> <german.eichber...@hp.com<mailto:german.eichber...@hp.com>> >> >> Reply-To: "OpenStack Development Mailing List (not for usage >> questions)" >> >> <openstack-dev@lists.openstack.org<mailto: >> openstack-...@lists.openstack.or >> >> g>> >> >> Date: Wednesday, April 8, 2015 at 11:24 AM >> >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> <openstack-dev@lists.openstack.org<mailto: >> openstack-...@lists.openstack.or >> >> g>> >> >> Cc: "Balle, Susanne" <susanne.ba...@hp.com<mailto:susanne.ba...@hp.com >> >> >> >> Subject: Re: [openstack-dev] [neutron][lbaas] Horizon support for >> >> neutron-lbaas v2 >> >> >> >> Hi, >> >> >> >> We briefly talked about it a few Neutron meetings back (LBaaS is now on >> >> demand) and created an etherpad to track things: >> >> https://etherpad.openstack.org/p/LBaaS_Horizon_Use_Cases >> >> >> >> Susanne and I met with HP’s UX designer to work on the design for some >> >> flows for the Horizon panel (cc’d) but I am glad that Vivek is taking >> the >> >> lead. Please check that etherpad for more information and feel free to >> >> update as things happen… >> >> >> >> Thanks, >> >> German >> >> >> >> >> >> From: Jain, Vivek [mailto:vivekj...@ebay.com] >> >> Sent: Tuesday, April 07, 2015 9:01 AM >> >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: Re: [openstack-dev] [neutron][lbaas] Horizon support for >> >> neutron-lbaas v2 >> >> >> >> Hi Evgeny, >> >> We have just started working on Horizon lbaasv2 support. I have to sync >> >> up with my team on the time-line but it is not targeted for Kilo >> release. >> >> Since it is a major effort, we will need more hands. Let me know if >> >> anyone is interested to contribute. >> >> >> >> On a related note, Do we have a sample code which uses neutronclient >> >> lbaas v2 methods? That will greatly speedup our horizon integration. >> >> >> >> Thanks, >> >> Vivek >> >> >> >> From: Phillip Toohill >> >> <phillip.tooh...@rackspace.com<mailto:phillip.tooh...@rackspace.com>> >> >> Reply-To: "OpenStack Development Mailing List (not for usage >> questions)" >> >> <openstack-dev@lists.openstack.org<mailto: >> openstack-...@lists.openstack.or >> >> g>> >> >> Date: Tuesday, April 7, 2015 at 7:50 AM >> >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> <openstack-dev@lists.openstack.org<mailto: >> openstack-...@lists.openstack.or >> >> g>> >> >> Subject: Re: [openstack-dev] [neutron][lbaas] Horizon support for >> >> neutron-lbaas v2 >> >> >> >> >> >> Hey Evgeny, >> >> >> >> >> >> >> >> I believe Vivek is working on Horizon lbaasv2 support. We werent given >> a >> >> timeline or anything but sounds like its being actively worked on. I >> >> would reach out to him to get better timelines if concerned. >> >> >> >> >> >> Phillip V. Toohill III >> >> Software Developer >> >> [ >> http://600a2794aa4ab5bae6bd-8d3014ab8e4d12d3346853d589a26319.r53.cf1.rack >> >> cdn.com/signatures/images/rackspace_logo.png] >> >> phone: 210-312-4366 >> >> mobile: 210-440-8374 >> >> >> >> ________________________________ >> >> From: Evgeny Fedoruk <evge...@radware.com<mailto:evge...@radware.com>> >> >> Sent: Tuesday, April 7, 2015 5:50 AM >> >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: [openstack-dev] [neutron][lbaas] Horizon support for >> >> neutron-lbaas v2 >> >> >> >> Hi guys, >> >> >> >> LBaaS v2 has no horizon support as for now and I want to know if this >> >> work is planned to be done and , if yes, in what time frame. >> >> Is there a plan to develop it for Kilo or for L release? >> >> >> >> Thanks, >> >> Evg >> >> >> __________________________________________________________________________ >> >> OpenStack Development Mailing List (not for usage questions) >> >> Unsubscribe: >> >> openstack-dev-requ...@lists.openstack.org<mailto: >> OpenStack-dev-request@lis >> >> ts.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-requ...@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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
