Re: [openstack-dev] How to write a new neutron L2 plugin using ML2 framework?

2014-02-11 Thread Mathieu Rohon
Hi, mellanox is also developing a ML2 driver : https://blueprints.launchpad.net/neutron/+spec/mlnx-ml2-support The Havana release is already out, and we are currently working for IceHouse. But the code for IceHouse should be under review before feb. 18th. So it would be difficult to have your

Re: [openstack-dev] Ready to import Launchpad Answers into Ask OpenStack

2014-02-11 Thread Sergey Lukjanov
Thank you! On Tue, Feb 11, 2014 at 11:36 AM, Stefano Maffulli stef...@openstack.orgwrote: Hi Sergey On Tue 11 Feb 2014 08:01:48 AM CET, Sergey Lukjanov wrote: Stefano, is it possible to import savanna's answers@launchpad to ask.o.o? Yes, indeed. I apologize for not putting you

Re: [openstack-dev] [Heat] in-instance update hooks

2014-02-11 Thread Thomas Spatzier
Hi Clint, thanks for writing this down. This is a really interesting use case and feature, also in relation to what was recently discussed on rolling updates. I have a couple of thoughts and questions: 1) The overall idea seems clear to me but I have problems understanding the detailed flow and

Re: [openstack-dev] [Heat] in-instance update hooks

2014-02-11 Thread Sergey Lukjanov
Hi Clint, nice blueprint. I've added a section about Savanna to the etherpad. Our further usecase looks like the Trove's one - we probably like to support resizing nodes. Additionally, we'd like to decommission data nodes before reboot/shutdown them. Thanks. On Tue, Feb 11, 2014 at 9:22 AM,

Re: [openstack-dev] [glance][nova]improvement-of-accessing-to-glance

2014-02-11 Thread Flavio Percoco
On 10/02/14 05:28 +, Eiichi Aikawa wrote: Hi, all, Thanks for your comment. Please let me re-explain. The main purpose of our blueprint is to use network resources more efficiently. To complete this purpose, we suggested the method of using 2 lists. We think, as I wrote before, by listing

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

2014-02-11 Thread Khanh-Toan Tran
Second, there is nothing wrong with booting the instances (or instantiating other resources) as separate commands as long as we support some kind of reservation token. I'm not sure what reservation token would do, is it some kind of informing the scheduler that the resources would not be

[openstack-dev] [Openstack-dev][All] tox 1.7.0 error while running tests

2014-02-11 Thread Swapnil Kulkarni
Hello, I created a new devstack environment today and installed tox 1.7.0, and getting error *tox.ConfigError: ConfigError: substitution key 'posargs' not found.* Details in [1]. Anybody encountered similar error before? Any workarounds/updates needed? [1]

[openstack-dev] [Mistral]

2014-02-11 Thread Dmitri Zimine
Do we have (or think about) a shorthand to calling REST_API action, without defining a service? FULL DSL: Services: TimeService: type: REST_API parameters: baseUrl:http://api.timezonedb.com key:my_api_key actions: get-time:

Re: [openstack-dev] [Openstack-dev][All] tox 1.7.0 error while running tests

2014-02-11 Thread Assaf Muller
- Original Message - From: Swapnil Kulkarni swapnilkulkarni2...@gmail.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Tuesday, February 11, 2014 11:26:29 AM Subject: [openstack-dev] [Openstack-dev][All] tox 1.7.0 error

Re: [openstack-dev] [Openstack-dev][All] tox 1.7.0 error while running tests

2014-02-11 Thread Andreas Jaeger
On 02/11/2014 10:26 AM, Swapnil Kulkarni wrote: Hello, I created a new devstack environment today and installed tox 1.7.0, and getting error *tox.ConfigError: ConfigError: substitution key 'posargs' not found.* Details in [1]. Anybody encountered similar error before? Any

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

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

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

2014-02-11 Thread Gary Kotton
+1 On 2/11/14 1:28 AM, Mark McClain mmccl...@yahoo-inc.com wrote: All- I¹d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg has been valuable contributor to Neutron by actively reviewing, working on bugs, and contributing code. Neutron cores please reply back with

Re: [openstack-dev] [Openstack-dev][All] tox 1.7.0 error while running tests

2014-02-11 Thread Dmitry Tantsur
Hi. This seems to be related: https://bugs.launchpad.net/openstack-ci/+bug/1274135 We also encountered this. On Tue, 2014-02-11 at 14:56 +0530, Swapnil Kulkarni wrote: Hello, I created a new devstack environment today and installed tox 1.7.0, and getting error tox.ConfigError: ConfigError:

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

2014-02-11 Thread Salvatore Orlando
+1 Il 11/feb/2014 10:47 Gary Kotton gkot...@vmware.com ha scritto: +1 On 2/11/14 1:28 AM, Mark McClain mmccl...@yahoo-inc.com wrote: All- I¹d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg has been valuable contributor to Neutron by actively reviewing, working

Re: [openstack-dev] [Openstack-stable-maint] Stable gate status?

2014-02-11 Thread Alan Pevec
Hi Mark and Anita, could we declare stable/havana neutron gate jobs good enough at this point? There are still random failures as this no-op change shows https://review.openstack.org/72576 but I don't think they're stable/havana specific. Do we have a list of those somewhere? Pulled out where

Re: [openstack-dev] [infra] Proposing Sergey Lukjanov for infra-core

2014-02-11 Thread Thierry Carrez
James E. Blair wrote: I'm very pleased to propose that we add Sergey Lukjanov to the infra-core team. He is among the top reviewers of projects in openstack-infra, and is very familiar with how jenkins-job-builder and zuul are used and configured. He has done quite a bit of work in helping

Re: [openstack-dev] [Heat] in-instance update hooks

2014-02-11 Thread Clint Byrum
Excerpts from Thomas Spatzier's message of 2014-02-11 00:38:53 -0800: Hi Clint, thanks for writing this down. This is a really interesting use case and feature, also in relation to what was recently discussed on rolling updates. I have a couple of thoughts and questions: 1) The overall

Re: [openstack-dev] universal wheel support

2014-02-11 Thread Sascha Peilicke
On Monday 10 February 2014 19:02:55 Doug Hellmann wrote: On Mon, Feb 10, 2014 at 1:14 PM, Joe Gordon joe.gord...@gmail.com wrote: On Mon, Feb 10, 2014 at 9:00 AM, Doug Hellmann doug.hellm...@dreamhost.com wrote: On Sat, Feb 8, 2014 at 7:08 PM, Monty Taylor mord...@inaugust.com

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

2014-02-11 Thread Robert Kukura
On 02/10/2014 06:28 PM, Mark McClain wrote: All- I’d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg has been valuable contributor to Neutron by actively reviewing, working on bugs, and contributing code. Neutron cores please reply back with +1/0/-1 votes. +1

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

2014-02-11 Thread Edgar Magana
+1 of course! Edgar Sent from my iPhone On Feb 11, 2014, at 8:28 AM, Mark McClain mmccl...@yahoo-inc.com wrote: All- I’d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg has been valuable contributor to Neutron by actively reviewing, working on bugs, and

[openstack-dev] [Murano] Can we migrate to oslo.messaging?

2014-02-11 Thread Serg Melikyan
oslo.messaging http://github.com/openstack/oslo.messaging is a library that provides RPC and Notifications API, they are part of the same library for mostly historical reasons. One of the major goals of *oslo.messaging* is to provide clean RPC and Notification API without any trace of messaging

[openstack-dev] [Neutron][IPv6] NAT64 Discussion

2014-02-11 Thread Xuhan Peng
In previous Neutron IPv6 team meeting, we discussed the requirement of providing NAT64 in OpenStack to facilitate the communication between IPv6 and IPv4 hosts. For example, from tenant IPv6 network to external traditional IPv4 network. I was suggested to initiate a discussion in ML to gather all

