@nacx @everett-toews @zack-shoylev I am delivering a project this week so I
have been heads down crunching on that, but to be honest I don't totally
understand the issue as it related to HP Cloud. HPs nova supports os-volumes
extension and IIRC cinder already has the attachment support baked
@@ -62,7 +62,7 @@ protected void configure() {
@Provides
@Singleton
public MultimapURI, URI aliases() {
- return ImmutableMultimap.URI, URIbuilder()
+ return customAliases(ImmutableMultimap.URI, URIbuilder()
Good approach. It works for both the HP and rackspace
Also uses @nacx better approach to making NovaHttpApi aliases overrideable.
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds/pull/712
-- Commit Summary --
* Volume attachment fix for cloudservers-uk
-- File Changes --
M
I've run the same test with the RC1 version (without the applied patches) and
the volume attachment API is also absent for HP cloud there.
@ccustine @everett-toews @zack-shoylev Is this ok? If not, I think we should
report it as a known issue (as no one have complaint about it before and it
The last change completely refactors how the extension namespace aliases are
configured. Now aliases are configured using Guice multibindings to allow
providers to contribute their own aliases in a clean way.
This also fixes the HPCloud volume attachment configuration and adds the
Apologies for the absence of feedback. We are about to release jclouds 1.9.0,
and the master branch are under code freeze. We are fixing an issue spotted
while testing the first release candidate, and expect to have the release out
by the end of this week. Once that happens I'll be back to the
Also note that the bindings configured in the providers are *added* to the
aliases map; they don't override the existing keys, but that should be aligned
with the current behavior, that already expects more than one namespace URI for
a given extension type (see
Hey jenkins, rebuild please
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/711#issuecomment-85117598
Ok, I've opened https://github.com/jclouds/jclouds/pull/711 to fix the
attachment in HPCloud. Basically it requires the same attachment extension
namespace than Rackspace, and the test needed to be a bit more generic, as the
Cinder version provided by HPCloud is 1.0, while the Compute version
Hey @devcsrj
So, a couple ways we could handle this:
1. We could do the image and push it to our Virtual Data Center, then we
perform the live tests against our account.
2. We could setup a dedicated jclouds account using the new Developer Program
at PB.
3. You could spin up a VM using
@nacx Just following up on this PR. Is there any outstanding work on our end we
should do?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/143#issuecomment-85134772
Once this is in, [this
commit](https://github.com/nacx/jclouds-labs-openstack/commit/8b252a4f3487a5533ace98da14f76c8e799810ad)
will need to be cherry-picked in jclouds-labs-openstack to align Neutron with
the changes in this PR. /cc @zack-shoylev
---
Reply to this email directly or view it on
Pushed to master as
[4db2b75a](https://git1-us-west.apache.org/repos/asf?p=jclouds.git;a=commit;h=4db2b75a).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/711#issuecomment-85253360
Seems to work with both UK and US Rackspace providers!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/711#issuecomment-85236999
@@ -91,17 +91,16 @@ protected void configure() {
}
}
+ // Allow providers to cleanly contribute their own aliases
The
[MapBinder](http://google.github.io/guice/api-docs/latest/javadoc/index.html?com/google/inject/multibindings/MapBinder.html)
javadoc already has the detailed
Thanks for helping with the testing @zack-shoylev, @everett-toews!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/711#issuecomment-85254266
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/700/changes
Changes:
[Ignasi Barrera] Use Guice multibindings to configure the aliases
--
Started by an SCM change
Building remotely on 55c39d77 (lxc-fedora17 standard m1.large large) in
:+1:
Success on OpenStack Juno (with DevStack)
mvn clean test -Plive
-Dtest.openstack-nova.endpoint=http://$DEVSTACK_HOST:5000/v2.0/
-Dtest.openstack-nova.identity=demo:demo
-Dtest.openstack-nova.credential=devstack
-Dtest.openstack-nova.image-id=$IMAGE_ID
This PR should be closed now as the changes here are already included in
https://github.com/jclouds/jclouds/commit/4db2b75addf9730d66ddde166a5d0e464434478f.
Thanks @zack-shoylev!
---
Reply to this email directly or view it on GitHub:
Closed #712.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/712#event-262956057
Hi @baldwinSPC ,
(2 + 3) :+1: Sounds about the right step, since for this provider to be
promoted out of labs, it'll need a testing account. Btw, can't seem to find the
_new developer program_. Is there some link or was it via email or something?
(3) This was the suggestion from Flavius (PB
[
https://issues.apache.org/jira/browse/JCLOUDS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zack Shoylev reassigned JCLOUDS-826:
Assignee: Zack Shoylev
JDBC blobstore
--
Key: JCLOUDS-826
@@ -91,17 +91,16 @@ protected void configure() {
}
}
+ // Allow providers to cleanly contribute their own aliases
Maybe add some more info about the mechanics of it.
---
Reply to this email directly or view it on GitHub:
See https://jclouds.ci.cloudbees.com/job/jclouds/3010/changes
Changes:
[Ignasi Barrera] Fixes OpenStack extension namespace configuration
[Ignasi Barrera] Fix HPCloudComputeTemplateBuilderLiveTest
--
Started by an SCM change
Building remotely on da8a1e50
24 matches
Mail list logo
