Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

Hi, keystone devs, Thank you for your many comments about my patch [1]. I modified this patch in reference to your comments. I want to get many opinions about this new Patch Set. Could you review it? [1]: https://review.openstack.org/#/c/261188/ Thank you, On Tue, 31 May 2016 20:46:36 +0900

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Jul 13, 2016, at 9:38 PM, Cheng, Yingxin wrote: >>Thinking about that a bit, it would seem that a host aggregate could also >> be represented as a namespace:name tag. That makes sense, since the fact >> that a host belongs to a particular aggregate is a

[openstack-dev] [tricircle]cancellation of weekly meeting of Jul.13

Due to flight delay, this weekly meeting of the Tricircle project will be canceled. Sent from HUAWEI AnyOffice 发件人：黄朝意 收件人：openstack-dev, 时间：2016-07-06 14:15:43 主题:[openstack-dev][tricircle]agenda of weekly meeting of Jul.6 Hi, team, IRC meeting:

Re: [openstack-dev] [nova][qa] When do we need tests for microversions in Tempest?

Hi Matt, 2016-07-14 11:55 GMT+09:00 Matt Riedemann : > There are several changes in Tempest right now trying to add response schema > validation for the 2.26 microversion which added server tags to the server > GET response. This is needed for anything testing a

Re: [openstack-dev] [nova][qa] When do we need tests for microversions in Tempest?

On Wed, Jul 13, 2016 at 09:55:33PM -0500, Matt Riedemann wrote: > There are several changes in Tempest right now trying to add response schema > validation for the 2.26 microversion which added server tags to the server > GET response. This is needed for anything testing a microversion >=2.26, >

[openstack-dev] [nova][qa] When do we need tests for microversions in Tempest?

There are several changes in Tempest right now trying to add response schema validation for the 2.26 microversion which added server tags to the server GET response. This is needed for anything testing a microversion >=2.26, which several people are trying to add. We have a similar issue with

Re: [openstack-dev] [Neutron] MultiTenant support for VLAN-Aware-VM

On 13 July 2016 at 16:51, Kevin Benton wrote: > Sub ports are just regular ports from a logical model perspective, right? > If so, there should be no problem attaching the port to a shared network or > RBAC granted network. > True, but I don't believe it until I test it :) On

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 7/14/16, 05:42, "Ed Leafe" wrote: On Jul 12, 2016, at 2:43 AM, Cheng, Yingxin wrote: > 4. Capabilities are managed/grouped/abstracted by namespaces, and scheduler can make decisions based on either cap_names or cap_namespaces > 5.

[openstack-dev] Openstack-CEPH-Developer Opportunity-Bangalore, India

Hello Openstack community, I am looking for hiring Openstack & CEPH developers for my team in Bangalore, if anyone keen to explore, do unicast me at jhusthi...@walmartlabs.com. Sorry folks for using this forum, thought of dropping a note. Thanks,

Re: [openstack-dev] [Gluon] Project Creation and Weekly Team Meeting starts on 07/13/2016 at 1800UTC Wednesdays

https://wiki.openstack.org/wiki/Meetings/Gluon/Agenda-20160713 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/c

[openstack-dev] [Neutron][networking-sfc] meeting topics for 7/14/2016 networking-sfc project IRC meeting

Hi everyone, The following link shows the topics I have for this week's project meeting discussion. Feel free to add more. https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting Meeting Info: Every Thursday 1700 UTC on #openstack-meeting-4 Thanks, Cathy

Re: [openstack-dev] [Neutron] MultiTenant support for VLAN-Aware-VM

Sub ports are just regular ports from a logical model perspective, right? If so, there should be no problem attaching the port to a shared network or RBAC granted network. On Jul 13, 2016 7:15 PM, "Armando M." wrote: > > > On 13 July 2016 at 15:32, Cathy Zhang

[openstack-dev] [craton] Craton developer meeting Thurs July 14 at 1700 UTC

Please join us this Thursday for our weekly Craton developer video meeting. To better accommodate people from Europe, we have moved the time for this and subsequent Thursday meetings to 1700 UTC. Topics to be discussed in this week's call include: - Inventory fabric. Recently we have decided

Re: [openstack-dev] [Neutron] MultiTenant support for VLAN-Aware-VM

