Closed #104.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/104#event-123950499
[
https://issues.apache.org/jira/browse/JCLOUDS-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett resolved JCLOUDS-545.
Resolution: Fixed
> SwiftApi and related Apis improveme
Merged to 1.7.x b6c21f8
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/105#issuecomment-43909877
Closed #105.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/105#event-123887219
Closed #103.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/103#event-123886964
Merged to master 3fc8973
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/103#issuecomment-43909807
> private static Payload payload(long bytes, String contentType) {
> - Payload payload = Payloads.newByteArrayPayload(NO_CONTENT);
> + Payload payload = Payloads.newByteSourcePayload(ByteSource.empty());
Yes, just cleanup. This is a much cleaner way to express an empty `ByteSource`.
Backport PR #103 into the 1.7.x branch
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-labs-openstack backport-545-17x
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-labs-openstack/pull/105
-- Commit Summa
@demobox Thanks! I just successfully built Karaf and the dependency was updated
to correctly match this change.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/64#issuecomment-43794379
@everett-toews Thanks for reviewing! Can I please get some feedback on:
`SwiftObject head(@PathParam("objectName") String objectName);`
versus:
`SwiftObject getWithoutBody(@PathParam("objectName") String objectName);`
---
Reply to this email directly or view it on GitHub:
https://github.com/jclo
This PR addresses the following:
- Correct URL decoding for Swift Object Names
- Use ByteSource where possible
- Adds test case for Rackspace Cloud Files CDN
https://issues.apache.org/jira/browse/JCLOUDS-562
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclo
Closed #365.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/365#event-123125254
@zack-shoylev No, closing since it has been [merged](
https://github.com/jclouds/jclouds/commit/a53438159a114fb2c42faee5b3e82b21000a8665).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/365#issuecomment-43690687
This PR fixes a simple typo in the jclouds-representations project poms.
Please refer to the [Maven Central
Repository](http://search.maven.org/#artifactdetails%7Corg.apache.jclouds.labs%7Cjclouds-represetations%7C1.7.2%7Cpom)
The incorrect spelling of the artifactId has been present since
[1.6
This PR addresses the API changes as described in:
https://issues.apache.org/jira/browse/JCLOUDS-545
Accessing the `SwiftObject` metadata (with no body) is somewhat awkward with
the current `head` request:
`SwiftObject head(@PathParam("objectName") String objectName);`
That said, I added a n
Needs a single space before the end tag
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/commit/473dcd4f9bb9f8609a4ad58db35582e4a66d97c4#commitcomment-6363351
Merged to 1.7.x c29f7e6
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/367#issuecomment-43382072
Closed #101.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/101#event-121632838
Closed #367.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/367#event-122072681
Merged to 1.7.x 1f1f2f1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/373#issuecomment-43379371
Closed #373.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/373#event-122062888
Backport of #369 to 1.7.x branch
You can merge this Pull Request by running:
git pull https://github.com/rackspace/jclouds backport-fix-retry
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/373
-- Commit Summary --
* Update openstack-keyston
> + server.enqueue(addCommonHeaders(new MockResponse()
> +.setResponseCode(201)
> +.addHeader("ETag", "d9f5eb4bba4e2f2f046e54611bc8196b")));
> +
> + try {
> + Properties overrides = new Properties();
> + overrides.setProperty(PROPERTY_MAX_RETRIES, 5
Reopened #101.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/101#event-121632878
Merged to master 94459ba
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/369#issuecomment-43231616
@zack-shoylev +1 LGTM Thx!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/101#issuecomment-43258003
@zack
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/101#issuecomment-43257949
@zack-shoylev LGTM! +1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/100#issuecomment-43341705
Closed #369.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/369#event-121539141
@demobox That test failure and it appears intermittent. Since the Checkstyle
warnings are compute related, this PR should be good to merge.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/357#issuecomment-42475179
@andrewgaul @zack-shoylev Reworded commit message and will merge first thing in
the morning.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/369#issuecomment-43171200
@zack-shoylev +1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/372#issuecomment-43171447
Closed #95.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/95#event-119686954
This PR is a backport of JCLOUDS-342 to openstack-keystone in order to handle
408 errors using a BackoffLimitedRetryHandler.
You can merge this Pull Request by running:
git pull https://github.com/rackspace/jclouds fix-retry
Or you can view, comment on it, or merge it online at:
https://git
Closed #348.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/348#event-119704602
Backport of #365
You can merge this Pull Request by running:
git pull https://github.com/rackspace/jclouds backport-fix-openstack-mock
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/367
-- Commit Summary --
* Fix Accept header and removed C
@zack-shoylev Thx, looks good +1
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/97#issuecomment-43007787
Jeremy Daggett created JCLOUDS-567:
--
Summary: Upgrade Apache HttpClient to 4.3.3
Key: JCLOUDS-567
URL: https://issues.apache.org/jira/browse/JCLOUDS-567
Project: jclouds
Issue Type
This PR updates the BaseOpenStackMock test to rely on Guava types, and also
removes the Content-Type header from MockResponses.
You can merge this Pull Request by running:
git pull https://github.com/rackspace/jclouds fix-openstack-mock
Or you can view, comment on it, or merge it online at:
Closed #356.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/356#event-119695544
Merged to master 7f28dce
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/348#issuecomment-42710504
Merged to master 02ab5a9
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/95#issuecomment-42705688
Merged to master 64ecd49
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/356#issuecomment-42708055
Jeremy Daggett created JCLOUDS-560:
--
Summary: Remove aliases method in OpenStack/Rackspace APIs
Key: JCLOUDS-560
URL: https://issues.apache.org/jira/browse/JCLOUDS-560
Project: jclouds
+1 @demobox I checked in the jclouds-labs project and found no other
references. Looks good to merge. cc @andrewgaul
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/321#issuecomment-42352951
Jeremy Daggett created JCLOUDS-559:
--
Summary: Upgrade to JAX-RS 2.0
Key: JCLOUDS-559
URL: https://issues.apache.org/jira/browse/JCLOUDS-559
Project: jclouds
Issue Type: Improvement
@demobox Hmm... Not related, and I will get them in another PR.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/95#issuecomment-42335645
@Phanatic @demobox There is an outstanding
[JIRA](https://issues.apache.org/jira/browse/JCLOUDS-554) to address this in
the base Nova API. HTH!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/96#issuecomment-42327810
This PR is to update the labs project to use the latest
[ServiceType](https://github.com/jclouds/jclouds/blob/master/apis/rackspace-cloudidentity/src/main/java/org/jclouds/rackspace/cloudidentity/v2_0/ServiceType.java)
class.
You can merge this Pull Request by running:
git pull https://github.
This PR updates the Cloud Databases UK/US Provider Metadata to use the updated
[Service
Type](https://github.com/jclouds/jclouds/blob/master/apis/rackspace-cloudidentity/src/main/java/org/jclouds/rackspace/cloudidentity/v2_0/ServiceType.java)
class.
You can merge this Pull Request by running:
[
https://issues.apache.org/jira/browse/JCLOUDS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989727#comment-13989727
]
Jeremy Daggett commented on JCLOUDS-558:
[~awruef] There is something awr
Backported to 1.7.x 792e325
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/350#issuecomment-42042188
Closed #350.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/350
Merged
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/350#issuecomment-41957901
@demobox Thanks for pointing out the JIRA commentary! I think this is a great
first step and we should make it so. Let's see what @everett-toews thinks about
it.
Having separate repos is really problematic for aggregating JavaDocs into a
single set. I don't think its possible the way our repos
@demobox Its really too bad that both can't be in the same docs! Maybe we can
have another menu item called "JavaDocs" that links to the current released
version for the main jclouds project. Another suggestion would be to create a
"JavaDocs" landing page similar to the "Release Notes" page cont
> + .addHeader("X-Auth-Token", authToken)
> + .payload(payloadFromStringWithContentType(
> + "{\"os-getVNCConsole\":{\"type\":\"novnc\"}}",
> + "application/json"))
> +
> .endpoint("https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/34
[
https://issues.apache.org/jira/browse/JCLOUDS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett resolved JCLOUDS-556.
Resolution: Not a Problem
Assignee: Jeremy Daggett
> jclo
[
https://issues.apache.org/jira/browse/JCLOUDS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985696#comment-13985696
]
Jeremy Daggett commented on JCLOUDS-556:
As mentioned in
[this|h
@demobox Yes, it looks great! Will there be another PR for linking this to the
Documentation menu somehow?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/93#issuecomment-41712004
> @@ -0,0 +1,5 @@
> +Please review the [How to Contribute
> Documentation](https://wiki.apache.org/jclouds/How%20to%20Contribute%20Documentation)
> page for information on how to submit and verify your documentation update.
> +
> +Thanks!
> +
> +The Apache jclouds team
New line after "team"?
--
[
https://issues.apache.org/jira/browse/JCLOUDS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-524:
---
Assignee: Zack Shoylev (was: Jeremy Daggett)
> Standardize Major OpenStack API Versi
@demobox Thanks for head's up! Another best practice: "Before submitting a
JIRA, make sure there isn't one submitted for the issue at hand". ;)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/88#issuecomment-41566218
@demobox +1 Simple enough change. LGTM!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/354#issuecomment-41447957
Jeremy Daggett created JCLOUDS-551:
--
Summary: Move JavaDocs to jclouds.apache.org
Key: JCLOUDS-551
URL: https://issues.apache.org/jira/browse/JCLOUDS-551
Project: jclouds
Issue Type
@everett-toews @demobox Can we host our JavaDocs on jclouds.apache.org? I
received some feedback recently that users get confused when they are
redirected to http://demobox.github.io/
What if we hosted the versioned API docs at:
http://jclouds.apache.org/reference//apidocs/index.html
or
http://
[
https://issues.apache.org/jira/browse/JCLOUDS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979821#comment-13979821
]
Jeremy Daggett commented on JCLOUDS-534:
Guava 17 was officially rele
[
https://issues.apache.org/jira/browse/JCLOUDS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978748#comment-13978748
]
Jeremy Daggett commented on JCLOUDS-546:
+1 The community is responsible for
That line wraps! ;) "rackspace-cloudfiles-us" is correct.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41102522
@demobox Interesting. How would the examples break that?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68#issuecomment-41101709
[
https://issues.apache.org/jira/browse/JCLOUDS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-524:
---
Description:
The OpenStack package names in jclouds should respect the standard OpenStack
>
> +// Access the AsyncBlobStore
> +AsyncBlobStore blobStore = context.getAsyncBlobStore();
@demobox Good catch, thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/68/files#r11862540
[
https://issues.apache.org/jira/browse/JCLOUDS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett reassigned JCLOUDS-524:
--
Assignee: Jeremy Daggett
> Standardize Major OpenStack API Versi
> @@ -45,7 +47,14 @@ public SwiftObject apply(Blob from) {
> return null;
>SwiftObject object =
> objectProvider.create(blob2ObjectMd.apply(from.getMetadata()));
>object.setPayload(checkNotNull(from.getPayload(), "payload: " + from));
> - object.setAllHeaders(from.ge
@shrinandj @demobox Yes, there is no test there now, but there will be.I will
get back to this PR next week.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/338#issuecomment-40775757
[
https://issues.apache.org/jira/browse/JCLOUDS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-536:
---
Description:
JCLOUDS-526 proposes the removal of the legacy Nova QuotaClassApi, however the
@demobox My opinion is that the extension should be *removed*, but lets get
input from @everett-toews and @zack-shoylev before deciding to remove it.
@jasdeep-hundal Oh, thanks, you are right! That wasn't apparent to me based on
the API name!
>From the latest docs, the following fields appear t
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973481#comment-13973481
]
Jeremy Daggett commented on JCLOUDS-537:
This issue is to track update
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-537:
---
Affects Version/s: 1.7.3
> Update blobstore examp
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-537:
---
Labels: blobstore examples (was: )
> Update blobstore examp
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett updated JCLOUDS-537:
---
Component/s: jclouds-examples
jclouds-blobstore
> Update blobst
[
https://issues.apache.org/jira/browse/JCLOUDS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett reassigned JCLOUDS-537:
--
Assignee: Jeremy Daggett
> Update blobstore examp
Jeremy Daggett created JCLOUDS-537:
--
Summary: Update blobstore examples
Key: JCLOUDS-537
URL: https://issues.apache.org/jira/browse/JCLOUDS-537
Project: jclouds
Issue Type: Improvement
Jeremy Daggett created JCLOUDS-536:
--
Summary: Support Nova Quota Sets Extension API
Key: JCLOUDS-536
URL: https://issues.apache.org/jira/browse/JCLOUDS-536
Project: jclouds
Issue Type
@demobox @everett-toews @zack-shoylev The `QuotaClassApi` looks to have been
removed and integrated into the `os-quota-sets` API:
http://api.openstack.org/api-ref-compute-v2-ext.html#ext-os-quota-sets
My feeling right now is that we can remove this API, with the understanding
that we add support
[
https://issues.apache.org/jira/browse/JCLOUDS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973255#comment-13973255
]
Jeremy Daggett commented on JCLOUDS-346:
Examples update in the followin
This simple PR updates the various OpenStack and Rackspace service types to the
latest known services.
The jclouds-labs-openstack project will need to be updated to the new types
once this PR is merged.
cc @everett-toews @zack-shoylev
You can merge this Pull Request by running:
git pull
ht
This PR updates the Rackspace Examples to use the new OpenStack Swift API.
JIRA: https://issues.apache.org/jira/browse/JCLOUDS-346
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-examples cloudfiles-updates
Or you can view, comment on it, or merge it
@pimenas Sounds like a plan, no objections! The `getConsole()` method
definitely leaves the options open for new types of consoles in the future.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/339#issuecomment-40733191
Hi @sallum! I am going to pull this branch to my local repo, do some minor
refactoring, and push it back. Let me know if you have any questions, as we
would like to move forward with the contribution of the Glance v2 API. Thanks!
---
Reply to this email directly or view it on GitHub:
https://git
+1 You beat me to it @andrewgaul!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/348#issuecomment-40614889
> @@ -0,0 +1,6 @@
> +{
I always just take the JSON data and run it through
[JSONlint](http://jsonlint.com/) because it formats everything nicely. Please
add a newline after the last `}`, thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/339/f
> + .addHeader("X-Auth-Token", authToken)
> + .payload(payloadFromStringWithContentType(
> + "{\"os-getVNCConsole\":{\"type\":\"novnc\"}}",
> + "application/json"))
> +
> .endpoint("https://az-1.region-a.geo-1.compute.hpcloudsvc.com/v1.1/34
> +
> +/**
> + * Provides asynchronous access to Consoles via the REST API.
> + *
> + *
> + * @see ConsoleApi
> + * @author Epi Vou
> + * @see ExtensionAsyncApi
> + * @see "http://docs.openstack.org/api/openstack-compute/2/content/Extensions-d1e1444.html";
> />
> + * @see http://nova.openstack.o
@pimenas Just a quick comment about providing the following methods:
getVNCConsole(), getSPICEConsole() and getRDPConsole()
I would provide a single method "getConsole(ConsoleType type)" because that
leaves the interface open to other types of consoles that might be added.
cc @demobox
---
Reply
Hi @pimenas! Thanks again for the contribution. :)
Since this feature is an extension to Nova, we should not tie it to the core
`ServerApi` by adding a `getConsole()` method. Currently, jclouds supports the
extension APIs as
[optional](https://github.com/jclouds/jclouds/blob/master/apis/opens
I ran it through the validator and it LGTM. I believe that I can give it a +1
now. :)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/75#issuecomment-40226628
@shrinandj
[CloudFilesBlobStoreContextModule](https://github.com/jclouds/jclouds/blob/master/apis/cloudfiles/src/main/java/org/jclouds/cloudfiles/blobstore/config/CloudFilesBlobStoreContextModule.java)
extends
[SwiftBlobStoreContextModule](https://github.com/jclouds/jclouds/blob/master/apis/swif
This PR fixes the case where jclouds is assuming the blob content type to be
`application/unknown`. The original discussion can be found
[here](http://markmail.org/thread/qdxqrkhnjygjny4k).
If the user does not specify a content type, then the `X-Detect-Conent-Type`
header should be added to th
Jeremy Daggett created JCLOUDS-524:
--
Summary: Standardize Major OpenStack API Versions
Key: JCLOUDS-524
URL: https://issues.apache.org/jira/browse/JCLOUDS-524
Project: jclouds
Issue Type
901 - 1000 of 1149 matches
Mail list logo
