[openstack-dev] [Quantum]How to contribute LBaas driver?
HuYanrui
huyr at arraynetworks.com.cn
Thu Aug 22 07:04:29 UTC 2013
Ilya, or other guys.
As previous mail indicated, we are a Loadbanlancer vendor.
We already developed our driver as Grizzly design requirement.
Now the driver is under internal testing.
Could you guys suggest what's the next move for contributing? Where to post the code and where to require code review?
And we also notice that in Havana there are big changes in LBaas and seems sturcture also changed to support multi vendors.
Is anything we vendor also need change to sync with OpenStack movement?
----- Original Message -----
From: Ilya Shakhat
To: OpenStack Development Mailing List
Sent: Thursday, December 20, 2012 7:27 PM
Subject: Re: [openstack-dev] [Quantum]How to contribute LBaas driver?
Hi Hu,Â
Community plan to develop driver for HAProxy and this driver will be included into Griizly LBaaS by default. Other drivers are not mandatory and may be developed by vendors (we hope they will do this). The API for drivers is not finished yet, draft version is in blueprint https://blueprints.launchpad.net/quantum/+spec/lbaas-driver-api We plan to complete the specification right after G2 milestone.Â
If you want to contribute driver code, the workflow is following:Â
 * write a blueprint describing feature set implemented by driver (e.g. what types of protocols and health monitors are supported)
 * write code and unit tests
 * post code to review and pass it
Overall these steps may take some time, but imho there are chances to get into G release.
Thanks,
Ilya
2012/12/20 HuYanrui <huyr at arraynetworks.com.cn>
Sam, or other guys can help answer this.
I see the new plan is to finish the develop before milestone of grizzly-3(2012/2/21).
And in the session minutes, it will include driver of F5,Citrix,Redware,Brocade.
Who will do the coding of these drivers? The company that owned the device?
We are also contribute our driver based on our Load balance device(based on new LBaas structure), is ther any oppotunity to catch the grizzly schedule?
I know there will be some code review or testing time, right?
Â
----- Original Message -----
From: Samuel Bercovici
To: OpenStack Development Mailing List
Sent: Thursday, December 06, 2012 11:33 PM
Subject: Re: [openstack-dev] [Quantum]How to contribute LBaas driver?
Hi,
Â
The code is part of the standard Quantum trunk.
The blue prints and code containing LBaaS are part of the *new* one.
Â
Regards,
               -Sam.
Â
Â
From: Gavin Mu [mailto:gavin.mu at gmail.com]
Sent: Thursday, December 06, 2012 5:27 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Quantum]How to contribute LBaas driver?
Â
Hi, llya,
Â
Is there an URL of the *new* LBaaS code repo? I did not find anything about LBaaS in quantum code repo, and I am still puzzled with the *current* status after reading that wiki...
Â
is the Quantum/LBaaS/API_1.0 in wiki for the *new* LBaaS? and what is the current status? just a design or have had a runable implementation? I noticed that it is different with the *old* Mirantis/openstack-lbaas one.
Â
I also noticed that there are several blueprints and also codereview which seems related with LBaaS, for example, lbaas-restapi-tenant, is this the *new* one? and currently what can we do if we want to design/code our drivers for the *new* one?
Â
Thanks & Regards,
Gavin
On Thu, Dec 6, 2012 at 6:02 PM, Ilya Shakhat <ishakhat at mirantis.com> wrote:
Mirantis/openstack-lbaas is an "old" version for Essex release. It is a separate project and it was not incorporated with Openstack nor official devstack. The "new" LBaaS is a part of Quantum module and it will be included into upcoming Grizzly release. All information about it is on http://wiki.openstack.org/Quantum/LBaaS
Â
Thanks,
Ilya
Â
Â
2012/12/6 HuYanrui <huyr at arraynetworks.com.cn>
Thanks for Ilya's kindly reply.
I previously got the code from github https://github.com/Mirantis/openstack-lbaas
Seems it's at least 2 months not updated. Is this the old one?
By search the file system of devstack, I did not find cooresponding file "*driver*" like in previous github files.
Seems I need read more in this link http://wiki.openstack.org/Quantum/LBaaS
----- Original Message -----
From: Ilya Shakhat
To: OpenStack Development Mailing List
Sent: Wednesday, December 05, 2012 5:54 PM
Subject: Re: [openstack-dev] [Quantum]How to contribute LBaas driver?
Â
The review process is rather straight-forward, depending on code quality it may require several iterations and a few weeks to be completed.
Â
If you are ready to start writing driver, note that its interface and workflow in Quantum LBaaS will differ from the initial LBaaS version. You may keep an eye on the progress by tracking blueprints on launchpad.net (specifically those that start with 'lbaas-' prefix). Regarding F5 driver - it was implemented for old LBaaS and will be not compatible with new version.
Â
Thanks,
Ilya
2012/12/5 HuYanrui <huyr at arraynetworks.com.cn>
Another question.
If our driver code was ready. How much longer it will take for the code pass review and accepted by openstack project?
I see F5 already have driver published on github, but still not see their code in openstack code.
----- Original Message -----
From: "Sachin Thakkar" <sthakkar at vmware.com>
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
Sent: Monday, November 19, 2012 4:23 PM
Subject: Re: [openstack-dev] [Quantum]How to contribute LBaas driver?
> That's likely because LBaaS as a core quantum feature is just underway for Grizzly. After the framework is in place, the plugins for each specific vendor will likely follow.
>
> Sachin
>
> ----- Original Message -----
> From: "HuYanrui" <huyr at arraynetworks.com.cn>
> To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
> Sent: Monday, November 19, 2012 12:14:19 AM
> Subject: Re: [openstack-dev] [Quantum]How to contribute LBaas driver?
>
> Thanks for Sachin's kindly reply.
> Just one more question:
> I saw F5 published their driver code on github. And LBaas proposal also mentioned F5 bigip.
> But there is no F5 driver in LBaas source on github.
> And I also did not found F5 name in company list of CLA at http://wiki.openstack.org/Contributors/Corporate
> ----- Original Message -----
> From: "Sachin Thakkar" <sthakkar at vmware.com>
> To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
> Sent: Monday, November 19, 2012 3:47 PM
> Subject: Re: [openstack-dev] [Quantum]How to contribute LBaas driver?
>
>
>> Hi Hu,
>>
>> Yes, that is the correct process. We initially were having separate LBaaS discussions during/after the summit but it has now been separated into distinct work items. If you're interested in helping, ping us when we discuss LBaaS during the quantum meeting
>>
>> Cheers,
>> Sachin
>>
>> ----- Original Message -----
>> From: "HuYanrui" <huyr at arraynetworks.com.cn>
>> To: openstack-dev at lists.openstack.org
>> Sent: Sunday, November 18, 2012 11:28:26 PM
>> Subject: [openstack-dev] [Quantum]How to contribute LBaas driver?
>>
>>
>>
>> Guys,
>> Just want to make sure how to contribue LBaas driver (commercial)?
>> Is this process same with contribute plugin in quantum like this page? -
>> http://wiki.openstack.org/QuantumDevelopment
>>
>>
>>
>> Hu Yanrui
>>
>> Array Networks Inc.
>>
>> Tel: 86 010-84446688 ext 259
>>
>> E-mail : huyr at arraynetworks.com.cn
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Â
------------------------------------------------------------------------
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Â
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Â
--------------------------------------------------------------------------
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
------------------------------------------------------------------------------
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130822/d08382c6/attachment.html>
More information about the OpenStack-dev
mailing list