Re: [openstack-dev] [nova] Kilo specs review day

2014-12-11 Thread Sahid Orentino Ferdjaoui
On Thu, Dec 11, 2014 at 08:41:49AM +1100, Michael Still wrote: Hi, at the design summit we said that we would not approve specifications after the kilo-1 deadline, which is 18 December. Unfortunately, we’ve had a lot of specifications proposed this cycle (166 to my count), and haven’t kept

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

2014-12-11 Thread Maxime Leroy
On Thu, Dec 11, 2014 at 2:37 AM, henry hly henry4...@gmail.com wrote: On Thu, Dec 11, 2014 at 3:48 AM, Ian Wells ijw.ubu...@cack.org.uk wrote: [..] The problem is that we effectively prevent running an out of tree Neutron driver (which *is* perfectly legitimate) if it uses a VIF plugging

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread joehuang
Hello, Russell, Many thanks for your reply. See inline comments. -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: Thursday, December 11, 2014 5:22 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit

Re: [openstack-dev] [Ironic] Some questions about Ironic service

2014-12-11 Thread xianchaobo
Hi,Fox Kevin M Thanks for your help. Also,I want to know whether these features will be implemented in Ironic? Do we have a plan to implement them? Thanks Xianchaobo From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: Tuesday, December 09, 2014 5:52 PM To: OpenStack Development Mailing

Re: [openstack-dev] [Murano] Oslo.messaging error

2014-12-11 Thread Ekaterina Chernova
Hi! I recommend you to create separate user and password in Rabbit MQ and do not use 'quest' user. Don't forget to edit config file. I recommend you to go to our IRC channel #murano Freenode. We will help you to set up your environment step by step! Regards, Kate. On Thu, Dec 11, 2014 at 10:12

Re: [openstack-dev] [oslo] deprecation 'pattern' library??

2014-12-11 Thread Julien Danjou
On Wed, Dec 10 2014, Joshua Harlow wrote: […] Or in general any other comments/ideas about providing such a deprecation pattern library? +1 * debtcollector made me think of loanshark :) -- Julien Danjou -- Free Software hacker -- http://julien.danjou.info signature.asc Description:

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

2014-12-11 Thread Daniel P. Berrange
On Thu, Dec 11, 2014 at 09:37:31AM +0800, henry hly wrote: On Thu, Dec 11, 2014 at 3:48 AM, Ian Wells ijw.ubu...@cack.org.uk wrote: On 10 December 2014 at 01:31, Daniel P. Berrange berra...@redhat.com wrote: So the problem of Nova review bandwidth is a constant problem across all

Re: [openstack-dev] [neutron][sriov] PciDeviceRequestFailed error

2014-12-11 Thread Akilesh K
Hey guys sorry for the delayed reply. The problem was with the whitelist. I had whitelisted the id of the physical function instead of the virtual function. On Mon, Dec 8, 2014 at 9:33 AM, shihanzhang ayshihanzh...@126.com wrote: I think the problem is in nova, can you show your

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

2014-12-11 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 +100. I vote -1 there and would like to point out that we *must* keep history during the split, and split from u/s code base, not random repositories. If you don't know how to achieve this, ask oslo people, they did it plenty of times when

Re: [openstack-dev] Lack of quota - security bug or not?

2014-12-11 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/12/14 22:12, Jeremy Stanley wrote: On 2014-12-10 16:07:35 -0500 (-0500), Jay Pipes wrote: On 12/10/2014 04:05 PM, Jeremy Stanley wrote: I think the bigger question is whether the lack of a quota implementation for everything a tenant

Re: [openstack-dev] [Neutron] XenAPI questions

2014-12-11 Thread Bob Ball
Hi Yamamoto, XenAPI and Neutron do work well together, and we have an private CI that is running Neutron jobs. As it's not currently the public CI it's harder to access logs. We're working on trying to move the existing XenServer CI from a nova-network base to a neutron base, at which point

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

