Re: [openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

Great news! Thanks Ihar! I'm interested in working on this :) My TZ is UTC+3:00. On Wed, Nov 11, 2015 at 12:14 AM, Martin Hickey wrote: > I am interested too and will be available to the subteam. > > On Tue, Nov 10, 2015 at 9:03 PM, Sean M. Collins >

Re: [openstack-dev] [networking-ovs-dpdk]

Hi Sean, Thanks for replying back, response inline. On Mon, Nov 9, 2015 at 8:24 PM, Mooney, Sean K wrote: > Hi > Can you provide some more information regarding your deployment? > > Can you check which kernel you are using. > > uname -a Linux ubuntu 3.16.0-50-generic

Re: [openstack-dev] [Fuel][Fuel-QA][Fuel-TechDebt] Code Quality: Do Not Hardcode - Fix Things Instead

Matthew Thanks for your feedback. Could you please elaborate more on the statistics of such tech-debt eliminations? My perception is that such bugs do not ever get fixed actually jeopardizing our efforts on bugfixing and actually making our statistics manupilative. So far my suggestion is the

Re: [openstack-dev] [kuryr] gerrit/git review problem error code 10061

Hi Baohua If you have a socks proxy to hand then you could check ‘tsocks’ - http://tsocks.sourceforge.net/ or check your distro’s package manager. It’s quite ‘transparent’ proxying (over socks 4 or 5) of pretty much any process you run with it, i.e.: tsocks scp -P29418

Re: [openstack-dev] Linux kernel IPv4 configuration during the neutron installation

On 11/11/15 10:30, JinXing F wrote: > > Hi, guys: > > during the neutron installation guide, I found that we need to > config the linux kernel as bellow: > > net.ipv4.ip_forward=1 > > net.ipv4.conf.all.rp_filter=0 > > net.ipv4.conf.default.rp_filter=0 > > > the first one is the ip address

Re: [openstack-dev] [Neutron][IPAM] ML2 don't call ipam driver remove_subnet function

Hi Gary Thanks for your information, It's very helpful. Thanh 2015-11-11 14:53 GMT+07:00 Gary Kotton : > Hi, > This should be resolved with this path - > https://review.openstack.org/239885 > Good luck > Gary > > From: thanh le giang > Reply-To:

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

Hello Matt, On 11/10/2015 07:33 PM, Matt Riedemann wrote: Let me qualify by saying I'm not a Neutron person. We know that gate-tempest-dsvm-neutron-full is failing hard as of the last 24 hours [1]. An error that's been showing up in tempest runs with neutron a lot is: "AssertionError: 0 ==

Re: [openstack-dev] [neutron][tap-as-a-service] weekly meeting

On Wed, Nov 11, 2015 at 7:24 PM, Takashi Yamamoto wrote: > hi, > > i have no idea why the link is broken. probabaly meeting_id given to #startmeeting was wrong? > > today's meeting log is here: >

[openstack-dev] [fuel][puppet] Detached roles and globals.pp

Hi all. I'm starting to resolve the todo at these line[1]. To solve this I think to hardcoded the role in the file, for example: *$swift_proxies = get_nodes_hash_by_roles($network_metadata, ['primary-swift-proxy', 'swift-proxy']) ? {* *true => get_nodes_hash_by_roles($network_metadata,

Re: [openstack-dev] [HA][RabbitMQ][messaging][Pacemaker][operators] Improved OCF resource agent for dynamic active-active mirrored clustering

> On 11 Nov 2015, at 6:26 PM, bdobre...@mirantis.com wrote: > > Thank you Andrew. > Answers below. > >>> > Sounds interesting, can you give any comment about how it differs to the > other[i] upstream agent? > Am I right that this one is effectively A/P and wont function without some > kind of

Re: [openstack-dev] [fuel][puppet] Detached roles and globals.pp

On Wed, Nov 11, 2015 at 1:41 PM, Daniel Depaoli < daniel.depa...@create-net.org> wrote: > Hi all. > I'm starting to resolve the todo at these line[1]. To solve this I think > to hardcoded the role in the file, for example: > > *$swift_proxies = get_nodes_hash_by_roles($network_metadata, >

Re: [openstack-dev] [fuel] Add Fuel to OpenStack projects: status update

I didn't read Jim's note as fuel integration tests need to run on OpenStack infra as reason. To me, it comes across as that we need have a long and complete conversation with infra about what we are doing in fuel integration. The deliverables would be: what can be done now in infra, what does

Re: [openstack-dev] [Fuel][Fuel-QA][Fuel-TechDebt] Code Quality: Do Not Hardcode - Fix Things Instead

Vladimir, Bugfixes and minor refactoring often belong in separate commits. Combining "extending foo to enable bar in XYZ" with "ensuring logs from service abc are sent via syslog" often makes little sense to code reviewers. In this case it is a feature enhancement + a bugfix. Looking at it from

Re: [openstack-dev] [kuryr] gerrit/git review problem error code 10061

Hi, An alternative solution is to use https instead of ssh to interact with gerrit: # It requires a "recent" gitreview git config gitreview.scheme https git config gitreview.port 443 git review -s It requires to define a http password in gerrit (settings > HTTP Password)

Re: [openstack-dev] [oslo.messaging] State wrapping in the MessageHandlingServer

On Tue, Nov 10, 2015 at 6:46 PM, Joshua Harlow wrote: > Matthew Booth wrote: > >> My patch to MessageHandlingServer is currently being reverted because it >> broke Nova tests: >> >> https://review.openstack.org/#/c/235347/ >> >> Specifically it causes a number of tests to

[openstack-dev] Linux kernel IPv4 configuration during the neutron installation

Hi, guys: during the neutron installation guide, I found that we need to config the linux kernel as bellow: net.ipv4.ip_forward=1 net.ipv4.conf.all.rp_filter=0 net.ipv4.conf.default.rp_filter=0 the first one is the ip address translation between LAN and WLAN, the second and third command

Re: [openstack-dev] [tacker] Proposing Sripriya Seetharam to Tacker core

+1 On Tue, Nov 10, 2015 at 10:42 PM, Stephen Wong wrote: > +1 > > On Mon, Nov 9, 2015 at 6:22 PM, Sridhar Ramaswamy > wrote: > >> I'd like to propose Sripriya Seetharam to join the Tacker core team. >> Sripriya >> ramped up quickly in early Liberty

Re: [openstack-dev] [neutron][tap-as-a-service] weekly meeting

Sounds interesting! I'd like to look at some past meeting logs (including from today), but the 'past meetings' link at http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting does not work for me. Neil -Original Message- From: Takashi Yamamoto [mailto:yamam...@midokura.com]

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Dmitry, I propose to give needed linux capabilities (like CAP_NET_BIND_SERVICE) to processes (services) which needs them and then start these processes from non-privileged user. It will give you ability to run each process without 'sudo' at all with well fine-grained permissions. On Tue, Nov 10,

Re: [openstack-dev] [Fuel][fuel] How can I install Redhat-OSP using Fuel

On Tue, Nov 10, 2015 at 02:15:02AM +, Fei LU wrote: >Greeting Fuel teams, >My company is working on the installation of virtualization >infrastructure, and we have noticed Fuel is a great tool, much better than >our own installer. The question is that Mirantis is currently

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

On 11/9/2015 9:59 PM, Vikram Choudhary wrote: Hi Cathy, Could you please check on this. My mother passed away yesterday and I will be on leave for couple of weeks. I'm very sorry to hear that. Please take all the time you need.

Re: [openstack-dev] [neutron][tap-as-a-service] weekly meeting

Hi, TAAS looks great for traffic monitoring. Some questions about TAAS. 1) Can TAAS be used for provider networks as well, or just for tenant networks ? 2) Will there be any performance impact is every neutron port and every packet is mirrored/duplicated ? 3) How is TAAS better than a

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

