Re: [openstack-dev] [charms]

+1 On Wed, 14 Feb 2018 at 11:29 Liam Young wrote: > Hi, > > I would like to propose that we do not support the notifications > method for automatically creating DNS records in Queens+. This method > for achieving Neutron integration has been superseded both upstream >

Re: [openstack-dev] [charms]

+1 On Wed, 14 Feb 2018 at 11:29 Liam Young wrote: > Hi, > > I would like to propose that we do not support the notifications > method for automatically creating DNS records in Queens+. This method > for achieving Neutron integration has been superseded both upstream >

Re: [openstack-dev] [charms]

Yes, that seems like a reasonable approach. +1 On Wed, Feb 14, 2018 at 11:29 AM, Liam Young wrote: > Hi, > > I would like to propose that we do not support the notifications > method for automatically creating DNS records in Queens+. This method > for achieving Neutron

Re: [openstack-dev] [tripleo] [neutron] Current containerized neutron agents introduce a significant regression in the dataplane

On Wed, Feb 14, 2018 at 5:40 AM, Brian Haley wrote: > On 02/13/2018 05:08 PM, Armando M. wrote: > >> >> >> On 13 February 2018 at 14:02, Brent Eagles beag...@redhat.com>> wrote: >> >> Hi, >> >> The neutron agents are implemented in such a way

Re: [openstack-dev] [tripleo] [neutron] Current containerized neutron agents introduce a significant regression in the dataplane

On 2/14/18 11:58 AM, Daniel Alvarez Sanchez wrote: On Wed, Feb 14, 2018 at 5:40 AM, Brian Haley > wrote: On 02/13/2018 05:08 PM, Armando M. wrote: On 13 February 2018 at 14:02, Brent Eagles

[openstack-dev] [charms]

Hi, I would like to propose that we do not support the notifications method for automatically creating DNS records in Queens+. This method for achieving Neutron integration has been superseded both upstream and in the charms. By removing support for it in Queens we prevent the charm from

Re: [openstack-dev] [all][infra] PTG Infra Helproom Info and Signup

Clark Boylan wrote: > Last PTG the infra helproom seemed to work out for projects that knew about > it. The biggest problem seemed to be that other projects either just weren't > aware that there is/was an Infra helproom or didn't know when an appropriate > time to show up would be. We are

Re: [openstack-dev] [infra] [all] project pipeline definition should stay in project-config or project side ?

On Wed, Feb 14, 2018 at 6:45 AM, Andreas Jaeger wrote: On 2018-02-14 01:28, Ghanshyam Mann wrote: On Wed, Feb 14, 2018 at 12:06 AM, Paul Belanger wrote: On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote: Hi Infra Team, I have 1 quick question

Re: [openstack-dev] [mistral][release][ffe] Requesting FFE for supporting source execution id in the Mistral client

On 14 February 2018 at 10:03, Renat Akhmerov wrote: > Hi, > > We were asked to do a FFE request to be able to release a new version of > Mistral client out of stable/queens branch. > > The backport patch: https://review.openstack.org/#/c/543393/ > The release patch:

[openstack-dev] [mistral][release][ffe] Requesting FFE for supporting source execution id in the Mistral client

Hi, We were asked to do a FFE request to be able to release a new version of Mistral client out of stable/queens branch. The backport patch: https://review.openstack.org/#/c/543393/ The release patch: https://review.openstack.org/#/c/543402 The reason to do that after the feature freeze is

Re: [openstack-dev] [infra] [all] project pipeline definition should stay in project-config or project side ?

On Wed, Feb 14, 2018 at 6:21 PM, Balázs Gibizer wrote: > > > On Wed, Feb 14, 2018 at 6:45 AM, Andreas Jaeger wrote: >> >> On 2018-02-14 01:28, Ghanshyam Mann wrote: >>> >>> On Wed, Feb 14, 2018 at 12:06 AM, Paul Belanger >>>

[openstack-dev] [publiccloud-wg] Reminder for todays meeting

Hi all, Time again for a meeting for the Public Cloud WG - today at 1400 UTC in #openstack-meeting-3 Agenda and etherpad at: https://etherpad.openstack.org/p/publiccloud-wg See you later! Tobias Rydberg -- Tobias Rydberg Senior Developer Mobile: +46 733 312780 www.citynetwork.eu |

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

