Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

If you compare the number of people that come to mid-cycles with the number of people that come to the summit and attend the design summit, i am sure (without knowing exact numbers) that there is a big difference in favor of the design summit. I also think that its important that users/operators

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

Le 6 févr. 2016 20:39, "Steven Dake (stdake)" a écrit : > > > > On 2/5/16, 1:14 AM, "Eric LEMOINE" wrote: > > >On Thu, Feb 4, 2016 at 5:13 PM, Jeff Peeler wrote: > >I totally agree with you Jeff. > > > >It is to be noted that we (my

[openstack-dev] [Neutron][Dragonflow] - IRC Meeting Canceled (2/8)

Hello all, Since many members (and also myself) cant make it for tomorrows meeting, we have decided to cancel it. For any urgent matters, feel free to send your question to the mailing list. We will have a meeting next week (2/15) as usual. Thanks Gal

Re: [openstack-dev] [keystone][ec2-api][heat] Moving EC2 Auth and S3Token to Externally supported

On Fri, Feb 05, 2016 at 05:57:56PM +, Fox, Kevin M wrote: >Might double check with the heat folks. I think they use some of it with >wait conditions still? Yes, we depend on the heat-api-cfn by default for many resources atm, which requires the keystone ec2tokens API. I started a

[openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API (was: [all] the trouble with names)

On 02/04/2016 06:38 AM, Sean Dague wrote: What options do we have? 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the road. Downside, yet another contention point. A registry would clearly be under TC administration,

[openstack-dev] Use of restricted and multiverse in the gate

Hey all, We're working on getting per-region APT mirrors stood up for the nodepool nodes to use in the gate. As part of working on this, it struck me that we currently have restricted and multiverse enabled in our sources.list file. I ran a quick test of removing both of them on a

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Jay and others, I’m not able to understand how the decoupled events will produce the desired outcome. Here’s why. There will still be a limit on expenditure that companies will be willing to undertake. If you were to decouple the two events, it isn’t as though companies won’t do the

[openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Hello all, tl;dr = I have long thought that the OpenStack Summits have become too commercial and provide little value to the software engineers contributing to OpenStack. I propose the following: 1) Separate the design summits from the conferences 2) Hold only a single OpenStack

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/07/2016 12:07 PM, Jay Pipes wrote: Hello all, tl;dr = I have long thought that the OpenStack Summits have become too commercial and provide little value to the software engineers contributing to OpenStack. I propose the following: 1) Separate the design summits from the conferences

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Sun, Feb 7, 2016 at 12:07 PM, Jay Pipes wrote: > Hello all, > > tl;dr > = > > I have long thought that the OpenStack Summits have become too commercial > and provide little value to the software engineers contributing to > OpenStack. > > I propose the following: > > 1)

[openstack-dev] [kosmos] IRC Meeting this week

Hi, As I am at the Designate mid cycle this week I will not make the IRC meeting this week. Can dougwig / johnsom take over, or will we skip this week? Thanks, Graham __ OpenStack Development Mailing List (not for usage

[openstack-dev] [designate] IRC Meeting Canceled this week

As most of us are in Galway at the mid cycle this week, we are going to cancel the meeting this week. Talk to you all tomorrow / next week. Thanks Graham __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova] Migration progress

On 02/04/2016 11:02 PM, Bhandaru, Malini K wrote: Another thought, for such ephemeral/changing data, such as progress, why not save the information in the cache (and flush to database at a lower rate), and retrieve for display to active listeners/UI from the cache. Once complete or aborted, of

Re: [openstack-dev] Dynamically adding Extra Specs

Apologies for the delayed responses. Comments inline. On 01/27/2016 02:29 AM, Dhvanan Shah wrote: Hey Jay! Thanks for the clarification. There was another thing that I wanted to know, is there any provision to pass extra arguments or some extra specifications along with the VM request to nova.

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Colleagues, I agree with this proposal: of course it's fun to receive some free tee-shirts/magnets, but my main interest as a developer is to take part in design summit. It will be awesome if contributors working together will also work togeter on design summits as those increase developers

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Sun, Feb 7, 2016 at 8:07 PM, Jay Pipes wrote: [snip] > Many contributors submit talks to speak at the conference part of an > OpenStack Summit because their company says it's the only way they will pay > for them to attend the design summit. This is, IMHO, a terrible

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On Mon, Feb 8, 2016 at 1:51 AM, Monty Taylor wrote: [snip] > Fifth - if we do this, the real need for the mid-cycles we currently have > probably goes away since the summit week can be a legit wall-to-wall work > week. > [snip] Another reply to a specific point... I

Re: [openstack-dev] [all] Proposal for having a service type registry and curated OpenStack REST API

On 02/07/2016 07:30 AM, Jay Pipes wrote: On 02/04/2016 06:38 AM, Sean Dague wrote: What options do we have? 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the road. Downside, yet another contention point. A registry

Re: [openstack-dev] Use of restricted and multiverse in the gate

On 02/07/2016 12:56 PM, Jim Meyer wrote: On Feb 7, 2016, at 6:11 AM, Monty Taylor wrote: Hey all, We're working on getting per-region APT mirrors stood up for the nodepool nodes to use in the gate. As part of working on this, it struck me that we currently have

[openstack-dev] [all] Getting error after doing unstack.sh on stable/liberty

I just did unstack.sh due to some reason and then afterwards when I run stack.sh I am getting following error i) Error: Service g-api is not running ii) Error: Service g-reg is not running iii) Error: Service h-api is not running After a lot of struggle I found a resolution that when I reboot my

Re: [openstack-dev] [all] Getting error after doing unstack.sh on stable/liberty

On Mon, Feb 08, 2016 at 07:04:31AM +0500, Umar Yousaf wrote: > I just did unstack.sh due to some reason and then afterwards when I run > stack.sh I am getting following error > i) Error: Service g-api is not running > ii) Error: Service g-reg is not running > iii) Error: Service h-api is not

Re: [openstack-dev] [keystone][ec2-api][swift] Moving EC2 Auth and S3Token to Externally supported

Hello guys, S3 compatibility API is now maitained in openstack namespace, it is in the external repository from original Swift though. It works as Swift proxy middleware to translate S3 api into pure Swift api. While the translation, Swift3 makes a credential to retrieve actual auth token from

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

On 02/07/2016 02:07 PM, Jay Pipes wrote: Hello all, tl;dr = I have long thought that the OpenStack Summits have become too commercial and provide little value to the software engineers contributing to OpenStack. I propose the following: 1) Separate the design summits from the conferences

Re: [openstack-dev] Dynamically adding Extra Specs

Hey Jay! I was looking at implementing a few scheduling algorithms of my own natively into OpenStack, and for that I went through the nova-scheduler. After going through the scheduler, I felt that it was not very easy to implement or extend and add new scheduling algorithms to the scheduler. The

Re: [openstack-dev] [nova] Authorization by user_id does not work in V2.1 API

> This doesn't feel intentional, and is a good catch. > https://review.openstack.org/#/c/276738/ was pushed this morning to fix it. I > think that's fine (and can be backported) > but needs tests. Sean, Thank you for your reply. I will review the patch. > It would be good to know if there were

[openstack-dev] [nova-scheduler] Scheduler sub-group meeting - Agenda 2/8

Meeting on #openstack-meeting-alt at 1400 UTC (7:00AM MDT) 1) Patches/Reviews - https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking 2) Bugs - https://bugs.launchpad.net/nova/+bugs?field.tag=scheduler 3) Opens -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: