Thank you for these interesting points. I will review my code before initiate the pull request. I have just created my account in JIRA. So you can find my name now.
best, Frédéric -----Everett Toews <[email protected]> a écrit : ----- A : "[email protected]" <[email protected]> De : Everett Toews <[email protected]> Date : 19/09/2014 17:46 Objet : Re: Contribute to jclouds to support LBaaS feature of openstack-neutron Great to have you on board Frédéric! Definitely read the stuff that Ignasi pointed out and, because you’re working in the Neutron API, I want to point out a couple of additional things. 1. New Builders Zack Shoylev did a refactoring and we’re trying something new in Neutron. In general, your code will need to go into the v2 package [1] (do *not* put it in the v2_0 package!). Because LBaaS is an extension, it will need to go into the extensions package [2]. Also, take a very close look at how domain objects are done in the domain package [3]. This is the new way of doing the builder pattern in Neutron. It should make your jclouds development _much_ easier. We would also love to hear feedback on it! 2. Tests You’ll also want to look at the Testing OpenStack [4] guide and specifically the Neutron section. It should be helpful. I searched for you name in JIRA [5] but didn’t find it. If you create a user there, I’d be happy to add you as a contributor to jclouds and assign you to this issue. Thanks, Everett [1] https://github.com/jclouds/jclouds-labs-openstack/tree/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2 [2] https://github.com/jclouds/jclouds-labs-openstack/tree/master/openstack/neutron/src/main/java/org/jclouds/openstack/neutron/v2/extensions [3] https://github.com/jclouds/jclouds-labs-openstack/tree/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2/domain [4] https://wiki.apache.org/jclouds/Testing%20OpenStack [5] https://issues.apache.org/jira/browse/JCLOUDS/ On Sep 19, 2014, at 2:58 AM, Ignasi Barrera <[email protected]> wrote: > Hi Frédéric, > > Thanks for your interest. Your contribution is very welcome. > > We use GitHub pull request for patch submissions. Please, have a look > at the how to contribute guide [1], specifically to point 2, where > you'll find several links explaining how the pull requests work. Ping > us or join the #jclouds IRC channel at Freenode if you need help! > > > I. > > > [1] http://wiki.apache.org/jclouds/How%20to%20Contribute > > On 19 September 2014 10:44, <[email protected]> wrote: >> Hi, >> >> I would like to contribute to jclouds, especially to support LBaaS feature >> of openstack-neutron. >> >> My motivation comes from InGeoCloudS (www.ingeoclouds.eu), an open source >> project that my company (www.akka.eu) has contributed significantly to build. >> The InGeoCloudS project aims at demonstrating the feasibility of employing a >> cloud-based infrastructure coupled with the necessary services to provide >> seamless access to geospatial public sector information. >> The InGeoCloudS platform is currently running on AWS and we use jclouds to >> migrate it to OpenStack. >> I must say using jclouds to address openstack-nova (compute) in our project >> is a success. >> >> However, we need the LBaaS feature and jclouds does not (yet) support it. >> The issue https://issues.apache.org/jira/browse/JCLOUDS-611 is unassigned, >> so I propose to resolve it. >> I have already written code (including mock tests and live tests and >> following the contribution guide) to support LBaaS v1 in project >> jclouds-labs-openstack (master branch). >> I know that a new version of LBaaS (v2) is about to come with the next >> openstack release (Juno). I have already started to write code support LBaaS >> v2 in jclouds, however this part of work is in pause because juno release >> candidate does not yet include LBaaS v2 feature. >> >> Could you please explain me how to post my contribution code to support >> LBaas v1 ? >> >> Best regards, >> >> Frédéric >> >> _______________________________________ >> >> >> L'intégrité de ce message n'étant pas assurée sur internet, AKKA >> TECHNOLOGIES et ses filiales ne peuvent être tenues responsables de son >> contenu. Ce message et les éventuels fichiers attachés contiennent des >> informations confidentielles. Au cas où il ne vous serait pas destiné, nous >> vous remercions de bien vouloir le supprimer et en aviser l'expéditeur. >> Toute utilisation de ce message non conforme à sa destination, toute >> diffusion ou toute publication, totale ou partielle, est interdite, sauf >> autorisation expresse. >> >> >> >> This message and the files that may be attached to it contain confidential >> information. AKKA TECHNOLOGIES or its subsidiaries may not be held >> responsible for their contents, whose accuracy and completeness cannot be >> guaranteed over the internet. If the message is not addressed to you, kindly >> delete it and notify the sender. Any use of this message not in accordance >> with its purpose, any dissemination or disclosure, either whole or partial, >> is prohibited except formal approval. >> >> >> ________________________________________ _______________________________________ L'intégrité de ce message n'étant pas assurée sur internet, AKKA TECHNOLOGIES et ses filiales ne peuvent être tenues responsables de son contenu. Ce message et les �ventuels fichiers attach�s contiennent des informations confidentielles. Au cas o� il ne vous serait pas destin�, nous vous remercions de bien vouloir le supprimer et en aviser l'exp�diteur. Toute utilisation de ce message non conforme � sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. This message and the files that may be attached to it contain confidential information. AKKA TECHNOLOGIES or its subsidiaries may not be held responsible for their contents, whose accuracy and completeness cannot be guaranteed over the internet. If the message is not addressed to you, kindly delete it and notify the sender. Any use of this message not in accordance with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. ________________________________________
