Hi Rita,
There are several reasons for jclouds to directly implement the rest
apis instead of using existing SDKs.
jclouds is all about cloud portability, and that is not only achieved
by providing a common interface for every provider to implement, but
by providing consistent ways of addressing
Hey guys,
Here is a question regarding SDK vs. REST API. The current azurecompute is
using the ASM rest api. I read some of the reasons for picking the rest api
over the java sdk. The current Azure java SDK has come a long way.
https://github.com/Azure/azure-sdk-for-java/. It is pretty nicely
a
Hi,
Sure. I'd fork the jclouds-labs repo and start a azurecompute-arm
provider there. You can copy most of the structure and relevant bits
of the existing azurecompute one as soon as you need them, and once
the ARM version starts to take shape we can think about refactoring
the common code in a co
I am an open source engineer at Microsoft. We have few customers who are
blocked by Azure compute support on jclouds when using ARM mode. We have couple
of folks who can help out in getting the ARM implementation going. Given that
there is an implementation using the class API already, we can c
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
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 the
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
+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 Fr
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 provide
+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-azure
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
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 `c
12 matches
Mail list logo