On Fri, Jan 26, 2018 at 5:57 PM James E. Blair wrote: > 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

Re: [openstack-dev] [security] Security PTG Planning, x-project request for topics.

Hi Luke, Omer (in CC) has confirmed that he can stand in for me if needed, but my preference would be that you conference me in. If you won't know until the very day whether conference equipment is available, that's fine, we can figure it out last minute. A projector will be useful either way.

Re: [openstack-dev] [all][infra] PTG Infra Helproom Info and Signup

On Wed, Feb 14, 2018 at 10:42 AM Thierry Carrez wrote: > Clark Boylan wrote: > > Last PTG the infra helproom seemed to work out for projects that knew > about it. The biggest problem seemed to be that other projects either just > weren't aware that there is/was an Infra

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 02/13/2018 05:30 PM, David Moreau Simard wrote: On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec wrote: I guess if RDO has chosen this path then we don't have much choice. This makes it sound like we had a choice to begin with. We've already had a lot of discussions

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

Andrea Frittoli writes: >> That has no irrelevant-files matches, and so matches everything. If you >> drop the use of that template, it will work as expected. Or, if you can >> say with some certainty that nova's irrelevant-files set is not >> over-broad, you could

[openstack-dev] [requirements][trove][tatu][barbican][compass][daisycloud][freezer][fuel][nova][openstack-ansible][pyghmi][solum] Migration from pycrypto

Development has stalled, (since 2014). It's been forked but now would be a good time to move to a more actively maintained crypto library like cryptography. Requirements wishes to drop pycrypto. Let me know if there's anything we can do to facilitate this. -- Matthew Thode (prometheanfire)

[openstack-dev] [keystone] [policy] policy meeting update

Last week during the policy meeting we questioned whether or not we needed weekly meetings anymore [0], especially since the agenda has been relatively sparse recently. Let's hold off on policy meetings until we get to the PTG. There, we're going to be discussing RBAC and all that fun stuff

Re: [openstack-dev] [mistral][release][ffe] Requesting FFE for supporting source execution id in the Mistral client

On 18-02-14 17:03:10, Renat Akhmerov wrote: > Hi, > > We were asked to do a FFE request to be able to release a new version of > Mistral client out of stable/queens branch. > > The backport patch: https://review.openstack.org/#/c/543393/ > The release patch: 

[openstack-dev] [os-upstream-institute][ptg] Working sessions at the PTG

Hi, As discussed earlier we would like to leverage the opportunity to face to face working sessions at the PTG with the training team and anyone who’s interested to join/help out. We have one dedicated time slot to meet and summarize our activities during the week and list of action points

Re: [openstack-dev] [ironic][triploe] support for firmware update

On Mon, Feb 12, 2018 at 6:52 PM, Stig Telfer wrote: > Hi Moshe - > > It seems a bit risky to automatically apply firmware updates. For > example, given a node will probably be rebooted for firmware updates to > take effect, if other vendors also did this then perhaps

[openstack-dev] [designate] V1 API is now fully removed

