Re: [openstack-dev] [all][Zaqar] Call for adoption (or exclusion?)

Tagging as `[all]`, sorry about that! On 20/04/15 14:54 +0200, Flavio Percoco wrote: Greetings, I'd like my first action as Zaqar's PTL to be based on reflections and transparency with regards to what our past has been, to what our present is and to what our future could be as a project and com

[openstack-dev] [Zaqar] Call for adoption (or exclusion?)

Greetings, I'd like my first action as Zaqar's PTL to be based on reflections and transparency with regards to what our past has been, to what our present is and to what our future could be as a project and community. Therefore, I'm sending this call for adoption and support before taking other a

Re: [openstack-dev] [oslo][pbr] getting 0.11 out the door. Maybe even 1.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/20/2015 02:22 PM, Victor Stinner wrote: >> I believe Redhat patch it out. I don't think they should need >> to, since we have explicit knobs for distros to use. > > pbr pulls pip which we don't want in RHEL. Example of patches in > RDO: > > h

Re: [openstack-dev] TC candidacy

confirmed On 04/20/2015 05:56 AM, Thierry Carrez wrote: > Hello list, > > I'm announcing my candidacy for the Technical Committee elections. > > I have been serving as the chair of the Technical Committee since its > inception, but I think we are at a critical point in the evolution of > the rol

Re: [openstack-dev] [oslo][pbr] getting 0.11 out the door. Maybe even 1.0

> I don't think its a bug in the applications. swift gets its version using pkg_resources, or falls back to pbr: https://github.com/openstack/swift/blob/master/swift/__init__.py I mean that other applications may do something similar? Victor _

[openstack-dev] [taskflow][glance][debian] Issue with ordereddict

Hi, Debian are hitting this issue https://bugs.launchpad.net/glance/+bug/1445827. Currently glance and glance_store include ordereddict in their requirements.txt. Since Glance no longer gates on py26 I think it should be ok to remove that requirement from glance and glance_store (both repos ha

Re: [openstack-dev] [oslo][pbr] getting 0.11 out the door. Maybe even 1.0

> I believe Redhat patch it out. I don't think they should need to, > since we have explicit knobs for distros to use. pbr pulls pip which we don't want in RHEL. Example of patches in RDO: https://github.com/redhat-openstack/nova/commit/a19939c8f9a7b84b8a4d713fe3d26949e5664089 https://github.com/

[openstack-dev] [mistral] Mistral team meeting reminder - 04/20/2015

This is a reminder about a team meeting today that we’ll hold at #openstack-mistral at 16.20 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) What's left to do in Kilo? (critical bugs, docs etc.) Open discussion [0] https://wiki.openstack.org/wiki/Mee

Re: [openstack-dev] [nova] Dropping DB Downgrades, need Turbo Hipster tests updated

Awesome, thanks Josh. On 04/20/2015 07:14 AM, Joshua Hesketh wrote: > Hi Sean, > > Thanks for your work on this. I'll take a closer look tomorrow and remove the > downgrade testing from turbo-hipster in line with the TC decision. > > Cheers, > Josh > > F

[openstack-dev] [mistral] Mistral Kilo RC1 released!

Hi all, Another milestone of Mistral (Kilo RC1) is released! Below are the links to Mistral and Mistral Client release pages where you can find downloadables and info about fixed bugs. Mistral: https://launchpad.net/mistral/kilo/kilo-rc1 Mistral Cl

Re: [openstack-dev] [puppet] Welcome to Puppet 4.0

On 19/Apr/2015 .::. 14:18, Emilien Macchi wrote: > We are adding Puppet 4.0 unit testing jobs support as non-voting for > now: https://review.openstack.org/175145 > > The workflow will be: > * have the non-voting jobs in check pipeline > * make the test work for our modules First, rspec-puppet ha

Re: [openstack-dev] [keystone] keystone middleware package changing release method in Liberty

On 04/19/2015 12:54 PM, Morgan Fainberg wrote: > > > On Sunday, April 19, 2015, Robert Collins > wrote: > > On 18 April 2015 at 15:20, Morgan Fainberg > > wrote: > > Hi everyone, > > > > I wanted to communicate to the community that the Keys