On 10/11/15 11:32, Adam Young wrote: On 11/10/2015 10:28 AM, Renat Akhmerov wrote: On 09 Nov 2015, at 20:43, Adam Young wrote: On 11/06/2015 06:28 PM, Tim Hinrichs wrote: Congress allows users to write a policy that executes an action under certain conditions. The

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

> Unfortunately, you're trying to work around misuse of the cloud API's, not > missing features from them. Don't use those volume types, and don't build > systems that rely on single ports and interfaces. IMO rebuild is a misguided > concept (something that took me a long time to realize).

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On 10 November 2015 at 12:08, Dmitry Tantsur wrote: > On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: > >> Hi, >> >> In the last Ironic meeting [1] we started a discussion about whether >> we need to have a mid-cycle meeting for the Mitaka cycle or not. Some >> ideas

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

On 11/11/2015 11:01 AM, Murray, Paul (HP Cloud) wrote: Unfortunately, you're trying to work around misuse of the cloud API's, not missing features from them. Don't use those volume types, and don't build systems that rely on single ports and interfaces. IMO rebuild is a misguided concept

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

I'm in the middle of deploying a keystone cluster to support multiple regions. We were told we wouldn't need rabbit for this case. Just something to keep in mind. Keystone's kind of unique in that it can be shared between regions. Thanks, Kevin From:

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Zane Bitter's message of 2015-11-11 09:43:43 -0800: > 1. Keystone (or some Rabbit->Zaqar proxy service reading notifications > from Keystone) sends "new federated user" notification out via Zaqar. > 2. Mistral picks up the message and checks policy to see what should be > done. >

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

