Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

On 2 February 2017 at 16:09, Armando M. wrote: > Hi neutrinos, > > I have put a number of patches in the merge queue for a few sub-projects. > We currently have a number of these that are on an independent release > schedule. In particular: > >- networking-bagpipe >-

Re: [openstack-dev] [requirements] [Horizon][Karbor][Magnum] Requesting FFE for xstatic packages

We are actively working to verify that magnum-ui works with the adjusted requirements.txt, and as soon as we have confirmed this change is non-disruptive, I will be ready to approve the FFE. Adrian > On Feb 7, 2017, at 4:54 PM, Richard Jones wrote: > > It looks like

Re: [openstack-dev] [oslo] pbr and warnerrors status

> On Feb 8, 2017, at 8:15 AM, Ben Nemec wrote: > > > > On 02/08/2017 09:41 AM, Doug Hellmann wrote: >> Excerpts from Ben Nemec's message of 2017-02-08 09:20:31 -0600: >>> >>> On 02/08/2017 01:53 AM, Andreas Jaeger wrote: On 2017-02-08 00:56, Ian Cordasco wrote:

Re: [openstack-dev] [requirements] [Horizon][Karbor][Magnum] Requesting FFE for xstatic packages

I voted to merge [1] and [2]: [1] https://review.openstack.org/#/c/429753/ [2] https://review.openstack.org/#/c/430941/ FFE approved for Magnum, provided this does not cause problems for other projects. Adrian On Feb 8, 2017, at 7:25 AM, Adrian Otto

Re: [openstack-dev] [oslo] pbr and warnerrors status

On 02/08/2017 09:41 AM, Doug Hellmann wrote: Excerpts from Ben Nemec's message of 2017-02-08 09:20:31 -0600: On 02/08/2017 01:53 AM, Andreas Jaeger wrote: On 2017-02-08 00:56, Ian Cordasco wrote: On Feb 7, 2017 5:47 PM, "Joshua Harlow"

Re: [openstack-dev] [fuel][release] Opting out of Ocata?

Dims Thank you for keeping the hand on the pulse. I am going to take over the PTL duties and we are going to produce releases according to the wiki . We are going to have RC1 next week (around Feb 15). After that we are going to proceed as

Re: [openstack-dev] [oslo] pbr and warnerrors status

Excerpts from Ben Nemec's message of 2017-02-08 09:20:31 -0600: > > On 02/08/2017 01:53 AM, Andreas Jaeger wrote: > > On 2017-02-08 00:56, Ian Cordasco wrote: > >> > >> > >> On Feb 7, 2017 5:47 PM, "Joshua Harlow" >> > wrote: > >> > >>

Re: [openstack-dev] [all][tc][swift][designate] New language addition process has been approved

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: 08 February 2017 13:49 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all][tc][swift][designate] New language addition > process has been approved > > On 19/01/17 11:59 +0100, Flavio

Re: [openstack-dev] [oslo] pbr and warnerrors status

On 02/08/2017 01:53 AM, Andreas Jaeger wrote: On 2017-02-08 00:56, Ian Cordasco wrote: On Feb 7, 2017 5:47 PM, "Joshua Harlow" > wrote: Likely just never pulled the trigger. Seems like we should pull it though. Will have to

Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

Has the liberty-eol cleanup happened? Because I still see stable/liberty branch in openstack/neutron repo, which gets in the way of some logic around proactive backports: https://review.openstack.org/#/c/427936/4/bugs-fixed-since.py@75, and I see backports proposed for the branch that is no longer

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

Doug Hellmann wrote: Excerpts from ChangBo Guo's message of 2017-02-08 10:41:04 +0800: Thanks Doug and amoralej, we should avoid this :(． One more thought about mox3: Is it used outside of OpenStack? If yes, Maybe we can retire mox3 if all projects move mox to mock. I thought our policy was

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

