Re: [openstack-dev] [gerrit] Preparing a patch that has dependency to more than one code under review

2014-08-08 Thread Sylvain Bauza
Hi Nader, Le 08/08/2014 09:23, Nader Lahouti a écrit : Hi, Is it possible to send a patch for review (i.e. A) on gerrit based on multiple commit under the review (i.e. B and C)? Based on the wiki page to add dependency these command should be used: A-B, A-C (no dependency between B and C)

Re: [openstack-dev] [OpenStack][InstanceGroup] metadetails and metadata in instance_group.py

2014-08-11 Thread Sylvain Bauza
Le 11/08/2014 18:03, Gary Kotton a écrit : On 8/11/14, 6:06 PM, Dan Smith d...@danplanet.com wrote: As the person who -2'd the review, I'm thankful you raised this issue on the ML, Jay. Much appreciated. The metadetails term isn't being invented in this patch, of course. I originally

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-12 Thread Sylvain Bauza
Hi Nikola, Le 12/08/2014 12:21, Nikola Đipanov a écrit : Hey Nova-istas, While I was hacking on [1] I was considering how to approach the fact that we now need to track one more thing (NUMA node utilization) in our resources. I went with - I'll add it to compute nodes table thinking it's a

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-12 Thread Sylvain Bauza
(sorry for reposting, missed 2 links...) Hi Nikola, Le 12/08/2014 12:21, Nikola Đipanov a écrit : Hey Nova-istas, While I was hacking on [1] I was considering how to approach the fact that we now need to track one more thing (NUMA node utilization) in our resources. I went with - I'll add it

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-12 Thread Sylvain Bauza
Le 12/08/2014 18:54, Nikola Đipanov a écrit : On 08/12/2014 04:49 PM, Sylvain Bauza wrote: (sorry for reposting, missed 2 links...) Hi Nikola, Le 12/08/2014 12:21, Nikola Đipanov a écrit : Hey Nova-istas, While I was hacking on [1] I was considering how to approach the fact that we now

Re: [openstack-dev] Openstack Capacity Planning

2014-08-13 Thread Sylvain Bauza
Le 13/08/2014 03:48, Fei Long Wang a écrit : Hi Adam, Please refer this https://wiki.openstack.org/wiki/Blazar. Hope it's helpful. Cheers. On 13/08/14 12:54, Adam Lawson wrote: Something was presented at a meeting recently which had me curious: what sort of capacity planning

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-13 Thread Sylvain Bauza
Le 12/08/2014 22:06, Sylvain Bauza a écrit : Le 12/08/2014 18:54, Nikola Đipanov a écrit : On 08/12/2014 04:49 PM, Sylvain Bauza wrote: (sorry for reposting, missed 2 links...) Hi Nikola, Le 12/08/2014 12:21, Nikola Đipanov a écrit : Hey Nova-istas, While I was hacking on [1] I

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-13 Thread Sylvain Bauza
Le 13/08/2014 12:21, Sylvain Bauza a écrit : Le 12/08/2014 22:06, Sylvain Bauza a écrit : Le 12/08/2014 18:54, Nikola Đipanov a écrit : On 08/12/2014 04:49 PM, Sylvain Bauza wrote: (sorry for reposting, missed 2 links...) Hi Nikola, Le 12/08/2014 12:21, Nikola Đipanov a écrit : Hey Nova

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-13 Thread Sylvain Bauza
Le 13/08/2014 18:40, Brian Elliott a écrit : On Aug 12, 2014, at 5:21 AM, Nikola Đipanov ndipa...@redhat.com wrote: Hey Nova-istas, While I was hacking on [1] I was considering how to approach the fact that we now need to track one more thing (NUMA node utilization) in our resources. I went

Re: [openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata

2014-08-14 Thread Sylvain Bauza
Mmm... I can understand that you perhaps need an external scheduler for your own purposes, but I think you can't expect your plugin merged upstream for two reasons : - during Icehouse, there was an effort for not having the scheduler proxying to the compute nodes - Call for scheduler needs to go

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-14 Thread Sylvain Bauza
] https://review.openstack.org/#/c/89893 Thanks, Michael On Thu, Aug 14, 2014 at 3:40 AM, Sylvain Bauza sba...@redhat.com wrote: Le 13/08/2014 18:40, Brian Elliott a écrit : On Aug 12, 2014, at 5:21 AM, Nikola Đipanov ndipa...@redhat.com wrote: Hey Nova-istas, While I was hacking

Re: [openstack-dev] [nova][core] Expectations of core reviewers

2014-08-14 Thread Sylvain Bauza
Le 14 août 2014 21:56, Joe Gordon joe.gord...@gmail.com a écrit : On Thu, Aug 14, 2014 at 1:47 AM, Daniel P. Berrange berra...@redhat.com wrote: On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote: On Thu, Aug 14, 2014 at 3:09 AM, Dan Smith d...@danplanet.com wrote: I'm not

