Re: [openstack-dev] [qa] trimming down Tempest smoke tag

On 1 May 2015 at 05:39, Sean Dague wrote: > On 04/30/2015 12:53 PM, Matt Riedemann wrote: > >> Yeah why would you not include admin tests? Like listing services and >> hosts in nova? > > It is extremely easy to say "why not include *, it's valid function" and > we're going to end up with an hour

Re: [openstack-dev] [magnum] Proposal for Madhuri Kumari to join Core Team

Team, Madnuri has been added to the magnum-core group [1]. Thanks everyone for your votes. Regards, Adrian [1] https://review.openstack.org/#/admin/groups/473,members On Apr 30, 2015, at 8:48 PM, Hongbin Lu mailto:hongbin...@gmail.com>> wrote: +1! On Apr 28, 2015, at 11:14 PM, "Steven Dake

Re: [openstack-dev] [Manila] Mount automation using Zeroconf

Hi, Have we considered cloud-init and qemu guest agent, I remember there was some discussion around this in the prev summit, but i couldn't find any etherpad/notes on that. I had one more question in this regards. Is it possible to do some kind of VM hotplug add operation as part of manila acces

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On 1 May 2015 at 13:24, Davanum Srinivas wrote: > One concrete suggestion based on my experience working with Kris > Lindgren on Heartbeat patch: > http://markmail.org/message/gifrt5f3mslco24j > > I could have added a "Co-Tested-By" (or "Co-Operator" - get it? :) in > my commit message which would

Re: [openstack-dev] PyCon-AU Openstack miniconf CFP open

Hi all, Just a reminder that this closes in *1 weeks time*. We're hoping to put together a great selection of OpenStack talks from developers, users and operators. If you're interested in presenting at the miniconf, please submit to the main call for proposals where we'll be picking content fr

Re: [openstack-dev] [magnum] Proposal for Madhuri Kumari to join Core Team

+1! On Apr 28, 2015, at 11:14 PM, "Steven Dake (stdake)" wrote: > Hi folks, > > I would like to nominate Madhuri Kumari to the core team for Magnum. Please > remember a +1 vote indicates your acceptance. A –1 vote acts as a complete > veto. > > Why Madhuri for core? > She participates on

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

I'm not core, but I want to +1 :) 2015-04-30 19:30 GMT+08:00 John Garbutt : > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please respond

[openstack-dev] [nova] Nova API meeting

Hi, Sorry for sending this reminder late. We have weekly Nova API meeting this week. But the meeting time was adjust. The meeting is being held today Friday UTC1200. We encourage cloud operators and those who use the REST API such as SDK developers and others who and are interested in the future

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

One concrete suggestion based on my experience working with Kris Lindgren on Heartbeat patch: http://markmail.org/message/gifrt5f3mslco24j I could have added a "Co-Tested-By" (or "Co-Operator" - get it? :) in my commit message which would have signaled a concrete contribution/feedback with specifi

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

I think it's easy to quantify a code contributor since we have systems that monitor activity - who contributed, what they contributed and when. But we don't have a system that monitors operator activity and honestly, that's the question mark for which I really don't have any answers. That might be

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On Thu, 2015-04-30 at 12:26 +0200, Flavio Percoco wrote: > I've seen the number of threads to discuss Ops topics increase in > openstack-dev and the influence of Ops - even just points of views > inherited from the feedback we've got - on reviews has gotten better > as well. Fantastic, that has al

[openstack-dev] [release] keystonemiddleware 1.6.1

The Keystone development team is happy to announce the 1.6.1 release of keystonemiddleware. This release is for the Liberty series and addresses a few minor updates in requirements and removes an excessively emitted logline when no token is found in headers passed to a service running Keystone midd

[openstack-dev] [all] pbr 0.11 released. Must read if you encounter pbr.version.SemanticVersion(XXXX), but target version ... errors

pbr 0.11 is finally released (now that Kilo is out :). This brings in more support to ensure that our version numbers are monotonically increasing. Mostly this should be unintrusive (but please do read the docs - http://docs.openstack.org/developer/pbr/#version). The key things you need to know

Re: [openstack-dev] os-ansible-deplpoyment has released Kilo

cool! From: Kevin Carter [kevin.car...@rackspace.com] Sent: Thursday, April 30, 2015 4:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] os-ansible-deplpoyment has released Kilo Hello Stackers, The OpenStack An

