[jira] [Commented] (JCLOUDS-114) Support OpenStack Keystone v3 API

[ https://issues.apache.org/jira/browse/JCLOUDS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072604#comment-16072604 ] Everett Toews commented on JCLOUDS-114: --- Apologies but I won't be able to help out here

Re: [openstack-dev] [all][api] POST /api-wg/news

> On Mar 9, 2017, at 11:52 AM, Ed Leafe <e...@leafe.com> wrote: > > Greetings OpenStack community, > > Today's meeting started on a heavyhearted note, as we hoisted our virtual > beers and gave a toast to Everett Toews, who recently had to step down from > his AP

Re: [openstack-dev] [all][api] POST /api-wg/news

On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi > wrote: 2017-02-06 6:45 GMT-08:00 Brian Rosmaita >: On 2/6/17 5:51 AM, Jordan Pittier wrote: [super-enormous snip -- Chris, Ken, and

Re: [openstack-dev] [ironic] [API] Evolving our REST API

On Oct 13, 2016, at 10:00 AM, Devananda van der Veen wrote: > > So I have finalized five proposals of substantial changes we can make, that > folks agreed were important to work on, and which I believe we can do within > the > microversion framework starting

Re: [openstack-dev] [all][API WG] How does one best express a time interval as an API filtering query?

> On Oct 6, 2016, at 10:43 AM, Jeremy Stanley wrote: > > On 2016-10-06 10:30:30 -0500 (-0500), Kevin L. Mitchell wrote: > [...] >> Problem with that is that ':' is a valid character within an ISO date, >> though I do like the 'between' prefix. Now, '/' can be used if it's

[openstack-dev] [all][api] POST /api-wg/news

Subject: [all][api] POST /api-wg/news Greetings OpenStack community, Today we were joined by Scott DAngelo (scottda) who has graciously taken over the liaison role for Cinder as Alex Meade steps down. Thanks for stepping up Scott and welcome to the API WG! We also cleaned house today and

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

Top posting with general comment... It sounds like there's some consensus in Nova-land around these traits (née "capabilities"). The API Working Group [4] is also aware of similar efforts in Cinder [1][2] and Glance [3]. If these are truly the same concepts being discussed across projects, it

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Our main new topic for today was making sure that we take a more active role in curating the bugs that are now being kept in launchpad [4] by including review of those bugs in the workshopping that we do in each meeting. If you find issues in the existing

Re: [Openstack-operators] [User-committee] ACTION Needed - All WGs Chairs

the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow for new development, and promotes convergence of new APIs and future versions of existing APIs. Co-chairs: Chris Dent Michael McCune Everett Toews Guidelines

Re: [openstack-dev] [api] APIs for exposing resource capabilities

On Aug 3, 2016, at 12:59 AM, Ramakrishna, Deepti > wrote: Hi, I would like to bring your attention to my spec [1] (already approved) on capability APIs and would like to get feedback from API WG. To summarize, I propose

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, A few interesting developments in the API WG this week. The API WG reviewed the new Glance Artifact Repository (aka Glare) API [4]. The team was already adhering to most of the API WG guidelines [3] and after some reviews they were able to get excellent coverage

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

> On Jun 1, 2016, at 2:01 PM, Matt Riedemann wrote: > > Agree with Sean, I'd prefer separate microversions since it makes getting > these in easier since they are easier to review (and remember we make changes > to python-novaclient for each of these also). > >

Re: [openstack-dev] [api] API-WG summit session recap

> On May 9, 2016, at 10:12 AM, michael mccune wrote: > > Promoting the guidelines > > > The heart of the API-WG has always been the guidelines that are produced, we > had a nice discussion about how we can increase the awareness and usage of > the

[openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

Hi All, The following API guideline is ready for final review. It will be merged on March 18, if there's no further feedback. 1. Header non-proliferation guideline https://review.openstack.org/#/c/280381/ Cheers, Everett

Re: [openstack-dev] [all] [api] API Working Group Refresher

On Jan 17, 2016, at 8:56 PM, Qiming Teng > wrote: On Fri, Jan 15, 2016 at 12:48:51PM +, Chris Dent wrote: At yesterday's API Working Group meeting we decided it would be a good idea to send out a refresher on the existence of

Re: [openstack-dev] [magnum][api] Looking for a Cross-Project Liaison for the API Working Group

On Dec 2, 2015, at 12:32 AM, 王华 > wrote: Adrian, I would like to be an alternate. Regards Wanghua On Wed, Dec 2, 2015 at 10:19 AM, Adrian Otto > wrote: Everett, Thanks for

[openstack-dev] [magnum][api] Looking for a Cross-Project Liaison for the API Working Group

Hello Magnumites, The API Working Group [1] is looking for a Cross-Project Liaison [2] from the Magnum project. What does such a role entail? The API Working Group seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

On Nov 30, 2015, at 7:58 AM, michael mccune wrote: > > On 11/30/2015 08:45 AM, Sean Dague wrote: >> Ok, I'm going to assume with no real disagreement we're agreed here. I'm >> moving the api-wg notifications to #openstack-sdks now - >>

[openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

Hi All, The following API guidelines are ready for cross project review. They will be merged on Nov. 20 if there's no further feedback. 1. Add introduction for API micro version guideline https://review.openstack.org/#/c/187112/ 2. Add description of pagination parameters

Re: [openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

> On Nov 13, 2015, at 12:01 PM, John Dickinson <m...@not.mn> wrote: > > > > On 13 Nov 2015, at 9:42, Everett Toews wrote: > >> Hi All, >> >> The following API guidelines are ready for cross project review. They will >> be merged on Nov.

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

Please note that should be #openstack-sdks (plural) ! > On Nov 13, 2015, at 6:58 AM, Sean Dague wrote: > > The #openstack-api IRC channel is quite quiet most days. As such it's > not something that people are regularly checking in on, or often forget > about (I know I've been

Re: [openstack-dev] [nova][api]

On Nov 9, 2015, at 12:29 AM, Tony Breeds wrote: > > On Fri, Nov 06, 2015 at 12:30:19PM +, John Garbutt wrote: > >> Ideally, I would like us to fill out that pagination part first. > > It seems the person leading this within the API-WG is AWOL so ... A couple of

Re: [openstack-dev] [nova][api]

On Nov 6, 2015, at 6:30 AM, John Garbutt > wrote: On 6 November 2015 at 12:11, Sean Dague > wrote: On 11/06/2015 04:13 AM, Salvatore Orlando wrote: It makes sense to have a single point were response

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

On Nov 3, 2015, at 11:46 PM, John Griffith > wrote: On Tue, Nov 3, 2015 at 4:57 PM, michael mccune > wrote: On 11/03/2015 05:20 PM, Boris Pavlovic wrote: What if we add new API method that will

Re: [openstack-dev] [nova][api] Pagination in thre API

On Nov 5, 2015, at 5:44 AM, John Garbutt > wrote: On 5 November 2015 at 09:46, Richard Jones > wrote: As a consumer of such APIs on the Horizon side, I'm all for consistency in pagination,

Re: [openstack-dev] [all] service catalog: TNG

On Oct 9, 2015, at 9:39 AM, Sean Dague wrote: > > It looks like some great conversation got going on the service catalog > standardization spec / discussion at the last cross project meeting. > Sorry I wasn't there to participate. > > A lot of that ended up in here (which was an

[openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

Hi All, The following API guidelines are ready for cross project review. They will be merged on Oct. 16 if there's no further feedback. 1. Adds an API documentation guideline document https://review.openstack.org/#/c/214817/ 2. Add http400 for nonexistent resource

Re: [openstack-dev] [api][keystone][openstackclient] Standards for object name attributes and filtering

On Sep 1, 2015, at 8:36 PM, Dolph Mathews wrote: > Does anyone have an example of an API outside of OpenStack that would return > 400 in this situation (arbitrary query string parameters)? Based on my past > experience, I'd expect them to be ignored, but I can't think

Re: [openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

On Aug 27, 2015, at 10:48 AM, Everett Toews <everett.to...@rackspace.com> wrote: > Hi All, > > The following API guidelines are ready for cross project review. They will be > merged on Sept. 4 if there's no further feedback. > > 1. Add description of pagin

Re: [openstack-dev] [api] [wsme] [ceilometer] Replacing WSME with _____ ?

On Aug 28, 2015, at 6:10 PM, Morgan Fainberg morgan.fainb...@gmail.com wrote: It seems like Flask has a reasonable amount of support and there is a good ecosystem around it but that aside (as Jay said)... I definitely support exposing the schema to the end user; making it easier for the end

[openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

Hi All, The following API guidelines are ready for cross project review. They will be merged on Sept. 4 if there's no further feedback. 1. Add description of pagination parameters https://review.openstack.org/#/c/190743/ 2. Require OpenStack- in headers https://review.openstack.org/#/c/215683/

Re: [openstack-dev] [api][keystone][openstackclient] Standards for object name attributes and filtering

On Aug 26, 2015, at 4:45 AM, Henry Nash hen...@linux.vnet.ibm.com wrote: Hi With keystone, we recently came across an issue in terms of the assumptions that the openstack client is making about the entities it can show - namely that is assumes all entries have a ‘name’ attribute (which is

Re: [openstack-dev] [Resend] [api] Who owns API versioning and deprecation policy?

On Aug 21, 2015, at 3:13 PM, Geoff Arnold ge...@geoffarnold.com wrote: After reading the following pages, it’s unclear what the current API deprecation policy is and who owns it. (The first spec implies that a change took place in May 2015, but is silent on what and why.) Any hints? An

Re: [openstack-dev] [api] [all] To changes-since or not to changes-since

On Aug 9, 2015, at 11:03 PM, hao wang sxmatch1...@gmail.commailto:sxmatch1...@gmail.com wrote: Hi, stackers Since now we have merged filtering guideline[1], is that said we should implement this feature according this guideline? like this: GET /app/items?f_updated_at=gte:some_timestamp Do

[openstack-dev] [all][api] New API Guidelines ready for cross project review

Hi All, We have 7 API Guidelines that are ready for a final review. 1. Add section clarifying PUT vs PATCH semantics https://review.openstack.org/#/c/183945/ 2. Adding 5xx guidance https://review.openstack.org/#/c/183698/ 3. Adds a small update to tagging guidance

Re: [openstack-dev] [api][Solum] Request for feedback on new API resource

On Jun 18, 2015, at 3:07 PM, Devdatta Kulkarni devdatta.kulka...@rackspace.commailto:devdatta.kulka...@rackspace.com wrote: Hi, API WG team, In Solum, recently we have been working on some changes to our REST API. Basically, we have introduced a new resource ('app'). The spec for this has

[openstack-dev] [all][api] New API Guidelines ready for cross project review

Hi All, We have 3 API Guidelines that are ready for a final review. 1. Add section on filtering https://review.openstack.org/#/c/177468/ 2. http guideline expansion: background https://review.openstack.org/#/c/181931/ 3. Should not return server-side tracebacks

Re: [openstack-dev] [monasca] [java]

On May 15, 2015, at 3:49 AM, Thierry Carrez thie...@openstack.org wrote: Dieterly, Deklan wrote: We’ve seen that Swift has introduced components in Go. So, this looks like a precedent for allowing other languages where deemed appropriate. Before we spend many man-hours hacking on the Python

Re: [openstack-dev] [nova][cinder] can we deprecate the volume CLIs in novaclient?

On May 15, 2015, at 10:28 AM, John Griffith john.griffi...@gmail.commailto:john.griffi...@gmail.com wrote: On Thu, May 14, 2015 at 8:29 PM, Matt Riedemann mrie...@linux.vnet.ibm.commailto:mrie...@linux.vnet.ibm.com wrote: This came up while talking about bug 1454369 [1]. This also came up at

Re: [openstack-dev] [api] Proposing Michael McCune as an API Working Group core

Top posting to make it official...Michael McCune (elmiko) is an API Working Group core! Cheers, Everett On May 11, 2015, at 8:57 PM, Ryan Brown rybr...@redhat.com wrote: On 05/11/2015 04:18 PM, Everett Toews wrote: I would like to propose Michael McCune (elmiko) as an API Working Group core

[openstack-dev] [all][api] State of the OpenStack API Working Group: Liberty Edition

This blog post is basically a preview of our cross-project session. http://blog.phymata.com/2015/05/14/state-of-the-api-wg-liberty-edition/ The API WG will also be busy bunch at the Summit. 1 cross-project session API Working Group: State of the Group [1] 2 working group sessions API

Re: [openstack-dev] [nova][api] Allow passing body for more API methods

On May 11, 2015, at 1:05 PM, Dean Troyer dtro...@gmail.commailto:dtro...@gmail.com wrote: On Mon, May 11, 2015 at 11:44 AM, Rosa, Andrea (HP Cloud Services) andrea.r...@hp.commailto:andrea.r...@hp.com wrote: Agreed. Violating the HTTP spec is something that should be avoided. Actually it is

[openstack-dev] [api] Proposing Michael McCune as an API Working Group core

I would like to propose Michael McCune (elmiko) as an API Working Group core. Among Michael’s many fine qualities: * Active from the start * Highly available * Very knowledgable about APIs * Committed the guideline template * Working on moving the API Guidelines wiki page * Lots of

Re: [openstack-dev] [api] Changing 403 Forbidden to 400 Bad Request for OverQuota was: [nova] Which error code should we return when OverQuota

On May 6, 2015, at 1:58 PM, David Kranz dkr...@redhat.commailto:dkr...@redhat.com wrote: +1 The basic problem is we are trying to fit a square (generic api) peg in a round (HTTP request/response) hole. But if we do say we are recognizing sub-error-codes, it might be good to actually give them

Re: [openstack-dev] [nova][api] API working group liaisons and responsibilities

On Apr 30, 2015, at 9:54 AM, Jay Pipes jaypi...@gmail.com wrote: Hi Stackers, OK, so Matthew Gilliard and Alex Xu have volunteered to be the Nova team's liaisons to the API working group. Big thank you to Matthew and Alex for volunteering for this important role. I've created a wiki

Re: [openstack-dev] [all][api] 3 API Guidelines up for final review

All 3 API guidelines have merged. Thanks everyone! Everett On Apr 22, 2015, at 2:08 PM, Everett Toews everett.to...@rackspace.com wrote: Hi All, We have 3 API Guidelines that are ready for a final review. 1. Metadata guidelines document https://review.openstack.org/#/c/141229/ 2

[openstack-dev] [api] Missing meetings this week

Hi All, I’ll be out the next few days and will be missing our meetings. Specifically the cross-project meeting [1] and our API WG meeting [2]. On the plus side I got to my action items from the last meeting and “froze” the 3 guidelines up for review and proposed a cross-project session [3]

[Openstack-operators] [all][api] 3 API Guidelines up for final review

Hi All, We have 3 API Guidelines that are ready for a final review. 1. Metadata guidelines document https://review.openstack.org/#/c/141229/ 2. Tagging guidelines https://review.openstack.org/#/c/155620/ 3. Guidelines on using date and time format https://review.openstack.org/#/c/159892/ If

[openstack-dev] [all][api] 3 API Guidelines up for final review

Hi All, We have 3 API Guidelines that are ready for a final review. 1. Metadata guidelines document https://review.openstack.org/#/c/141229/ 2. Tagging guidelines https://review.openstack.org/#/c/155620/ 3. Guidelines on using date and time format https://review.openstack.org/#/c/159892/ If

Re: [openstack-dev] [api] Minor changes to API

On Apr 20, 2015, at 7:07 PM, Ian Wells ijw.ubu...@cack.org.ukmailto:ijw.ubu...@cack.org.uk wrote: On 20 April 2015 at 15:23, Matthew Treinish mtrein...@kortar.orgmailto:mtrein...@kortar.org wrote: On Mon, Apr 20, 2015 at 03:10:40PM -0700, Ian Wells wrote: It would be nice to have a consistent

Re: [openstack-dev] [all] [api] gabbi: A tool for declarative testing of APIs

On Apr 20, 2015, at 2:45 PM, Chris Dent chd...@redhat.com wrote: I wanted to make a quick update on the latest happenings with gabbi[0], the tool I've created to do declarative testing of OpenStack APIs (starting with Ceilometer and Gnocchi). * Jay Pipes and I are doing a presentation API

Re: [openstack-dev] [api] Minor changes to API

On Apr 20, 2015, at 2:19 PM, Douglas Mendizabal douglas.mendiza...@rackspace.commailto:douglas.mendiza...@rackspace.com wrote: Hi openstack-dev@ I was wondering if the API Working Group had an opinion on how to deal with minor changes to the api? For example, what if you wanted to add a new

Re: [openstack-dev] [api] API WG Meeting Time

On Apr 1, 2015, at 10:12 AM, Ian Cordasco ian.corda...@rackspace.com wrote: On 4/1/15, 08:24, michael mccune m...@redhat.com wrote: On 04/01/2015 08:35 AM, Jay Pipes wrote: On 03/31/2015 10:13 PM, Everett Toews wrote: Ever since daylight savings time it has been increasing difficult

Re: [openstack-dev] [Openstack-operators] [all][log] Openstack HTTP error codes

On Jan 29, 2015, at 8:34 PM, Rochelle Grober rochelle.gro...@huawei.commailto:rochelle.gro...@huawei.com wrote: Hi folks! Changed the tags a bit because this is a discussion for all projects and dovetails with logging rationalization/standards/ At the Paris summit, we had a number of session

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

Closed #166. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/166#event-272752086

Re: [jclouds-site] add softlayer getting started (#134)

@andreaturli The next release is out. ;) I'll leave this one up to you. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/134#issuecomment-89337328

Re: [jclouds-examples] Add layer 7 load balancer examples. (#61)

Closed #61. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/61#event-272780705

Re: [jclouds-site] Update compute.md (#130)

Closed #130. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/130#event-272779175

Re: [jclouds-labs-openstack] Adds service predicates and more tests (#186)

:+1: after a check for naming consistency is done. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/186#issuecomment-89410171

Re: [jclouds-labs-openstack] Adds service predicates and more tests (#186)

+import static com.google.common.base.Preconditions.checkNotNull; +import static java.util.concurrent.TimeUnit.SECONDS; +import static org.jclouds.util.Predicates2.retry; + +import org.jclouds.openstack.poppy.v1.domain.Service; +import org.jclouds.openstack.poppy.v1.domain.ServiceStatus;

Re: [jclouds] JCLOUDS-599 ability to execute function locally before initScript runs. (#406)

Closed #406. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/406#event-272756458

Re: [jclouds-labs-openstack] Adds service predicates and more tests (#186)

+import static com.google.common.base.Preconditions.checkNotNull; +import static java.util.concurrent.TimeUnit.SECONDS; +import static org.jclouds.util.Predicates2.retry; + +import org.jclouds.openstack.poppy.v1.domain.Service; +import org.jclouds.openstack.poppy.v1.domain.ServiceStatus;

Re: [jclouds] JCLOUDS-670 Option force no password when launching images on providers (#486)

Closed #486. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/486#event-272758128

Re: [jclouds] Throw sane error if one of security groups is null (#515)

Closed #515. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/515#event-272760104

Re: [jclouds] Updated the requests in unit test case to include globalIdentifier (#531)

Closed #531. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/531#event-272761027

Re: [jclouds] Expecting 2 of 3 or the first flaky test to succeed (#577)

Closed #577. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/577#event-272761787

Re: [jclouds-site] Update aws.md (#129)

Closed #129. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/129#event-272762945

[openstack-dev] [api] API WG Meeting Time

Ever since daylight savings time it has been increasing difficult for many API WG members to make it to the Thursday 00:00 UTC meeting time. Do we change it so there’s only the Thursday 16:00 UTC meeting time? On a related note, I can’t make it to tomorrow’s meeting. Can someone else please

[openstack-dev] [all] [api] Erring is Caring

Hi All, An API Working Group Guideline for Errors https://review.openstack.org/#/c/167793/ Errors are a crucial part of the developer experience when using an API. As developers learn the API they inevitably run into errors. The quality and consistency of the error messages returned to them

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

Top posting to continue the discussion in another thread. [openstack-dev] [all] [api] Erring is Caring http://lists.openstack.org/pipermail/openstack-dev/2015-March/060314.html Everett On Feb 4, 2015, at 10:29 AM, Duncan Thomas duncan.tho...@gmail.commailto:duncan.tho...@gmail.com wrote:

Re: [jclouds-site] Updated for 1.9.0 (#155)

Merged and published. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/155#issuecomment-87833345

[jclouds-site] Updated for 1.9.0 (#155)

You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-site/pull/155 -- Commit Summary -- * Updated for 1.9.0 -- File Changes -- M guides/openstack.md (20) -- Patch Links -- https://github.com/jclouds/jclouds-site/pull/155.patch

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

I don't know the history of this PR but the fact that it's been open since Nov. 30, 2013 is odd. @aledsage @demobox @andrewgaul Does it make sense to continue working on this? --- Reply to this email directly or view it on GitHub:

Re: [openstack-dev] [API] Do we need to specify follow the HTTP RFCs?

Top posting the relevant review https://review.openstack.org/#/c/161946/ Everett On Feb 13, 2015, at 8:44 AM, michael mccune m...@redhat.commailto:m...@redhat.com wrote: On 02/12/2015 02:20 PM, Ryan Brown wrote: +1 I think the way to go would be: We suggest (pretty please) that you comply

Re: [VOTE] Release Apache jclouds 1.9.0 RC2

+1 binding Verified 1.9.0-rc2 with verify_jclouds_rc.sh [1] SmokeTest ran with the PR [2] ComputeService live tests on Rackspace 100% successful - run by Zack BlobStore live tests on Rackspace 98% successful - run by Zack (when run with the PR [3] they’re 100% successful) Thanks to everyone

Re: [jclouds-labs] BlobStore API for Orion based back-ends (#45)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Support for OpenStack OS-Services API (#573)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] JCLOUDS-670 Option force no password when launching images on providers (#486)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Add support for Azure Copy Blob (#514)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Introduce BlobstoreCli (#487)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] JCLOUDS-642: InternalUrl fallback (#462)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Token based authentication in openstack-keystone (#433)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-examples] Add an example to create/delete/list Google Cloud Storage buckets. (#64)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-examples] GCS-Example initial commit (#66)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-labs-openstack] OS Ceilometer API support (#166)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-examples] Simplify interface of Google examples and fix the name and comment of userName variable (#63)

@demobox Can this be closed? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-examples/pull/63#issuecomment-85717848

Re: [jclouds-site] Update compute.md (#131)

Merged. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/131#issuecomment-85720599

Re: [jclouds] Add copyBlob to portable abstraction and add S3-optimized variant (#511)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Updated the requests in unit test case to include globalIdentifier (#531)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Throw sane error if one of security groups is null (#515)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-site] Update compute.md (#130)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-site] Update aws.md (#129)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-site] add softlayer getting started (#134)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Expecting 2 of 3 or the first flaky test to succeed (#577)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] Import rackspace-cloudfiles from labs (#565)

Superseded by #705 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/565#issuecomment-85716224

Re: [jclouds-examples] Add layer 7 load balancer examples. (#61)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-karaf] JCLOUDS-85: Improving the creation of instance of PropertyShellTableFact... (#18)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds] JCLOUDS-599 ability to execute function locally before initScript runs. (#406)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-labs] JCLOUDS-664: Implemented Role represenstaion in API (#118)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

Re: [jclouds-labs-aws] JCLOUDS-750: Refactor glacier domain classes using @AutoValue (#64)

Thanks for the pull request but it's release week in jclouds and that means it's time to clean up the PR queue. This PR will be over 6 months old as of April 1. If you intend to continue work on it, please make a comment by April 2. Otherwise it will be closed on April 3. --- Reply to this

  1   2   3   4   5   6   7   8   9   10   >