On 8 February 2017 at 09:13, Thomas Morin wrote: > Hi Armando, > > As far as networking-bgpvpn and networking-bagpipe are concerned, the plan > is to do like we've been doing for the past 2 releases, which is to cut a > branch and make a release not too far after

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

Hi Armando, As far as networking-bgpvpn and networking-bagpipe are concerned, the plan is to do like we've been doing for the past 2 releases, which is to cut a branch and make a release not too far after Openstack. The date of March 10th looks reasonable as a target, and we'll stick to that.

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

Armando, networking-sfc will cut a stable/ocata branch by March 10. -Louis From: Armando M. [mailto:arma...@gmail.com] Sent: Wednesday, February 08, 2017 8:16 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [stadium]

Re: [openstack-dev] [tripleo] Moving mirror server images to tarballs.o.o (Was: [rdo-list] RDO-CI Scrum Weekly Scrum Recap)

On Wed, Feb 08, 2017 at 08:50:10AM -0500, John Trowbridge wrote: > Moving this thread from rdo-list, but leaving in copy as it is relevant > there too. However it is more of a TripleO topic. > > On 02/07/2017 03:56 PM, Paul Belanger wrote: > > On Tue, Feb 07, 2017 at 03:34:09PM -0500, Ronelle

Re: [openstack-dev] [neutron][networking-l2gw] ocata release?

Gary, Thank you - you da man... -Sukhdev On Sun, Feb 5, 2017 at 11:27 PM, Gary Kotton wrote: > Done - https://review.openstack.org/gitweb?p=openstack/networking- > l2gw.git;a=shortlog;h=refs/heads/stable/ocata > A luta continua > > On 2/6/17, 8:51 AM, "Gary Kotton"

[openstack-dev] [nova] Cells meeting canceled

Hi all, Today's cells meeting is canceled. We're still working on getting ocata out the door, a bunch of normal participants are out today, and not much has transpired for pike just yet. --Dan __ OpenStack Development

[openstack-dev] [All] IRC Mishaps

Hello All! So I am sure we've all seen it: people writing terminal commands into our project channels, misusing '/' commands, etc. But have any of you actually done it? If any of you cores, ptls or other upstanding members of our wonderful community have had one of these embarrassing experiences

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

Regarding to networking-odl, we're going to cut stable/ocata branch around Feb 11. After a while testing, the release will be done to avoid much delay the official schedule. The plan for Pike is to graduate from independent model. thanks, On Wed, Feb 08, 2017 at 08:16:13AM -0800, "Armando M."

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

Regarding vmware-nsx we are planning to cut a version in the coming days. Thanks Gary On 2/8/17, 8:51 PM, "Isaku Yamahata" wrote: Regarding to networking-odl, we're going to cut stable/ocata branch around Feb 11. After a while testing, the release will be

Re: [openstack-dev] [tripleo] Moving mirror server images to tarballs.o.o (Was: [rdo-list] RDO-CI Scrum Weekly Scrum Recap)

On 2017-02-08 14:10:16 -0500 (-0500), Paul Belanger wrote: [...] > We basically create a publisher in JJB to handle this, which looks in the > $WORKSPACE/images folder for things to scp to tarballs.o.o. Take a look at > the > kolla job for example. > > What we can do, is create an experimental

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