Re: [openstack-dev] [nova] Review priorities as we approach juno-3

2014-08-14 Thread Sylvain Bauza
Le 14 août 2014 22:02, Michael Still mi...@stillhq.com a écrit : Hi. We're rapidly approaching j-3, so I want to remind people of the current reviews that are high priority. The definition of high priority I am using here is blueprints that are marked high priority in launchpad that have

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-15 Thread Sylvain Bauza
Le 15 août 2014 08:16, Nikola Đipanov ndipa...@redhat.com a écrit : On 08/14/2014 10:25 PM, Sylvain Bauza wrote: Hi mikal, Le 14 août 2014 01:49, Michael Still mi...@stillhq.com mailto:mi...@stillhq.com a écrit : So, there's been a lot of email in the last few days and I feel I am

Re: [openstack-dev] [nova][core] Expectations of core reviewers

2014-08-18 Thread Sylvain Bauza
Le 18 août 2014 14:36, Salvatore Orlando sorla...@nicira.com a écrit : As the conversation has drifted away from a discussion pertaining the nova core team, I have some comments inline as well. On 18 August 2014 12:18, Thierry Carrez thie...@openstack.org wrote: Doug Hellmann wrote: On

Re: [openstack-dev] [Nova] Concerns around the Extensible Resource Tracker design - revert maybe?

2014-08-19 Thread Sylvain Bauza
Le 15/08/2014 15:35, Andrew Laski a écrit : On 08/14/2014 03:21 AM, Nikola Đipanov wrote: On 08/13/2014 06:05 PM, Sylvain Bauza wrote: Le 13/08/2014 12:21, Sylvain Bauza a écrit : Le 12/08/2014 22:06, Sylvain Bauza a écrit : Le 12/08/2014 18:54, Nikola Đipanov a écrit : On 08/12/2014 04

[openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

2014-08-19 Thread Sylvain Bauza
Hi, As it was also stated in http://www.stillhq.com/openstack/juno/12.html, we expect to finish the prerequisites for Scheduler split by Juno. That requires to merge two blueprints, one with the spec validated but patches still under review [1] and one with the spec still subject to

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

2014-08-19 Thread Sylvain Bauza
Le 19/08/2014 14:51, Sylvain Bauza a écrit : Hi, As it was also stated in http://www.stillhq.com/openstack/juno/12.html, we expect to finish the prerequisites for Scheduler split by Juno. That requires to merge two blueprints, one with the spec validated but patches still under review

Re: [openstack-dev] [Nova] Scheduler split wrt Extensible Resource Tracking

2014-08-20 Thread Sylvain Bauza
/19/2014 06:39 PM, Sylvain Bauza wrote: On the other hand, ERT discussion is decoupled from the scheduler split discussion and will be delayed until Extensible Resource Tracker owner (Paul Murray) is back from vacation. In the mean time, we're considering new patches using ERT as non-acceptable

Re: [openstack-dev] [nova] Prioritizing review of potentially approvable patches

2014-08-21 Thread Sylvain Bauza
Le 21/08/2014 13:57, Daniel P. Berrange a écrit : Tagged with '[nova]' but this might be relevant data / idea for other teams too. With my code contributor hat on, one of the things that I find most the frustrating about Nova code review process is that a patch can get a +2 vote from one core

Re: [openstack-dev] [nova] Is the BP approval process broken?

2014-08-29 Thread Sylvain Bauza
lifeSorry folks, I just had a new daughter since Thursday so I'm on PTO until Monday, so thanks to the people who discussed about the blueprint I created and how we can avoid the problem raised by Don for Kilo. /life Answers inline. Le 29/08/2014 19:42, John Garbutt a écrit : I think this is

Re: [openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

2014-09-03 Thread Sylvain Bauza
Le 03/09/2014 14:38, Kuvaja, Erno a écrit : Another well working option that can be easily used: 1) get a Linux system with internet connection (local box, VM in a cloud, whatever floats your boat) 2) install irssi and screen 3) run irssi in a screen Now you can login (local console, ssh,

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-04 Thread Sylvain Bauza
Le 04/09/2014 15:36, Gary Kotton a écrit : Hi, I do not think that Nova is in a death spiral. I just think that the current way of working at the moment is strangling the project. I do not understand why we need to split drivers out of the core project. Why not have the ability to provide Œcore

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-04 Thread Sylvain Bauza
Le 04/09/2014 17:00, Solly Ross a écrit : My only question is about the need to separate out each virt driver into a separate project, wouldn't you accomplish a lot of the benefit by creating a single virt project that includes all of the drivers? I don't think there's particularly a *point*

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-04 Thread Sylvain Bauza
Le 04/09/2014 17:57, Daniel P. Berrange a écrit : On Thu, Sep 04, 2014 at 03:49:26PM +, Dugger, Donald D wrote: Actually, I think Sylvain's point is even stronger as I don't think splitting the virt drivers out of Nova is a complete fix. It may solve the review latency for the virt driver

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-05 Thread Sylvain Bauza
Le 05/09/2014 01:26, Jay Pipes a écrit : On 09/04/2014 10:33 AM, Dugger, Donald D wrote: Basically +1 with what Daniel is saying (note that, as mentioned, a side effect of our effort to split out the scheduler will help but not solve this problem). The difference between Dan's proposal and

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-05 Thread Sylvain Bauza
Le 05/09/2014 01:22, Michael Still a écrit : On Thu, Sep 4, 2014 at 5:24 AM, Daniel P. Berrange berra...@redhat.com wrote: [Heavy snipping because of length] The radical (?) solution to the nova core team bottleneck is thus to follow this lead and split the nova virt drivers out into

Re: [openstack-dev] [Nova] Feature Freeze Exception process for Juno

2014-09-05 Thread Sylvain Bauza
Le 05/09/2014 13:05, Nikola Đipanov a écrit : On 09/04/2014 10:25 PM, Solly Ross wrote: Anyway, I think it would be useful to have some sort of page where people could say I'm an SME in X, ask me for reviews and then patch submitters could go and say, oh, I need an someone to review my patch

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-05 Thread Sylvain Bauza
Le 05/09/2014 14:48, Jay Pipes a écrit : On 09/05/2014 02:59 AM, Sylvain Bauza wrote: Le 05/09/2014 01:26, Jay Pipes a écrit : On 09/04/2014 10:33 AM, Dugger, Donald D wrote: Basically +1 with what Daniel is saying (note that, as mentioned, a side effect of our effort to split out

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-05 Thread Sylvain Bauza
Le 05/09/2014 12:48, Sean Dague a écrit : On 09/05/2014 03:02 AM, Sylvain Bauza wrote: Le 05/09/2014 01:22, Michael Still a écrit : On Thu, Sep 4, 2014 at 5:24 AM, Daniel P. Berrange berra...@redhat.com wrote: [Heavy snipping because of length] The radical (?) solution to the nova core

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-05 Thread Sylvain Bauza
Le 05/09/2014 15:11, Jay Pipes a écrit : On 09/05/2014 08:58 AM, Sylvain Bauza wrote: Le 05/09/2014 14:48, Jay Pipes a écrit : On 09/05/2014 02:59 AM, Sylvain Bauza wrote: Le 05/09/2014 01:26, Jay Pipes a écrit : On 09/04/2014 10:33 AM, Dugger, Donald D wrote: Basically +1 with what Daniel

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-08 Thread Sylvain Bauza
Le 08/09/2014 18:06, Steven Dake a écrit : On 09/05/2014 06:10 AM, Sylvain Bauza wrote: Le 05/09/2014 12:48, Sean Dague a écrit : On 09/05/2014 03:02 AM, Sylvain Bauza wrote: Le 05/09/2014 01:22, Michael Still a écrit : On Thu, Sep 4, 2014 at 5:24 AM, Daniel P. Berrange berra...@redhat.com

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

2014-09-10 Thread Sylvain Bauza
Le 10/09/2014 10:44, Daniel P. Berrange a écrit : On Tue, Sep 09, 2014 at 05:14:43PM -0700, Stefano Maffulli wrote: To me, this means you don't really want a sin bin where you dump drivers and tell them not to come out until they're fit to be reviewed by the core; You want a trusted driver

Re: [openstack-dev] [nova] Server Groups - remove VM from group?

2014-09-11 Thread Sylvain Bauza
Le 11/09/2014 01:10, Joe Cropper a écrit : Agreed - I’ll draft up a formal proposal in the next week or two and we can focus the discussion there. Thanks for the feedback - this provides a good framework for implementation considerations. Count me on it, I'm interested in discussing the

Re: [openstack-dev] [gantt] Cancel the IRC meeting this week?

2014-09-16 Thread Sylvain Bauza
Le 15/09/2014 20:20, Dugger, Donald D a écrit : I’d like to propose that we defer the meeting this week and reconvene next Tues, 9/23. I don’t think there’s much new to talk about right now and we’re waiting for a write up on the claims process. I’d like to get that write up when it’s

Re: [openstack-dev] [blazar]: proposal for a new lease type

2014-09-18 Thread Sylvain Bauza
Le 18/09/2014 15:27, Lisa a écrit : Hi all, my name is Lisa Zangrando and I work at the Italian National Institute for Nuclear Physics (INFN). In particular I am leading a team which is addressing the issue concerning the efficiency in the resource usage in OpenStack. Currently OpenStack

Re: [openstack-dev] pycharm license?

2014-09-24 Thread Sylvain Bauza
Le 24/09/2014 17:41, Andrew Melton a écrit : Hey Devs, I just got clarification on what it was meant by 'commercial developer.' If developer participates in commercial consulting, develops commercial per-order customization / implementation for OpenStack (if any) – they are considered a

[openstack-dev] [climate] IRC meeting exceptionnally today 2000 UTC

2013-12-09 Thread Sylvain Bauza
, 2013, Sylvain Bauza wrote: Well, I wouldn't say more, I also have family concerns ;-) I will prepare the meeting by checking all individual actions, so I will only raise the left ones. Hooks clarification can be postponed to the next meeting or discussed directly on chan. I saw you made

[openstack-dev] [Climate] Minutes from today meeting

2013-12-09 Thread Sylvain Bauza
Huge thanks for our Russian peers who did exceptional efforts for joining us exceptionnally today at 2000 UTC (midnight their time), I owe you a beer :-) You can find our weekly meeting minutes on http://eavesdrop.openstack.org/meetings/climate/2013/climate.2013-12-09-20.01.html Thanks, -Sylvain

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

2013-12-13 Thread Sylvain Bauza
While I agree with most of what Thierry said, I need clarifications though, on what a Program is, and what is the key point where an idea should get its own Program instead of being headed by an already existing Program. For example, take Barbican which is providing extra features to Keystone, or

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

2013-12-13 Thread Sylvain Bauza
thie...@openstack.org Sylvain Bauza wrote: While I agree with most of what Thierry said, I need clarifications though, on what a Program is, A team is a group of people working on a given mission. They can be freely created. They apply to become an OpenStack Program if they feel their (well

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

2013-12-13 Thread Sylvain Bauza
Apologies for the miss, I just double-checked and Nova does have its own mission statement : http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml Thanks, -Sylvain 2013/12/13 Sylvain Bauza sylvain.ba...@gmail.com Thanks Thierry. AFAIK, Compute (Nova) is not having

Re: [openstack-dev] Unified Guest Agent proposal

2013-12-13 Thread Sylvain Bauza
the process, which should make things easy to implement and scale. Thanks, Kevin From: Sylvain Bauza [sylvain.ba...@gmail.com] Sent: Thursday, December 12, 2013 11:43 PM To: OpenStack Development Mailing List, (not for usage questions) Subject: Re

Re: [openstack-dev] [Nova][TripleO] Nested resources

2013-12-14 Thread Sylvain Bauza
Hi Kevin, 2013/12/2 Fox, Kevin M kevin@pnnl.gov Hi all, I just want to run a crazy idea up the flag pole. TripleO has the concept of an under and over cloud. In starting to experiment with Docker, I see a pattern start to emerge. * As a User, I may want to allocate a BareMetal node

Re: [openstack-dev] [climate] Weekly meeting accidental moving to Tuesday, 10:00 UTC

2013-12-16 Thread Sylvain Bauza
Le 16/12/2013 10:41, Dina Belova a écrit : Hello! Guys, I have no opportunity to hold our IRC meeting today. I propose to move it tomorrow, the same time. Please let me know if you are OK with that. Thank you! +2 to this. No regular meetings planned on Tuesdays 1000UTC as per

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

2013-12-18 Thread Sylvain Bauza
Le 17/12/2013 14:59, Thierry Carrez a écrit : Mark McLoughlin wrote: On Tue, 2013-12-17 at 13:44 +0100, Thierry Carrez wrote: Mark McLoughlin wrote: How about if we had an emerging projects page where the TC feedback on each project would be listed? That would give visibility to our

Re: [openstack-dev] [governance] Becoming a Program, before applying for incubation

2013-12-18 Thread Sylvain Bauza
Le 18/12/2013 11:25, Thierry Carrez a écrit : Sylvain Bauza wrote: Well, correct me if I'm wrong, but Stackforge is already the place for promising projects ? If so, why creating a wikipage for listing them ? Not really. Any project can be in stackforge. It doesn't have to be promising

Re: [openstack-dev] Diversity as a requirement for incubation

2013-12-18 Thread Sylvain Bauza
Le 18/12/2013 11:40, Thierry Carrez a écrit : I guess there are 3 options: 1. Require diversity for incubation, but find ways to bless or recommend projects pre-incubation so that this diversity can actually be achieved 2. Do not require diversity for incubation, but require it for graduation,

Re: [openstack-dev] Diversity as a requirement for incubation

2013-12-19 Thread Sylvain Bauza
Le 18/12/2013 16:37, Steven Dake a écrit : In the early days of incubation requests, I got the distinct impression managers at companies believed that actually getting a project incubated in OpenStack was not possible, even though it was sparsely documented as an option. Maybe things are

[openstack-dev] [Climate] Next two weekly meetings cancelled ?

2013-12-19 Thread Sylvain Bauza
Hi team, I won't be able to attend the next two weekly meetings (23Dec and 30Dec), I would like to postpone our meetings till 6th January 2014. Any objections to this ? -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

2013-12-19 Thread Sylvain Bauza
Le 19/12/2013 13:54, Sergey Lukjanov a écrit : yup, agreed. Additionally, I'd like to start a discussion about new meeting time that'd be more US-folks friendly. Luckily, we do have Internet now :

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

2013-12-19 Thread Sylvain Bauza
Le 19/12/2013 13:57, Dina Belova a écrit : I have Christmas holidays till 12th January... So I don't really know I if I will be available 6th Jan. Oh ok. Who else are still on vacation these times ? We can do our next meeting on 12th Jan, but I'm concerned with the delivery of Climate 0.1

[openstack-dev] [Climate] PTL Candidacy

2013-12-19 Thread Sylvain Bauza
Hi, I hereby would like to announce my candidacy for the Climate (Reservations) PTL. A brief history about me : I'm playing with Software Engineering and Operations since more than 10 years, with a special focus on Openstack since the Essex release. I promoted Openstack in my previous

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

2013-12-20 Thread Sylvain Bauza
. Or we can move to 1900-2000UTC. it looks fine for me. Or move to early Europe morning. *__* Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2013/12/19 Sylvain Bauza sylvain.ba...@bull.net mailto:sylvain.ba...@bull.net Le 19/12/2013 13:57, Dina Belova

Re: [openstack-dev] [Climate] Next two weekly meetings cancelled ?

2013-12-20 Thread Sylvain Bauza
for Fridays 1500 UTC On Fri, Dec 20, 2013 at 1:26 PM, Sylvain Bauza sylvain.ba...@bull.net mailto:sylvain.ba...@bull.net wrote: Well, 2000UTC means midnight for you, guys. Not really safe for family concerns :-) Maybe you were meaning 2000

Re: [openstack-dev] [climate] PTL electinos: voting

2013-12-25 Thread Sylvain Bauza
Hi. I know that's pretty late for asking but could we consider having a quorum for voting ? As the election is running during vacations for most of the team, my concern is to make sure there are enough voters. Thanks, Sylvain Le 25 déc. 2013 11:08, Sergey Lukjanov slukja...@mirantis.com a écrit

Re: [openstack-dev] [climate] PTL electinos: voting

2013-12-26 Thread Sylvain Bauza
will not be available for this period? Currently, we have 70% participation (poll have been started 18h ago). On Thu, Dec 26, 2013 at 2:27 AM, Sylvain Bauza sylvain.ba...@gmail.comwrote: Hi. I know that's pretty late for asking but could we consider having a quorum for voting ? As the election

Re: [openstack-dev] [Openstack] Quota delegation tool (for nova) ?

2013-12-26 Thread Sylvain Bauza
Hi Ulrich, I already discussed with Tim during last Swiss meetup at CERN about how Climate could maybe help you on your use cases. There are still many things to discuss and a demo to run out so we could see if it match your needs. Basically, Climate is a new Stackforge project planning to

Re: [openstack-dev] [climate] PTL elections: final results

2014-01-05 Thread Sylvain Bauza
Kudos to Dina for the PTL position. 3 vs. 5 with 80% participation means it's a good thing for Climate : this is not a Stackforge project pushed by only one sponsor and having a benevolent dictator, but rather a mix of various experiences and subprojects with people having various ideas. Now,

[openstack-dev] [Climate] Reminder: Meeting today at 1500 UTC

2014-01-10 Thread Sylvain Bauza
Hi folks, Please keep in mind that our weekly meeting changed its timeslot from Mondays to Fridays 1500 UTC. #openstack-meeting should be available at this time, booking it. -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [gantt[ Patches to sync gantt up to the current nova tree

2014-01-12 Thread Sylvain Bauza
I think we should still review the patches in case of any merging issues with Gantt code. If the volume of reviews is high, then we have to increase the number of reviewers. I was part of the discussions for an external scheduler, I will dedicate some time for +1... Afaik, the current weekly

Re: [openstack-dev] [keystoneclient] old keystone-client package on pypi

2014-01-13 Thread Sylvain Bauza
Le 27/12/2013 10:24, Nikolay Starodubtsev a écrit : Hi all, Guys, I want to say that keystoneclient package on pypi is too old. For example it hadn't Client func in keystoneclient/client.py. May be someone can help me with this? Speaking of python-keystoneclient, the latest release is

Re: [openstack-dev] [keystoneclient] old keystone-client package on pypi

2014-01-13 Thread Sylvain Bauza
Le 13/01/2014 13:49, Thierry Carrez a écrit : Sylvain Bauza wrote: Le 27/12/2013 10:24, Nikolay Starodubtsev a écrit : Hi all, Guys, I want to say that keystoneclient package on pypi is too old. For example it hadn't Client func in keystoneclient/client.py. May be someone can help me

Re: [openstack-dev] [climate][cafe] Climate and Café teams meeting

2014-01-13 Thread Sylvain Bauza
I can propose anytime at 0600 UTC, I can make efforts for waking up earlier :-) I can yet understand that other EU people couldn't attend the call, so I will aggregate and feedback all the topics for my French peers. -Sylvain 2014/1/13 Nikolay Starodubtsev nstarodubt...@mirantis.com Hi, all!

