Francesco,

thanks for your update and for your effort!

I think #135 is almost ready to be merged, I think we are waiting to close
the main pending discussion on
https://github.com/jclouds/jclouds-labs/pull/135#discussion-diff-24976668

I like both the idea of splitting JCLOUDS-164 in multiple subtasks or
simply create a new set of JIRA ISSUES to improve Azure compute
implmentation.

Best,
Andrea

On Tue Feb 24 2015 at 2:16:54 PM Francesco Chicchiriccò <ilgro...@apache.org>
wrote:

> Hi all,
> a quick update on ours (Fabio's and mine) current activities.
>
> First of all, we are basing our work on PR #135 rather than
> jclouds-labs' master, since the former contains a whole set of fixes and
> new features, and is in turn based on the latter.
> About this, is anyone able to provide a sneak peek on expected actual
> merge timeframe? From the e-mail below it seems quite soon.
>
> We are currently trying to make all live tests succeeding with an actual
> Azure instance: this is the initial main purpose of our contribution,
> and will constitute the ground of our first pull request.
>
> (Incidentally, I remember that there are free MSDN subscriptions
> available - including Azure - for ASF committers; see
> https://svn.apache.org/repos/private/committers/donated-
> licenses/msdn-license-grants.txt
> for details)
>
> The intention is then to move from there by identifying some subtasks of
> JCLOUDS-664 for each specific item.
> WDYT?
>
> Regards.
>
> On 20/02/2015 10:45, Francesco Chicchiriccò wrote:
> > On 20/02/2015 10:13, Andrea Turli wrote:
> >> Hi Francesco,
> >>
> >> thanks for your interest in jclouds!
> >>
> >> Azure Compute implementation is under the spot these days and we are
> >> working hard to improve it.
> >> You may be aware of [1] and moreover there are currently a couple of
> >> pending PRs which are providing an initial implementation of the
> >> AzureComputeServiceAdapter [2]
> >
> > Hi Andrea, I am aware of course of the recent "Azure SDK Vs REST"
> > discussion, and I also know that at the end the REST option was
> > preferred.
> >
> >> As [2] will be soon merged, I think we could wait for #135 and then
> >> rebase
> >> your #137 on it, if it is still needed.
> >> WDYT?
> >
> > This sounds reasonable: I think we should coordinate our work (even by
> > opening some subtasks of JCLOUDS-664) in order to avoid latency and
> > being as much effective as possible.
> > How would do you see this?
> >
> >> Feel free to join IRC #jclouds to discuss better next steps!
> >
> > I'm already there :-)
> > Regards.
> >
> >> [1]: http://www.mail-archive.com/dev@jclouds.apache.org/msg05877.html
> >> [2]: https://github.com/jclouds/jclouds-labs/pull/135
> >>
> >> On Fri Feb 20 2015 at 10:03:45 AM Francesco Chicchiriccò
> >> <ilgro...@apache.org> wrote:
> >>
> >>> Hi JClouds community,
> >>> I am interested in contributing to the Azure compute provider with
> >>> target of completing its implementation, as part of Eduard's team
> >>> with a
> >>> focus on Azure.
> >>>
> >>> Is there anyone actively working on this [1]?
> >>> I see as initial directions to implement methods in [2] and to change
> >>> the deprecated implementations in [3]: am I missing something?
> >>>
> >>> I have prepared a first pull request [4] which fixes some troubles I've
> >>> found with live (e.g. against an actual Azure subscription) test
> >>> execution.
> >>> WDYT?
> >>>
> >>> Regards.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/JCLOUDS-664
> >>> [2] https://github.com/jclouds/jclouds-labs/blob/master/
> >>> azurecompute/src/main/java/org/jclouds/azurecompute/compute/
> >>> AzureComputeServiceAdapter.java
> >>> [3] https://github.com/jclouds/jclouds-labs/blob/master/
> >>> azurecompute/src/main/java/org/jclouds/azurecompute/config/
> >>> AzureComputeHttpApiModule.java
> >>> [4] https://github.com/jclouds/jclouds-labs/pull/137
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC
> http://people.apache.org/~ilgrosso/
>
>

Reply via email to