You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/09/06 19:39:55 UTC

[jira] [Commented] (JCLOUDS-209) Add support for full GCE v1beta15 API

    [ https://issues.apache.org/jira/browse/JCLOUDS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760402#comment-13760402 ] 

ASF subversion and git services commented on JCLOUDS-209:
---------------------------------------------------------

Commit 53386380836e15ddb01e131b2ab9329e443d8b63 in branch refs/heads/master from [~abayer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs-google.git;h=5338638 ]

JCLOUDS-209. Move to GCE v1beta15 API, with new features/methods included

Does not include aggregated list method calls, due to those calls not
working with service accounts.

Does not include image insert or deprecate due to the extremely
complex system for creating images in GCE, which makes writing tests
for that a pain. Will come in a later commit.

                
> Add support for full GCE v1beta15 API
> -------------------------------------
>
>                 Key: JCLOUDS-209
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-209
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-labs-google
>    Affects Versions: 1.7.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 1.7.0
>
>
> So in JCLOUDS-192, we've got the 1.6.x line's GCE support working again, but it's not fully implementing all of the v1beta15 API. I'm working on getting that done and added to 1.7.0, but am going to leave the 1.6.x line as is, supporting the APIs existing in v1beta13 running against v1beta15, adding only the new API calls needed for things like zone vs global operations. Here, I'll get it all working. =)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira