Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

> Which service's logs are missing the request_id? > If I look at neutron-server logs with my current setup I get two files: neutron-server.log neutron-server.json the standard log file has in all neutron.wsgi lines information like: neutron.wsgi [req-4fda8017-50c7-40eb-9e7b-710e7fba0d01 97d34

Re: [openstack-dev] [kolla] Re: About maridb 10.1 on kolla

After using RDO mariadb, i found galera is fallback from galera-25.3.20 to 25.3.16. I am not sure what's the exact difference between these two version. But what i found is: > ‘SAFE TO BOOTSTRAP’ PROTECTION [1] > Starting with provider version 3.19, Galera has an additional protection > against a

Re: [openstack-dev] [neutron] Stepping down from core

On Sat, Dec 16, 2017 at 4:01 AM, Armando M. wrote: > Hi neutrinos, > > To some of you this email may not come as a surprise. it was a surprise to me. > > During the past few months my upstream community engagements have been more > and more sporadic. While I tried hard to stay committed and fulf

[openstack-dev] The OpenStack Magnum service whether to supports Kubernetes Cluster/Bay auto scaling

Hi，all In Pike version, the OpenStack Magnum container service whether to supports Kubernetes Cluster/Bay node to auto scaling？ At present, the backend engine Swarm supports Cluster/Bay node auto scaling. Best Regards chao.xu

Re: [openstack-dev] [qa] [tc] Need champion for "cold upgrades capabilities" goal

Emilien Macchi wrote: > [...] > This is the list of service projects that don't have the tag yet: > aodh > blazar > cloudkitty > congress > dragonflow > ec2api > freezer > karbor > kuryr > masakari > mistral > monasca > murano > octavia > panko > searchlight > senlin > tacker > trove > vitrage > wa

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

Yeah, help means to be the "Champion" for me :-) 2018-01-12 14:22 GMT+08:00 Emilien Macchi : > On Thu, Jan 11, 2018 at 9:59 PM, ChangBo Guo wrote: > > I would like to help the goal - enable mutable configuration, would like > to > > post a patch for that later. > > are you interested to be the

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On Thursday, 11 January 2018 23:52:00 CET Matt Riedemann wrote: > On 1/11/2018 10:36 AM, Colleen Murphy wrote: > > 1) All trademark-related tests should go in the tempest repo, in > > accordance > > > > with the original resolution. This would mean that even projects that > > have > >

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

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] [nova] [placement] resource providers update 18-02

Resource provider and placement 18-02. Getting a bit more warmed up here, so should be more stuff from more places. # Most Important Completing alternate hosts and exposing the basic nested resource providers functionality is what matters. We've reached that stage in the cycle where at least so

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Excerpts from Luigi Toscano's message of 2018-01-12 10:49:55 +0100: > On Thursday, 11 January 2018 23:52:00 CET Matt Riedemann wrote: > > On 1/11/2018 10:36 AM, Colleen Murphy wrote: > > > 1) All trademark-related tests should go in the tempest repo, in > > > accordance > > > > > > with the or

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Saverio Proto's message of 2018-01-12 09:17:55 +0100: > > Which service's logs are missing the request_id? > > > If I look at neutron-server logs with my current setup I get two files: > > neutron-server.log > neutron-server.json > > the standard log file has in all neutron.wsgi li

[openstack-dev] [horizon][trunk][ngdetails] Trunk admin panel and changes related to ngdetails patches

Hi Horizon Team I read the meeting log (http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-01-10-20.00.log.html) and if I understand well the proposal is to merge part of the ngdetails patches (https://review.openstack.org/#/q/topic:bug/1681627+(status:open) ) in Queens, and a

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

On Fri, Jan 12, 2018 at 1:27 AM, ChangBo Guo wrote: > Yeah, help means to be the "Champion" for me :-) That's very cool, if you can write a proposal in governance, similar to https://review.openstack.org/#/c/532361/ (Example with Sean). The community will vote on which goals we take for Rocky.

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

Here's a quick update before the weekend: 2 goals were proposed to governance: Remove mox https://review.openstack.org/#/c/532361/ Champion: Sean McGinnis (unless someone else steps up) Ensure pagination links https://review.openstack.org/#/c/532627/ Champion: Monty Taylor 2 more goals are abou

[openstack-dev] [qa][neutron][octavia][horizon][networking-l2gw] Renaming tox_venvlist in Zuul v3 run-tempest

The Zuul v3 tox jobs use "tox_envlist" to name the tox environment to use, the tempest run-tempest role used "tox_venvlist" with an extra "v" in it. This lead to some confusion and a wrong fix, so let's be consistent across these jobs. I've just pushed changes under the topic tox_envlist to sync t

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

I was reading a tweet from Jean-Daniel and wondering if there would be an appropriate community goal regarding support of some of the later API versions or whether this would be more of a per-project goal. https://twitter.com/pilgrimstack/status/951860289141641217 Interesting numbers about cust

[openstack-dev] [network-ovn] SNAT traffic in OVN.

Hi all, Networking-ovn will support distributed floating IP, how about the snat traffic? Will in every compute node or not? Any suggestions are welcomed. __ OpenStack Development Mailing List (not for usage questions) Unsubscri

[openstack-dev] [keystone] Keystone Team Update - Week of 8 January 2018

# Keystone Team Update - Week of 8 January 2018 ## News ### PTG We're still brainstorming for the PTG. If you have any topic proposals, please add them to the etherpad[1]. We'll need to coordinate with other teams to schedule discussion time on our major cross-project topics, especially unified

[openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

Since we are discussing goals for the Rocky cycle, I would like to propose a change to the way we track progress on the goals. We've started to see lots and lots of changes to the goal documents, more than anticipated when we designed the system originally. That leads to code review churn within t

[openstack-dev] Developer Mailing List Digest January 5-12th

Contribute to the Dev Digest by summarizing OpenStack Dev List thread: * https://etherpad.openstack.org/p/devdigest * http://lists.openstack.org/pipermail/openstack-dev/ * http://lists.openstack.org/pipermail/openstack-sigs HTML version: https://www.openstack.org/blog/2018/01/developer-mailing-l

[openstack-dev] [storyboard] need help figuring out how to use auth with storyboard client

The storyboard client docs mention an "access token" [1] as something a client needs in order to create stories and make other sorts of changes. They don't explain what that token is or how to get one, though. Where do I get a token? How long does the token work? Can I safely put a token in a con

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

Hi everyone, Today, we opened the Call for Presentations for the Vancouver Summit , which will take place May 21-24. The deadline to submit your proposal is February 8th.

Re: [openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

On Fri, Jan 12, 2018 at 12:37 PM, Doug Hellmann wrote: > Since we are discussing goals for the Rocky cycle, I would like to > propose a change to the way we track progress on the goals. > > We've started to see lots and lots of changes to the goal documents, > more than anticipated when we designe

Re: [openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

On Fri, Jan 12, 2018 at 01:11:40PM -0800, Emilien Macchi wrote: > On Fri, Jan 12, 2018 at 12:37 PM, Doug Hellmann wrote: > > Since we are discussing goals for the Rocky cycle, I would like to > > propose a change to the way we track progress on the goals. > > > > We've started to see lots and lots

Re: [openstack-dev] [storyboard] need help figuring out how to use auth with storyboard client

On Fri, Jan 12, 2018, at 12:57 PM, Doug Hellmann wrote: > The storyboard client docs mention an "access token" [1] as something > a client needs in order to create stories and make other sorts of > changes. They don't explain what that token is or how to get one, > though. > > Where do I get a to

Re: [openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

> > > > How does this sound as an approach? Does anyone have any reservations > > about using storyboard this way? > > Sounds like a good idea, and will help to "Eat Our Own Dog Food" (if > we want Storyboard adopted at some point). My thoughts as well. This would be a good way to get more people

Re: [openstack-dev] [storyboard] need help figuring out how to use auth with storyboard client

On 2018-01-12 15:57:44 -0500 (-0500), Doug Hellmann wrote: > The storyboard client docs mention an "access token" [1] as something > a client needs in order to create stories and make other sorts of > changes. They don't explain what that token is or how to get one, > though. > > Where do I get a

Re: [openstack-dev] [qa][neutron][octavia][horizon][networking-l2gw] Renaming tox_venvlist in Zuul v3 run-tempest

On Fri, Jan 12, 2018 at 05:13:28PM +0100, Andreas Jaeger wrote: > The Zuul v3 tox jobs use "tox_envlist" to name the tox environment to > use, the tempest run-tempest role used "tox_venvlist" with an extra "v" > in it. This lead to some confusion and a wrong fix, so let's be > consistent across the

Re: [openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

I think this is a great idea! This would really help with getting more eyes on StoryBoard. I think a lot of people haven't touched it much in the last year or two and aren't aware of all of its capabilities at this point and this would be a great way to get people up to speed. This use case (cros

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

On 01/12/2018 11:09 AM, Tim Bell wrote: > I was reading a tweet from Jean-Daniel and wondering if there would be an > appropriate community goal regarding support of some of the later API > versions or whether this would be more of a per-project goal. > > https://twitter.com/pilgrimstack/status

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

> I don't think this is a configuration problem. > > Which version of the oslo.log library do you have installed? Hello Doug, I use the Ubuntu packages, at the moment I have this version: python-oslo.log 3.16.0-0ubuntu1~cloud0 thank you Saverio _

[openstack-dev] [glance][oslo][requirements] oslo.serialization fails with glance

https://review.openstack.org/531788 is the review we are seeing it in, but 2.22.0 failed as well. I'm guessing it was introduced in either https://github.com/openstack/oslo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8 or https://github.com/openstack/oslo.serialization/commit/cdb2