[openstack-dev] Fwd: [Openstack] [GSoC] Call for Mentors and Participants

2014-02-11 Thread Davanum Srinivas
Hi all, Apologies if you saw this already. Since we have a really tight deadline to drum up mentor and student participation, forwarding this once to the openstack-dev mailing list. The deadline is this Friday the 14th. thanks, dims On Sun, Feb 9, 2014 at 5:34 PM, Davanum Srinivas

Re: [openstack-dev] OpenStack-dev Digest, Vol 22, Issue 27

2014-02-11 Thread Abishek Subramanian (absubram)
Hi Shixiong, Thanks for the reply and clearing up my question! The document you've shared - they aren't the only possible combinations correct? Each of the two fields can have any one of these four values in any possible combination yes? Thanks! On 2/11/14 7:00 AM,

Re: [openstack-dev] [Murano] Can we migrate to oslo.messaging?

2014-02-11 Thread Doug Hellmann
On Tue, Feb 11, 2014 at 8:05 AM, Serg Melikyan smelik...@mirantis.comwrote: oslo.messaging http://github.com/openstack/oslo.messaging is a library that provides RPC and Notifications API, they are part of the same library for mostly historical reasons. One of the major goals of

[openstack-dev] [Nova][Glance]supporting of v1 and v2 glance APIs in Nova

2014-02-11 Thread Lingxian Kong
Greetings A few days ago, I met some problems when using 'createimage' feature in Nova, we found that using V1 of glanceclient has some problem with processing of metadata, the version number and even the glance URIs are both hardcoded in Nova. then, we found the bluepring[1] proposed, and the

Re: [openstack-dev] [Mistral]

2014-02-11 Thread Renat Akhmerov
Dmitry, I think you are right here. I think for simple case we should be able to use in-place action definition without having to define the action separately. Like you said it’s only valuable if we need to reuse it. The only difference I see between std:send-email and something like REST_API

Re: [openstack-dev] [Murano] Can we migrate to oslo.messaging?

2014-02-11 Thread Serg Melikyan
Doug, thank you for your response! With moving to *oslo.messaging *I think we need to carefully re-evaluate our communication patterns and try to either fit them to RPC/Notification, or work on extending *oslo.messaging *with some new ideas. Adopting a new library is always a challenge. The RPC

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

2014-02-11 Thread Chris Friesen
On 02/11/2014 03:21 AM, Khanh-Toan Tran wrote: Second, there is nothing wrong with booting the instances (or instantiating other resources) as separate commands as long as we support some kind of reservation token. I'm not sure what reservation token would do, is it some kind of informing

Re: [openstack-dev] [Openstack-stable-maint] Stable gate status?

2014-02-11 Thread Anita Kuno
On 02/11/2014 04:57 AM, Alan Pevec wrote: Hi Mark and Anita, could we declare stable/havana neutron gate jobs good enough at this point? There are still random failures as this no-op change shows https://review.openstack.org/72576 but I don't think they're stable/havana specific. Do we

Re: [openstack-dev] [Heat] in-instance update hooks

2014-02-11 Thread Steven Dake
On 02/10/2014 10:22 PM, Clint Byrum wrote: Hi, so in the previous thread about rolling updates it became clear that having in-instance control over updates is a more fundamental idea than I had previously believed. During an update, Heat does things to servers that may interrupt the server's

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

2014-02-11 Thread Sumit Naiksatam
+1 Sumit. On Feb 10, 2014 3:33 PM, Mark McClain mmccl...@yahoo-inc.com wrote: All- I'd like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg has been valuable contributor to Neutron by actively reviewing, working on bugs, and contributing code. Neutron cores please reply

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

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

[openstack-dev] [Murano] Community meeting agenda - 02/11/2014

2014-02-11 Thread Alexander Tivelkov
Hi, This is just a reminder that we are going to have a weekly meeting of Murano team in IRC (#openstack-meeting-alt) today at 17:00 UTC (9am PST) . The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda Feel free to add anything you want to discuss. --

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

2014-02-11 Thread Dina Belova
Like a restaurant reservation, it would claim the resources for use by someone at a later date. That way nobody else can use them. That way the scheduler would be responsible for determining where the resource should be allocated from, and getting a reservation for that resource. It would

[openstack-dev] Hyper-v meeting cancelled.

2014-02-11 Thread Peter Pouliot
Hi all. We are currently working to bring additional compute power to the hyper-v ci infrastructure. Because this task currently takes precedence I need to cancel the meeting for today. P ___ OpenStack-dev mailing list

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

2014-02-11 Thread Khanh-Toan Tran
Thanks, I will look closely at it. De : Dina Belova [mailto:dbel...@mirantis.com] Envoyé : mardi 11 février 2014 16:45 À : OpenStack Development Mailing List (not for usage questions) Objet : Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver Scheduler Like a restaurant

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

2014-02-11 Thread Yathiraj Udupi (yudupi)
I thought of adding some more points about the Solver Scheduler to this conversation. Think of SolverScheduler as a placement decision engine, which gives an optimal solution for the specified request based on the current information available at a specific time. The request could potentially be

Re: [openstack-dev] [Heat] in-instance update hooks

2014-02-11 Thread Clint Byrum
Excerpts from Steven Dake's message of 2014-02-11 07:19:19 -0800: On 02/10/2014 10:22 PM, Clint Byrum wrote: Hi, so in the previous thread about rolling updates it became clear that having in-instance control over updates is a more fundamental idea than I had previously believed. During an

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

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

[openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack

2014-02-11 Thread Andrey Danin
Hi Openstackers, We are working on link aggregation support in Fuel. We wonder what are the most desirable types of bonding now in datacenters. We had some issues (see below) with OVS bond in LACP mode, and it turned out that standard Linux bonding (attached to OVS bridges) was a better option in

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

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

Re: [openstack-dev] [Mistral]

2014-02-11 Thread Dmitri Zimine
Yes it makes sense, let's draft how it may look; and also think over implementation implications - now we separate task parameters, action parameters, and service parameters, we may need to merge them when instantiating the action. DZ. On Feb 11, 2014, at 6:19 AM, Renat Akhmerov

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

2014-02-11 Thread Eddie Sheffield
A few days ago, I met some problems when using 'createimage' feature in Nova, we found that using V1 of glanceclient has some problem with processing of metadata, the version number and even the glance URIs are both hardcoded in Nova. then, we found the bluepring[1] proposed, and the

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

2014-02-11 Thread Dina Belova
This is something to explore to add in Nova, using a local service or external service (need to explore Climate). I need to find out more about Climate. Here is Climate Launchpad: https://launchpad.net/climate That's still really young project, but I believe it'll have great future

[openstack-dev] [Neutron][IPv6] Idea: Floating IPv6 - Without any kind of NAT

2014-02-11 Thread Martinx - ジェームズ
Hello Stackers! It is very nice to watch the OpenStack evolution in IPv6! Great job guys!! I have another idea: Floating IP for IPv6, or just Floating IPv6 With IPv4, as we know, OpenStack have a feature called Floating IP, which is basically a 1-to-1 NAT rule (within tenant's Namespace

Re: [openstack-dev] [neutron] [group-policy] Changing the meeting time

2014-02-11 Thread Stephen Wong
Hi Kyle, Almost missed this - sounds good to me. Thanks, - Stephen On Mon, Feb 10, 2014 at 7:30 PM, Kyle Mestery mest...@siliconloons.comwrote: Folks: I'd like to propose moving the Neutron Group Policy meeting going forward, starting with this Thursday. The meeting has been at 1600

[openstack-dev] www.xrefs.info: addition of openflow and SDN

2014-02-11 Thread John Smith
I setup http://www.xrefs.info for open source developers to do cross reference search based on OpenGrok. It covers projects like linux kernel from version 0.01 to latest, android, linux packages, BSD, cloud computing, big data, SDN etc.. Check it out...Let me know if you have any suggestions or

Re: [openstack-dev] [Heat] in-instance update hooks

2014-02-11 Thread Fox, Kevin M
Another scaling down/update use case: Say I have a pool of ssh servers for users to use (compute cluster login nodes). Autoscaling up is easy. Just launch a new node and add it to the load balancer. Scaling down/updating is harder. It should ideally: * Set the admin state on the load balancer

Re: [openstack-dev] [Neutron][IPv6] Idea: Floating IPv6 - Without any kind of NAT

2014-02-11 Thread Veiga, Anthony
Hello Stackers! It is very nice to watch the OpenStack evolution in IPv6! Great job guys!! Thanks! I have another idea: Floating IP for IPv6, or just Floating IPv6 With IPv4, as we know, OpenStack have a feature called Floating IP, which is basically a 1-to-1 NAT rule (within tenant's

Re: [openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack

2014-02-11 Thread Clint Byrum
Excerpts from Andrey Danin's message of 2014-02-11 08:42:46 -0800: Hi Openstackers, We are working on link aggregation support in Fuel. We wonder what are the most desirable types of bonding now in datacenters. We had some issues (see below) with OVS bond in LACP mode, and it turned out that

Re: [openstack-dev] [infra] Proposing Sergey Lukjanov for infra-core

2014-02-11 Thread Sergey Lukjanov
Thank you all! I'm glad to help infra team with extremely growing number of CRs to their projects. On Tue, Feb 11, 2014 at 2:24 PM, Thierry Carrez thie...@openstack.orgwrote: James E. Blair wrote: I'm very pleased to propose that we add Sergey Lukjanov to the infra-core team. He is

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

2014-02-11 Thread Yathiraj Udupi (yudupi)
hi Sylvain and Dina, Thanks for your pointers about Climate. I will take a closer look at it and try it out. So after a reservation lease for a VM is made by Climate, who acts on it to finally instantiate the VM ? Is it Climate or Nova should act on the lease to finally provision the VM.

Re: [openstack-dev] [neutron] [group-policy] Changing the meeting time

2014-02-11 Thread Sumit Naiksatam
Hi Kyle, The new time sounds good to me as well, thanks for initiating this. ~sumit. On Tue, Feb 11, 2014 at 9:02 AM, Stephen Wong s3w...@midokura.com wrote: Hi Kyle, Almost missed this - sounds good to me. Thanks, - Stephen On Mon, Feb 10, 2014 at 7:30 PM, Kyle Mestery

Re: [openstack-dev] [Neutron][LBaaS] Proposal for model

2014-02-11 Thread WICKES, ROGER
[Roger] Hi Stephen! Great job! Obviously your experience is both awesome and essential here. I would ask that we add a historical archive (physically implemented as a log file, probably) object to your model. When you mentioned sending data off to Ceilometer, that triggered me to think about

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

2014-02-11 Thread Dina Belova
So after a reservation lease for a VM is made by Climate, who acts on it to finally instantiate the VM ? Is it Climate or Nova should act on the lease to finally provision the VM. Now to take resources for VM it's actually created and then immediately shelved, not to be in active state and

Re: [openstack-dev] [Heat] in-instance update hooks

2014-02-11 Thread Clint Byrum
Thanks Kevin, great summary. This is beyond the scope of in-instance notification. I think this is more like the generic notification API that Thomas Herve suggested in the rolling updates thread. It can definitely use the same method for its implementation, and I think it is adjacent to, and not

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

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

[openstack-dev] [oslo-notify] notifications consumed by multiple subscribers

2014-02-11 Thread Sanchez, Cristian A
Hi, I’m planning to use oslo.notify mechanisms to implement a climate blueprint: https://blueprints.launchpad.net/climate/+spec/notifications. Ideally, the notifications sent by climate should be received by multiple services subscribed to the same topic. Is that possible with oslo.notify? And

Re: [openstack-dev] [Murano] Can we migrate to oslo.messaging?

2014-02-11 Thread Doug Hellmann
On Tue, Feb 11, 2014 at 9:59 AM, Serg Melikyan smelik...@mirantis.comwrote: Doug, thank you for your response! With moving to *oslo.messaging *I think we need to carefully re-evaluate our communication patterns and try to either fit them to RPC/Notification, or work on extending

Re: [openstack-dev] [oslo-notify] notifications consumed by multiple subscribers

2014-02-11 Thread Doug Hellmann
On Tue, Feb 11, 2014 at 1:28 PM, Sanchez, Cristian A cristian.a.sanc...@intel.com wrote: Hi, I'm planning to use oslo.notify mechanisms to implement a climate blueprint: https://blueprints.launchpad.net/climate/+spec/notifications. Ideally, the notifications sent by climate should be

Re: [openstack-dev] [infra] Meeting Tuesday February 11th at 19:00 UTC

2014-02-11 Thread Elizabeth Krumbach Joseph
On Mon, Feb 10, 2014 at 7:48 AM, Elizabeth Krumbach Joseph l...@princessleia.com wrote: The OpenStack Infrastructure (Infra) team is hosting our weekly meeting tomorrow, Tuesday February 11th, at 19:00 UTC in #openstack-meeting Thanks to everyone who attended, minutes and logs now available

Re: [openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack

2014-02-11 Thread Dan Prince
- Original Message - From: Andrey Danin ada...@mirantis.com To: openstack-dev@lists.openstack.org, fuel-dev fuel-...@lists.launchpad.net Sent: Tuesday, February 11, 2014 11:42:46 AM Subject: [openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack Hi Openstackers, We are

Re: [openstack-dev] [neutron] [group-policy] Changing the meeting time

2014-02-11 Thread Kyle Mestery
FYI, I’ve made the change on the meeting pages as well [1]. The Neutron Group Policy meeting is now at 1700UTC Thursday’s on #openstack-meeting-alt. Thanks! Kyle [1] https://wiki.openstack.org/wiki/Meetings#Neutron_Group_Policy_Sub-Team_Meeting On Feb 11, 2014, at 11:30 AM, Sumit Naiksatam

Re: [openstack-dev] [Neutron] Support for multiple provider networks with same VLAN segmentation id

2014-02-11 Thread Aaron Rosen
I believe it would need to be like: network_vlan_ranges = physnet1:100:300, phynet2:100:300, phynet3:100:300 Additional comments inline: On Mon, Feb 10, 2014 at 8:49 PM, Vinay Bannai vban...@gmail.com wrote: Bob and Kyle, Thanks for your review. We looked at this option and it seems it

[openstack-dev] [python-openstacksdk] First meeting scheduled

2014-02-11 Thread Jesse Noller
As I said last week; we’re ready to kickoff and have regular meetings for the “unified python SDK” project. The initial meeting is scheduled on the wiki: https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting Date/Time: Feb. 19th - 19:00 UTC / 1pm CST IRC channel:

Re: [openstack-dev] [keystone] role of Domain in VPC definition

2014-02-11 Thread Martin, JC
Ravi, It seems that the following Blueprint https://wiki.openstack.org/wiki/Blueprint-aws-vpc-support has been approved. However, I cannot find a discussion with regard to the merit of using project vs. domain, or other mechanism for the implementation. I have an issue with this approach as

Re: [openstack-dev] [Trove] Backup/Restore encryption/decryption issue

2014-02-11 Thread Michael Basnight
Denis Makogon dmako...@mirantis.com writes: Goodday, OpenStack DВaaS community. I'd like to start conversation about guestagent security issue related to backup/restore process. Trove guestagent service uses AES with 256 bit key (in CBC mode) [1] to encrypt backups which are stored

Re: [openstack-dev] [python-openstacksdk] First meeting scheduled

2014-02-11 Thread Boris Pavlovic
Jesse, Why not next approach: 1) Switch all clients to apiclient[1] (internal unification) 2) Unify API of all clients (external unification) 3) Unify work with keystone 4) Graduate apiclient 5) Switch all clients to apiclient lib 6) Make one simple plugable mechanism. e.g. subclass based factory

Re: [openstack-dev] [Trove] Backup/Restore encryption/decryption issue

2014-02-11 Thread Denis Makogon
As we decided at meeting, we wouldn't keep our own implementations of security stuff, we'll use Barbican as single entry point of delivering secrets. I hadn't talked with Barbican team, but since oslo-incubator will (someday) release oslo.crypto lib for all projects, i think that adding

Re: [openstack-dev] [python-openstacksdk] First meeting scheduled

2014-02-11 Thread Jesse Noller
On Feb 11, 2014, at 3:02 PM, Boris Pavlovic bpavlo...@mirantis.com wrote: Jesse, Why not next approach: 1) Switch all clients to apiclient[1] (internal unification) This was discussed several weeks ago here: http://lists.openstack.org/pipermail/openstack-dev/2014-January/024441.html This

