Re: [openstack-dev] [Neutron] FWaaS IceHouse summit prep and IRC meeting

2013-10-30 Thread Sumit Naiksatam
I believe people would like to define the zone based on the router port (corresponding to that router's interface). The zone definition at port-level granularity allows one to do that. I think your other question is answered as well (firewall will be supported on particular routers). Thanks,

Re: [openstack-dev] [Nova] Blueprint review process

2013-10-30 Thread Russell Bryant
On 10/29/2013 07:14 PM, Tom Fifield wrote: On 30/10/13 07:58, Russell Bryant wrote: On 10/29/2013 04:24 PM, Stefano Maffulli wrote: On 10/28/2013 10:28 AM, Russell Bryant wrote: 2) Setting clearer expectations. Since we have so many blueprints for Nova, I feel it's very important to

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

2013-10-30 Thread Alex Glikson
Mike Spreitzer mspre...@us.ibm.com wrote on 30/10/2013 06:11:04 AM: Date: 30/10/2013 06:12 AM Alex also wrote: ``I wonder whether it is possible to find an approach that takes into account cross-resource placement considerations (VM-to-VM communicating over the application network, or

Re: [openstack-dev] [Nova] Blueprint review process

2013-10-30 Thread Tom Fifield
On 30/10/13 17:14, Russell Bryant wrote: On 10/29/2013 07:14 PM, Tom Fifield wrote: On 30/10/13 07:58, Russell Bryant wrote: On 10/29/2013 04:24 PM, Stefano Maffulli wrote: On 10/28/2013 10:28 AM, Russell Bryant wrote: 2) Setting clearer expectations. Since we have so many blueprints for

[openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Swapnil Kulkarni
I had a discussion with russellb regarding this for yesterday, I would like to discuss this with the team regarding the blueprint mentioned in subject. https://blueprints.launchpad.net/nova/+spec/auto-vm-discovery-on-hypervisor Description: Organizations opting to use openstack can have varied

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Russell Bryant
On 10/30/2013 02:36 AM, Swapnil Kulkarni wrote: I had a discussion with russellb regarding this for yesterday, I would like to discuss this with the team regarding the blueprint mentioned in subject. https://blueprints.launchpad.net/nova/+spec/auto-vm-discovery-on-hypervisor Description:

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Jason Kölker
On Wed, Oct 30, 2013 at 6:19 AM, Ravi Kumar Pasumarthy ravi...@thoughtworks.com wrote: Hello, Looks like the current column limit for the code base is 80. Because of this large space on the right hand side is not used. Please find the attached pictures of couple of developer screens working

Re: [openstack-dev] [Nova] Blueprint review process

2013-10-30 Thread Russell Bryant
On 10/30/2013 02:26 AM, Tom Fifield wrote: On 30/10/13 17:14, Russell Bryant wrote: On 10/29/2013 07:14 PM, Tom Fifield wrote: So, how would you feel about giving some priority manipulation abilities to the user committee? :) Abilities, no, but input, of course. Any practical ideas on the

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Swapnil Kulkarni
I agree, I was wondering having additional support for such a feature would definitely have value addition for adoption of OpenStack. It can be developed as an optional functionality during host addition which users can opt on case-to-case basis. Best Regards, Swapnil On Wed, Oct 30, 2013 at

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Alex Glikson
Maybe a more appropriate approach could be to have a tool/script that does it, as a one time thing. For example, it could make sense in a scenario when Nova DB gets lost or corrupted, a new Nova controller is deployed, and the DB needs to be recreated. Potentially, since Nova DB is primarily a

Re: [openstack-dev] [Nova]Ideas of idempotentcy-client-token

2013-10-30 Thread Mitsuru Kanabuchi
On Tue, 29 Oct 2013 10:32:18 + Joe Gordon joe.gord...@gmail.com wrote: * Can you fill out the questions found in http://justwriteclick.com/2013/09/17/openstack-docimpact-flag-walk-through/ I guess, ClientToken(Idempotent) implementation is nice idea for API requester. In my opinion, after

Re: [openstack-dev] [Cinder] Propose Jay Bryant for core

