On Fri, Apr 25, 2014 at 6:10 PM, Zaro wrote:
> Gerrit 2.8 allows setting label values on patch sets either thru the
> command line[1] or REST API[2]. Since we will setup WIP as a -1 score
> on a label this will just be a matter of updating git-review to set
> the label on new patchsets. I'm no
Hi, if you're in the CC list for this email, you've proposed a session
which has been (tentatively - final confirmation tomorrow or so)
accepted for the Juno summit.
Please ensure that you take care of the following required steps for
these proposals:
- There must be a dedicated etherpad for the
Thanks for submitting your session(s) - unfortunately summit space is
limited and while the selection is not yet final its likely your
session(s) below won't be included.
Please do feel free to raise the discussion topic at the TripleO
program pod during the week though - that is there specificall
On 22 April 2014 20:45, Thierry Carrez wrote:
> Robert Collins wrote:
>> I've pulled the summit talks into an etherpad
>> (https://etherpad.openstack.org/p/tripleo-icehouse-summit) - btw, who
>> can review these within the system itself?
>
> As the lead for the TripleO topic, you should be able to
I've collated the votes and put a proposed selection of talks (some
sessions merged) up; I'm going to push a draft timetable as soon as I
finish clicking on the clicky thing .:).
If your session has been selected you now need to:
- ensure there is an etherpad for it
- link it into the global lis
On 28/04/14 05:02, Michael Still wrote:
Hi.
I've just pushed a draft summit schedule to sched.org. I'd be
interested in people who proposed a session that was accepted checking
if their session time clashes with other commitments that they have,
as well as people who are passionate about a given
Hi, developers,
When I test the ceilometer threshold alarm, I find that there is no
limitation for the threshold value, which means we can set it to negative
value, but I didn't find any volume of meters will be negative, (if I'm
wrong, please let me know, thanks)
So, my question is: should we ad
On Thu, 2014-04-17 at 19:58 +0300, Roman Bodnarchuk wrote:
> Hello,
>
> I am trying to make sure that a user can't do anything useful with an
> unscoped token, and got to the following code in
> keystoneclient.middleware.auth_token:
>
> if _token_is_v2(token_info) and not auth_ref.proj
On 19:19 Sun 27 Apr , Andreas Jaeger wrote:
> So, my proposal would be:
> * Remove WADL links
> * Have PDF links to go http://docs.openstack.org
> * For those current links to the site http://docs.openstack.org: Take
> care that they point either to a current file or get redirected to
> htt
Jay, Huiba, Chris, Solly, Zhiyan, and everybody else,
I am so excited that two of the proposals: Image Upload Plugin(
http://summit.openstack.org/cfp/details/353) and Data transfer service
Plugin(http://summit.openstack.org/cfp/details/352) have been merged
together and scheduled in the coming d
Hi Matthew,
Thanks for your response.
2014-04-28 11:02 GMT+09:00 Matthew Treinish :
> On Mon, Apr 28, 2014 at 01:01:00AM +, Kenichi Oomichi wrote:
>>
>> Now we are working for adding Nova API responses checks to Tempest[1] to
>> block backward incompatible changes.
>> With this work, Tempest
I'm making a new thread continuing from
[openstack-dev] [Neutron][LBaaS] BBG edit of new API proposal
I think this warrants its own thread since the discussion doesn't
pertain directly to Stephen's proposal.
Eugene,
What I think what Stephen is trying to say is that in the previous IRC
meeting i
Hi Balaji.
Although I don't have specific opinion on name itself, can you share
its origin?
googlability for virtue seems okay, but I'm bit worried about legal stuff.
thanks,
On Thu, Apr 24, 2014 at 05:55:43AM +,
"balaj...@freescale.com" wrote:
> +1 for the proposal to make it as separate
2014-04-28 11:00 GMT+09:00 Michael Still :
> On Mon, Apr 28, 2014 at 11:24 AM, Kenichi Oomichi
> wrote:
>> Hi Michael,
>>
>> Thanks for the schedule draft.
>> I'd like to pick one comment about it.
>>
>> Now sessions related to Nova v3 API are scheduled like:
>> - 5:20pm May 14: "Nova V3 API"
>>
On Mon, Apr 28, 2014 at 01:01:00AM +, Kenichi Oomichi wrote:
>
> Hi,
>
> Sorry for my late response, but I'd like to discuss this again.
>
> Now we are working for adding Nova API responses checks to Tempest[1] to
> block backward incompatible changes.
> With this work, Tempest checks each r
On Mon, Apr 28, 2014 at 11:24 AM, Kenichi Oomichi
wrote:
> Hi Michael,
>
> Thanks for the schedule draft.
> I'd like to pick one comment about it.
>
> Now sessions related to Nova v3 API are scheduled like:
> - 5:20pm May 14: "Nova V3 API"
> - 5:00pm May 15: "Nova V2 on V3 API implementation POC
Hi Michael,
Thanks for the schedule draft.
I'd like to pick one comment about it.
Now sessions related to Nova v3 API are scheduled like:
- 5:20pm May 14: "Nova V3 API"
- 5:00pm May 15: "Nova V2 on V3 API implementation POC"
but "Nova V3 API" session needs some inputs from "Nova V2 on V3 API
Hi,
Sorry for my late response, but I'd like to discuss this again.
Now we are working for adding Nova API responses checks to Tempest[1] to
block backward incompatible changes.
With this work, Tempest checks each response(status code, response body)
and raises a test failure exception if detect
On Sun, Apr 27, 2014 at 12:19 PM, Andreas Jaeger wrote:
> The documentation team noticed that we have links in the version
> responses of several APIs that contain URLs that do not exist at all.
>
> For example, cinder includes a link to
> "
> http://jorgew.github.com/block-storage-api/content/os
Thanks for your inputs, Matt and Anne. I’m punting on the first question (re:
publishing) for now. It sounds like this is a larger discussion and we can make
progress on the PHP SDK user-facing documentation without answering it right
away. I’ll bring it up again if we don’t have an answer by th
On 25/04/14 11:29, Clint Byrum wrote:
> Also by loading the whole stack we've allowed resources to bleed into
> other resource. Currently to read Metadata for a single item that
> entails _a lot_ of queries to the database because we end up having to
> load the entire stack. We can't continue that
On 23/04/14 04:42, Thomas Spatzier wrote:
> Hi all,
>
> following up on Zane's request from end of last week, I wanted to kick off
> some discussion on the ML around a design summit session proposal titled "
> Next steps for Heat Software Orchestration". I guess there will be things
> that can be s
Hi,
> You knew from the action items that came out of the IRC meeting of April
> 17 that my team would be working on an API revision proposal. You also knew
> that this proposal was to be accompanied by an object model diagram and
> glossary, in order to clear up confusion. You were in that meeti
Somewhat surprised this got zero responses. Some comments inline from me.
On 04/15/2014 10:39 PM, Adam Young wrote:
As we get closer to the summit, I'd like to make sure we have resolution
on one of the most critical issues in Keystone. How to deal with users
coming out of multiple data sources
Hi Michael,
Thanks for sharing the schedule. A quick glance shows me that all
scheduler-related sessions will happen on Friday, that's fine :-)
Just a quick note, Climate (now Blazar) was identified as a good
opportunity for scheduling in Nova but the session will happen on Tuesday
afternoon [1].
Hi.
I've just pushed a draft summit schedule to sched.org. I'd be
interested in people who proposed a session that was accepted checking
if their session time clashes with other commitments that they have,
as well as people who are passionate about a given proposal ensuring
that they're available
The documentation team noticed that we have links in the version
responses of several APIs that contain URLs that do not exist at all.
For example, cinder includes a link to
"http://jorgew.github.com/block-storage-api/content/os-block-storage-1.0.pdf";
- and jorgew.github.com does not exist as hos
Agree with Dina, we should support V2 here.
Sorry, I had no time for delivering a new client, but as V1 and V2 are
quite identical, I can take this blueprint.
-Sylvain
2014-04-27 17:44 GMT+02:00 Dina Belova :
> Christian, variant #2 looks good to me)
>
>
> On Fri, Apr 25, 2014 at 9:59 PM, Marti
Christian, variant #2 looks good to me)
On Fri, Apr 25, 2014 at 9:59 PM, Martinez, Christian <
christian.marti...@intel.com> wrote:
> Hello,
>
> One comment regarding
> https://blueprints.launchpad.net/climate/+spec/before-end-notification-crud:
>
> One of Dina’s comments on the https://review.
I have done a little test for the image download and upload. I created an
API for the image access, containing copyFrom and sendTo. I moved the
image download and upload code from XenApi into the implementation for
Http with some modifications, and the code worked for libvirt as well.
copyFrom
>
> On Fri, Apr 25, 2014 at 4:03 AM, Eugene Nikanorov > wrote:
>
>> Hi Stephen,
>>
>> Thanks for the great document. As I promised, I'll try to make a few
>> action items out if it.
>> First of all, I'd like to say that the API you have proposed is very
>> close to what is proposed in the blueprin
Hi,
The work to design the APIs concerning L7 content switching and SSL termination
has started a bit before the Icehouse summit, it involved the ML in a very
active fashion.
The ML was silent on this because we have completed the discussion and moved to
implementation.
We got to a very advance
Hi Eugene,
Apologies for the delay in my response. It took me a while to figure out
how to say what I wanted to say here as diplomatically as possible. In the
end, I decided I couldn't be diplomatic about some of the things that I
think needed to be said. I don't play games of politics very well a
33 matches
Mail list logo
