Re: [jclouds-site] Change links to ASF Confluence wiki (#148)
I merged this but when I try to publish it, I'm getting the error svn: E175002: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/repos/asf/!svn/me' Has anyone else ever run into that one? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/148#issuecomment-66126003
[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)
We are still looking into it. I expect @jdaggett will chime in as well. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/623#issuecomment-66158427
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
[jclouds-labs-aws] Use AutoService for creation of Service Loader Metadata (#67)
This PR updates all of the apis/providers to use AutoService and fixes several failed tests. You can merge this Pull Request by running: git pull https://github.com/jdaggett/jclouds-labs-aws autoservice Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-labs-aws/pull/67 -- Commit Summary -- * Fixed ambiguous methods in tests * Use AutoService for creation of Service Loader Metadata -- File Changes -- M aws-elb/pom.xml (5) M aws-elb/src/main/java/org/jclouds/aws/elb/AWSELBProviderMetadata.java (12) D aws-elb/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M aws-iam/pom.xml (5) M aws-iam/src/main/java/org/jclouds/aws/iam/AWSIAMProviderMetadata.java (15) D aws-iam/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M aws-rds/pom.xml (5) M aws-rds/src/main/java/org/jclouds/aws/rds/AWSRDSProviderMetadata.java (12) D aws-rds/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M elb/pom.xml (5) M elb/src/main/java/org/jclouds/elb/ELBApiMetadata.java (7) D elb/src/main/resources/META-INF/services/org.jclouds.apis.ApiMetadata (1) M glacier/pom.xml (5) M glacier/src/main/java/org/jclouds/glacier/GlacierApiMetadata.java (3) D glacier/src/main/resources/META-INF/services/org.jclouds.apis.ApiMetadata (1) M glacier/src/test/java/org/jclouds/glacier/GlacierClientLiveTest.java (2) M glacier/src/test/java/org/jclouds/glacier/GlacierClientMockTest.java (4) M iam/pom.xml (5) M iam/src/main/java/org/jclouds/iam/IAMApiMetadata.java (4) D iam/src/main/resources/META-INF/services/org.jclouds.apis.ApiMetadata (1) M rds/pom.xml (5) M rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java (7) D rds/src/main/resources/META-INF/services/org.jclouds.apis.ApiMetadata (1) -- Patch Links -- https://github.com/jclouds/jclouds-labs-aws/pull/67.patch https://github.com/jclouds/jclouds-labs-aws/pull/67.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-aws/pull/67
Jenkins build is back to normal : jclouds » jclouds-labs-aws #1644
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1644/changes
Re: [jclouds-labs-aws] Use AutoService for creation of Service Loader Metadata (#67)
[jclouds » jclouds-labs-aws #1644](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1644/) 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-aws/pull/67#issuecomment-66180717
[jclouds-labs] Use AutoService for creation of Service Loader Metadata (#115)
This PR updates the remaining APIs/Providers to use AutoService. You can merge this Pull Request by running: git pull https://github.com/rackerlabs/jclouds-labs autoservice Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-labs/pull/115 -- Commit Summary -- * Use AutoService for creation of Service Loader Metadata -- File Changes -- M cdmi/pom.xml (5) M cdmi/src/main/java/org/jclouds/snia/cdmi/v1/CDMIApiMetadata.java (3) D cdmi/src/main/resources/META-INF/services/org.jclouds.apis.ApiMetadata (1) M cloudsigma2-hnl/pom.xml (5) M cloudsigma2-hnl/src/main/java/org/jclouds/cloudsigma2/CloudSigma2HonoluluProviderMetadata.java (5) D cloudsigma2-hnl/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M cloudsigma2-lvs/pom.xml (5) M cloudsigma2-lvs/src/main/java/org/jclouds/cloudsigma2/CloudSigma2LasVegasProviderMetadata.java (5) D cloudsigma2-lvs/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M cloudsigma2-sjc/pom.xml (5) M cloudsigma2-sjc/src/main/java/org/jclouds/cloudsigma2/CloudSigma2SanJoseProviderMetadata.java (5) D cloudsigma2-sjc/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M cloudsigma2-wdc/pom.xml (5) M cloudsigma2-wdc/src/main/java/org/jclouds/cloudsigma2/CloudSigma2WashingtonProviderMetadata.java (9) D cloudsigma2-wdc/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M cloudsigma2-zrh/pom.xml (5) M cloudsigma2-zrh/src/main/java/org/jclouds/cloudsigma2/CloudSigma2ZurichProviderMetadata.java (9) D cloudsigma2-zrh/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M cloudsigma2/pom.xml (5) M cloudsigma2/src/main/java/org/jclouds/cloudsigma2/CloudSigma2ApiMetadata.java (4) D cloudsigma2/src/main/resources/META-INF/services/org.jclouds.apis.ApiMetadata (1) M digitalocean/pom.xml (5) M digitalocean/src/main/java/org/jclouds/digitalocean/DigitalOceanProviderMetadata.java (3) D digitalocean/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) M joyent-cloudapi/pom.xml (5) M joyent-cloudapi/src/main/java/org/jclouds/joyent/cloudapi/v6_5/JoyentCloudApiMetadata.java (5) M joyentcloud/pom.xml (5) M joyentcloud/src/main/java/org/jclouds/joyent/joyentcloud/JoyentCloudProviderMetadata.java (5) D joyentcloud/src/main/resources/META-INF/services/org.jclouds.providers.ProviderMetadata (1) -- Patch Links -- https://github.com/jclouds/jclouds-labs/pull/115.patch https://github.com/jclouds/jclouds-labs/pull/115.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/115
Re: [jclouds-labs] Use AutoService for creation of Service Loader Metadata (#115)
[jclouds » jclouds-labs #1960](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1960/) 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/pull/115#issuecomment-66186745
[jira] [Commented] (JCLOUDS-40) remove Async interface from all apis and providers
[ https://issues.apache.org/jira/browse/JCLOUDS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238497#comment-14238497 ] Daniel Broudy commented on JCLOUDS-40: -- Is this issue ready to be closed? remove Async interface from all apis and providers -- Key: JCLOUDS-40 URL: https://issues.apache.org/jira/browse/JCLOUDS-40 Project: jclouds Issue Type: Improvement Components: jclouds-blobstore, jclouds-core, jclouds-labs, jclouds-labs-aws, jclouds-labs-google, jclouds-labs-openstack Affects Versions: 1.7.0 Reporter: Adrian Cole Original Estimate: 72h Remaining Estimate: 72h In jclouds 1.6.0, we deprecated all async interfaces. Let's use this issue and subtasks to track removing it and all supporting code from 1.7.x (current master) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JCLOUDS-363) jclouds-labs-google 1.6.x compatibility
[ https://issues.apache.org/jira/browse/JCLOUDS-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238503#comment-14238503 ] Daniel Broudy commented on JCLOUDS-363: --- Is this still an open issue? jclouds-labs-google 1.6.x compatibility --- Key: JCLOUDS-363 URL: https://issues.apache.org/jira/browse/JCLOUDS-363 Project: jclouds Issue Type: Bug Components: jclouds-labs-google Reporter: Alex Heneveld we are starting to use GCE heavily as it is nice and fast (once you overcome setting up api key headaches) however the only branch currently present is master tied to jclouds v1.7.0 master. furthermore it uses features (eg SecurityGroupExtension) not compilation-compatible with jclouds 1.6.x. it would be very helpful to have a branch of jclouds-lab-google for 1.6.x which can be released in conjunction with 1.6.3. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds-site] Change links to ASF Confluence wiki (#148)
Hmmm nope. Have you shared the error with ASF Infra? Also, if you commit smaller units, say one directory at a time, can you commit? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/148#issuecomment-66199337
Re: [jclouds-labs-google] Updates to Address, Disk, Image, Operations + others (#106)
Closed #106. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/106#event-204513365
Re: [jclouds-labs-google] Updates to Address, Disk, Image, Operations + others (#106)
Committed to master as [70af047](https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-google.git;a=commit;h=70af04770fce742c05e918a680c29ad192b58442). Thanks @danbroudy! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/106#issuecomment-66200900
Re: [jclouds-labs-google] Added targetPool:AggregatedList, getHealth. Updated HttpHealthCheck (#108)
@@ -157,6 +158,22 @@
@Nullable
Operation removeHealthCheck(@PathParam(targetPool) String targetPool,
@PayloadParam(healthChecks) ListURI healthChecks);
+ /**
+* Gets the HealthStatus of an instance in a targetPool.
+*
+* @param targetPool the name of the target pool.
+* @param healthChecks the self-links of the health checks to be removed
from the targetPool.
+*
+* @return an Operation resource. To check on the status of an operation,
poll the Operations resource returned to
+* you, and look for the status field.
+*/
+ @Named(TargetPools:getHealth)
+ @POST
+ @Path(/{targetPool}/getHealth)
+ @Nullable
Usually, 404 exceptions are propagated as a `ResourceNotFoundException` unless
a fallback is configured to transform that into a `null` return value. Can this
method really return null?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/108/files#r21492545
Jenkins build is back to normal : jclouds » jclouds-labs-google #1848
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1848/changes
Re: [jclouds-labs-google] Added targetPool:AggregatedList, getHealth. Updated HttpHealthCheck (#108)
+* have a workaround for.
+*/
+ /**
+* @param requestPath Defaults to / when null.
+* @param port Defaults to 80 when null.
+* @param checkIntervalSec Defaults to 5 when null.
+* @param timeoutSec Defaults to 5 when null.
+* @param unhealthyThreshold Defaults to 2 when null.
+* @param healthyThreshold Defaults to 2 when null.
+*/
+ static HttpHealthCheckCreationOptions createWithDefaults(String host,
+ String requestPath, Integer port, Integer checkIntervalSec, Integer
timeoutSec, Integer unhealthyThreshold,
+ Integer healthyThreshold, String description) {
+ return create(host, requestPath != null ? requestPath : /, port !=
null ? port : 80,
+checkIntervalSec != null ? checkIntervalSec : 5, timeoutSec !=
null ? timeoutSec : 5,
+unhealthyThreshold != null ? unhealthyThreshold : 2,
healthyThreshold != null ? healthyThreshold : 2, description);
Would it make sense to move these default to constant values or to a constant
class?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/108/files#r21492752
Jenkins build became unstable: jclouds-labs-google » jclouds Google Cloud Storage provider #353
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-google/org.apache.jclouds.labs$google-cloud-storage/353/
Jenkins build became unstable: jclouds-labs-google #353
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-google/353/changes
Re: [jclouds-labs-google] Updated Network, MachineType, Region, Route, Snapshot, TargetInstance, a... (#109)
Bringing Apis up to 100% coverage! Nice! Committed to master as [d3205b1](https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-google.git;a=commit;h=d3205b1b2bb36322d06c9d5fe09779413f70cd1a). Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/109#issuecomment-66203630
[jira] [Commented] (JCLOUDS-40) remove Async interface from all apis and providers
[ https://issues.apache.org/jira/browse/JCLOUDS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238617#comment-14238617 ] Ignasi Barrera commented on JCLOUDS-40: --- Yes, I think so. Thanks for checking [~broudy]. remove Async interface from all apis and providers -- Key: JCLOUDS-40 URL: https://issues.apache.org/jira/browse/JCLOUDS-40 Project: jclouds Issue Type: Improvement Components: jclouds-blobstore, jclouds-core, jclouds-labs, jclouds-labs-aws, jclouds-labs-google, jclouds-labs-openstack Affects Versions: 1.7.0 Reporter: Adrian Cole Original Estimate: 72h Remaining Estimate: 72h In jclouds 1.6.0, we deprecated all async interfaces. Let's use this issue and subtasks to track removing it and all supporting code from 1.7.x (current master) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JCLOUDS-40) remove Async interface from all apis and providers
[ https://issues.apache.org/jira/browse/JCLOUDS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ignasi Barrera resolved JCLOUDS-40. --- Resolution: Fixed Fix Version/s: 1.9.0 2.0.0 remove Async interface from all apis and providers -- Key: JCLOUDS-40 URL: https://issues.apache.org/jira/browse/JCLOUDS-40 Project: jclouds Issue Type: Improvement Components: jclouds-blobstore, jclouds-core, jclouds-labs, jclouds-labs-aws, jclouds-labs-google, jclouds-labs-openstack Affects Versions: 1.7.0 Reporter: Adrian Cole Fix For: 2.0.0, 1.9.0 Original Estimate: 72h Remaining Estimate: 72h In jclouds 1.6.0, we deprecated all async interfaces. Let's use this issue and subtasks to track removing it and all supporting code from 1.7.x (current master) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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=14238626#comment-14238626 ] Ignasi Barrera commented on JCLOUDS-153: The I/O executor has been removed, but the user executor is still used in many providers to perform concurrent operations. Next steps should be to identify those providers and refactor them to accept an executor provided by the user. One possible approach to ease the migration would be to refactor the classes that use the user executor in a way similar to what I did with this class in the DigitalOcean provider, providing a factory that allows the class to be injected, but also requiring users to provide the executor to be used for concurrency: https://github.com/jclouds/jclouds-labs/blob/master/digitalocean/src/main/java/org/jclouds/digitalocean/strategy/ListSshKeys.java 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)
Jenkins build is back to stable : jclouds-labs-google » jclouds Google Cloud Storage provider #354
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-google/org.apache.jclouds.labs$google-cloud-storage/354/
Jenkins build is back to stable : jclouds-labs-google #354
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-google/354/changes
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())); Move the cleanup to a separate method that runs `@AfterMethod(alwaytRun = true)` to avoid leaking resources if the test fails. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174/files#r21495405
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
+ // + + assertNotNull(ipv4PortId); + + Port ipv4Port = portApi.get(ipv4PortId); + assertNotNull(ipv4Port); + assertEquals(ipv4Port.getId(), ipv4PortId); + assertEquals(ipv4Port.getName(), JClouds-Live-IPv4-Port); + + assertNotNull(portApi.update(ipv4PortId, Port.updateBuilder().name(Updated).build())); + Port updatedIpv4Port = portApi.get(ipv4PortId); + assertEquals(updatedIpv4Port.getName(), Updated); + + assertTrue(portApi.delete(ipv4PortId)); + assertTrue(subnetApi.delete(ipv4SubnetId)); + assertTrue(networkApi.delete(networkId)); Same comment about resource cleanup. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174/files#r21495442
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
+ + assertEquals(retrievedSubnet.getId(), subnet.getId()); + assertEquals(retrievedSubnet.getCidr(), 192.168.100.0/30); + assertTrue(retrievedSubnet.getDnsNameservers().isEmpty()); + assertEquals(retrievedSubnet.getAllocationPools().size(), 1); + assertEquals(retrievedSubnet.getHostRoutes().size(), 1); + assertNotNull(subnetApi.update(retrievedSubnet.getId(), Subnet.updateBuilder().name(jclouds-live-test-update).build())); + + retrievedSubnet = subnetApi.get(retrievedSubnet.getId()); + + assertEquals(retrievedSubnet.getId(), subnet.getId()); + assertEquals(retrievedSubnet.getName(), jclouds-live-test-update); + assertTrue(retrievedSubnet.getDnsNameservers().isEmpty()); + + assertTrue(subnetApi.delete(subnet.getId())); + assertTrue(networkApi.delete(networkId)); Same cleanup thing. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174/files#r21495523
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
+ +appender name=WIREFILE class=ch.qos.logback.core.FileAppender +filetarget/test-data/jclouds-wire.log/file + +encoder +Pattern%d %-5p [%c] [%thread] %m%n/Pattern +/encoder +/appender + +appender name=BLOBSTOREFILE class=ch.qos.logback.core.FileAppender +filetarget/test-data/jclouds-blobstore.log/file + +encoder +Pattern%d %-5p [%c] [%thread] %m%n/Pattern +/encoder +/appender Remove this logger, as it is not needed in this provider. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174/files#r21495502
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
+/logger + +logger name=jclouds.wire +level value=DEBUG / +appender-ref ref=WIREFILE / +/logger + +logger name=jclouds.headers +level value=DEBUG / +appender-ref ref=WIREFILE / +/logger + +logger name=jclouds.blobstore +level value=DEBUG / +appender-ref ref=BLOBSTOREFILE / +/logger Remove this logger. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174/files#r21495508
[jira] [Commented] (JCLOUDS-780) Remove vcloud and vcloud-director from jclouds
[ https://issues.apache.org/jira/browse/JCLOUDS-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238665#comment-14238665 ] Ignasi Barrera commented on JCLOUDS-780: PP to remove it from the jclouds CLI: https://github.com/jclouds/jclouds-cli/pull/24 Remove vcloud and vcloud-director from jclouds -- Key: JCLOUDS-780 URL: https://issues.apache.org/jira/browse/JCLOUDS-780 Project: jclouds Issue Type: Task Components: jclouds-core Reporter: Adrian Cole Assignee: Adrian Cole Fix For: 1.9.0 For over a month, we've discussed the fate of vcloud [1]. For example, we've already removed all vcloud providers as they no longer work with version 1.0 [2]. Also users who contact us either run custom forks [3], or also find features they need missing [4]. Eventhough the replacement code was supposed to be vcloud-director, it has never left labs, and has too much technical debt to continue attempting to support [5]. A couple stakeholders have offered they may be able to help [6], or encourage vmware to add a new api to cover modern products [7]. Good wishes aside, the facts remain that we have 2 aging apis, that are unsupportable in current form. Keeping vcloud and vcloud-director codebases limits the project's ability to move forward, so we must drop them. Users who wish to continue on either codebase will need to maintain their own fork. When it comes time to start vcloud products again, we'll want to start very small, with at least 2 champions, and some means to keep tests passing. If we don't, we'll surely repeat history again. [1] http://markmail.org/thread/4p22wkbrd4mncmss [2] https://issues.apache.org/jira/browse/JCLOUDS-743 [3] http://markmail.org/message/gxcl37zq2pnn22sf [4] http://markmail.org/thread/ligd5sbkmvoo7vdi [5] http://markmail.org/thread/s5i6i4nr6f5k5wew [6] http://markmail.org/thread/5fav2wa6ylxbqpdy [7] http://markmail.org/thread/q4otznoqoygrz64b -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: jclouds-labs-aws » Apache jclouds :: AWS :: Glacier API #295
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/295/ -- Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds [INFO] [INFO] [INFO] Building Apache jclouds :: AWS :: Glacier API 2.0.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ glacier --- [INFO] [INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ glacier --- [INFO] [INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ glacier --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ glacier --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ glacier --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/main/clojure [INFO] Copying 1 resource [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ glacier --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 66 source files to https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/target/classes [WARNING] bootstrap class path not set in conjunction with -source 1.6 [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/main/java/org/jclouds/glacier/blobstore/strategy/internal/BaseSlicingStrategy.java:[62,25] redundant cast to long [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/main/java/org/jclouds/glacier/binders/BindArchiveSizeToHeaders.java: Some input files use unchecked or unsafe operations. [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/main/java/org/jclouds/glacier/binders/BindArchiveSizeToHeaders.java: Recompile with -Xlint:unchecked for details. [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ glacier --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/test/clojure [INFO] Copying 11 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ glacier --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 14 source files to https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/target/test-classes [INFO] - [WARNING] COMPILATION WARNING : [INFO] - [WARNING] bootstrap class path not set in conjunction with -source 1.6 [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/test/java/org/jclouds/glacier/blobstore/strategy/internal/MultipartUploadStrategyMockTest.java: Some input files use or override a deprecated API. [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/test/java/org/jclouds/glacier/blobstore/strategy/internal/MultipartUploadStrategyMockTest.java: Recompile with -Xlint:deprecation for details. [INFO] 3 warnings [INFO] - [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/test/java/org/jclouds/glacier/GlacierClientMockTest.java:[354,7] reference to assertThat is ambiguous, both method TassertThat(java.lang.IterableT) in org.assertj.core.api.Assertions and method TassertThat(T) in org.assertj.core.api.Assertions match [ERROR] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/test/java/org/jclouds/glacier/GlacierClientMockTest.java:[355,7] reference to assertThat is ambiguous, both method TassertThat(java.lang.IterableT) in org.assertj.core.api.Assertions and method TassertThat(T) in org.assertj.core.api.Assertions match [ERROR] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/org.apache.jclouds.labs$glacier/ws/src/test/java/org/jclouds/glacier/GlacierClientLiveTest.java:[93,10] reference to assertThat is ambiguous, both method TassertThat(java.lang.IterableT) in
[jclouds-cli] JCLOUDS-780: Remove vcloud feature (#24)
The feature was removed from jclouds-karaf but was still present in the CLI, making the build fail. You can merge this Pull Request by running: git pull https://github.com/nacx/jclouds-cli 780-remove-vcloud Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds-cli/pull/24 -- Commit Summary -- * Remove vcloud feature -- File Changes -- M assembly/pom.xml (1) -- Patch Links -- https://github.com/jclouds/jclouds-cli/pull/24.patch https://github.com/jclouds/jclouds-cli/pull/24.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-cli/pull/24
Build failed in Jenkins: jclouds-labs-aws #295
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/295/ -- [...truncated 4000 lines...] [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/options/ListSecurityGroupsOptions.java:50: warning - Tag @see: can't find getMarker() in org.jclouds.rds.options.ListSecurityGroupsOptions [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/options/ListSubnetGroupsOptions.java:50: warning - Tag @see: can't find getMarker() in org.jclouds.rds.options.ListSubnetGroupsOptions [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/IPRange.java:45: warning - Tag @see: can't find getCidrIp() in org.jclouds.rds.domain.IPRange [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/SecurityGroup.java:128: warning - Tag @see: reference not found: SecurityGroupGroup#getVpcId() [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/SubnetGroup.java:85: warning - Tag @see: can't find getSubnets() in org.jclouds.rds.domain.Instance [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/SubnetGroup.java:93: warning - Tag @see: can't find getSubnets() in org.jclouds.rds.domain.Instance [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [INFO] Building jar: https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT-javadoc.jar [INFO] [INFO] --- maven-source-plugin:2.2:jar-no-fork (attach-sources) @ rds --- [INFO] Building jar: https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-surefire-plugin:2.17:test (integration) @ rds --- [JENKINS] Recording test results[INFO] [INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ rds --- [INFO] Checking compile classpath [INFO] Checking runtime classpath [INFO] Checking test classpath [INFO] [INFO] --- maven-checkstyle-plugin:2.13:check (default) @ rds --- [INFO] [INFO] [INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ rds --- [INFO] [INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ rds --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ rds --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ rds --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/clojure [INFO] Copying 1 resource [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ rds --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ rds --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/test/clojure [INFO] Copying 16 resources [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ rds --- [INFO] Nothing to compile - all classes are up to date [WARNING] Failed to getClass for org.gaul.modernizer_maven_plugin.ModernizerMojo [INFO] [INFO] --- modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ rds --- [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ rds --- [INFO] Installing https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT.jar to https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/.repository/org/apache/jclouds/labs/rds/2.0.0-SNAPSHOT/rds-2.0.0-SNAPSHOT.jar [INFO] Installing https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/pom.xml to https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/.repository/org/apache/jclouds/labs/rds/2.0.0-SNAPSHOT/rds-2.0.0-SNAPSHOT.pom [INFO] Installing https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT-tests.jar to
Build failed in Jenkins: jclouds-labs-aws #295
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/295/ -- [...truncated 4001 lines...] [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/options/ListSubnetGroupsOptions.java:50: warning - Tag @see: can't find getMarker() in org.jclouds.rds.options.ListSubnetGroupsOptions [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/IPRange.java:45: warning - Tag @see: can't find getCidrIp() in org.jclouds.rds.domain.IPRange [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/SecurityGroup.java:128: warning - Tag @see: reference not found: SecurityGroupGroup#getVpcId() [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/SubnetGroup.java:85: warning - Tag @see: can't find getSubnets() in org.jclouds.rds.domain.Instance [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/domain/SubnetGroup.java:93: warning - Tag @see: can't find getSubnets() in org.jclouds.rds.domain.Instance [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [WARNING] https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/java/org/jclouds/rds/RDSApiMetadata.java:34: warning - Tag @link: reference not found: ApiMetadata [INFO] Building jar: https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT-javadoc.jar [INFO] [INFO] --- maven-source-plugin:2.2:jar-no-fork (attach-sources) @ rds --- [INFO] Building jar: https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-surefire-plugin:2.17:test (integration) @ rds --- [JENKINS] Recording test results[INFO] [INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ rds --- [INFO] Checking compile classpath [INFO] Checking runtime classpath [INFO] Checking test classpath [INFO] [INFO] --- maven-checkstyle-plugin:2.13:check (default) @ rds --- [INFO] [INFO] [INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ rds --- [INFO] [INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ rds --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ rds --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ rds --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/main/clojure [INFO] Copying 1 resource [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ rds --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ rds --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/src/test/clojure [INFO] Copying 16 resources [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ rds --- [INFO] Nothing to compile - all classes are up to date [WARNING] Failed to getClass for org.gaul.modernizer_maven_plugin.ModernizerMojo [INFO] [INFO] --- modernizer-maven-plugin:1.1.0:modernizer (modernizer) @ rds --- [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ rds --- [INFO] Installing https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT.jar to https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/.repository/org/apache/jclouds/labs/rds/2.0.0-SNAPSHOT/rds-2.0.0-SNAPSHOT.jar [INFO] Installing https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/pom.xml to https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/.repository/org/apache/jclouds/labs/rds/2.0.0-SNAPSHOT/rds-2.0.0-SNAPSHOT.pom [INFO] Installing https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT-tests.jar to https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/.repository/org/apache/jclouds/labs/rds/2.0.0-SNAPSHOT/rds-2.0.0-SNAPSHOT-tests.jar [INFO] Installing https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ws/rds/target/rds-2.0.0-SNAPSHOT-javadoc.jar to
Re: [jclouds] Upgrade assertj-core to 1.7.0 and assertj-guava to 1.3.0 (a2a410d)
This change seems to have broken the jclouds-labs-aws build: https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws/ @jdaggett Can you fix it please? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/commit/a2a410d05a61f02ed26f0df921795b2dfb109b3b#commitcomment-8885193
[jira] [Closed] (JCLOUDS-363) jclouds-labs-google 1.6.x compatibility
[ https://issues.apache.org/jira/browse/JCLOUDS-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Heneveld closed JCLOUDS-363. - Resolution: Won't Fix No longer needed. Happily running with recent versions. :) jclouds-labs-google 1.6.x compatibility --- Key: JCLOUDS-363 URL: https://issues.apache.org/jira/browse/JCLOUDS-363 Project: jclouds Issue Type: Bug Components: jclouds-labs-google Reporter: Alex Heneveld we are starting to use GCE heavily as it is nice and fast (once you overcome setting up api key headaches) however the only branch currently present is master tied to jclouds v1.7.0 master. furthermore it uses features (eg SecurityGroupExtension) not compilation-compatible with jclouds 1.6.x. it would be very helpful to have a branch of jclouds-lab-google for 1.6.x which can be released in conjunction with 1.6.3. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds] Upgrade assertj-core to 1.7.0 and assertj-guava to 1.3.0 (a2a410d)
I've just seen the fix is already part of another PR: https://github.com/jdaggett/jclouds-labs-aws/commit/29cf3da7ea8186804db2bfd5b5a9c18e3dd83a3c Could you merge that commit alone to get the build fixed? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/commit/a2a410d05a61f02ed26f0df921795b2dfb109b3b#commitcomment-8885245
[jira] [Commented] (JCLOUDS-780) Remove vcloud and vcloud-director from jclouds
[ https://issues.apache.org/jira/browse/JCLOUDS-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238690#comment-14238690 ] ASF subversion and git services commented on JCLOUDS-780: - Commit e2e0ea7f01c9f4407e6216d4731f70fe576fbc3a in jclouds-cli's branch refs/heads/master from [~nacx] [ https://git-wip-us.apache.org/repos/asf?p=jclouds-cli.git;h=e2e0ea7 ] JCLOUDS-780: Remove vcloud feature Remove vcloud and vcloud-director from jclouds -- Key: JCLOUDS-780 URL: https://issues.apache.org/jira/browse/JCLOUDS-780 Project: jclouds Issue Type: Task Components: jclouds-core Reporter: Adrian Cole Assignee: Adrian Cole Fix For: 1.9.0 For over a month, we've discussed the fate of vcloud [1]. For example, we've already removed all vcloud providers as they no longer work with version 1.0 [2]. Also users who contact us either run custom forks [3], or also find features they need missing [4]. Eventhough the replacement code was supposed to be vcloud-director, it has never left labs, and has too much technical debt to continue attempting to support [5]. A couple stakeholders have offered they may be able to help [6], or encourage vmware to add a new api to cover modern products [7]. Good wishes aside, the facts remain that we have 2 aging apis, that are unsupportable in current form. Keeping vcloud and vcloud-director codebases limits the project's ability to move forward, so we must drop them. Users who wish to continue on either codebase will need to maintain their own fork. When it comes time to start vcloud products again, we'll want to start very small, with at least 2 champions, and some means to keep tests passing. If we don't, we'll surely repeat history again. [1] http://markmail.org/thread/4p22wkbrd4mncmss [2] https://issues.apache.org/jira/browse/JCLOUDS-743 [3] http://markmail.org/message/gxcl37zq2pnn22sf [4] http://markmail.org/thread/ligd5sbkmvoo7vdi [5] http://markmail.org/thread/s5i6i4nr6f5k5wew [6] http://markmail.org/thread/5fav2wa6ylxbqpdy [7] http://markmail.org/thread/q4otznoqoygrz64b -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jclouds-cli] JCLOUDS-780: Remove vcloud feature (#24)
Pushed to master as [e2e0ea7](https://git-wip-us.apache.org/repos/asf?p=jclouds-cli.git;a=commit;h=e2e0ea7f01c9f4407e6216d4731f70fe576fbc3a). --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-cli/pull/24#issuecomment-66210209
Re: [jclouds-cli] JCLOUDS-780: Remove vcloud feature (#24)
Closed #24. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-cli/pull/24#event-204549506
Jenkins build is back to normal : jclouds-cli #236
See https://jclouds.ci.cloudbees.com/job/jclouds-cli/236/changes
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
The suggested cleanup should be applied to the US provider as well. Expand PR? Some of this (resource cleanup) will be useful in the Neutron live tests also. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174#issuecomment-66217496
Re: [jclouds-labs-openstack] Add support for Rackspace Cloud Networks UK (#174)
The cleanup is pretty straightforward. If it makes sense in US and Neutron I'd expand this PR with a second commit addressing that. Let's make sure things get fixed when we spot them. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/174#issuecomment-66240821