2013-10-30 Thread Avishay Traeger
+1 From: John Griffith john.griff...@solidfire.com To: OpenStack Development Mailing List openstack-dev@lists.openstack.org, Date: 10/29/2013 11:05 PM Subject:[openstack-dev] [Cinder] Propose Jay Bryant for core Hey, I wanted to propose Jay Bryant (AKA jsbryant,

[openstack-dev] Update resources API

2013-10-30 Thread GROSZ, Maty (Maty)
Hi *, I wonder how does OpenStack Update resource APIs are handling a case in which the update request is to clear an existed attribute value: For example, let A be a resource (Server, Image, Volume... whatever) and A1, A2 and A3 are all attribute of resource A. Let 'a' be the current value of

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Swapnil Kulkarni
Exactly, I believe getting new as well as existing workload in any cloud environment is always a plus and I agree this will mostly be a tool/script to be used as per requirement. Best Regards, Swapnil Kulkarni swapnilkulkarni2...@gmail.com +91-87960 10622(c) http://in.linkedin.com/in/coolsvap

Re: [openstack-dev] [Nova]Ideas of idempotentcy-client-token

2013-10-30 Thread haruka tanizawa
Hi Mitsuru-san! Thank you for your comment. I guess, ClientToken(Idempotent) implementation is nice idea for API requester. In my opinion, after POST requested, A requester have to stop processing when it cannot get response, because requester doesn't know what the resouce created

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Victor Sergeyev
By the way, pep8 says, that it is okay to increase the nominal line length from 80 to 100 characters. See http://www.python.org/dev/peps/pep-0008/#maximum-line-length I'm ok with 80 characters, but just for information - is there any plans to to increase the line length in OpenStack? Victor On

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Alex Glikson
Russell Bryant rbry...@redhat.com wrote on 30/10/2013 10:20:34 AM: On 10/30/2013 03:13 AM, Alex Glikson wrote: Maybe a more appropriate approach could be to have a tool/script that does it, as a one time thing. For example, it could make sense in a scenario when Nova DB gets lost or

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Roman Prykhodchenko
Hi there, Limiting the lines to 80 symbols makes viewing/editing/comparing two files on a single screen quite comfortable. This is not only useful for Vimers who do not use graphical IDEs but also makes debugging/troubleshooting easier when someone has a development/preproduction server(s)

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

2013-10-30 Thread Steven Weston
Does anybody know what the status of this Blueprint is? https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip I am new to the neutron developer community and I am looking for a first project - this might be a good place to start. But the last update was in March of this

[openstack-dev] [TripleO] TripleO core reviewer update - november

2013-10-30 Thread Robert Collins
Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with -core responsibilities. In this months review: - James Slagle for -core - Arata

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Zhongyue Luo
This would be a nightmare to some people who work with xwindows disabled by default. Not to mention going through code via console on a server. On Oct 30, 2013 4:53 PM, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: Hi there, Limiting the lines to 80 symbols makes

Re: [openstack-dev] [TripleO] TripleO core reviewer update - november

2013-10-30 Thread Chris Jones
Hi On 30 October 2013 09:06, Robert Collins robe...@robertcollins.net wrote: - James Slagle for -core Very +1 - Arata Notsu to be removed from -core +1 - Devananda van der veen to be removed from -core +1 Thanks to Arata and Devananda for their efforts to date (and of course

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

2013-10-30 Thread Álvaro López García
Hi Tim. On Tue 29 Oct 2013 (16:18), Tim Bell wrote: We also need some standardisation on the command line options for the client portion (such as --os-auth-method, --os-x509-cert etc.) . Unfortunately, this is not yet in Oslo so there would be multiple packages to be enhanced. I totally

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

2013-10-30 Thread Álvaro López García
On Tue 29 Oct 2013 (17:04), Adam Young wrote: On 10/29/2013 12:18 PM, Tim Bell wrote: We also need some standardisation on the command line options for the client portion (such as --os-auth-method, --os-x509-cert etc.) . Unfortunately, this is not yet in Oslo so there would be multiple

Re: [openstack-dev] [Nova] Blueprint review process

2013-10-30 Thread Thierry Carrez
Stefano Maffulli wrote: On 10/28/2013 10:28 AM, Russell Bryant wrote: 2) Setting clearer expectations. Since we have so many blueprints for Nova, I feel it's very important to accurately set expectations for how the priority of different projects compare. In the last cycle, priorities were

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

2013-10-30 Thread David Chadwick
Hi Alvaro On 30/10/2013 09:38, Álvaro López García wrote: On Tue 29 Oct 2013 (17:04), Adam Young wrote: On 10/29/2013 12:18 PM, Tim Bell wrote: We also need some standardisation on the command line options for the client portion (such as --os-auth-method, --os-x509-cert etc.) .

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Joe Gordon
On Wed, Oct 30, 2013 at 8:31 AM, Alex Glikson glik...@il.ibm.com wrote: Russell Bryant rbry...@redhat.com wrote on 30/10/2013 10:20:34 AM: On 10/30/2013 03:13 AM, Alex Glikson wrote: Maybe a more appropriate approach could be to have a tool/script that does it, as a one time thing.

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Daniel P. Berrange
On Wed, Oct 30, 2013 at 10:35:59AM +, Joe Gordon wrote: On Wed, Oct 30, 2013 at 8:31 AM, Alex Glikson glik...@il.ibm.com wrote: Russell Bryant rbry...@redhat.com wrote on 30/10/2013 10:20:34 AM: On 10/30/2013 03:13 AM, Alex Glikson wrote: Maybe a more appropriate approach could

[openstack-dev] [Climate] The next 2 weekly meetings

2013-10-30 Thread Sylvain Bauza
Hi Climate folks, Mondays 1000 UTC is the regular timeslot for Climate IRC weekly meetings, but there will be some impacts for the next 2 weeks : - Monday 4/11, we all will be flying to the Openstack Summit, either already in HK or on track. - Monday 11/11 is a day off in France Here is

[openstack-dev] [qa] Cancelling QA meeting for tomorrow

2013-10-30 Thread Sean Dague
I now some of the qa-core is already starting to get on planes, and everyone else will be soon. As such I'm cancelling the QA meeting for tomorrow (and the week after, being summit and all). Etherpads for summit sessions can be found here -

Re: [openstack-dev] [Climate] The next 2 weekly meetings

2013-10-30 Thread Dina Belova
I'm OK with 1/, but I have flight from HK exactly 12/11, that's why 2/ is not really comfortable for me. Dina On Wed, Oct 30, 2013 at 2:53 PM, Sylvain Bauza sylvain.ba...@bull.netwrote: Hi Climate folks, Mondays 1000 UTC is the regular timeslot for Climate IRC weekly meetings, but there

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Sean Dague
On 10/30/2013 06:48 AM, Thierry Carrez wrote: Zhongyue Luo wrote: This would be a nightmare to some people who work with xwindows disabled by default. Not to mention going through code via console on a server. Yes, preserving the ability to work on code and visualizing patches in default

Re: [openstack-dev] [Climate] The next 2 weekly meetings

2013-10-30 Thread Dina Belova
Wednesdays the same time (10:00 UTC) is also free. I think we may use this date for our meeting, if you don't mind. On Wed, Oct 30, 2013 at 3:16 PM, Dina Belova dbel...@mirantis.com wrote: I'm OK with 1/, but I have flight from HK exactly 12/11, that's why 2/ is not really comfortable for me.

Re: [openstack-dev] [Climate] The next 2 weekly meetings

2013-10-30 Thread Sylvain Bauza
Hi Dina, I'm fine with the Wed timeslot at 1000 UTC. Others ? -Sylvain Le 30/10/2013 12:25, Dina Belova a écrit : Wednesdays the same time (10:00 UTC) is also free. I think we may use this date for our meeting, if you don't mind. On Wed, Oct 30, 2013 at 3:16 PM, Dina Belova

Re: [openstack-dev] [TripleO] TripleO core reviewer update - november

2013-10-30 Thread James Slagle
On Wed, Oct 30, 2013 at 5:06 AM, Robert Collins robe...@robertcollins.net wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

2013-10-30 Thread Gary Kotton
From: Alex Glikson glik...@il.ibm.commailto:glik...@il.ibm.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Wednesday, October 30, 2013 12:32 AM To: OpenStack Development Mailing List (not

[openstack-dev] [Nova] The existent ability of showing deleted flavors in Flavors v2 API

2013-10-30 Thread Tiago Mello
Hey there! The current API for Flavors allows you to retrieve information about a flavor even though it has been deleted. However it does not return any information saying that flavor is deleted. This is a problem for nova client flavor-delete today and possibly for other situations. Nova client

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Steven Hardy
On Wed, Oct 30, 2013 at 10:45:57AM +0200, Roman Prykhodchenko wrote: If a line of code is complex enough to not fit 80 symbols I'd suggest simplifying the algorithm. Btw, some of displays can be turned for 90˚ so this might be a way to go with graphical IDEs :) Agreed, I think Linus Torvalds

[openstack-dev] [qa] Duplicated test effort development

2013-10-30 Thread Christopher Yeoh
Hi, It looks like we have lots of people writing tests at the moment which is great, but the downside is we're starting to see people accidentally writing tests for the same APIs at the same time. There is a google spreadsheet which covers the Nova v2 API where we can reserve what tests we're

Re: [openstack-dev] [qa] Duplicated test effort development

2013-10-30 Thread Christopher Yeoh
On Wed, Oct 30, 2013 at 11:18 PM, Steven Hardy sha...@redhat.com wrote: On Wed, Oct 30, 2013 at 11:00:22PM +1030, Christopher Yeoh wrote: snip I don't think blueprints/bugs work so well at this, and I don't think we have anything else setup at the moment, so as a temporary measure I've

[openstack-dev] [Climate] Launchpad project update

2013-10-30 Thread Dina Belova
Hi everyone! I've added Climate into the 'openstack' group on Launchpad to make Gerrit links to BPs working. Additionally I've updated project description to cover current status. Thanks! Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

2013-10-30 Thread Isaku Yamahata
On Wed, Oct 30, 2013 at 04:14:40AM +, Jiang, Yunhong yunhong.ji...@intel.com wrote: But how about long term direction? Neutron should know/manage such network related resources on compute nodes? So you mean the PCI device management will be spited between Nova and Neutron? For

Re: [openstack-dev] [Cinder] Propose Jay Bryant for core

2013-10-30 Thread Martin, Kurt Frederick (ESSN Storage MSDU)
+1 -Original Message- From: John Griffith [mailto:john.griff...@solidfire.com] Sent: Tuesday, October 29, 2013 1:54 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Cinder] Propose Jay Bryant for core Hey, I wanted to propose Jay Bryant (AKA jsbryant, AKA jungleboy,

Re: [openstack-dev] [Climate] Launchpad project update

2013-10-30 Thread Sylvain Bauza
Le 30/10/2013 14:41, Dina Belova a écrit : Hi everyone! I've added Climate into the 'openstack' group on Launchpad to make Gerrit links to BPs working. Additionally I've updated project description to cover current status. Cool ! Nice to see you found the root cause for the broken links

Re: [openstack-dev] [nova] Thoughs please on how to address a problem with mutliple deletes leading to a nova-compute thread pool problem

2013-10-30 Thread Dan Genin
Punishing benign users as a defense against (potentially) malicious users sounds like a bad strategy. This should not be a zero-sum game. On 10/28/2013 02:49 PM, Joshua Harlow wrote: Sure, convergence model is great and likely how it has to be done. Its just a question of what is that

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Flavio Percoco
On 30/10/13 07:22 -0400, Sean Dague wrote: On 10/30/2013 06:48 AM, Thierry Carrez wrote: Zhongyue Luo wrote: This would be a nightmare to some people who work with xwindows disabled by default. Not to mention going through code via console on a server. Yes, preserving the ability to work on

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Dan Smith
1) I agree with Russell that Nova should not try to manage VMs it didn't create. Me too. A lot. --Dan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] Meetings will resume Thursday, Nov. 7

2013-10-30 Thread Russell Bryant
Greetings, The next two Nova meetings are canceled. We will resume our weekly meetings on Thursday, Nov 7. Get those Icehouse blueprints filed and in shape in the meantime! Thanks, -- Russell Bryant ___ OpenStack-dev mailing list

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

2013-10-30 Thread Adam Young
On 10/30/2013 05:38 AM, Álvaro López García wrote: On Tue 29 Oct 2013 (17:04), Adam Young wrote: On 10/29/2013 12:18 PM, Tim Bell wrote: We also need some standardisation on the command line options for the client portion (such as --os-auth-method, --os-x509-cert etc.) . Unfortunately, this

Re: [openstack-dev] [Nova] Meetings will resume Thursday, Nov. 14

2013-10-30 Thread Russell Bryant
On 10/30/2013 10:59 AM, Russell Bryant wrote: Greetings, The next two Nova meetings are canceled. We will resume our weekly meetings on Thursday, Nov 7. Get those Icehouse blueprints filed and in shape in the meantime! Thanks, Oops, we will resume on the *14* of November, not the

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Daniel P. Berrange
On Wed, Oct 30, 2013 at 04:20:34AM -0400, Russell Bryant wrote: On 10/30/2013 03:13 AM, Alex Glikson wrote: Maybe a more appropriate approach could be to have a tool/script that does it, as a one time thing. For example, it could make sense in a scenario when Nova DB gets lost or

Re: [openstack-dev] [Cinder] Propose Jay Bryant for core

2013-10-30 Thread Duncan Thomas
+1 On 29 October 2013 20:54, John Griffith john.griff...@solidfire.com wrote: Hey, I wanted to propose Jay Bryant (AKA jsbryant, AKA jungleboy, AKA :) ) for core membership on the Cinder team. Jay has been working on Cinder for a while now and has really shown some dedication and

