[openstack-dev] Cross-Project meeting, Tue December 9th, 21:00 UTC

2014-12-09 Thread Thierry Carrez
Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting Tuesday at 21:00 UTC, with the following agenda: * Convergence on specs process (johnthetubaguy) * Approval process differences * Path structure differences * specs.o.o aspect differences (toc)

Re: [openstack-dev] [Mistral] Query on creating multiple resources

2014-12-09 Thread Renat Akhmerov
Hey, I think it’s a question of what the final goal is. For just creating security groups as a resource I think Georgy and Zane are right, just use Heat. If the goal is to try Mistral or have this simple workflow as part of more complex then it’s totally fine to use Mistral. Sorry, I’m

Re: [openstack-dev] [Mistral] Query on creating multiple resources

2014-12-09 Thread Renat Akhmerov
No problem, let us know if you have any other questions. Renat Akhmerov @ Mirantis Inc. On 09 Dec 2014, at 11:57, Sushma Korati sushma_kor...@persistent.com wrote: Hi, Thank you guys. Yes I am able to do this with heat, but I faced issues while trying the same with mistral. As

Re: [openstack-dev] [Mistral] Event Subscription

2014-12-09 Thread Renat Akhmerov
Ok, got it. So my general suggestion here is: let's keep it as simple as possible for now, create something that works and then let’s see how to improve it. And yes, consumers may be and mostly will be 3rd parties. Thanks Renat Akhmerov @ Mirantis Inc. On 09 Dec 2014, at 08:25, W Chan

Re: [openstack-dev] [Mistral] Action context passed to all action executions by default

2014-12-09 Thread Renat Akhmerov
Hi Winson, I think it makes perfect sense. The reason I think is mostly historical and this can be reviewed now. Can you pls file a BP and describe your suggested design on that? I mean how we need to alter interface Action etc. Thanks Renat Akhmerov @ Mirantis Inc. On 09 Dec 2014, at

Re: [openstack-dev] Cross-Project meeting, Tue December 9th, 21:00 UTC

2014-12-09 Thread joehuang
Hi, If time is available, how about adding one agenda to guide the direction for cascading to move forward? Thanks in advance. The topic is : Need cross-program decision to run cascading as an incubated project mode or register BP separately in each involved project. CI for cascading is

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Roman Prykhodchenko
It is true that IPA and FuelAgent share a lot of functionality in common. However there is a major difference between them which is that they are intended to be used to solve a different problem. IPA is a solution for provision-use-destroy-use_by_different_user use-case and is really great for

Re: [openstack-dev] [Ironic] How to get past pxelinux.0 bootloader?

2014-12-09 Thread Peeyush Gupta
So, basically if I am using pxe driver, I would have to provide pxelinux.0? On 12/09/2014 03:24 PM, Fox, Kevin M wrote: You probably want to use the agent driver, not the pxe one. It lets you use bootloaders from the image. From: Peeyush Gupta Sent: Monday,

Re: [openstack-dev] Cross-Project meeting, Tue December 9th, 21:00 UTC

2014-12-09 Thread Thierry Carrez
joehuang wrote: If time is available, how about adding one agenda to guide the direction for cascading to move forward? Thanks in advance. The topic is : Need cross-program decision to run cascading as an incubated project mode or register BP separately in each involved project. CI for

[openstack-dev] [neutron] mid-cycle hot reviews

2014-12-09 Thread Miguel Ángel Ajo
Hi all! It would be great if you could use this thread to post hot reviews on stuff that it’s being worked out during the mid-cycle, where others from different timezones could participate. I know posting reviews to the list is not permitted, but I think an exception in this case would

Re: [openstack-dev] [horizon] REST and Django

2014-12-09 Thread Tihomir Trifonov
Sorry for the late reply, just few thoughts on the matter. IMO the REST middleware should be as thin as possible. And I mean thin in terms of processing - it should not do pre/post processing of the requests, but just unpack/pack. So here is an example: instead of making AJAX calls that contain

[openstack-dev] People of OpenStack (and their IRC nicks)

2014-12-09 Thread Matthew Gilliard
Sometimes, I want to ask the author of a patch about it on IRC. However, there doesn't seem to be a reliable way to find out someone's IRC handle. The potential for useful conversation is sometimes missed. Unless there's a better alternative which I didn't find,