Re: [openstack-dev] [Trove] Replication Contract Verbiage

2014-02-11 Thread Michael Basnight
Daniel Salinas imsplit...@gmail.com writes: https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API#REPLICATION I have updated the wiki page to reflect the current proposal for replication verbiage with some explanation of the choices. I would like to open discussion here

[openstack-dev] [requirements] problems with non overlapping requirements changes

2014-02-11 Thread Sean Dague
A few weeks ago we realized one of the wrecking balls in the gate were non overlapping requirements changes, like this - https://review.openstack.org/#/c/72475/ Regular jobs in the gate have to use the OpenStack mirror. Requirements repo doesn't, because it needs to be able to test things not in

Re: [openstack-dev] oslo.config improvements

2014-02-11 Thread Shaun McCance
On Mon, 2014-02-10 at 10:50 -0500, Doug Hellmann wrote: 2) It locates options based on them being defined at the top level of a module (not in function or packed into some object), but it gets info by looking at cfg.CONF, which require

Re: [openstack-dev] [oslo-notify] notifications consumed by multiple subscribers

2014-02-11 Thread Sandy Walsh
The notification system can specify multiple queues to publish to, so each of your dependent services can feed from a separate queue. However, this is a critical bug in oslo.messaging that has broken this feature. https://bugs.launchpad.net/nova/+bug/1277204 Hopefully it'll get fixed quickly