Re: [openstack-dev] extending nova boot

2013-10-30 Thread Drew Fisher
I hate to be that guy but I have to bump this thread to try to get answer. Can anybody help me out? On 10/28/13 4:06 PM, Drew Fisher wrote: Chris and Phil, Thanks for the clue on using scheduler_hints as a template. I've implemented a V2 API version of my extension to get started (for

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Mike Spreitzer
Swapnil Kulkarni swapnilkulkarni2...@gmail.com wrote on 10/30/2013 02:36:37 AM: I had a discussion with russellb regarding this for yesterday, I would like to discuss this with the team regarding the blueprint mentioned in subject.

Re: [openstack-dev] Revisiting current column number limit in code

2013-10-30 Thread Lyle, David
-Original Message- From: Flavio Percoco [mailto:fla...@redhat.com] Sent: Wednesday, October 30, 2013 8:25 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Revisiting current column number limit in code On 30/10/13 07:22 -0400, Sean

Re: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova

2013-10-30 Thread Eddie Sheffield
Mark Washenberger mark.washenber...@markwash.net said: ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I am not a fan of all the specific talk to glance code we

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Mike Spreitzer
Daniel P. Berrange berra...@redhat.com wrote on 10/30/2013 12:38:21 PM: ... This avoids any need to deal with the hard problems of adopting arbitrary VMs. Sorry, my writing was unclear. I did not mean another use case for adopting VMs; I mean another use case for VM discovery. Regards,