On 13 July 2016 at 15:32, Cathy Zhang wrote: > Hi Everyone, > > We have been discussing on multi-tenant VNF for service chain on the OVN > mailing alias. > We are thinking about leveraging the vlan-aware-VM for supporting this. > > AFAIK, with current nova, we cannot

Re: [openstack-dev] [Nova] Regarding fix for 1454165

On 07/13/2016 04:12 PM, Sean Wilcox wrote: With this bug fix the resize_instance definition was effectively changed that is passed into the virt drivers finish_migration() function, IMHO. Agreed. Is it really true that changing memory and/or cpu isn't a resize at all? No, it's definitely a

[openstack-dev] [new][winstackers] os-win 1.1.0 release (newton)

We are pleased to announce the release of: os-win 1.1.0: Windows / Hyper-V library for OpenStack projects. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/os-win With package available at:

Re: [openstack-dev] [daisycloud-core] Core Discussions

Jaivish, I also thought about that . As we have more and more development activities on the go ,we really need to look into this. I will not available at meeting but I would like to elect Wei ( kong.w...@zte.com.cn) to become the core member, because he has good experience on testing, ci and

[openstack-dev] [Neutron] MultiTenant support for VLAN-Aware-VM

Hi Everyone, We have been discussing on multi-tenant VNF for service chain on the OVN mailing alias. We are thinking about leveraging the vlan-aware-VM for supporting this. AFAIK, with current nova, we cannot create a multi-tenant VNF. Currently, nova checks whether the neutron port belongs

[openstack-dev] [Nova] Regarding fix for 1454165

With this bug fix the resize_instance definition was effectively changed that is passed into the virt drivers finish_migration() function, IMHO. Is it really true that changing memory and/or cpu isn't a resize at all? If so it seems the definition of the resize_instance parameter for

Re: [openstack-dev] [Cinder][CI] Rule of recheck keywords has been updated

On 07/13/2016 05:36 PM, Sean McGinnis wrote: > Thanks for sending this out! > > It would be appreciated if all CI maintainers get this updated to follow > the recommendations soon. It would really help us have consistency > across systems. > > Sean Clarifying this is a Cinder decision, so all

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Jul 12, 2016, at 2:43 AM, Cheng, Yingxin wrote: > 4. Capabilities are managed/grouped/abstracted by namespaces, and scheduler > can make decisions based on either cap_names or cap_namespaces > 5. Placement service DON’T have any specific knowledge of a capability, it

Re: [openstack-dev] [Cinder][CI] Rule of recheck keywords has been updated