[openstack-dev] [OpenStack][Product Work Group] [Enterprise][API][Telco][Dev] [Security][Operators][Marketing][User Committee] Cross-Project Vancouver Work Session

The Product Work Group has formed to listen and aggregate feedback on the desired capabilities for the OpenStack platform from Customers, Users and the Developer Community (including PTLs). Using this feedback we intent to help PTLs and Contributors resolve issues that are either of strategic

[openstack-dev] [octavia] Joining Neutron under the big tent

Hi, I am proposing that Octavia is joining the Networking program as a project under the Services area. Octavia is the open scalable reference implementation for Neutron LBaaS V2 and has always seen itself as part of the networking program. We have adopted most governance rules from the Networkin

Re: [openstack-dev] [Neutron][LBaaS] Why do we need to select subnet when creating a pool?

Thanks Bharath for replying. But when I add members , I can successfully specify a member ip address from a different pool than the subnet when creating pool, hence the confusion. And theoretically, why would members for a pool have to belong to the same subnet? Date: Tue, 28 Apr 2015 17:50

[openstack-dev] [all] Why the Cloud Service Federation project is a good subject for the Cross-project track.

tl;dr I’d like to use a slot in the cross-project track to discuss the best way of managing cross-project, multi-cycle initiatives, using the forthcoming Cloud Service Federation (Broker) project to make it concrete rather than theoretical. Desired outcome: recommendations to Product group, vert

Re: [openstack-dev] [Elections] TC Election analysis

On Thu, Apr 30, 2015 at 1:28 PM, Maish Saidel-Keesing wrote: > > On 04/30/15 21:48, Joe Gordon wrote: > >> As others have done for past elections, here is a brief breakdown of the >> TC election ballot data. >> >> analysis: http://paste.openstack.org/show/213831 >> source code: http://paste.opens

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

I’m not core - but Melanie has always been very helpful with me on bug triage issues [ when I was doing that consistently ;-) ] +1 On 4/30/15, 4:30 AM, "John Garbutt" wrote: >Hi, > >I propose we add Melanie to nova-core. > >She has been consistently doing great quality code reviews[1], >alo

Re: [openstack-dev] [swift] Go! Swift!

On 1 May 2015 at 09:04, Dean Troyer wrote: > On Thu, Apr 30, 2015 at 3:28 PM, Robert Collins > wrote: >> >> Blaming pip for our problems, when we haven't been willing to go and >> contribute fixes to pip is massively unfair to the pip developers. > > > So I _really_ do not blame pip, it is by far

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

I'm not core, but I completely support Melanie's helpfulness on IRC! On Thu, Apr 30, 2015 at 6:30 AM, John Garbutt wrote: > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contribu

Re: [openstack-dev] [Elections] TC Election analysis

On 2015-04-30 23:28:53 +0300 (+0300), Maish Saidel-Keesing wrote: [...] > I am wondering why the participation level is so low. This is > really one of the few opportunities a contributor has to define > the direction of OpenStack as a whole. And yet it goes down each > election. [...] As a percen

Re: [openstack-dev] [swift] Go! Swift!

On Thu, Apr 30, 2015 at 3:28 PM, Robert Collins wrote: > Blaming pip for our problems, when we haven't been willing to go and > contribute fixes to pip is massively unfair to the pip developers. > So I _really_ do not blame pip, it is by far the best of the options, it is just (still) incomplete

[openstack-dev] os-ansible-deplpoyment has released Kilo

Hello Stackers, The OpenStack Ansible Deployment (OSAD) project is happy to announce our stable Kilo release, version 11.0.0. The project has come a very long way from initial inception and taken a lot of work to excise our original vendor logic from the stack and transform it into a community-

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

For the record, thanks for your replies guys. I am not suggesting any specific means to resolve or suggesting what we're doing is wrong; only that the current structure seems odd. The TC charter, as I read it, states that the TC committee represents everything of a technical nature of OpenStack vi