I saw [1] and realised that we should be more explicit about the upcoming release. As highlighted in [2], this email is a reminder that the long awaited removal of the DNS V1 API is now complete with [3]. This means from Queens onwards it will not be possible to re-enable the V1 API (we have had

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

On Fri, Jan 26, 2018 at 2:05 PM Balázs Gibizer wrote: > 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: [openstack-dev] [neutron] [OVN] L3 traffic

On Tue, Feb 13, 2018 at 11:24 PM, Numan Siddique wrote: > > > On Wed, Feb 14, 2018 at 4:19 AM, Assaf Muller wrote: >> >> I'm not aware of plans for OVN to supported distributed SNAT, therefor >> a networking node will still be required for the foreseeable

[openstack-dev] [zun][kuryr][kuryr-libnetwork][neutron] Gate breakage due to removal of tag extension

Hi all, Zun's gate is currently broken due to the removal of tag extension [1] at neutron side. The reason is that Zun has a dependency on Kuryr-libnetwork and Kuryr-libnetwork relies on the tag extension that was removed. A quick fixup is to revert the tag extension removal patch [2]. This

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On Wed, Feb 14, 2018 at 11:19 AM, Ben Nemec wrote: > > I have to admit I don't entirely understand this constraint. CentOS 7 is in > support until 2024. I would think RHEL 7's timeline is similar or even > longer. If Python 2 is going out of support in 2020, does that

Re: [openstack-dev] [neutron] [networking-ovn] Non voting jobs for networking-ovn on neutron.

On Mon, Dec 4, 2017 at 5:20 AM, Miguel Angel Ajo Pelayo wrote: > We were thinking about the option of having a couple of non-voting jobs > on > the neutron check for networking-ovn. It'd be great for us, in terms of > traceability, > we re-use a lot of the neutron unit

[openstack-dev] [cinder] No Weekly Meeting 2/21/18 or 2/28/18

Team, We will not be having a weekly meeting on 2/21/2018 or 2/28/2018 due to people traveling to the PTG and the PTG itself. Regular meeting will return on 3/7/2018 . See you all at the PTG! Jay __ OpenStack

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

On Wed, Feb 14, 2018 at 4:05 PM James E. Blair wrote: > Andrea Frittoli writes: > > >> That has no irrelevant-files matches, and so matches everything. If you > >> drop the use of that template, it will work as expected. Or, if you can > >> say

Re: [openstack-dev] [horizon] collectstatic with custom theme is broken at least since Ocata

Hello Mateusz, thanks for your input. I just want to confirm that a patch was merged in master and backported all the way back to Ocata to fix the bug. details here: https://bugs.launchpad.net/horizon/+bug/1744239 thank you Saverio On 05.02.18 14:54, Mateusz Kowalski wrote: > Hi, > > We

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

On 2/5/2018 9:00 PM, Matt Riedemann wrote: Given the size and detail of this thread, I've tried to summarize the problems and possible solutions/workarounds in this etherpad: https://etherpad.openstack.org/p/nova-aggregate-filter-allocation-ratio-snafu For those working on this, please

Re: [openstack-dev] [tripleo][python3] python3 readiness?

2018-02-14 17:05 GMT+01:00 Ben Nemec : > > > On 02/13/2018 05:30 PM, David Moreau Simard wrote: >> >> On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec wrote: >>> >>> >>> I guess if RDO has chosen this path then we don't have much choice. >> >> >> This

[openstack-dev] [nova] Queens blueprint burndown chart

I sent a similar email after Pike was released [1] and these are our blueprint burndown chart results for Queens [2]. Comparing to Pike, the trends are similar, with the overall numbers down. Things ramp up until the spec freeze, then tail off, with a little spike toward the end to get things

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 02/13/2018 10:24 PM, Haïkel wrote: RDO has *yet* to choose a plan, and people were invited to work on the "stabilized" repository draft [0]. If anyone has a better plan that fits all the constraints, please share it asap. Whatever the plan, we're launching it with the Rocky cycle. Among

[openstack-dev] [oslo] Meetings for the next two weeks

Hi, I will be on PTO for the next Oslo meeting, and the week after that is the PTG so there will be no meeting. Doug Hellmann has offered to run the meeting next week if necessary, but as of this writing there is nothing new on the agenda and unless that changes I'm inclined to skip it.

Re: [openstack-dev] [charms]

Seems very reasonable. +1 On 02/14/2018 05:35 AM, Alex Kavanagh wrote: > Yes, that seems like a reasonable approach. +1 > > On Wed, Feb 14, 2018 at 11:29 AM, Liam Young > wrote: > > Hi, > > I would like to propose that we do not

Re: [openstack-dev] [requirements][trove][tatu][barbican][compass][daisycloud][freezer][fuel][nova][openstack-ansible][pyghmi][solum] Migration from pycrypto

On 18-02-14 13:55:53, Sean McGinnis wrote: > On Wed, Feb 14, 2018 at 10:09:47AM -0600, Matthew Thode wrote: > > Development has stalled, (since 2014). It's been forked but now would > > be a good time to move to a more actively maintained crypto library like > > cryptography. > > > >

Re: [openstack-dev] [FFE][requirements][release][oslo] osprofiler bug fix needed

On 18-02-12 02:14:51, Nguyễn Trọng Vĩnh (Tovin Seven) wrote: > Hello, > > Currently, Oslo release for Queens is out. > However, OSProfiler faces an issue that make some Nova CLI command not > working. > Detail for this issue: https://launchpad.net/bugs/1743586 > > Patch that fix this bug:

Re: [openstack-dev] [requirements][trove][tatu][barbican][compass][daisycloud][freezer][fuel][nova][openstack-ansible][pyghmi][solum] Migration from pycrypto

On Wed, Feb 14, 2018 at 10:09:47AM -0600, Matthew Thode wrote: > Development has stalled, (since 2014). It's been forked but now would > be a good time to move to a more actively maintained crypto library like > cryptography. > > Requirements wishes to drop pycrypto. Let me know if there's

Re: [openstack-dev] [monasca][congress] help configuring monasca for gate

Thank Witek =) We're looking at getting pushed alarm data from Monasca via webhook. Fabiog started that quite a while back and we're hoping to revive it. Not sure there is any feature requests. But I do want to understand the authentication situation in Monasca webhook. Wondering whether Congress

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 13/02/18 16:53 -0600, Ben Nemec wrote: On 02/13/2018 01:57 PM, Tom Barron wrote: Since python 2.7 will not be maintained past 2020 [1] it is a reasonable conjecture that downstream distributions will drop support for python 2 between now and then, perhaps as early as next year. I'm not