Thanks for sending this out! It would be appreciated if all CI maintainers get this updated to follow the recommendations soon. It would really help us have consistency across systems. Sean > Hello Cinder Third-Party CI Maintainers, > > The rule of recheck keywords has been discussed in

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On Jul 11, 2016, at 6:08 AM, Alex Xu wrote: > For example, the capabilities can be defined as: > > COMPUTE_HW_CAP_CPU_AVX > COMPUTE_HW_CAP_CPU_SSE > > COMPUTE_HV_CAP_LIVE_MIGRATION > COMPUTE_HV_CAP_LIVE_SNAPSHOT > > > ( The COMPUTE means this

Re: [openstack-dev] [Murano][user-guide][docs] Add section 'Murano applications guide' to the End User Guide

Hi Lana! Thank for your reply! It looks like, the spec is definitely needed in this case. I'll send it on review asap. Regards, Serg On Wed, Jul 13, 2016 at 2:31 AM, Lana Brindley wrote: > Hi Serg! > > I've cc'd Joseph into this mail, to make sure he sees it.

Re: [openstack-dev] [new][oslo] mox3 0.17.0 release (newton)

Excerpts from Jeremy Stanley's message of 2016-07-13 17:22:32 +: > On 2016-07-13 17:10:20 +0200 (+0200), Markus Zoeller wrote: > > Whoever chooses the wording in these announcements, you're a genius! > > You too can be a genius--add some more--there's only ~20 at the > moment so they repeat

[openstack-dev] [nova] Let's kill quota classes (again)

We got a bug that the os-quota-class-sets API isn't documented: https://bugs.launchpad.net/nova/+bug/1602400 That's probably because we hate it and no one understands it. See this previous thread about trying to sort this out from the long long ago:

[openstack-dev] [Cinder][CI] Rule of recheck keywords has been updated

Hello Cinder Third-Party CI Maintainers, The rule of recheck keywords has been discussed in today's IRC meeting [1]. And the wiki [2] of tested-3rdParty-drivers has been updated. # The diff is [3]. Please check the update and update your CI. It would be appreciated if you could also update the

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Hello to All. I have free capacity to work on porting code to Py3. So, if any PTL is running out of team capacity i can help to work on project to enable Py3 support. Kind regards, Denys Makogon 2016-07-06 13:01 GMT+03:00 Flavio Percoco : > On 24/06/16 12:17 -0400, Sean

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

+1, would make a great addition. On Wed, Jul 13, 2016 at 12:47 PM, Carter, Kevin wrote: > +1 from me too. It'll be great to have him on the core team. > > On Tue, Jul 12, 2016 at 1:33 PM, Truman, Travis > wrote: > > Jean-Philippe has been

[openstack-dev] [designate] Designate News Round Up

Hi All, Just a quick update on a few things! Mid Cycle = The Mid Cycle is confirmed for 22-26th of August. It will be in Dublin, in the city center. The address is 64 Mount Street Lower, Dublin 2. D02 TH77 Ireland I will be updating the page on the wiki with local hotels over the

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

+1 from me too. It'll be great to have him on the core team. On Tue, Jul 12, 2016 at 1:33 PM, Truman, Travis wrote: > Jean-Philippe has been providing great code reviews and patches for some > time. His recent commitment to running bug triage every week shows his >

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

On Tue, Jul 12, 2016 at 11:33 AM, Truman, Travis wrote: > In short, just the kind of contribution our community desires from core > reviewers. > I'm happy to add my +1. -- SteveL __ OpenStack

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

From: "Truman, Travis" > Subject: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles Jean-Philippe has been providing great code reviews and patches for

[openstack-dev] [app-catalog] App Catalog IRC meeting Thursday July 14th

Join us Thursday for our weekly meeting, scheduled for July 14th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog Tomorrow we will be

Re: [openstack-dev] [new][oslo] mox3 0.17.0 release (newton)

On 2016-07-13 17:10:20 +0200 (+0200), Markus Zoeller wrote: > Whoever chooses the wording in these announcements, you're a genius! You too can be a genius--add some more--there's only ~20 at the moment so they repeat pretty often:

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

On 2016-07-13 13:25:44 +0200 (+0200), Markus Zoeller wrote: > For some reason the gate docs job didn't find the issue (wrong json > format) which got fixed with change [1]. It doesn't even emit a warning. > Locally, the execution of "tox -e docs" does find the issue. Can we make > the gate docs

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 2016-07-13 13:35:18 +0200 (+0200), Markus Zoeller wrote: [...] > it cannot be used in "gerrty" though, or can it? [...] It's probably one or two more lines of code to also print the Gerrit query such that it could be pasted into Gertty ^O (or make use of `gertty --open` to trigger opening that

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 2016-07-13 09:56:37 +0200 (+0200), Sahid Orentino Ferdjaoui wrote: [...] > Gerrit comments are lost when the patch get merged, we may want to > provide some stats from these tags in future that's why I think commit > message is better. It's not true at all that Gerrit comments are lost when

Re: [openstack-dev] The future of OpenStack documentation

Excerpts from Matt Kassawara's message of 2016-07-13 09:52:45 -0600: > The configuration reference essentially uses a script to parse help strings > from code in project repositories. Occasionally, the documentation team > augments content beyond what the automation provides. However, these >

Re: [openstack-dev] [TripleO] Making TripleO CI easier to consume outside of TripleO CI

I concur, in infra we install roles from git repos. Those are defined in a yaml that are then feeded to ansible-galaxy tool: http://git.openstack.org/cgit/openstack-infra/system-config/tree/roles.yaml Regards 2016-07-13 17:58 GMT+02:00 David Moreau Simard : > On Wed, Jul 13,

Re: [openstack-dev] [TripleO] Making TripleO CI easier to consume outside of TripleO CI

On Wed, Jul 13, 2016 at 9:06 AM, Wesley Hayutin wrote: > We also considered ansible-galaxy and any of the ansible roles found in > github/redhat-openstack/ansible-role could be moved into galaxy. Galaxy did > not end up meeting our requirements for installing the roles and

Re: [openstack-dev] The future of OpenStack documentation

The configuration reference essentially uses a script to parse help strings from code in project repositories. Occasionally, the documentation team augments content beyond what the automation provides. However, these content augmentations, the script, and schedule for running the script belong to

Re: [openstack-dev] [new][oslo] mox3 0.17.0 release (newton)

On 13.07.2016 16:01, no-re...@openstack.org wrote: > We are tickled pink to announce the release of: > Whoever chooses the wording in these announcements, you're a genius! -- Regards, Markus Zoeller (markus_z) > mox3 0.17.0: Mock object framework for Python > > This release is part of the

[openstack-dev] [release][ptl][all] newton-2 milestone deadline 14 July

PTLs and release liaisons, please remember that 14 July is the deadline for proposing your second milestone tags for deliverables using the cycle-with-milestone release model during newton. Milestones are date-based, so if missing the deadline means missing the milestone. Doug

[openstack-dev] [new][oslo] oslotest 2.7.0 release (newton)

We are pleased to announce the release of: oslotest 2.7.0: Oslo test framework This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslotest With package available at: https://pypi.python.org/pypi/oslotest Please report

[openstack-dev] [new][oslo] stevedore 1.16.0 release (newton)

We are overjoyed to announce the release of: stevedore 1.16.0: Manage dynamic plugins for Python applications This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/stevedore With package available at:

[openstack-dev] [new][oslo] oslosphinx 4.6.0 release (newton)

We are jubilant to announce the release of: oslosphinx 4.6.0: OpenStack Sphinx Extensions and Theme This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslosphinx With package available at:

[openstack-dev] [new][oslo] taskflow 2.3.0 release (newton)

We are jazzed to announce the release of: taskflow 2.3.0: Taskflow structured state management library. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/taskflow With package available at:

[openstack-dev] [new][oslo] tooz 1.41.0 release (newton)

We are jazzed to announce the release of: tooz 1.41.0: Coordination library for distributed systems. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/tooz With package available at: https://pypi.python.org/pypi/tooz

[openstack-dev] [new][oslo] oslo.vmware 2.11.0 release (newton)

We are delighted to announce the release of: oslo.vmware 2.11.0: Oslo VMware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware With package available at: https://pypi.python.org/pypi/oslo.vmware

[openstack-dev] [new][oslo] oslo.reports 1.12.0 release (newton)

We are eager to announce the release of: oslo.reports 1.12.0: oslo.reports library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.reports With package available at: https://pypi.python.org/pypi/oslo.reports

[openstack-dev] [new][oslo] oslo.rootwrap 4.4.0 release (newton)

We are gleeful to announce the release of: oslo.rootwrap 4.4.0: Oslo Rootwrap This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.rootwrap With package available at: https://pypi.python.org/pypi/oslo.rootwrap

[openstack-dev] [new][oslo] oslo.service 1.13.0 release (newton)

We are eager to announce the release of: oslo.service 1.13.0: oslo.service library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.service With package available at: https://pypi.python.org/pypi/oslo.service

[openstack-dev] [new][oslo] oslo.policy 1.12.0 release (newton)

We are jazzed to announce the release of: oslo.policy 1.12.0: Oslo Policy library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.policy With package available at: https://pypi.python.org/pypi/oslo.policy

[openstack-dev] [new][oslo] oslo.serialization 2.11.0 release (newton)

We are glad to announce the release of: oslo.serialization 2.11.0: Oslo Serialization library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.serialization With package available at:

[openstack-dev] [new][oslo] oslo.versionedobjects 1.13.0 release (newton)

We are glad to announce the release of: oslo.versionedobjects 1.13.0: Oslo Versioned Objects library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.versionedobjects With package available at:

[openstack-dev] [new][oslo] oslo.privsep 1.10.0 release (newton)

We are content to announce the release of: oslo.privsep 1.10.0: OpenStack library for privilege separation This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.privsep With package available at:

Re: [openstack-dev] The future of OpenStack documentation

On 11.07.2016 00:02, Steve Martinelli wrote: > I personally like this solution, it seems much more scalable. This follows > the same pattern of the API docs (moving the content to project repos), > which puts the onus back on the project team to maintain and create > documentation. I'm also hoping

[openstack-dev] [new][oslo] oslo.db 4.8.0 release (newton)

We are satisfied to announce the release of: oslo.db 4.8.0: Oslo Database library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.db With package available at: https://pypi.python.org/pypi/oslo.db Please

[openstack-dev] [new][oslo] oslo.log 3.12.0 release (newton)

We are thrilled to announce the release of: oslo.log 3.12.0: oslo.log library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.log With package available at: https://pypi.python.org/pypi/oslo.log Please report

[openstack-dev] [new][oslo] oslo.concurrency 3.12.0 release (newton)

We are chuffed to announce the release of: oslo.concurrency 3.12.0: Oslo Concurrency library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.concurrency With package available at:

[openstack-dev] [new][oslo] oslo.i18n 3.8.0 release (newton)

We are overjoyed to announce the release of: oslo.i18n 3.8.0: Oslo i18n library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.i18n With package available at: https://pypi.python.org/pypi/oslo.i18n Please

[openstack-dev] [new][oslo] oslo.middleware 3.15.0 release (newton)

We are thrilled to announce the release of: oslo.middleware 3.15.0: Oslo Middleware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.middleware With package available at:

[openstack-dev] [new][oslo] oslo.context 2.6.0 release (newton)

We are chuffed to announce the release of: oslo.context 2.6.0: Oslo Context library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.context With package available at: https://pypi.python.org/pypi/oslo.context

[openstack-dev] [new][oslo] oslo.config 3.13.0 release (newton)

We are thrilled to announce the release of: oslo.config 3.13.0: Oslo Configuration API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.config With package available at: https://pypi.python.org/pypi/oslo.config

[openstack-dev] [new][oslo] oslo.cache 1.11.0 release (newton)

We are psyched to announce the release of: oslo.cache 1.11.0: Cache storage for Openstack projects. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.cache With package available at:

[openstack-dev] [new][oslo] automaton 1.3.0 release (newton)

We are satisfied to announce the release of: automaton 1.3.0: Friendly state machines for python. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/automaton With package available at:

[openstack-dev] [new][oslo] futurist 0.15.0 release (newton)

We are eager to announce the release of: futurist 0.15.0: Useful additions to futures, from the future. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/futurist With package available at:

[openstack-dev] [new][oslo] mox3 0.17.0 release (newton)

We are tickled pink to announce the release of: mox3 0.17.0: Mock object framework for Python This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/mox3 With package available at: https://pypi.python.org/pypi/mox3 Please

[openstack-dev] [new][oslo] debtcollector 1.6.0 release (newton)

We are pumped to announce the release of: debtcollector 1.6.0: A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non- destructive manner. This release is part of the newton release series. With source available at:

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

Thanks for the update, Matt. I will join our meeting next week. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 12, 2016 at 4:25 PM, Matt Riedemann wrote: > On 7/12/2016 6:29 AM, Ivan Kolodyazhny wrote: > >> Hi team, >> >> Do we have any decision on

[openstack-dev] [storlets] IRC meeting times

Hi, I would like to change the IRC meeting times to Tuesdays at 07:00AM UTC That's: 16:00 JST 10:00 IST Any objections? Thanks! Eran __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Neutron][DVR] - No IRC Meeting today

Hi Folks, Sorry for the late notice, but we will not have a DVR sub-team meeting today since neither Swami nor myself will be there to chair it. We will resume our meetings next week on July 20th. If you have any questions please ping us on IRC or send an email to the list.

Re: [openstack-dev] [TripleO] Making TripleO CI easier to consume outside of TripleO CI

On Wed, Jul 13, 2016 at 8:54 AM, Michal Pryc wrote: > John, > > On Tue, Jul 12, 2016 at 9:39 PM, John Trowbridge wrote: > >> Howdy folks, >> >> In the TripleO meeting two weeks ago, it came up that tripleo-quickstart >> is being used as a CI tool in RDO. This

Re: [openstack-dev] [kolla] New specs process - a dicussion

Josh, We did have the discussion at summit. We aren't even going to have a "big spec". We are going to run as bare minimal of a spec as possible. The reason I brought up spec additions is because Kolla has become so large, managing the project using current techniques is not optimal. I don't

Re: [openstack-dev] [TripleO] Making TripleO CI easier to consume outside of TripleO CI

John, On Tue, Jul 12, 2016 at 9:39 PM, John Trowbridge wrote: > Howdy folks, > > In the TripleO meeting two weeks ago, it came up that tripleo-quickstart > is being used as a CI tool in RDO. This came about organically, because > we needed to use RDO CI to self-gate quickstart

Re: [openstack-dev] [mistral] [murano] [yaql] yaqluator bug

Thank You Renat, Moshe, Stan and all! ср, 6 июл. 2016 г. в 7:01, Renat Akhmerov : > Great! Alex, enjoy using yaqluator :) > > Renat Akhmerov > @Nokia > > On 05 Jul 2016, at 23:16, Elisha, Moshe (Nokia - IL) < > moshe.eli...@nokia.com> wrote: > > Thank you all for