Re: [openstack-dev] [Elections] TC Election analysis

On 04/30/15 21:48, Joe Gordon wrote: As others have done for past elections, here is a brief breakdown of the TC election ballot data. analysis: http://paste.openstack.org/show/213831 source code: http://paste.openstack.org/show/213830 Some highlights are: * 3 people voted but ranked everyon

Re: [openstack-dev] [swift] Go! Swift!

On 1 May 2015 at 06:11, Dean Troyer wrote: > Honestly I don't think Go's dep system, which is still developing, is any > worse than Python's, which is also still developing. The big win for us > (devs, ops, everyone!) is that the hassles are build-time, not > install/run-time. Once you have a bu

[openstack-dev] OpenStackClient 1.2.0 release

OpenStackClient 1.2.0 has been released to PyPI. python-openstackclient can be installed from the following locations: PyPI: https://pypi.python.org/pypi/python-openstackclient OpenStack tarball: http://tarballs.openstack.org/python-openstackclient /python-openstackclient-1.2.0.tar.gz

Re: [openstack-dev] Manila client (v1.1.0) region support

Thanks Valeriy, I filed this defect: https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_manila_-2Bbug_1450613&d=AwIGaQ&c=DZ-EF4pZfxGSU6MfABwx0g&r=zHvLuN-cA8dJrDKv-7gpbBCgBAKPaAzJfG6sccaIdHHNpjwlcFjsdjPhFr9XPGnV&m=-5mRhr6zsbDKoOY59zZmnU58ZQwyrD4158jdisZVyYk&s=VFJIw949FNR9HwVoo8

Re: [openstack-dev] [Neutron] _get_subnet() in OpenContrail tests results in port deletion

The OpenContrail plugin itself doesn't even use the Neutron DB. I believe what you are observing is a side effect of the fake server they have for their tests, which does inherit the neutron DB. When you call a method on the core plugin in the contrail unit test case, it will go through their requ

Re: [openstack-dev] [swift] Go! Swift!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/30/2015 08:06 PM, John Dickinson wrote: > >> On Apr 30, 2015, at 9:52 AM, Jay Pipes >> wrote: >> >> On 04/30/2015 12:40 PM, John Dickinson wrote: >>> Swift is a scalable and durable storage engine for storing >>> unstructured data. It's bee

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On 4/30/2015 6:30 AM, John Garbutt wrote: Hi, I propose we add Melanie to nova-core. She has been consistently doing great quality code reviews[1], alongside a wide array of other really valuable contributions to the Nova project. Please respond with comments, +1s, or objections within one w

Re: [openstack-dev] [swift] Go! Swift!

Last I used it, they only had static compiling, which meant you had to rebuild all the go apps when one shared piece needed updating. That sort of thing is usually distasteful to the distro folks... Docker does the same thing in a way, and that's gaining a lot of ground these days, so maybe its

Re: [openstack-dev] Manila client (v1.1.0) region support

Hello, Joe It is bug, "region_name" is not used as should be. Feel free to file a bug for it. Kind Regards Valeriy Ponomaryov On Thu, Apr 30, 2015 at 8:23 PM, Joe Meadows wrote: > Hi, > > I work for Hitachi Data Systems (HDS) and am developing Manila support for > our HNAS line of NAS server

Re: [openstack-dev] [neutron] Need guidance - functional tests and rootwrap

So, I think I see where it is failing, but I'm not quite sure how to resolve. It appears that the functional test for the namespace module and strongswan module, will end up invoking neutron-vpn-netns-wrapper script, which is setup to point to neutron-vpnaas/services/vpn/common/netns_wrapper.py.

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

+1 and +1 for not a core :) Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC From: Davanum

[openstack-dev] [Elections] TC Election analysis

As others have done for past elections, here is a brief breakdown of the TC election ballot data. analysis: http://paste.openstack.org/show/213831 source code: http://paste.openstack.org/show/213830 Some highlights are: * 3 people voted but ranked everyone as #19 * 16% of the ballots voted for

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

+1 :-) -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Thursday, April 30, 2015 6:44 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core On 04/30/2015 07:30 AM, John Garbutt wrote: > Hi, > > I propose