Re: [openstack-dev] [keystoneclient] old keystone-client package on pypi

2014-01-13 Thread Sylvain Bauza
Le 13/01/2014 15:00, Dolph Mathews a écrit : Ooh, I meant to get this done last week as I agree that keystoneclient needed to see a new release, but it totally slipped my mind. python-keystoneclient 0.4.2 is now available on pypi! https://pypi.python.org/pypi/python-keystoneclient/0.4.2

Re: [openstack-dev] [climate][cafe] Climate and Cafe teams meeting

2014-01-14 Thread Sylvain Bauza
:) On Mon, Jan 13, 2014 at 6:58 PM, Sergey Lukjanov slukja...@mirantis.comwrote: Are there any guys from PST timezone? On Mon, Jan 13, 2014 at 5:32 PM, Sylvain Bauza sylvain.ba...@gmail.comwrote: I can propose anytime at 0600 UTC, I can make efforts for waking up earlier

Re: [openstack-dev] [climate][cafe] Climate and Cafe teams meeting

2014-01-14 Thread Sylvain Bauza
One more thing, we can meet up on #openstack-climate (logging available), or we can take a room in #openstack-meeting for starting a formal meeting and get minutes. Both are convenient for me, but with a preference for #openstack-climate. -Sylvain 2014/1/14 Sylvain Bauza sylvain.ba