Excerpts from Murray, Paul (HP Cloud)'s message of 2015-11-11 09:01:16 -0800: > > Unfortunately, you're trying to work around misuse of the cloud API's, not > > missing features from them. Don't use those volume types, and don't build > > systems that rely on single ports and interfaces. IMO

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

On 09/11/15 11:55, Adam Young wrote: On 11/09/2015 10:57 AM, Tim Hinrichs wrote: Congress happens to have the capability to run a script/API call under arbitrary conditions on the state of other OpenStack projects, which sounded like what you wanted. Or did I misread your original question?

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

My order of preference would be: 1. Coordinated regional mid-cycles 2. Normal mid-cycle 3. Virtual mid-cycle 4. No mid-cycle Thanks, John On Tue, Nov 10, 2015 at 10:45 AM, Lucas Alvares Gomes wrote: > Hi, > > In the last Ironic meeting [1] we started a discussion about

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 09/11/15 21:30 -0600, Matt Riedemann wrote: On 11/9/2015 9:12 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600: On

Re: [openstack-dev] [puppet] ::db classes

On Wed, Nov 11, 2015 at 9:50 AM, Clayton O'Neill wrote: > I discovered this issue last night and opened a bug on it ( > https://bugs.launchpad.net/puppet-tuskar/+bug/1515273). > > This effects most of the modules, and the short version of it is that the > defaults in all the

[openstack-dev] [puppet] ::db classes