Re: [openstack-dev] [swift] Go! Swift!

On 04/30/2015 12:52 PM, Jay Pipes wrote: On 04/30/2015 12:40 PM, John Dickinson wrote: Swift is a scalable and durable storage engine for storing unstructured data. It's been proven time and time again in production in clusters all over the world. We in the Swift developer community are constan

[openstack-dev] [chef] A new Core Member

I’d like to announce and congratulate Samuel Cassiba as a new core member for the Openstack-Chef project. Please congratulate and thank him for stepping up! -JJ Asghar __ OpenStack Development Mailing List (not for usage que

Re: [openstack-dev] [swift] Go! Swift!

On 04/30/2015 01:54 PM, Clint Byrum wrote: > * Go's import and build system is rather odd. Python's weird distribution > issues are at least well known in the OpenStack community. This is > actually the main reason I've never gravitated toward Go, as I feel > it is trying to be magical rather

Re: [openstack-dev] [swift] Go! Swift!

> On Apr 30, 2015, at 10:54 AM, Clint Byrum wrote: > > Excerpts from John Dickinson's message of 2015-04-30 09:40:02 -0700: >> Swift is a scalable and durable storage engine for storing unstructured >> data. It's been proven time and time again in production in clusters all >> over the world.

Re: [openstack-dev] [swift] Go! Swift!

On Thu, Apr 30, 2015 at 12:54 PM, Clint Byrum wrote: > * Go's import and build system is rather odd. Python's weird distribution > issues are at least well known in the OpenStack community. This is > actually the main reason I've never gravitated toward Go, as I feel > it is trying to be ma

Re: [openstack-dev] [swift] Go! Swift!

> On Apr 30, 2015, at 9:52 AM, Jay Pipes wrote: > > On 04/30/2015 12:40 PM, John Dickinson wrote: >> Swift is a scalable and durable storage engine for storing >> unstructured data. It's been proven time and time again in production >> in clusters all over the world. >> >> We in the Swift devel

Re: [openstack-dev] [swift] Go! Swift!

Excerpts from John Dickinson's message of 2015-04-30 09:40:02 -0700: > Swift is a scalable and durable storage engine for storing unstructured data. > It's been proven time and time again in production in clusters all over the > world. > > We in the Swift developer community are constantly looki

Re: [openstack-dev] About Sahara EDP New Ideas for Liberty

Hi Trevor you mean adding an abstract layer for basic function like run job, cancel job etc, the we implement these by specific job engine like oozie, Ooyala job server etc, right ? so I will do two things as below: (1) working on the scheduler edp jobs by oozie coordination so make sure we can r

Re: [openstack-dev] [all] Replace mysql-python with mysqlclient

On 4/30/15 11:16 AM, Dan Smith wrote: There is an open discussion to replace mysql-python with PyMySQL, but PyMySQL has worse performance: https://wiki.openstack.org/wiki/PyMySQL_evaluation My major concern with not moving to something different (i.e. not based on the C library) is the thread

Re: [openstack-dev] [all] Replace mysql-python with mysqlclient

On 4/30/15 11:00 AM, Victor Stinner wrote: Hi, I propose to replace mysql-python with mysqlclient in OpenStack applications to get Python 3 support, bug fixes and some new features (support MariaDB's libmysqlclient.so, support microsecond in TIME column). It is not feasible to use MySQLcli

Re: [openstack-dev] [qa] trimming down Tempest smoke tag

On 04/30/2015 12:53 PM, Matt Riedemann wrote: > Yeah why would you not include admin tests? Like listing services and > hosts in nova? It is extremely easy to say "why not include *, it's valid function" and we're going to end up with an hour long smoke test. At some point, you have to cut. Nov

[openstack-dev] Manila client (v1.1.0) region support

Hi, I work for Hitachi Data Systems (HDS) and am developing Manila support for our HNAS line of NAS server. The HNAS server has an internal REST server so I am implementing the Manila API natively on the server. For various reasons this is a better fit than the standard Python driver implemen

[openstack-dev] [MagnetoDB] magnetodb 2015.1 milestone release

Hello, all! MagnetoDB 2015.1 milestone has been released! https://launchpad.net/magnetodb/kilo/2015.1 https://pypi.python.org/pypi/magnetodb/2015.1 Next blueprints were implemented during this milestone: https://blueprints.launchpad.net/magnetodb/+spec/request-metrics https://blueprints

Re: [openstack-dev] [QA][Glance][Heat][Cinder] Removing the CLI tests from Tempest

On Thu, Apr 30, 2015 at 05:44:40PM +0100, Louis Taylor wrote: > On Thu, Apr 30, 2015 at 12:28:15PM -0400, Matthew Treinish wrote: > > We're now at the end of the cycle and there are 3 clients that still have > > CLI > > tests in tempest. I have pushed the patch up to remove all these tests here:

Re: [openstack-dev] [qa] trimming down Tempest smoke tag

On 4/28/2015 4:19 PM, David Kranz wrote: On 04/28/2015 06:38 AM, Sean Dague wrote: The Tempest Smoke tag was originally introduced to provide a quick view of your OpenStack environment to ensure that a few basic things were working. It was intended to be fast. However, during Icehouse the smo

Re: [openstack-dev] [swift] Go! Swift!

On 04/30/2015 12:40 PM, John Dickinson wrote: Swift is a scalable and durable storage engine for storing unstructured data. It's been proven time and time again in production in clusters all over the world. We in the Swift developer community are constantly looking for ways to improve the codeba

Re: [openstack-dev] [QA][Glance][Heat][Cinder] Removing the CLI tests from Tempest

On Thu, Apr 30, 2015 at 12:28:15PM -0400, Matthew Treinish wrote: > We're now at the end of the cycle and there are 3 clients that still have CLI > tests in tempest. I have pushed the patch up to remove all these tests here: > > https://review.openstack.org/#/c/178757/ Hi Matt, This is being wo

[openstack-dev] [swift] Go! Swift!

Swift is a scalable and durable storage engine for storing unstructured data. It's been proven time and time again in production in clusters all over the world. We in the Swift developer community are constantly looking for ways to improve the codebase and deliver a better quality codebase to u

[openstack-dev] [QA][Glance][Heat][Cinder] Removing the CLI tests from Tempest

Hi Everyone, At the beginning of the cycle I said by the end of the cycle I wanted to remove all the python-*client CLI tests from tempest since they really weren't in the scope of the project and the framework for cli testing was the first thing included in tempest-lib. [1] Additionally a cou

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On Thu, Apr 30, 2015 at 4:30 AM, John Garbutt wrote: > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please respond with comments, +1s, or

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On Thu, 2015-04-30 at 12:30 +0100, John Garbutt wrote: > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please respond with comments, +1s, or objec

Re: [openstack-dev] [all] Replace mysql-python with mysqlclient

> If we're going to move, shouldn't we be looking at something that > supports our threading model? I would prefer to make baby steps, and first fix the Python 3 compatibility. Enhance concurrency/parallelism is a much more complex project than just replacing a single line in dependencies ;-) S

Re: [openstack-dev] [all] Replace mysql-python with mysqlclient

> There is an open discussion to replace mysql-python with PyMySQL, but > PyMySQL has worse performance: > > https://wiki.openstack.org/wiki/PyMySQL_evaluation My major concern with not moving to something different (i.e. not based on the C library) is the threading problem. Especially as we move

Re: [openstack-dev] [nova][api] API working group liaisons and responsibilities

+1, i think this is really nice mike On 04/30/2015 10:54 AM, Jay Pipes wrote: Hi Stackers, OK, so Matthew Gilliard and Alex Xu have volunteered to be the Nova team's liaisons to the API working group. Big thank you to Matthew and Alex for volunteering for this important role. I've created a w

[openstack-dev] [all] Replace mysql-python with mysqlclient

Hi, I propose to replace mysql-python with mysqlclient in OpenStack applications to get Python 3 support, bug fixes and some new features (support MariaDB's libmysqlclient.so, support microsecond in TIME column). The MySQL database is popular, but the Python driver mysql-python doesn't look to

[openstack-dev] [OSSN 0048] Glance method filtering does not work under certain conditions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Glance method filtering does not work under certain conditions - --- ### Summary ### Glance is using the Python assert statement for validating the HTTP method type in its caching middleware for some image endpoints. The Python documentation states th

[openstack-dev] [nova][api] API working group liaisons and responsibilities

Hi Stackers, OK, so Matthew Gilliard and Alex Xu have volunteered to be the Nova team's liaisons to the API working group. Big thank you to Matthew and Alex for volunteering for this important role. I've created a wiki page [1] that details the responsibilities of these liaisons. If these du

Re: [openstack-dev] [infra][third-party][neutron-lbaas] git review - how to provide the URL to the test artifacts

Hello, Shane. git-review doesn't support this. You can add a comment using existing Gerrit APIs: either via SSH [0] or via HTTP [1]. [0] https://review.openstack.org/Documentation/cmd-review.html#_examples [1] https://review.openstack.org/Documentation/rest-api-changes.html#set-review On Tue, Ap

Re: [openstack-dev] [Neutron] A big tent home for Neutron backend code

On 04/29/2015 09:19 PM, Jeremy Stanley wrote: > On 2015-04-29 16:46:13 -0700 (-0700), Joe Gordon wrote: >> On Wed, Apr 22, 2015 at 12:30 PM, Kyle Mestery wrote: >>> On Wed, Apr 22, 2015 at 1:19 PM, Russell Bryant > [...] 1) Project governance has moved to a "big tent" model [1]. The vast >>

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

> I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. Extremely +1. --Dan __ OpenS

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On 04/30/2015 07:30 AM, John Garbutt wrote: Hi, I propose we add Melanie to nova-core. She has been consistently doing great quality code reviews[1], alongside a wide array of other really valuable contributions to the Nova project. Please respond with comments, +1s, or objections within one w

Re: [openstack-dev] Congrats (I think) to the new TC

On 04/30/2015 09:26 AM, David Medberry wrote: Hey guys, Congrats to the new TC leaders. http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ef1379fee7b94688 Please reach out to me (and openstack-operat...@lists.openstack.org ) if you ever need ope

[openstack-dev] [Neutron] _get_subnet() in OpenContrail tests results in port deletion

Hi, I am debugging issue observed in OpenContrail tests[1] and so far it does not look obvious. Issue: In create_port[2] new transaction is started. Port gets created, but disappears right after reading subnet from plugin in reference ipam driver[3]: >plugin = manager.NeutronManager.get_plu

[openstack-dev] Congrats (I think) to the new TC

Hey guys, Congrats to the new TC leaders. http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ef1379fee7b94688 Please reach out to me (and openstack-operat...@lists.openstack.org) if you ever need operator input (that you aren't already getting.) And many thanks for volunteering so much of your

Re: [openstack-dev] [Elections] Results of the TC Election

On Apr 30, 2015, at 8:15 AM, Tristan Cacqueray wrote: > Please join me in congratulating the 7 newly elected members of the TC. > > * Thierry Carrez > * Jay Pipes > * James E. Blair > * Flavio Percoco > * Mark McClain > * Dean Troyer > * Robert Collins Congratulations to you all! I am disappoi

Re: [openstack-dev] [Elections] Results of the TC Election

On Thu, Apr 30, 2015 at 7:15 AM, Tristan Cacqueray < tristan.cacque...@enovance.com> wrote: > Here's to Libery, and Liberty too! Thanks for officiating Tristan. -dave __ OpenStack Development Mailing List (not for usage qu

[openstack-dev] [Elections] Results of the TC Election

Please join me in congratulating the 7 newly elected members of the TC. * Thierry Carrez * Jay Pipes * James E. Blair * Flavio Percoco * Mark McClain * Dean Troyer * Robert Collins Full results: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ef1379fee7b94688 Thank you to all candidates who s

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

+1 from me as well! (Ditto as Ed, not a core). -- dims On Thu, Apr 30, 2015 at 9:00 AM, Ed Leafe wrote: > On Apr 30, 2015, at 6:30 AM, John Garbutt wrote: > >> I propose we add Melanie to nova-core. > > I know I'm not core, so my vote doesn't count, but I think that this would be > a great add

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On Apr 30, 2015, at 6:30 AM, John Garbutt wrote: > I propose we add Melanie to nova-core. I know I'm not core, so my vote doesn't count, but I think that this would be a great addition. +1 -- Ed Leafe signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On 04/30/2015 12:30 PM, John Garbutt wrote: > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please respond with comments, +1s, or objecti

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

+1. She is an excellent reviewer, and has in many other ways greatly benefited the Nova project. On 04/30/15 at 12:30pm, John Garbutt wrote: Hi, I propose we add Melanie to nova-core. She has been consistently doing great quality code reviews[1], alongside a wide array of other really valuab

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

On 04/30/2015 07:30 AM, John Garbutt wrote: > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please respond with comments, +1s, or objecti

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

+1 I think she'd be a valuable addition to the team. Michael On 30 Apr 2015 9:30 pm, "John Garbutt" wrote: > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the >

[openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

Hi, I propose we add Melanie to nova-core. She has been consistently doing great quality code reviews[1], alongside a wide array of other really valuable contributions to the Nova project. Please respond with comments, +1s, or objections within one week. Many thanks, John [1] https://review.op

[openstack-dev] [oslo][heat] Versioned objects backporting

Hello, After discussions, we've spotted possible gap in versioned objects: backporting of too-new versions in RPC. Nova does that by conductor, but not every service has something like that. I want to propose another approach: 1. Milestone pinning - we need to make single reference to versions

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On 30/04/15 12:07 +0300, Maish Saidel-Keesing wrote: On 04/30/15 10:15, Thierry Carrez wrote: Doug Hellmann wrote: Anyway, I find it curious that the TC is elected by those within the developer community but TC candidates talk about representing the operator

[openstack-dev] [fuel][plugin] Are there up to date instructions for setting up CI for a Fuel plugin?

The Fuel plugin wiki advises setting up continuous integration and links to these instructions for doing so - http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/comment-page-1/#comment-216389. That page currently has a disclaimer that some of the steps will not current

[openstack-dev] [Fuel] Transaction scheme

Hi folks! Recently I faced a pretty sad fact that in Nailgun there’s no common approach to manage transactions. There are commits and flushes in random places of the code and it used to work somehow just because it was all synchronous. However, after just a few of the subcomponents have been mo

Re: [openstack-dev] [Fuel] Nominate Julia Aranovich for fuel-web core

+1, indeed Julia's reviews are very thorough. P. On 04/30/2015 11:28 AM, Vitaly Kramskikh wrote: > Hi, > > I'd like to nominate Julia Aranovich > for fuel-web > core team. Julia's reviews are > always thor

[openstack-dev] [Fuel] Nominate Julia Aranovich for fuel-web core

Hi, I'd like to nominate Julia Aranovich for fuel-web core team. Julia's reviews are always thorough and have decent quality. She is one of the top contributors and reviewers in fuel-web repo (mostly for JS/

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

On 04/30/15 10:15, Thierry Carrez wrote: Doug Hellmann wrote: Anyway, I find it curious that the TC is elected by those within the developer community but TC candidates talk about representing the operator community who are not allowed to vote. Operators meaning Admins, Architects, etc. It soun

Re: [openstack-dev] [Fuel] Infiniband support in Fuel

Hi Sergii, As for me, if someone creates a plugin for infiniband - he may store it's "mac" address at any place, not strictly in our Nailgun model. Also, I created the request changing field length in Nailgun, but there are still possible places in Fuel library or even some other related projects

[openstack-dev] [Cinder] ABCMeta driver porting

Dear cinder driver maintainers, the abc driver porting bp got merged [1] and with this we need to refactor all cinder driver classes slightly. I hope we will manage to deprecate the usage of driver.VolumeDriver during Liberty. The porting should be very trivial (~ 2 LOC) in the most cases (see [2]

Re: [openstack-dev] [tc] Who is allowed to vote for TC candidates

Doug Hellmann wrote: >> Anyway, I find it curious that the TC is elected by those within the >> developer community but TC candidates talk about representing the operator >> community who are not allowed to vote. Operators meaning Admins, >> Architects, etc. It sounds like this is something most TC