2014-12-11 Thread Gary Kotton
On 12/11/14, 12:50 PM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 +100. I vote -1 there and would like to point out that we *must* keep history during the split, and split from u/s code base, not random repositories. If you don't know how to

Re: [openstack-dev] Lack of quota - security bug or not?

2014-12-11 Thread George Shuklin
On 12/10/2014 10:34 PM, Jay Pipes wrote: On 12/10/2014 02:43 PM, George Shuklin wrote: I have some small discussion in launchpad: is lack of a quota for unprivileged user counted as security bug (or at least as a bug)? If user can create 100500 objects in database via normal API and ops have

[openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Anna Kamyshnikova
Hello everyone! In neutron there is a rather old bug [1] about adding uniqueness for security group name and tenant id. I found this idea reasonable and started working on fix for this bug [2]. I think it is good to add a uniqueconstraint because: 1) In nova there is such constraint for security

Re: [openstack-dev] [neutron] Services are now split out and neutron is open for commits!

2014-12-11 Thread Thierry Carrez
Kyle Mestery wrote: Folks, just a heads up that we have completed splitting out the services (FWaaS, LBaaS, and VPNaaS) into separate repositores. [1] [2] [3]. This was all done in accordance with the spec approved here [4]. Thanks to all involved, but a special thanks to Doug and Anita, as

Re: [openstack-dev] Lack of quota - security bug or not?

2014-12-11 Thread Thierry Carrez
George Shuklin wrote: On 12/10/2014 10:34 PM, Jay Pipes wrote: On 12/10/2014 02:43 PM, George Shuklin wrote: I have some small discussion in launchpad: is lack of a quota for unprivileged user counted as security bug (or at least as a bug)? If user can create 100500 objects in database

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

2014-12-11 Thread Murugan, Visnusaran
-Original Message- From: Zane Bitter [mailto:zbit...@redhat.com] Sent: Wednesday, December 10, 2014 11:17 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown You really need to get a real email client with quoting

Re: [openstack-dev] Lack of quota - security bug or not?