Re: [openstack-dev] [TripleO] Making TripleO CI easier to consume outside of TripleO CI

On Tue, Jul 12, 2016 at 3:39 PM, John Trowbridge wrote: > Howdy folks, > > In the TripleO meeting two weeks ago, it came up that tripleo-quickstart > is being used as a CI tool in RDO. This came about organically, because > we needed to use RDO CI to self-gate quickstart (it

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 13.07.2016 09:56, Sahid Orentino Ferdjaoui wrote: > On Tue, Jul 12, 2016 at 06:45:03PM +0200, Markus Zoeller wrote: >> On 12.07.2016 17:39, Sahid Orentino Ferdjaoui wrote: >>> On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote: After closing the old (>18months) bug reports

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 2016-07-13 13:35, Markus Zoeller wrote: > On 12.07.2016 20:31, Jeremy Stanley wrote: >> On 2016-07-12 10:46:54 -0700 (-0700), Augustina Ragwitz wrote: >> [...] >>> I like #3 but I worry about the comments getting spammy if things are >>> dropped from and added to the list repeatedly. Would

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

+1 JP :) On Tue, 12 Jul 2016 at 19:34 Truman, Travis wrote: > Jean-Philippe has been providing great code reviews and patches for some > time. His recent commitment to running bug triage every week shows his > willingness to step up and take responsibilities within

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 12.07.2016 20:31, Jeremy Stanley wrote: > On 2016-07-12 10:46:54 -0700 (-0700), Augustina Ragwitz wrote: > [...] >> I like #3 but I worry about the comments getting spammy if things are >> dropped from and added to the list repeatedly. Would tagging the bugs in >> Launchpad work? We can easily

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

