Re: [openstack-dev] [requirements] adding uwsgi to global-requirements

> Original Message > Subject: Re: [openstack-dev] [requirements] adding uwsgi to > global-requirements > Local Time: December 19, 2017 9:57 PM > UTC Time: December 20, 2017 2:57 AM > From: mtrein...@kortar.org > To: Sam Yaple , OpenStack Development Mailing List (not for > usage

Re: [openstack-dev] [requirements] adding uwsgi to global-requirements

On 17-12-19 19:50:59, Sam Yaple wrote: > > Original Message > > Subject: Re: [openstack-dev] [requirements] adding uwsgi to > > global-requirements > > Local Time: December 19, 2017 6:34 PM > > UTC Time: December 19, 2017 11:34 PM > > From: mtrein...@kortar.org > > To: Sam Yaple

[openstack-dev] [Neutron][dhcp] why dhcp agent doesn't report exception to neutron server?

Hello folks, Here is the problem I encountered, I created a network with 172.16.111.0/30 subnet that disabled DHCP, there are two IP addresses which are available in the pool, 172.16.111.1 is reserved for the gateway, 172.16.111.2 was allocated to VM. there is no error happened when I update

Re: [openstack-dev] [all] Switching to longer development cycles

On 20/12/17 09:29, Joshua Harlow wrote: > Zane Bitter wrote: >> Getting off-topic, but since you walked in to this one ;) >> >> On 14/12/17 21:43, Matt Riedemann wrote: >>> What are the real problems that the Nova team is not working on and >>> apparently is a priority to everyone else in the Ope

Re: [openstack-dev] [all] Switching to longer development cycles

On 20/12/17 07:07, Zane Bitter wrote: > On 13/12/17 11:17, Thierry Carrez wrote: >> So... What do you think ? > > Some points against that I haven't seen mentioned much yet: > > * Following our standard deprecation policy, it would take up to 3 > years to remove anything. For perspective, 3 years

Re: [openstack-dev] [all] Switching to longer development cycles

On 20/12/17 08:20, Zane Bitter wrote: > Getting off-topic, but since you walked in to this one ;) > > On 14/12/17 21:43, Matt Riedemann wrote: >> What are the real problems that the Nova team is not working on and >> apparently is a priority to everyone else in the OpenStack ecosystem >> but we a

Re: [openstack-dev] [requirements] adding uwsgi to global-requirements

On Tue, Dec 19, 2017 at 07:50:59PM -0500, Sam Yaple wrote: > > Original Message > > Subject: Re: [openstack-dev] [requirements] adding uwsgi to > > global-requirements > > Local Time: December 19, 2017 6:34 PM > > UTC Time: December 19, 2017 11:34 PM > > From: mtrein...@kortar.or

Re: [openstack-dev] [nova][stable] What nova needs to get to newton end of life

On 12/15/2017 4:50 AM, Lee Yarwood wrote: On 14-12-17 09:15:18, Matt Riedemann wrote: I'm not sure how many other projects still have an active stable/newton branch, but I know nova is one of them. At this point, these are I think the things that need to get done to end of life the newton branc

Re: [openstack-dev] [nova]Notification update week 51

On 12/18/2017 4:10 AM, Balazs Gibizer wrote: Hi, Here is the last status update / focus settings mail for 2017 Bugs [High] https://bugs.launchpad.net/nova/+bug/1737201 TypeError when sending notification during attach_interface Fix proposed and needs a second core to look at: https://revi

Re: [openstack-dev] [requirements] adding uwsgi to global-requirements