2014-12-11 Thread Clark, Robert Graham
On 11/12/2014 13:16, Thierry Carrez thie...@openstack.org wrote: George Shuklin wrote: On 12/10/2014 10:34 PM, Jay Pipes wrote: On 12/10/2014 02:43 PM, George Shuklin wrote: I have some small discussion in launchpad: is lack of a quota for unprivileged user counted as security bug (or at

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Jay Pipes
On 12/11/2014 07:22 AM, Anna Kamyshnikova wrote: Hello everyone! In neutron there is a rather old bug [1] about adding uniqueness for security group name and tenant id. I found this idea reasonable and started working on fix for this bug [2]. I think it is good to add a uniqueconstraint

[openstack-dev] [project-config][infra] Advanced way to run specific jobs against code changes

2014-12-11 Thread Denis Makogon
Good day Stackers. I’d like to raise question about implementing custom pipelines for Zuul. For those of you how’s pretty familiar with project-config and infra itself it wouldn’t be a news that for now Zuul layout supports only few pipelines types [1]

Re: [openstack-dev] [Ironic] Some questions about Ironic service

2014-12-11 Thread Fox, Kevin M
I would hope yes to all, but there is a lot of hard work there. Some things there require neutron to configure physical switches. Some require a guest agent in the image to get cinder working, or cinder controlled hardware. And all require developers interested enough in making it happen. No

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

2014-12-11 Thread Daniel P. Berrange
On Tue, Dec 09, 2014 at 03:39:35PM +, Daniel P. Berrange 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 anybody

[openstack-dev] [Ironic] ironic-discoverd status update

2014-12-11 Thread Dmitry Tantsur
Hi all! As you know I actively promote ironic-discoverd project [1] as one of the means to do hardware inspection for Ironic (see e.g. spec [2]), so I decided it's worth to give some updates to the community from time to time. This email is purely informative, you may safely skip it, if

Re: [openstack-dev] Lack of quota - security bug or not?

2014-12-11 Thread George Shuklin
On 12/11/2014 03:16 PM, Thierry Carrez wrote: George Shuklin wrote: On 12/10/2014 10:34 PM, Jay Pipes wrote: On 12/10/2014 02:43 PM, George Shuklin wrote: I have some small discussion in launchpad: is lack of a quota for unprivileged user counted as security bug (or at least as a bug)? If

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

2014-12-11 Thread Tihomir Trifonov
*​​Client just needs to know which URL to hit in order to invoke a certain API, and does not need to know the procedure name or parameters ordering.* ​That's where the difference is. I think the client has to know the procedure name and parameters. Otherwise​ we have a translation factory

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Mark McClain
On Dec 11, 2014, at 8:43 AM, Jay Pipes jaypi...@gmail.com wrote: I'm generally in favor of making name attributes opaque, utf-8 strings that are entirely user-defined and have no constraints on them. I consider the name to be just a tag that the user places on some resource. It is the

Re: [openstack-dev] [oslo] deprecation 'pattern' library??

2014-12-11 Thread Davanum Srinivas
Surprisingly deprecator is still available on pypi On Thu, Dec 11, 2014 at 2:04 AM, Julien Danjou jul...@danjou.info wrote: On Wed, Dec 10 2014, Joshua Harlow wrote: […] Or in general any other comments/ideas about providing such a deprecation pattern library? +1 * debtcollector made

[openstack-dev] [nova] - filter out fields in keypair object.

2014-12-11 Thread Dmitry Bogun
Hi. Why we filter out some fields from keeper object in create and list operations? in module nova.api.openstack.compute.plugins.v3.keypairs class KeypairController(wsgi.Controller): # ... def _filter_keypair(self, keypair, **attrs): clean = { 'name': keypair.name,

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

2014-12-11 Thread Maxime Leroy
On Thu, Dec 11, 2014 at 11:41 AM, Daniel P. Berrange berra...@redhat.com wrote: On Thu, Dec 11, 2014 at 09:37:31AM +0800, henry hly wrote: On Thu, Dec 11, 2014 at 3:48 AM, Ian Wells ijw.ubu...@cack.org.uk wrote: On 10 December 2014 at 01:31, Daniel P. Berrange berra...@redhat.com wrote:

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

2014-12-11 Thread Daniel P. Berrange
On Thu, Dec 11, 2014 at 04:15:00PM +0100, Maxime Leroy wrote: On Thu, Dec 11, 2014 at 11:41 AM, Daniel P. Berrange berra...@redhat.com wrote: On Thu, Dec 11, 2014 at 09:37:31AM +0800, henry hly wrote: On Thu, Dec 11, 2014 at 3:48 AM, Ian Wells ijw.ubu...@cack.org.uk wrote: On 10 December

[openstack-dev] [barbican] PKCS#11 configuration

2014-12-11 Thread Ivan Wallis
Hi, I am trying to configure Barbican with an external HSM that has a PKCS#11 provider and just wondering if someone can point me in the right direction on how to configure this type of environment? Regards, Ivan ___ OpenStack-dev mailing list

Re: [openstack-dev] [neutron] mid-cycle update

2014-12-11 Thread Kyle Mestery
On Wed, Dec 10, 2014 at 5:41 PM, Michael Still mi...@stillhq.com wrote: On Thu, Dec 11, 2014 at 10:14 AM, Kyle Mestery mest...@mestery.com wrote: The Neutron mid-cycle [1] is now complete, I wanted to let everyone know how it went. Thanks to all who attended, we got a lot done. I admit to

Re: [openstack-dev] [nova] Kilo specs review day

2014-12-11 Thread Andrew Laski
On 12/10/2014 04:41 PM, Michael Still wrote: Hi, at the design summit we said that we would not approve specifications after the kilo-1 deadline, which is 18 December. Unfortunately, we’ve had a lot of specifications proposed this cycle (166 to my count), and haven’t kept up with the review

Re: [openstack-dev] [neutron] mid-cycle update

2014-12-11 Thread Mark McClain
On Dec 11, 2014, at 10:29 AM, Kyle Mestery mest...@mestery.com wrote: On Wed, Dec 10, 2014 at 5:41 PM, Michael Still mi...@stillhq.com mailto:mi...@stillhq.com wrote: This all sounds like good work. Did you manage to progress the nova-network to neutron migration tasks as well? I

[openstack-dev] [nova] meeting location change

2014-12-11 Thread Sean Dague
In today's early Nova meeting (UTC 1400), we realized that there no longer is a conflicting meeting in #openstack-meeting. I've adjusted the location here - https://wiki.openstack.org/wiki/Meetings#Nova_team_Meeting Also added a formula based on date +%U to let you figure out if it's an early or

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Henry Gessau
On Thu, Dec 11, 2014, Mark McClain m...@mcclain.xyz wrote: On Dec 11, 2014, at 8:43 AM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: I'm generally in favor of making name attributes opaque, utf-8 strings that are entirely user-defined and have no constraints on them. I

[openstack-dev] Reason for mem/vcpu ratio in default flavors

2014-12-11 Thread David Kranz
Perhaps this is a historical question, but I was wondering how the default OpenStack flavor size ratio of 2/1 was determined? According to http://aws.amazon.com/ec2/instance-types/, ec2 defines the flavors for General Purpose (M3) at about 3.7/1, with Compute Intensive (C3) at about 1.9/1 and

Re: [openstack-dev] [Fuel] We lost some commits during upstream puppet manifests merge

2014-12-11 Thread Aleksandr Didenko
Also I’m just wondering how do we keep upstream modules in our repo? They are not submodules, so how is it organized? Currently, we don't have any automatic tracking system for changes we apply to the community/upstream modules, that could help us to re-apply them during the sync. Only git or

Re: [openstack-dev] [barbican] PKCS#11 configuration

2014-12-11 Thread Ade Lee
Which HSM do you have? On Thu, 2014-12-11 at 07:24 -0800, Ivan Wallis wrote: Hi, I am trying to configure Barbican with an external HSM that has a PKCS#11 provider and just wondering if someone can point me in the right direction on how to configure this type of environment? Regards,

Re: [openstack-dev] [nova][cinder][infra] Ceph CI status update

2014-12-11 Thread Anita Kuno
On 12/11/2014 09:36 AM, Jon Bernard wrote: Heya, quick Ceph CI status update. Once the test_volume_boot_pattern was marked as skipped, only the revert_resize test was failing. I have submitted a patch to nova for this [1], and that yields an all green ceph ci run [2]. So at the moment, and

Re: [openstack-dev] [nova][cinder][infra] Ceph CI status update

2014-12-11 Thread Anita Kuno
On 12/11/2014 09:36 AM, Jon Bernard wrote: Heya, quick Ceph CI status update. Once the test_volume_boot_pattern was marked as skipped, only the revert_resize test was failing. I have submitted a patch to nova for this [1], and that yields an all green ceph ci run [2]. So at the moment, and

Re: [openstack-dev] [Horizon] Proposal to add IPMI meters from Ceilometer in Horizon

2014-12-11 Thread David Lyle
Please submit the blueprint and set the target for the milestone you are targeting. That will add it the the blueprint review process for Horizon. Seems like a minor change, so at this time, I don't foresee any issues with approving it. David On Thu, Dec 11, 2014 at 12:34 AM, Xin, Xiaohui

Re: [openstack-dev] [Horizon] Moving _conf and _scripts to dashboard

2014-12-11 Thread David Lyle
I'm probably not understanding the nuance of the question but moving the _scripts.html file to openstack_dashboard creates some circular dependencies, does it not? templates/base.html in the horizon side of the repo includes _scripts.html and insures that the javascript needed by the existing

[openstack-dev] We are looking for ten individuals to participate in a usability study sponsored by the Horizon team

2014-12-11 Thread Kruithof, Piet
We are looking for ten individuals to participate in a usability study sponsored by the Horizon team. The purpose of the study is to evaluate the proposed Launch Instance workflow. The study will be moderated remotely via Google Hangouts. Participant description: individuals who use cloud

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread Jay Pipes
On 12/11/2014 04:02 AM, joehuang wrote: [joehuang] The major challenge for VDF use case is cross OpenStack networking for tenants. The tenant's VM/Volume may be allocated in different data centers geographically, but virtual network (L2/L3/FW/VPN/LB) should be built for each tenant automatically

[openstack-dev] [Keystone][python-keystoneclient][pycadf] Abandoning of inactive reviews

2014-12-11 Thread Morgan Fainberg
This is a notification that at the start of next week, all projects under the Identity Program are going to see a cleanup of old/lingering open reviews. I will be reviewing all reviews. If there is a negative score (this would be, -1 or -2 from jenkins, -1 or -2 from a code reviewer, or -1

Re: [openstack-dev] [neutron] mid-cycle update

2014-12-11 Thread Carl Baldwin
We also spent a half day progressing the Ipam work and made a plan to move forward. Carl On Dec 10, 2014 4:16 PM, Kyle Mestery mest...@mestery.com wrote: The Neutron mid-cycle [1] is now complete, I wanted to let everyone know how it went. Thanks to all who attended, we got a lot done. I admit

Re: [openstack-dev] [sahara] team meeting Dec 11 1800 UTC

2014-12-11 Thread Sergey Lukjanov
http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-12-11-17.59.html http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-12-11-17.59.log.html On Wed, Dec 10, 2014 at 6:21 PM, Sergey Lukjanov slukja...@mirantis.com wrote: Hi folks, We'll be having the Sahara team

Re: [openstack-dev] [nova] Kilo specs review day

2014-12-11 Thread Joe Gordon
On Thu, Dec 11, 2014 at 7:30 AM, Andrew Laski andrew.la...@rackspace.com wrote: On 12/10/2014 04:41 PM, Michael Still wrote: Hi, at the design summit we said that we would not approve specifications after the kilo-1 deadline, which is 18 December. Unfortunately, we’ve had a lot of

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

2014-12-11 Thread W Chan
Renat, Here's the blueprint. https://blueprints.launchpad.net/mistral/+spec/mistral-runtime-context I'm proposing to add *args and **kwargs to the __init__ methods of all actions. The action context can be passed as a dict in the kwargs. The global context and the env context can be provided

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread Andrew Laski
On 12/11/2014 04:02 AM, joehuang wrote: Hello, Russell, Many thanks for your reply. See inline comments. -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: Thursday, December 11, 2014 5:22 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev]

Re: [openstack-dev] [nova] Kilo specs review day

2014-12-11 Thread Michael Still
The dashboard is really cool, although I had to fix the spelling error... Michael On Fri, Dec 12, 2014 at 6:26 AM, Joe Gordon joe.gord...@gmail.com wrote: On Thu, Dec 11, 2014 at 7:30 AM, Andrew Laski andrew.la...@rackspace.com wrote: On 12/10/2014 04:41 PM, Michael Still wrote: Hi,

Re: [openstack-dev] [Horizon] Moving _conf and _scripts to dashboard

2014-12-11 Thread Thai Q Tran
It would not create a circular dependency, dashboard would depend on horizon - not the latter.Scripts that are library specific will live in horizon while scripts that are panel specific will live in dashboard.Let me draw a more concrete example.In Horizon We know that _script and _conf are

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

2014-12-11 Thread Vishvananda Ishaya
On Dec 11, 2014, at 2:41 AM, Daniel P. Berrange berra...@redhat.com wrote: On Thu, Dec 11, 2014 at 09:37:31AM +0800, henry hly wrote: On Thu, Dec 11, 2014 at 3:48 AM, Ian Wells ijw.ubu...@cack.org.uk wrote: On 10 December 2014 at 01:31, Daniel P. Berrange berra...@redhat.com wrote: So

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Vishvananda Ishaya
On Dec 11, 2014, at 8:00 AM, Henry Gessau ges...@cisco.com wrote: On Thu, Dec 11, 2014, Mark McClain m...@mcclain.xyz wrote: On Dec 11, 2014, at 8:43 AM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: I'm generally in favor of making name attributes opaque, utf-8 strings

Re: [openstack-dev] Reason for mem/vcpu ratio in default flavors

2014-12-11 Thread Vishvananda Ishaya
Probably just a historical artifact of values that we thought were reasonable for our machines at NASA. Vish On Dec 11, 2014, at 8:35 AM, David Kranz dkr...@redhat.com wrote: Perhaps this is a historical question, but I was wondering how the default OpenStack flavor size ratio of 2/1 was

Re: [openstack-dev] [oslo] deprecation 'pattern' library??

2014-12-11 Thread Joshua Harlow
Ya, I to was surprised by the general lack of this kind of library on pypi. One would think u know that people deprecate stuff, but maybe this isn't the norm for python... Why deprecate when u can just make v2.0 ;) -Josh Davanum Srinivas wrote: Surprisingly deprecator is still available on

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Vishvananda Ishaya
On Dec 11, 2014, at 1:04 PM, Jay Pipes jaypi...@gmail.com wrote: On 12/11/2014 04:01 PM, Vishvananda Ishaya wrote: On Dec 11, 2014, at 8:00 AM, Henry Gessau ges...@cisco.com wrote: On Thu, Dec 11, 2014, Mark McClain m...@mcclain.xyz wrote: On Dec 11, 2014, at 8:43 AM, Jay Pipes

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Jay Pipes
On 12/11/2014 04:07 PM, Vishvananda Ishaya wrote: On Dec 11, 2014, at 1:04 PM, Jay Pipes jaypi...@gmail.com wrote: On 12/11/2014 04:01 PM, Vishvananda Ishaya wrote: On Dec 11, 2014, at 8:00 AM, Henry Gessau ges...@cisco.com wrote: On Thu, Dec 11, 2014, Mark McClain m...@mcclain.xyz wrote:

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Sean Dague
On 12/11/2014 04:16 PM, Jay Pipes wrote: On 12/11/2014 04:07 PM, Vishvananda Ishaya wrote: On Dec 11, 2014, at 1:04 PM, Jay Pipes jaypi...@gmail.com wrote: On 12/11/2014 04:01 PM, Vishvananda Ishaya wrote: On Dec 11, 2014, at 8:00 AM, Henry Gessau ges...@cisco.com wrote: On Thu, Dec 11,

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Mathieu Gagné
On 2014-12-11 8:43 AM, Jay Pipes wrote: I'm generally in favor of making name attributes opaque, utf-8 strings that are entirely user-defined and have no constraints on them. I consider the name to be just a tag that the user places on some resource. It is the resource's ID that is unique. I

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells - summit recap and move forward

2014-12-11 Thread Joe Gordon
On Thu, Dec 11, 2014 at 1:02 AM, joehuang joehu...@huawei.com wrote: Hello, Russell, Many thanks for your reply. See inline comments. -Original Message- From: Russell Bryant [mailto:rbry...@redhat.com] Sent: Thursday, December 11, 2014 5:22 AM To: openstack-dev@lists.openstack.org

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

2014-12-11 Thread Joe Gordon
On Wed, Dec 10, 2014 at 7:42 AM, Pasquale Porreca pasquale.porr...@dektech.com.au wrote: Well, one of the main reason to choose an open source product is to avoid vendor lock-in. I think it is not advisable to embed in the software running in an instance a call to OpenStack specific

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Clint Byrum
Excerpts from Jay Pipes's message of 2014-12-11 05:43:46 -0800: On 12/11/2014 07:22 AM, Anna Kamyshnikova wrote: Hello everyone! In neutron there is a rather old bug [1] about adding uniqueness for security group name and tenant id. I found this idea reasonable and started working on

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

2014-12-11 Thread Rochelle Grober
First, I agree that it's much friendlier to have unique security group names and not have to use UUIDs since when there is a need for more than a default, the Tennant admin will want to be able to easily track info related to it, plus in the GUI, if it allows a new one to be created, it should

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

2014-12-11 Thread Zane Bitter
On 11/12/14 01:14, Anant Patil wrote: On 04-Dec-14 10:49, Zane Bitter wrote: On 01/12/14 02:02, Anant Patil wrote: On GitHub:https://github.com/anantpatil/heat-convergence-poc I'm trying to review this code at the moment, and finding some stuff I don't understand:

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

2014-12-11 Thread Zane Bitter
On 11/12/14 08:26, Murugan, Visnusaran wrote: [Murugan, Visnusaran] In case of rollback where we have to cleanup earlier version of resources, we could get the order from old template. We'd prefer not to have a graph table. In theory you could get it by keeping old templates around. But that

[openstack-dev] [Cross Project][Ops][Log] Logging Working Group: need to establish our regular meeting(s)

2014-12-11 Thread Rochelle Grober
Hi guys, I apologize for taking so long to get to this, but I think once we start meeting, our momentum will build. I'm cross posting this to dev and operators so anyone who is interested can participate. I've set up a Doodle to vote on the first set of times (these happen to work for me and

Re: [openstack-dev] [Horizon] Proposal to add IPMI meters from Ceilometer in Horizon

2014-12-11 Thread Xin, Xiaohui
Got it. Thanks! We will soon add the blueprint for IPMI meters in Horizon. Thanks Xiaohui From: David Lyle [mailto:dkly...@gmail.com] Sent: Friday, December 12, 2014 1:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Horizon] Proposal to add

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread joehuang
Hi, Jay, Good question, see inline comments, pls. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Friday, December 12, 2014 1:58 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all] [tc] [PTL] Cascading

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread Joshua Harlow
So I think u mean 'proprietary'? http://www.merriam-webster.com/dictionary/proprietary -Josh joehuang wrote: Hi, Jay, Good question, see inline comments, pls. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Friday,

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