Excerpts from Joshua Harlow's message of 2017-02-08 10:01:27 -0800: > Doug Hellmann wrote: > > Excerpts from ChangBo Guo's message of 2017-02-08 10:41:04 +0800: > >> Thanks Doug and amoralej, we should avoid this :(． > >> > >> One more thought about mox3: Is it used outside of OpenStack? If yes,

[openstack-dev] [keystone] ocata backport potential tag

Hi all, Now that Pike is open for development, I've create an official ocata-backport-potential bug tag. In the event you see a bug that affects Ocata, feel free to use the tag. Thanks! __ OpenStack Development Mailing List

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

i plan to cut a release for networking-midonet once relevant projects get ready. ie. neutron-vpnaas, tap-as-a-service On Thu, Feb 9, 2017 at 1:16 AM, Armando M. wrote: > > > On 2 February 2017 at 16:09, Armando M. wrote: >> >> Hi neutrinos, >> >> I have put

Re: [openstack-dev] [requirements] [Horizon][Karbor][Magnum] Requesting FFE for xstatic packages

On Wed, Feb 08, 2017 at 03:42:06PM +, Adrian Otto wrote: > I voted to merge [1] and [2]: > > [1] https://review.openstack.org/#/c/429753/ > [2] https://review.openstack.org/#/c/430941/ > > FFE approved for Magnum, provided this does not cause problems for other > projects. Thanks everyone

Re: [openstack-dev] [All] IRC Mishaps

On 02/08/2017 03:36 PM, Kendall Nelson wrote: Hello All! So I am sure we've all seen it: people writing terminal commands into our project channels, misusing '/' commands, etc. But have any of you actually done it? If any of you cores, ptls or other upstanding members of our wonderful

Re: [openstack-dev] [All] IRC Mishaps

At a previous employer we had a policy that all passwords started with "/" because of the sheer number of times someone typed the root password into a public IRC channel. Michael On Thu, Feb 9, 2017 at 10:04 AM, Jay Pipes wrote: > On 02/08/2017 03:36 PM, Kendall Nelson

Re: [openstack-dev] [openstack-ansible] Propose Marc Gariepy as core reviewer

+1 On Mon, Feb 6, 2017 at 12:17 PM, Hugh Saunders wrote: > +1 > > On Fri, 3 Feb 2017 at 19:50 Steve Lewis wrote: > >> On Fri, Feb 3, 2017 at 5:33 AM, Jesse Pretorius < >> jesse.pretor...@rackspace.co.uk> wrote: >> >> I’d like to propose Marc Gariepy [1]

Re: [openstack-dev] [All] IRC Mishaps

How about the crowd favorite of accidentally submitting your password in chat instead of where you were trying to? At least people can help you evaluate your password strength :) On Wed, Feb 8, 2017, 12:38 PM Kendall Nelson wrote: > Hello All! > > So I am sure we've all

Re: [openstack-dev] [release][all] started branching tools and requirements

Excerpts from Doug Hellmann's message of 2017-02-08 08:29:45 -0500: > We have started the process of branching devstack, grenade, and the > requirements repo. This may introduce some instability into the gate > until we are finished. Please join #openstack-release if you would like > to follow

Re: [openstack-dev] [All] IRC Mishaps

Thanks Jay :) Pretty sure we've all been there! On Wed, Feb 8, 2017, 3:08 PM Jay Pipes wrote: > On 02/08/2017 03:36 PM, Kendall Nelson wrote: > > Hello All! > > > > So I am sure we've all seen it: people writing terminal commands into > > our project channels, misusing '/'

Re: [openstack-dev] [All] IRC Mishaps

I've definitely done this before :) Thanks for sharing! On Wed, Feb 8, 2017, 3:13 PM Travis McPeak wrote: > How about the crowd favorite of accidentally submitting your password in > chat instead of where you were trying to? > > At least people can help you evaluate

Re: [openstack-dev] Refstack - final mascot

+1 From: Rochelle Grober [mailto:rochelle.gro...@huawei.com] Sent: Tuesday, February 07, 2017 8:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Refstack - final mascot Looks great to me. --Rocky From:

Re: [openstack-dev] [All] IRC Mishaps

On 09/02/17 06:36, Kendall Nelson wrote: > Hello All! > > So I am sure we've all seen it: people writing terminal commands into our > project channels, misusing '/' commands, etc. But have any of you actually > done it? > > If any of you cores, ptls or other upstanding members of our wonderful

Re: [openstack-dev] [Blazar] bug list before next release

