Re: [openstack-dev] [tc] [election] NON nomination for TC

Thank you for all your hard work and serving as a great role model, Sean. On 03/10/17 05:03, Sean Dague wrote: > I'd like to announce that after 4 years serving on the OpenStack > Technical Committee, I will not be running in this fall's > election. Over the last 4 years we've navigated some

[openstack-dev] [congress] drivers conf discussion

Continuing from the 10/5 IRC discussion on drivers conf, here I've laid out some decision points and incomplete pros and cons. If you're interested, please add relevant pros and cons as well as further discussion on your thoughts and preferences on the decision points. Thanks!

Re: [openstack-dev] [octavia] Proposing Nir Magnezi as Octavia core reviewer

+1 Welcome Nir, well earned. German On 10/4/17, 4:28 PM, "Michael Johnson" wrote: Hello OpenStack folks, I would like to propose Nir Magnezi as a core reviewer on the Octavia project. He has been an active contributor to the Octavia projects for a

Re: [openstack-dev] [all][elections] Candidate proposals for TC (Technical Committee) positions are now open

On Sun, Oct 01, 2017 at 11:26:33PM +, Kendall Nelson wrote: > Hello Again, > > A few corrections from the kickoff email: > > Candidates for the Technical Committee Positions: Any Foundation individual > member can propose their candidacy for an available, directly-elected TC > seat. (except

[openstack-dev] [octavia] Proposing Nir Magnezi as Octavia core reviewer

Hello OpenStack folks, I would like to propose Nir Magnezi as a core reviewer on the Octavia project. He has been an active contributor to the Octavia projects for a few releases and has been providing solid patch review comments. His review stats are also in line with other core reviewers.

Re: [openstack-dev] [tripleo] bugs moved to queens-2

On 10/04/2017 03:22 PM, Alex Schultz wrote: > Hey everyone, > > So during our IRC meeting[0], it was mentioned that we should move <= > Medium bugs over to queens-2 to help with visibility of more important > bugs. Since we had 470+ total bugs targeted to queens-1, I have moved > all the medium

Re: [openstack-dev] [policy] AWS IAM session

Yeah. Very interesting. Thanks for sharing. Kevin From: Adam Heczko [ahec...@mirantis.com] Sent: Wednesday, October 04, 2017 2:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [policy] AWS IAM session Hi

[openstack-dev] [tripleo] bugs moved to queens-2

Hey everyone, So during our IRC meeting[0], it was mentioned that we should move <= Medium bugs over to queens-2 to help with visibility of more important bugs. Since we had 470+ total bugs targeted to queens-1, I have moved all the medium bugs that were not yet In Progress to queens-2 and will

Re: [openstack-dev] [policy] AWS IAM session

Hi Devdatta, excellent post on IAM models. Thank you! On Wed, Oct 4, 2017 at 10:59 PM, Devdatta Kulkarni < kulkarni.devda...@gmail.com> wrote: > +1 > > I spent some time recently studying IAM models of AWS and GCP. > Based on this I had created following post comparing and summarizing the > two

Re: [openstack-dev] [policy] AWS IAM session

+1 I spent some time recently studying IAM models of AWS and GCP. Based on this I had created following post comparing and summarizing the two models at high-level: http://devcentric.io/2017/07/13/comparing-iam-models-of-aws-and-gcp/ Thought of sharing it here as it may help with big-picture

Re: [openstack-dev] [tc] [election] NON nomination for TC

On Mon, Oct 2, 2017 at 10:03 AM, Sean Dague wrote: > I'd like to announce that after 4 years serving on the OpenStack > Technical Committee, I will not be running in this fall's > election. Over the last 4 years we've navigated some rough seas > together, including the transition

Re: [openstack-dev] [docs] Evidence of Success

Emilien Macchi October 4, 2017 at 12:35 PM The draft is really good! It reflects very well what we said we would do at the PTG, way to go. I think the next steps would be: - Definition of Done, or how you consider something achieved (code merged, doc published,

Re: [openstack-dev] [ptg] Simplification in OpenStack

On 10:45 Sep 12, Mike Perez wrote: > Hey all, > > Back in a joint meeting with the TC, UC, Foundation and The Board it was > decided as an area of OpenStack to focus was Simplifying OpenStack. This > intentionally was very broad so the community can kick start the conversation > and help tackle

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

FYI, a container with net=host runs exactly like it was running outside of a container with respect to iptables/networking. So that should not be an issue. If it can be done on the host, it should be able to happen in a container. Thanks, Kevin From: Dan Prince

Re: [openstack-dev] [docs] Evidence of Success

On Wed, Oct 4, 2017 at 8:46 AM, Jimmy McArthur wrote: > I've made a bit of progress on the collaborative vision for the Docs team: > https://docs.google.com/document/d/1Xy78CnmnKlQ7SbR1XewqgrUdGe7DqnKAGYw_9aj5Ndg/edit# > > This still needs plenty of work, but I wanted to put

[openstack-dev] [sahara] Meeting time

Hi saharans and meeting time organizers, during the Denver PTG the sahara team agreed that the best meeting time for the whole team is on Thursday at 14:00UTC. Currently we work with a changing meeting time, one week it is at 14UTC and the other is at 18UTC. We would like to ask the meeting

[openstack-dev] [cinder][sydney summit] Etherpad for information relevant to the Cinder Team ...

Team, It was discussed in today's team meeting that it would be good to start collecting information about who is going to Sydney, what forum sessions we have planned, etc. I have started an etherpad with this goal in mind [1]. If you have information or sessions that are relevant for the

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Wed, Oct 4, 2017 at 9:10 AM, Dmitry Tantsur wrote: > (top-posting, as it is not a direct response to a specific line) > > This is your friendly reminder that we're not quite near containerized > ironic-inspector. The THT for it has probably never been tested at all, and >

Re: [openstack-dev] Odp.: Odp.: [neutron][lbaasv2][agent implementation] L7 policy support

Hi Mihaela, The old neutron-lbaas haproxy namespace driver does not have L7 support. Only the Octavia driver and some vendor provider drivers have L7 support. Michael On Tue, Oct 3, 2017 at 11:35 PM, Pawel Suder wrote: > Hello, > > > It seems that

[openstack-dev] [ironic] Using pxe-drac driver

Hi, I have been using agent_ipmitool to discover and provision Dell servers with different OSes(RHEL7.3/7.4,Fedora25/26,Ubuntu Xenial) I have recently tried using pxe_drac with no luck finding how to get it to work fully I need it to discover Mellanox pci Nic's and it only discovered on board

Re: [openstack-dev] [policy] AWS IAM session

+1 -- Kristi Nikolla Software Engineer @ massopen.cloud kri...@nikolla.me On Wed, Oct 4, 2017, at 10:08 AM, Zane Bitter wrote: > On 03/10/17 16:08, Lance Bragstad wrote: > > Hey all, > > > > It was mentioned in today's keystone meeting [0] that it would be useful > > to go through AWS

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

Matt Riedemann October 4, 2017 at 10:51 AM What's the difference between this tag and the zero-impact-upgrades tag? I guess the accessible one is, can a user still ssh into their VM while the nova compute service is being upgraded. The zero-impact-upgrade one

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

On 10/3/2017 1:52 PM, Sean McGinnis wrote: I'm hoping this will get a little more attention. We recently started discussing removing governance tags that did not have any projects asserting them. I think this makes a lot of sense. Some tags were defined apparently in the hope that it would get

Re: [openstack-dev] It's time...

On 2017-10-04 11:17 AM, Jeremy Stanley wrote: On 2017-10-04 22:21:32 +0800 (+0800), Tom Fifield wrote: [...] the timing is right for me to step down as your Community Manager. [...] Your tireless assistance will be missed. I'm lucky to have been able to count you as a colleague all these

Re: [openstack-dev] It's time...

The community will miss you and so will I :( You're a good soul, Tom! Enjoy those beachside beverages!! Jeremy Stanley October 4, 2017 at 10:17 AM On 2017-10-04 22:21:32 +0800 (+0800), Tom Fifield wrote: [...] [...] Your tireless assistance will be missed. I'm

[openstack-dev] [docs] Evidence of Success

I've made a bit of progress on the collaborative vision for the Docs team: https://docs.google.com/document/d/1Xy78CnmnKlQ7SbR1XewqgrUdGe7DqnKAGYw_9aj5Ndg/edit# This still needs plenty of work, but I wanted to put out what we have so we can start to get some feedback from other members of the

Re: [openstack-dev] Security of Meta-Data

Hi Folks, I'm still processing all this information - thanks for your help! --Pino On Wed, Oct 4, 2017 at 7:58 AM, Jeremy Stanley wrote: > On 2017-10-04 10:47:02 +0100 (+0100), Luke Hinds wrote: > [...] > > The recommendation is not to use metadata for security sensitive >

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Wed, Oct 4, 2017 at 7:00 AM, Dan Prince wrote: > On Tue, 2017-10-03 at 16:03 -0600, Alex Schultz wrote: >> On Tue, Oct 3, 2017 at 2:46 PM, Dan Prince >> wrote: >> > >> > >> > On Tue, Oct 3, 2017 at 3:50 PM, Alex Schultz >> > wrote:

Re: [openstack-dev] It's time...

On 2017-10-04 22:21:32 +0800 (+0800), Tom Fifield wrote: [...] > the timing is right for me to step down as your Community Manager. [...] Your tireless assistance will be missed. I'm lucky to have been able to count you as a colleague all these years, and by all means don't hesitate to reach out

Re: [openstack-dev] [tc][election] non-candidacy for TC

On 2017-10-03 23:05:42 -0400 (-0400), Steve Martinelli wrote: > Folks, due to changes in my day job I will not be running in the > next TC election. [...] Your service to the community is appreciated, and I will still endeavor to seek your awesome advice from time to time. Thanks for everything!

Re: [openstack-dev] [tc][election] non-candidacy for TC

Steve, thanks for all you've done on the TC, and for OpenStack. Looking forward to continuing to work with you, -amrith On Tue, Oct 3, 2017 at 11:05 PM, Steve Martinelli wrote: > Folks, due to changes in my day job I will not be running in the next TC > election. I

Re: [openstack-dev] [docs][ptls][install] Install guide vs. tutorial

On 9/29/2017 3:27 PM, Doug Hellmann wrote: Excerpts from Petr Kovar's message of 2017-09-29 21:09:02 +0200: On Tue, 26 Sep 2017 18:53:04 -0500 Jay S Bryant wrote: On 9/25/2017 3:47 AM, Alexandra Settle wrote: > I completely agree consistency is more

[openstack-dev] [python-openstackclient][python-openstacksdk][neutron] Bridging neutronclient gaps

While I realize my timing may be a little bad here with all the other things we have going on, I wanted to follow up on our plans for the SDK and OSC as time is already flying by for Queens. As we discussed before [1], there are some gaps in the OSC/SDK model that keep us from getting parity with

[openstack-dev] [OSSN-0082] Heap and Stack based buffer overflows in dnsmasq prior to version 2.78

Heap and Stack based buffer overflows in dnsmasq prior to version 2.78 -- ### Summary ### A series of heap and stack based buffer overflows have been discovered in versions of dnsmasq prior to release 2.78. ### Affected Services

Re: [openstack-dev] [tc][election] non-candidacy for TC

Steve, Just wanted to say thanks for everything and glad you'll still be about! Amy (spotz) On Tue, Oct 3, 2017 at 10:05 PM, Steve Martinelli wrote: > Folks, due to changes in my day job I will not be running in the next TC > election. I still intend to contribute to

Re: [openstack-dev] It's time...

Tom, You will be missed! It's been a pleasure working with you even on opposing tracks this last track chair round! Thanks for everything you've done for the community! Amy (spotz) On Wed, Oct 4, 2017 at 9:21 AM, Tom Fifield wrote: > Hi all, > > Tom here, on a personal

[openstack-dev] It's time...

Hi all, Tom here, on a personal note. It's quite fitting that this November our summit is in Australia :) I'm hoping to see you there because after being part of 15 releases, and travelling the equivalent of a couple of round trips to the moon to witness OpenStack grow around the world, the

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

On Wed, Oct 04, 2017 at 02:07:53PM +0100, Jean-Philippe Evrard wrote: > > - I don't see any mention of documentation in the required steps to > get this governance tag. > I think it can serve the community better if we enforce the > inclusion of the documentation on > 'HOW to trigger this

Re: [openstack-dev] [policy] AWS IAM session

On 03/10/17 16:08, Lance Bragstad wrote: Hey all, It was mentioned in today's keystone meeting [0] that it would be useful to go through AWS IAM (or even GKE) as a group. With all the recent policy discussions and work, it seems useful to get our eyes on another system. The idea would be to

Re: [openstack-dev] [storyboard] Should New Projects Be Using Storyboard?

On 2017-10-04 13:51:37 +0100 (+0100), Stephen Finucane wrote: [...] > Not to hijack the thread but, we're moving projects to storyboard? > The only thing I can find about this is that the Watcher project > considering switching [1]. Is there a spec or something I can look > at about this? There

Re: [openstack-dev] [tripleo][quickstart][rdo] shipping python-virtualbmc in Newton to allow undercloud upgrades from Newton to Queens

On 04-10-17 12:17:30, Dmitry Tantsur wrote: > Hi! > > The only issue I can think of is python-pyghmi version. I think one in > Newton is too old and has to be bumped to at least one in Ocata. But if you > say you've deployed successfully, probably it was already bumped for some > reason. Yeah we

Re: [openstack-dev] [Infra][Nova] Requesting +1/-1 reporting permission for s390x libvirt/kvm (zkvm) Nova CI

On 2017-10-04 11:05:46 +0200 (+0200), Andreas Scheuring wrote: [...] > We already got this permission granted in the Nova Meeting on > February, 2nd 2017 [4], but after our CI went down on May 16 for a > couple of weeks, we somehow (technically) lost the permission. As > we already got the

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

(top-posting, as it is not a direct response to a specific line) This is your friendly reminder that we're not quite near containerized ironic-inspector. The THT for it has probably never been tested at all, and the iptables magic we do may simply not be containers-compatible. Milan would

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

On Tue, Oct 3, 2017 at 7:52 PM, Sean McGinnis wrote: > I'm hoping this will get a little more attention. > > We recently started discussing removing governance tags that did not have any > projects asserting them. I think this makes a lot of sense. Some tags were > defined

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, 2017-10-03 at 16:03 -0600, Alex Schultz wrote: > On Tue, Oct 3, 2017 at 2:46 PM, Dan Prince > wrote: > > > > > > On Tue, Oct 3, 2017 at 3:50 PM, Alex Schultz > > wrote: > > > > > > On Tue, Oct 3, 2017 at 11:12 AM, Dan Prince

Re: [openstack-dev] Security of Meta-Data

On 2017-10-04 10:47:02 +0100 (+0100), Luke Hinds wrote: [...] > The recommendation is not to use metadata for security sensitive > data (its possible to spoof by setting a X-Forwarded header), > please see the following OpenStack Security Note on the topic: > >

Re: [openstack-dev] [storyboard] Should New Projects Be Using Storyboard?

On Tue, 2017-10-03 at 12:57 -0700, Mike Perez wrote: > I noticed that the project creator [1] and cookiecutter [2] promote using > launchpad. If we're migrating projects to storyboard today, should we stop > promoting launchpad for new projects? Not to hijack the thread but, we're moving projects

Re: [openstack-dev] Update on Zuul v3 Migration - and what to do about issues

On Wed, Oct 04, 2017 at 02:39:17PM +0900, Rikimaru Honjo wrote: > Hello, > > I'm trying to run jobs with Zuul v3 in my local environment.[1] > I prepared a sample job that runs sleep command on zuul's host. > This job doesn't use Nodepool. [2] > > As a result, Zuul v3 submitted "SUCCESS" to

Re: [openstack-dev] [all] Important information for people with in-repo Zuul v3 config

On Wed, Oct 4, 2017 at 1:00 PM Jon Schlueter wrote: > On Wed, Oct 4, 2017 at 7:35 AM, Sean Dague wrote: > > On 10/04/2017 07:23 AM, Boden Russell wrote: > >> > >> On 10/3/17 1:37 PM, Monty Taylor wrote: > >>> The partial rollback of Zuulv3 is in place now.

Re: [openstack-dev] [tripleo][quickstart][rdo] shipping python-virtualbmc in Newton to allow undercloud upgrades from Newton to Queens

Hi! The only issue I can think of is python-pyghmi version. I think one in Newton is too old and has to be bumped to at least one in Ocata. But if you say you've deployed successfully, probably it was already bumped for some reason. On 10/04/2017 02:08 PM, Lee Yarwood wrote: Hello all, I'm

[openstack-dev] [tripleo][quickstart][rdo] shipping python-virtualbmc in Newton to allow undercloud upgrades from Newton to Queens

Hello all, I'm currently working to get the tripleo-spec for fast-forward upgrades out of WIP and merged ahead of the Queens M-1 milestone next week. One of the documented pre-requisite steps for fast-forward upgrades is for an operator to linearly upgrade the undercloud from Newton (N) to Queens

Re: [openstack-dev] May I run iscsiadm --op show & update 100 times?

On 03/10, Rikimaru Honjo wrote: > Hello Gorka, > > On 2017/10/02 20:37, Gorka Eguileor wrote: > > On 02/10, Rikimaru Honjo wrote: > > > Hello, > > > > > > I'd like to discuss about the following bug of os-brick. > > > > > > * os-brick's iscsi initiator unexpectedly reverts node.startup from > > >

[openstack-dev] [Openstack-operators][all][heat] Removal of CloudWatch api

Add OpenStack ops ML -- Forwarded message -- From: Rabi Mishra Date: 2017-10-04 18:47 GMT+08:00 Subject: [openstack-dev] [heat] Removal of CloudWatch api To: "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org>

Re: [openstack-dev] [all] Important information for people with in-repo Zuul v3 config

On Wed, Oct 4, 2017 at 7:35 AM, Sean Dague wrote: > On 10/04/2017 07:23 AM, Boden Russell wrote: >> >> On 10/3/17 1:37 PM, Monty Taylor wrote: >>> The partial rollback of Zuulv3 is in place now. Zuulv2 is acting as your >>> gate keeper once again. >> >> Since the rollback, one of

Re: [openstack-dev] [heat] Removal of CloudWatch api

Rabi, I’d suggest to review the proposal with the openstack-operators list who would be able to advise on potential impact for their end users. Tim From: Rabi Mishra Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [all] Important information for people with in-repo Zuul v3 config

On Wed, Oct 4, 2017 at 12:23 PM Boden Russell wrote: > > On 10/3/17 1:37 PM, Monty Taylor wrote: > > The partial rollback of Zuulv3 is in place now. Zuulv2 is acting as your > > gate keeper once again. > > Since the rollback, one of the neutron-lib (v2) jobs has been >

Re: [openstack-dev] [Monasca] [wiki] Where is GUI tutorial of Monasca

Hi Takeyuki, I'm afraid we don't have documentation for the GUI. The concepts of alarm definitions, alarms and notifications are explained here [1]. You may also want to have a look at practical examples of working with the API using the Python client [2, 3]. I know that our documentation is

Re: [openstack-dev] [all] Important information for people with in-repo Zuul v3 config

And we find following error in heat's zuulv2 jobs [1]: x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE

Re: [openstack-dev] [all] Important information for people with in-repo Zuul v3 config

On 10/04/2017 07:23 AM, Boden Russell wrote: > > On 10/3/17 1:37 PM, Monty Taylor wrote: >> The partial rollback of Zuulv3 is in place now. Zuulv2 is acting as your >> gate keeper once again. > > Since the rollback, one of the neutron-lib (v2) jobs has been > consistently failing [1] with: > >

Re: [openstack-dev] [all] Important information for people with in-repo Zuul v3 config

On 10/3/17 1:37 PM, Monty Taylor wrote: > The partial rollback of Zuulv3 is in place now. Zuulv2 is acting as your > gate keeper once again. Since the rollback, one of the neutron-lib (v2) jobs has been consistently failing [1] with: c/_cffi_backend.c:15:17: fatal error: ffi.h: No such file or

Re: [openstack-dev] [Monasca] Query for the official document of Monasca manual installation on openstack

Hi Manik, I would recommend you installing Monasca components using Docker Compose [1] and manually installing the agents [2] on your controller and compute nodes. You will also have to add/configure Monasca users in Keystone with roles as configured by default_authorized_roles and

[openstack-dev] [heat] Removal of CloudWatch api

Hi All, As discussed in the last meeting, here is the ML thead to gather more feedback on this. Background: Heat support for AWS CloudWatch compatible API (a very minimalistic implementation, primarily used for metric data collection for autoscaling, before the telemetry services in OpenStack),

Re: [openstack-dev] Security of Meta-Data

There is an assumption that you've got solid network security on the path between your guests and your nova-API. Either because you've got a secure network path, or you run the neutron proxy server on the host itself, and so this is a no hop call. Because this is a bootstrapping problem, and the

Re: [openstack-dev] Security of Meta-Data

On Tue, Oct 3, 2017 at 11:00 PM, Giuseppe de Candia < giuseppe.decan...@gmail.com> wrote: > Hi Folks, > > > Are there any documented conventions regarding the security model for > MetaData? > > > Note that CloudInit allows passing user and ssh service public/private > keys via MetaData service

[openstack-dev] [kuryr] VTG sessions today postponed

Hi fellow kuryrs, Due to illness of one of the key contributors in todays sessions, we'll postpone the sessions today. As soon as he recovers we'll publish the new time. Regards, Toni __ OpenStack Development Mailing List

[openstack-dev] [Infra][Nova] Requesting +1/-1 reporting permission for s390x libvirt/kvm (zkvm) Nova CI

Hello, I'm requesting +1/-1 reporting permission (non-voting) to Nova for the s390x libvirt/kvm (zKVM) nova ci [1] (check pipeline only). We already got this permission granted in the Nova Meeting on February, 2nd 2017 [4], but after our CI went down on May 16 for a couple of weeks, we

Re: [openstack-dev] [all] Important information for people with in-repo Zuul v3 config

On Tue, Oct 3, 2017 at 8:37 PM Monty Taylor wrote: > Hi everybody, > > The partial rollback of Zuulv3 is in place now. Zuulv2 is acting as your > gate keeper once again. The status page for Zuulv2 can be found at > http://status.openstack.org/zuul and Zuulv3 can be found at

[openstack-dev] [charms] bug day this Thursday

Hi All Reminder that as this Thursday is the first Thursday of the month its officially a bug triage/fix day! Our new (23) queue is looking better than ever [0] so it would be great to get that down to near 0. After that focus should switch to High (62) and then Medium (174) bugs already

[openstack-dev] [Monasca] [wiki] Where is GUI tutorial of Monasca

Hi I'm very grateful that if you consider my request. Would you tell me where the tutorial of Monasca is, especially after installation? If it does not exist, it is helpful for us to add the tutorial on wiki page. https://wiki.openstack.org/wiki/Monasca Especially, I would like to know the

Re: [openstack-dev] Security of Meta-Data

Referring to the original question 'Note that CloudInit allows passing user and ssh service public/private keys via MetaData service (or ConfigDrive). One assumes it must be secure, but I have not found a security model or documentation.' The metadata service is as secure as underlaying

[openstack-dev] Odp.: Odp.: [neutron][lbaasv2][agent implementation] L7 policy support

Hello, It seems that HaproxyOnHostPluginDriver from https://github.com/openstack/neutron-lbaas/blob/mitaka-eol/neutron_lbaas/drivers/haproxy/plugin_driver.py#L21 extends AgentDriverBase

Re: [openstack-dev] Security of Meta-Data

Hi, You can configure the metadata service to be secure. You just need to make sure that nova is configured correctly. FYI - https://github.com/openstack/neutron/blob/master/neutron/conf/agent/metadata/config.py#L68 Thanks Gary On 10/4/17, 7:01 AM, "Joshua Harlow" wrote: