Re: [openstack-dev] [all] -1 due to line length violation in commit messages

If anyone disagrees with the commit format, please, go ahead and fix it (It's really easy using the gerrit web) For such cosmetic changes (and others similars), we should not wait for the author to do it. Sometimes, for a stupid comma, and with all the TZ, a change can need more than a day to be

Re: [openstack-dev] [Manila] CephFS native driver

On Sat, Sep 26, 2015 at 4:32 PM, John Spray wrote: > On Sat, Sep 26, 2015 at 1:27 AM, Ben Swartzlander > wrote: > > On 09/24/2015 09:49 AM, John Spray wrote: > >> > >> Hi all, > >> > >> I've recently started work on a CephFS driver for Manila. The

Re: [openstack-dev] [nova] how to address boot from volume failures

2015-10-01 5:45 GMT+08:00 Andrew Laski : > On 09/30/15 at 05:03pm, Sean Dague wrote: > >> Today we attempted to branch devstack and grenade for liberty, and are >> currently blocked because in liberty with openstack client and >> novaclient, it's not possible to boot a server

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

+1 On 10/1/15, 10:56 AM, "Ghe Rivero" wrote: >If anyone disagrees with the commit format, please, go ahead and fix it >(It's >really easy using the gerrit web) For such cosmetic changes (and others >similars), we should not wait for the author to do it. Sometimes, for a

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

Rich Megginson writes: > On 09/30/2015 11:43 AM, Sofer Athlan-Guyot wrote: >> Gilles Dubreuil writes: >> >>> On 30/09/15 03:43, Rich Megginson wrote: On 09/28/2015 10:18 PM, Gilles Dubreuil wrote: > On 15/09/15 19:55, Sofer Athlan-Guyot wrote:

Re: [openstack-dev] [glance] Models and validation for v2

Yep, the way we removed the validation is not good long term solution (IMO) because we still requesting the schema for unvalidated_model and I am not sure why do we need it. I will create a spec about it soon so we can discuss it in more details. Best regards, Kairat Kushaev On Thu, Oct 1, 2015

Re: [openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

Ihar Hrachyshka wrote: >> Also: >> http://ttx.re/new-versioning.html >> >> And we finally publish the series / versions map at: >> http://docs.openstack.org/releases/ > > Awesome stuff! Why don’t we see major server projects there, like nova or > neutron? because they are not released for

Re: [openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

On 2015-10-01 14:30:13 +0200 (+0200), Ihar Hrachyshka wrote: > Awesome stuff! Why don’t we see major server projects there, like > nova or neutron? They haven't released yet in Liberty. If you follow the links to one of the earlier development cycles you'll see their releases listed for it (under

Re: [openstack-dev] [nova] live migration in Mitaka

On Wed, Sep 30, 2015 at 11:25:12AM +, Murray, Paul (HP Cloud) wrote: > > > Please respond to this post if you have an interest in this and what > > you would like to see done. Include anything you are already > > getting on with so we get a clear picture. > > Thank you to those who replied

Re: [openstack-dev] [Manila] CephFS native driver

On Thu, Oct 1, 2015 at 8:36 AM, Deepak Shetty wrote: > > > On Thu, Sep 24, 2015 at 7:19 PM, John Spray wrote: >> >> Hi all, >> >> I've recently started work on a CephFS driver for Manila. The (early) >> code is here: >>

Re: [openstack-dev] [Manila] CephFS native driver

On Thu, Oct 1, 2015 at 12:58 AM, Shinobu Kinjo wrote: > Is there any plan to merge those branches to master? > Or is there anything needs to be done more? As I said in the original email, this is unfinished code, and my message was just to let people know this was underway so

Re: [openstack-dev] [nova] how to address boot from volume failures

On 09/30/2015 10:41 PM, melanie witt wrote: > On Sep 30, 2015, at 14:45, Andrew Laski > wrote: > >> I have a slight preference for #1. Nova is not buggy here novaclient >> is so I think we should contain the fix there. >> >> Is using the v2 API an

Re: [openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

Jeremy Stanley wrote: > On 2015-10-01 10:54:20 +1000 (+1000), Richard Jones wrote: > [...] >> I believe that if we are moving to semver, then 12.0.0 is >> appropriate. > > Each project participating in the release is following semver > independently, with the first digit indicating the number of

Re: [openstack-dev] [nova] how to address boot from volume failures

On 10/01/15 at 06:17am, Sean Dague wrote: On 09/30/2015 10:41 PM, melanie witt wrote: On Sep 30, 2015, at 14:45, Andrew Laski > wrote: I have a slight preference for #1. Nova is not buggy here novaclient is so I think we should contain the fix

Re: [openstack-dev] [oslo] nominating Brant Knudson for Oslo core

+1 On Mon, Sep 28, 2015 at 4:37 AM Victor Stinner wrote: > +1 for Brant > > Victor > > Le 24/09/2015 19:12, Doug Hellmann a écrit : > > Oslo team, > > > > I am nominating Brant Knudson for Oslo core. > > > > As liaison from the Keystone team Brant has participated in

Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

Hi, Just a small note, we shouldn't remove it completely from Nailgun codebase, because we still have old environments to support, we should remove it from newest releases only. Thanks, On Thu, Oct 1, 2015 at 1:10 AM, Mike Scherbakov wrote: > Hi team, > where do we

Re: [openstack-dev] [Manila] CephFS native driver

On Thu, Oct 1, 2015 at 8:26 AM, Deepak Shetty wrote: >> > I think it will be important to document all of these limitations. I >> > wouldn't let them stop you from getting the driver done, but if I was a >> > deployer I'd want to know about these details. >> >> Yes,

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

Some of us are actively watching the thread / participating. I'll make sure it gets on the TC agenda in the near future. I think most of the recommendations are quite good, especially on the client support front for clients / tools within our community. On 09/30/2015 10:37 PM, Matt Fischer

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

This is now queued up for discussion this week - https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda On 10/01/2015 06:22 AM, Sean Dague wrote: > Some of us are actively watching the thread / participating. I'll make > sure it gets on the TC agenda in the near future. > > I think

[openstack-dev] [Rally][Meeting][Agenda]

Hi, its a friendly reminder that if you what to discuss some topics at Rally meetings, please add you topic to our Meeting agenda https://wiki.openstack.org/wiki/Meetings/Rally#Agenda. Don't forget to specify who will lead topic discussion. Add some information about topic(links, etc.) Thank you

Re: [openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

> On 01 Oct 2015, at 14:21, Thierry Carrez wrote: > > Jeremy Stanley wrote: >> On 2015-10-01 10:54:20 +1000 (+1000), Richard Jones wrote: >> [...] >>> I believe that if we are moving to semver, then 12.0.0 is >>> appropriate. >> >> Each project participating in the

Re: [openstack-dev] [glance] Models and validation for v2

We've been taking validation out as issues have been reported (it was removed from image-list recently for example). Removing across the board probably does make sense. Agree with you. That's why I am asking about reasoning. Perhaps, we need to realize how to get rid of this in glanceclient.

Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

Hi, Can we get the latest supported release version? We will remove from nailgun after End of Life of that particular release... -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser __ OpenStack Development

Re: [openstack-dev] [stable][glance] glance-stable-maint group refresher

On 30/09/15 12:46 +, Kuvaja, Erno wrote: Hi all, I’d like to propose following changes to glance-stable-maint team: 1) Removing Zhi Yan Liu from the group; unfortunately he has moved on to other ventures and is not actively participating our operations anymore. 2) Adding Mike

Re: [openstack-dev] [pecan] [mistral] Pecan python3 compatibility

Hi, Le 01/10/2015 15:50, Nikolay Makhotkin a écrit : In Mistral, we are trying to fix the codebase for supporting python3, but we are not able to do this since we faced issue with pecan library. If you want to see the details, see this traceback - [1]. I tried to run Mistral tests on Python 3

[openstack-dev] [ironic] Some reminders on the specs process

Hi all, Just a couple quick reminders about our specs process, given our new release model: * New specs should be proposed to the specs/approved/ directory, not a mitaka directory. * Specs approved in a previous development cycle do not need to be re-approved for Mitaka. The team reserves

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > - more changes with less infra tinkering! neutron devs should not need to go > to infra projects so often to make an impact; > -- make our little neat devstack plugin used for qos and sr-iov only a huge > pile of bash code that is

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

Sean, Thanks for bringing this topic to TC meeting. Regards, Ivan Kolodyazhny, Web Developer, http://blog.e0ne.info/, http://notacash.com/, http://kharkivpy.org.ua/ On Thu, Oct 1, 2015 at 1:43 PM, Sean Dague wrote: > This is now queued up for discussion this week - >

[openstack-dev] [pecan] [mistral] Pecan python3 compatibility

Hi, pecan folks! I have an question for you about python3 support in pecan library. In Mistral, we are trying to fix the codebase for supporting python3, but we are not able to do this since we faced issue with pecan library. If you want to see the details, see this traceback - [1]. (Actually,

Re: [openstack-dev] [magnum]swarm + compose = k8s?

Kris, I think the proposal of hierarchical projects is out of the scope of magnum, and you might need to bring it up at keystone or cross-project meeting. I am going to propose a walk-around that might work for you at existing tenancy model. Suppose there is a department (department A) with

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On 1 October 2015 at 06:45, Ihar Hrachyshka wrote: > Hi all, > > I talked recently with several contributors about what each of us plans > for the next cycle, and found it’s quite useful to share thoughts with > others, because you have immediate yay/nay feedback, and maybe

Re: [openstack-dev] [pecan] [mistral] Pecan python3 compatibility

> > > If value is a bounded method, you can replace value.im_class with > type(value.__self__). > > Yes. Python 3 does not support im_class attribute for methods. -- Best Regards, Nikolay __ OpenStack Development Mailing

[openstack-dev] [puppet] ubuntu trusty beaker jobs are broken

fog-google which is a beaker dependency dropped Ruby 1.x support, and enforces 2.x. Ubuntu Trusty does not provide Ruby 2.x so our CI is broken. Good news! A fix is ongoing in beaker to pin fog-google: https://github.com/puppetlabs/beaker/pull/973 Hopefully it will be merged & released soon. --

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

> On 01 Oct 2015, at 15:45, Ihar Hrachyshka wrote: > > Hi all, > > I talked recently with several contributors about what each of us plans for > the next cycle, and found it’s quite useful to share thoughts with others, > because you have immediate yay/nay feedback, and

[openstack-dev] [neutron] New cycle started. What are you up to, folks?

Hi all, I talked recently with several contributors about what each of us plans for the next cycle, and found it’s quite useful to share thoughts with others, because you have immediate yay/nay feedback, and maybe find companions for next adventures, and what not. So I’ve decided to ask

[openstack-dev] [ironic] Mitaka summit session proposal deadline

Hi folks, We need to have our summit sessions decided by October 15. So, I'd like to propose a couple of dates. Oct 9: session proposal deadline. Oct 12: we go through session proposals in the Ironic meeting and try to get a rough order of session priority. Sometime between Oct 12 and 15, we'll

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/30/2015 06:01 PM, Murali R wrote: > Yes, sfc without nsh is what I am looking into and I am thinking ovn can > have a better approach. > > I did an implementation of sfc around nsh that used ovs & flows from > custom ovs-agent back in mar-may. I added fields in ovs agent to send >

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Hi Fabio, The Congress team talked this over during our IRC yesterday. It looks like can meet with your team during one of our meeting slots. As far as I know the schedule for those meetings hasn't been set. But once it is I'll reach out (or you can) to discuss the day/time. Tim On Mon, Sep

Re: [openstack-dev] [heat] Traditional question about Heat IRC meeting time.

On 29/09/15 05:56, Sergey Kraynev wrote: Hi Heaters! Previously we had constant "tradition" to change meeting time for involving more people from different time zones. However last release cycle show, that two different meetings with 07:00 and 20:00 UTC are comfortable for most of our

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins wrote: > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > > - more changes with less infra tinkering! neutron devs should not need > to go to infra projects so often to make an impact; > > -- make our little neat

[openstack-dev] [all] [ptls] Proposed Design Summit track/room/time allocation

Hi PTLs, A few weeks ago I posted here the allocation of slots for each track at the Design Summit: http://lists.openstack.org/pipermail/openstack-dev/2015-September/073654.html You replied with a set of constraints, which makes it a fun scheduling problem to solve. I did my best to take those

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On Thu, Oct 01, 2015 at 11:05:29AM EDT, Kyle Mestery wrote: > On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins wrote: > > > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > > > - more changes with less infra tinkering! neutron devs should not need > > to go to

Re: [openstack-dev] [ceilometer][aodh][gnocchi] Tokyo design session planning

hi, just a reminder, please submit any topics ASAP so we can properly vote on items. if you have a feature you'd like to submit this cycle it'd greatly help your chances of merging should you present/explain your topic to us common folks. On 10/09/15 02:03 PM, gord chung wrote: hi, as

[openstack-dev] [puppet] acceptance tests status

Hi, Most of our modules have acceptance tests (run in beaker CI jobs) and they make our modules can be deployed and actually deploy OpenStack services. They are also really helpful for reviewers to validate patches do not break the module. While we are currently working on integration testing, I

Re: [openstack-dev] [Sender Auth Failure] Re: [neutron] New cycle started. What are you up to, folks?

I was wondering if you provide a little bit more background on the QoS item, "-- remove RPC upgrade tech debt that we left in L (that should open path for new QoS rules that are currently blocked by it);”. Is this related to the issue you point out in the commit message for the

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

> On 01 Oct 2015, at 17:05, Kyle Mestery wrote: > > On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins wrote: > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > > - more changes with less infra tinkering! neutron devs should not need to > >

Re: [openstack-dev] [Congress] hands on lab

Hi all, I updated the hands-on lab. Here's the newest version of the instructions: https://goo.gl/W0Rhcv Here's the newest version of the VirtualBox image: https://goo.gl/o062Kc​ Please give it a try and let me know if you run into any problems. - Alex

Re: [openstack-dev] [heat] Traditional question about Heat IRC meeting time.

+1 for 7:00 Sent from my iPhone > On Oct 1, 2015, at 10:36 PM, Zane Bitter wrote: > >> On 29/09/15 05:56, Sergey Kraynev wrote: >> Hi Heaters! >> >> Previously we had constant "tradition" to change meeting time for >> involving more people from different time zones. >>

Re: [openstack-dev] [stable][horizon] adding Doug Fish to horizon stable-maint

+1 On Thu, Oct 1, 2015 at 3:21 AM, Matthias Runge wrote: > Hello, > > I would like to propose to add > > Doug Fish (doug-fish) > > to horizon-stable-maint team. > > I'd volunteer and introduce him to stable branch policy. > > Matthias > -- > Matthias Runge

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On 1 October 2015 at 08:42, Sean M. Collins wrote: > On Thu, Oct 01, 2015 at 11:05:29AM EDT, Kyle Mestery wrote: > > On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins > wrote: > > > > > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > > > >

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

+1. From: Ghe Rivero [ghe.riv...@gmail.com] Sent: Thursday, October 01, 2015 12:56 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [all] -1 due to line length violation in commit messages If anyone

Re: [openstack-dev] [magnum]swarm + compose = k8s?

I believe keystone already supports hierarchical projects Thanks, Kevin From: Hongbin Lu [hongbin...@huawei.com] Sent: Thursday, October 01, 2015 7:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

> On 01 Oct 2015, at 17:42, Sean M. Collins wrote: > > On Thu, Oct 01, 2015 at 11:05:29AM EDT, Kyle Mestery wrote: >> On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins wrote: >> >>> On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: - more

Re: [openstack-dev] [Sender Auth Failure] Re: [neutron] New cycle started. What are you up to, folks?

Johnston, Nate wrote: I was wondering if you provide a little bit more background on the QoS item, "-- remove RPC upgrade tech debt that we left in L (that should open path for new QoS rules that are currently blocked by it);”. Is this related to the issue you point out in the commit

Re: [openstack-dev] [nova] live migration in Mitaka

On 2015-10-01 7:26 AM, Kashyap Chamarthy wrote: > On Wed, Sep 30, 2015 at 11:25:12AM +, Murray, Paul (HP Cloud) wrote: >> >>> Please respond to this post if you have an interest in this and what >>> you would like to see done. Include anything you are already >>> getting on with so we get a

[openstack-dev] [Fuel] Bugfixing status. 12 weeks before SCF.

Guys, I was not able to participate in our weekly IRC meeting. So I'd like to share our bug status for 8.0 release with offline e-mail. We have 494 Fuel bugs on Launchpad. This number can be splitted into several piles. 1) Critical and High priority bugs. We have 48 of them now. 2 in UI, 31 in

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Russell, " These logical flows look similar to OpenFlow, but it talks about network resources in the logical sense (not based on where they are physically located). I think we can implement SFC purely in the logical space. " Exactly. I was in the ovn presentation at Vancouver and at that time

Re: [openstack-dev] [Horizon] Selenium is now green - please pay attention to it

Also, please rebase patches to make sure they are passing selenium and integration, even if they have been previously verified. Yes, it¹s a little frustrating, but selenium is still non-voting so it will not block merges. Rob On 01/10/2015 19:34, "Doug Fish" wrote:

Re: [openstack-dev] [pecan] [mistral] Pecan python3 compatibility

Yep, this definitely looks like a Python3-specific bug. If you'll open a ticket, I'll take a look as soon as I get a chance :)! On 10/01/15 02:44 PM, Doug Hellmann wrote: Excerpts from Nikolay Makhotkin's message of 2015-10-01 16:50:04 +0300: Hi, pecan folks! I have an question for you

Re: [openstack-dev] [tripleo] How to selectively enable new services?

On Wed, 2015-09-30 at 21:05 +0100, Steven Hardy wrote: > Hi all, > > So I wanted to start some discussion on $subject, because atm we have > a > couple of patches adding support for new services (which is great!): > > Manila: https://review.openstack.org/#/c/188137/ > Sahara:

Re: [openstack-dev] [magnum]swarm + compose = k8s?

Do you mean this proposal http://specs.openstack.org/openstack/keystone-specs/specs/juno/hierarchical_multitenancy.html ? It looks like a support of hierarchical role/privilege, and I couldn't find anything related to resource sharing. I am not sure if it can address the use cases Kris

Re: [openstack-dev] [all] [ptls] Proposed Design Summit track/room/time allocation

On 01/10/15 17:17, Thierry Carrez wrote: > Hi PTLs, > > A few weeks ago I posted here the allocation of slots for each track at > the Design Summit: > > http://lists.openstack.org/pipermail/openstack-dev/2015-September/073654.html > > You replied with a set of constraints, which makes it a fun

[openstack-dev] [nova] It's time to update the Liberty release notes

We need to go through the changes which were tagged for release notes [1]. Generally this means anything with the UpgradeImpact tag but can also mean things with DocImpact. Here are the commits in liberty that had the UpgradeImpact tag: mriedem@ubuntu:~/git/nova$ git log --oneline -i --grep

Re: [openstack-dev] [puppet] [infra] split integration jobs

On 09/30/2015 07:37 PM, Jeremy Stanley wrote: [...] > > I don't think adding one more job is going to put a strain on our > available resources. In fact it consumes just about as much to run a > single job twice as long since we're constrained on the number of > running instances in our

Re: [openstack-dev] [Horizon] Selenium is now green - please pay attention to it

Thanks for your work on this Richard! A good place to check this is during code reviews. If you see a patch causing these tests to fail, that's a good reason to -1! Sent from my iPhone > On Sep 30, 2015, at 10:45 PM, Richard Jones wrote: > > Hi folks, > > Selenium

Re: [openstack-dev] [pecan] [mistral] Pecan python3 compatibility

Excerpts from Nikolay Makhotkin's message of 2015-10-01 16:50:04 +0300: > Hi, pecan folks! > > I have an question for you about python3 support in pecan library. > > In Mistral, we are trying to fix the codebase for supporting python3, but > we are not able to do this since we faced issue with

[openstack-dev] [Congress] Tokyo sessions

Hi all, We just got a tentative assignment for our meeting times in Tokyo. Our 3 meetings are scheduled back-to-back-to-back on Wed afternoon from 2:00-4:30p. I don't think there's much chance of getting the meetings moved, but does anyone have a hard conflict? Here's our schedule for Wed:

Re: [openstack-dev] [ops] Operator Local Patches

On 9/30/2015 5:47 PM, Matt Fischer wrote: Is the purge deleted a replacement for nova-manage db archive-deleted? It hasn't worked for several cycles and so I assume it's abandoned. On Sep 30, 2015 4:16 PM, "Matt Riedemann" >

Re: [openstack-dev] Announcing Liberty RC1 availability in Debian

On 09/30/2015 01:58 PM, Thomas Goirand wrote: > 3/ Horizon dependencies still in NEW queue > == > > It is also worth noting that Horizon hasn't been fully FTP master > approved, and that some packages are still remaining in the NEW queue. > This isn't the

Re: [openstack-dev] [Fuel][PTL] PTL Candidates Q Session

> we may mix technical direction / tech debt roadmap and process, political, and people management work of PTL. sorry, of course I meant that we rather should NOT mix these things. To make my email very short, I'd say PTL role is more political and process-wise rather than architectural. On Wed,

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Apologize typo "...us get overboard." ==> should be "... get us onboard" :) On Thu, Oct 1, 2015 at 11:38 AM, Murali R wrote: > Russell, > > " These logical flows > look similar to OpenFlow, but it talks about network resources in the > logical sense (not based on where

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Thanks a lot Tim. I really appreciate. Fabio From: Tim Hinrichs > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Thursday, October 1, 2015 at 7:40

Re: [openstack-dev] [neutron][ovn] New cycle started. What are you up to, folks?

On 10/01/2015 09:45 AM, Ihar Hrachyshka wrote: > Hi all, > > I talked recently with several contributors about what each of us > plans for the next cycle, and found it’s quite useful to share > thoughts with others, because you have immediate yay/nay feedback, > and maybe find companions for

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

(With apologies to the Who)... "Meet the new things, same as the old things" DVR - let's make it real folks :) Performance - I keep turning over rocks and finding things that just don't make sense to me... I suspect others will come a calling as we go... Ryan Moats

Re: [openstack-dev] [Horizon] Selenium is now green - please pay attention to it

On 2015-10-01 18:38:49 + (+), Rob Cresswell (rcresswe) wrote: > Also, please rebase patches to make sure they are passing selenium and > integration, even if they have been previously verified. > Yes, it¹s a little frustrating, but selenium is still non-voting so it > will not block

Re: [openstack-dev] [pecan] [mistral] Pecan python3 compatibility

Or, since many OpenStack projects now use Pecan, we could fix this ourselves as a thank you note to Pecan developers! Salvatore On 1 October 2015 at 21:08, Ryan Petrello wrote: > Yep, this definitely looks like a Python3-specific bug. If you'll open a > ticket,

[openstack-dev] [fuel][fuel-library] librarian workflows

Hey Fuel folks, We have recently had some concerns around the librarian workflows and custom patches to upstream modules. I have updated the Fuel wiki[0] with additional information to try and clarify how librarian is used within fuel-library and what the rules are around the use of custom

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

This commit brings Fuel ACLs in sync with each other and in line with the agreement on this thread: https://review.openstack.org/230195 Please review carefully. Note that I intentionally didn't touch any of the plugins ACLs, primarily to save time for us and the openstack-infra team until after

[openstack-dev] [infra][nova][all] Pillow breaking gate?

It looks like Pillow (pulled in by blockdiag, pulled in by sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably others) had a 3.0.0 release today, and now the gate is breaking because libjpeg isn't available in the image…thoughts on how best to address this problem? -- Kevin L.

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On Thu, Oct 1, 2015, at 03:48 PM, Kevin L. Mitchell wrote: > It looks like Pillow (pulled in by blockdiag, pulled in by > sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably > others) had a 3.0.0 release today, and now the gate is breaking because > libjpeg isn't available in the

[openstack-dev] [Magnum]: PTL Voting is now open

If you are a Foundation individual member and had a commit in one of Magnum's projects[0] over the Kilo-Liberty timeframe (September 18, 2014 06:00 UTC to September 18, 2015 05:59 UTC) then you are eligible to vote. You should find your email with a link to the Condorcet page to cast your vote in

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On Thu, Oct 01, 2015 at 05:48:25PM -0500, Kevin L. Mitchell wrote: > It looks like Pillow (pulled in by blockdiag, pulled in by > sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably > others) had a 3.0.0 release today, and now the gate is breaking because > libjpeg isn't available

Re: [openstack-dev] [Magnum]: PTL Voting is now open

I want to thank personally and publicly our election officials for their willingness to take care of this election. Nice work, Tony and Tristan. Much appreciated. Anne On Thu, Oct 1, 2015 at 5:58 PM, Tony Breeds wrote: > If you are a Foundation individual member and

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On Thu, 2015-10-01 at 15:53 -0700, Clark Boylan wrote: > On Thu, Oct 1, 2015, at 03:48 PM, Kevin L. Mitchell wrote: > > It looks like Pillow (pulled in by blockdiag, pulled in by > > sphinxcontrib-seqdiag, in test-requirements.txt of nova and probably > > others) had a 3.0.0 release today, and now

[openstack-dev] [operators] [cinder] Does anyone use Cinder XML API?

Hi all, I would like to ask if anybody uses Cinder XML API. AFAIR, almost one year ago XML-related tests were removed from Tempest [1]. XML API removed from Nova last year [2] and doesn't supported by Heat. I didn't check for the others projects. For now, I don't know does Cinder XML API work

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On 10/01/2015 09:23 PM, Carlos Garza wrote: > I fixed this on my local ubuntu 14.04 box by doing ³apt-get install > libjpeg-dev² > Can we just make that a low level package dependency on the images in gate > so that > We can move forward? The patch to do so has merged:

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

On 2 October 2015 at 12:00, Kevin L. Mitchell wrote: > On Thu, 2015-10-01 at 15:53 -0700, Clark Boylan wrote: >> On Thu, Oct 1, 2015, at 03:48 PM, Kevin L. Mitchell wrote: >> > It looks like Pillow (pulled in by blockdiag, pulled in by >> > sphinxcontrib-seqdiag, in

Re: [openstack-dev] [Kuryr] tox -egenconfig not working

Hi, On Wed, Sep 30, 2015 at 2:27 PM, Vikas Choudhary wrote: > Hi, > > I tried to generate sample kuryr.using "tox -e genconfig", but it is > failing: > > genconfig create: /home/vikas/kuryr/.tox/genconfig > genconfig installdeps: -r/home/vikas/kuryr/requirements.txt,

Re: [openstack-dev] [Neutron] Defect management

Hi neutrinos, Whilst we go down the path of revising the way we manage/process bugs in Neutron, and transition to the proposed model [1], I was wondering if I can solicit some volunteers to screen the bugs outlined in [2]. It's only 24 bugs so it should be quick ;) Btw, you can play with filters

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

I fixed this on my local ubuntu 14.04 box by doing ³apt-get install libjpeg-dev² Can we just make that a low level package dependency on the images in gate so that We can move forward? On 10/1/15, 5:48 PM, "Kevin L. Mitchell" wrote: >It looks like Pillow (pulled in

[openstack-dev] [Ceilometer] Capturing isolated events

Can ceilometer-gurus advise? [For Ceilometer/Juno] Use case: catch instance creation error notifications with ceilometer. I tried the notifications as well as metering route, but haven't quite figured out how to do this -- - Added a notification class to ceilometer

Re: [openstack-dev] [Kuryr] tox -egenconfig not working

If its because of an Error like "ValueError: --enable-jpeg requested but jpeg not found, aborting² triggered by a dependency pull of Python pillow which then I got around it by doing an ³apt-get install libjpeg-dev² on my ubuntu build. I agree its seemed odd when it happened on tox but not on

Re: [openstack-dev] [magnum] New Core Reviewers

+1 for both! Welcome! On Thu, Oct 1, 2015 at 7:07 AM, Hongbin Lu wrote: > +1 for both. Welcome! > > > > *From:* Davanum Srinivas [mailto:dava...@gmail.com] > *Sent:* September-30-15 7:00 PM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:*

Re: [openstack-dev] [nova] how to address boot from volume failures

>1) fix the client without a revert I prefer to go with this option, since fix already done and pending review. >This means that until people upgrade their >client they loose access to this function on the server. This applies to any of the proposed options. On Thu, Oct 1, 2015 at 12:03 AM,

[openstack-dev] What's Up, Doc? 2 October

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, Welcome to October, which means: it's nearly release day! I've been brushing up on the release management tasks, and continued my housekeeping duties to make sure we're in shape. The next two weeks will be spent watching the Installation

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

This is going to be busy cycle for me, but with many exciting and interesting topics: *Kuryr* Kuryr is starting to gain interest from the community and going to be demoed and presented in OpenStack Tokyo, i think all this positive feedback means we are on the right track and we have a very busy

Re: [openstack-dev] [infra][nova][all] Pillow breaking gate?

I've +2'ed Tony's Nova patch, but it would be nice to get another core to take a look as well. Michael On Fri, Oct 2, 2015 at 12:34 PM, Robert Collins wrote: > On 2 October 2015 at 12:00, Kevin L. Mitchell > wrote: > > On Thu,

[openstack-dev] [stable][horizon] adding Doug Fish to horizon stable-maint

Hello, I would like to propose to add Doug Fish (doug-fish) to horizon-stable-maint team. I'd volunteer and introduce him to stable branch policy. Matthias -- Matthias Runge __ OpenStack Development

Re: [openstack-dev] [nova] how to address boot from volume failures

On 09/30/2015 10:45 PM, Andrew Laski wrote: > On 09/30/15 at 05:03pm, Sean Dague wrote: >> Today we attempted to branch devstack and grenade for liberty, and are >> currently blocked because in liberty with openstack client and >> novaclient, it's not possible to boot a server from volume using

Re: [openstack-dev] [fuel][shotgun] do we still use subs?

Hey Alex, I'm +1 for removal. I don't thing shotgun should be responsible for log sanitizing, because sensitive data shouldn't get to the logs at the first place. Thanks, Igor On Wed, Sep 30, 2015 at 4:05 PM, Alexander Gordeev wrote: > Hello fuelers, > > My question is

  1   2   >