[jira] [Created] (JCLOUDS-465) jclouds incompatibility with Guava 16.0.1
Ben McCann created JCLOUDS-465: -- Summary: jclouds incompatibility with Guava 16.0.1 Key: JCLOUDS-465 URL: https://issues.apache.org/jira/browse/JCLOUDS-465 Project: jclouds Issue Type: Bug Reporter: Ben McCann jclouds works with guava 15, but when I try upgrading my project to 16.0.1, I get the following error: java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException at org.jclouds.util.TypeToken2.where(TypeToken2.java:61) at org.jclouds.rest.internal.BaseRestApiMetadata.contextToken(BaseRestApiMetadata.java:60) at org.jclouds.rest.internal.BaseRestApiMetadata$Builder.init(BaseRestApiMetadata.java:74) at org.jclouds.openstack.swift.SwiftApiMetadata$Builder.init(SwiftApiMetadata.java:85) at org.jclouds.openstack.swift.SwiftApiMetadata$Builder.init(SwiftApiMetadata.java:81) at org.jclouds.openstack.swift.SwiftApiMetadata$ConcreteBuilder.init(SwiftApiMetadata.java:108) at org.jclouds.openstack.swift.SwiftApiMetadata$ConcreteBuilder.init(SwiftApiMetadata.java:108) at org.jclouds.openstack.swift.SwiftApiMetadata.init(SwiftApiMetadata.java:60) at com.connectifier.datastore.ObjectStore.init(ObjectStore.java:55) at com.connectifier.datastore.ObjectStore$$FastClassByGuice$$39607599.newInstance(generated) at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40) at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53) at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254) at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024) at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JCLOUDS-465) jclouds incompatibility with Guava 16.0.1
[ https://issues.apache.org/jira/browse/JCLOUDS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898935#comment-13898935 ] Ignasi Barrera commented on JCLOUDS-465: Hi! Could you try upgrading to jclouds 1.8.0-SNAPSHOT? We have already upgraded it to use Guava 16.0.1 (see [core/pom.xml|https://github.com/jclouds/jclouds/blob/master/core/pom.xml#L98]). The change won't be backported to previous versions as upgrading such a core dependency in a minor release can have an important impact in existing integrations. Let us know if jclouds 1.8.0-SNAPSHOT fixes the issue! jclouds incompatibility with Guava 16.0.1 - Key: JCLOUDS-465 URL: https://issues.apache.org/jira/browse/JCLOUDS-465 Project: jclouds Issue Type: Bug Reporter: Ben McCann jclouds works with guava 15, but when I try upgrading my project to 16.0.1, I get the following error: java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException at org.jclouds.util.TypeToken2.where(TypeToken2.java:61) at org.jclouds.rest.internal.BaseRestApiMetadata.contextToken(BaseRestApiMetadata.java:60) at org.jclouds.rest.internal.BaseRestApiMetadata$Builder.init(BaseRestApiMetadata.java:74) at org.jclouds.openstack.swift.SwiftApiMetadata$Builder.init(SwiftApiMetadata.java:85) at org.jclouds.openstack.swift.SwiftApiMetadata$Builder.init(SwiftApiMetadata.java:81) at org.jclouds.openstack.swift.SwiftApiMetadata$ConcreteBuilder.init(SwiftApiMetadata.java:108) at org.jclouds.openstack.swift.SwiftApiMetadata$ConcreteBuilder.init(SwiftApiMetadata.java:108) at org.jclouds.openstack.swift.SwiftApiMetadata.init(SwiftApiMetadata.java:60) at com.connectifier.datastore.ObjectStore.init(ObjectStore.java:55) at com.connectifier.datastore.ObjectStore$$FastClassByGuice$$39607599.newInstance(generated) at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:60) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40) at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53) at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:94) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254) at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024) at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (JCLOUDS-466) OpenStack Keystone ServiceApi/ServiceAsyncApi doesn't provide any operation for OpenStack Keystone services
Pedro Navarro Pérez created JCLOUDS-466: --- Summary: OpenStack Keystone ServiceApi/ServiceAsyncApi doesn't provide any operation for OpenStack Keystone services Key: JCLOUDS-466 URL: https://issues.apache.org/jira/browse/JCLOUDS-466 Project: jclouds Issue Type: Bug Components: jclouds-labs-openstack Affects Versions: 1.7.1 Reporter: Pedro Navarro Pérez ServiceApi/ServiceAsyncApi provides the next method: Set? extends Tenant listTenants(); this action is not related to the service entities, moreover tenants listing is already provided by TeanantApi/TenantAsyncApi. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * @return The string value.
+ */
+ public String value() {
+ return name();
+ }
+
+ @Override
+ public String toString() {
+ return value();
+ }
+
+ /**
+ * @param status The string representation of a Status
+ * @return The corresponding Status.
+ */
+ public static Status fromValue(String status) {
Sorry, I'm not sure what you mean. How would it be used? Why can't valueOf() be
used instead?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9674175
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
The Javadoc can always be updated in later PRs. No need to block merging on Javadoc at this point in time. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34887114
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899337#comment-13899337
]
Ben Mabey commented on JCLOUDS-427:
---
Thanks for resolving this issue so quickly. Do you have any idea when 1.6.4
will land on Maven Central?
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Key: JCLOUDS-427
URL: https://issues.apache.org/jira/browse/JCLOUDS-427
Project: jclouds
Issue Type: Bug
Components: jclouds-core
Affects Versions: 1.7.0, 1.6.3
Reporter: graham o'regan
Assignee: Andrew Phillips
Priority: Critical
Fix For: 1.8.0, 1.7.1, 1.6.4
Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Running 'mvn test' results in test failures similar to this;
{code}
Caused by: com.google.inject.CreationException: Guice creation errors:
1)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.rest.HttpClient,
A cannot be used as a key; It is not fully specified.
2)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.http.IntegrationTestClient,
A cannot be used as a key; It is not fully specified.
3) org.jclouds.rest.RestContextorg.jclouds.http.IntegrationTestClient, A
cannot be used as a key; It is not fully specified.
4) No implementation for org.jclouds.rest.HttpClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
{code}
I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899356#comment-13899356
]
Andrew Phillips commented on JCLOUDS-427:
-
[~bmabey]: 1.6.4 is not currently planned, as far as I'm aware. I take it from
your comment that upgrading to 1.7.1 is not an option for you. Are you able to
use 1.6.3-SNAPSHOT successfully for now (this contains the relevant workaround)?
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Key: JCLOUDS-427
URL: https://issues.apache.org/jira/browse/JCLOUDS-427
Project: jclouds
Issue Type: Bug
Components: jclouds-core
Affects Versions: 1.7.0, 1.6.3
Reporter: graham o'regan
Assignee: Andrew Phillips
Priority: Critical
Fix For: 1.8.0, 1.7.1, 1.6.4
Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Running 'mvn test' results in test failures similar to this;
{code}
Caused by: com.google.inject.CreationException: Guice creation errors:
1)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.rest.HttpClient,
A cannot be used as a key; It is not fully specified.
2)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.http.IntegrationTestClient,
A cannot be used as a key; It is not fully specified.
3) org.jclouds.rest.RestContextorg.jclouds.http.IntegrationTestClient, A
cannot be used as a key; It is not fully specified.
4) No implementation for org.jclouds.rest.HttpClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
{code}
I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899362#comment-13899362
]
Ben Mabey commented on JCLOUDS-427:
---
Yeah, I'm looking for a quick fix now so I can take time to upgrade to the 1.7x
line. A 1.6.3-SNAPSHOT would work for me but I am not finding it in Maven
Central either. I'll look into making the jump to 1.7.1.
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Key: JCLOUDS-427
URL: https://issues.apache.org/jira/browse/JCLOUDS-427
Project: jclouds
Issue Type: Bug
Components: jclouds-core
Affects Versions: 1.7.0, 1.6.3
Reporter: graham o'regan
Assignee: Andrew Phillips
Priority: Critical
Fix For: 1.8.0, 1.7.1, 1.6.4
Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Running 'mvn test' results in test failures similar to this;
{code}
Caused by: com.google.inject.CreationException: Guice creation errors:
1)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.rest.HttpClient,
A cannot be used as a key; It is not fully specified.
2)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.http.IntegrationTestClient,
A cannot be used as a key; It is not fully specified.
3) org.jclouds.rest.RestContextorg.jclouds.http.IntegrationTestClient, A
cannot be used as a key; It is not fully specified.
4) No implementation for org.jclouds.rest.HttpClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
{code}
I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * @return The string value.
+ */
+ public String value() {
+ return name();
+ }
+
+ @Override
+ public String toString() {
+ return value();
+ }
+
+ /**
+ * @param status The string representation of a Status
+ * @return The corresponding Status.
+ */
+ public static Status fromValue(String status) {
fromValue is used in our custom json parsers to provide UNRECOGNIZED. valueOf
is used automatically otherwise. However, you can't override valueOf. Now,
having looked at it some more, I think I can remove UNRECOGNIZED and fromValue.
This will simplify the code without losing functionality.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9678918
[jclouds-chef] Adding test source scanning to Checkstyle config (#42)
Backport of 4cef85d from the main jclouds repo You can merge this Pull Request by running: git pull https://github.com/jclouds/jclouds-chef port-4cef85d Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-chef/pull/42 -- Commit Summary -- * Adding test source scanning to Checkstyle config -- File Changes -- M project/pom.xml (1) -- Patch Links -- https://github.com/jclouds/jclouds-chef/pull/42.patch https://github.com/jclouds/jclouds-chef/pull/42.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/42
[jira] [Commented] (JCLOUDS-427) Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for interface implementations
[
https://issues.apache.org/jira/browse/JCLOUDS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899385#comment-13899385
]
Andrew Phillips commented on JCLOUDS-427:
-
[~bmabey]: If a quick fix is OK for now, see
http://jclouds.apache.org/documentation/userguide/installation-guide/#snapshot
or http://apache.markmail.org/thread/637ayb6d6uz36bam for instructions on
getting hold of 1.6.3-SNAPSHOT.
Hope that helps!
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Key: JCLOUDS-427
URL: https://issues.apache.org/jira/browse/JCLOUDS-427
Project: jclouds
Issue Type: Bug
Components: jclouds-core
Affects Versions: 1.7.0, 1.6.3
Reporter: graham o'regan
Assignee: Andrew Phillips
Priority: Critical
Fix For: 1.8.0, 1.7.1, 1.6.4
Attachments: JCLOUDS-427-1.6.x.patch, JCLOUDS-427.patch
Upgrading JDK from 1.7.0_45 to 1.7.0_51 causes problems when searching for
interface implementations
Running 'mvn test' results in test failures similar to this;
{code}
Caused by: com.google.inject.CreationException: Guice creation errors:
1)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.rest.HttpClient,
A cannot be used as a key; It is not fully specified.
2)
org.jclouds.rest.config.SyncToAsyncHttpApiProviderorg.jclouds.http.IntegrationTestClient,
A cannot be used as a key; It is not fully specified.
3) org.jclouds.rest.RestContextorg.jclouds.http.IntegrationTestClient, A
cannot be used as a key; It is not fully specified.
4) No implementation for org.jclouds.rest.HttpClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
5) No implementation for org.jclouds.http.IntegrationTestClient was bound.
at
org.jclouds.rest.config.BinderUtils.bindHttpApiProvider(BinderUtils.java:106)
{code}
I've tested using OpenJDK on Centos 6.4 and Oracle JDK on OS X 10.9 with the
same results.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jclouds-chef] Adding test source scanning to Checkstyle config (1.7.x) (#43)
1.7.x version of https://github.com/jclouds/jclouds-chef/pull/42 You can merge this Pull Request by running: git pull https://github.com/jclouds/jclouds-chef port-4cef85d-1.7.x Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-chef/pull/43 -- Commit Summary -- * Adding test source scanning to Checkstyle config -- File Changes -- M project/pom.xml (1) -- Patch Links -- https://github.com/jclouds/jclouds-chef/pull/43.patch https://github.com/jclouds/jclouds-chef/pull/43.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/43
Re: [jclouds-chef] Adding test source scanning to Checkstyle config (#42)
[jclouds » jclouds-chef #774](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/774/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/42#issuecomment-34899715
Re: [jclouds-chef] Adding test source scanning to Checkstyle config (#42)
[jclouds-chef-pull-requests #104](https://jclouds.ci.cloudbees.com/job/jclouds-chef-pull-requests/104/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/42#issuecomment-34899877
Re: [jclouds-chef] Adding test source scanning to Checkstyle config (1.7.x) (#43)
[jclouds » jclouds-chef #775](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/775/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/43#issuecomment-34900291
Re: [jclouds-chef] Adding test source scanning to Checkstyle config (#42)
@nacx: Looks OK? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/42#issuecomment-34901248
Re: [jclouds-chef] Adding test source scanning to Checkstyle config (#42)
+1! Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/42#issuecomment-34904331
Re: [jclouds-chef] Adding test source scanning to Checkstyle config (1.7.x) (#43)
Committed to [1.7.x](https://git-wip-us.apache.org/repos/asf?p=jclouds-chef.git;a=commit;h=3aff904fb9b5b071ad13e3a25f37b274c8ec7e7d) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-chef/pull/43#issuecomment-34904781
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * @return The string value.
+ */
+ public String value() {
+ return name();
+ }
+
+ @Override
+ public String toString() {
+ return value();
+ }
+
+ /**
+ * @param status The string representation of a Status
+ * @return The corresponding Status.
+ */
+ public static Status fromValue(String status) {
Specifically, it is needed for EnumTypeAdapterThatReturnsFromValue which is the
custom jclouds enum adapter. If the enum string cannot be parsed automatically,
fromValue is called.
I am not sure if I am explaining this well...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9683492
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
This seems to be code-complete. Remaining documentation todos will be updated later as that documentation becomes more available. Rebasing and merging. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34914050
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * @return The string value.
+ */
+ public String value() {
+ return name();
+ }
+
+ @Override
+ public String toString() {
+ return value();
+ }
+
+ /**
+ * @param status The string representation of a Status
+ * @return The corresponding Status.
+ */
+ public static Status fromValue(String status) {
I have not been explaining this in enough detail. There is a jclouds GSON
feature (enum adapter) where fromValue is called if GSON cannot deserialize the
value.
1. Bad value encountered in JSON
2. Adapter cannot deserialize using known enum values (exception)
3. Adapter calls fromValue
4. fromValue uses valueOf and fails (exception)
5. fromValue returns UNRECOGNIZED
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9684725
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
[jclouds » jclouds-labs-openstack #843](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/843/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34914633
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * @return The string value.
+ */
+ public String value() {
+ return name();
+ }
+
+ @Override
+ public String toString() {
+ return value();
+ }
+
+ /**
+ * @param status The string representation of a Status
+ * @return The corresponding Status.
+ */
+ public static Status fromValue(String status) {
Oh, and note null is still possible.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9684760
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
[jclouds-labs-openstack-pull-requests #162](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/162/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34914850
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
merged --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34915516
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
Closed #78. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78
Re: [jclouds-examples] Renames domain classes for consitency (#31)
merged --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/31#issuecomment-34918266
Re: [jclouds-examples] Renames domain classes for consitency (#31)
Closed #31. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/31
Re: [jclouds-labs] profitbricks: impl: provider base (#44)
@sivikt Have you had a chance to continue working on this PR? Should we close it? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/44#issuecomment-34920486
Re: [jclouds] Jclouds 136 -- Implementation of DynECT HTTP Redirect service API (#37)
Closed #37. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/37
Re: [jclouds] Jclouds 136 -- Implementation of DynECT HTTP Redirect service API (#37)
This PR seems to be dead. I'm closing it. Please, add a comment if you plan to update and reopen it! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/37#issuecomment-34920798
Re: [jclouds] JCLOUDS-241: Added missing options to ListUsageRecordsOptions (#124)
How should be proceed with this PR? Is still work to be done? Or should we close it? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/124#issuecomment-34921284
Re: [jclouds] Implement a poor-mans rollback if static nat creation fails (#184)
It's been a while now... Is it worth reopening this PR against master, as there is no 1.6 release scheduled? Implementing a generic and proper rolback for the compute operations can be quite complex as providers do very different things as part of the node provisioning procedure (network creation, ip allocation, storage provisioning, etc). Having a generic rollback mechanism that only considers the operations that got materialized in the provider before the failure happened can be complex and we could spend as many time as we wanted to properly implement it in all the existing providers. I'm personally in favor of merging this, but I'd push the changes to master. WDYT? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/184#issuecomment-34922048
Re: [jclouds] JCLOUDS-213: Fixing SoftLayer support (#247)
@ahgittin Could you fix what @demobox commented so we can merge this? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/247#issuecomment-34922387
Re: [jclouds] JCLOUDS-423: Update Service Type for Cloud Files CDN (#252)
Closed #252. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/252
[jira] [Assigned] (JCLOUDS-467) nameNodes only taking first name with AWS
[
https://issues.apache.org/jira/browse/JCLOUDS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Bayer reassigned JCLOUDS-467:
Assignee: Andrew Bayer
nameNodes only taking first name with AWS
-
Key: JCLOUDS-467
URL: https://issues.apache.org/jira/browse/JCLOUDS-467
Project: jclouds
Issue Type: Bug
Components: jclouds-compute
Reporter: Everett Toews
Assignee: Andrew Bayer
Fix For: 1.8.0
I'll put nameNodes into TemplateOptions but only the first gets used.
{code}
public class NameNodes {
public static final String MCW = multi-cloud-workshop;
public static final String LOAD_BALANCER = MCW + -lb;
public static final String DATABASE = MCW + -db;
public static final String WEB_SERVER_01 = MCW + -webserver-01;
public static final String WEB_SERVER_02 = MCW + -webserver-02;
private final ComputeService computeService;
public static void main(String[] args) {
NameNodes nameNodes = null;
try {
nameNodes = new NameNodes();
nameNodes.createServers();
} catch (Throwable e) {
e.printStackTrace();
} finally {
if (nameNodes != null) {
nameNodes.close();
}
}
}
public NameNodes() throws IOException {
IterableModule modules = ImmutableSet.Moduleof(
new SLF4JLoggingModule(),
new SshjSshClientModule());
Properties overrides = new Properties();
overrides.setProperty(POLL_INITIAL_PERIOD, 3);
overrides.setProperty(POLL_MAX_PERIOD, 3);
ComputeServiceContext context = ContextBuilder.newBuilder(aws-ec2)
.credentials(myAwsAccessKeyId, myAwsSecretAccessKey)
.modules(modules)
.overrides(overrides)
.buildView(ComputeServiceContext.class);
computeService = context.getComputeService();
}
private MapString, NodeMetadata createServers() throws
RunNodesException, IOException {
SetString nodeNames = ImmutableSet.of(DATABASE, WEB_SERVER_01,
WEB_SERVER_02, LOAD_BALANCER);
System.out.println(format(Creating servers %s, Joiner.on(,
).join(nodeNames)));
TemplateOptions options = computeService.templateOptions()
.nodeNames(nodeNames)
.inboundPorts(22);
Template template = computeService.templateBuilder()
.imageNameMatches(ubuntu/images/ubuntu-precise-12.04-amd64-server-20131003)
.locationId(us-west-2)
.hardwareId(m1.small)
.options(options)
.build();
Set? extends NodeMetadata nodes =
computeService.createNodesInGroup(MCW, 4, template);
MapString, NodeMetadata nameToNode = newHashMap();
System.out.println(Created servers:);
for (NodeMetadata node: nodes) {
String name = node.getName();
String publicIpAddress =
getOnlyElement(node.getPublicAddresses());
String user = node.getCredentials().getUser();
System.out.println(format( %-40s %s@%s, name, user,
publicIpAddress));
nameToNode.put(name, node);
}
return nameToNode;
}
private void close() {
computeService.getContext().close();
}
}
{code}
The output is
{code}
Creating servers multi-cloud-workshop-db, multi-cloud-workshop-webserver-01,
multi-cloud-workshop-webserver-02, multi-cloud-workshop-lb
Created servers:
multi-cloud-workshop-db ubuntu@54.184.78.205
multi-cloud-workshop-db ubuntu@54.203.107.107
multi-cloud-workshop-db ubuntu@54.202.100.94
multi-cloud-workshop-db ubuntu@54.184.52.175
{code}
Confirmed the names of the instances in the AWS console too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (JCLOUDS-467) nameNodes only taking first name with AWS
[
https://issues.apache.org/jira/browse/JCLOUDS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899817#comment-13899817
]
Andrew Bayer commented on JCLOUDS-467:
--
Queues, maybe?
nameNodes only taking first name with AWS
-
Key: JCLOUDS-467
URL: https://issues.apache.org/jira/browse/JCLOUDS-467
Project: jclouds
Issue Type: Bug
Components: jclouds-compute
Reporter: Everett Toews
Assignee: Andrew Bayer
Fix For: 1.8.0
I'll put nameNodes into TemplateOptions but only the first gets used.
{code}
public class NameNodes {
public static final String MCW = multi-cloud-workshop;
public static final String LOAD_BALANCER = MCW + -lb;
public static final String DATABASE = MCW + -db;
public static final String WEB_SERVER_01 = MCW + -webserver-01;
public static final String WEB_SERVER_02 = MCW + -webserver-02;
private final ComputeService computeService;
public static void main(String[] args) {
NameNodes nameNodes = null;
try {
nameNodes = new NameNodes();
nameNodes.createServers();
} catch (Throwable e) {
e.printStackTrace();
} finally {
if (nameNodes != null) {
nameNodes.close();
}
}
}
public NameNodes() throws IOException {
IterableModule modules = ImmutableSet.Moduleof(
new SLF4JLoggingModule(),
new SshjSshClientModule());
Properties overrides = new Properties();
overrides.setProperty(POLL_INITIAL_PERIOD, 3);
overrides.setProperty(POLL_MAX_PERIOD, 3);
ComputeServiceContext context = ContextBuilder.newBuilder(aws-ec2)
.credentials(myAwsAccessKeyId, myAwsSecretAccessKey)
.modules(modules)
.overrides(overrides)
.buildView(ComputeServiceContext.class);
computeService = context.getComputeService();
}
private MapString, NodeMetadata createServers() throws
RunNodesException, IOException {
SetString nodeNames = ImmutableSet.of(DATABASE, WEB_SERVER_01,
WEB_SERVER_02, LOAD_BALANCER);
System.out.println(format(Creating servers %s, Joiner.on(,
).join(nodeNames)));
TemplateOptions options = computeService.templateOptions()
.nodeNames(nodeNames)
.inboundPorts(22);
Template template = computeService.templateBuilder()
.imageNameMatches(ubuntu/images/ubuntu-precise-12.04-amd64-server-20131003)
.locationId(us-west-2)
.hardwareId(m1.small)
.options(options)
.build();
Set? extends NodeMetadata nodes =
computeService.createNodesInGroup(MCW, 4, template);
MapString, NodeMetadata nameToNode = newHashMap();
System.out.println(Created servers:);
for (NodeMetadata node: nodes) {
String name = node.getName();
String publicIpAddress =
getOnlyElement(node.getPublicAddresses());
String user = node.getCredentials().getUser();
System.out.println(format( %-40s %s@%s, name, user,
publicIpAddress));
nameToNode.put(name, node);
}
return nameToNode;
}
private void close() {
computeService.getContext().close();
}
}
{code}
The output is
{code}
Creating servers multi-cloud-workshop-db, multi-cloud-workshop-webserver-01,
multi-cloud-workshop-webserver-02, multi-cloud-workshop-lb
Created servers:
multi-cloud-workshop-db ubuntu@54.184.78.205
multi-cloud-workshop-db ubuntu@54.203.107.107
multi-cloud-workshop-db ubuntu@54.202.100.94
multi-cloud-workshop-db ubuntu@54.184.52.175
{code}
Confirmed the names of the instances in the AWS console too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jclouds] Add keystone user add and delete methods. (#290)
Add support for the keystone user add and delete API. I have NOT yet tested this against a live environment. You can merge this Pull Request by running: git pull https://github.com/trainman419/jclouds master Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/290 -- Commit Summary -- * Add keystone user add and delete methods. -- File Changes -- M apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/features/UserApi.java (17) M apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/features/UserAsyncApi.java (25) M apis/openstack-keystone/src/test/java/org/jclouds/openstack/keystone/v2_0/features/UserApiExpectTest.java (37) A apis/openstack-keystone/src/test/resources/user_add.json (8) -- Patch Links -- https://github.com/jclouds/jclouds/pull/290.patch https://github.com/jclouds/jclouds/pull/290.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290
Re: [jclouds] Add keystone user add and delete methods. (#290)
@@ -123,4 +127,25 @@ @Fallback(EmptySetOnNotFoundOr404.class) ListenableFuture? extends Set? extends Role listRolesOfUserOnTenant(@PathParam(userId) String userId, @PathParam(tenantId) String tenantId); + + /** @see UserApi#add(String, String, Boolean, String) */ Needs proper Javadoc commenting. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290/files#r9694208
Re: [jclouds] Add keystone user add and delete methods. (#290)
@@ -123,4 +127,25 @@ @Fallback(EmptySetOnNotFoundOr404.class) ListenableFuture? extends Set? extends Role listRolesOfUserOnTenant(@PathParam(userId) String userId, @PathParam(tenantId) String tenantId); + + /** @see UserApi#add(String, String, Boolean, String) */ + @Named(user:add) + @POST + @SelectJson(user) + @Consumes(MediaType.APPLICATION_JSON) + @Path(/users) + @RequestFilters(AuthenticateRequest.class) + @Fallback(NullOnNotFoundOr404.class) + ListenableFuture? extends User add(@PayloadParam(username) String userName, +@PayloadParam(email) String userEmail, +@PayloadParam(enabled) boolean enabled, +@PayloadParam(OS-KSADM:password) String password); + + /** @see UserApi#delete(String) */ Needs proper Javadoc commenting. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290/files#r9694209
Re: [jclouds] Add keystone user add and delete methods. (#290)
The code looks good but we really do need at least a couple of live tests before we can accept this. When the live tests are ready I'll test them against [DevStack with Havana](http://blog.phymata.com/2013/12/18/devstack-havana-on-the-rackspace-cloud/). --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290#issuecomment-34938954
Re: [jclouds] Add keystone user add and delete methods. (#290)
Addressed javadoc issue. I reformatted the existing comments as well to keep things consistent. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290#issuecomment-34939055
Re: [jclouds] Add keystone user add and delete methods. (#290)
[jclouds » jclouds #839](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/839/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290#issuecomment-34940066
Re: [jclouds] Add keystone user add and delete methods. (#290)
Added live tests. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290#issuecomment-34941215
Re: [jclouds] Add keystone user add and delete methods. (#290)
[jclouds-pull-requests #598](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/598/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290#issuecomment-34941409
Re: [jclouds] Add keystone user add and delete methods. (#290)
[jclouds-pull-requests #599](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/599/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290#issuecomment-34942022
Re: [jclouds] Add keystone user add and delete methods. (#290)
[jclouds » jclouds #840](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/840/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/290#issuecomment-34942390
