[
https://issues.apache.org/jira/browse/JCLOUDS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015623#comment-14015623
]
Everett Toews commented on JCLOUDS-554:
---------------------------------------
>From http://www.hpcloud.com/console
"In keeping with the previously announced plan, HP Helion Public Cloud will
begin the retirement of the Compute v12.12 environment starting Monday June
2nd, 2014. Instances that are currently running in this environment will no
longer be accessible and will be queued for termination. Access to your
Account, Compute v13.5 resources, and all other services will continue to be
available through the HP Helion Public Cloud Console built on OpenStack Horizon
at https://horizon.hpcloud.com. Should you have any questions, comments, or
concerns please contact our Support Team via chat on this page."
I think it's appropriate to switch now.
> 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: Jeremy Daggett
> Labels: openstack
>
> 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)