2014-12-11 Thread Tripp, Travis S
Tihomir, Your comments in the patch were the actually the clearest to me about ease of customizing without requiring upstream changes and really made me think more about your points. Here are a couple of bullet points for consideration. * Will we take on auto-discovery of API extensions

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread joehuang
Hello, Andrew, Thanks for your confirmation. See inline comments, pls. -Original Message- From: Andrew Laski [mailto:andrew.la...@rackspace.com] Sent: Friday, December 12, 2014 3:56 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all] [tc] [PTL] Cascading vs.

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells - summit recap and move forward

2014-12-11 Thread joehuang
Hello, Joe Thank you for your good question. Question: How would something like flavors work across multiple vendors. The OpenStack API doesn't have any hard coded names and sizes for flavors. So a flavor such as m1.tiny may actually be very different vendor to vendor. Answer: The flavor is

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread joehuang
Hello, Joshua, Sorry, my fault. You are right. I owe you two dollars. Best regards Chaoyi Huang ( joehuang ) -Original Message- From: Joshua Harlow [mailto:harlo...@outlook.com] Sent: Friday, December 12, 2014 9:47 AM To: OpenStack Development Mailing List (not for usage questions)

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

2014-12-11 Thread henry hly
+100! So, for the vif-type-vhostuser, a general script path name replace the vif-detail vhost_user_ovs_plug, because it's not the responsibility of nova to understand it. On Thu, Dec 11, 2014 at 11:24 PM, Daniel P. Berrange berra...@redhat.com wrote: On Thu, Dec 11, 2014 at 04:15:00PM +0100,

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

