Re: [jclouds] Fixes blob-related tests that fail occasionally (#683)
@@ -432,7 +433,13 @@ public void deleteObject(String name) throws
InterruptedException {
String container = getContainerName();
try {
addBlobToContainer(container, name, name, MediaType.TEXT_PLAIN);
+ if (view.getConsistencyModel() == ConsistencyModel.EVENTUAL) {
It would be great to replace these kinds of comparisons with
`Assert.isEqualTo(Object expected)` available to us in assertj. Just an idea,
WDYT?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/683/files#r24683078
Re: [jclouds] Adds Availability Zone to Server (#681)
Pushed to **master** 3e84133 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/681#issuecomment-74162595
Re: [jclouds] Adds Availability Zone to Server (#681)
Closed #681. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/681#event-235017688
Re: [jclouds] add availability zone to server (#574)
@limorbortman Thanks for the contribution! I pulled your branch and submitted #681 to get this into **master**. /cc @inbarsto --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/574#issuecomment-74152835
[jclouds] Adds Availability Zone to Server (#681)
Integrates PR #574 into master from [limorbortman](https://github.com/limorbortman/jclouds-1/commit/c8fa27054d458e3b519e2b923b4af9053cbed39f) Thanks! You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/681 -- Commit Summary -- * add availability zone to server -- File Changes -- M apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/config/NovaParserModule.java (22) M apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/Server.java (34) M apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/ServerExtendedAttributes.java (37) M apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/ServerWithSecurityGroups.java (10) A apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/ExtendedAvailabilityZoneExpectTest.java (50) A apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/ExtendedAvailabilityZoneLiveTest.java (41) M apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/features/ServerApiLiveTest.java (29) M apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/parse/ParseServerDetailsStatesTest.java (382) M apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/parse/ParseServerTest.java (37) M apis/openstack-nova/src/test/resources/server_details.json (1) -- Patch Links -- https://github.com/jclouds/jclouds/pull/681.patch https://github.com/jclouds/jclouds/pull/681.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/681
Re: [jclouds] Implemented compute attach interfaces extension. (#497)
Integrated in #679 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/497#issuecomment-74108047
Re: [jclouds] Nova Attach Interface Extension API (#679)
Closed #679. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/679#event-234102036
Re: [jclouds] Nova Attach Interface Extension API (#679)
Closed #679. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/679#event-234124144
Re: [jclouds] Nova Attach Interface Extension API (#679)
Pushed to **master** a356ca9 and 59fc232 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/679#issuecomment-73927744
Re: [jclouds] Nova Attach Interface Extension API (#679)
Reopened #679. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/679#event-234105917
[jclouds] Nova Attach Interface Extension API (#679)
This PR integrates #497 that implements the Nova compute attach interfaces extension. /cc @zack-shoylev You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/679 -- Commit Summary -- * Implemented Nova compute attach interfaces extension. -- File Changes -- M apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/NovaApi.java (8) M apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/config/NovaHttpApiModule.java (2) A apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/FixedIP.java (136) A apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/InterfaceAttachment.java (173) A apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/domain/PortState.java (57) A apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/AttachInterfaceApi.java (115) M apis/openstack-nova/src/main/java/org/jclouds/openstack/nova/v2_0/extensions/ExtensionNamespaces.java (5) A apis/openstack-nova/src/test/java/org/jclouds/openstack/nova/v2_0/extensions/AttachInterfaceApiExpectTest.java (89) A apis/openstack-nova/src/test/resources/attach_interface_details.json (14) A apis/openstack-nova/src/test/resources/attach_interfaces_list.json (16) M apis/openstack-nova/src/test/resources/extension_list_full.json (20) -- Patch Links -- https://github.com/jclouds/jclouds/pull/679.patch https://github.com/jclouds/jclouds/pull/679.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/679
Re: [jclouds] Remove cloudservers from allcompute/pom.xml (#668)
@andreaturli +1 from me as well, thank you! Pushed to master cc277e7 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/668#issuecomment-73808284
Re: [jclouds] Remove cloudservers from allcompute/pom.xml (#668)
Closed #668. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/668#event-233622139
[jclouds-labs-openstack] Initial support for OpenStack Poppy Service API (#178)
This PR is intended to get feedback from the community on the new builder support. It does _not_ include live tests. - Introduces `AutoValue.Builder` support to jclouds - Adds `Service` and related domain objects - Adds Poppy `ServiceApi` create and get methods - Adds `ServiceApiMockTest` /cc @zack-shoylev @nacx @demobox You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-labs-openstack/pull/178 -- Commit Summary -- * JCLOUDS-806: Support OpenStack Poppy Service API and introduce AutoValue.Builder support -- File Changes -- M openstack-poppy/pom.xml (1) M openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/PoppyApi.java (6) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Caching.java (82) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Domain.java (70) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Error.java (40) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Origin.java (85) M openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Provider.java (6) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Restriction.java (82) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Service.java (85) M openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/features/FlavorApi.java (16) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/features/ServiceApi.java (78) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/functions/ParseServiceURIFromHeaders.java (43) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/options/ServiceCreateOptions.java (67) A openstack-poppy/src/test/java/org/jclouds/openstack/poppy/v1/features/ServiceApiMockTest.java (130) A openstack-poppy/src/test/resources/poppy_service_create_request.json (37) A openstack-poppy/src/test/resources/poppy_service_get_response.json (72) -- Patch Links -- https://github.com/jclouds/jclouds-labs-openstack/pull/178.patch https://github.com/jclouds/jclouds-labs-openstack/pull/178.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/178
Re: [jclouds] Refactor ssh properties (#532)
@demobox Closing this PR. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/532#issuecomment-72109665
Re: [jclouds-labs-openstack] Add Rackspace CDN UK/US Providers (#177)
@andrewgaul Thanks again for the review! Pushed to **master** 8b17517 /cc @zack-shoylev --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/177#issuecomment-71787786
[jclouds-labs-openstack] Add Rackspace CDN UK/US Providers (#177)
This PR adds support for the Early Access Rackspace CDN US/UK Providers, which is based on the OpenStack Poppy API. You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-labs-openstack/pull/177 -- Commit Summary -- * Add Rackspace CDN UK/US Providers -- File Changes -- M pom.xml (2) A rackspace-cdn-uk/README.md (7) A rackspace-cdn-uk/pom.xml (125) A rackspace-cdn-uk/src/main/java/org/jclouds/rackspace/cdn/uk/CDNUKProviderMetadata.java (116) A rackspace-cdn-uk/src/test/java/org/jclouds/rackspace/cdn/uk/CDNUKProviderTest.java (28) A rackspace-cdn-uk/src/test/resources/logback.xml (56) A rackspace-cdn-us/README.md (7) A rackspace-cdn-us/pom.xml (125) A rackspace-cdn-us/src/main/java/org/jclouds/rackspace/cdn/us/CDNUSProviderMetadata.java (121) A rackspace-cdn-us/src/test/java/org/jclouds/rackspace/cdn/us/CDNUSProviderTest.java (28) A rackspace-cdn-us/src/test/resources/logback.xml (56) -- Patch Links -- https://github.com/jclouds/jclouds-labs-openstack/pull/177.patch https://github.com/jclouds/jclouds-labs-openstack/pull/177.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/177
Re: [jclouds-labs-openstack] Add Rackspace CDN UK/US Providers (#177)
+
+ /**
+* @return a {@link Properties} object containing the default provider
properties.
+* This returns the credential type, service type, and configured regions.
+*/
+ public static Properties defaultProperties() {
+ Properties properties = new Properties();
+ properties.setProperty(CREDENTIAL_TYPE,
CloudIdentityCredentialTypes.API_KEY_CREDENTIALS);
+ properties.setProperty(SERVICE_TYPE, ServiceType.CDN);
+
+ properties.setProperty(PROPERTY_REGIONS, ORD,DFW,IAD,SYD,HKG);
+ properties.setProperty(PROPERTY_REGION + .ORD. + ISO3166_CODES,
US-IL);
+ properties.setProperty(PROPERTY_REGION + .DFW. + ISO3166_CODES,
US-TX);
+ properties.setProperty(PROPERTY_REGION + .IAD. + ISO3166_CODES,
US-VA);
+ properties.setProperty(PROPERTY_REGION + .SYD. + ISO3166_CODES,
AU-NSW);
+ properties.setProperty(PROPERTY_REGION + .HKG. + ISO3166_CODES,
HK);
@andrewgaul Yes! UK is the special case. All of the other regions are available
via the US auth endpoint. HTH!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/177/files#r23667059
[jira] [Updated] (JCLOUDS-700) OpenStack Nova AvailabilityZone class missing hosts field
[
https://issues.apache.org/jira/browse/JCLOUDS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-700:
---
Assignee: (was: Jeremy Daggett)
OpenStack Nova AvailabilityZone class missing hosts field
---
Key: JCLOUDS-700
URL: https://issues.apache.org/jira/browse/JCLOUDS-700
Project: jclouds
Issue Type: Bug
Components: jclouds-compute
Affects Versions: 1.8.0
Reporter: Jeremy Daggett
Labels: api, openstack
Fix For: 2.0.0
The {{hosts}} field is not taken into consideration by the
{{AvailabilityZone}} class as documented
[here|https://github.com/openstack/nova/blob/grizzly-eol/nova/api/openstack/compute/contrib/availability_zone.py#L138].
The following actions should be taken to ensure the correct implementation:
* Add the {{hosts}} field to {{AvailabilityZone}} class.
* Move {{AvailabilityZone}} and {{ZoneState}} from the deprecated
{{org.jclouds.openstack.nova.v2_0.domain.zonescoped}} package to the correct
{{org.jclouds.openstack.nova.v2_0.domain}} package.
* Change {{ZoneState.available()}} to {{ZoneState.isAvailable()}}.
* Update expect/live tests.
* Deprecate where appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (JCLOUDS-695) Support OpenStack Heat Resource API
[ https://issues.apache.org/jira/browse/JCLOUDS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-695: --- Assignee: (was: Jeremy Daggett) Support OpenStack Heat Resource API --- Key: JCLOUDS-695 URL: https://issues.apache.org/jira/browse/JCLOUDS-695 Project: jclouds Issue Type: Sub-task Components: jclouds-labs-openstack Reporter: Jeremy Daggett Labels: api, openstack, orchestration http://developer.openstack.org/api-ref-orchestration-v1.html#stack-resources -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-694) Support OpenStack Heat Stack API
[ https://issues.apache.org/jira/browse/JCLOUDS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-694: --- Assignee: (was: Jeremy Daggett) Support OpenStack Heat Stack API Key: JCLOUDS-694 URL: https://issues.apache.org/jira/browse/JCLOUDS-694 Project: jclouds Issue Type: Sub-task Components: jclouds-labs-openstack Reporter: Jeremy Daggett Labels: api, openstack, orchestration http://developer.openstack.org/api-ref-orchestration-v1.html#stacks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-705) Support OpenStack Swift Storage Policies
[ https://issues.apache.org/jira/browse/JCLOUDS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-705: --- Assignee: (was: Jeremy Daggett) Support OpenStack Swift Storage Policies Key: JCLOUDS-705 URL: https://issues.apache.org/jira/browse/JCLOUDS-705 Project: jclouds Issue Type: New Feature Components: jclouds-blobstore, jclouds-labs-openstack Reporter: Jeremy Daggett Labels: openstack-swift http://docs.openstack.org/developer/swift/overview_policies.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-793) make blobstore put operations report server errors via HttpResponseException
[ https://issues.apache.org/jira/browse/JCLOUDS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-793: --- Assignee: (was: Jeremy Daggett) make blobstore put operations report server errors via HttpResponseException Key: JCLOUDS-793 URL: https://issues.apache.org/jira/browse/JCLOUDS-793 Project: jclouds Issue Type: Improvement Components: jclouds-blobstore Affects Versions: 1.8.1 Reporter: Daniel Hsueh Labels: features observed with openstack-swift 1.8.1 ObjectApi.put() if the server responds with a 4xx/5xx response, the put() call returns null for the etag would it be more useful if there was an HttpResponseException were thrown, with the actual request, response, and response code available? as of now, the null response only indicates that an etag was not found in the response, not that the whole request failed I observe that a failure to communicate (e.g. BackoffLimitedRetryHandler running through its retires) will result in an HttpResponseException there may also be an issue with consistency -- from perusing the AzureBlobClient and S3Client code it seems like an HttpException(did not receive ETag) would be thrown, and not a null etag I would also propose that GETs report 4xx/5xx responses via HttpResponseException as well I realize this is a major departure from existing behavior, perhaps this exception-reporting-on-error could be enabled via an override? thank you -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-559) Upgrade to JAX-RS 2.0
[ https://issues.apache.org/jira/browse/JCLOUDS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-559: --- Assignee: (was: Jeremy Daggett) Upgrade to JAX-RS 2.0 - Key: JCLOUDS-559 URL: https://issues.apache.org/jira/browse/JCLOUDS-559 Project: jclouds Issue Type: Improvement Components: jclouds-core Affects Versions: 2.0.0 Reporter: Jeremy Daggett Labels: patch Upgrade the JAX-RS library from 1.1.1 to the latest 2.0 version: javax.ws.rs » jsr311-api http://mvnrepository.com/artifact/javax.ws.rs/jsr311-api/1.1.1 javax.ws.rs » javax.ws.rs-api http://mvnrepository.com/artifact/javax.ws.rs/javax.ws.rs-api/2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JCLOUDS-537) Update blobstore examples
[ https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett resolved JCLOUDS-537. Resolution: Fixed Fix Version/s: 1.7.3 Update blobstore examples - Key: JCLOUDS-537 URL: https://issues.apache.org/jira/browse/JCLOUDS-537 Project: jclouds Issue Type: Improvement Components: jclouds-blobstore, jclouds-examples Affects Versions: 1.7.3 Reporter: Jeremy Daggett Assignee: Jeremy Daggett Labels: blobstore, examples Fix For: 1.7.3 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
+ @Override
+ public Builder toBuilder() {
+ return new Builder().fromApiMetadata(this);
+ }
+
+ public PoppyApiMetadata() {
+ this(new Builder());
+ }
+
+ protected PoppyApiMetadata(Builder builder) {
+ super(builder);
+ }
+
+ public static Properties defaultProperties() {
+ Properties properties = BaseHttpApiMetadata.defaultProperties();
+ properties.setProperty(SERVICE_TYPE, cdn);
There was a dependency on [PR 650]
(https://github.com/jclouds/jclouds/pull/650) that I submitted yesterday and
will be changed in the next PR for the Poppy `ServiceApi`.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/176/files#r23389705
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
+import org.jclouds.json.config.GsonModule.Iso8601DateAdapter;
+import org.jclouds.openstack.poppy.v1.PoppyApi;
+import org.jclouds.openstack.poppy.v1.handlers.PoppyErrorHandler;
+import org.jclouds.rest.ConfiguresHttpApi;
+import org.jclouds.rest.config.HttpApiModule;
+
+import com.google.common.base.Supplier;
+import com.google.gson.FieldNamingPolicy;
+import com.google.inject.TypeLiteral;
+
+@ConfiguresHttpApi
+public class PoppyHttpApiModule extends HttpApiModulePoppyApi {
+
+ @Override
+ protected void configure() {
+ bind(new TypeLiteralSupplierURI()
{}).annotatedWith(CDN.class).to(new TypeLiteralSupplierURI() {});
Sure! I followed the same pattern used in the [Cloud DNS
API](https://github.com/jclouds/jclouds/blob/master/apis/rackspace-clouddns/src/main/java/org/jclouds/rackspace/clouddns/v1/config/CloudDNSHttpApiModule.java#L38).
It uses the Keystone
[`ProviderModule`](https://github.com/jclouds/jclouds/blob/master/apis/openstack-keystone/src/main/java/org/jclouds/openstack/keystone/v2_0/config/KeystoneAuthenticationModule.java#L90)
because this is a global, regionless service.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/176/files#r23394909
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
+
+/**
+ * Provides access to Flavor features.
+ */
+@Beta
+@RequestFilters(AuthenticateRequest.class)
+@Consumes(MediaType.APPLICATION_JSON)
+@Endpoint(CDN.class)
+@Path(/flavors)
+public interface FlavorApi {
+
+ @Named(flavor:list)
+ @GET
+ @SelectJson(flavors)
+ @Fallback(EmptyFluentIterableOnNotFoundOr404.class)
+ FluentIterableFlavor list();
Great! I completely agree with using `ListT` in all of the APIs going
forward. :+1:
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/176/files#r23394809
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
+ try {
+ PoppyApi poppyApi = api(server.getUrl(/).toString(),
openstack-poppy, overrides);
+ FlavorApi api = poppyApi.getFlavorApi();
+
+ ListFlavor flavors = api.list().toList();
+
+ assertThat(server.getRequestCount()).isEqualTo(2);
+ assertAuthentication(server);
+ assertRequest(server.takeRequest(), GET, BASE_URI + /flavors);
+
+ assertThat(flavors).isNotEmpty();
+
+ } finally {
+ server.shutdown();
+ }
+ }
I will add the test.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/176/files#r23394937
Re: [jclouds] Fixes the exponential backoff for a value of 0 (#644)
@nacx I just did a line by line review with @zack-shoylev on this PR and it LGTM +1 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/644#issuecomment-70900850
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
@zack-shoylev I just submitted [PR 650](https://github.com/jclouds/jclouds/pull/650) a few minutes ago to add the CDN service type to Keystone. Regarding the AutoValue naming, I sent a [message](http://markmail.org/message/dhlr44ux74vajjtx) to the list for community feedback. I propose that we use `getXXX()` across the project. Now that the 500 error has been fixed, I propose that we squash these commits and merge it. The Service API will be in the next Poppy PR. WDYT? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/176#issuecomment-70879202
Re: [jclouds] JCLOUDS-794: Use bogus URL for generic S3 endpoint (#649)
@andrewgaul Oh yeah, wise decision to change this endpoint! +1 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/649#issuecomment-70878877
Re: [jclouds] Add CDN service type for OpenStack Poppy (#650)
Pushed to **master** c902fbf --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/650#issuecomment-70905727
[jclouds] Add CDN service type for OpenStack Poppy (#650)
This PR adds CDN to the list of known service types returned in the Keystone Service Catalog. You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/650 -- Commit Summary -- * Add CDN service type for OpenStack Poppy -- File Changes -- M apis/openstack-keystone/src/main/java/org/jclouds/openstack/v2_0/ServiceType.java (5) -- Patch Links -- https://github.com/jclouds/jclouds/pull/650.patch https://github.com/jclouds/jclouds/pull/650.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/650
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
Closed #176. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/176#event-222812036
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
Squashed and pushed to **master** a006915 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/176#issuecomment-70972868
Re: [jclouds] fix usermetadata check on OS X (#648)
@kahing I will pull the changes over later this morning and let you know, thanks! :+1: --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/648#issuecomment-70680769
Re: [jclouds] fix usermetadata check on OS X (#648)
@kahing Well, that was strange... I had a git remote problem with your repo and now that it is sorted out, `master` is happy again on OS X! +1 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/648#issuecomment-70752052
Re: [jclouds] fix usermetadata check on OS X (#648)
@kahing Thanks again! Can you please address the comment from @andrewgaul above? Once that looks good, we should get it merged. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/648#issuecomment-70753228
Re: [jclouds] fix usermetadata check on OS X (#648)
@kahing I just run `mvn clean install` :smile: --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/648#issuecomment-70743082
Re: [jclouds] Update AutoValue to version 1.0 (#646)
@zack-shoylev Glad to be of service! :grinning: --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/646#issuecomment-70730960
Re: [jclouds-labs] Add missing dependency to Profitbricks (#123)
@nacx It looks like I created my branch prior to commit 6e1a037. No wonder it failed! Thanks! :sunglasses: --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/123#issuecomment-70520164
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
+
+ assertThat(online).isTrue();
+ } finally {
+ server.shutdown();
+ }
+ }
+
+ @Test(enabled = false)
+ public void testPingFailOn500() throws Exception {
+ MockWebServer server = mockOpenStackServer();
+ server.enqueue(addCommonHeaders(new
MockResponse().setBody(stringFromResource(/access.json;
+ server.enqueue(addCommonHeaders(new
MockResponse().setResponseCode(500)));
+
+ try {
+ PoppyApi poppyApi = api(server.getUrl(/).toString(),
openstack-poppy, overrides);
+ boolean online = poppyApi.ping();
Yes, it hangs on the `ping()`. Note that the test is currently disabled.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/176/files#r23181622
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
+]
+}
+],
+token: {
+tenant: {
+name: jclouds,
+id: 123123,
+enabled: true,
+description: null
+},
+id: TOKEN,
+expires: 2014-04-28T22:48:24Z,
+issued_at: 2014-04-28T21:48:24.972896
+}
+}
+}
Yes, I have been including newlines for all JSON resources.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/176/files#r23181991
Re: [jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.jclouds.openstack.poppy.v1.domain; + +import java.util.List; +import java.util.Set; + +import org.jclouds.json.SerializedNames; +import org.jclouds.openstack.v2_0.domain.Link; + +import com.google.auto.value.AutoValue; + +/** + * Representation of an OpenStack Poppy CDN Flavor. Thanks, I plan to update the javadocs across the board once the `ServiceApi` is implemented and complete. HTH --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/176/files#r23182132
[jira] [Commented] (JCLOUDS-806) Support OpenStack Poppy API
[ https://issues.apache.org/jira/browse/JCLOUDS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14282948#comment-14282948 ] Jeremy Daggett commented on JCLOUDS-806: https://github.com/jclouds/jclouds-labs-openstack/pull/176 Support OpenStack Poppy API --- Key: JCLOUDS-806 URL: https://issues.apache.org/jira/browse/JCLOUDS-806 Project: jclouds Issue Type: New Feature Components: jclouds-labs-openstack Reporter: Jeremy Daggett Assignee: Jeremy Daggett Labels: cdn, openstack OpenStack Poppy is a modular, vendor-neutral API, that wraps provisioning instructions for all CDN vendors that support it. - REST API for CDN service provisioning - Multi-tenant - Integrated with Keystone for Authentication - Integrated with Designate for dynamic CNAMEing - Support for CDN providers (Fastly, MaxCDN, CloudFront, Akamai, Edgecast) Rackspace has [Early Access|http://docs.rackspace.com/cdn/api/v1.0/cdn-devguide/content/Overview.html] support for this API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (JCLOUDS-806) Support OpenStack Poppy API
Jeremy Daggett created JCLOUDS-806: -- Summary: Support OpenStack Poppy API Key: JCLOUDS-806 URL: https://issues.apache.org/jira/browse/JCLOUDS-806 Project: jclouds Issue Type: New Feature Components: jclouds-labs-openstack Reporter: Jeremy Daggett Assignee: Jeremy Daggett OpenStack Poppy is a modular, vendor-neutral API, that wraps provisioning instructions for all CDN vendors that support it. - REST API for CDN service provisioning - Multi-tenant - Integrated with Keystone for Authentication - Integrated with Designate for dynamic CNAMEing - Support for CDN providers (Fastly, MaxCDN, CloudFront, Akamai, Edgecast) Rackspace has [Early Access|http://docs.rackspace.com/cdn/api/v1.0/cdn-devguide/content/Overview.html] support for this API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds-labs] Split Auto dependencies (#122)
Closed #122. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/122#event-220239969
Re: [jclouds] Add Rackspace CDN service type (#647)
Closed #647. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/647#event-220249255
Re: [jclouds-labs-google] Split Auto dependencies (#123)
Closed #123. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/123#event-220387458
[jclouds-labs-openstack] Initial support for OpenStack Poppy (#176)
This PR provides support for the OpenStack Poppy (CDN) API and implements the Flavor API. Unit tests and live tests are provided, however MWS is constantly hanging in the [`PoppyMockTest.testPingFailOn500()`](https://github.com/rackerlabs/jclouds-labs-openstack/compare/jclouds:master...rackerlabs:poppy#diff-ae97466568519b14c8faa1a515aed39bR54). This test is currently disabled, and I would appreciate any help on why this test hangs! :confused: Running the live tests against the Early Access Rackspace CDN endpoint requires the following command: ``` $ mvn clean install -Plive -Dtest.openstack-poppy.identity=username -Dtest.openstack-poppy.credential=password -Dtest.openstack-poppy.endpoint=keystone-auth-url -Djclouds.keystone.service-type=rax:cdn ``` Looking forward to the feedback, thx! You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-labs-openstack/pull/176 -- Commit Summary -- * Initial OpenStack Poppy skeleton and support for Flavor API -- File Changes -- A openstack-poppy/README.md (28) A openstack-poppy/pom.xml (130) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/PoppyApi.java (65) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/PoppyApiMetadata.java (92) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/PoppyFallbacks.java (39) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/config/CDN.java (33) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/config/PoppyHttpApiModule.java (53) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Flavor.java (44) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/domain/Provider.java (42) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/features/FlavorApi.java (62) A openstack-poppy/src/main/java/org/jclouds/openstack/poppy/v1/handlers/PoppyErrorHandler.java (52) A openstack-poppy/src/test/java/org/jclouds/openstack/poppy/v1/PoppyApiMetadataTest.java (34) A openstack-poppy/src/test/java/org/jclouds/openstack/poppy/v1/features/FlavorApiLiveTest.java (71) A openstack-poppy/src/test/java/org/jclouds/openstack/poppy/v1/features/FlavorApiMockTest.java (104) A openstack-poppy/src/test/java/org/jclouds/openstack/poppy/v1/features/PoppyApiMockTest.java (73) A openstack-poppy/src/test/java/org/jclouds/openstack/poppy/v1/internal/BasePoppyApiLiveTest.java (45) A openstack-poppy/src/test/java/org/jclouds/openstack/poppy/v1/internal/BasePoppyApiMockTest.java (43) A openstack-poppy/src/test/resources/access.json (242) A openstack-poppy/src/test/resources/logback.xml (58) A openstack-poppy/src/test/resources/poppy_flavor_get_response.json (20) A openstack-poppy/src/test/resources/poppy_flavor_list_response.json (24) M pom.xml (1) -- Patch Links -- https://github.com/jclouds/jclouds-labs-openstack/pull/176.patch https://github.com/jclouds/jclouds-labs-openstack/pull/176.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/176
Re: [jclouds] Refactor blobstore filesystem tests for Mac OS X (#643)
@kahing @andrewgaul Just FYI I didn't spend any more time on this after closing this PR because of other priorities. As of today, the master branch has been broken for a week on Mac OS X. :disappointed: Can you guys please provide a fix for it that makes sense for the filesystem provider? Should I submit a JIRA? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/643#issuecomment-70349617
Re: [jclouds] Update AutoValue to version 1.0 (#646)
Pushed to **master** 24f9af7 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/646#issuecomment-70350109
Re: [jclouds] add availability zone to server (#574)
@limorbortman Can you provide an update on this PR? Let's work on getting this merged next week. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/574#issuecomment-70350832
Re: [jclouds] Implemented compute attach interfaces extension. (#497)
@RoadRoller Happy New Year! Do you have time to pick this back up now? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/497#issuecomment-70350937
Re: [jclouds] Refactor ssh properties (#532)
@demobox Should we just close this? It was a little refactor, but if there is no perceived value, let's just close it. Let me know, thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/532#issuecomment-70351036
Re: [jclouds] [JCLOUDS-609] Adding vCloud API 1.5 support (#418)
@melanj I am closing this PR since vcloud and vcloud-director have been removed from both the [jclouds](https://github.com/jclouds/jclouds/pull/604) and [jclouds-labs](https://github.com/jclouds/jclouds-labs/pull/111) repos. cc @demobox @nacx --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/418#issuecomment-70178078
Re: [jclouds] [JCLOUDS-609] Adding vCloud API 1.5 support (#418)
Closed #418. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/418#event-219765488
[jira] [Created] (JCLOUDS-803) Refactor OpenStack Live Tests
Jeremy Daggett created JCLOUDS-803:
--
Summary: Refactor OpenStack Live Tests
Key: JCLOUDS-803
URL: https://issues.apache.org/jira/browse/JCLOUDS-803
Project: jclouds
Issue Type: Improvement
Components: jclouds-core
Reporter: Jeremy Daggett
Refactor live tests to use a {{@DataProvider}} for specifying the current
region. Currently, the behavior is to loop through regions in every test
method. Using this in combination with {{@AfterMethod}}, will improve
readability and cleanup of test resources.
Refer to the conversation in jclouds-labs-openstack [PR 174|
https://github.com/jclouds/jclouds-labs-openstack/pull/174] for additional
context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (JCLOUDS-634) Support Swift Account ACLs
[ https://issues.apache.org/jira/browse/JCLOUDS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-634: --- Assignee: (was: Jeremy Daggett) Support Swift Account ACLs -- Key: JCLOUDS-634 URL: https://issues.apache.org/jira/browse/JCLOUDS-634 Project: jclouds Issue Type: New Feature Components: jclouds-labs-openstack Reporter: Jeremy Daggett Labels: openstack-swift Fix For: 2.0.0 In addition to supporting Container ACLs as described in JCLOUDS-530, Account ACLs should also be supported in the Swift API. http://docs.openstack.org/developer/swift/misc.html#swift.common.middleware.acl.format_acl_v2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-239) Add an Extension to compute for disks/volumes
[ https://issues.apache.org/jira/browse/JCLOUDS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-239: --- Assignee: (was: Jeremy Daggett) Add an Extension to compute for disks/volumes - Key: JCLOUDS-239 URL: https://issues.apache.org/jira/browse/JCLOUDS-239 Project: jclouds Issue Type: Improvement Components: jclouds-compute Reporter: Andrew Bayer Fix For: 2.0.0 Most compute providers/APIs have some concept of disks/volumes other than the boot disk - possibly all of them, though I'd have to check to be sure. We should have an abstraction for dealing with those disks - creating new ones, attaching them to instances, attaching additional volumes at instance creation time as well as later, destroying them, snapshotting, etc... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-530) Support OpenStack Swift Container Access Control Lists
[ https://issues.apache.org/jira/browse/JCLOUDS-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-530: --- Assignee: (was: Jeremy Daggett) Support OpenStack Swift Container Access Control Lists -- Key: JCLOUDS-530 URL: https://issues.apache.org/jira/browse/JCLOUDS-530 Project: jclouds Issue Type: Improvement Components: jclouds-labs-openstack Reporter: Everett Toews http://docs.openstack.org/api/openstack-object-storage/1.0/content/special-metadata-acls.html http://docs.rackspace.com/files/api/v1/cf-devguide/content/Container_ACLs-d1e.html Overview of the Rackspace implementation: http://www.rackspace.com/blog/create-cloud-files-container-level-access-control-policies/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-280) Missing create Bootable Volume with Cinder
[ https://issues.apache.org/jira/browse/JCLOUDS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-280: --- Assignee: (was: Jeremy Daggett) Missing create Bootable Volume with Cinder -- Key: JCLOUDS-280 URL: https://issues.apache.org/jira/browse/JCLOUDS-280 Project: jclouds Issue Type: Bug Affects Versions: 1.6.3 Reporter: BK Lau Priority: Blocker Currently Cinder allows user to create a Bootable Volume but we are missing that feature. This feature is important for long-running instance which allows instance to fail and reboot without loosing any data. See also See https://bugs.launchpad.net/openstack-api-site/+bug/1215147 See http://docs.openstack.org/grizzly/openstack-compute/admin/content/instance-creation.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-514) Need to be able to attach block volumes at instance creation in Nova
[
https://issues.apache.org/jira/browse/JCLOUDS-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-514:
---
Assignee: (was: Jeremy Daggett)
Need to be able to attach block volumes at instance creation in Nova
Key: JCLOUDS-514
URL: https://issues.apache.org/jira/browse/JCLOUDS-514
Project: jclouds
Issue Type: New Feature
Components: jclouds-compute, jclouds-core
Reporter: Jasdeep Hundal
Labels: features
The Nova API allows for attaching block volumes to an instance at creation
time, it would be nice to access this feature through JClouds.
Example Nova JSON:
{server: {name: jasdeep-test, imageRef:
ed5912af-ff25-4ff3-bbec-6c00898c14b8, block_device_mapping:
[{volume_size: , volume_id: f696b2aa-4c83-40ad-ab25-984b59dd2e3c,
delete_on_termination: 1, device_name: vda}], flavorRef: small,
max_count: 1, min_count: 1}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (JCLOUDS-718) Compute TemplateOptions.getGroups() is ambigous
[
https://issues.apache.org/jira/browse/JCLOUDS-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-718:
---
Assignee: (was: Jeremy Daggett)
Compute TemplateOptions.getGroups() is ambigous
---
Key: JCLOUDS-718
URL: https://issues.apache.org/jira/browse/JCLOUDS-718
Project: jclouds
Issue Type: Bug
Components: jclouds-compute
Affects Versions: 1.8.0
Reporter: Jeremy Daggett
Priority: Minor
Labels: compute, security-groups
From a user's perspective, this method is quite confusing. What does this
method _actually_ return? Groups of IPs, groups of availability zones... What
specifically?
In the {{TemplateOptions}} class, the {{getGroups()}} method lacks intent and
should be aptly renamed to {{getSecurityGroups()}}. The method should be
deprecated and replaced with the suggested method signature, and marked for
removal in 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (JCLOUDS-710) OpenStack Keystone should use Guava MediaType
[
https://issues.apache.org/jira/browse/JCLOUDS-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett resolved JCLOUDS-710.
Resolution: Invalid
This Keystone MediaType class is a value object and should not use the Guava
class.
OpenStack Keystone should use Guava MediaType
-
Key: JCLOUDS-710
URL: https://issues.apache.org/jira/browse/JCLOUDS-710
Project: jclouds
Issue Type: Improvement
Components: jclouds-core
Affects Versions: 1.6.0, 1.7.0, 1.8.0
Reporter: Jeremy Daggett
Assignee: Jeremy Daggett
Priority: Minor
Labels: openstack
Prefer Guava's MediaType over the
{{org.jclouds.openstack.keystone.v2_0.domain.MediaType}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
@nacx @zack-shoylev Refactoring these tests is going to take a lot more work than anticipated. I just submitted [JCLOUDS-803](https://issues.apache.org/jira/browse/JCLOUDS-803) to track the issue. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174#issuecomment-69971569
[jira] [Resolved] (JCLOUDS-731) Support Nova Block Device Mapping v2
[ https://issues.apache.org/jira/browse/JCLOUDS-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett resolved JCLOUDS-731. Resolution: Implemented Fix Version/s: 1.8.2 2.0.0 https://github.com/jclouds/jclouds/pull/558 Pushed to master 00b2de6 and 1.8.x 8122f0b Support Nova Block Device Mapping v2 Key: JCLOUDS-731 URL: https://issues.apache.org/jira/browse/JCLOUDS-731 Project: jclouds Issue Type: New Feature Components: jclouds-core Reporter: Jeremy Daggett Assignee: Jeremy Daggett Labels: openstack-nova Fix For: 2.0.0, 1.8.2 This new format for [block devices|https://github.com/openstack/nova/blob/stable/havana/nova/block_device.py] was introduced in the OpenStack Havana release and should be supported in jclouds. Refer to the [API docs|http://developer.openstack.org/api-ref-compute-v2-ext.html#ext-os-block-device-mapping-v2-boot] for additional information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCLOUDS-640) Add InfoApi to openstack-swift
[ https://issues.apache.org/jira/browse/JCLOUDS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett updated JCLOUDS-640: --- Assignee: (was: Jeremy Daggett) Add InfoApi to openstack-swift -- Key: JCLOUDS-640 URL: https://issues.apache.org/jira/browse/JCLOUDS-640 Project: jclouds Issue Type: Improvement Components: jclouds-blobstore, jclouds-labs-openstack Affects Versions: 1.8.0 Reporter: Jeremy Daggett Labels: api, openstack-swift Fix For: 2.0.0 Add support for Swift discoverable features: http://docs.openstack.org/api/openstack-object-storage/1.0/content/discoverability.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds] Update okhttp to version 2.2.0 (#641)
@nacx Yes, the downstream repos will inherit this value. Do we need to update the 1.8.x branch with this commit? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/641#issuecomment-70006489
Re: [jclouds] Update okhttp to version 2.2.0 (#641)
Closed #641. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/641#event-219094157
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
Closed #174. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174#event-219094749
[jclouds] Update AutoValue to version 1.0 (#646)
AutoValue was [updated](https://github.com/google/auto/commit/c36dbb535c905fb2cdbfa2755f25241d90dbd9c4) to version 1.0 recently! This PR is pretty self-explainatory :smile: **NOTE:** Downstream repositories broke when making this change initially. I submitted [PR 122](https://github.com/jclouds/jclouds-labs/pull/122) in `jclouds-labs` and [PR 123](https://github.com/jclouds/jclouds-labs-google/pull/123) in `jclouds-labs-google` to split out the dependencies into `auto-service` and `auto-value`. They will need to be committed _prior_ to merging this PR! You can merge this Pull Request by running: git pull https://github.com/rackspace/jclouds update-autovalue-1.0 Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/646 -- Commit Summary -- * Update AutoValue to version 1.0 -- File Changes -- M project/pom.xml (2) -- Patch Links -- https://github.com/jclouds/jclouds/pull/646.patch https://github.com/jclouds/jclouds/pull/646.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/646
[jclouds] Add Rackspace CDN service type (#647)
This PR adds the Early Access Rackspace CDN service `rax:cdn` to the known service types that can be returned in the Cloud Identity Service Catalog. For additional info on the CDN service, please refer to the [docs](http://docs.rackspace.com/cdn/api/v1.0/cdn-devguide/content/Overview.html). You can merge this Pull Request by running: git pull https://github.com/rackspace/jclouds cdn-service-type Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/647 -- Commit Summary -- * Add Rackspace CDN service type -- File Changes -- M apis/rackspace-cloudidentity/src/main/java/org/jclouds/rackspace/cloudidentity/v2_0/ServiceType.java (5) -- Patch Links -- https://github.com/jclouds/jclouds/pull/647.patch https://github.com/jclouds/jclouds/pull/647.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/647
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
@nacx @zack-shoylev Thanks! Pushed to **master** e934350 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174#issuecomment-70009224
[jclouds-labs-google] Split Auto dependencies (#123)
Splitting the `auto-service` and `auto-value` dependencies allows us to control individual versions of these libraries. You can merge this Pull Request by running: git pull https://github.com/rackerlabs/jclouds-labs-google split-auto-dependencies Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-labs-google/pull/123 -- Commit Summary -- * Split Auto dependencies into auto-service and auto-value -- File Changes -- M google-cloud-storage/pom.xml (5) M google-compute-engine/pom.xml (5) -- Patch Links -- https://github.com/jclouds/jclouds-labs-google/pull/123.patch https://github.com/jclouds/jclouds-labs-google/pull/123.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/123
[jclouds-labs] Split Auto dependencies (#122)
Splitting the auto-service and auto-value dependencies allows us to control individual versions of these libraries. You can merge this Pull Request by running: git pull https://github.com/rackerlabs/jclouds-labs split-auto-dependencies Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-labs/pull/122 -- Commit Summary -- * Split Auto dependencies into auto-service and auto-value -- File Changes -- M abiquo/pom.xml (5) M azurecompute/pom.xml (6) M docker/pom.xml (5) -- Patch Links -- https://github.com/jclouds/jclouds-labs/pull/122.patch https://github.com/jclouds/jclouds-labs/pull/122.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/122
Re: [jclouds] Update okhttp to version 2.2.0 (#641)
@nacx Thanks for the clarification! Pushed to **master** e09b615 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/641#issuecomment-70009026
Re: [jclouds] Refactor blobstore filesystem tests for Mac OS X (#643)
Closed #643. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/643#event-218319306
[jclouds] Refactor blobstore filesystem tests for Mac OS X (#643)
This PR refactors the filesystem blobstore tests slightly for Mac OS. - Utilizes class/method level `dataProvider` and `dataProviderClass` in tests where necessary - (minor) 3-space indent cleanup `org.jclouds.util.TestUtils` - pulled up constants from `org.jclouds.filesystem.utils.TestUtils` - pulled up `@DataProvider` for Mac OS/Windows - pulled up `isWindowsOs()` method `org.jclouds.filesystem.integration.FilesystemBlobIntegrationTest` - pulled up description of Mac OS xattrs bug info to class level - added failing methods from `BaseBlobIntegrationTest` - now skips all tests on Mac OS @zack-shoylev Can you please run this on Windows for a sanity check? Thx! You can merge this Pull Request by running: git pull https://github.com/rackspace/jclouds refactor/filesystem-tests-osx Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/643 -- Commit Summary -- * Refactor blobstore filesystem tests for Mac OS X -- File Changes -- M apis/filesystem/src/test/java/org/jclouds/filesystem/FilesystemBlobStoreTest.java (14) M apis/filesystem/src/test/java/org/jclouds/filesystem/integration/FilesystemBlobIntegrationTest.java (66) M apis/filesystem/src/test/java/org/jclouds/filesystem/integration/FilesystemContainerIntegrationTest.java (17) M apis/filesystem/src/test/java/org/jclouds/filesystem/strategy/internal/FilesystemStorageStrategyImplTest.java (18) M apis/filesystem/src/test/java/org/jclouds/filesystem/utils/TestUtils.java (356) M core/src/test/java/org/jclouds/utils/TestUtils.java (30) -- Patch Links -- https://github.com/jclouds/jclouds/pull/643.patch https://github.com/jclouds/jclouds/pull/643.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/643
Re: [jclouds] disable directory blob tests in OS X (#640)
@kahing @andrewgaul After pulling this commit and running the tests again, I am
getting two new failures :confused: :
```
Failed tests:
FilesystemBlobIntegrationTestBaseBlobIntegrationTest.testPutByteSource:531-BaseBlobIntegrationTest.testPut:584
Expecting:
{}
to be equal to:
{key1=value1, key2=value2}
but was not.
FilesystemBlobIntegrationTestBaseBlobIntegrationTest.testPutInputStream:539-BaseBlobIntegrationTest.testPut:584
Expecting:
{}
to be equal to:
{key1=value1, key2=value2}
but was not.
```
Any insight is appreciated, thx!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/640#issuecomment-69770173
Re: [jclouds] disable directory blob tests in OS X (#640)
We should skip those additional two tests as well. I will submit a PR shortly with the changes, thx! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/640#issuecomment-69775234
Re: [jclouds] Refactor blobstore filesystem tests for Mac OS X (#643)
@andrewgaul sure thing. closing... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/643#issuecomment-69807025
Re: [jclouds] Use AutoService for creation of Service Loader Metadata (#621)
Pushed to **master** d3c1e2e and **1.8.x** bc48aad --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/621#issuecomment-69630178
Re: [jclouds] support directory blobs (#637)
@gaul @kahing Hi! I wanted to give you a head's up that on Mac OS X, I am consistently seeing these failures on master: ``` Failed tests: FilesystemBlobStoreTest.testGetDirectoryBlob:488 expected [true] but found [false] FilesystemBlobStoreTest.testListDirectoryBlobs:505 expected [true] but found [false] FilesystemBlobStoreTest.testPutDirectoryBlobs:471 expected [true] but found [false] FilesystemStorageStrategyImplTest.testDeleteIntermediateDirectoryBlob:399 expected [true] but found [false] FilesystemStorageStrategyImplTest.testGetDirectoryBlob:360 expected [true] but found [false] FilesystemStorageStrategyImplTest.testWriteDirectoryBlob:352 expected [true] but found [false] ``` Looking into a fix... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/637#issuecomment-69624045
Re: [jclouds] Use AutoService for creation of Service Loader Metadata (#621)
Closed #621. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/621#event-217609105
Re: [jclouds] disable directory blob tests in OS X (#640)
@kahing Thanks for the fix! This is exactly how I worked around the issue earlier this morning. As soon as the build succeeds, I am +1 for this PR. cc/ @andrewgaul --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/640#issuecomment-69632506
[jclouds] Update okhttp to version 2.2.0 (#641)
This PR updates the `okhttp` dependency to version **2.2.0**. There are quite a number of [fixes](https://github.com/square/okhttp/blob/master/CHANGELOG.md#version-220) in this release. For APIs that require this dependency, the new [interceptors](https://github.com/square/okhttp/wiki/Interceptors) could prove to be a very useful feature. You can merge this Pull Request by running: git pull https://github.com/rackspace/jclouds update-okhttp-2.2.0 Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/641 -- Commit Summary -- * Update okhttp to version 2.2.0 -- File Changes -- M project/pom.xml (2) -- Patch Links -- https://github.com/jclouds/jclouds/pull/641.patch https://github.com/jclouds/jclouds/pull/641.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/641
Re: [jclouds] Backport Chef Map ordering to 1.8.x (#639)
Closed #639. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/639#event-217479324
[jclouds] Backport Chef Map ordering to 1.8.x (#639)
In attempting to backport the `AutoService` changes to the **1.8.x** branch today, I consistently ran into test failures because of this ordering issue. Apparently, commit [cd4ce6](https://github.com/jclouds/jclouds/commit/cd4ce6b1923b37c30a98f3ff5c54947c68ecf292) had not been backported. :cry: cc @nacx You can merge this Pull Request by running: git pull https://github.com/rackspace/jclouds backport-JCLOUDS-428-1.8.x Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/639 -- Commit Summary -- * JCLOUDS-428: Use Maps with a consistent iteration order -- File Changes -- M apis/chef/src/main/java/org/jclouds/chef/internal/BaseChefService.java (2) M apis/chef/src/main/java/org/jclouds/ohai/functions/NestSlashKeys.java (4) M apis/chef/src/test/java/org/jclouds/chef/internal/BaseChefServiceTest.java (4) M apis/chef/src/test/java/org/jclouds/ohai/config/OhaiModuleTest.java (2) M apis/chef/src/test/java/org/jclouds/ohai/functions/NestSlashKeysTest.java (26) -- Patch Links -- https://github.com/jclouds/jclouds/pull/639.patch https://github.com/jclouds/jclouds/pull/639.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/639
Re: [jclouds-labs-aws] Use AutoService for creation of Service Loader Metadata (#67)
Pushed to **master** 0628788 and **1.8.x** d315755 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-aws/pull/67#issuecomment-69220864
[jira] [Resolved] (JCLOUDS-568) Swift - allow easy update of object content-type
[ https://issues.apache.org/jira/browse/JCLOUDS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Daggett resolved JCLOUDS-568. Resolution: Unresolved Swift - allow easy update of object content-type Key: JCLOUDS-568 URL: https://issues.apache.org/jira/browse/JCLOUDS-568 Project: jclouds Issue Type: Improvement Components: jclouds-labs-openstack Affects Versions: 1.7.2 Reporter: Zack Shoylev Assignee: Jeremy Daggett the current metadata call updateMetadata does not support sending a content-type to change the object content-type. If this is not supported in a different way, this should be supported by this call. This might require replacing the Produce() with a filter, and making sure content-type is not escaped by OBJECT_METADATA_PREFIX; but there might be other issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (JCLOUDS-802) Non-metadata Swift headers cannot be updated
Jeremy Daggett created JCLOUDS-802: -- Summary: Non-metadata Swift headers cannot be updated Key: JCLOUDS-802 URL: https://issues.apache.org/jira/browse/JCLOUDS-802 Project: jclouds Issue Type: Bug Components: jclouds-core Affects Versions: 1.8.1 Reporter: Jeremy Daggett Assignee: Jeremy Daggett Swift has the ability to update additional headers (metadata) associated with either a [container|http://docs.rackspace.com/files/api/v1/cf-devguide/content/POST_updateacontainermeta_v1__account___container__containerServicesOperations_d1e000.html] or an [object|http://docs.rackspace.com/files/api/v1/cf-devguide/content/POST_updateaobjmeta_v1__account___container___object__objectServicesOperations_d1e000.html]. The ContainerApi and ObjectApi updateMetadata() method should allow updates to these additional headers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
+ + assertEquals(network.getId(), net.getId()); + assertEquals(network.getName(), jclouds-test); + assertTrue(network.getSubnets().isEmpty()); + assertNotNull(networkApi.update(net.getId(), Network.updateBuilder().name(jclouds-live-test).build())); + + network = networkApi.get(net.getId()); + + assertEquals(network.getId(), net.getId()); + assertEquals(network.getName(), jclouds-live-test); + assertTrue(network.getSubnets().isEmpty()); + + Network net2 = networkApi.create(Network.createBuilder(jclouds-test2).build()); + assertNotNull(net2); + + assertTrue(networkApi.delete(net.getId())); @nacx We should add this to our best practices. :+1: --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174/files#r21694580
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
@nacx @zack-shoylev I completely agree that we should fix things as we find them. However, IMHO, I think we should step back and address any Neutron test cleanup first and then the providers in separate PRs. I just updated the logger files for now. Thoughts? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174#issuecomment-7179
[jira] [Commented] (JCLOUDS-793) make blobstore put operations report server errors via HttpResponseException
[ https://issues.apache.org/jira/browse/JCLOUDS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14242005#comment-14242005 ] Jeremy Daggett commented on JCLOUDS-793: Thanks [~dchsueh], if you could share any snippets of the exceptions from the logs, that would be great. make blobstore put operations report server errors via HttpResponseException Key: JCLOUDS-793 URL: https://issues.apache.org/jira/browse/JCLOUDS-793 Project: jclouds Issue Type: Improvement Components: jclouds-blobstore Affects Versions: 1.8.1 Reporter: Daniel Hsueh Assignee: Jeremy Daggett Labels: features observed with openstack-swift 1.8.1 ObjectApi.put() if the server responds with a 4xx/5xx response, the put() call returns null for the etag would it be more useful if there was an HttpResponseException were thrown, with the actual request, response, and response code available? as of now, the null response only indicates that an etag was not found in the response, not that the whole request failed I observe that a failure to communicate (e.g. BackoffLimitedRetryHandler running through its retires) will result in an HttpResponseException there may also be an issue with consistency -- from perusing the AzureBlobClient and S3Client code it seems like an HttpException(did not receive ETag) would be thrown, and not a null etag I would also propose that GETs report 4xx/5xx responses via HttpResponseException as well I realize this is a major departure from existing behavior, perhaps this exception-reporting-on-error could be enabled via an override? thank you -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds] Use AutoService for creation of Service Loader Metadata (#621)
@nacx Last of the cleanup here, thx. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/621#issuecomment-66326578
Re: [jclouds] Use AutoService for creation of Service Loader Metadata (#621)
@nacx 7b596a9 should address your comments. My apologies for any inconvenience. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/621#issuecomment-66371066
[jira] [Commented] (JCLOUDS-153) Remove the jclouds Executors
[ https://issues.apache.org/jira/browse/JCLOUDS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238149#comment-14238149 ] Jeremy Daggett commented on JCLOUDS-153: [~nacx] Do you know where we stand on this issue? Remove the jclouds Executors Key: JCLOUDS-153 URL: https://issues.apache.org/jira/browse/JCLOUDS-153 Project: jclouds Issue Type: Sub-task Components: jclouds-core Affects Versions: 1.7.0 Reporter: Ignasi Barrera Once all providers and apis have been un-asynched, the jclouds executors (and all their related stuff such as the FutureIterables class) used to perform the asynchronous api calls should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds] JCLOUDS-578: replaced request headers with swift object corresponding on... (#623)
@n3llino The `SwiftObject` has a [`setAllHeaders(MultiMapString, String headers)`](https://github.com/jclouds/jclouds/blob/master/apis/swift/src/main/java/org/jclouds/openstack/swift/domain/SwiftObject.java#L36) method to perform this operation. Can you please clarify your intent for this PR? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/623#issuecomment-66164008
