Re: [openstack-dev] [requirements] [vitrage][glance][ironic] global requirements update for python-vitrageclient

Also seeing this for the u-c [1] and g-r [2] bumps for python-ironicclient 2.2.0. These are required in order to use the ironic node traits feature in nova. [1] https://review.openstack.org/#/c/538093 [2] https://review.openstack.org/#/c/538066/3 On 25 January 2018 at 11:15, Afek, Ifat (Nokia -

Re: [openstack-dev] [tripleo] Upgrade community weekly meeting

Hi All, After few weeks and meetings on Friday, we decide to change a little bit the pattern of this meeting. We decided to keep the schedule up and open for anything/anyone, but each times, we will check before the meeting if the agenda [1] is empty. If so, then we won't make it, or we would use

Re: [openstack-dev] [requirements] [vitrage][glance][ironic] global requirements update for python-vitrageclient

Looks like this should be resolved by https://review.openstack.org/#/c/537453/. Mark On 26 January 2018 at 10:33, Mark Goddard wrote: > Also seeing this for the u-c [1] and g-r [2] bumps for python-ironicclient > 2.2.0. These are required in order to use the ironic node

[openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

Hi, I'm getting more and more confused how the zuul job hierarchy works or is supposed to work. First there was a bug in nova that some functional tests are not triggered although the job (re-)definition in the nova part of the project-config should not prevent it to run [1]. There we

Re: [openstack-dev] [tripleo] CI'ing ceph-ansible against TripleO scenarios

On 01/26/2018 01:49 AM, Paul Belanger wrote: > On Thu, Jan 25, 2018 at 04:22:56PM -0800, Emilien Macchi wrote: >> Is there any plans to run TripleO CI jobs in ceph-ansible? >> I know the project is on github but thanks to zuulv3 we can now easily >> configure ceph-ansible to run Ci jobs in

Re: [openstack-dev] [tripleo] Upgrade community weekly meeting

Hi All, After few weeks and meetings on Friday, we decide to change a little bit the pattern of this meeting. We decided to keep the schedule up and open for anything/anyone, but each times, we will check before the meeting if the agenda [1] is empty. If so, then we won't make it, or we would use

Re: [openstack-dev] [ALL][requirements] A freeze is coming and you should be prepared

On 1/26/2018 12:12 AM, Matthew Thode wrote: Last day, gate is sad and behind, but not my fault you waited til the last minute :P (see my first comment). The Iceman Cometh! Well, the requirements jobs seem to be busted as well:

Re: [openstack-dev] [requirements] [vitrage][glance][ironic] global requirements update for python-vitrageclient

On 18-01-26 10:47:38, Mark Goddard wrote: > Looks like this should be resolved by > https://review.openstack.org/#/c/537453/. > Mark > > On 26 January 2018 at 10:33, Mark Goddard wrote: > > > Also seeing this for the u-c [1] and g-r [2] bumps for python-ironicclient > >

Re: [openstack-dev] [tc] [all] TC Report 18-04

On 1/23/2018 12:40 PM, Chris Dent wrote: ## OpenStack-wide Goals There are four proposed [OpenStack-wide goals](https://governance.openstack.org/tc/goals/index.html): * [Add Cold upgrades   capabilities](https://review.openstack.org/#/c/533544/) * [Add Rocky goal to remove  

[openstack-dev] [release][ptl][all] extending queens-3 milestone deadlines

This morning during the release team meeting [1] the team agreed that given the issues with CI this week it makes sense to extend the deadlines for the milestone. The queens-3 deadline for projects following the cycle-with-milestones release model is extended to Monday 29 January. The

Re: [openstack-dev] [ALL][requirements] A freeze is coming and you should be prepared

On Fri, Jan 26, 2018 at 9:46 AM, Matt Riedemann wrote: > > Well, the requirements jobs seem to be busted as well: > > http://logs.openstack.org/93/538093/1/check/legacy-requireme > nts-integration-dsvm/157d877/job-output.txt.gz#_2018-01-26_11_17_31_182762 The fix is in the

Re: [openstack-dev] [horizon][packaging] django-openstack-auth retirement

On 2018-01-24 08:47:30 -0600 (-0600), Monty Taylor wrote: [...] > Horizon and neutron were updated to start publishing to PyPI > already. > > https://review.openstack.org/#/c/531822/ > > This is so that we can start working on unwinding the neutron and > horizon specific versions of jobs for

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

On 2018-01-26 08:57:02 -0800 (-0800), James E. Blair wrote: [...] > Perhaps a method of automatically noting the dependencies in git > notes could help with that case? Or maybe use a different way of > communicating that information -- even with change-ids, there's > still a lot of missing

Re: [openstack-dev] [nova][neutron][infra] zuul job definitions overrides and the irrelevant-file attribute

Balázs Gibizer writes: > Hi, > > I'm getting more and more confused how the zuul job hierarchy works or > is supposed to work. Hi! First, you (or others) may or may not have seen this already -- some of it didn't exist when we first rolled out v3, and some of it

Re: [openstack-dev] [tc] [all] TC Report 18-04

Excerpts from Matt Riedemann's message of 2018-01-26 09:38:18 -0600: > On 1/23/2018 12:40 PM, Chris Dent wrote: > > ## OpenStack-wide Goals > > > > There are four proposed [OpenStack-wide > > goals](https://governance.openstack.org/tc/goals/index.html): > > > > * [Add Cold upgrades > >  

Re: [openstack-dev] [tc] [all] TC Report 18-04

On 1/26/2018 9:57 AM, Doug Hellmann wrote: Ideally we would use the time at the PTG to discuss implementation details. For something like the mox one, there really are no implementation details, are there? -- Thanks, Matt

Re: [openstack-dev] [neutron][l3][flavors][floatingip] FFE request for patch no 523257 and 532993

Manjeets, This FFE has been approved. Tracking it here: https://launchpad.net/neutron/+milestone/queens-rc1 Cheers On Thu, Jan 25, 2018 at 12:17 PM, Bhatia, Manjeet S < manjeet.s.bha...@intel.com> wrote: > Hello all ! > > > > I’d like to request a FFE for patch 523257 [1] that adds new

Re: [openstack-dev] [tc] [all] TC Report 18-04

Excerpts from Matt Riedemann's message of 2018-01-26 10:08:46 -0600: > On 1/26/2018 9:57 AM, Doug Hellmann wrote: > > Ideally we would use the time at the PTG to discuss implementation > > details. > > For something like the mox one, there really are no implementation > details, are there? >

[openstack-dev] [tc] Technical Committee Status update, January 26th

Hi! This is the weekly summary of Technical Committee initiatives. You can find the full list of all open topics (updated twice a week) at: https://wiki.openstack.org/wiki/Technical_Committee_Tracker If you are working on something (or plan to work on something) governance-related that is not

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

Mathieu Gagné writes: > On Thu, Jan 25, 2018 at 7:08 PM, James E. Blair wrote: >> Mathieu Gagné writes: >> >>> On Thu, Jan 25, 2018 at 3:55 PM, Ben Nemec wrote: I'm curious what this means as

[openstack-dev] [Neutron] q-3 tag and FFE being tracked

Hi Neutron Team, This is our Queens 3 milestone patch: https://review.openstack.org/#/c/537651/. Please note that we still have to create a tag for VPNaaS, which recently rejoined the Neutron Stadium We have also created a list that we are targeting for RC1:

Re: [openstack-dev] [masakari] BUG in Masakari Installation and Procedure and/or Documentation

Update on this. It turned out that i had incorrectly set the ‘project_name’ and ‘username’ in /etc/masakarimonitors/masakarimonitors.conf Setting both these attributes to ‘admin’ made it such that the instancemonitor’s notification to masakari-engine was successful. e.g.

Re: [openstack-dev] [Neutron] q-3 tag and FFE being tracked

This is the patch for VPNaaS: https://review.openstack.org/#/c/538295/ On Fri, Jan 26, 2018 at 1:39 PM, Miguel Lavalle wrote: > Hi Neutron Team, > > This is our Queens 3 milestone patch: > > https://review.openstack.org/#/c/537651/. > > Please note that we still have to

Re: [openstack-dev] [requirements] [vitrage][glance][ironic] global requirements update for python-vitrageclient

Sorry for the late reply. https://review.openstack.org/#/c/537453/ merged a few hours ago and the "can't copy" error should no longer occur. On Fri, Jan 26, 2018 at 10:22 AM, Matthew Thode wrote: > On 18-01-26 10:47:38, Mark Goddard wrote: >> Looks like this should be

Re: [openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

Should be no issues with python-octaviaclient, we do not use the short options. Michael On Fri, Jan 26, 2018 at 1:03 PM, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2018-01-18 10:15:16 -0500: >> We've been working this week to resolve an issue between

Re: [openstack-dev] [tc] Technical Committee Status update, January 26th

On 1/26/2018 10:26 AM, Thierry Carrez wrote: NB: mriedem suggested on the ML that we wait until the PTG in Dublin to make the final call. It gives more time to carefully consider the goals, but delays the start of the work and makes planning pre-PTG a bit more difficult. Sorry. Did anyone talk

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Sorry about the delay. This Week's Priorities (as of the weekly ironic meeting)

[openstack-dev] [trove] Retiring the trove-integration repository, final call

Initial indication was provided in July last year, that the trove-integration repository was going away. All the elements have been merged into trove, and are being maintained there. I do not believe anyone spoke up then. If anyone is depending on the separate repository, do speak up. Cheers,

Re: [openstack-dev] Vancouver Summit CFP is open - what’s new

On 1/12/2018 2:59 PM, Lauren Sell wrote: Hi everyone, Today, we opened the Call for Presentations for the Vancouver Summit , which will take place May 21-24. The

[openstack-dev] [blazar][release] we need a new blazar client release

The PyPI service is now validating package metadata more strictly, and the classifier values for python-blazarclient do not pass the validation checks. This means the 1.0.0 package we built cannot be uploaded to PyPI [1]. The fix will take several steps. 1. dmsimard has proposed [2] to master to

Re: [openstack-dev] Vancouver Summit CFP is open - what’s new

We will reach out to PTLs directly to solicit Protect Updates. Thanks!! Jimmy McArthur 512.965.4846 > On Jan 26, 2018, at 6:07 PM, Matt Riedemann wrote: > >> On 1/12/2018 2:59 PM, Lauren Sell wrote: >> Hi everyone, >> Today, we opened the Call for

Re: [openstack-dev] [blazar][release] we need a new blazar client release

Excerpts from Doug Hellmann's message of 2018-01-26 16:41:23 -0500: > The PyPI service is now validating package metadata more strictly, and > the classifier values for python-blazarclient do not pass the validation > checks. This means the 1.0.0 package we built cannot be uploaded to > PyPI [1].

Re: [openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

Excerpts from Doug Hellmann's message of 2018-01-18 10:15:16 -0500: > We've been working this week to resolve an issue between cliff and > barbicanclient due to a collision in the option namespace [0]. > Barbicanclient was using the -s option, and then cliff's lister > command base class added

Re: [openstack-dev] [ALL][requirements] A freeze is coming and you should be prepared

On 18-01-26 00:12:38, Matthew Thode wrote: > On 18-01-24 22:32:27, Matthew Thode wrote: > > On 18-01-24 01:29:47, Matthew Thode wrote: > > > On 18-01-23 01:23:50, Matthew Thode wrote: > > > > Requirements is freezing Friday at 23:59:59 UTC so any last > > > > global-requrements updates that need

Re: [openstack-dev] Help still needed at FOSDEM!

Boris - It's a fairly low commitment. It's just for an hour, standing at the OpenStack booth, answering questions that tend to be at a very basic level (e.g. What's OpenStack?). You can sign up for a slot via the etherpad here: https://etherpad.openstack.org/p/fosdem-2018 Best, -m.

Re: [openstack-dev] [blazar][release] we need a new blazar client release

Hi Doug, Thanks for the info and fixes. I pushed a patch for blazar client 1.0.1 release[1]. 1. https://review.openstack.org/538368 best regards, Masahito On 2018/01/27 6:44, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2018-01-26 16:41:23 -0500: The PyPI service is now

[openstack-dev] [congress][requirements][RFE] adding tenacity to congress requirements

Looking to add tenacity to congress requirements because it's needed by a forthcoming bug fix. No change to requirements repo. Does this need an exception? Thanks a lot! https://review.openstack.org/#/c/538369/ Eric Kao