2014-12-11 Thread Richard Jones
On Fri Dec 12 2014 at 1:06:08 PM Tripp, Travis S travis.tr...@hp.com wrote: ​Do we really need the lines:​ project = api.keystone.tenant_get(request, id) kwargs = _tenant_kwargs_from_DATA(request.DATA, enabled=None) ​ I agree that if you already have all the data it is really bad to have

[openstack-dev] [heat-docker]Does the heat-docker supports auto-scaling and monitoring the Docker container?

2014-12-11 Thread Chenliang (L)
Hi, Now We can deploying Docker containers in an OpenStack environment using Heat. But I feel confused. Could someone can tell me does the heat-docker supports monitoring the Docker container in a stack and how to monitor it? Does it supports auto-scaling the Docker container? Best Regards,

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells - summit recap and move forward

2014-12-11 Thread Joe Gordon
On Thu, Dec 11, 2014 at 6:25 PM, joehuang joehu...@huawei.com wrote: Hello, Joe Thank you for your good question. Question: How would something like flavors work across multiple vendors. The OpenStack API doesn't have any hard coded names and sizes for flavors. So a flavor such as

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread Dan Smith
[joehuang] Could you pls. make it more clear for the deployment mode of cells when used for globally distributed DCs with single API. Do you mean cinder/neutron/glance/ceilometer will be shared by all cells, and use RPC for inter-dc communication, and only support one vendor's OpenStack

