+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/ > >> > >> >
