Thanks for the updates @cirix! I had a couple of comments. Hope it's reasonable.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/135#issuecomment-59416677
On Oct 14, 2014, at 8:57 AM, Jay Pipes jaypi...@gmail.com wrote:
I personally think proposing patches to an openstack-api repository is the
most effective way to make those proposals. Etherpads and wiki pages are fine
for dumping content, but IMO, we don't need to dump content -- we already
+1
Merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/65#issuecomment-58958211
[
https://issues.apache.org/jira/browse/JCLOUDS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews closed JCLOUDS-592.
-
Resolution: Fixed
GenerateTempURL example logs warning when using RegionScopedBlobStoreContext
Hey Adrian,
Since your return there has been a lot of change (and that’s not a bad thing).
I was at JavaOne when the pull request avalanche started and, frankly, I
haven’t really caught up with everything that’s changed. The gist I’m getting
from the PRs is paying down tech debt. So far, I’ve
https://wiki.openstack.org/wiki/API_Working_Group
This is the start of the API Working Group (API WG).
To avoid bike shedding over the name of the working group, I decided to title
the wiki page API Working Group. Simple, to the point, and avoids loaded terms
like standards, best practices,
Thanks @smashwilson!
I don't want to derail the efforts on this PR but if you guys think what Ash
has in his gist is a simple (and it does look pretty simple) alternative that
meets everyone's requirements then give it some consideration.
---
Reply to this email directly or view it on GitHub:
+1
I'm okay with the groupId change.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/158#issuecomment-58442151
:tada:
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/553#issuecomment-58029599
+1
Sorry about the delayed review. Still getting unburied after JavaOne.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/132#issuecomment-58066324
Thanks for the sharp eyes @yaronr!
I think it's more than slightly confusing considering there are also examples
on this page that use `client` to refer to a `SshClient`.
Instead of renaming the `ComputeService` var to `client`, would you be willing
to rename all of the other `ComputeService`
+dependency
+ groupIdorg.apache.jclouds/groupId
+ artifactIdjclouds-all/artifactId
+ version1.8.0/version
+/dependency
+dependency
+ groupIdorg.apache.jclouds.driver/groupId
+ artifactIdjclouds-log4j/artifactId
+ version1.8.0/version
+/dependency
+dependency
+
Backported to 1.8.x
https://github.com/jclouds/jclouds-labs-openstack/commit/06348f686f629d1f45a610ecc795c57686d883a9
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-58099387
/10LkAD8Wk5Kcj38nQghTW-bQdCOXaxZad5W5Chu6HUCA/edit
On Oct 3, 2014, at 5:52 PM, Adrian Cole adrian.f.c...@gmail.com wrote:
Sounds fair. Thanks for standing up for regular releases :)
-A
On Fri, Oct 3, 2014 at 3:49 PM, Everett Toews
everett.to...@rackspace.com wrote:
So it’s a pretty normal
Any objections to using wildcards for brevity’s sake where it makes sense?
e.g.
openstack-*
elastichosts-*
rackspace-*
hpcloud-*
cloudsigma2-*
Probably doesn’t make sense for aws providers/apis as stewardship of them isn’t
uniform.
Everett
On Oct 6, 2014, at 2:03 PM, Andrew Gaul
hoping this isn’t too much to ask for and we can just ship some code.
Thanks,
Everett
On Oct 2, 2014, at 11:12 AM, Everett Toews everett.to...@rackspace.com wrote:
Let's schedule the release of 1.8.1.
All code into 1.8.x by Monday, Oct. 6 EOD
Begin release on Tuesday, Oct. 7
Can someone
Let's schedule the release of 1.8.1.
All code into 1.8.x by Monday, Oct. 6 EOD
Begin release on Tuesday, Oct. 7
Can someone volunteer to do the actual release steps?
I'll be catching up with work stuff all next week after being on the road for a
few weeks but I can do it if necessary.
Thanks,
[
https://issues.apache.org/jira/browse/JCLOUDS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14149848#comment-14149848
]
Everett Toews commented on JCLOUDS-172:
---
I am not opposed to graduating a @Beta
On Sep 24, 2014, at 9:42 AM, Dean Troyer dtro...@gmail.com wrote:
I'll bring an API consumer's perspective.
+1
I’d bring an API consumer’s perspective as well.
Looks like there’s lots of support for an API WG. What’s the next step?
Form a WG under the User Committee [1] or is there
On Sep 24, 2014, at 12:02 PM, Tim Bell tim.b...@cern.ch wrote:
Seems like there is some overlap with the end user (i.e. consumer) working
group at https://wiki.openstack.org/wiki/End_User_Working_Group
Sounds like it would be worth discussing with them on how to focus on these
needs. The
+1!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/126#issuecomment-56675797
The way the versioning was handled was the first thing I looked at and was
comfortable with the approach. But thinking about it a bit more I could use an
example.
@fbrouille Can you provide us with an example here in the PR comments that
shows how a user would write some code against v1 LBaaS
[
https://issues.apache.org/jira/browse/JCLOUDS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews updated JCLOUDS-611:
--
Assignee: Frédéric Brouillé
Neutron LBaaS extension request
Great to have you on board Frédéric!
Definitely read the stuff that Ignasi pointed out and, because you’re working
in the Neutron API, I want to point out a couple of additional things.
1. New Builders
Zack Shoylev did a refactoring and we’re trying something new in Neutron. In
general, your
account in JIRA. So you can find my name now.
best,
Frédéric
-Everett Toews everett.to...@rackspace.com a écrit : -
A : dev@jclouds.apache.org dev@jclouds.apache.org
De : Everett Toews everett.to...@rackspace.com
Date : 19/09/2014 17:46
Objet : Re: Contribute to jclouds to support
Okay. What needs to be revisited?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/448#issuecomment-56131484
[
https://issues.apache.org/jira/browse/JCLOUDS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137901#comment-14137901
]
Everett Toews commented on JCLOUDS-172:
---
Hi Alex,
GCE seems like a stable
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/500#issuecomment-55040074
+* The fourth argument (args[3]) must be your password
+*
+* For this example your endpoint must be the *admin endpoint* of your
Identity service
+* (e.g. http://111.222.333.444:35357/v2.0/;)
+*/
+ public static void main(String[] args) throws IOException {
+
+ if (tenantAdminApiExtension.isPresent()) {
+ System.out.format(TenantAdminApi is present%n);
+
+ TenantAdminApi tenantAdminApi = tenantAdminApiExtension.get();
+ CreateTenantOptions tenantOptions = CreateTenantOptions.Builder
+ .description(My
@@ -0,0 +1,64 @@
+# OpenStack Examples
+Example code that uses jclouds to perform common tasks on an OpenStack
Cloud. The class names are self explanatory and the code is well commented
for you to follow along.
Sure.
---
Reply to this email directly or view it on GitHub:
Merge and publish!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#issuecomment-54484345
My preference too is to not use any Java 7 specific features in the examples
until we've released 2.0.0. The examples really should be consistent with the
language level we support.
---
Reply to this email directly or view it on GitHub:
Closed #53.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/53#event-161258946
Just to be clear, after this merges, any changes to these classes that needs to
be backported to 1.8.x from here on out will require removing these changes
while backporting. Correct?
---
Reply to this email directly or view it on GitHub:
@@ -44,7 +42,12 @@ public PaginationOptions queryParameters(MultimapString,
String queryParams) {
/**
* Only return objects changed since this time.
+*
+* @deprecated The {@code changes-since} query does not apply to all
OpenStack APIs. Please refer to the OpenStack
+
Thanks @nacx! Fixed and merged.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/62#issuecomment-54543435
On Sep 3, 2014, at 3:36 AM, Ignasi Barrera n...@apache.org wrote:
I also like the syntax and think that's a pattern we could use in more
places.
Regarding the naming I'm +1 to change the *Options to *Request or something
else to avoid confusion with the already xisting Options pattern.
The
Here’s how to report a bug.
http://jclouds.apache.org/reference/report-a-bug/
Thanks,
Everett
On Sep 4, 2014, at 4:14 PM, Ignasi Barrera
n...@apache.orgmailto:n...@apache.org wrote:
Using the latest version should work. Could you please file an issue in our
JIRA [1] with the relevant code
@@ -19,7 +19,7 @@
import com.google.common.base.Optional;
import com.google.common.collect.FluentIterable;
-import org.jclouds.openstack.nova.v2_0.domain.regionscoped.AvailabilityZone;
+import org.jclouds.openstack.nova.v2_0.domain.zonescoped.AvailabilityZone;
This should still use
@@ -24,7 +24,7 @@
import org.jclouds.Fallbacks.EmptyFluentIterableOnNotFoundOr404;
import org.jclouds.openstack.keystone.v2_0.filters.AuthenticateRequest;
-import org.jclouds.openstack.nova.v2_0.domain.regionscoped.AvailabilityZone;
+import
+1
After the few comments have been addressed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/503#issuecomment-54301540
+1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/505#issuecomment-54348575
Reopened #124.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/124#event-160761654
@@ -0,0 +1,119 @@
+---
+author: Zack Shoylev
+comments: true
+date: 2014-09-03 23:00:00+00:00
+layout: post
+slug: better-builders-with-jclouds
+title: Better Builders with jclouds!
+---
+
+# Better Builders with jclouds
No need to repeat the title here.
---
Reply to this email
@@ -0,0 +1,119 @@
+---
+author: Zack Shoylev
+comments: true
+date: 2014-09-03 23:00:00+00:00
+layout: post
+slug: better-builders-with-jclouds
+title: Better Builders with jclouds!
+---
+
+# Better Builders with jclouds
+
+If you are a new
Can you also please add the testing info to [Testing
OpenStack](https://wiki.apache.org/jclouds/Testing%20OpenStack)?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54375377
Alright. I figured an early 2.0.0 release was a bit of a long shot. Good
discussion though. Let’s continue it on the “jclouds roadmap” thread.
Thanks,
Everett
On Sep 2, 2014, at 3:54 PM, Andrew Phillips aphill...@qrmedia.com wrote:
TL;DR: I'm not against marketing releases as such, but I
On Sep 2, 2014, at 5:50 PM, Andrew Gaul g...@apache.org wrote:
I would like to move all tasks to a
indefinite version and only move a task to a definite version when we
have an owner and a corresponding JIRA issue. Thoughts?
+1
I’ve never understood why we set the Fix Version when an issue
We have a situation uncovered by this issue [1] where the JSON response has
different value types for String keys in a Map.
For example,
{
images: [
{
id: cd9d57a9-0978-45f3-9cbc-edb99347be6b,
metadata: {
block_device_mapping: [
{
snapshot_id:
[
https://issues.apache.org/jira/browse/JCLOUDS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118263#comment-14118263
]
Everett Toews commented on JCLOUDS-687:
---
Before starting coding on this, we need
[
https://issues.apache.org/jira/browse/JCLOUDS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118263#comment-14118263
]
Everett Toews edited comment on JCLOUDS-687 at 9/2/14 3:23 PM
Everett Toews created JCLOUDS-699:
-
Summary: Properly deprecate zonescoped domain objects
Key: JCLOUDS-699
URL: https://issues.apache.org/jira/browse/JCLOUDS-699
Project: jclouds
Issue Type
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-examples openstack-examples
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-examples/pull/62
-- Commit Summary --
* The start of examples for OpenStack
Need to update pom.xml to include `moduleopenstack-heat/module`
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54223732
Can you give us the mvn command you used to do the live testing?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/138#issuecomment-54227227
On Aug 30, 2014, at 2:34 PM, Andrew Gaul g...@apache.org wrote:
Why should we release 2.0 out of step with the agreed-upon major release
cadence? If we cannot follow our own policy for the first release after
agreeing upon a policy, what confidence does that give our users in
subsequent
On Aug 28, 2014, at 3:08 AM, Flavio Percoco fla...@redhat.com wrote:
Unfortunately, as Nataliia mentioned, we can't just get rid of it in
v1.1 because that implies a major change in the API, which would require
a major release. What we can do, though, is start working on a spec for
the V2 of
@@ -44,7 +42,11 @@ public PaginationOptions queryParameters(MultimapString,
String queryParams) {
/**
* Only return objects changed since this time.
+*
+* @deprecated The {@code changes-since} query does not apply to all
OpenStack APIs.
SGTM
---
Reply to this email
+ @POST
+ @SelectJson(floatingip)
+ FloatingIP create(@WrapWith(floatingip) FloatingIP.CreateOptions
floatingIP);
+
+ /**
+* Update a floatingip
+*
+* @param id the id of the floatingip to update
+* @param floatingIP Contains only the attributes to update
+*
Hi All,
At our current release cadence we would reach 2.0.0 until Feb. 2015. I’d like
to propose that we release 2.0.0 in mid-Sept. for a number of reasons.
1. A big boost in interest for jclouds at JavaOne
I’ll be giving an “Introduction to Apache jclouds” session at JavaOne on Sept.
30. I
Closed #459.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/459#event-158461684
I think OpenStack Upstream Training [1] is pretty much exactly what you’re
describing. Make sure to click on the More Details link there.
There will be one at the Paris Summit. [2]
Cheers,
Everett
[1] https://wiki.openstack.org/wiki/OpenStack_Upstream_Training
[2]
On Aug 23, 2014, at 4:08 PM, Andrew Gaul g...@apache.org wrote:
You explicitly used semvar-style version numbers. Is this an implicit
part of your proposal?
Nope.
We already agreed to a six-month major release
cadence and already do not break compatibility between minor (micro)
minor point upgrades.
This is the common ground we agree on and I thought we could move forward on
these 2 points alone for the sake of progress. Do you have any arguments for or
against the 2 points below?
On Tue, Aug 19, 2014 at 10:36:58PM +, Everett Toews wrote:
Let’s see what we can
+* This API is an extension that may or may not be present in your
OpenStack cloud. Use the Optional return type
+* to determine if it is present.
+*/
+ @Delegate
+ OptionalSecurityGroupApi getSecurityGroupApi(@EndpointParam(parser =
RegionToEndpoint.class) String region);
Done.
On Aug 19, 2014, at 6:15 PM, Chris Custine chris.cust...@gmail.com wrote:
Could one of you guys with admin access to the wiki add me so that I can
edit? User name is ChrisCustine.
Thanks,
Chris
--
Chris Custine
. e.g. users
upgrading from an earlier 3.x should be able to use a later
3.x release without source modification.” (pasted from Gaul’s previous email
below).
Can everyone agree on those two points?
Regards,
Everett
On Jul 11, 2014, at 11:45 PM, Everett Toews everett.to...@rackspace.com wrote
I'm not crazy about this.
If the code is deprecated, it will eventually be deleted. No need to shuffle it
around before deleting it.
If the code isn't deprecated, we support it. Putting it into a legacy dir
just confuses the issue, especially if you were to change the Maven groupId
too. No
If I don't hear anything else on this by the end of the week, I'll merge it.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/459#issuecomment-52182466
@@ -0,0 +1,3 @@
+# jclouds Development Tools
+
+This is a collection of tools that aid in the development of jclouds itself.
Changed dir name to scripts. I'd prefer the scripts not to get mixed in with
the tools that we might actually release. Whereas the scripts won't be released.
---
Thanks for getting this started @andrewgaul
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/123#issuecomment-51728508
[
https://issues.apache.org/jira/browse/JCLOUDS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090757#comment-14090757
]
Everett Toews commented on JCLOUDS-655:
---
More context will help us find a solution
[
https://issues.apache.org/jira/browse/JCLOUDS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090773#comment-14090773
]
Everett Toews commented on JCLOUDS-655:
---
This is odd. How did the metadata field
[
https://issues.apache.org/jira/browse/JCLOUDS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091314#comment-14091314
]
Everett Toews commented on JCLOUDS-655:
---
Nova bug filed:
https
Public bug reported:
1. Fire up a DevStack instance from the stable/havana, stable/icehouse, or
master branches.
2. Go into Horizon
3. Launch an instance
1. Instance Boot Source: Boot from image (creates a new volume)
2. Image Name: cirros
3. Device size (GB): 1
1. For the instance that
Hi @lcheng61. This really isn't the best or most visible place for questions
like these. If you have any more follow up questions, I invite you to join our
[community](http://jclouds.apache.org/community/) and send an email to the user
mailing list. Thanks.
---
Reply to this email directly or
A closed pull request is not the place for this conversation. Please move it to
the user mailing list. You can subscribe by going to the
[community](http://jclouds.apache.org/community/) page.
---
Reply to this email directly or view it on GitHub:
[
https://issues.apache.org/jira/browse/JCLOUDS-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14089934#comment-14089934
]
Everett Toews commented on JCLOUDS-653:
---
In this particular case, I think it's
Squashed, merged, and published! If anyone else has something to add, just go
ahead and open another PR.
Thanks so much for the team effort on the release notes. I think starting a PR
for the release notes early on in the cycle works well as we can add things as
they happen rather then trying
/**
* Provides access to Flavor extra specs features.
+* @deprecated Please use {@link #getFlavorExtrasApi(String region)} as
this method will be removed
Should be getFlavorExtraSpecsApi
---
Reply to this email directly or view it on GitHub:
/**
* Provides synchronous access to Snapshot features.
+* @deprecated Please use {@link #getSnapshotApi()} as this method will
be removed
Should be getSnapshotApi(String region)
---
Reply to this email directly or view it on GitHub:
This refactoring should include NovaEC2Api for completeness. I have no idea why
that module exists...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/463#issuecomment-51390286
+ InstanceApi getInstanceApi(@EndpointParam(parser =
RegionToEndpoint.class) @Nullable String region);
+
+ /**
+* Provides access to User features.
+*/
+ @Delegate
+ @Path(/instances/{instanceId})
+ UserApi getUserApiForInstance(@EndpointParam(parser =
+*/
+ @Delegate
+ FlavorApi getFlavorApi(@EndpointParam(parser = RegionToEndpoint.class)
@Nullable String region);
+
+ /**
+* Provides access to Instance features.
+*/
+ @Delegate
+ InstanceApi getInstanceApi(@EndpointParam(parser =
RegionToEndpoint.class)
Refactor CloudDNSApi getRecordApiForDomain and getReverseDNSApiForService to
drop ForBlah
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/463#issuecomment-51390839
+ @Region
+ SetString getConfiguredRegions();
+
+ /**
+* Provides access to Load Balancer features.
+*/
+ @Delegate
+ LoadBalancerApi getLoadBalancerApi(
+ @EndpointParam(parser = RegionToEndpoint.class) @Nullable String
region);
+
+ /**
+* Provides
Please be sure to remove the ForRegion**AndBlah** from the method sigs.
Basically remove For and everything after it.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/123#issuecomment-51391815
@nacx @demobox I've included posts in quicknews now in [this
commit](https://git-wip-us.apache.org/repos/asf/jclouds-site/repo?p=jclouds-site.git;a=commit;h=fd21d0484faa0617355976427b6a7805d432d6c1)
I've also added quicknews for AP's blog post in [this
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.0
released](TODO). You can read the details of the specific JIRA issues
addressed in this release at the [JIRA Release
I'll get started on the Javadoc...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/114#issuecomment-51229334
Oops. Have to wait until 1.8.0 syncs to Maven Central first.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/114#issuecomment-51232481
[
https://issues.apache.org/jira/browse/JCLOUDS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086531#comment-14086531
]
Everett Toews commented on JCLOUDS-651:
---
[Copy
Object|http://docs.rackspace.com
On Aug 4, 2014, at 7:04 PM, Andrew Gaul
g...@apache.orgmailto:g...@apache.org wrote:
Further, if we are going to change the
default, can we align with other language bindings like fog?
+1
fog deprecated default region support over 6 months ago. They’re going to be
removing it completely now.
Javadoc [1] is done and published, and links are included the release notes PR
[2].
Everett
[1] http://jclouds.apache.org/reference/javadoc/1.8.x/
[2] https://github.com/jclouds/jclouds-site/pull/114
On Aug 5, 2014, at 4:41 PM, Andrew Phillips aphill...@qrmedia.com wrote:
Some FYI items
+date: 2014-08-02 14:00:00+00:00
+layout: post
+slug: 1-release-2-committers
+title: 1 release, 2 committers...a busy week for jclouds!
+image: /img/posts/chris-and-andrea.jpg
+---
+
+img class=img-right src=/img/posts/chris-and-andrea.png/There's a lot
going on this week for the jclouds
+1
Once comments are addressed.
Thanks @demobox!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/116#issuecomment-51082662
I'm all for enabling the build failure. I don't think someone looking at the
Checkstyle warnings and saying fix x, y, and z warning is a good use of review
time. Checkstyle should simply fail the build. Then we know both locally and in
the build that the code is clean w.r.t Checkstyle.
For
+1 after comments addressed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/462#issuecomment-51085775
+1
rackspace-cloudidentity is definitely the proper home for this (legacy) code.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/461#issuecomment-51119001
301 - 400 of 1710 matches
Mail list logo