Re: [openstack-dev] [heat-docker]Does the heat-docker supports auto-scaling and monitoring the Docker container?

2014-12-11 Thread Jay Lau
So you are using heat docker driver but not nova docker driver, right? If you are using nova docker driver, then the container was treated as VM and you can do monitoring and auto scaling with heat. But with heat docker driver, it talk to docker host directly which you need to define in HEAT

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

2014-12-11 Thread Ryu Ishimoto
On Thu, Dec 11, 2014 at 7:41 PM, Daniel P. Berrange berra...@redhat.com wrote: Yes, I really think this is a key point. When we introduced the VIF type mechanism we never intended for there to be soo many different VIF types created. There is a very small, finite number of possible ways to

[openstack-dev] [python-cinderclient] Return request ID to caller

2014-12-11 Thread Malawade, Abhijeet
HI, I want your thoughts on blueprint 'Log Request ID Mappings' for cross projects. BP: https://blueprints.launchpad.net/nova/+spec/log-request-id-mappings It will enable operators to get request id's mappings easily and will be useful in analysing logs effectively. For logging 'Request ID

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

2014-12-11 Thread Renat Akhmerov
Maybe put all these different context under a kwarg called context? For example, ctx = { env: {...}, global: {...}, runtime: { execution_id: ..., task_id: ..., ... } } action = SomeMistralAction(context=ctx) IMO, that is a nice idea. I