Hi Hiroaki, > I have a question about namespace migration. > Do we completely remove climate namespace from blazar repo? IMO, we should remain climate namespace at least one release cycle. Someone could have their own plugin for blazar with climate namespace. If it remains in next one cycle,

[openstack-dev] [tricircle]schedule for Ocata release and Pike meetup/PTG

Hello,team, Thanks for your great contribution, the Ocata cycle is almost done. As what we discussed in weekly meeting, the schedule for Ocata release and Pike meetup/PTG as follows: 1.Ocata branch this Friday or early 2. Regression test until Feb.15 3. Ocata release Feb.16 4. Pike meetup

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

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, Jan 9th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

[openstack-dev] [release][all] HELP NEEDED: test failures blocking requirements ocata branch and opening of pike

The patch to update the XStatic package versions [1] is blocked by a patch to remove nova-docker from the requirements project sync list [2], which is in turn running into issues in the gate-grenade-dsvm-neutron-multinode-ubuntu-xenial job [3]. We need some folks who understand these tests and

Re: [openstack-dev] [Blazar] bug list before next release

Hi Masahito Thank you for listing tasks for Blazar 0.2.0 release. I have a question about namespace migration. Do we completely remove climate namespace from blazar repo? If so, I want to add one more task "Remove climate namespace from blazar-nova repo" because namespace has been already

Re: [openstack-dev] [nova] Next notification meeting on 02.14.

On Tue, Feb 7, 2017 at 3:56 PM, Matt Riedemann wrote: On 2/7/2017 7:40 AM, Balazs Gibizer wrote: Hi, As we agreed last week's meeting there won't be meeting this week. The next notification subteam meeting will be held on 2017.02.14 17:00 UTC [1] on

[openstack-dev] [tripleo] Populating Hiera data before NetworkDeployment

Hello, We are facing an issue in enabling DPDK in openvswitch. Currently, DPDK is enabled by configuring DPDK_OPTIONS at Step4 using puppet-vswitch (vswitch::dpdk) module. This flow has limitations: * if DPDK is used for Tenant Network, Ping Test (AllNodesValidation) will fail * for DPDK bond,

[openstack-dev] [Nova] How boot with bdm_v2={source_type=image, destination_type=local} should been used?

Hi All, As I was working on "Check destination_type when booting with bdm provided": https://review.openstack.org/#/c/402372/ and addressing reviewers comments, I find out that the current source_type=image, destination_type=local seems unusable. According to docs:

Re: [openstack-dev] [Nova] How boot with bdm_v2={source_type=image, destination_type=local} should been used?

HI Zhenyu You're referring to API doc, but you're checking it with nova cli, which does not do exactly that what you want. In the case when you specify image and block-device parameters, nova cli sends image_ref and two (!) bdms. Both these bdms have the same boot_index and conflict with each

[openstack-dev] [karbor][stackalytics] Karbor Missing Commits in Stackalytics

Hey all, By looking at http://stackalytics.com/?metric=commits=all_type=all=karbor I noticed that Karbor has only 195 commits in Stackalytics, while in fact, it has 721 commits (438 of them are not Jenkin's merges). It seems like this happens because of the past Smaug -> Karbor rename. The

Re: [openstack-dev] [Nova] How boot with bdm_v2={source_type=image, destination_type=local} should been used?

Zhenyu, btw iianm if you specify image only (w/o bdm) in the command line, nova cli sends exactly that combination which you're interesting for: image_ref and bdmv2. From: Feodor Tersin Sent: Wednesday, February 8, 2017 2:11:05 PM To:

Re: [openstack-dev] [karbor] Karbor Mascot draft

