You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2014/04/30 19:02:20 UTC
[jira] [Commented] (JCLOUDS-554) openstack-nova defaults to API
v1.1
[ https://issues.apache.org/jira/browse/JCLOUDS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985746#comment-13985746 ]
Chris Custine commented on JCLOUDS-554:
---------------------------------------
The 12.12 endpoints are Nova 1.1 and are indeed going away on June 1 per HP. The current HP Cloud 13.5 release endpoints are Nova 2.0. I am updating HP compute and object storage providers for jclouds and will submit PRs soon.
> openstack-nova defaults to API v1.1
> -----------------------------------
>
> Key: JCLOUDS-554
> URL: https://issues.apache.org/jira/browse/JCLOUDS-554
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Reporter: Everett Toews
> Assignee: Everett Toews
> Labels: openstack
> Fix For: 1.8.0, 1.7.3
>
>
> All of the domain objects in openstack-nova are written for v2 of the API (org.jclouds.openstack.nova.v2_0.*) but jclouds talks to v1.1 endpoints by default.
> Also v1.1 hasn't been used in OpenStack since Diablo, 5 releases ago. Diablo isn't even supported anymore.
> openstack-nova should default to v2 in the pom.xml test.openstack-nova.api-version and in NovaApiMetadata.
> HP might still be running v1.1 on their Diablo based "pre-13.5" HPCloud which is to be discontinued on June 1, 2014.
--
This message was sent by Atlassian JIRA
(v6.2#6252)