Re: [openstack-dev] [Nova] Blueprint review process

2013-10-30 Thread Stefano Maffulli
On Wed 30 Oct 2013 03:29:32 AM PDT, Thierry Carrez wrote: (1) Rating blueprints low priority doesn't mean they won't make it. It means we have no idea if they will make it. Maybe the proposer doesn't have a proven track record of hitting promised deadlines, maybe we don't have core reviewers

Re: [openstack-dev] [nova][scheduler] Instance Group Model and APIs - Updated document with an example request payload

2013-10-30 Thread Mike Spreitzer
Alex Glikson glik...@il.ibm.com wrote on 10/30/2013 02:26:08 AM: Mike Spreitzer mspre...@us.ibm.com wrote on 30/10/2013 06:11:04 AM: Date: 30/10/2013 06:12 AM Alex also wrote: ``I wonder whether it is possible to find an approach that takes into account cross-resource placement

Re: [openstack-dev] [TripleO] TripleO core reviewer update - november

2013-10-30 Thread Derek Higgins
On 30/10/13 09:06, Robert Collins wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with -core responsibilities. In this months

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

2013-10-30 Thread Brad Topol
+1! Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Adam Young ayo...@redhat.com To: openstack-dev@lists.openstack.org Date: 10/30/2013 11:13 AM Subject:Re: [openstack-dev]

[openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Clint Byrum
So, recently we've had quite a long thread in gerrit regarding locking in Heat: https://review.openstack.org/#/c/49440/ In the patch, there are two distributed lock drivers. One uses SQL, and suffers from all the problems you might imagine a SQL based locking system would. It is extremely hard

[openstack-dev] [nova] [neutron] #openstack IRC meeting UTC 1300 Friday on PCI pass-through network support

2013-10-30 Thread Robert Li (baoli)
Hi, Let's have a meeting with the #openstack IRC channel at UTC 1300 Friday. Based on our email discussions so far, I listed the topics in below: -- physical network binding -- nova/neutron APIs to support SRIOV -- PCI Alias thanks, Robert

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Georgy Okrokvertskhov
Hi Clint, I think you rose a point here. We implemented distributed engine in Murano without locking mechanism by keeping state consistent on each step. We extracted this engine from Murano and plan to put it as a part of Mistral project for task management and execution. Working Mistral

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Alex Glikson
There is a ZK-backed driver in Nova service heartbeat mechanism ( https://blueprints.launchpad.net/nova/+spec/zk-service-heartbeat) -- would be interesting to know whether it is widely used (might be worth asking at the general ML, or user groups). There have been also discussions on using it

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Steven Dake
On 10/30/2013 10:42 AM, Clint Byrum wrote: So, recently we've had quite a long thread in gerrit regarding locking in Heat: https://review.openstack.org/#/c/49440/ In the patch, there are two distributed lock drivers. One uses SQL, and suffers from all the problems you might imagine a SQL based

Re: [openstack-dev] [TripleO] TripleO core reviewer update - november

2013-10-30 Thread Joe Gordon
On Oct 30, 2013 9:10 AM, Robert Collins robe...@robertcollins.net wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with -core

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Mike Spreitzer
Clint Byrum cl...@fewbar.com wrote on 10/30/2013 01:42:53 PM: ... The engine should store _all_ of its state in a distributed data store of some kind. Any engine should be aware of what is already happening with the stack from this state and act accordingly. That includes the engine

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Joshua Harlow
For taskflow usage/details: https://wiki.openstack.org/wiki/TaskFlow Let me know if the documentation there is not sufficient about defining who its useful so that I can make it more clear (to resolve the 'versed on TaskFlow's details' part). As I have tried to define the use-cases that it can

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Robert Collins
On 31 October 2013 06:42, Clint Byrum cl...@fewbar.com wrote: So, recently we've had quite a long thread in gerrit regarding locking in Heat: https://review.openstack.org/#/c/49440/ In the patch, there are two distributed lock drivers. One uses SQL, and suffers from all the problems you

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Joshua Harlow
So afaik hbase recommends. http://hbase.apache.org/book/zk.sasl.auth.html It doesn't integrate with keystone, but that¹s expected ;) -Josh On 10/30/13 11:25 AM, Robert Collins robe...@robertcollins.net wrote: On 31 October 2013 06:42, Clint Byrum cl...@fewbar.com wrote: So, recently we've

Re: [openstack-dev] [TripleO] TripleO core reviewer update - november

2013-10-30 Thread Jordan OMara
On 30/10/13 18:16 +, Joe Gordon wrote: On Oct 30, 2013 9:10 AM, Robert Collins robe...@robertcollins.net wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing

[openstack-dev] [Solum] An early peek into the Solum.io website

2013-10-30 Thread Roshan Agrawal
The Solum community website is very close to be launched publicly. If you want to take an early peek into how it is coming along, here are the access details: www.Solum.iohttp://www.Solum.io User name: Solum, password: OpenStack The Solum logo is still in works, what we have now is meant to be a

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Joshua Harlow
As for the mutex and locking and all that problem. I would expect locking to be a necessity at some point for openstack. Even if the state transitions are the locks themselves (that¹s still a lock by another name imho) and u need a reliable way to store and change those state transitions (aka

[openstack-dev] [Solum] Solum transitioned to openstack-dev

2013-10-30 Thread Adrian Otto
Hi, The Solum team has agreed[1] to use openstack-dev, and has closed its project-specific mailing list. We look forward to discussing ongoing design and development efforts here. We are also transitioning to an openstack meeting channel for subsequent public meetings. Regards, Adrian Otto

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Tim Daly
On Oct 30, 2013, at 11:11 AM, Alex Glikson glik...@il.ibm.com wrote: There is a ZK-backed driver in Nova service heartbeat mechanism (https://blueprints.launchpad.net/nova/+spec/zk-service-heartbeat) -- would be interesting to know whether it is widely used (might be worth asking at the

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Sandy Walsh
On 10/30/2013 03:10 PM, Steven Dake wrote: I will -2 any patch that adds zookeeper as a dependency to Heat. Certainly any distributed locking solution should be plugin based and optional. Just as a database-oriented solution could be the default plugin. Re: the Java issue, we already have

Re: [openstack-dev] [Solum] Solum transitioned to openstack-dev

2013-10-30 Thread Clayton Coleman
- Original Message - Hi, The Solum team has agreed[1] to use openstack-dev, and has closed its project-specific mailing list. We look forward to discussing ongoing design and development efforts here. We are also transitioning to an openstack meeting channel for subsequent public

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Jay Pipes
Has anyone looked into using concoord for distributed locking? https://pypi.python.org/pypi/concoord Best, -jay On 10/30/2013 02:39 PM, Joshua Harlow wrote: So my idea here was that to break the abstraction for heat into 3 parts. Pardon my lack of heat terminology/knowledge if I miss

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Qing He
Has anyone looked at any lock-free solution? -Original Message- From: Sandy Walsh [mailto:sandy.wa...@rackspace.com] Sent: Wednesday, October 30, 2013 12:20 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey On

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Clint Byrum
Excerpts from Joshua Harlow's message of 2013-10-30 11:57:30 -0700: As for the mutex and locking and all that problem. I would expect locking to be a necessity at some point for openstack. Even if the state transitions are the locks themselves (that¹s still a lock by another name imho) and

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Joshua Harlow
To me u just made state consistency be a lock by another name. A lock protects a region of code from being mutually accessed, u can do the same with state consistency. In the end though u need some reliable transactional consistent storage (a database, zookeeper, other) to store that state

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

2013-10-30 Thread Lakshminaraya Renganarayana
Zane, thanks very much for the detailed feedback. I have added my comments inline. Zane Bitter zbit...@redhat.com wrote on 10/29/2013 08:46:21 AM: ... As brief feedback on these suggestions: E1: Probably +1 for inputs, but tentative -1 for attributes. I'm not sure we can check anything useful

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Sandy Walsh
Doh, sorry, left out the important part I had originally intended. The ZK unit tests could be split to not run by default, but if you're a ZK shop ... run them yourself. They might not be included in the gerrit tests, but should be the nature with heavy-weight drivers. We need to do more of this

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Robert Collins
On 31 October 2013 08:37, Sandy Walsh sandy.wa...@rackspace.com wrote: Doh, sorry, left out the important part I had originally intended. The ZK unit tests could be split to not run by default, but if you're a ZK shop ... run them yourself. They might not be included in the gerrit tests, but

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Joshua Harlow
+1 ;) On 10/30/13 12:37 PM, Clint Byrum cl...@fewbar.com wrote: Excerpts from Joshua Harlow's message of 2013-10-30 11:57:30 -0700: As for the mutex and locking and all that problem. I would expect locking to be a necessity at some point for openstack. Even if the state transitions are

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

2013-10-30 Thread Mike Spreitzer
Lakshminaraya Renganarayana/Watson/IBM@IBMUS wrote on 10/30/2013 03:35:32 PM: Zane Bitter zbit...@redhat.com wrote on 10/29/2013 08:46:21 AM: ... In this method (i.e. option (2) above) shouldn't we be building the dependency graph in Heat rather than running through them sequentially

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Chris Friesen
On 10/30/2013 01:34 PM, Joshua Harlow wrote: To me u just made state consistency be a lock by another name. A lock protects a region of code from being mutually accessed Personally I view a lock as protecting a set of data from being mutually accessed. The question to me becomes what

Re: [openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

2013-10-30 Thread Sandy Walsh
On 10/30/2013 04:44 PM, Robert Collins wrote: On 31 October 2013 08:37, Sandy Walsh sandy.wa...@rackspace.com wrote: Doh, sorry, left out the important part I had originally intended. The ZK unit tests could be split to not run by default, but if you're a ZK shop ... run them yourself. They

[openstack-dev] Proposal for the new service: MagnetoDB, DynamoDB API implementation for OpenStack

2013-10-30 Thread Ilya Sviridov
Hi, Openstackers I would like to propose a new initiative to implement AWS DynamoDB API for OpenStack. I believe this is a right moment for OpenStack community to start MagnetoDB discussion and design around such service as more data processing and management services, such as Savanna and Trove,

[openstack-dev] [savanna] team meeting Oct 31 1800 UTC

2013-10-30 Thread Sergey Lukjanov
Hi folks, We'll be having the Savanna team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_October.2C_31 http://www.timeanddate.com/worldclock/fixedtime.html?msg=Savanna+Meetingiso=20131031T18 P.S. The Nov 7

Re: [openstack-dev] [OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack for existing workload

2013-10-30 Thread Alan Kavanagh
Sorry Russell but I have to ask, what is the different you see between traditional datacenter virtualization and cloud. IMHO the two co-exist and Cloud (the buzz word that it is) is the umbrella for all encompassing data center. That said im still missing why this would not be a useful feature

Re: [openstack-dev] [Solum] Solum transitioned to openstack-dev

2013-10-30 Thread Clint Byrum
Excerpts from Adrian Otto's message of 2013-10-30 12:08:28 -0700: Hi, The Solum team has agreed[1] to use openstack-dev, and has closed its project-specific mailing list. We look forward to discussing ongoing design and development efforts here. We are also transitioning to an openstack

Re: [openstack-dev] [Heat] Comments on Steve Baker's Proposal on HOT Software Config

2013-10-30 Thread Zane Bitter
On 30/10/13 20:35, Lakshminaraya Renganarayana wrote: I'd like to see some more detail about how inputs/outputs would be exposed in the configuration management systems - or, more specifically, how the user can extend this to arbitrary configuration management systems. The way

[openstack-dev] [Solum] Separation of concerns for 0.1 git deploy blueprint

2013-10-30 Thread Clayton Coleman
In the IRC meeting yesterday [1] we discussed splitting the individual topics for the git deploy blueprint [2] into rough sub areas. To help frame the abstractions we've been discussing I roughed out a flow based on two user inputs, REST API create and a git push and then tried to draw boxes

[openstack-dev] Keystone Concurrency Races in SQL Assignment Backend

2013-10-30 Thread Peter Feiner
Hi Brant, In addition to the race you've fixed in https://review.openstack.org/#/c/50767/, it looks like there are quite a few more races in the SQL backend of keystone.assignment. I filed a bug to this effect: https://bugs.launchpad.net/keystone/+bug/1246489. The general problem is that

Re: [openstack-dev] [keystone] Support for external authentication (i.e. REMOTE_USER) in Havana

2013-10-30 Thread Álvaro López García
Hi Adam. On Wed 30 Oct 2013 (11:08), Adam Young wrote: On 10/30/2013 05:38 AM, Álvaro López García wrote: (...) Please take into account that external authentication and the REMOTE_USER stuff can be used without any federation at all. For example if an org is providing their users with

Re: [openstack-dev] [Solum] Solum transitioned to openstack-dev

2013-10-30 Thread Stefano Maffulli
On 10/30/2013 12:08 PM, Adrian Otto wrote: The Solum team has agreed[1] to use openstack-dev, and has closed its project-specific mailing list. Welcome. There is now also a topic on the Dev list: people can subscribe to receive only messages tagged [Solum] or [solum] in the subject. Cheers,

Re: [openstack-dev] [Solum] Solum transitioned to openstack-dev

2013-10-30 Thread Adrian Otto
Thanks Stef! I see the category listed here in my options: http://lists.openstack.org/cgi-bin/mailman/options/openstack-dev So, that's working. My concern is that the topic is listed as OpenStack Solum and should be listed as Solum because this project is not incubated, and should not use

Re: [openstack-dev] [Nova][Glance] Support of v1 and v2 glance APIs in Nova

2013-10-30 Thread Mark Washenberger
On Wed, Oct 30, 2013 at 9:04 AM, Eddie Sheffield eddie.sheffi...@rackspace.com wrote: Mark Washenberger mark.washenber...@markwash.net said: ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

  1   2   >