> Original Message > Subject: Re: [openstack-dev] [requirements] adding uwsgi to > global-requirements > Local Time: December 19, 2017 6:34 PM > UTC Time: December 19, 2017 11:34 PM > From: mtrein...@kortar.org > To: Sam Yaple , OpenStack Development Mailing List (not for > usag

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On Tue, Dec 19, 2017 at 5:45 PM, Derek Higgins wrote: > > > On 19 December 2017 at 22:23, Brian Haley wrote: >> >> On 12/19/2017 04:00 PM, Ben Nemec wrote: >>> >>> >>> >>> On 12/19/2017 02:43 PM, Brian Haley wrote: On 12/19/2017 11:53 AM, Ben Nemec wrote: > > The reboot is done

Re: [openstack-dev] [requirements] adding uwsgi to global-requirements

On Tue, Dec 19, 2017 at 05:46:34PM -0500, Sam Yaple wrote: > Hello, > > I wanted to bring up the idea of getting uwsgi into the requirements repo. I > seem to recall this being discussed a couple of years back, but for the life > of me I cannot find the thread, so forgive me if I am digging up a

[openstack-dev] [requirements] adding uwsgi to global-requirements

Hello, I wanted to bring up the idea of getting uwsgi into the requirements repo. I seem to recall this being discussed a couple of years back, but for the life of me I cannot find the thread, so forgive me if I am digging up ancient history. I would like to see uwsgi in global-requirements.txt

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 19 December 2017 at 22:23, Brian Haley wrote: > On 12/19/2017 04:00 PM, Ben Nemec wrote: > >> >> >> On 12/19/2017 02:43 PM, Brian Haley wrote: >> >>> On 12/19/2017 11:53 AM, Ben Nemec wrote: >>> The reboot is done (mostly...see below). On 12/18/2017 05:11 PM, Joe Talerico wrote:

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 12/19/2017 04:00 PM, Ben Nemec wrote: On 12/19/2017 02:43 PM, Brian Haley wrote: On 12/19/2017 11:53 AM, Ben Nemec wrote: The reboot is done (mostly...see below). On 12/18/2017 05:11 PM, Joe Talerico wrote: Ben - Can you provide some links to the ovs port exhaustion issue for some backgr

Re: [openstack-dev] [pbr] Git submodules support

Hi, > > * But once in the docker build, PBR complains about not getting access to* > > > * upstream GIT. And it is true: the git tree (with dependencies) has been* > > > * checkedout by gitlab and the docker build (running in a gitlab runner) > does*>* not give access to the repository, because it

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 12/19/2017 02:43 PM, Brian Haley wrote: On 12/19/2017 11:53 AM, Ben Nemec wrote: The reboot is done (mostly...see below). On 12/18/2017 05:11 PM, Joe Talerico wrote: Ben - Can you provide some links to the ovs port exhaustion issue for some background? I don't know if we ever had a bug

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On 12/19/2017 11:53 AM, Ben Nemec wrote: The reboot is done (mostly...see below). On 12/18/2017 05:11 PM, Joe Talerico wrote: Ben - Can you provide some links to the ovs port exhaustion issue for some background? I don't know if we ever had a bug opened, but there's some discussion of it in

Re: [openstack-dev] [all] Switching to longer development cycles

Zane Bitter wrote: Getting off-topic, but since you walked in to this one ;) On 14/12/17 21:43, Matt Riedemann wrote: What are the real problems that the Nova team is not working on and apparently is a priority to everyone else in the OpenStack ecosystem but we are somehow oblivious? * Provid

[openstack-dev] [keystone] federated performance feedback

Hey all, We've had a topic come up a few times about making it so IDs can be specified in the API request when creating a project [0]. This has come up over several releases, including the Queens release and in today's keystone meeting [1]. The proposal is meant to solve spanning keystone in large

Re: [openstack-dev] [all] Switching to longer development cycles

Getting off-topic, but since you walked in to this one ;) On 14/12/17 21:43, Matt Riedemann wrote: What are the real problems that the Nova team is not working on and apparently is a priority to everyone else in the OpenStack ecosystem but we are somehow oblivious? * Providing a secure channe

Re: [openstack-dev] [pbr] Git submodules support

On Tue, Dec 19, 2017, at 10:18 AM, Gaetan wrote: > Hello > > I recently submitted the following pull request in order to allow using git > submodules with PBR modules: https://review.openstack.org/#/c/524421/ > > To give a little bit of context, in my team, all our python modules are > followin

[openstack-dev] [pbr] Git submodules support

Hello I recently submitted the following pull request in order to allow using git submodules with PBR modules: https://review.openstack.org/#/c/524421/ To give a little bit of context, in my team, all our python modules are following almos the same pattern: - python 3 only - setup.py/setuptools/d

Re: [openstack-dev] [all] Switching to longer development cycles

On 13/12/17 11:17, Thierry Carrez wrote: So... What do you think ? Some points against that I haven't seen mentioned much yet: * Following our standard deprecation policy, it would take up to 3 years to remove anything. For perspective, 3 years ago we had just shipped Juno. (I feel old now.)

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

Quick update for third party CI owners, if you are using “DEVSTACK_GATE_TEMEPST_ALL_PLUGIN=1” in your CI you will need to disable that and use the TEMPEST_PLUGINS+= in your local config as described below to enable *only* the ironic-tempest-plugin. If you have …TEMPEST_ALL_PLUGIN=1 set it’ll lo

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On Tue, Dec 19, 2017 at 9:53 AM, Ben Nemec wrote: > The reboot is done (mostly...see below). > > On 12/18/2017 05:11 PM, Joe Talerico wrote: >> >> Ben - Can you provide some links to the ovs port exhaustion issue for >> some background? > > > I don't know if we ever had a bug opened, but there's s

Re: [openstack-dev] [castellan] Removing Keystoneauth Dependency in Castellan Discussion

On Tue, Dec 12, 2017 at 5:34 PM, Doug Hellmann wrote: > Excerpts from Dave McCowan (dmccowan)'s message of 2017-12-12 21:36:51 > +: > > > > On 12/12/17, 3:15 PM, "Doug Hellmann" wrote: > > > > >Excerpts from Dave McCowan (dmccowan)'s message of 2017-12-12 19:56:49 > > >+: > > >> > > >> O

[openstack-dev] [tripleo] The Weekly Owl - 3rd Edition

Note: this is the third edition of a weekly update of what happens in TripleO, with a little touch of fun. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. +-+ | Gene

Re: [openstack-dev] [TripleO] Planning for job execution outside the gate with Zuul v3