Re: [openstack-dev] [oslo] deprecation 'pattern' library??

2014-12-11 Thread Joshua Harlow
Filed spec @ https://review.openstack.org/#/c/141220/ Comments welcome :-) -Josh Joshua Harlow wrote: Ya, I to was surprised by the general lack of this kind of library on pypi. One would think u know that people deprecate stuff, but maybe this isn't the norm for python... Why deprecate

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread henry hly
On Fri, Dec 12, 2014 at 11:41 AM, Dan Smith d...@danplanet.com wrote: [joehuang] Could you pls. make it more clear for the deployment mode of cells when used for globally distributed DCs with single API. Do you mean cinder/neutron/glance/ceilometer will be shared by all cells, and use RPC for

Re: [openstack-dev] [Neutron] XenAPI questions

2014-12-11 Thread YAMAMOTO Takashi
hi, good to hear. do you have any estimate when it will be available? will it cover dom0 side of the code found in neutron/plugins/openvswitch/agent/xenapi? YAMAMOTO Takashi Hi Yamamoto, XenAPI and Neutron do work well together, and we have an private CI that is running Neutron jobs. As

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells - summit recap and move forward

2014-12-11 Thread joehuang
Hi Joe, Thank you to lead us to deep diving into cascading. My answer is listed below your question. I don't think this is sufficient. If the underlying hardware the between multiple vendors is different setting the same values for a flavor will result in different performance

Re: [openstack-dev] [all] [tc] [PTL] Cascading vs. Cells – summit recap and move forward

2014-12-11 Thread joehuang
Hello, Dan, Correct, cells only applies to single-vendor distributed deployments. In both its current and future forms, it uses private APIs for communication between the components, and thus isn't suited for a multi-vendor environment. Thank you for your confirmation. My doubt is what's