Re: [openstack-dev] [tripleo][python3] python3 readiness?

2018-02-14 22:53 GMT+01:00 Tom Barron : > On 13/02/18 16:53 -0600, Ben Nemec wrote: >> >> >> >> On 02/13/2018 01:57 PM, Tom Barron wrote: >>> >>> Since python 2.7 will not be maintained past 2020 [1] it is a reasonable >>> conjecture that downstream distributions >>> will drop

Re: [openstack-dev] [tripleo][python3] python3 readiness?

On 02/14/2018 03:26 PM, Haïkel wrote: I agree it won't be simple, we will have to provide those repositories, determine how we will gate updates, fix puppet modules, POI, etc.. and that's only a beginning. That's why we won't be providing raw Fedora but rather a curated version and at some

Re: [openstack-dev] [TripleO][ui] Network Configuration wizard

On 02/09/2018 08:49 AM, Jiri Tomasek wrote: *Step 2. network-environment -> NIC configs* Second step of network configuration is NIC config. For this network-environment.yaml is used which references NIC config templates which define network_config in their resources section. User is

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

On Thu, Feb 15, 2018 at 1:43 AM, Andrea Frittoli wrote: > > > On Wed, Feb 14, 2018 at 4:05 PM James E. Blair wrote: >> >> Andrea Frittoli writes: >> >> >> That has no irrelevant-files matches, and so matches everything.

[openstack-dev] [Election] PTL Election Results & Conclusion

Hello Everyone! Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability thank you to all those who make this process possible. Now for

[openstack-dev] [ptg] etherpad for Fast Forward Upgrading?

Hello everyone, Can someone be nice enough to point me to the Rocky Fast Forward Upgrading etherpad page? I am seeing Fast Forward Upgrading scheduled on Monday [1], but the etherpad for it is not listed in [2]. Thanks in advance. [1] https://www.openstack.org/ptg/#tab_schedule [2]

Re: [openstack-dev] [all][infra] PTG Infra Helproom Info and Signup

On 02/14, Andrea Frittoli wrote: > On Wed, Feb 14, 2018 at 10:42 AM Thierry Carrez > wrote: > > > Clark Boylan wrote: > > > Last PTG the infra helproom seemed to work out for projects that knew > > about it. The biggest problem seemed to be that other projects either just

Re: [openstack-dev] [nova] Rocky PTG early planning

> On Jan 8, 2018, at 10:33, Matt Riedemann wrote: > > As the Queens release winds to a close, I've started thinking about topics > for Rocky that can be discussed at the PTG. > > I've created an etherpad [1] for just throwing various topics in there, > completely

Re: [openstack-dev] [mistral][release][ffe] Requesting FFE for supporting source execution id in the Mistral client

Thanks! Renat Akhmerov @Nokia On 14 Feb 2018, 22:55 +0700, Matthew Thode , wrote: > On 18-02-14 17:03:10, Renat Akhmerov wrote: > > Hi, > > > > We were asked to do a FFE request to be able to release a new version of > > Mistral client out of stable/queens branch. >