Re: [openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

On 13 нояб. 2013 г., at 6:39, Angus Salkeld wrote: > Your work mates;) https://github.com/rackerlabs/qonos > > how about merge qonos into mistral, or at lest put it into stack forge? Just got to looking at qonos. It actually looks similar in some ways to Mistral but with some differences: no

Re: [openstack-dev] [Solum] Command Line Interface for Solum

On Nov 14, 2013 1:10 PM, "Adrian Otto" wrote: > > Noorul, > > On Nov 13, 2013, at 7:43 PM, Noorul Islam K M > wrote: > > > Doug Hellmann writes: > > > >> On Sun, Nov 10, 2013 at 10:15 AM, Noorul Islam K M wrote: > >> > >>> > >>> Hello all, > >>> > >>> I registered a new blueprint [1] for comman

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

>-Original Message- >From: Clint Byrum [mailto:cl...@fewbar.com] >Sent: Tuesday, November 12, 2013 9:24 PM >To: openstack-dev >Subject: Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat > >Excerpts from Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo)'s >messag

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

>>From: Steve Baker [mailto:sba...@redhat.com] >>Sent: Tuesday, November 12, 2013 9:25 PM >>To: openstack-dev@lists.openstack.org >>Subject: Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat >> >>On 11/13/2013 07:50 AM, Steven Dake wrote: >>On 11/12

Re: [openstack-dev] Glance Tasks

Responses to both Jay and George inline. On Wed, Nov 13, 2013 at 5:08 PM, Jay Pipes wrote: > Sorry for top-posting, but in summary, I entirely agree with George here. > His logic is virtually identical to the concerns I raised with the initial > proposal for Glance Tasks here: > > http://lists.

Re: [openstack-dev] Nova SSL Apache2 Question

On 13 November 2013 23:39, Miller, Mark M (EB SW Cloud - R&D - Corvallis) < mark.m.mil...@hp.com> wrote: > I finally found a set of web pages that has a working set of configuration > files for the major OpenStack services " > http://andymc-stack.co.uk/2013/07/apache2-mod_wsgi-openstack-pt-2-nova-

Re: [openstack-dev] Custom Flavor creation through Heat

>not the video I was looking for, but he kind of makes the point about >planning... >http://youtu.be/2E0C9zLSINE?t=42m55s > ># Shawn Hartsock > Thanks Shawn for your inputs. As I have mentioned earlier, the usecase is mostly for telecom cloud applications running in our private cloud. The hardw

Re: [openstack-dev] [RFC] Straw man to start the incubation / graduation requirements discussion

Kurt Griffiths wrote: >> Also does it place a requirement that all projects wanting to request >> incubation to be placed in stackforge ? That sounds like a harsh >> requirement if we were to reject them. > > I think that anything that encourages projects to get used to the > OpenStack development

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

On 13/11/13 17:20 -0800, Stefano Maffulli wrote: On 11/13/2013 04:34 PM, Colin McNamara wrote: Not to be contrarian, but 92% of the commits in Havana came from non-individual contributions. The majority of those came from big name companies (IBM, RedHat, etc). ow, that's harsh. Despite what US

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

On 13/11/13 17:22 -0700, John Griffith wrote: On Wed, Nov 13, 2013 at 5:14 PM, Jay Pipes wrote: On 11/11/2013 12:44 PM, Daniel P. Berrange wrote: On Mon, Nov 11, 2013 at 03:20:20PM +0100, Nicolas Barcet wrote: Dear TC members, Our companies are actively encouraging our respective customers

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

Stefano Maffulli wrote: > On 11/13/2013 04:34 PM, Colin McNamara wrote: >> Not to be contrarian, but 92% of the commits in Havana came from >> non-individual contributions. The majority of those came from big name >> companies (IBM, RedHat, etc). > > ow, that's harsh. Despite what US Supreme Cour

Re: [openstack-dev] [RFC] Straw man to start the incubation / graduation requirements discussion

On 14/11/13 10:13 +0100, Thierry Carrez wrote: Kurt Griffiths wrote: Also does it place a requirement that all projects wanting to request incubation to be placed in stackforge ? That sounds like a harsh requirement if we were to reject them. I think that anything that encourages projects to g