On Mon, Nov 20, 2017 at 3:31 PM, David Moreau Simard wrote: > Hi, > > As the migration of review.rdoproject.org to Zuul v3 draws closer, I'd like > to open up the discussion around how we want to approach an eventual > migration to Zuul v3 outside the gate. > I'd like to take this opportunity to a

[openstack-dev] [Neutron] Weekly IRC meeting cancelled on December 25th

Hi Neutron Team, We will cancel the weekly IRC meeting on Monday December 25th. We will resume on Tuesday January 2nd at 1400UTC Best regards Miguel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

Please feel free to reach out to me (jlvillal) on IRC (#openstack-ironic) or here if anyone has questions on how to transition over. For our Ironic jobs it was about a 4 line change per job. See the openstack/ironic patch here: https://review.openstack.org/#/c/527730/ Basically need to bring in t

Re: [openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

On 19 December 2017 at 08:21, Lucas Alvares Gomes wrote: > Hi all, > > Just sending this email to try to understand the model for stable branch > maintenance in networking-ovn (potentially other neutron drivers too). > > Right now, only members of the ``neutron-stable-maint`` gerrit group are > a

Re: [openstack-dev] [docs][ptls][all] documentation retention policy changes

On Tue, 17 Oct 2017 19:15:32 +0200 Petr Kovar wrote: > On Thu, 28 Sep 2017 12:51:18 -0400 > Doug Hellmann wrote: > > > At the Queens PTG in Denver the documentation team members present > > discussed a new retention policy for content published to > > docs.openstack.org. I have a spec up for re

[openstack-dev] [tc] [all] TC Report 51

( Clicky bits included: https://anticdent.org/tc-report-51.html ) This will be the last TC Report of the year, expect the next one around the 9th of January. We're closing out the year with a series of discussions about making changes to deal with various frustrations in the contributor communi

[openstack-dev] Nominate Joseph Davis to Monasca core

Hello everyone, And another nomination. I would like to add Joseph Davis to the Monasca core reviewers team. Happy reviewing, Witek __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-

[openstack-dev] [neutron][networking-ovn] Stable branch maintainers for networking-ovn

Hi all, Just sending this email to try to understand the model for stable branch maintenance in networking-ovn (potentially other neutron drivers too). Right now, only members of the ``neutron-stable-maint`` gerrit group are able to approve patches for the stable branches; this can cause some del

Re: [openstack-dev] [all] Switching to longer development cycles

On 12/13/2017 11:17 AM, Thierry Carrez wrote: Hi everyone, Over the past year, it has become pretty obvious to me that our self-imposed rhythm no longer matches our natural pace. It feels like we are always running elections, feature freeze is always just around the corner, we lose too much time

[openstack-dev] Mixed service version CI testing

During discussion in the TC channel today [1], we got talking about how there is a perception that you must upgrade all of the services together for anything to work, at least the 'core' services like keystone/nova/cinder/neutron/glance - although maybe that's really just nova/cinder/neutron?

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

Dell - Internal Use - Confidential Dell Ironic Ci is failing on this patch because of that. With holidays and many on vacation, would appreciate some additional time to make the switch. Thanks Rajini From: Ruby Loo [mailto:opensr...@gmail.com] Sent: Tuesday, December 19, 2017 8:48 AM To: OpenStac

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

On Mon, Dec 18, 2017 at 11:29 PM, wrote: > Thanks for response. > My recommendation is: > 1. only allow patches into openstack/ironic-tempest-plugin > 2. Give Ironic CI owners time period (3 weeks?) to switch their setup to > only use openstack/ironic-tempest-plugin and not master and report back

[openstack-dev] [tripleo] Canceling weekly meetings for Dec 26th and Jan 2nd

Hey everyone, Due to likely low attendance, we'll be canceling the next two weekly meetings on Dec 26th and Jan 2nd. We'll resume weekly meetings back on Jan 9th. Happy holidays and stuff. Thanks, -Alex __ OpenStack Develop

[openstack-dev] [FEMDC] Wed. 20 Dec - IRC Meeting 15:00 UTC

Dear all, A gentle reminder for our Wednesday meeting at 15:00 UTC A draft agenda is available at line 1638, you are very welcome to add any item. https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017

Re: [openstack-dev] [cinder][ceilometer] cinder capacity notifications

On 12/12, gordon chung wrote: > hi, > > i'm attempting to add support for the cinder capacity notifications that > were added a while back[1]. > > adding measurement support in ceilometer is pretty simple where in most > cases you just add an entry to a yaml file[2]. the problem i have right > now

Re: [openstack-dev] [all] [security] Security SIG

This is an important evolution for the security group / project / SIG! Congratulations everyone on taking things this far and to Luke for your excellent stewardship. -Rob On Thu, Dec 14, 2017 at 5:30 PM, Luke Hinds wrote: > Hi All, > > Following on from the mailing list discussion [0], we now

[openstack-dev] [neutron] Bug deputy report

Hello, I was on bug deputy between 11.12.2017 and 18.12.2017. Below short summary about bugs reported in this time. https://bugs.launchpad.net/neutron/+bug/1737917 - not prioritized, for me it looks like some issue with l2pop so if someone is familiar with l2pop, please check it. I asked Migue