Re: [openstack-dev] [nova] Dropping DB Downgrades, need Turbo Hipster tests updated

Hi Sean, Thanks for your work on this. I'll take a closer look tomorrow and remove the downgrade testing from turbo-hipster in line with the TC decision. Cheers, Josh From: Sean Dague Sent: Monday, 20 April 2015 8:38 PM To: OpenStack Development Mailing

Re: [openstack-dev] [all][code quality] Voting coverage job (-1 if coverage get worse after patch)

On 04/18/2015 09:30 PM, Boris Pavlovic wrote: > Hi stackers, > > Code coverage is one of the very important metric of overall code > quality especially in case of Python. It's quite important to ensure > that code is covered fully with well written unit tests. > > One of the nice thing is cover

[openstack-dev] [Rally] Rally release management changes and future worfklow

Hi all, as some of you probably know, Rally has recently adopted a release-based software development model. The latest release is 0.0.3 (appeared on Apr 14). We have set as our goal to have a new release every 2-3 weeks. Since this is quite ambitious and not so easy to achieve, we are also going

[openstack-dev] [nova] Dropping DB Downgrades, need Turbo Hipster tests updated

This proposed patch to drop the db downgrades in Nova master is making Turbo Hipster face plant - https://review.openstack.org/#/c/175010/ It appears that turbo hipster is walking all the way up, then walking back down through migrations, which clearly, is no longer a thing. It would be nice to m

Re: [openstack-dev] [oslo][pbr] getting 0.11 out the door. Maybe even 1.0

On 20 April 2015 at 22:10, Victor Stinner wrote: >> If there's nothing majorly wrong mid-L, I'd like to release 1.0.0 just >> to get us into 'ok its stable' mentality. > > I read that many packages modify the source code of libraries and > applications to avoid a dependency to pbr at runtime. Wha

Re: [openstack-dev] [neutron] [QoS] weekly meeting - update

Thank you Irena, I believe this last minute change deserves an explanation, I asked Irena to write to the list on my behalf (thank you!). I got a surgery to one of my kids scheduled on Wednesday (it’s something very mild near the ear), also it’s holiday for a few of the participants that w

Re: [openstack-dev] [oslo][pbr] getting 0.11 out the door. Maybe even 1.0

> If there's nothing majorly wrong mid-L, I'd like to release 1.0.0 just > to get us into 'ok its stable' mentality. I read that many packages modify the source code of libraries and applications to avoid a dependency to pbr at runtime. What's the status of this issue? Is pbr still used/required

[openstack-dev] [neutron] [QoS] weekly meeting - update

Hi, This week neutron QoS meeting will take place on Tuesday, April 21 at 14:00 UTC on #openstack-meeting-3. Next week, the meeting is back to its original slot: Wed at 14:00 UTC on #openstack-meeting-3. Please join if you are interested. _

[openstack-dev] TC candidacy

Hello list, I'm announcing my candidacy for the Technical Committee elections. I have been serving as the chair of the Technical Committee since its inception, but I think we are at a critical point in the evolution of the role of the Technical Committee, and if you allow it, I'd like to be aroun

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

- We should start making agenda for each meeting and publish it to Rally wiki +1 - We should do 2 meeting per week: We can do both things in one meeting. __ OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

Sorry, I have incorrectly read the proposed meeting days. Meetings of Monday and Wednesday are okay, but I agree with Roman that Monday/Thursday would be a bit better. Best regards, Mikhail Dubov Engineering OPS Mirantis, Inc. E-Mail: mdu...@mirantis.com Skype: msdubov On Mon, Apr 20, 2015 at 12

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

Hi, Agree with all proposes. But maybe it's make sense to do a bigger interval between mitings to make as much as possible work for the next meting. For example Monday/Thursday. Its not principal for me. -Thanks, Roman Vasilets. On Fri, Apr 17, 2015 at 4:26 PM, Boris Pavlovic wrote: > Rally te

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

Hi Boris, thanks for your proposal. As for the agenda, I really think it's important to have it in advance. How are we going to prepare it? Google docs? Who is going to be responsible for that? As for the meeting time, I'm ok with 15:00 UTC, as well as with some earlier time that would satisfy Y