Re: [openstack-dev] oslo.config improvements

2014-02-11 Thread Doug Hellmann
On Tue, Feb 11, 2014 at 4:38 PM, Shaun McCance sha...@gnome.org wrote: On Mon, 2014-02-10 at 10:50 -0500, Doug Hellmann wrote: 2) It locates options based on them being defined at the top level of a module (not in function or packed into some object), but it

Re: [openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack

2014-02-11 Thread Robert Collins
On 12 February 2014 05:42, Andrey Danin ada...@mirantis.com wrote: Hi Openstackers, We are working on link aggregation support in Fuel. We wonder what are the most desirable types of bonding now in datacenters. We had some issues (see below) with OVS bond in LACP mode, and it turned out that

Re: [openstack-dev] [Neutron] Support for multiple provider networks with same VLAN segmentation id

2014-02-11 Thread Vinay Bannai
One way to look at the VLANs is that it identifies a security zone that meets some regulatory compliance standards. The VLANs on each rack are separated from other VLANs by using VRF. Tenants in our case map to applications. So each application is served by a VIP with a pool of VMs. So all

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

2014-02-11 Thread Lingxian Kong
2014-02-12 0:38 GMT+08:00 Eddie Sheffield eddie.sheffi...@rackspace.com: A few days ago, I met some problems when using 'createimage' feature in Nova, we found that using V1 of glanceclient has some problem with processing of metadata, the version number and even the glance URIs are both

[openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'

2014-02-11 Thread Gary Duan
Hi, The patch I submitted for L3 service framework integration fails on jenkins test, py26 and py27. The console only gives following error message, 2014-02-12 00:45:01.710 | FAIL: process-returncode 2014-02-12 00:45:01.711 | tags: worker-1 and at the end, 2014-02-12 00:45:01.916 | ERROR:

Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'

2014-02-11 Thread Clark Boylan
On Tue, Feb 11, 2014 at 5:52 PM, Gary Duan garyd...@gmail.com wrote: Hi, The patch I submitted for L3 service framework integration fails on jenkins test, py26 and py27. The console only gives following error message, 2014-02-12 00:45:01.710 | FAIL: process-returncode 2014-02-12

Re: [openstack-dev] [Murano] Can we migrate to oslo.messaging?

2014-02-11 Thread Joshua Harlow
Is murano python3.x compatible, from what I understand oslo.messaging isn't (yet). If murano is supporting python3.x then brining in oslo.messaging might make it hard for murano to be 3.x compatible. Maybe not a problem (I'm not sure of muranos python version support). From: Serg Melikyan

Re: [openstack-dev] [Murano] Can we migrate to oslo.messaging?

2014-02-11 Thread Alexander Tivelkov
Hi Joshua, Currently we are not 3.x compatible, at least not all of the modules. Migration to python3 should eventually be done, but for now it is the least of our concerns, while relying on a non-standard messaging solution instead of community-approved one is likely to cause problems, both in

Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'

2014-02-11 Thread Gary Duan
Hi, Clark, Thanks for your reply. I thought the same thing at first, but the page by default only shows the failed cases. The other 1284 cases were OK. Gary On Tue, Feb 11, 2014 at 6:07 PM, Clark Boylan clark.boy...@gmail.comwrote: On Tue, Feb 11, 2014 at 5:52 PM, Gary Duan

Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'

2014-02-11 Thread Clark Boylan
On Tue, Feb 11, 2014 at 7:05 PM, Gary Duan garyd...@gmail.com wrote: Hi, Clark, Thanks for your reply. I thought the same thing at first, but the page by default only shows the failed cases. The other 1284 cases were OK. Gary On Tue, Feb 11, 2014 at 6:07 PM, Clark Boylan

Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'

2014-02-11 Thread Gary Duan
Clark, You are right. The test must have been bailed out. The question is what I should look for. Even a successful case has a lot of Traceback, ERROR log in subunit_log.txt. Thanks, Gary On Tue, Feb 11, 2014 at 7:19 PM, Clark Boylan clark.boy...@gmail.comwrote: On Tue, Feb 11, 2014 at 7:05

[openstack-dev] [Nova] modify_image_attribute() in ec2_api is broken in Nova

2014-02-11 Thread wu jiang
Hi all, I met some problems when testing an ec2_api:'modify_image_attribute()' in Nova. I found the params send to Nova, are not suitable to match it in AWS api. I logged it in launchpad: https://bugs.launchpad.net/nova/+bug/1272844 - 1. Here is the definition part of

Re: [openstack-dev] [Neutron] Neutron py27 test 'FAIL: process-returncode'

2014-02-11 Thread trinath.soman...@freescale.com
Hi Gary- Look into the logs with a search towards your written code keywords.. There might be some issues related to PEP8 or invalid import paths. Hope this helps. -- Trinath Somanchi - B39208 trinath.soman...@freescale.com | extn: 4048 From: Gary Duan [mailto:garyd...@gmail.com] Sent:

Re: [openstack-dev] [Fuel][TripleO] NIC bonding for OpenStack

2014-02-11 Thread Jesse Pretorius
On 11 February 2014 18:42, Andrey Danin ada...@mirantis.com wrote: We are working on link aggregation support in Fuel. We wonder what are the most desirable types of bonding now in datacenters. We had some issues (see below) with OVS bond in LACP mode, and it turned out that standard Linux