Re: [openstack-dev] Cross-project meeting, Tue Oct 13th, 21:00 UTC

2015-10-13 Thread Emilien Macchi
On 10/12/2015 10:33 AM, Emilien Macchi wrote: > Dear PTLs, cross-project liaisons, and interested team members, > > We'll have a cross-project meeting tomorrow at 21:00 UTC, with the > following agenda: > > https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda > > *

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Steve Baker
On 14/10/15 10:15, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal > wrote: All above make sense, just one thing, how about using word "zaqar" instead of messaging? That is what all other projects

Re: [openstack-dev] [cinder] RemoteFS drivers refactoring: move code, which works with images to separate classes

2015-10-13 Thread Sean McGinnis
On Tue, Oct 13, 2015 at 07:01:45PM +, D'Angelo, Scott wrote: > If you create a blueprint and a spec for this, the details can be discussed > in the spec. Yes, something like this we should definitely have a spec and blueprint for. Please write up a spec and propose to the cinder-specs repo

[openstack-dev] [ptl][release] communication during mitaka

2015-10-13 Thread Doug Hellmann
PTLs and release liaisons This is the first of what will likely be several emails describing differences in the way we will be handling release management for the Mitaka cycle. To start I want to make sure the expectations for communication are clear to everyone so there is no confusion or

Re: [openstack-dev] [puppet] Proposing Denis Egorenko core

2015-10-13 Thread Matt Fischer
On Tue, Oct 13, 2015 at 2:29 PM, Emilien Macchi wrote: > Denis Egorenko (degorenko) is working on Puppet OpenStack modules for > quite some time now. > > Some statistics [1] about his contributions (last 6 months): > * 270 reviews > * 49 negative reviews > * 216 positive

Re: [openstack-dev] [Fuel] Changes in bugs workflow on Launchpad

2015-10-13 Thread Vladimir Kuklin
Dima What I think is that we need to somehow group the bugs so that after they are initially triaged particular component developers can understand which bugs to get from the pool of unassigned bugs. Could you please show how you are going to tackle this? On Tue, Oct 13, 2015 at 11:24 PM, Mike

[openstack-dev] [Nova][Cinder][Manila] Liberty RC3 available

2015-10-13 Thread Thierry Carrez
Hello everyone, Due to Murphy's law and a mix of not-so-fun dependencies issues, we just respinned a release candidate for Nova, Cinder and Manila. The list of RC3 fixes, as well as RC3 tarballs are available at: https://launchpad.net/nova/liberty/liberty-rc3

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

2015-10-13 Thread Colleen Murphy
On Tue, Oct 13, 2015 at 6:13 AM, Vladimir Kuklin wrote: > Puppetmaster and Fuelers, > > Last week I mentioned that I would like to bring the theme of using native > ruby OpenStack client and use it within the providers. > > Emilien told me that I had already been late and

Re: [openstack-dev] [Neutron] Do not merge until further notice

2015-10-13 Thread Hirofumi Ichihara
> On 2015/10/14, at 4:07, Armando M. wrote: > > Hi folks, > > We are in the last hours of Liberty, let's pause for a second and consider > merging patches only if absolutely necessary. The gate is getting clogged and > we need to give priority to potential RC3 fixes or

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

2015-10-13 Thread Monty Taylor
On 10/13/2015 05:15 PM, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal > wrote: All above make sense, just one thing, how about using word "zaqar" instead of messaging? That is what all other

[openstack-dev] [tc] projects.yaml (project since data)

2015-10-13 Thread Shamail Tahir
Hi, In the older integrated release model we used to have a field that showed "integrated-since" data about a project. I was just reviewing the current projects.yaml[1] file and noticed that there is no information in there that shows how long a project has been under OpenStack governance. That

Re: [openstack-dev] [OpenStack-docs][Neutron] Networking Guide - Call for contributors

2015-10-13 Thread Edgar Magana
Thanks my friend! Edgar From: "John Davidge (jodavidg)" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, October 13, 2015 at 8:55 AM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [OpenStack-docs][Neutron]

[openstack-dev] [infra] Upgrade to Gerrit 2.11

2015-10-13 Thread Zaro
Hello All, The openstack-infra team would like to upgrade from our Gerrit 2.8 to Gerrit 2.11. We are proposing to do the upgrade shortly after the Mitaka summit. The main motivation behind the upgrade is to allow us to take advantage of some of the new REST api, ssh commands, and stream events

Re: [openstack-dev] [tc] projects.yaml (project since data)

2015-10-13 Thread Robert Collins
Makes sense to me. Care to propose such a change to the repo? On 14 October 2015 at 11:53, Shamail Tahir wrote: > Hi, > > In the older integrated release model we used to have a field that showed > "integrated-since" data about a project. I was just reviewing the current >

Re: [openstack-dev] [tc] projects.yaml (project since data)

2015-10-13 Thread Shamail
Sure. Thanks. > On Oct 13, 2015, at 8:55 PM, Robert Collins wrote: > > Makes sense to me. Care to propose such a change to the repo? > >> On 14 October 2015 at 11:53, Shamail Tahir wrote: >> Hi, >> >> In the older integrated release model we

Re: [openstack-dev] [TripleO] Auto-abandon bot

2015-10-13 Thread Dan Prince
On Mon, 2015-10-12 at 11:38 -0500, Ben Nemec wrote: > On 10/10/2015 08:12 AM, Jeremy Stanley wrote: > > On 2015-10-09 17:10:15 -0500 (-0500), Ben Nemec wrote: > > > As discussed in the meeting a week or two ago, we would like to > > > bring > > > back the auto-abandon functionality for old,

Re: [openstack-dev] [TripleO] review priorities etherpad

2015-10-13 Thread Dan Prince
On Tue, 2015-10-13 at 10:32 +0300, marios wrote: > On 10/10/15 00:16, Dan Prince wrote: > > On Thu, 2015-10-08 at 09:17 -0400, James Slagle wrote: > > > At the TripleO meething this week, we talked about using an > > > etherpad > > speaking of which - and given attendance since the time change, >

Re: [openstack-dev] [all] FYI - Depends-On vs. backports

2015-10-13 Thread Rochelle Grober
Could you put this in the devref? Or getting started or something so this info isn't lost and new devs will be educated? Thanks! --Rocky > -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Tuesday, October 13, 2015 2:44 AM > To: openstack-dev@lists.openstack.org >

Re: [openstack-dev] [Neutron] Do not merge until further notice

2015-10-13 Thread Armando M.
On 13 October 2015 at 16:55, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > > > > On 2015/10/14, at 4:07, Armando M. wrote: > > > > Hi folks, > > > > We are in the last hours of Liberty, let's pause for a second and > consider merging patches only if absolutely

[openstack-dev] [Neutron] Revision of the RFE/blueprint submission process

2015-10-13 Thread Armando M.
Hi neutrinos, >From last cycle, the team has introduced the concept of RFE bugs [0]. I have suggested a number of refinements over the past few days [1,2,3] to streamline/clarify the process a bit further, also in an attempt to deal with the focus and breadth of the project [4,5]. Having said

[openstack-dev] [Neutron] liberty stable branch development

2015-10-13 Thread Armando M.
Hi folks, A heads-up: we are currently experiencing a number of failures on the stable/liberty for neutron [1]. Bear with us whilst we go through the painstaking process of fixing the dependency issues that caused the recent grief. Thanks, Armando [1]

<    1   2