Hey, Please send your vote for Karbor's mascot in mailing list or in Karbor's IRC channel (just type 'mascot option 1' or 'mascot option 2') until Thursday February 9th 08:00 UTC ( https://time.is/compare/0800_9_Feb_2017_in_UTC ). --Yuval From: Yuval Brik

[openstack-dev] [openstack-docs] Bug smash

Hey everyone, We have 2 weeks until the Ocata release. Hooray! We have fixed 251 so far! But, we have some more work to do… I know everyone is busy with their respective guides and testing, but we have 24 bugs (half are wishlist!) that were assigned for Newton and Ocata that we have not

Re: [openstack-dev] [OpenStack-docs] [openstack-docs] Bug smash

Correction! 251 bugs* - good to see I can type an email without errors. On 2/8/17, 11:25 AM, "Alexandra Settle" wrote: Hey everyone, We have 2 weeks until the Ocata release. Hooray! We have fixed 251 so far! But, we have some more work to do… I

[openstack-dev] [tripleo] Moving mirror server images to tarballs.o.o (Was: [rdo-list] RDO-CI Scrum Weekly Scrum Recap)

Moving this thread from rdo-list, but leaving in copy as it is relevant there too. However it is more of a TripleO topic. On 02/07/2017 03:56 PM, Paul Belanger wrote: > On Tue, Feb 07, 2017 at 03:34:09PM -0500, Ronelle Landy wrote: >> Greetings All, >> >> Links to the RDO-CI team scrum[1] and

Re: [openstack-dev] [all][tc][swift][designate] New language addition process has been approved

On 19/01/17 11:59 +0100, Flavio Percoco wrote: Greetings, The Technical Committe recently approved a new reference document which describes how new programming languages can be proposed for inclusion as supported languages by OpenStack. The new reference document can be found here[0]. I'd like

Re: [openstack-dev] [all][tc][swift][designate] New language addition process has been approved

On 08/02/2017 14:56, Flavio Percoco wrote: > On 19/01/17 11:59 +0100, Flavio Percoco wrote: >> Greetings, >> >> The Technical Committe recently approved a new reference document which >> describes how new programming languages can be proposed for inclusion as >> supported languages by OpenStack.

[openstack-dev] [release][all] started branching tools and requirements

We have started the process of branching devstack, grenade, and the requirements repo. This may introduce some instability into the gate until we are finished. Please join #openstack-release if you would like to follow along. Doug

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

Excerpts from ChangBo Guo's message of 2017-02-08 10:41:04 +0800: > Thanks Doug and amoralej, we should avoid this :(． > > One more thought about mox3: Is it used outside of OpenStack? If yes, > Maybe we can retire mox3 if all projects move mox to mock. I thought our policy was that mox3 was

[openstack-dev] [dib] diskimage-builder v2 RC1 release; request for test

Hi diskimage-builder has been working on a feature/v2 branch incorporating some largely internal changes to the way it finds and calls elements, enhancements to partitioning and removal of some long-deprecated elements. We have just tagged 2.0.0rc1 and are requesting testing by interested

[openstack-dev] [monasca] Monasca Ocata midcycle

Hi Everyone, We will be holding a Monasca Midcycle on Wednesday February 22nd, and Thursday February 23rd, 2017, via Lync/Skype video conferencing. The etherpad for the midcycle is located at, https://etherpad.openstack.org/p/monasca_ocata_midcycle. The etherpad has the Lync/Skype connection

Re: [openstack-dev] [kuryr] Resource management videoconf meeting

On Tue, Feb 7, 2017 at 5:30 PM, Antoni Segura Puimedon wrote: > Hi all, > > In the last weekly IRC meeting it was agreed to hold a videoconf meeting > about resource management. For those unaware, the topic revolves around the > reutilization of Neutron resources like ports

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

I just added it in https://etherpad.openstack.org/p/community-goals yesterday. submit a community goal for this ? 2017-02-09 3:20 GMT+08:00 Doug Hellmann : > Excerpts from Joshua Harlow's message of 2017-02-08 10:01:27 -0800: > > Doug Hellmann wrote: > > > Excerpts from