Re: [openstack-dev] [neutron] Prefix delegation using dibbler client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 UPD: dibbler packages are now available in all Fedora updates repositories, starting from Fedora 20, plus EPEL7. Packages are called: dibbler-[client|docs|requestor|relay|server]. Specifically, you can locate them at: http://download.eng.brq.redhat

Re: [openstack-dev] [oslo][policy][neutron] oslo.policy API is not powerful enough to switch Neutron to it

On 20 April 2015 at 10:03, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/17/2015 07:49 PM, Salvatore Orlando wrote: > > == 2. filling in admin context with admin roles == > > > > Admin context object is filled with .roles attribute that is a list > > of roles

Re: [openstack-dev] [release] release critical oslo.messaging changes

Sean Dague wrote: > Proposed actions are to do both of: > > - oslo.messaging release with heartbeats off by default (simulates 1.8.0 > behavior before the heartbeat code landed) > - oslo.messaging requiring py-amqp >= 1.4.0, so that if you enable the > heartbeating, at least you are protected from

Re: [openstack-dev] [keystone] keystoneclient stable/icehouse broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/20/2015 12:34 AM, Brant Knudson wrote: > > > On Sun, Apr 19, 2015 at 3:07 PM, Brant Knudson > wrote: > > > Ever since the stable/icehouse branch was created for > python-keystoneclient it's been broken. There are a coup

Re: [openstack-dev] [packaging][neutron] --config-dir vs. --config-file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nah, pointing --config-dir, either as one or as one of many arguments, is just plain wrong. We want to have a way to set different configuration values for different services, so merging all configuration files into single pile of Neutron Configuration

Re: [openstack-dev] [oslo][policy][neutron] oslo.policy API is not powerful enough to switch Neutron to it

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/17/2015 07:49 PM, Salvatore Orlando wrote: > == 2. filling in admin context with admin roles == > > Admin context object is filled with .roles attribute that is a list > of roles considered granting admin permissions [4]. The attribute > would t

[openstack-dev] [oslo][pbr] getting 0.11 out the door. Maybe even 1.0

So, we've fixed up the semver logic. I went through the review backlog and merged the stuff that was good. One thing in particular was problematic - prompting me to put up https://review.openstack.org/#/c/174646/ - the commit this backs out added per-platform requirements.txt files, which in ligh

Re: [openstack-dev] Fwd: Integration Gerrit with Launchpad

Andreas, I missed it. Thanks for your help. Takehiro 2015-04-20 16:40 GMT+09:00 Andreas Jaeger : > On 04/20/2015 09:26 AM, Kaneko Takehiro wrote: > >> Hi, >> >> I'm managing a stackforge project and want to integrate Gerrit with >> Launchpad. >> >> Links; >>Git: https://git.openstack.org/cg

Re: [openstack-dev] Fwd: Integration Gerrit with Launchpad

On 04/20/2015 09:26 AM, Kaneko Takehiro wrote: Hi, I'm managing a stackforge project and want to integrate Gerrit with Launchpad. Links; Git: https://git.openstack.org/cgit/stackforge/rack/ Launchpad: https://launchpad.net/python-rack Project name 'rack' is duplicated in Launchpad so I n

Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]

>Yes. Totally agree. I hate it that I have to spend a giant amount of effort on one of my clouds to get a working network to my VMs when on the other cloud I get a VM that can talk to the network. >Guess which one I think should be the default behavior? Whichever one you choose to deploy with Neut

[openstack-dev] Fwd: Integration Gerrit with Launchpad

Hi, I'm managing a stackforge project and want to integrate Gerrit with Launchpad. Links; Git: https://git.openstack.org/cgit/stackforge/rack/ Launchpad: https://launchpad.net/python-rack Project name 'rack' is duplicated in Launchpad so I named our project 'python-rack'. How can I integrate

Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

Hi Ramy, Soon I'll be the responsible of the Midokura's third-party CI, which has been mute for a while because a flaky physical resources that our sys admins couldn't take care because they are overloaded of work... Count on me! On Mon, 20 Apr 2015 05:17, Asselin, Ramy wrote: > All Third-Party

<    1   2