[openstack-dev] [Climate] 0.1 status meeting

2014-01-14 Thread Sylvain Bauza
Hi team, As agreed during our last meeting, we need to discuss on the progression before code freeze next Tuesday. I could propose tomorrow Wed 15 1000 UTC on #openstack-climate. +1/-1 to this, please. -Sylvain ___ OpenStack-dev mailing list

Re: [openstack-dev] [gantt] Sync up patches

2014-01-14 Thread Sylvain Bauza
Thanks Don for raising the point, I was about to send an email after finishing up to review. To me, it appears I have to give -1 when either : 1. Change is related to API documentation or WSGI framework. AIUI, Gantt will be plugged to Nova thanks to its RPC interface, it makes no sense to ship

Re: [openstack-dev] a common client library

2014-01-15 Thread Sylvain Bauza
Hi Doug, Count me in. Climate is currently working on delivering its first python-climateclient but it would be great if we could leverage any olso lib for this. -Sylvain 2014/1/15 Doug Hellmann doug.hellm...@dreamhost.com Several people have mentioned to me that they are interested in, or

Re: [openstack-dev] [gantt] Sync up patches

2014-01-16 Thread Sylvain Bauza
Le 16/01/2014 17:18, Vishvananda Ishaya a écrit : On Jan 16, 2014, at 6:46 AM, Joe Gordon joe.gord...@gmail.com mailto:joe.gord...@gmail.com wrote: On Wed, Jan 15, 2014 at 1:29 PM, Dugger, Donald D donald.d.dug...@intel.com mailto:donald.d.dug...@intel.com wrote: My thought was to

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-20 Thread Sylvain Bauza
Le 20/01/2014 16:57, Jay Pipes a écrit : On Mon, Jan 20, 2014 at 10:18 AM, Day, Phil philip@hp.com mailto:philip@hp.com wrote: HI Folks, The original (and fairly simple) driver behind whole-host-allocation (https://wiki.openstack.org/wiki/WholeHostAllocation) was to

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-20 Thread Sylvain Bauza
Hi Jay, Le 20/01/2014 17:34, Jay Pipes a écrit : On Mon, Jan 20, 2014 at 11:18 AM, Sylvain Bauza sylvain.ba...@bull.net mailto:sylvain.ba...@bull.net wrote: Jay, please be aware of the existence of Climate, which is a Stackforge project for managing dedicated resources (like AWS

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-20 Thread Sylvain Bauza
2014/1/20 Jay Pipes jaypi...@gmail.com But I believe that the two concerns can be tackled separately. Indeed. I fully agree with the fact isolation can be provided by Nova, and Climate would by the way happy to leverage it for providing capacity planning on top of it. By the way, I'm

Re: [openstack-dev] Climate - Was: Next steps for Whole Host allocation / Pclouds

2014-01-21 Thread Sylvain Bauza
Hi Phil, Le 21/01/2014 13:13, Day, Phil a écrit : Hi Phil and Jay, Phil, maybe you remember I discussed with you about the possibility of using pclouds with Climate, but we finally ended up using Nova aggregates and a dedicated filter. That works pretty fine. We don't use instance_properties

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-21 Thread Sylvain Bauza
Le 21/01/2014 12:57, Day, Phil a écrit : So, I actually don't think the two concepts (reservations and isolated instances) are competing ideas. Isolated instances are actually not reserved. They are simply instances that have a condition placed on their assignment to a particular compute node

Re: [openstack-dev] [gantt] How to include nova modules in unit tests

2014-01-21 Thread Sylvain Bauza
Hi Don, Look at how Climate is doing this [1]. The idea is to pull the master tarball as an eggfile. That works fine, the only issues we have is when we register opts to CONF where we could get DuplicateOpt if we try to register opt with same name when importing. -Sylvain [1] :

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-22 Thread Sylvain Bauza
Le 22/01/2014 02:50, Jay Pipes a écrit : Yup, agreed. It's difficult to guess what the capacity implications would be without having solid numbers on customer demands for this functionality, including hard data on how long such instances would typically live (see my previous point about

Re: [openstack-dev] [gantt] How to include nova modules in unit tests

2014-01-22 Thread Sylvain Bauza
Le 22/01/2014 01:37, Dugger, Donald D a écrit : Sylvain- Tnx, that worked great. (Now if I can just find a way to get the affinity tests working, all the other tests pass. I only have 17 tests failing out of 254.) I'm pretty busy these days with Climate 0.1 to deliver, but if I find

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-22 Thread Sylvain Bauza
Le 22/01/2014 15:57, Mike Spreitzer a écrit : Is that enough? Remember that some of us are concerned with business workloads, rather than HPC jobs. While it might be acceptable in a business workload to plan on regularly recycling every individual instance, it is definitely not acceptable

Re: [openstack-dev] [gantt] How to include nova modules in unit tests

2014-01-22 Thread Sylvain Bauza
2014/1/22 Joe Gordon joe.gord...@gmail.com On Tue, Jan 21, 2014 at 7:35 PM, Dugger, Donald D donald.d.dug...@intel.com wrote: Well, the first goal is to get the scheduler code into a separate tree, even though that code is still utilizing common code from nova. Right now just about

[openstack-dev] [Nova] Why Nova should fail to boot if there are only one private network and one public network ?

2014-01-23 Thread Sylvain Bauza
Hi, I filed a bug [1] a while ago about the impact of a review [2] which now prevents Nova to boot instances if there are two available networks within Neutron. As a side effect, users now need to pass the nic ID on the nova boot command even for simple setups with only one private network

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-23 Thread Sylvain Bauza
Le 23/01/2014 18:05, Day, Phil a écrit : I think there is a cross-over point here somewhere - call it managed cloud where the user doesn't want to run a cloud but does want (and is willing to pay for) some guarantee of isolation of hypervisors, but also wants to share other aspects of the

Re: [openstack-dev] [Nova] Why Nova should fail to boot if there are only one private network and one public network ?

2014-01-24 Thread Sylvain Bauza
Hi Phil, Le 24/01/2014 14:13, Day, Phil a écrit : HI Sylvain, The change only makes the user have to supply a network ID if there is more than one private network available (and the issue there is that otherwise the assignment order in the Guest is random, which normally leads to all sorts

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

2014-01-24 Thread Sylvain Bauza
Le 23/01/2014 18:17, Day, Phil a écrit : Just to be clear I'm not advocating putting any form of automated instance life-cycle into Nova - I agree that belongs in an external system like Climate. However for a reservations model to work efficiently it seems to be you need two complementary

Re: [openstack-dev] [Nova] Why Nova should fail to boot if there are only one private network and one public network ?

2014-01-24 Thread Sylvain Bauza
Hi Phil, 2014/1/24 Day, Phil philip@hp.com So I can see that option [1] would make the validation work by (presumably) not including the shared network in the list of networks, but looking further into the code allocate_for_instance() uses the same call to decide which networks it

Re: [openstack-dev] [Climate] [Ceilometer] Integration

2014-01-27 Thread Sylvain Bauza
Hi Julien, 2014/1/27 Julien Danjou jul...@danjou.info Hi, I've created a blueprint for Climate support in Ceilometer: https://blueprints.launchpad.net/ceilometer/+spec/climate-support I've added a list of resources that I think should be metered. I'm not sure about the other ones

Re: [openstack-dev] [all] Lots of gating failures because of testtools

2014-01-29 Thread Sylvain Bauza
Le 29/01/2014 12:07, Ivan Melnikov a écrit : I also filed a bug for taskflow, feel free to add your projects there if it's affected, too: https://bugs.launchpad.net/taskflow/+bug/1274050 Climate is also impacted, we can at least declare a recheck with this bug number. -Sylvain

Re: [openstack-dev] [all] Lots of gating failures because of testtools

2014-01-29 Thread Sylvain Bauza
Le 29/01/2014 12:51, Sean Dague a écrit : Right, but until a testtools fix is released, it won't pass. So please no rechecks until we have a new testtools from Robert that fixes things. -Sean Indeed you're right. Any way to promote some bugs with Gerrit without doing a recheck, then

Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver Scheduler

2014-01-30 Thread Sylvain Bauza
Hi Khanh-Toan, I only have one comment on your proposal : why are you proposing something new for overcommitments with aggregates while the AggregateCoreFilter [1] and AggregateRAMFilter [2]already exist, which AIUI provide same feature ? I'm also concerned about the scope of changes for

Re: [openstack-dev] [climate] New date for closest team meeting

2014-01-30 Thread Sylvain Bauza
Le 30/01/2014 15:33, Dina Belova a écrit : Hi, folks! We need to choose new date for our next weekly teem meeting due to some emergency - at least two our core members (Sylvain and Swann) and usually active meeting participants will be travelling to FOSDEM tomorrow 15:00 UTC. So they'll have

[openstack-dev] Python 3 compatibility

2014-02-03 Thread Sylvain Bauza
Hi, I was at the FOSDEM event this week-end and some interesting talks about asyncio raised my interest about this framework for replacing eventlet. Although there is an experimental port of asyncio for Python 2.6 named trollius [1], I think it would be a good move for having Python 3. I know

Re: [openstack-dev] Python 3 compatibility

2014-02-04 Thread Sylvain Bauza
Hi Julien, 2014-02-03 Julien Danjou jul...@danjou.info: There's https://wiki.openstack.org/wiki/Python3 but it's not (always) up to date. Thanks for the pointer, really helpful about the status for the main projects and some key hints. The interest never decreased, but it's always have

[openstack-dev] [wsme] WSME/Pecan serializing Exceptions

2014-02-04 Thread Sylvain Bauza
Hi, The WSME wsexpose() decorator for Pecan serializes any Exception being raised on a controller [1] I can understand the behaviour for security and visualization concerns, but I was wondering if it was possible to add an extra parameter to the decorator in order to explicitely raise the

Re: [openstack-dev] [wsme] WSME/Pecan serializing Exceptions

2014-02-04 Thread Sylvain Bauza
hi Doug, 2014-02-04 Doug Hellmann doug.hellm...@dreamhost.com: On Tue, Feb 4, 2014 at 9:43 AM, Sylvain Bauza sylvain.ba...@gmail.comwrote: If the exception has a code attribute, it is set as the status code for the response. Otherwise, the status is set to 500 as a default

Re: [openstack-dev] WSME 0.6 released

2014-02-06 Thread Sylvain Bauza
Thanks Doug, 2014-02-06 15:54 GMT+01:00 Doug Hellmann doug.hellm...@dreamhost.com: cdf74daac2a204d5fe77f4b2bf5a956f65a73a6f Support dynamic types f191f32a722ef0c2eaad71dd33da4e7787ac2424 Add IntegerType and some classes for validation Doug Do you know when the docs will be updated ?

Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver Scheduler

2014-02-11 Thread Sylvain Bauza
2014-02-10 18:45 GMT+01:00 Chris Friesen chris.frie...@windriver.com: In that model, we would pass a bunch of information about multiple resources to the solver scheduler, have it perform scheduling *and reserve the resources*, then return some kind of resource reservation tokens back to the

Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver Scheduler

2014-02-11 Thread Sylvain Bauza
Le 11/02/2014 16:09, Chris Friesen a écrit : Yes. So what I'm suggesting is that we schedule the two VMs as one call to the SolverScheduler. The scheduler then gets reservations for the necessary resources and returns them to the caller. This would be sort of like the existing Claim

Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver Scheduler

2014-02-11 Thread Sylvain Bauza
Le 11/02/2014 17:23, Yathiraj Udupi (yudupi) a écrit : Hi Dina, Thanks for note about Climate logic. This is something that will be very useful, when we will have to schedule from Nova multiple instances (of potentially different flavors) as a single request. If the Solver Scheduler, can

Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver Scheduler

2014-02-11 Thread Sylvain Bauza
2014-02-11 18:28 GMT+01:00 Yathiraj Udupi (yudupi) yud...@cisco.com: Thanks for your pointers about Climate. I will take a closer look at it and try it out. So after a reservation lease for a VM is made by Climate, who acts on it to finally instantiate the VM ? Is it Climate or Nova

  1   2   3   4   5   6   >