On 2016-07-13 13:25, Markus Zoeller wrote: > For some reason the gate docs job didn't find the issue (wrong json > format) which got fixed with change [1]. It doesn't even emit a warning. > Locally, the execution of "tox -e docs" does find the issue. Can we make > the gate docs job aware of such

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 13.07.2016 10:09, Andreas Jaeger wrote: > On 2016-07-12 09:59, Markus Zoeller wrote: >> After closing the old (>18months) bug reports nobody is working on a few >> days ago [1], it became clear that the "in progress" reports are the >> majority [2]. After asking Gerrit how long it usually takes

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

On 23.06.2016 12:21, Andreas Jaeger wrote: > On 06/23/2016 10:43 AM, Markus Zoeller wrote: >> On 21.06.2016 15:01, Doug Hellmann wrote: >>> A while back pbr had a feature that let projects pass "warnerror" >>> through to Sphinx during documentation builds, causing any warnings in >>> that build to

Re: [openstack-dev] [Fuel] Mitaka stable branch

Bogdan, Vladimir *Regarding upgrades of Fuel Master Node and environments. * First, regarding Fuel Master Node upgrades and enablement of usage of 9.0 LCM features with older clusters. It is assumed that we test usability of Fuel Mitaka code with already deployed clusters, e.g. 8.0, 7.0 and so

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 12-07-16 09:59:12, Markus Zoeller wrote: > After closing the old (>18months) bug reports nobody is working on a few > days ago [1], it became clear that the "in progress" reports are the > majority [2]. After asking Gerrit how long it usually takes to get a fix > merged [3], this is the result:

