Hi Rita, Thanks again for your interest.
I think as we discussed already at https://pony-poc.apache.org/thread.html/Zr4ln1ju1yrizap you could start a new jclouds/jclouds-labs provider called `azurecompute-arm`. The structure of this new jclouds provider would be similar to either jclouds/jclouds/providers/digitalocean2 [1] or jclouds/jclouds-labs/docker [2] Please consider reading those notes [3] before starting the development. Feel free to reach to us using the usual contacts [4] in particular IRC [5] if you want to discuss with us. Looking forward to seeing your first PR! Andrea [1]: https://github.com/jclouds/jclouds/tree/master/providers/digitalocean2/src/main/java/org/jclouds/digitalocean2 [2]: https://github.com/jclouds/jclouds-labs/tree/master/docker [3]: https://cwiki.apache.org/confluence/display/JCLOUDS/Writing+jclouds+Code [4]: http://jclouds.apache.org/community/ [5]: https://webchat.freenode.net/?channels=jclouds On Fri, Jan 29, 2016 at 3:02 PM Ignasi Barrera <n...@apache.org> wrote: > Hi Rita, > > Apologies for the late reply! > > Thank you for your interest in helping with the Azure compute > provider. There is currently no ongoing development to support ARM, so > I'd say "go for it!". > > Regarding the best way to start, I'd suggest to listen to what Andrea > Turli or Francesco think, as they are the ones who developed the > current azurecompute provider and will know better if its current > structure is good for the ARM version too or if it makes more sense to > start a new ARM provider. > > In any case, things are better discussed when they're tangible, so if > you already have a plan in mind, just start hacking and send a PR > (either to the existing provider or to create a new one). We > appreciate early and small PRs, as they make it easier to review and > to set the basis at the beginning. If you are up to contributing, > please, have a look at our "how to contribute" guide [1]. > > > Look forward to seeing the ARM support take shape! > > I. > > > > [1] https://cwiki.apache.org/confluence/display/JCLOUDS/How+to+Contribute > > On 22 January 2016 at 19:40, Rita Zhang <rita.z.zh...@gmail.com> wrote: > > Hey guys, > > Awesome work for adding azure compute support in jclouds! I am an open > source engineer at Microsoft. We have couple of folks who can help out in > getting the ARM implementation going. Before we dive into this, want to > make sure we do not duplicate any ongoing efforts and that this is of an > interest to the community. > > > > Thanks > > > > On 2015-12-11 08:51, Andrea Turli <andrea.tu...@gmail.com> wrote: > >> +1 > >> > >> I think it is best to keep them separate also in light of > >> > https://azure.microsoft.com/en-us/documentation/articles/resource-manager-deployment-model/#considerations-for-virtual-machines > >> Looks to me ASM and ARM are alternative approaches rather than ARM being > >> the evolution of ASM. > >> > >> Thanks > >> > >> On Fri, Dec 11, 2015 at 5:47 PM, Ignasi Barrera <n...@apache.org> > wrote: > >> > >> > I'd also say we can promote azure with the xml api as soon as it is > >> > stable, and start a new provider in labs (say azurecompute-arm?) that > >> > consumes the new API. If it is not only the api that changes, but also > >> > how networking and other stuff is configured, it is likely that the > >> > changes to the provider will be major and non-backwards compatible, > >> > which is an issue when updating promoted providers. > >> > > >> > Starting a new one and let the users choose will be easier for them > >> > and will facilitate us the deprecation of the legacy one when the > >> > classic api is shut down. > >> > > >> > On 11 December 2015 at 13:05, Andrea Turli <andrea.tu...@gmail.com> > wrote: > >> > > +1 > >> > > > >> > > let's merge soon https://github.com/jclouds/jclouds-labs/pull/197 > and > >> > > promote azurecompute! > >> > > > >> > > On Fri, Dec 11, 2015 at 11:37 AM, Francesco ChicchiriccÚ < > >> > > ilgro...@apache.org> wrote: > >> > > > >> > >> On 11/12/2015 11:18, Andrea Turli wrote: > >> > >> > >> > >>> Hi, > >> > >>> > >> > >>> currently we are struggling to have a good jclouds-azurecompute > api to > >> > be > >> > >>> promoted to jclouds/jclouds. > >> > >>> I've noticed that MS suggests now to use (and/or switch) to ARM > (Azure > >> > >>> Resource Manager) and they have marked the previous API (and also > the > >> > >>> console) with `classic` label. > >> > >>> > >> > >>> I don't know if `classic` will be deprecated soon, but it seems > >> > sensible > >> > >>> to > >> > >>> consider the switch to ARM: those API are json based which will > >> > >>> considerably reduce the glitches due to xml we are facing since > the > >> > >>> beginning and they introduce a stronger network model (port > ranges w/t > >> > >>> limitations and security groups etc) which look a step in the > right > >> > >>> direction. > >> > >>> > >> > >>> Thoughts? > >> > >>> > >> > >> > >> > >> While I confirm that it seems that ARM is the future, I also > believe > >> > that > >> > >> the classic API is not likely to disappear soon. > >> > >> > >> > >> I'd propose then to not consider ARM for promoting > jclouds-azurecompute, > >> > >> but to open an issue on JIRA right now for adding the ARM support > there > >> > (or > >> > >> to start a brand new provider, don't know which alternative fits > >> > better). > >> > >> > >> > >> Regards. > >> > >> > >> > >> -- > >> > >> Francesco ChicchiriccÚ > >> > >> > >> > >> Tirasa - Open Source Excellence > >> > >> http://www.tirasa.net/ > >> > >> > >> > >> Involved at The Apache Software Foundation: > >> > >> member, Syncope PMC chair, Cocoon PMC, Olingo PMC, CXF committer > >> > >> http://home.apache.org/~ilgrosso/ > >> > >> > >> > >> > >> > > >> >