Re: [openstack-dev] People of OpenStack (and their IRC nicks)

2014-12-09 Thread Nicolas Trangez
On Tue, 2014-12-09 at 10:46 +, Matthew Gilliard wrote: can we autogenerate it somehow? Maybe some 'irc_nick' field in Stackalytic's default_data.json could be added and used to populate such page? Nicolas ___ OpenStack-dev mailing list

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Vladimir Kozhukalov
Just a short explanation of Fuel use case. Fuel use case is not a cloud. Fuel is a deployment tool. We install OS on bare metal servers and on VMs and then configure this OS using Puppet. We have been using Cobbler as our OS provisioning tool since the beginning of Fuel. However, Cobbler assumes

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Yuriy Zveryanskyy
Good day Ironicers. I do not want to discuss questions like Is feature X good for release Y? or Is feature Z in Ironic scope or not?. I want to get an answer for this: Is Ironic a flexible, easy extendable and user-oriented solution for deployment? Yes, it is I think. IPA is the great

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sahid Orentino Ferdjaoui
On Tue, Dec 09, 2014 at 06:39:43AM -0500, Sean Dague wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes it tough to run locally. It also would be a

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Dmitry Tantsur
Hi folks, Thank you for additional explanation, it does clarify things a bit. I'd like to note, however, that you talk a lot about how _different_ Fuel Agent is from what Ironic does now. I'd like actually to know how well it's going to fit into what Ironic does (in additional to your

Re: [openstack-dev] Cross-Project meeting, Tue December 9th, 21:00 UTC