Re: [openstack-dev] [nova] Can not rebuild boot-from-volume instance

On 12-07-16 15:12:24, zehua wrote: > Hi, all > I booted a new instance from a volume and then attached an other volume to it, > and created image for the instance whos block_device_mapping like this: > > > | block_device_mapping | [{"guest_format": null, "boot_index": 0, >

[openstack-dev] [Freezer] Freezer Mascot

Hi, We should select a Mascot for Freezer project. Please add your suggestions in the etherpad below: https://etherpad.openstack.org/p/freezer_mascot We need to select 3-5 leading suggestions, send them to OpenStack representative for evaluation. We will then conduct the final vote. Please go

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

> 1. we agreed on whether the 'network_interface' was, or was not, an interface that was similar to the existing power, deploy, ... interfaces so that it fit into the driver composition work with the network interface being environment- (binding a node to a particular Switch type) rather than

Re: [openstack-dev] [Fuel] New version of fuel-devops (2.9.21)

Hi Bogdan, thanks for the question! On 07/12/2016 10:26 AM, Bogdan Dobrelya wrote: > On 07/12/2016 09:24 AM, Bogdan Dobrelya wrote: >> Thank you for a hard work, that's a really great tool. >> >> Anyone who is interested, please note that fuel-devops, despite of the >> name, may be used outside

[openstack-dev] [Fuel][QA] Changes in requirements.txt in the fuel-qa repository

Hi all, Recently there was a change in the fuel-qa requirements [1], that can be found in patches for 6.1, 7.0, 8.0, mitaka and master [2] [3] [4] [5] [6]. The goal is to split the requirements for system tests from requirements for fuel-devops, which is mostly the part of the system

Re: [openstack-dev] [Fuel] Mitaka stable branch

On 07/13/2016 11:08 AM, Vladimir Kozhukalov wrote: > > > Few Q: > - Is the stable/mitaka the only stable branch in the scope of the > changes? > > ​Yes, this announce is only about Mitaka branch. All other stable > branches are to be treated as usual, i.e. no feature backports, bug

Re: [openstack-dev] [Fuel] Mitaka stable branch

> > Few Q: > - Is the stable/mitaka the only stable branch in the scope of the changes? > ​Yes, this announce is only about Mitaka branch. All other stable branches are to be treated as usual, i.e. no feature backports, bug fixes only following "master first" policy, etc. > > - As the master and

[openstack-dev] [vitrage] Vitrage Mascot Selection

Hi, As we discussed in the IRC meeting today, we should select a Mascot for Vitrage project. Please add your suggestions in the etherpad below: https://etherpad.openstack.org/p/vitrage-mascot We need to select 3-5 leading suggestions, send them to OpenStack representative for evaluation, and

Re: [openstack-dev] [Fuel] Mitaka stable branch

On 07/13/2016 10:17 AM, Vladimir Kozhukalov wrote: > Dear colleagues, > > I'd like to announce some of our plans on how we are going to > support/develop Fuel Mitaka stable branch. The plan is as follows: > > 0) We have been working hard and have fixed a lot of bugs in Mitaka > branch as for

[openstack-dev] [Neutron][networking-ovn][networking-odl] Syncing neutron DB and OVN DB

Adding the proper tags in subject On Wed, Jul 13, 2016 at 1:22 PM, Numan Siddique wrote: > Hi Neutrinos, > > Presently, In the OVN ML2 driver we have 2 ways to sync neutron DB and OVN > DB > - At neutron-server startup, OVN ML2 driver syncs the neutron DB and OVN > DB if

[openstack-dev] [Fuel] Mitaka stable branch

Dear colleagues, I'd like to announce some of our plans on how we are going to support/develop Fuel Mitaka stable branch. The plan is as follows: 0) We have been working hard and have fixed a lot of bugs in Mitaka branch as for late. This week we are going to announce 9.0.1 release which is

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On 2016-07-12 09:59, Markus Zoeller wrote: > After closing the old (>18months) bug reports nobody is working on a few > days ago [1], it became clear that the "in progress" reports are the > majority [2]. After asking Gerrit how long it usually takes to get a fix > merged [3], this is the result:

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On Tue, Jul 12, 2016 at 06:45:03PM +0200, Markus Zoeller wrote: > On 12.07.2016 17:39, Sahid Orentino Ferdjaoui wrote: > > On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote: > >> After closing the old (>18months) bug reports nobody is working on a few > >> days ago [1], it became

  1   2   >