Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

2015-06-02 Thread Thomas Goirand
On 06/01/2015 07:16 PM, Jeremy Stanley wrote: On 2015-06-01 14:55:06 +0200 (+0200), Thomas Goirand wrote: [...] So, should I start writing a script to build an image for package building (ie: an image with sbuild, git-buildpackage, and so on...)? [...] Probably what we'd want to do is

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

2015-06-02 Thread Miguel Ángel Ajo
The backport seems reasonable IMO. Is this tested in a multihost environment?. I ask, because given the Ian explanation (which probably I got wrong), the issue is in the NET-NIC-VM path while the patch fixes the path in the network node (this is ran in the dhcp agent). dhcp-NIC-NET. Best,

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-02 Thread Jay Lau
Thanks Adrian, imho making name as required can bring more convenient to end users because UUID is difficult to use. Without name, the end user need to retrieve the UUID of the bay/baymodel first before he did some operations for the bay/baymodel, its really time consuming. We can discuss more in

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

2015-06-02 Thread Ian Wells
The fix should work fine. It is technically a workaround for the way checksums work in virtualised systems, and the unfortunate fact that some DHCP clients check checksums on packets where the hardware has checksum offload enabled. (This doesn't work due to an optimisation in the way QEMU treats

[openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-02 Thread Serg Melikyan
I would like to ask community for the help to implement support for TOSCA in Murano: https://blueprints.launchpad.net/murano/+spec/support-tosca-format I was driving this feature and during OpenStack Summit in Paris we spent good amount of time discussing how we can implement support for TOSCA

[openstack-dev] [Cinder] [Taskflow]Review help to cinder bp:Implement function to manage/unmanage snapshots

2015-06-02 Thread hao wang
Hi, folks, There is a cinder bp:Implement function to manage/unmanage snapshots( https://review.openstack.org/#/c/144590/), that we use taskflow to implement this feature. So I need your guys' help(cinder taskflow) to push this forward. Thanks. -- Best Wishes For You!

Re: [openstack-dev] [Cinder] [Taskflow]Review help to cinder bp:Implement function to manage/unmanage snapshots

2015-06-02 Thread Dulko, Michal
Right now we’re working on refactoring current TaskFlow implementations in Cinder to make them more readable and clean. Then we’ll be able to decide if we want to get more TaskFlow into Cinder or step back from using it. Deadline for refactoring work is around 1 of July. Here’s related patch

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Boris Bobrov
On Tuesday 02 June 2015 09:32:45 Chenhong Liu wrote: There is keystone/exception.py which contains Exceptions defined and used inside keystone provide 4xx and 5xx status code. And we can use it like: exception.Forbidden.code, exception.forbiddent.title exception.NotFound.code,

Re: [openstack-dev] [Murano] Nominating Kirill Zaitsev for murano-core

2015-06-02 Thread Ekaterina Chernova
+1 Regards, Kate. On Tue, Jun 2, 2015 at 9:32 AM, Serg Melikyan smelik...@mirantis.com wrote: I'd like to propose Kirill Zaitsev to core members of Murano team. Kirill Zaitsev is active member of our community, he implemented https://launchpad.net/murano/+milestone/2015.1.0 several

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

2015-06-02 Thread Ian Wells
VIF plugging, but not precisely libvirt VIF plugging, so I'll tout this to a hopefully interested audience. At the summit, we wrote up a spec we were thinking of doing at [1]. It actually proposes two things, which is a little naughty really, but hey. Firstly we propose that we turn binding

Re: [openstack-dev] [Murano] Nominating Filip Blaha for murano-core

2015-06-02 Thread Ekaterina Chernova
+1 Welcome! On Tue, Jun 2, 2015 at 9:25 AM, Serg Melikyan smelik...@mirantis.com wrote: Folks, I'd like to propose Filip Blaha to core members of Murano team. Filip is active member of our community and he maintains a good score as contributor:

[openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Chenhong Liu
There is keystone/exception.py which contains Exceptions defined and used inside keystone provide 4xx and 5xx status code. And we can use it like: exception.Forbidden.code, exception.forbiddent.title exception.NotFound.code, exception.NotFound.title This makes the code looks pretty and

[openstack-dev] [neutron] [fwaas] -IPv6 support in Kilo

2015-06-02 Thread Rukhsana Ansari
Hi, I was browsing the code to understand IPv6 support For FWaaS in Kilo. I don't see a restriction in the db code or in reference fwaas_plugin.py However, from this:

Re: [openstack-dev] [neutron] [fwaas] -IPv6 support in Kilo

2015-06-02 Thread Mike Spreitzer
From: Rukhsana Ansari rukhsana.ans...@oneconvergence.com To: openstack-dev@lists.openstack.org Date: 06/02/2015 01:59 PM Subject: [openstack-dev] [neutron] [fwaas] -IPv6 support in Kilo Hi, I was browsing the code to understand IPv6 support For FWaaS in Kilo. I don't see a

Re: [openstack-dev] [Fuel] Call for 7.0 feature design and review

2015-06-02 Thread Sean M. Collins
Can we update the vxlan bp to target it to 7.0? The series goal is still set to 6.1.x https://blueprints.launchpad.net/fuel/+spec/neutron-vxlan-support Thanks -- Sean M. Collins __ OpenStack Development Mailing List (not

Re: [openstack-dev] [Fuel] Call for 7.0 feature design and review

2015-06-02 Thread Andrew Woodward
Updated Sean, I see that there is no spec linked in gerrit or the BP do we have one? On Tue, Jun 2, 2015 at 11:07 AM Sean M. Collins s...@coreitpro.com wrote: Can we update the vxlan bp to target it to 7.0? The series goal is still set to 6.1.x

[openstack-dev] Dynamic Policy for Access Control Subteam Meeting

2015-06-02 Thread Adam Young
Since this a cross project concern, sending it out to the wider mailing list: We have a sub-effort in Keystone to do better access control policy (not the Neutron or Congress based policy efforts). I presented on this at the summit, and the effort is under full swing. We are going to set

[openstack-dev] [Tacker] Tacker (NFV MANO VNFM) team meeting June 4th

2015-06-02 Thread Stephen Wong
Please note the change in time (and day of the week) and channel: Meeting on #openstack-meeting at 1600 UTC (9:00am PDT) Agenda can be found here (feel free to add yours): https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_June_4.2C_2015 Thanks, - Stephen

[openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-02 Thread Vahid S Hashemian
Hi Serg, As I mentioned in my earlier email to you I am interested in participating in this effort. I am a Heat-Translator contributor and have started looking at how the integration may work (at a higher level for now). I'll send my thoughts on that shortly. Thanks. Regards,

[openstack-dev] [puppet] Change abandonment policy

2015-06-02 Thread Colleen Murphy
In today's meeting we discussed implementing a policy for whether and when core reviewers should abandon old patches whose author's were inactive. (This doesn't apply to authors that want to abandon their own changes, only for core reviewers to abandon other people's changes.) There are a few

[openstack-dev] Release naming for M open for nominations

2015-06-02 Thread Monty Taylor
Hey everyone! It's time to pick a name for the M release. If you have a name you'd like us to vote on, please add it here: https://wiki.openstack.org/wiki/Release_Naming/M_Proposals The nominations will be open until 2015-06-07 23:59:59 UTC. If you don't remember the rules, they're here:

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

2015-06-02 Thread Wanjing Xu
Thanks everybody. While I am trying to digest all the responses, I am here to reply why we are not considering a driver. We already have an application which listens to neutron events to do some other stuff, it might just be easier for us if we reuse this framework and program the LBaasS from

Re: [openstack-dev] [puppet] Change abandonment policy

2015-06-02 Thread Andrew Woodward
Also in favor of #2 and thought it was how it was running. #4 sounds bad and may hide good code. How do we want to account for drive-by authors who are going to be unable to work on future revisions. We talked a while back that we wanted to be able to account for this as some operators are unable

Re: [openstack-dev] [Fuel] vxlan support

2015-06-02 Thread Andrew Woodward
Samuel, VXLAN was moved to 7.0, as you noted it won't make 6.1. Mirantis has identified this as a high priority for 7.0 so it should get more attention this time. However any assistance in CR / Testing is always appreciated. On Thu, May 28, 2015 at 1:38 PM Samuel Bartel

[openstack-dev] [Neutron][Nova] DHCP sent by veth interface connected to Linux Bridge

2015-06-02 Thread Padmanabhan Krishnan
Hello, I am seeing some weird behavior in my setup and would really appreciate if someone could clarify a few things below: Setup: Simple two node. One with control+compute (Node1) and another a compute (Node2). Since, Node2 is running low in HW, I create a AvlZone putting only Node2 so that I

[openstack-dev] [qa] SafeConfigParser.write duplicates defaults: bug or feature?

2015-06-02 Thread David Kranz
The verify_tempest_config script has an option to write a new conf file. I noticed that when you do this, the items in DEFAULT are duplicated in every section that is written. Looking at the source I can see why this happens. I guess it is not harmful but is this considered a bug in the write

Re: [openstack-dev] [Murano] Nominating Kirill Zaitsev for murano-core

2015-06-02 Thread Kirill Zaitsev
Thanks all! Someone should now say «With great power comes great responsibility»  And I should respond with something like «Night gathers, and now my watch begins», should I?  I kind of like this kind of symbolism =) Isn’t there a Core Developer Oath or Vow? Shouldn’t we think of one? -- 

[openstack-dev] New meeting time for nova-scheduler - vote!

2015-06-02 Thread Ed Leafe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, The current meeting time of 1500 UTC on Tuesday is presenting some conflicts, so we're trying to come up with an alternative. I've created a Doodle for anyone who is interested in attending these meetings to indicate what times work and which

Re: [openstack-dev] [neutron] Mechanism drivers and Neutron server forking?

2015-06-02 Thread Kevin Benton
Sorry about the long delay. Even the LOG.error(KEVIN PID=%s network response: %s % (os.getpid(), r.text)) line? Surely the server would have forked before that line was executed - so what could prevent it from executing once in each forked process, and hence generating multiple logs? Yes, just

[openstack-dev] [Horizon] high priority patches, please review

2015-06-02 Thread Richard Jones
Hi Horizon devs, The following test patches are a high priority, blocking further new work in Liberty until they're landed. Please consider helping review them to get the landed ASAP: https://review.openstack.org/#/c/170554/ https://review.openstack.org/#/c/167738/

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

2015-06-02 Thread Wanjing Xu
Doug Our current event consumer is listening to the queue with the topic specified in neutron.conf as notification_topics = x. neutron will generate all create/update/delete events(from api) to this queue including vip/member/pool events. So we don't need to write a driver to generate the

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

2015-06-02 Thread Doug Wiegley
Hi, Ok, so you just need a noop driver, which you can find in the review link I posted a few emails back. Thanks, doug On Jun 2, 2015, at 6:23 PM, Wanjing Xu wanjing...@hotmail.com wrote: Doug Our current event consumer is listening to the queue with the topic specified in

Re: [openstack-dev] [all] error codes design conclusion?

2015-06-02 Thread Gareth
Thanks Rochelle, looking forward to your next version On Wed, Jun 3, 2015 at 6:27 AM, Rochelle Grober rochelle.gro...@huawei.com wrote: Spec is in the works but needs to be reworked a bit more. It’s under Openstack-specs. I’m revamping it, but I’m taking vacation until Monday, so you won’t

Re: [openstack-dev] [Glance] [all] Liberty summit: Updates in Glance

2015-06-02 Thread Fei Long Wang
On 02/06/15 01:51, Jay Pipes wrote: On 06/01/2015 08:30 AM, John Garbutt wrote: On 1 June 2015 at 13:10, Flavio Percoco fla...@redhat.com wrote: On 01/06/15 11:57 +0100, John Garbutt wrote: On 26/05/15 13:54 -0400, Nikhil Komawar wrote: FWIW, moving Nova from glance v1 to glance v2, without

[openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-02 Thread Vahid S Hashemian
In other words, can a new component that is being to an environment have dependency on the existing ones? If so, how does that defined? For example, going back to your example of a multi-tier application, if I initially have PostgreDB in my environment, and later add Tomcat, how do I tell

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Joe Gordon
On Tue, Jun 2, 2015 at 4:12 PM, Robert Collins robe...@robertcollins.net wrote: On 3 June 2015 at 10:34, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-06-02 21:59:34 + (+), Ian Cordasco wrote: I like this very much. I recall there was a session at the summit about this that

[openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-02 Thread Vahid S Hashemian
Hi Gosha, Thank you very much for your message. Before I can answer your question I would need to better understand how Murano handles life-cycle operations that you mentioned. I hope you can bear with me with these questions or point me to documents that I need to read. When I deploy an

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Ian Wienand
On 06/03/2015 07:24 AM, Boris Pavlovic wrote: Really it's hard to find cores that understand whole project, but it's quite simple to find people that can maintain subsystems of project. We are made wise not by the recollection of our past, but by the responsibility for our future. -

[openstack-dev] [release][oslo] oslo.messaging release 1.13.0 (liberty)

2015-06-02 Thread doug
We are content to announce the release of: oslo.messaging 1.13.0: Oslo Messaging API This release is part of the liberty release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.messaging For more details, please see the git log history below and:

Re: [openstack-dev] [neutron] [fwaas] -IPv6 support in Kilo

2015-06-02 Thread Sumit Naiksatam
Hi Rukhsana, When you say IPv6 support for FWaaS in Kilo can you indicate exactly what you are looking for? The FWaaS rules in the resource model support both formats (which I recall has always been the case). A particular implementation/driver may not support ipv6 (and which is what you are

Re: [openstack-dev] [nova] I think nova behaves poorly when booting multiple instances

2015-06-02 Thread Chris Friesen
On 06/02/2015 02:36 PM, Andrew Laski wrote: There used to be a project that I think was looking for an API like this to provide a reservation system, Climate or Blazar or something. There was brief talk of providing something like it for that use case, but the idea was put on the backburner to

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Boris Pavlovic
Jeremy, the Infrastructure Project is now past 120 repos with more than 70 core reviewers among those. I dislike the idea of having 120 repos for single tool. It makes things complicated for everybody: documentation stuff, installation, maintaing, work that touches multiple repos and so

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Jeremy Stanley
On 2015-06-03 02:36:20 +0300 (+0300), Boris Pavlovic wrote: I dislike the idea of having 120 repos for single tool. It makes things complicated for everybody: documentation stuff, installation, maintaing, work that touches multiple repos and so on.. So I would prefer to have single repo

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Sean McGinnis
I like this idea. I agree, as things grow it is probably easier to find folks that know certain areas a project rather than the full scope. This could be a good way to handle the load and delegate some pieces (such as driver reviews) to a different set of people. On 06/02/2015 04:24 PM,

[openstack-dev] 6.1 Hard Code Freeze - status update June 2nd

2015-06-02 Thread Eugene Bogdanov
Hello everyone, We currently see 6 bugs as main HCF dependencies [1]. We'll try to close all of them overnight. If we don't succeed, we'll need another day. We'll take decision whether we do/do not declare HCF based on the results tomorrow morning PDT. [1] Key HCF dependencies:

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Salvatore Orlando
On 2 June 2015 at 23:59, Ian Cordasco ian.corda...@rackspace.com wrote: On 6/2/15, 16:24, Boris Pavlovic bo...@pavlovic.me wrote: Hi stackers, Issue --- Projects are becoming bigger and bigger overtime. More and more people would like to contribute code and usually core

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Jeremy Stanley
On 2015-06-02 21:59:34 + (+), Ian Cordasco wrote: I like this very much. I recall there was a session at the summit about this that Thierry and Kyle led. If I recall correctly, the discussion mentioned that it wasn't (at this point in time) possible to use gerrit the way you describe

Re: [openstack-dev] [keystone][reseller] New way to get a project scoped token by name

2015-06-02 Thread Morgan Fainberg
Hi Henrique, I don't think we need to specifically call out that we want a domain, we should always reference the namespace as we do today. Basically, if we ask for a project name we need to also provide it's namespace (your option #1). This clearly lines up with how we handle projects in domains

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

2015-06-02 Thread James E. Blair
Hi, This came up at the TC meeting today, and I volunteered to provide an update from the discussion. In general, I think there is a lot of support for a packaging effort in OpenStack. The discussion here has been great; we need to answer a few questions, get some decisions written down, and

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

2015-06-02 Thread Doug Wiegley
Hi, If you have an existing event consumer that you want to stick with, you could write a driver that just generates events. There are some error status warts that you’d either have to live with or handle, but you could do that later. Thanks, doug On Jun 2, 2015, at 1:05 PM, Wanjing Xu

[openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Boris Pavlovic
Hi stackers, *Issue* *---* Projects are becoming bigger and bigger overtime. More and more people would like to contribute code and usually core reviewers team can't scale enough. It's very hard to find people that understand full project and have enough time to do code reviews. As a result

[openstack-dev] [cors] Last Call for Comments

2015-06-02 Thread Michael Krotscheck
Hey everyone! The CORS spec has been under review for about a month now, and the TC has put it on the agenda next week for final approval. I plan on doing one final revision of the document - if it is warranted - so get your comments in now! https://review.openstack.org/#/c/179866/ Michael

Re: [openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-02 Thread Georgy Okrokvertskhov
Hi Vahid, Thank you for sharing your thoughts. I have a questions about application life-cycle if we use TOSCA translator. In Murano the main advantage of using HOT format is that we can update Het stack with resources as soon as we need to deploy additional application. We can dynamically create

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Ian Cordasco
On 6/2/15, 16:24, Boris Pavlovic bo...@pavlovic.me wrote: Hi stackers, Issue --- Projects are becoming bigger and bigger overtime. More and more people would like to contribute code and usually core reviewers team can't scale enough. It's very hard to find people that understand full

Re: [openstack-dev] [keystone] [nova] [oslo] oslo.policy requests from the Nova team

2015-06-02 Thread David Lyle
The Horizon project also uses the nova policy.json file to do role based access control (RBAC) on the actions a user can perform. If the defaults are hidden in the code, that makes those checks a lot more difficult to perform. Horizon will then get to duplicate all the hard coded defaults in our

Re: [openstack-dev] Dynamic Policy for Access Control Subteam Meeting

2015-06-02 Thread Morgan Fainberg
On Tue, Jun 2, 2015 at 12:09 PM, Adam Young ayo...@redhat.com wrote: Since this a cross project concern, sending it out to the wider mailing list: We have a sub-effort in Keystone to do better access control policy (not the Neutron or Congress based policy efforts). I presented on this

Re: [openstack-dev] [openstackclient] Image create-or-update

2015-06-02 Thread Steve Martinelli
I'm thinking that the current approach is probably how we want to keep things. I can't imagine many other projects being okay with multiple create calls with the same name. Though if you're really adamant about including that support, we could include a new flag (--or-update) that performs the

Re: [openstack-dev] [keystone] [nova] [oslo] oslo.policy requests from the Nova team

2015-06-02 Thread Kevin L. Mitchell
On Tue, 2015-06-02 at 16:16 -0600, David Lyle wrote: The Horizon project also uses the nova policy.json file to do role based access control (RBAC) on the actions a user can perform. If the defaults are hidden in the code, that makes those checks a lot more difficult to perform. Horizon will

Re: [openstack-dev] [all] error codes design conclusion?

2015-06-02 Thread Rochelle Grober
Spec is in the works but needs to be reworked a bit more. It’s under Openstack-specs. I’m revamping it, but I’m taking vacation until Monday, so you won’t see the new patch until at least next week. You are welcome to comment on the current version, though:

Re: [openstack-dev] [Neutron][LBaaS] No LBaaS agent?

2015-06-02 Thread Wanjing Xu
Hi Kunal Is it OK if you tell us how this agentless controller is done? Or at least give me the pointer to the installation guide? I wonder if using an noop driver is the way. RegardsWanjingFrom: kunalhgan...@gmail.com Date: Mon, 1 Jun 2015 19:02:29 -0700 To:

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Robert Collins
On 3 June 2015 at 10:34, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-06-02 21:59:34 + (+), Ian Cordasco wrote: I like this very much. I recall there was a session at the summit about this that Thierry and Kyle led. If I recall correctly, the discussion mentioned that it wasn't (at

Re: [openstack-dev] [Magnum] Discuss mesos-bay-type Blueprint

2015-06-02 Thread Kai Qiang Wu
Hi All, For mesos bay, I think what we should implement depends on user-cases. If users use magnum to create mesos-bay, what would they do with mesos in following steps ? 1. If they go to mesos (framework or anything) directly, we'd better not involve any new mesos objects, but use container if

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

2015-06-02 Thread Matthew Thode
On 06/02/2015 05:41 PM, James E. Blair wrote: Hi, This came up at the TC meeting today, and I volunteered to provide an update from the discussion. In general, I think there is a lot of support for a packaging effort in OpenStack. The discussion here has been great; we need to answer a

Re: [openstack-dev] [Murano] Help needed with TOSCA support in Murano

2015-06-02 Thread Georgy Okrokvertskhov
When you update an environment in Murano it will update underlying stack. You should not see a new stack for the same environment. If you have a PostgresDB deployed and then add a Tomcat application you will see that stack was updated with new resources. There is no dependency between Tomcat and

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-02 Thread Adrian Otto
Eric, On Jun 2, 2015, at 10:07 PM, Eric Windisch e...@windisch.usmailto:e...@windisch.us wrote: On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto adrian.o...@rackspace.commailto:adrian.o...@rackspace.com wrote: I have reflected on this further and offer this suggestion: 1) Add a feature to

Re: [openstack-dev] [Magnum] Discuss mesos-bay-type Blueprint

2015-06-02 Thread Jay Lau
In today's IRC meeting, the conclusion for now is that create a Marathon+Mesos bay without exposing any object to Magnum but enable end user operate Marathon directly. Thanks. 2015-06-03 9:19 GMT+08:00 Kai Qiang Wu wk...@cn.ibm.com: Hi All, For mesos bay, I think what we should implement

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-02 Thread Jay Lau
I think that we did not come to a conclusion in today's IRC meeting. Adrian proposed that Magnum generate a unique name just like what docker is doing for docker run, the problem mentioned by Andrew Melton is that Magnum support multi tenant, we should support the case that bay/baymodel under

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-02 Thread Eric Windisch
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto adrian.o...@rackspace.com wrote: I have reflected on this further and offer this suggestion: 1) Add a feature to Magnum to auto-generate human readable names, like Docker does for un-named containers, and ElasticSearch does for naming cluster

Re: [openstack-dev] [nova] I think nova behaves poorly when booting multiple instances

2015-06-02 Thread Jay Pipes
On 06/02/2015 07:25 PM, Chris Friesen wrote: On 06/02/2015 02:36 PM, Andrew Laski wrote: There used to be a project that I think was looking for an API like this to provide a reservation system, Climate or Blazar or something. There was brief talk of providing something like it for that use

Re: [openstack-dev] [nova] I think nova behaves poorly when booting multiple instances

2015-06-02 Thread Chris Friesen
On 06/02/2015 07:48 PM, Jay Pipes wrote: On 06/02/2015 07:25 PM, Chris Friesen wrote: In many cases only nova-compute can resolve races (resource tracking of specific CPU cores, specific PCI devices, etc. in the face of parallel scheduling) so unless we're going to guarantee no races then I

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-02 Thread Adrian Otto
I have reflected on this further and offer this suggestion: 1) Add a feature to Magnum to auto-generate human readable names, like Docker does for un-named containers, and ElasticSearch does for naming cluster nodes. Use this feature if no name is specified upon the creation of a Bay or

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread John Griffith
On Tue, Jun 2, 2015 at 7:19 PM, Ian Wienand iwien...@redhat.com wrote: On 06/03/2015 07:24 AM, Boris Pavlovic wrote: Really it's hard to find cores that understand whole project, but it's quite simple to find people that can maintain subsystems of project. We are made wise not by the

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

2015-06-02 Thread Salvatore Orlando
On 3 June 2015 at 07:12, John Griffith john.griffi...@gmail.com wrote: On Tue, Jun 2, 2015 at 7:19 PM, Ian Wienand iwien...@redhat.com wrote: On 06/03/2015 07:24 AM, Boris Pavlovic wrote: Really it's hard to find cores that understand whole project, but it's quite simple to find people

Re: [openstack-dev] [puppet] Change abandonment policy

2015-06-02 Thread Cody Herriges
Colleen Murphy wrote: snip 3) Manually abandon after N months/weeks changes that have a -1 that was never responded to ``` If a change is submitted and given a -1, and subsequently the author becomes unresponsive for a few weeks, reviewers should leave reminder comments on the review or

[openstack-dev] UPDATED: [new][mercador] Announcing Mercador, a project to federate OpenStack cloud services.

2015-06-02 Thread Geoff Arnold
[Updated with additional information.] Hello, I'm pleased to announce the development of a new project called Mercador (Portuguese for “merchant”). Mercador will provide a mechanism for integrating OpenStack cloud services from one cloud service provider (CSP) into the set of services

Re: [openstack-dev] [neutron] Mechanism drivers and Neutron server forking?

2015-06-02 Thread Salvatore Orlando
I'm not sure if you can test this behaviour on your own because it requires the VMware plugin and the eventlet handling of backend response. But the issue was manifesting and had to be fixed with this mega-hack [1]. The issue was not about several workers executing the same code - the loopingcall

Re: [openstack-dev] [nova] I think nova behaves poorly when booting multiple instances

2015-06-02 Thread Alexis Lee
Alexis Lee said on Tue, Jun 02, 2015 at 11:28:03AM +0100: Paul Murray tells me there was a blueprint for this some time ago, but I can't find a spec for it. I'm interested in pushing this, I'll put up a spec at some point unless someone beats me to it. Oops, found it, thanks Paul:

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Neo Liu
On Tue, Jun 2, 2015 at 5:46 PM Boris Bobrov bbob...@mirantis.com wrote: On Tuesday 02 June 2015 09:32:45 Chenhong Liu wrote: There is keystone/exception.py which contains Exceptions defined and used inside keystone provide 4xx and 5xx status code. And we can use it like:

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread samuel
Hi Chenhong Liu, encapsulated into the WSGI application, Keystone is architecturally organized as follows: Application - Router - Controller - Manager - Driver The Router connects called URLs with the code in the Controller, which delegates actions to Manager, which manages the business

Re: [openstack-dev] [Manila] Expected Manila behavior for creation of share from snapshot

2015-06-02 Thread Valeriy Ponomaryov
Deepak, transfer-* is not suitable in this particular case. Usage of share networks causes creation of resources, when transfer does not. Also in this topic we have creation of new share based on some snapshot. Valeriy On Sun, May 31, 2015 at 4:23 PM, Deepak Shetty dpkshe...@gmail.com wrote:

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-02 Thread Steven Dake (stdake)
Kennan, Agree on no requirement for unique name. Regards -steve From: Kai Qiang Wu wk...@cn.ibm.commailto:wk...@cn.ibm.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Monday, June 1, 2015

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

2015-06-02 Thread Neo Liu
On Tue, Jun 2, 2015 at 7:24 PM samuel sam...@lsd.ufcg.edu.br wrote: Hi Chenhong Liu, In addition, I think creating a common file to place non-error HTTP status code is a good idea and can be discussed with the Keystone cores. Feel free to add a point to our weekly meeting, Tuesdays 18:00

[openstack-dev] About the volume status exposure during migration

2015-06-02 Thread Sheng Bo Hou
Hi Avishay, I really appreciate your comments on the spec I submitted for volume migration improvement.(https://review.openstack.org/#/c/186327/) I truly understand your concerns about exposing the migrating status to the end user(not admin). However, there is something I get confused: when we

Re: [openstack-dev] [nova][scheduler] Updating Our Concept of Resources

2015-06-02 Thread Alexis Lee
Ed Leafe said on Mon, Jun 01, 2015 at 07:40:17AM -0500: We need to update our concept of a resource internally in Nova, both in the DB and in code, and stop thinking that every request should have a flavor. If you allocate all the memory of a box to high-mem instances, you may not be billing

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

2015-06-02 Thread Miguel Ángel Ajo
Ooook, fully understood now. Thanks Ihar Ian for the clarification :) Miguel Ángel Ajo On Tuesday, 2 de June de 2015 at 13:33, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/02/2015 10:10 AM, Miguel Ángel Ajo wrote: The backport seems reasonable IMO.

[openstack-dev] [murano] python versions

2015-06-02 Thread Kirill Zaitsev
It seems that python-muranoclient is the last project from murano-official group, that still supports python2.6. Other projects do not have a 2.6 testing job (correct me if I’m wrong). Personally I think it’s time to drop support for 2.6 completely, and add (at least non-voting) jobs with

Re: [openstack-dev] [Neutron] virtual machine can not get DHCP lease due packet has no checksum

2015-06-02 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/02/2015 10:10 AM, Miguel Ángel Ajo wrote: The backport seems reasonable IMO. Is this tested in a multihost environment?. I ask, because given the Ian explanation (which probably I got wrong), the issue is in the NET-NIC-VM path while

[openstack-dev] [Global Requirements] Adding apscheduler to global requirements

2015-06-02 Thread BORTMAN, Limor (Limor)
Hi all, As part as a BP in mistral (Add seconds granularity in cron-trigger execute[1]) I would like to add apscheduler (Advanced Python Scheduler[2]) to the openstack Global Requirements. Any objections? [1] https://blueprints.launchpad.net/mistral/+spec/cron-trigger-seconds-granularity [2]

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

2015-06-02 Thread Irena Berezovsky
Hi Ian, I like your proposal. It sounds very reasonable and makes separation of concerns between neutron and nova very clear. I think with vif plug script support [1]. it will help to decouple neutron from nova dependency. Thank you for sharing this, Irena [1]

[openstack-dev] [nova] RequestSpec object and Instance model

2015-06-02 Thread Sylvain Bauza
Hi, Currently working on implementing the RequestSpec object BP [1], I had some cool comments on my change here : https://review.openstack.org/#/c/145528/12/nova/objects/request_spec.py,cm Since we didn't discussed on how to persist that RequestSpec object, I think the comment is valuable.

[openstack-dev] [keystone][reseller] New way to get a project scoped token by name

2015-06-02 Thread Henrique Truta
Hi folks, In Reseller[1], we’ll have the domains concept merged into projects, that means that we will have projects that will behave as domains. Therefore, it will be possible to have two projects with the same name in a hierarchy, one being a domain and another being a regular project. For

Re: [openstack-dev] [Nova] Liberty mid-cycle meetup

2015-06-02 Thread Matt Riedemann
On 5/11/2015 9:48 AM, Michael Still wrote: Ok, given we've had a whole bunch people sign up already and no complaints here, I think this is a done deal. So, you can now assume that the dates are final. I will email people currently registered to let them know as well. I have added the

[openstack-dev] Cross-Project meeting, Tue Jun 2nd, 21:00 UTC

2015-06-02 Thread Thierry Carrez
Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting today at 21:00 UTC, with the following agenda: * Horizontal teams announcements * Update the API WG merge process for Liberty [1] * Vertical teams announcements * Open discussion [1]

Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel

2015-06-02 Thread Steven Dake (stdake)
I can see both points of view. Principle of least surprise applies here. A list of bays without names would be surprising for a tenant imo :) I don’t particularly have a strong opinion, but my inclination is to lean towards non-unique names as a requirement for creating bays. Again I am not

[openstack-dev] [release][oslo] oslo.concurrency release 1.10.0 (liberty)

2015-06-02 Thread doug
We are stoked to announce the release of: oslo.concurrency 1.10.0: Oslo Concurrency library This release is part of the liberty release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.concurrency For more details, please see the git log history below and:

Re: [openstack-dev] [Murano] Nominating Kirill Zaitsev for murano-core

2015-06-02 Thread Stan Lagun
+1 without any doubt Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis sla...@mirantis.com On Tue, Jun 2, 2015 at 10:43 AM, Ekaterina Chernova efedor...@mirantis.com wrote: +1 Regards, Kate. On Tue, Jun 2, 2015 at 9:32 AM, Serg Melikyan smelik...@mirantis.com wrote:

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

2015-06-02 Thread Gary Kotton
Hi, At the summit this was discussed in the nova sessions and there were a number of concerns regarding security etc. Thanks Gary From: Irena Berezovsky irenab@gmail.commailto:irenab@gmail.com Reply-To: OpenStack List

[openstack-dev] [new][mercador] Announcing Mercador, a project to federate OpenStack cloud services.

2015-06-02 Thread Geoff Arnold
Hello, I'm pleased to announce the development of a new project called Mercador (Portuguese for “merchant”). Mercador will provide a mechanism for integrating OpenStack cloud services from one cloud service provider (CSP) into the set of services published by a second CSP. The mechanism is

Re: [openstack-dev] [Murano] Nominating Filip Blaha for murano-core

2015-06-02 Thread Stan Lagun
+1 Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis sla...@mirantis.com On Tue, Jun 2, 2015 at 9:25 AM, Serg Melikyan smelik...@mirantis.com wrote: Folks, I'd like to propose Filip Blaha to core members of Murano team. Filip is active member of our community and he

Re: [openstack-dev] [nova] I think nova behaves poorly when booting multiple instances

2015-06-02 Thread Alexis Lee
Andrew Laski said on Mon, Jun 01, 2015 at 09:26:33AM -0400: However what these parameters give users, versus orchestrating outside of Nova, is the ability to have the instances all scheduled as a single block. We should seek to provide this via persistent claims. IE add to the API something

  1   2   >