[openstack-dev] [Ceilometer] Meeting agenda for Thu Nov 14th at 1500 UTC

The Ceilometer project team holds a meeting in #openstack-meeting, see https://wiki.openstack.org/wiki/Meetings/MeteringAgenda for more details. Next meeting is on Thu Nov 14th at 1500 UTC Please add your name with the agenda item, so we know who to call on during the meeting. * Pick our officia

Re: [openstack-dev] Congress: an open policy framework

On 13/11/13 10:40 -0800, Tim Hinrichs wrote: We're just getting started with Congress and understanding how it will integrate with the OS ecosystem, but here's our current thinking about how Congress relates to Oslo's policy engine and to Keystone. Comments and suggestions are welcome. Cong

Re: [openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

As for EventScheduler proposal, I think it actually fits Mistral model very well. What described in EvenScheduler is basically the ability to configure webhooks to be called periodically or at a certain time. First of all, from the very beginning the concept of scheduling has been considered a v

Re: [openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

On 14/11/13 11:29, Renat Akhmerov wrote: As for EventScheduler proposal, I think it actually fits Mistral model very well. What described in EvenScheduler is basically the ability to configure webhooks to be called periodically or at a certain time. First of all, from the very beginning the conce

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

Also, just to add some pedantry (which you know I am very fond of), it would be the case to share on openstack-dev minutes and logs from eavesdrop after each subteam meeting. I know they're anyway at http://eavesdrop.openstack.org/meetings/ - but sending an email will be useful to notify the rest o

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

Sure, no problem. On Thu, Nov 14, 2013 at 3:07 PM, Salvatore Orlando wrote: > Also, just to add some pedantry (which you know I am very fond of), it > would be the case to share on openstack-dev minutes and logs from eavesdrop > after each subteam meeting. > I know they're anyway at http://eaves

Re: [openstack-dev] [Neutron] - Vendor specific erros

In general, an error state make sense. I think you might want to send more details about how this state plugs into the load balancer state machine, but I reckon it is a generally non-recoverable state which could be reached by any other state; in that case it would be a generic enough case which mi

Re: [openstack-dev] [Neutron] Blueprint -- Floating IP Auto Association

Hi Steven, I see three Steven Weston on Launchpad. If you give me your LP ID, I will assign the blueprint to you. This is a nova parity item and i'd like to raise the priority to High. It would be also good to hear from you about the implementation approach. In the past we debated two alternative

Re: [openstack-dev] [neutron] [ipv6] IPv6 meeting - Thursdays 21:00UTC - #openstack-meeting-alt

Although IRC requires typing, I find it more inclusive than Webex. It's easy to have 100s of people in a IRC room, not so easy on a conf call. Also, people like me whose 1st language is not English might find easier to write & read rather than listen & speak. Finally, the capability of generating

Re: [openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

On 14 Nov 2013, at 18:03, Zane Bitter wrote: > What might be a downside is that sharing a back-end may not be technically > convenient - one thing we have been reminded of in Heat is that a service > with timed tasks has to be scaled out in a completely different way to a > service that avoid

[openstack-dev] [Cinder][Glance] OSLO update

Hello all, I have made several patches that update modules in cinder/openstack/common from oslo which have not been reviewed for more than a month already. My colleague has the same problem with her patches in Glance. Probably it's not a top priority issue, but if oslo is not updated periodically

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

On Thu, Nov 14, 2013 at 08:22:57AM +, Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo) wrote: > Thanks Steve Baker for the information. I am also waiting to hear from Steve > Hardy, if keystone trust system will fix the nova flavors admin privileges > issue. So, basically, no. Tru

Re: [openstack-dev] [nova][object] One question to the resource tracker session

On 13 November 2013 23:22, Andrew Laski wrote: > On 11/13/13 at 11:12pm, Jiang, Yunhong wrote: >> >> Hi, Dan Smith and all, >> I noticed followed statement in 'Icehouse tasks' in >> https://etherpad.openstack.org/p/IcehouseNovaExtensibleSchedulerMetrics >> >> convert resour

Re: [openstack-dev] Congress: an open policy framework

On Wed, Nov 13, 2013 at 10:40 AM, Tim Hinrichs wrote: > We're just getting started with Congress and understanding how it will > integrate with the OS ecosystem, but here's our current thinking about how > Congress relates to Oslo's policy engine and to Keystone. Comments and > suggestions are

Re: [openstack-dev] [Cinder][Glance] OSLO update

Hello! I have made the same work in Glance — updating glance/openstack from Oslo. I'd appreciate your reviews and comments very much. https://review.openstack.org/#/c/46088/ https://review.openstack.org/#/c/46955/ https://review.openstack.org/#/c/48195/ Also I've faced a strange problem

[openstack-dev] Split of the openstack-dev list

Hi everyone, I think that we have recently reached critical mass for the openstack-dev mailing-list, with 2267 messages posted in October, and November well on its way to pass 2000 again. Some of those are just off-topic (and I've been regularly fighting against them) but most of them are just abo

Re: [openstack-dev] Split of the openstack-dev list

Thierry Carrez wrote: > [...] > That will not solve all issues. We should also collectively make sure > that *usage questions are re-routed* to the openstack general > mailing-list, where they belong. Too many people still answer off-topic > questions here on openstack-dev, which encourages people

[openstack-dev] AWS compatibility discussions at today's Nova Meeting

Hi Folks, As a first follow up after last week's design summit session, let's discuss at today's Nova meeting the steps to be taken for putting in continuous efforts for AWS compatibility in Openstack. Nova Meeting: 21:00 UTC Summit Etherpad:

Re: [openstack-dev] Split of the openstack-dev list

On Thu, Nov 14 2013, Thierry Carrez wrote: > Other suggestion: we could stop posting meeting reminders to -dev (I > know, I'm guilty of it) and only post something if the meeting time > changes, or if the weekly meeting is canceled for whatever reason. Good suggestion. -- Julien Danjou -- Free

Re: [openstack-dev] Split of the openstack-dev list

On Thu, Nov 14 2013, Thierry Carrez wrote: > Thoughts ? I agree on the need to split, the traffic is getting huge. As I'd have to subscribe to both openstack-dev and stackforge-dev, that would not help me personally, but I think it can be an easy and first step. -- Julien Danjou -- Free Softwa

Re: [openstack-dev] Split of the openstack-dev list

Yeah, that's big problem... Especially when you are trying to keep track on lots of topics... I suppose this solution will do letters' prioritisation at least easier for developers and everybody who is subscribed on openstack-dev. Nice idea. On Thu, Nov 14, 2013 at 9:12 PM, Thierry Carrez wrote:

Re: [openstack-dev] Split of the openstack-dev list

On Thu, Nov 14, 2013 at 02:19:24PM +0100, Thierry Carrez wrote: > Thierry Carrez wrote: > > [...] > > That will not solve all issues. We should also collectively make sure > > that *usage questions are re-routed* to the openstack general > > mailing-list, where they belong. Too many people still an

Re: [openstack-dev] Split of the openstack-dev list

https://wiki.openstack.org/wiki/Meetings 2013/11/14 Daniel P. Berrange > On Thu, Nov 14, 2013 at 02:19:24PM +0100, Thierry Carrez wrote: > > Thierry Carrez wrote: > > > [...] > > > That will not solve all issues. We should also collectively make sure > > > that *usage questions are re-routed* t

Re: [openstack-dev] Split of the openstack-dev list

On Thu, Nov 14 2013, Daniel P. Berrange wrote: > Is there somewhere on the website which keeps a record of all regular > scheduled meetings people can discover / refer to easily ? It's all on the wiki: https://wiki.openstack.org/wiki/Meetings -- Julien Danjou // Free Software hacker / indepe

Re: [openstack-dev] [Solum] Command Line Interface for Solum

On Thu, Nov 14, 2013 at 1:28 AM, Adrian Otto wrote: > Are you referring to "openstack solum …" in your suggestion of what not to > do? If there is no project name in there, how would it work? Would we have > a flat global namespace for all verbs? > Yes. See https://wiki.openstack.org/wiki/OpenSta

Re: [openstack-dev] Split of the openstack-dev list

On 14/11/13 13:23, Daniel P. Berrange wrote: Is there somewhere on the website which keeps a record of all regular scheduled meetings people can discover / refer to easily ? https://wiki.openstack.org/wiki/Meetings Cheers, -- Stephen Gran Senior Systems Integrator - theguardian.com Please con

Re: [openstack-dev] Glance Tasks

One critical reasons why tasks rather than resource status may be required is because: a) The system state may not be sufficient at time of POST/PUT to generate a “minimum viable resource” and we don’t want to risk timeouts waiting for the “minimum viable resource" b) There may be more stuff ab

Re: [openstack-dev] [reviews] putting numbers on -core team load

On Thu, Nov 14, 2013 at 5:59 PM, Robert Collins wrote: > > Total reviews: 10705 (118.9/day) > Total reviewers: 406 > Total reviews by core team: 5289 (58.8/day) > Core team size: 17 > New patch sets in the last 90 days: 7515 (83.5/day) > > This is the really interesting bit. Remembering that every

Re: [openstack-dev] Split of the openstack-dev list

This would also have the added benefit of reducing the times people conflate related open source projects from stackforge with OpenStack itself. Having related oss discussions on a list called "OpenStack-Dev" may certainly have given the wrong impression to the casual observer. On Nov 14, 201

Re: [openstack-dev] [reviews] putting numbers on -core team load

On Fri, Nov 15, 2013 at 12:04 AM, Christopher Yeoh wrote: > On Thu, Nov 14, 2013 at 5:59 PM, Robert Collins > wrote: > So if everyone uploaded perfect changesets we'd only need 40 core reviews > per day :-) > And I should add in terms of changesets that are eventually going to merge (not be aban

Re: [openstack-dev] Split of the openstack-dev list

Julien Danjou wrote: > On Thu, Nov 14 2013, Thierry Carrez wrote: > >> Thoughts ? > > I agree on the need to split, the traffic is getting huge. > > As I'd have to subscribe to both openstack-dev and stackforge-dev, that > would not help me personally, but I think it can be an easy and first > s

Re: [openstack-dev] Split of the openstack-dev list

On 11/14/2013 08:12 AM, Thierry Carrez wrote: > Hi everyone, > > I think that we have recently reached critical mass for the > openstack-dev mailing-list, with 2267 messages posted in October, and > November well on its way to pass 2000 again. Some of those are just > off-topic (and I've been regu

Re: [openstack-dev] Split of the openstack-dev list

On 14/11/13 14:12 +0100, Thierry Carrez wrote: Hi everyone, I think that we have recently reached critical mass for the openstack-dev mailing-list, with 2267 messages posted in October, and November well on its way to pass 2000 again. Some of those are just off-topic (and I've been regularly fig

Re: [openstack-dev] [nova] Core pinning

On 13.11.2013 20:20, Jiang, Yunhong wrote: -Original Message- From: Chris Friesen [mailto:chris.frie...@windriver.com] Sent: Wednesday, November 13, 2013 9:57 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] Core pinning On 11/13/2013 11:40 AM, Jiang, Yunhon

Re: [openstack-dev] Congress: an open policy framework

On 14/11/13 04:40 -0800, Morgan Fainberg wrote: On Wed, Nov 13, 2013 at 10:40 AM, Tim Hinrichs wrote: We're just getting started with Congress and understanding how it will integrate with the OS ecosystem, but here's our current thinking about how Congress relates to Oslo's policy engine and

Re: [openstack-dev] [reviews] putting numbers on -core team load

On Thu, Nov 14, 2013 at 08:29:36PM +1300, Robert Collins wrote: > At the summit there were lots of discussions about reviews, and I made > the mistake of sending a mail to Russell proposing a few new stats we > could gather. > > I say mistake, because he did so and then some... we new have extra >

[openstack-dev] [Mistral] Etherpad for Mistral high level design and 3rd party technologies

Hi, We’ve created an etherpad to start thinking about Mistral main components and listing out possible 3rd party technologies to use for their implementation. https://etherpad.openstack.org/p/MistralDesignAndDependencies Feel free to share your ideas. Thanks. Renat Akhmerov @ Mirantis Inc.__

[openstack-dev] [Solum] Version scheme

Hello all, We need to decide on version scheme that we are going to use. Monty Taylor said the following in one of the comments for review [1]: Setting a version here enrolls solum in managing its version in a pre-release versioning manner, such that non-tagged versions will indicated that the

Re: [openstack-dev] [reviews] putting numbers on -core team load

On 11/14/2013 09:03 AM, Daniel P. Berrange wrote: > On Thu, Nov 14, 2013 at 08:29:36PM +1300, Robert Collins wrote: >> At the summit there were lots of discussions about reviews, and I made >> the mistake of sending a mail to Russell proposing a few new stats we >> could gather. >> >> I say mistake

Re: [openstack-dev] RFC: reverse the default Gerrit sort order

On Thu, Nov 07, 2013 at 12:36:49PM +1300, Robert Collins wrote: > I've been thinking about review queues recently (since here at the > summit everyone is talking about reviews! :)). > > One thing that struck me today was that Gerrit makes it easier to > review the newest changes first, rather than

Re: [openstack-dev] [PTL] Proposed Icehouse release schedule

On Wed, Nov 13, 2013 at 9:07 PM, Jeremy Stanley wrote: > On 2013-11-13 14:15:31 +0100 (+0100), Thierry Carrez wrote: > [...] > > * Week of April 21 > [...] > > I've already got travel plans this week, so works for me (and > release week too, though it was scheduled well over a year ago). > > > *

Re: [openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

On 14/11/13 12:26, Renat Akhmerov wrote: On 14 Nov 2013, at 18:03, Zane Bitter mailto:zbit...@redhat.com>> wrote: What might be a downside is that sharing a back-end may not be technically convenient - one thing we have been reminded of in Heat is that a service with timed tasks has to be scal

[openstack-dev] [Neutron] Port mirroring

Hello devs, I'd like to start working at this blueprint: https://blueprints.launchpad.net/neutron/+spec/port-mirroring I didn't receive much feedback so please have a look at it. It was not approved yet. What's the usual workflow? Shall I wait for approval before I start implementing it? Sorry

Re: [openstack-dev] Glance Tasks

On 11/14/2013 08:32 AM, George Reese wrote: One critical reasons why tasks rather than resource status may be required is because: a) The system state may not be sufficient at time of POST/PUT to generate a “minimum viable resource” and we don’t want to risk timeouts waiting for the “minimum via

Re: [openstack-dev] Split of the openstack-dev list

++ On 11/14/2013 08:37 AM, m...@openstack.org wrote: This would also have the added benefit of reducing the times people conflate related open source projects from stackforge with OpenStack itself. Having related oss discussions on a list called "OpenStack-Dev" may certainly have given the wro

Re: [openstack-dev] [style] () vs \ continuations

On Wed, Nov 13, 2013 at 6:46 PM, Robert Collins wrote: > Hi so - in http://docs.openstack.org/developer/hacking/ > > it has as bullet point 4: > Long lines should be wrapped in parentheses in preference to using a > backslash for line continuation. > > I'm seeing in some reviews a request for () o

Re: [openstack-dev] [nova] Configure overcommit policy

On 13 November 2013 14:51, Khanh-Toan Tran wrote: > Well, I don't know what John means by "modify the over-commit calculation in > the scheduler", so I cannot comment. I was talking about this code: https://github.com/openstack/nova/blob/master/nova/scheduler/filters/core_filter.py#L64 But I am

[openstack-dev] [Heat] Continue discussing multi-region orchestration

Hi all, At summit in Hong Kong we had a design session where we discussed adding multi-region orchestration support to Heat. During the session we had really heated discussion and spent most of the time on explaining the problem. I think it was really good starting point and right now more pe

Re: [openstack-dev] Split of the openstack-dev list

On Thu, Nov 14, 2013 at 7:12 AM, Thierry Carrez wrote: > Hi everyone, > > I think that we have recently reached critical mass for the > openstack-dev mailing-list, with 2267 messages posted in October, and > November well on its way to pass 2000 again. Some of those are just > off-topic (and I've

Re: [openstack-dev] Split of the openstack-dev list

+1, agreed. Personally, I’ll subscribe to both lists but I think it really could help to prioritize emails. Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. On Nov 14, 2013, at 5:12 PM, Thierry Carrez wrote: > Hi everyone, > > I think that we have recently reached critic

Re: [openstack-dev] [keystone] design summit outcomes

On Wed, Nov 13, 2013 at 10:04:04AM -0600, Dolph Mathews wrote: > I guarantee there's a few things I'm forgetting, but this is my collection > of things we discussed at the summit and determined to be good things to > pursue during the icehouse timeframe. The contents represent a high level > mix of

Re: [openstack-dev] Split of the openstack-dev list

On Thu, Nov 14, 2013 at 7:12 AM, Thierry Carrez wrote: > Hi everyone, > > I think that we have recently reached critical mass for the > openstack-dev mailing-list, with 2267 messages posted in October, and > November well on its way to pass 2000 again. Some of those are just > off-topic (and I've

Re: [openstack-dev] Using AD for keystone authentication only

You can assign roles to users in keystoneclient ($ keystone help user-role-add) -- the assignment would be persisted in SQL. openstackclient supports assignments to groups as well if you switch to --identity-api-version=3 On Wed, Nov 13, 2013 at 3:08 PM, Avi L wrote: > Oh ok so in this case how

Re: [openstack-dev] [nova] Configure overcommit policy

In fact, there is a blueprint which would enable supporting this scenario without partitioning -- https://blueprints.launchpad.net/nova/+spec/cpu-entitlement The idea is to annotate flavors with CPU allocation guarantees, and enable differentiation between instances, potentially running on the

Re: [openstack-dev] Alembic or SA Migrate (again)

On 11/13/2013 05:31 AM, Roman Podoliaka wrote: 2) run tests on MySQL/PostgreSQL instead (we have a proof-of-concept implementation here [2]) The latter approach has a few problems though: 1) even if tests are run in parallel and each test case is run within a single transaction with ROLLBACK in

Re: [openstack-dev] [qa] Tracking development of scenario tests

+1, This is a great idea. We could consider it as a general process for all tests. 2013/11/14 Koderer, Marc > Hi all, > > I think we have quite the same issue with the neutron testing. I already > put it on the agenda for the QA meeting for today. > Let's make it to a general topic. > > Regard

Re: [openstack-dev] [neutron] Group-based Policy Sub-team Meetings

Kyle, Thank you for organizing this. I think the original email you sent out did not solicit any comments (except for possibly proposing a different time for the weekly meetings). So that is probably why you have not heard from anybody (including me). So we are ready to have the meeting but if t

Re: [openstack-dev] Split of the openstack-dev list

On Thu, Nov 14, 2013 at 2:22 PM, Julien Danjou wrote: > > Other suggestion: we could stop posting meeting reminders to -dev (I > > know, I'm guilty of it) and only post something if the meeting time > > changes, or if the weekly meeting is canceled for whatever reason. > > Good suggestion. > Or

Re: [openstack-dev] Split of the openstack-dev list

Good idea. -romain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Solum] Version scheme

I'm not a big fan of using date information in the version number. Is there an advantage to doing that? Using a model like 0.0.1 makes it easier to communicate. A better approach might be to use Major.Minor.Revision.Build. If we want to use dates, Year.Month.Day.Build or Year.Minor.Revision.B

Re: [openstack-dev] [heat][mistral] EventScheduler vs Mistral scheduling

On Thu, Nov 14, 2013 at 4:29 AM, Renat Akhmerov wrote: > As for EventScheduler proposal, I think it actually fits Mistral model > very well. What described in EvenScheduler is basically the ability to > configure webhooks to be called periodically or at a certain time. First of > all, from the ver

[openstack-dev] [keystone] External authentication

Hi all, During the review of [1] I had a look at the tests that are related with external authentication (i.e. the usage of REMOTE_USER) in Keystone and I realised that there is a bunch of them that are setting "external" as one of the authentication methods. However, in keystone.auth.controllers

Re: [openstack-dev] nova image list | Error 401

On 2013-11-14 04:41, Santosh Kumar wrote: Hi Experts, I am following Havana guide for installation of three node set up. After installing all services of NOVA ( nova-api , nova-cert, nova-scheduler, nova-consoleauth, nova-novncproxy ), when I tires to verify All the things by # nova image-l

Re: [openstack-dev] [Solum] Version scheme

On 11/14/2013 10:36 AM, Murali Allada wrote: > I'm not a big fan of using date information in the version number. Is > there an advantage to doing that? Using a model like 0.0.1 makes it > easier to communicate. > > A better approach might be to use *Major.Minor.Revision.Build*. If we > want to

[openstack-dev] [Heat] rough draft of Heat autoscaling API

http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and provides schemas for inputs and outputs using JSON-Schema. The source document is currently at https://githu

Re: [openstack-dev] [heat][keystone] APIs, roles, request scope and admin-ness

On Sat, Nov 2, 2013 at 11:06 AM, Steven Hardy wrote: > Hi all, > > Looking to start a wider discussion, prompted by: > https://review.openstack.org/#/c/54651/ > https://blueprints.launchpad.net/heat/+spec/management-api > https://etherpad.openstack.org/p/heat-management-api > > Summary - it has b

Re: [openstack-dev] [Solum] Version scheme

- Original Message - > > > On 11/14/2013 10:36 AM, Murali Allada wrote: > > I'm not a big fan of using date information in the version number. Is > > there an advantage to doing that? Using a model like 0.0.1 makes it > > easier to communicate. > > > > A better approach might be to use

Re: [openstack-dev] [Solum] Version scheme

Monty Taylor writes: > On 11/14/2013 10:36 AM, Murali Allada wrote: >> I'm not a big fan of using date information in the version number. Is >> there an advantage to doing that? Using a model like 0.0.1 makes it >> easier to communicate. >> >> A better approach might be to use *Major.Minor.Revi

Re: [openstack-dev] [nova] Configure overcommit policy

>Step 1: use flavors so nova can tell between the two workloads, and >configure them differently > >Step 2: find capacity for your workload given your current cloud usage > >At the moment, most of our solutions involve reserving bits of your >cloud capacity for different workloads, generally using

Re: [openstack-dev] [neutron] Group-based Policy Sub-team Meetings

On Nov 14, 2013, at 9:38 AM, Mohammad Banikazemi wrote: > Kyle, > > Thank you for organizing this. > > I think the original email you sent out did not solicit any comments (except > for possibly proposing a different time for the weekly meetings). So that is > probably why you have not hear

Re: [openstack-dev] [Neutron] Port mirroring

On Nov 14, 2013, at 8:46 AM, Rossella Sblendido wrote: > > Hello devs, > > I'd like to start working at this blueprint: > > https://blueprints.launchpad.net/neutron/+spec/port-mirroring > > I didn't receive much feedback so please have a look at it. > > It was not approved yet. What's the usu

Re: [openstack-dev] Congress: an open policy framework

I completely agree that making Congress successful will rely crucially on addressing performance and scalability issues. Some thoughts... 1. We're definitely intending to cache data locally to avoid repeated API calls. In fact, a prototype cache is already in place. We haven't yet hooked up

Re: [openstack-dev] [PTL] Proposed Icehouse release schedule

Anne Gentle wrote: > Just a question, did you consider a week off post-summit? I want to > ensure the tons of questions that come in about the schedule can be > answered. I felt the weeks up to the summit were still quite busy, not > just from a docs perspective, but from a PTL/scheduler/arranger >

[openstack-dev] [Nova][vmware] VMwareAPI sub-team reviews update 2013-11-14

Greetings Stackers! I hope you had a great time at the Summit! I'm expecting the VMwareAPI sub-team's priorities to shift around a bit as we digest the outcomes from the sessions. So, with that in mind, I'll stick to just updating on what reviews are in flight and where they are as far as our

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Nov 14, 2013, at 10:19 AM, Christopher Armstrong mailto:chris.armstr...@rackspace.com>> wrote: http://docs.heatautoscale.apiary.io/ I've thrown together a rough sketch of the proposed API for autoscaling. It's written in API-Blueprint format (which is a simple subset of Markdown) and prov

Re: [openstack-dev] Split of the openstack-dev list

On Nov 14, 2013 5:16 AM, "Thierry Carrez" wrote: > > Hi everyone, > > I think that we have recently reached critical mass for the > openstack-dev mailing-list, with 2267 messages posted in October, and > November well on its way to pass 2000 again. Some of those are just > off-topic (and I've been

Re: [openstack-dev] Split of the openstack-dev list

On 11/14/2013 08:21 AM, Julien Danjou wrote: On Thu, Nov 14 2013, Thierry Carrez wrote: Thoughts ? I agree on the need to split, the traffic is getting huge. As I'd have to subscribe to both openstack-dev and stackforge-dev, that would not help me personally, but I think it can be an easy an

Re: [openstack-dev] [style] () vs \ continuations

On Nov 14, 2013 6:58 AM, "Dolph Mathews" wrote: > > > On Wed, Nov 13, 2013 at 6:46 PM, Robert Collins wrote: >> >> Hi so - in http://docs.openstack.org/developer/hacking/ >> >> it has as bullet point 4: >> Long lines should be wrapped in parentheses in preference to using a >> backslash for line

Re: [openstack-dev] [Cinder][Glance] OSLO update

This ML is not for review requests. Please read http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html best, Joe sent on the go On Nov 14, 2013 4:26 AM, "Elena Ezhova" wrote: > Hello all, > > I have made several patches that update modules in cinder/openstack/common > fr

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

Good stuff! Some questions/comments: If web hooks are associated with policies and policies are independent entities, how does a web hook specify the scaling group to act on? Does calling the web hook activate the policy on every associated scaling group? Regarding web hook execution and cool d

Re: [openstack-dev] [Solum] Version scheme

Thanks for the clear explanation Monty. -Murali > On Nov 14, 2013, at 10:08 AM, "Monty Taylor" wrote: > > > >> On 11/14/2013 10:36 AM, Murali Allada wrote: >> I'm not a big fan of using date information in the version number. Is >> there an advantage to doing that? Using a model like 0.0.

Re: [openstack-dev] Nova SSL Apache2 Question

Hello Jesse, Thank you for the information. Would you be so kind as to provide a URL to the updated rcbops chef cookbooks for Quantum? Regards, Mark From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com] Sent: Thursday, November 14, 2013 12:43 AM To: OpenStack Development Mailing List (not f

Re: [openstack-dev] [Heat] rough draft of Heat autoscaling API

On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt wrote: > Good stuff! Some questions/comments: > > If web hooks are associated with policies and policies are independent > entities, how does a web hook specify the scaling group to act on? Does > calling the web hook activate the policy on every as

Re: [openstack-dev] [nova][object] One question to the resource tracker session

> -Original Message- > From: Andrew Laski [mailto:andrew.la...@rackspace.com] > Sent: Wednesday, November 13, 2013 3:22 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova][object] One question to the resource > tracker session > > On

Re: [openstack-dev] [style] () vs \ continuations

On Thu, Nov 14, 2013 at 10:03 AM, Joe Gordon wrote: > > On Nov 14, 2013 6:58 AM, "Dolph Mathews" wrote: >> >> >> On Wed, Nov 13, 2013 at 6:46 PM, Robert Collins >> wrote: >>> >>> Hi so - in http://docs.openstack.org/developer/hacking/ >>> >>> it has as bullet point 4: >>> Long lines should be wr

Re: [openstack-dev] [heat][keystone] APIs, roles, request scope and admin-ness

On Thu, Nov 14, 2013 at 10:20:02AM -0600, Dolph Mathews wrote: > On Sat, Nov 2, 2013 at 11:06 AM, Steven Hardy wrote: > > > Hi all, > > > > Looking to start a wider discussion, prompted by: > > https://review.openstack.org/#/c/54651/ > > https://blueprints.launchpad.net/heat/+spec/management-api

Re: [openstack-dev] Nova SSL Apache2 Question

I believe I found it under nova-network. Thanks, Mark From: Miller, Mark M (EB SW Cloud - R&D - Corvallis) Sent: Thursday, November 14, 2013 9:31 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Nova SSL Apache2 Question Hello Jesse, Thank you fo

Re: [openstack-dev] [nova] Configure overcommit policy

Khanh-Toan Tran wrote on 14/11/2013 06:27:39 PM: > It is interesting to see the development of the CPU entitlement > blueprint that Alex mentioned. It was registered in Jan 2013. > Any idea whether it is still going on? Yes. I hope we will be able to rebase and submit for review soon. Regards

  1   2   3   >