2014-12-09 Thread joehuang
Hello, Thierry, That sounds great. Best Regards Chaoyi Huang ( joehuang ) From: Thierry Carrez [thie...@openstack.org] Sent: 09 December 2014 18:32 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Cross-Project meeting, Tue December

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 07:32 AM, Sahid Orentino Ferdjaoui wrote: On Tue, Dec 09, 2014 at 06:39:43AM -0500, Sean Dague wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message,

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Julien Danjou
On Tue, Dec 09 2014, Sean Dague wrote: 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes it tough to run locally. It also would be a reason to prevent us from not rerunning tests on commit message changes (something we could do

Re: [openstack-dev] People of OpenStack (and their IRC nicks)

2014-12-09 Thread Jeremy Stanley
On 2014-12-09 13:58:28 +0100 (+0100), Sahid Orentino Ferdjaoui wrote: We probably don't want to maintain an other page of Wiki. Yes, the wiki is about low-overhead collaborative documentation. It is not suitable as a database. We can recommend in how to contribute to fill correctly the IRC

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

2014-12-09 Thread Daniel P. Berrange
On Tue, Dec 09, 2014 at 10:53:19AM +0100, Maxime Leroy wrote: I have also proposed a blueprint to have a new plugin mechanism in nova to load external vif driver. (nova-specs: https://review.openstack.org/#/c/136827/ and nova (rfc patch): https://review.openstack.org/#/c/136857/) From my

Re: [openstack-dev] [oslo.messaging][devstack] ZeroMQ driver maintenance next steps

2014-12-09 Thread Doug Hellmann
On Dec 8, 2014, at 11:25 PM, Li Ma skywalker.n...@gmail.com wrote: Hi all, I tried to deploy zeromq by devstack and it definitely failed with lots of problems, like dependencies, topics, matchmaker setup, etc. I've already registered a blueprint for devstack-zeromq [1]. I added the

[openstack-dev] [neutron] Spec reviews this week by the neutron-drivers team

2014-12-09 Thread Kyle Mestery
The neutron-drivers team has started the process of both accepting and rejecting specs for Kilo now. If you've submitted a spec, you will soon see the spec either approved or land in either the abandoned or -2 category. We're doing our best to put helpful messages when we do abandon or -2 specs,

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Doug Hellmann
On Dec 9, 2014, at 6:39 AM, Sean Dague s...@dague.net wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes it tough to run locally. It also would

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Vladimir Kozhukalov
Vladimir Kozhukalov On Tue, Dec 9, 2014 at 3:51 PM, Dmitry Tantsur dtant...@redhat.com wrote: Hi folks, Thank you for additional explanation, it does clarify things a bit. I'd like to note, however, that you talk a lot about how _different_ Fuel Agent is from what Ironic does now. I'd like

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Vladimir Kozhukalov
s/though/throw/g Vladimir Kozhukalov On Tue, Dec 9, 2014 at 5:40 PM, Vladimir Kozhukalov vkozhuka...@mirantis.com wrote: Vladimir Kozhukalov On Tue, Dec 9, 2014 at 3:51 PM, Dmitry Tantsur dtant...@redhat.com wrote: Hi folks, Thank you for additional explanation, it does clarify

Re: [openstack-dev] [oslo.messaging][devstack] ZeroMQ driver maintenance next steps

2014-12-09 Thread ozamiatin
+1 To wiki page. I also tried to deploy devstack with zmq, and met the same problems https://bugs.launchpad.net/devstack/+bug/1397999 https://bugs.launchpad.net/oslo.messaging/+bug/1395721 We also have some unimplemented closures in zmq driver: one of them:

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Dmitry Tantsur
On 12/09/2014 03:40 PM, Vladimir Kozhukalov wrote: Vladimir Kozhukalov On Tue, Dec 9, 2014 at 3:51 PM, Dmitry Tantsur dtant...@redhat.com mailto:dtant...@redhat.com wrote: Hi folks, Thank you for additional explanation, it does clarify things a bit. I'd like to note, however,

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Jim Rollenhagen
On Tue, Dec 09, 2014 at 04:01:07PM +0400, Vladimir Kozhukalov wrote: Just a short explanation of Fuel use case. Fuel use case is not a cloud. Fuel is a deployment tool. We install OS on bare metal servers and on VMs and then configure this OS using Puppet. We have been using Cobbler as our

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 09:11 AM, Doug Hellmann wrote: On Dec 9, 2014, at 6:39 AM, Sean Dague s...@dague.net wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Chmouel Boudjnah
On Tue, Dec 9, 2014 at 12:39 PM, Sean Dague s...@dague.net wrote: 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes it tough to run locally. I do run them locally using git-review custom script features which would launch a flake8

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Monty Taylor
On 12/09/2014 03:39 AM, Sean Dague wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes it tough to run locally. It also would be a reason to prevent

[openstack-dev] [Third-party] Voting for new Third-party CI weekly IRC meeting time

2014-12-09 Thread Kurt Taylor
All of the feedback so far has supported moving the existing IRC Third-party CI meeting to better fit a worldwide audience. The consensus is that we will have only 1 meeting per week at alternating times. You can see examples of other teams with alternating meeting times at:

[openstack-dev] [Nova] question about Get Guest Info row in HypervisorSupportMatrix

2014-12-09 Thread Dmitry Guryanov
Hello! There is a feature in HypervisorSupportMatrix (https://wiki.openstack.org/wiki/HypervisorSupportMatrix) called Get Guest Info. Does anybody know, what does it mean? I haven't found anything like this neither in nova api nor in horizon and nova command line. -- Thanks, Dmitry Guryanov

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Yuriy Zveryanskyy
On 12/09/2014 05:00 PM, Jim Rollenhagen wrote: On Tue, Dec 09, 2014 at 04:01:07PM +0400, Vladimir Kozhukalov wrote: Just a short explanation of Fuel use case. Fuel use case is not a cloud. Fuel is a deployment tool. We install OS on bare metal servers and on VMs and then configure this OS

[openstack-dev] new library oslo.context released

2014-12-09 Thread Doug Hellmann
The Oslo team is pleased to announce the release of oslo.context 0.1.0. This is the first version of oslo.context, the library containing the base class for the request context object. This is a relatively small module, but we’ve placed it in a separate library so oslo.messaging and oslo.log

[openstack-dev] Hyper-V Meeting Canceled for Today

2014-12-09 Thread Peter Pouliot
Hi All, I'm canceling the hyper-v meeting today due to a conflicting shedules, we will resume next week. Peter J. Pouliot CISSP Microsoft Enterprise Cloud Solutions C:\OpenStack New England Research Development Center 1 Memorial Drive Cambridge, MA 02142 P: 1.(857).4536436 E:

Re: [openstack-dev] [Keystone] OSAAA-Policy

2014-12-09 Thread Brad Topol
+1! Makes sense. --Brad Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Morgan Fainberg morgan.fainb...@gmail.com To: Adam Young ayo...@redhat.com, OpenStack Development Mailing List

Re: [openstack-dev] [cinder] HA issues

2014-12-09 Thread Dulko, Michal
And what about no recovery in case of failure mid-task? I can see that there's some TaskFlow integration done. This lib seems to address these issues (if used with taskflow.persistent submodule, which Cinder isn't using). Any plans for further integration with TaskFlow? -Original

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Brian Curtin
On Tue, Dec 9, 2014 at 9:05 AM, Sean Dague s...@dague.net wrote: - [H305 H306 H307] Organize your imports according to the `Import order template`_ and `Real-world Import Order Examples`_ below. I think these remain reasonable guidelines, but H302 is exceptionally tricky to get right, and

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Vladimir Kozhukalov
We assume next step will be to put provision data (disk partition scheme, maybe other data) into driver_info and make Fuel Agent driver able to serialize those data (special format) and implement a corresponding data driver in Fuel Agent for this format. Again very simple. Maybe it is time to

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 11:15 AM, Brian Curtis wrote: On Tue, Dec 9, 2014 at 9:05 AM, Sean Dague s...@dague.net wrote: - [H305 H306 H307] Organize your imports according to the `Import order template`_ and `Real-world Import Order Examples`_ below. I think these remain reasonable guidelines, but H302

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Jeremy Stanley
On 2014-12-09 07:29:31 -0800 (-0800), Monty Taylor wrote: I DO like something warning about commit subject length ... but maybe that should be a git-review function or something. [...] How about a hook in Gerrit to refuse commits based on some simple (maybe even project-specific) rules? --

Re: [openstack-dev] [Keystone] OSAAA-Policy

2014-12-09 Thread Adam Young
On 12/09/2014 10:57 AM, Brad Topol wrote: +1! Makes sense. --Brad Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Morgan Fainberg morgan.fainb...@gmail.com To: Adam Young

Re: [openstack-dev] [cinder] HA issues

2014-12-09 Thread Duncan Thomas
There are some significant limitations to the pure taskflow approach, however some combination of atomic micro-state management and taskflow persistence is being looked at Duncan Thomas On Dec 9, 2014 6:24 PM, Dulko, Michal michal.du...@intel.com wrote: And what about no recovery in case of

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Johannes Erdfelt
On Tue, Dec 09, 2014, Sean Dague s...@dague.net wrote: This check should run on any version of python and give the same results. It does not, because it queries python to know what's in stdlib vs. not. Just to underscore that it's difficult to get right, I found out recently that hacking

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Matthew Treinish
On Tue, Dec 09, 2014 at 10:15:34AM -0600, Brian Curtin wrote: On Tue, Dec 9, 2014 at 9:05 AM, Sean Dague s...@dague.net wrote: - [H305 H306 H307] Organize your imports according to the `Import order template`_ and `Real-world Import Order Examples`_ below. I think these remain

Re: [openstack-dev] [Neutron] Core/Vendor code decomposition

2014-12-09 Thread Salvatore Orlando
I would like to chime into this discussion wearing my plugin developer hat. We (the VMware team) have looked very carefully at the current proposal for splitting off drivers and plugins from the main source code tree. Therefore the concerns you've heard from Gary are not just ramblings but are

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Johannes Erdfelt
On Tue, Dec 09, 2014, Sean Dague s...@dague.net wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes it tough to run locally. It also would be a

Re: [openstack-dev] [Nova] question about Get Guest Info row in HypervisorSupportMatrix

2014-12-09 Thread Daniel P. Berrange
On Tue, Dec 09, 2014 at 06:33:47PM +0300, Dmitry Guryanov wrote: Hello! There is a feature in HypervisorSupportMatrix (https://wiki.openstack.org/wiki/HypervisorSupportMatrix) called Get Guest Info. Does anybody know, what does it mean? I haven't found anything like this neither in nova

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 11:41 AM, Johannes Erdfelt wrote: On Tue, Dec 09, 2014, Sean Dague s...@dague.net wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 11:28 AM, Jeremy Stanley wrote: On 2014-12-09 07:29:31 -0800 (-0800), Monty Taylor wrote: I DO like something warning about commit subject length ... but maybe that should be a git-review function or something. [...] How about a hook in Gerrit to refuse commits based on some

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Kevin L. Mitchell
On Tue, 2014-12-09 at 10:05 -0500, Sean Dague wrote: Sure, the H8* group is git commit messages. It's checking for line length in the commit message. I agree the H8* group should be dropped. It would be appropriate to create a new gate check job that validated that, but it should not be part

Re: [openstack-dev] [Keystone] OSAAA-Policy

2014-12-09 Thread Morgan Fainberg
On December 9, 2014 at 10:43:51 AM, Adam Young (ayo...@redhat.com) wrote: On 12/09/2014 10:57 AM, Brad Topol wrote: +1!  Makes sense. --Brad Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet:  bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From:  

Re: [openstack-dev] [all] Deprecating exceptions

2014-12-09 Thread Jeremy Stanley
On 2014-12-09 16:50:48 +0100 (+0100), Jakub Ruzicka wrote: On 22.9.2014 17:24, Ihar Hrachyshka wrote: [...] Aren't clients supposed to be backwards compatible? Isn't it the exact reason why we don't maintain stable branches for client modules? Supposed, yes. However, it's not

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 11:58 AM, Kevin L. Mitchell wrote: On Tue, 2014-12-09 at 10:05 -0500, Sean Dague wrote: Sure, the H8* group is git commit messages. It's checking for line length in the commit message. I agree the H8* group should be dropped. It would be appropriate to create a new gate check

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Jeremy Stanley
On 2014-12-09 11:56:54 -0500 (-0500), Sean Dague wrote: Honestly, any hard rejection ends up problematic. For instance, it means it's impossible to include actual urls in commit messages to reference things without a url shortener much of the time. Fair enough. I think this makes it a human

[openstack-dev] [Nova] question about Get Guest Info row in HypervisorSupportMatrix

2014-12-09 Thread Markus Zoeller
On Tue, Dec 09, 2014 at 06:33:47PM +0300, Dmitry Guryanov wrote: Hello! There is a feature in HypervisorSupportMatrix (https://wiki.openstack.org/wiki/HypervisorSupportMatrix) called Get Guest Info. Does anybody know, what does it mean? I haven't found anything like this

[openstack-dev] [oslo][Keystone] Policy graduation

2014-12-09 Thread Morgan Fainberg
I would like to propose that we keep the policy library under the oslo program. As with other graduated projects we will maintain a core team (that while including the oslo-core team) will be comprised of the expected individuals from the Identity and other security related teams. The change

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Kevin L. Mitchell
On Tue, 2014-12-09 at 12:05 -0500, Sean Dague wrote: I agree that dropping H302 and the grouping checks makes sense. I think we should keep the H301, H303, H304, and the basic ordering checks, however; it doesn't seem to me that these would be that difficult to implement or maintain.

Re: [openstack-dev] [oslo][Keystone] Policy graduation

2014-12-09 Thread Adam Young
On 12/09/2014 12:18 PM, Morgan Fainberg wrote: I would like to propose that we keep the policy library under the oslo program. As with other graduated projects we will maintain a core team (that while including the oslo-core team) will be comprised of the expected individuals from the Identity

Re: [openstack-dev] [Neutron] Core/Vendor code decomposition

2014-12-09 Thread Armando M.
On 9 December 2014 at 09:41, Salvatore Orlando sorla...@nicira.com wrote: I would like to chime into this discussion wearing my plugin developer hat. We (the VMware team) have looked very carefully at the current proposal for splitting off drivers and plugins from the main source code tree.

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Doug Hellmann
On Dec 9, 2014, at 10:05 AM, Sean Dague s...@dague.net wrote: On 12/09/2014 09:11 AM, Doug Hellmann wrote: On Dec 9, 2014, at 6:39 AM, Sean Dague s...@dague.net wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Yuriy Zveryanskyy
Vladimir, IMO there is more global problem. Anyone who wants to use baremetal deploy service should resolve problems with power management, PXE/iPXE support, DHCP, etc. Or he/she can use Ironic. User has his own vision of deploy workflow and features needed for it. He hears from Ironic people:

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Fox, Kevin M
We've been interested in Ironic as a replacement for Cobbler for some of our systems and have been kicking the tires a bit recently. While initially I thought this thread was probably another Fuel not playing well with the community kind of thing, I'm not thinking that any more. Its deeper

Re: [openstack-dev] [Neutron] Core/Vendor code decomposition

2014-12-09 Thread Salvatore Orlando
On 9 December 2014 at 17:32, Armando M. arma...@gmail.com wrote: On 9 December 2014 at 09:41, Salvatore Orlando sorla...@nicira.com wrote: I would like to chime into this discussion wearing my plugin developer hat. We (the VMware team) have looked very carefully at the current proposal

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Vladimir Kozhukalov
Kevin, Just to make sure everyone understands what Fuel Agent is about. Fuel Agent is agnostic to image format. There are 3 possibilities for image format 1) DISK IMAGE contains GPT/MBR table and all partitions and metadata in case of md or lvm. That is just something like what you get when run

[openstack-dev] [Keystone] No Meeting Today

2014-12-09 Thread Morgan Fainberg
This is a quick note that the Keystone team will not be holding a meeting today. Based upon last week’s meeting the goals for today are to review open specs[1] and blocking code reviews for the k1 milestone[2] instead. We will continue with the normal meeting schedule next week. [1] 

Re: [openstack-dev] [Mistral]

2014-12-09 Thread Nikolay Makhotkin
Guys, May be I misunderstood something here but what is the difference between this one and https://blueprints.launchpad.net/mistral/+spec/mistral-execution-environment ? On Tue, Dec 9, 2014 at 5:35 PM, Dmitri Zimine dzim...@stackstorm.com wrote: Winson, thanks for filing the blueprint:

Re: [openstack-dev] [cinder] Code pointer for processing cinder backend config

2014-12-09 Thread Mike Perez
On 09:36 Sat 06 Dec , Pradip Mukhopadhyay wrote: Where this config info is getting parsed out in the cinder code? https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/netapp/options.py https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/netapp/common.py#L76

[openstack-dev] [neutron] Tap-aaS Spec for Kilo

2014-12-09 Thread Anil Rao
Hi, The latest version of the Tap-aaS spec is available at: https://review.openstack.org/#/c/140292/ It was uploaded last night and we are hoping that it will be considered as a candidate for the Kilo release. Thanks, Anil ___ OpenStack-dev mailing

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

2014-12-09 Thread Maru Newby
On Dec 9, 2014, at 7:04 AM, Daniel P. Berrange berra...@redhat.com wrote: On Tue, Dec 09, 2014 at 10:53:19AM +0100, Maxime Leroy wrote: I have also proposed a blueprint to have a new plugin mechanism in nova to load external vif driver. (nova-specs: https://review.openstack.org/#/c/136827/

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Clint Byrum
Excerpts from Yuriy Zveryanskyy's message of 2014-12-09 04:05:03 -0800: Good day Ironicers. I do not want to discuss questions like Is feature X good for release Y? or Is feature Z in Ironic scope or not?. I want to get an answer for this: Is Ironic a flexible, easy extendable and

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 12:20 PM, Kevin L. Mitchell wrote: On Tue, 2014-12-09 at 12:05 -0500, Sean Dague wrote: I agree that dropping H302 and the grouping checks makes sense. I think we should keep the H301, H303, H304, and the basic ordering checks, however; it doesn't seem to me that these would be

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 12:07 PM, Jeremy Stanley wrote: On 2014-12-09 11:56:54 -0500 (-0500), Sean Dague wrote: Honestly, any hard rejection ends up problematic. For instance, it means it's impossible to include actual urls in commit messages to reference things without a url shortener much of the time.

[openstack-dev] [hacking] hacking package upgrade dependency with setuptools

2014-12-09 Thread Surojit Pathak
Hi all, On a RHEL system, as I upgrade hacking package from 0.8.0 to 0.9.5, I see flake8 stops working. Upgrading setuptools resolves the issue. But I do not see a change in version for pep8 or setuptools, with the upgrade in setuptools. Any issue in packaging? Any explanation of this

Re: [openstack-dev] [neutron] mid-cycle hot reviews

2014-12-09 Thread Carl Baldwin
On Tue, Dec 9, 2014 at 3:33 AM, Miguel Ángel Ajo majop...@redhat.com wrote: Hi all! It would be great if you could use this thread to post hot reviews on stuff that it’s being worked out during the mid-cycle, where others from different timezones could participate. I think we've used the

Re: [openstack-dev] People of OpenStack (and their IRC nicks)

2014-12-09 Thread Stefano Maffulli
On 12/09/2014 06:04 AM, Jeremy Stanley wrote: We already have a solution for tracking the contributor-IRC mapping--add it to your Foundation Member Profile. For example, mine is in there already: http://www.openstack.org/community/members/profile/5479 I recommend updating the

Re: [openstack-dev] [oslo][Keystone] Policy graduation

2014-12-09 Thread Doug Hellmann
On Dec 9, 2014, at 12:18 PM, Morgan Fainberg morgan.fainb...@gmail.com wrote: I would like to propose that we keep the policy library under the oslo program. As with other graduated projects we will maintain a core team (that while including the oslo-core team) will be comprised of the

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Jeremy Stanley
On 2014-12-09 13:49:00 -0500 (-0500), Sean Dague wrote: [...] And I also think that if a commit message change doesn't retrigger all the tests, people will be a lot happier updating them. Agreed--though this will need a newer Gerrit plus a new feature in Zuul so it recognizes the difference in

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Sean Dague
On 12/09/2014 02:46 PM, Jeremy Stanley wrote: On 2014-12-09 13:49:00 -0500 (-0500), Sean Dague wrote: [...] And I also think that if a commit message change doesn't retrigger all the tests, people will be a lot happier updating them. Agreed--though this will need a newer Gerrit plus a new

[openstack-dev] [oslo] updated instructions for creating a library repository

2014-12-09 Thread Doug Hellmann
Now that the infra manual includes the “Project Creator’s Guide”, I have updated our wiki page to refer to it. I could use a sanity check to make sure I don’t have things in a bad order. If you have a few minutes to help with that, please look over

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Devananda van der Veen
Thank you for explaining in detail what Fuel's use case is. I was lacking this information, and taking the FuelAgent proposal in isolation. Allow me to respond to several points inline... On Tue Dec 09 2014 at 4:08:45 AM Vladimir Kozhukalov vkozhuka...@mirantis.com wrote: Just a short

Re: [openstack-dev] [Nova] question about Get Guest Info row in HypervisorSupportMatrix

2014-12-09 Thread Daniel P. Berrange
On Tue, Dec 09, 2014 at 06:15:01PM +0100, Markus Zoeller wrote: On Tue, Dec 09, 2014 at 06:33:47PM +0300, Dmitry Guryanov wrote: Hello! There is a feature in HypervisorSupportMatrix (https://wiki.openstack.org/wiki/HypervisorSupportMatrix) called Get Guest Info. Does

Re: [openstack-dev] [Mistral] Query on creating multiple resources

2014-12-09 Thread Zane Bitter
On 09/12/14 03:48, Renat Akhmerov wrote: Hey, I think it’s a question of what the final goal is. For just creating security groups as a resource I think Georgy and Zane are right, just use Heat. If the goal is to try Mistral or have this simple workflow as part of more complex then it’s

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

2014-12-09 Thread Kevin L. Mitchell
On Tue, 2014-12-09 at 13:46 -0500, Sean Dague wrote: Yes, the following fails H305 and H306. nova/tests/fixtures.py Fixtures for Nova tests. from __future__ import absolute_import import gettext import logging import os import uuid import fixtures from oslo.config import cfg

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Devananda van der Veen
On Tue Dec 09 2014 at 7:49:32 AM Yuriy Zveryanskyy yzveryans...@mirantis.com wrote: On 12/09/2014 05:00 PM, Jim Rollenhagen wrote: On Tue, Dec 09, 2014 at 04:01:07PM +0400, Vladimir Kozhukalov wrote: Many many various cases are possible. If you ask why we'd like to support all those

Re: [openstack-dev] [Neutron] Core/Vendor code decomposition

2014-12-09 Thread Ivar Lazzaro
I agree with Salvatore that the split is not an easy thing to achieve for vendors, and I would like to bring up my case to see if there are ways to make this at least a bit simpler. At some point I had the need to backport vendor code from Juno to Icehouse (see first attempt here [0]). That in

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Devananda van der Veen
On Tue Dec 09 2014 at 10:13:52 AM Vladimir Kozhukalov vkozhuka...@mirantis.com wrote: Kevin, Just to make sure everyone understands what Fuel Agent is about. Fuel Agent is agnostic to image format. There are 3 possibilities for image format 1) DISK IMAGE contains GPT/MBR table and all

Re: [openstack-dev] [hacking] hacking package upgrade dependency with setuptools

2014-12-09 Thread Joe Gordon
On Tue, Dec 9, 2014 at 11:05 AM, Surojit Pathak suro.p...@gmail.com wrote: Hi all, On a RHEL system, as I upgrade hacking package from 0.8.0 to 0.9.5, I see flake8 stops working. Upgrading setuptools resolves the issue. But I do not see a change in version for pep8 or setuptools, with the

Re: [openstack-dev] [qa] How to delete a VM which is in ERROR state?

2014-12-09 Thread Joe Gordon
On Sat, Dec 6, 2014 at 5:08 PM, Danny Choi (dannchoi) dannc...@cisco.com wrote: Hi, I have a VM which is in ERROR state. +--+--+++-++ | ID

Re: [openstack-dev] [Ironic] Fuel agent proposal

2014-12-09 Thread Devananda van der Veen
On Tue Dec 09 2014 at 9:45:51 AM Fox, Kevin M kevin@pnnl.gov wrote: We've been interested in Ironic as a replacement for Cobbler for some of our systems and have been kicking the tires a bit recently. While initially I thought this thread was probably another Fuel not playing well with

Re: [openstack-dev] [keystone][all] Max Complexity Check Considered Harmful

2014-12-09 Thread Joe Gordon
On Mon, Dec 8, 2014 at 5:03 PM, Brant Knudson b...@acm.org wrote: Not too long ago projects added a maximum complexity check to tox.ini, for example keystone has max-complexity=24. Seemed like a good idea at the time, but in a recent attempt to lower the maximum complexity check in

Re: [openstack-dev] [nova][docker][containers][qa] nova-docker CI failing a lot on unrelated nova patches

2014-12-09 Thread Joe Gordon
On Fri, Dec 5, 2014 at 11:43 AM, Ian Main im...@redhat.com wrote: Sean Dague wrote: On 12/04/2014 05:38 PM, Matt Riedemann wrote: On 12/4/2014 4:06 PM, Michael Still wrote: +Eric and Ian On Fri, Dec 5, 2014 at 8:31 AM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:

Re: [openstack-dev] [keystone][all] Max Complexity Check Considered Harmful

2014-12-09 Thread Angus Salkeld
On Wed, Dec 10, 2014 at 8:43 AM, Joe Gordon joe.gord...@gmail.com wrote: On Mon, Dec 8, 2014 at 5:03 PM, Brant Knudson b...@acm.org wrote: Not too long ago projects added a maximum complexity check to tox.ini, for example keystone has max-complexity=24. Seemed like a good idea at the

Re: [openstack-dev] [nova][docker][containers][qa] nova-docker CI failing a lot on unrelated nova patches

2014-12-09 Thread Eric Windisch
While gating on nova-docker will prevent patches that cause nova-docker to break 100% to land, it won't do a lot to prevent transient failures. To fix those we need people dedicated to making sure nova-docker is working. What would be helpful for me is a way to know that our tests are

Re: [openstack-dev] [NFV][Telco] pxe-boot

2014-12-09 Thread Joe Gordon
On Wed, Dec 3, 2014 at 1:16 AM, Pasquale Porreca pasquale.porr...@dektech.com.au wrote: The use case we were thinking about is a Network Function (e.g. IMS Nodes) implementation in which the high availability is based on OpenSAF. In this scenario there is an Active/Standby cluster of 2 System

Re: [openstack-dev] People of OpenStack (and their IRC nicks)

2014-12-09 Thread Angus Salkeld
On Wed, Dec 10, 2014 at 5:11 AM, Stefano Maffulli stef...@openstack.org wrote: On 12/09/2014 06:04 AM, Jeremy Stanley wrote: We already have a solution for tracking the contributor-IRC mapping--add it to your Foundation Member Profile. For example, mine is in there already:

Re: [openstack-dev] [nova][docker][containers][qa] nova-docker CI failing a lot on unrelated nova patches

2014-12-09 Thread Joe Gordon
On Tue, Dec 9, 2014 at 3:18 PM, Eric Windisch e...@windisch.us wrote: While gating on nova-docker will prevent patches that cause nova-docker to break 100% to land, it won't do a lot to prevent transient failures. To fix those we need people dedicated to making sure nova-docker is working.

  1   2   >