[
https://issues.apache.org/jira/browse/JCLOUDS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182963#comment-14182963
]
Adrian Cole commented on JCLOUDS-664:
-------------------------------------
There have been a serious round of cleanups, and now azurecompute works against
the latest api version. These cleanups have been painstakingly ported to 1.8.x
(pain caused by JCLOUDS-653 which made almost every commit have a conflict over
MoreObjects).
Next steps:
1. refine api so that it works with ComputeService (may include adding
additional rest calls)
2. investigate oauth alternative to SSL client auth, or at least make SSL
client auth less terrible.
http://azure.microsoft.com/en-us/documentation/articles/api-management-howto-oauth2/
3. See about auto-value generation of things like equals/hashCode (JCLOUDS-750)
to trim codebase and reduce chance of mistakes like JCLOUDS-653 affecting this
provider.
> Azure compute support
> ---------------------
>
> Key: JCLOUDS-664
> URL: https://issues.apache.org/jira/browse/JCLOUDS-664
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-compute, jclouds-labs
> Affects Versions: 2.0.0
> Reporter: Andrew Bayer
> Assignee: Adrian Cole
> Fix For: 2.0.0
>
> Attachments: JCLOUDS-664.patch
>
>
> So we've got a very old, very stale, very incomplete azure-management (a.k.a.
> compute) implementation in labs. Let's actually modernize and finish that
> thing. Azure is unquestionably the biggest cloud out there that we don't have
> viable support for, so it's a really useful target.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