I discovered this issue last night and opened a bug on it ( https://bugs.launchpad.net/puppet-tuskar/+bug/1515273). This effects most of the modules, and the short version of it is that the defaults in all the ::db classes are wrong for max_pool_size and max_overflow. We’re setting test to 10

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

2015-11-11 16:38 GMT+03:00 Thierry Carrez : > > date_fix_committed is probably not set if we directly switch the bug to > "Fix released", and that is what we plan to do now with Launchpad bugs. > > We might therefore need a backward-compatible patch to Stackalytics so >

Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils

> On Nov 11, 2015, at 3:54 AM, Andrey Kurilin wrote: > > > > On Tue, Nov 10, 2015 at 4:25 PM, Sean Dague > wrote: > On 11/10/2015 08:24 AM, Andrey Kurilin wrote: > >>It was also proposed to reuse openstackclient or the openstack

Re: [openstack-dev] [nova] [doc] [api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Great! I'll help out on this side of the world. Before the 8th, please review this patch to re-arrange and publish the Compute API Guide (concept topics) to developer.openstack.org. nova: https://review.openstack.org/#/c/230186/ It depends on this one in infra:

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

Excerpts from Ilya Shakhat's message of 2015-11-11 17:17:58 +0300: > 2015-11-11 16:38 GMT+03:00 Thierry Carrez : > > > > > date_fix_committed is probably not set if we directly switch the bug to > > "Fix released", and that is what we plan to do now with Launchpad bugs. > >

Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils

On Tue, Nov 10, 2015 at 4:25 PM, Sean Dague wrote: > On 11/10/2015 08:24 AM, Andrey Kurilin wrote: > >>It was also proposed to reuse openstackclient or the openstack SDK. > > > > Openstack SDK was proposed a long time ago(it looks like it was several > > cycles ago) as

Re: [openstack-dev] [oslo] Graduate apiclient library

Hi! I really like the idea of graduation apiclient to separate library. On Tue, Nov 10, 2015 at 8:29 AM, Kekane, Abhishek < abhishek.kek...@nttdata.com> wrote: > Hi Devs, > > In the Mitaka design summit session [1], it was decided to create a new > library apiclient with completely new code

Re: [openstack-dev] [telemetry][gnocchi] defining scope/domain

On Tue, Nov 10 2015, gord chung wrote: Hi Gordon, > i was doing some googling on the current state of time series databases to see > if there was a worthwhile db to implement as a Gnocchi driver and it seems > we're currently in the same state as before: there are flaws with all open > source

Re: [openstack-dev] [neutron][tap-as-a-service] weekly meeting

hi, i have no idea why the link is broken. today's meeting log is here: http://eavesdrop.openstack.org/meetings/tap_as_a_service_meeting/2015/tap_as_a_service_meeting.2015-11-11-06.36.html On Wed, Nov 11, 2015 at 7:08 PM, Neil Jerram wrote: > Sounds interesting!

Re: [openstack-dev] [fuel][puppet] Detached roles and globals.pp

Hi, I think something like this would be more flexible: $swift_proxy_roles = hiera('swift_proxy_roles', ['primary-controller', 'controller']) $swift_storage_roles = hiera('swift_storage_roles', ['primary-controller', 'controller']) # ... $swift_nodes =

Re: [openstack-dev] [Fuel][fuel] How can I install Redhat-OSP using Fuel

Hi, Fei It seems you will need to do several things with Fuel - create a new release, associate your cluster with it when creating it and provide paths to corresponding repositories with packages. Also, you will need to create a base image for Image-based provisioning. I am not sure we have all

Re: [openstack-dev] [nova][docs][api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Sorry, add [docs] and [api] tags to the title! 2015-11-11 20:51 GMT+08:00 Alex Xu : > Hi, > > At nova api subteam weekly meeting, we decided hold 2 days virtual doc > sprint to help the Nova API document. The initial proposed date is Dec 8 > and 9(Let me know if the date is

Re: [openstack-dev] [HA][RabbitMQ][messaging][Pacemaker][operators] Improved OCF resource agent for dynamic active-active mirrored clustering

Hi, Andrew Let me answer your questions. This agent is active/active which actually marks one of the node as 'pseudo'-master which is used as a target for other nodes to join to. We also check which node is a master and use it in monitor action to check whether this node is clustered with this

Re: [openstack-dev] [fuel][puppet] Detached roles and globals.pp

With before you mean before in globals.pp or in another module? The best solution should be add it in override plugin module, but it is executed after globals so it has no effect on globals. On Wed, Nov 11, 2015 at 12:13 PM, Sergey Vasilenko wrote: > > On Wed, Nov 11,

Re: [openstack-dev] [Ironic][Nova][Neutron] Multi-tenancy support

Hi Vasyl, I have not cross checked every patch in your list, but, the list looks about right. >From the Ironic, Nova, and Neutron point of the code is pretty much in place with these patches. In this week's meeting we discussed the plan for merging these patches. Couple of things are holding us

Re: [openstack-dev] [Nova] live migration sub-team meeting

So, to confirm: The live migration IRC meeting will be held on: Tuesdays at 1400 UTC in #openstack-meeting-3, starting next week: Tuesday 17th November. See: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration On that page you will find links the tracking pages and bugs. Please check

[openstack-dev] [nova] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Hi, At nova api subteam weekly meeting, we decided hold 2 days virtual doc sprint to help the Nova API document. The initial proposed date is Dec 8 and 9(Let me know if the date is conflict with other thing). The sprint is running on local time for folks. Peoples can work on the patch and also

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

Ilya Shakhat wrote: > Doug, > > You are right, there should not be any changes in the stats. Bugs are > mapped to release only by date, target milestone is not taken into > account. For resolved bugs metric Stackalytics uses 'date_fix_commited' > field, for filed bugs metric - 'date_created'.

[openstack-dev] [neutron] [networking-sfc] We will resume our weekly Service Chain project IRC meeting starting on 11/12/2015

Hi everyone, Here is the meeting info: Weekly on Thursday at 1700 UTC in #openstack-meeting-4 (IRC webclient) . Due to the day time saving change, the

[openstack-dev] [Fuel][Infra] HA deployment tests on nodepool

Hi, everyone, in Fuel project we run two HA deployment tests for every commit in openstack/fuel-library repository. Currently these tests are run by Fuel CI - the standalone Third-Party CI system, which can vote on openstack/fuel* projects. But we'd like it to be the part of the gate. As

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Excerpts from Clint Byrum's message of 2015-11-11 10:57:26 -0800: > Excerpts from Morgan Fainberg's message of 2015-11-10 20:17:12 -0800: > > On Nov 10, 2015 16:48, "Clint Byrum" wrote: > > > > > > Excerpts from Morgan Fainberg's message of 2015-11-10 15:31:16 -0800: > > > > On

[openstack-dev] [QA] Meeting Thursday November 12th at 9:00 UTC

[QA] Meeting Thursday November 12th at 9:00 UTC Hi everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, October 1st at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

Re: [openstack-dev] [QA] Meeting Thursday November 12th at 9:00 UTC

Hi everyone, # Sorry for sending this main again. # My previous mail contains some bugs. Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, November 12th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

[openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

hello all: I will update some Magnum functional testing status, functional/integration testing is important to us, since we change/modify the Heat template rapidly, we need to verify the modification is correct, so we need to cover all templates Magnum has. and currently we only has k8s

Re: [openstack-dev] [nova] live migration management approach

> -Original Message- > From: Paul Carlton [mailto:paul.carlt...@hpe.com] > Sent: Tuesday, November 10, 2015 4:51 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [nova] live migration management approach > > All > > I inherited the task of

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

Eli, I like this proposed approach. We did have a discussion with a few Stackers from openstack-infra in Tokyo to express our interest in using bare metal for gate testing. That’s still a way out, but that may be another way to speed this up further. A third idea would be to adjust the nova

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

Agree with Paul and Louis. The networking-sfc repo should be preserved to support the service function chain functionality. Flow classifier is just needed to specify what flows will go through the service port chain. The flow classifier API is designed as a separate plugin which is independent

Re: [openstack-dev] [Fuel] Default PostgreSQL server encoding is 'ascii'

Hello, Yeah, that's true. There shouldn't be any VBox specific hacks, and I believe PostgreSQL uses locale's encoding by default (which is ASCII in containers). Well, basically the bug should be assigned on library team - we should specify UTF-8 explicitly in PostgreSQL config, since Nailgun

[openstack-dev] [searchlight] Feature request and bug workflow

Searchlighters, When we began this project, we had many discussions about process and made a conscious decision to support as lightweight of a workflow for feature requests as possible. We all discussed how we want to encourage contribution from everybody by supporting both developers and

Re: [openstack-dev] [nova][cinder] About rebuilding volume-backed instances.

On 2015-11-11 11:25:09 -0600 (-0600), Chris Friesen wrote: > I didn't think that the overhead of deleting/creating an instance was *that* > much different than rebuilding an instance. > > Do you have any information about where the "significant performance > advantage" was coming from? The main

[openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (greg hill)

Greetings all stackers, I propose that we add Greg Hill[1] to the taskflow-core[2] team. Greg (aka jimbo) has been actively contributing to taskflow for a while now, both in helping make taskflow better via code contribution(s) and by helping spread more usage/knowledge of taskflow at rackspace

[openstack-dev] [app-catalog] IRC Meeting Thursday November 12th at 17:00UTC

Greetings! Our next OpenStack Community App Catalog meeting will take place this Thursday November 12th at 17:00 UTC in #openstack-meeting-3 The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog Please add agenda items if there's anything specific you would like to

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/11/2015 8:51 AM, Flavio Percoco wrote: On 09/11/15 21:30 -0600, Matt Riedemann wrote: On 11/9/2015 9:12 PM, Matthew Treinish wrote: On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote: On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote: Excerpts from Matt

[openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

Folks, Any concerns? please chime in: https://review.openstack.org/244275 Thanks -- Dims -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [release][stackalytics] possibly breaking bug closing statistics?

On 12 November 2015 at 03:17, Ilya Shakhat wrote: > 2015-11-11 16:38 GMT+03:00 Thierry Carrez : >> >> >> date_fix_committed is probably not set if we directly switch the bug to >> "Fix released", and that is what we plan to do now with Launchpad bugs.

Re: [openstack-dev] [Neutron] Stop pushing stuff to the gate queue

On 10 November 2015 at 12:13, Armando M. wrote: > Neutron Cores, > > We have high failure rate (see [1] for more context). We have an initial > bug report [2] filed, and more triaged is happening. > > Let's hold on before we push stuff to the gate queue. Once [2] is solved >

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

On Nov 11, 2015 10:57, "Clint Byrum" wrote: > > Excerpts from Morgan Fainberg's message of 2015-11-10 20:17:12 -0800: > > On Nov 10, 2015 16:48, "Clint Byrum" wrote: > > > > > > Excerpts from Morgan Fainberg's message of 2015-11-10 15:31:16 -0800: > > > > On

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (greg hill)

+1 from me! On Wed, Nov 11, 2015 at 3:02 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Greg Hill[1] to the taskflow-core[2] team. > > Greg (aka jimbo) has been actively contributing to taskflow for a > while now, both in helping make taskflow

Re: [openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

On Wed, 2015-11-11 at 14:14 -0500, Davanum Srinivas wrote: > Any concerns? please chime in: > https://review.openstack.org/244275 Commented on the review, but I have to point out that python-novaclient, which, to my knowledge, still supports Python 2.6, also happens to depend on oslo.i18n,

Re: [openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

Kevin, right, that's exactly the intention of this email :) we should drop py2.6 from python-novaclient as well -- Dims On Wed, Nov 11, 2015 at 3:07 PM, Kevin L. Mitchell wrote: > On Wed, 2015-11-11 at 14:14 -0500, Davanum Srinivas wrote: >> Any concerns? please

Re: [openstack-dev] [ceilometer] proposal to add Rohit Jaiswal to Ceilometer core

thanks for the feedback. it's my pleasure to welcome Rohit to the Ceilometer core team. everyone back to work! :) On 05/11/15 08:45 AM, gord chung wrote: hi folks, i'd like to nominate Rohit Jaiswal as core for Ceilometer. he's done a lot of good work recently like discovering and fixing

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (greg hill)

+1 Excerpts from Davanum Srinivas (dims)'s message of 2015-11-11 15:05:37 -0500: > +1 from me! > > On Wed, Nov 11, 2015 at 3:02 PM, Joshua Harlow wrote: > > Greetings all stackers, > > > > I propose that we add Greg Hill[1] to the taskflow-core[2] team. > > > > Greg (aka

[openstack-dev] [reno] [release] Where do release notes of stable branches go?

I’m setting up reno for murano repository and been testing and playing with it a bit and this question seems unclear to me. So where should we put release notes for stable releases? Into respective branches or into master? --  Kirill Zaitsev Murano team Software Engineer Mirantis,

Re: [openstack-dev] [Fuel][Fuel-QA][Fuel-TechDebt] Code Quality: Do Not Hardcode - Fix Things Instead

Folks, I have one thing to add: if workaround is unavoidable, please DO comment it. Usually workaround aren't obvious, and it would be incredibly helpful to comment all of them; and do not hesitate to write extensive comments. The clearer you write - the less time your colleagues will spend next

Re: [openstack-dev] Help with getting keystone to migrate to Debian testing: fixing repoze.what and friends

Excerpts from Morgan Fainberg's message of 2015-11-10 20:17:12 -0800: > On Nov 10, 2015 16:48, "Clint Byrum" wrote: > > > > Excerpts from Morgan Fainberg's message of 2015-11-10 15:31:16 -0800: > > > On Tue, Nov 10, 2015 at 3:20 PM, Thomas Goirand wrote: > > >

Re: [openstack-dev] [oslo.messaging] State wrapping in the MessageHandlingServer

Matthew Booth wrote: On Tue, Nov 10, 2015 at 6:46 PM, Joshua Harlow > wrote: Matthew Booth wrote: My patch to MessageHandlingServer is currently being reverted because it broke Nova tests:

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (greg hill)

+1 Greg has been actively contributing to taskflow, both code, code review, and general discussions and helping users. It would be great to have him as a core. On Wed, Nov 11, 2015 at 12:02 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Greg

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

On 11/10/2015 8:30 AM, Sean M. Collins wrote: On Mon, Nov 09, 2015 at 07:58:34AM EST, Jay Pipes wrote: 2) Keep the security-group API as-is to keep outward compatibility with AWS. Create a single, new service-groups and service-group-rules API for L2 to L7 traffic classification using mostly

Re: [openstack-dev] [Fuel][fuel] How can I install Redhat-OSP using Fuel

Hey Fei LU, Thanks for being interested in Fuel. I'll help you with pleasure. First of all, as Vladimir mentioned, you need to create a new release. That's could be done by POST request to /api/v1/releases/. You can use JSON of CentOS with slight changes. When releases is created you need to do

[openstack-dev] [Neutron] Priority management for new features

Hi neutronians, Whilst I recover from the gate failure binge eating...I wanted to put out there a couple of process changes that should help the drivers team and the PTL to improve their ability to justify priority assignments for new features. Comments welcome. Cheers, Armando [1]

Re: [openstack-dev] [oslo][all] Oslo libraries dropping python 2.6 compatability

On 2015-11-11 14:07:25 -0600 (-0600), Kevin L. Mitchell wrote: > On Wed, 2015-11-11 at 14:14 -0500, Davanum Srinivas wrote: > > Any concerns? please chime in: > > https://review.openstack.org/244275 > > Commented on the review, but I have to point out that python-novaclient, > which, to my

Re: [openstack-dev] [Neutron] Priority management for new features

On Wed, Nov 11, 2015 at 4:19 PM, Armando M. wrote: > Hi neutronians, > > Whilst I recover from the gate failure binge eating...I wanted to put out > there a couple of process changes that should help the drivers team and the > PTL to improve their ability to justify priority

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On Wed, Nov 11, 2015 at 11:16 AM, Ruby Loo wrote: > On 10 November 2015 at 12:08, Dmitry Tantsur wrote: > >> On 11/10/2015 05:45 PM, Lucas Alvares Gomes wrote: >> >>> Hi, >>> >>> In the last Ironic meeting [1] we started a discussion about whether >>>

Re: [openstack-dev] [stackalytics] [metrics] Review metrics: average numbers

Hi, Mike, I'm not sure what you are looking for exactly, but maybe you can have a look at the quarterly reports. AFAIK, currently there is none specific to Fuel, but for example for Nova, you have: http://activity.openstack.org/dash/reports/2015-q3/pdf/projects/nova.pd f In page 6, you have

[openstack-dev] [stackalytics] Review metrics: average numbers

Hi stackers, I have a question about Stackalytics. I'm trying to get some more data from code review stats. For Fuel, for instance, http://stackalytics.com/report/reviews/fuel-group/open shows some useful stats. Do I understand right, that average numbers here are calculated out of open reviews,

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Wed, Nov 11, 2015 at 10:14 AM Clint Byrum wrote: > > But as Renat mentioned, the part about triggering Mistral workflows from > > a message does not yet exist. As Tim pointed out, Congress could be a > > solution to that (listening for a message and then starting

Re: [openstack-dev] [reno] [release] Where do release notes of stable branches go?

Excerpts from Kirill Zaitsev's message of 2015-11-12 00:26:02 +0300: > I’m setting up reno for murano repository and been testing and playing with > it a bit and this question seems unclear to me. > > So where should we put release notes for stable releases? Into respective > branches or into

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On Wed, Nov 11, 2015 at 3:15 AM, Lucas Alvares Gomes wrote: > > So, what people think about it? Should we have a mid-cycle for the > Mitaka release or not? If so, what format should we use? > I like the idea of having a midcycle as it's a useful sync point, so my

Re: [openstack-dev] [HA][RabbitMQ][messaging][Pacemaker][operators] Improved OCF resource agent for dynamic active-active mirrored clustering

> On 11 Nov 2015, at 11:35 PM, Vladimir Kuklin wrote: > > Hi, Andrew > > Let me answer your questions. > > This agent is active/active which actually marks one of the node as > 'pseudo'-master which is used as a target for other nodes to join to. We also > check which

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

Paul, Agree completely that the networking-sfc repo should be preserved as it includes functionality beyond that of just a classifier - it defines the service chain structure. Work on a common service classifier API could be done by the networking-sfc team to help in evaluating that API. -

Re: [openstack-dev] [Neutron] Priority management for new features

On 11 November 2015 at 13:58, Kyle Mestery wrote: > On Wed, Nov 11, 2015 at 4:19 PM, Armando M. wrote: > >> Hi neutronians, >> >> Whilst I recover from the gate failure binge eating...I wanted to put out >> there a couple of process changes that should

Re: [openstack-dev] [fuel] Using upstream packages & modules

On Tue, Nov 10, 2015 at 11:10 AM, Vladimir Kuklin wrote: > Alex > > Thanks for your very detailed answer - it clarified things a bit. So, if you > would allow me to rephrase it - you are actually conducting a research on > what is the actual gap between our downstream/fork

Re: [openstack-dev] [all] [dlm] Zookeeper and openjdk, mythbusted

On Mon, 2015-11-09 at 10:19 -0500, Adam Young wrote: > I personally like Java, but feel like we should focus on limiting the > number of languages we need to understand in order to Do OpenStack > development. That's a quite useful datapoint to collect in surveys: How many languages are your

Re: [openstack-dev] [searchlight] Feature request and bug workflow

I've already spoken to you about this and I think everyone would agree that for large features blueprints are cumbersome; my preference would be for simple blueprints (uncontroversial and straightforward from a design perspective) to leave a full description in launchpad but for larger ones to

Re: [openstack-dev] [all] [dlm] Zookeeper and openjdk, mythbusted

development is different then dependencies... So erlang is a dependency for rabbit, but no one in openstack currently writes anything in erlang. zookeeper would be a dependency, not a target for development that being said, openstack at present doesn't have any hard dependencies on java,

Re: [openstack-dev] [Oslo][TaskFlow] Proposal for new core reviewer (greg hill)

Looks like he's doing good reviews so +1. - Brant On Wed, Nov 11, 2015 at 2:02 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Greg Hill[1] to the taskflow-core[2] team. > > Greg (aka jimbo) has been actively contributing to taskflow for a >