Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

+1 On 5/31/18, 10:08 AM, "Borne Mace" wrote: Greetings all, I would like to propose the addition of Steve Noyes to the kolla-cli core reviewer team. Consider this nomination as my personal +1. Steve has a long history with the kolla-cli and should be considered its

Re: [openstack-dev] [neutron][api][graphql] Feature branch creation please (PTL/Core)

On 05/06/18 13:02, Akihiro Motoki wrote: Hi Gilles, 2018年6月5日(火) 10:46 Gilles Dubreuil >: On 04/06/18 22:20, Doug Hellmann wrote: >> On Jun 4, 2018, at 7:57 AM, Gilles Dubreuil mailto:gdubr...@redhat.com>> wrote: >> >> Hi, >> >> Can

Re: [openstack-dev] [neutron][api][graphql] Feature branch creation please (PTL/Core)

Hi Gilles, 2018年6月5日(火) 10:46 Gilles Dubreuil : > > > On 04/06/18 22:20, Doug Hellmann wrote: > >> On Jun 4, 2018, at 7:57 AM, Gilles Dubreuil > wrote: > >> > >> Hi, > >> > >> Can someone from the core team request infra to create a feature branch > for the Proof of Concept we agreed to do

Re: [openstack-dev] [tc] Organizational diversity tag

On Jun 4, 2018, at 2:10 PM, Doug Hellmann wrote: > >> Those rules were added because we wanted to avoid the appearance of one >> company implementing features that would only be beneficial to it. This >> arose from concerns in the early days when Rackspace was the dominant >> contributor:

Re: [openstack-dev] [neutron][api][graphql] Feature branch creation please (PTL/Core)

On 04/06/18 22:20, Doug Hellmann wrote: On Jun 4, 2018, at 7:57 AM, Gilles Dubreuil wrote: Hi, Can someone from the core team request infra to create a feature branch for the Proof of Concept we agreed to do during API SIG forum session [1] a Vancouver? Thanks, Gilles [1]

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

Zane Bitter wrote: > On 31/05/18 14:35, Julia Kreger wrote: > > Back to the topic of nitpicking! > > > > I virtually sat down with Doug today and we hammered out the positive > > aspects that we feel like are the things that we as a community want > > to see as part of reviews coming out of this

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

Hi Ihar, I still cannot believe that you are leaving OpenStack world. Words can hardly express how I appreciate your guidance either in OVO work or Neutron as a whole. It was valuable experience to me both technically and non-technically to get to work with you. Please do hang out in the

Re: [openstack-dev] [nova] spec review day next week Tuesday 2018-06-05

On Wed, 30 May 2018 12:22:20 -0700, Melanie Witt wrote: Howdy all, This cycle, we have our spec freeze later than usual at milestone r-2 June 7 because of the review runways system we've been trying out. We wanted to allow more time for spec approvals as blueprints were completed via runways.

[openstack-dev] [tripleo] Status of Standalone installer (aka All-In-One)

TL;DR: we made nice progress and you can checkout this demo: https://asciinema.org/a/185533 We started the discussion back in Dublin during the last PTG. The idea of Standalone (aka All-In-One, but can be mistaken with all-in-one overcloud) is to deploy a single node OpenStack where the

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

On 6/4/2018 3:31 PM, Ihar Hrachyshka wrote: Hi neutrinos and all, As some of you've already noticed, the last several months I was scaling down my involvement in Neutron and, more generally, OpenStack. I am at a point where I feel confident my disappearance won't disturb the project, and so I

Re: [openstack-dev] Forum Recap - Stein Release Goals

On 6/4/2018 4:20 PM, Doug Hellmann wrote: See my comments on the other part of the thread, but I think this is too optimistic until we add a couple of people to the review team on OSC. Others from the OSC team who have a better perspective on how much work is actually left may have a different

Re: [openstack-dev] [TC] Stein Goal Selection

On 6/4/2018 5:13 PM, Sean McGinnis wrote: Yes, exactly what I meant by the NOOP. I'm not sure what Cinder would check here. We don't have to see if placement has been set up or if cell0 has been configured. Maybe once we have the facility in place we would find some things worth checking, but at

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

On Monday, June 04, 2018 18:47, Jay Pipes wrote: >Just my two cents, but the OpenStack and Linux foundations seem to be pumping >out new "open events" at a pretty regular clip -- >OpenStack Summit, OpenDev, >Open Networking Summit, OpenStack Days, OpenInfra Days, OpenNFV summit, the >list

Re: [openstack-dev] [tc] Organizational diversity tag

On 2018-06-04 17:52:28 -0400 (-0400), Doug Hellmann wrote: [...] > I am still curious to know which teams have the policy. If it is more > widespread than I realized, maybe it's reasonable to extend it and use > it as the basis for a health check after all. [...] Not team-wide, but I have a

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

On 2018-06-04 14:28:28 -0700 (-0700), Amy Marrich wrote: > On Mon, Jun 4, 2018 at 7:29 AM, Zane Bitter wrote: > > On 04/06/18 10:19, Amy Marrich wrote: > > > [...] > > > I'll read in more detail, but do we want to add rollcall-vote? > > > > Is it used anywhere other than in the governance repo?

Re: [openstack-dev] [nova] [placement] Upgrade concerns with nested Resource Providers

There has been much discussion. We've gotten to a point of an initial proposal and are ready for more (hopefully smaller, hopefully conclusive) discussion. To that end, there will be a HANGOUT tomorrow (TUESDAY, JUNE 5TH) at 1500 UTC. Be in #openstack-placement to get the link to join. The

Re: [openstack-dev] [tc] summary of joint leadership meeting from 20 May

On 06/04/2018 05:02 PM, Doug Hellmann wrote: The most significant point of interest to the contributor community from this section of the meeting was the apparently overwhelming interest from companies employing contributors, as well as 2/3 of the contributors to recent releases who responded to

Re: [openstack-dev] [tc] Organizational diversity tag

On 04/06/18 17:52, Doug Hellmann wrote: Excerpts from Zane Bitter's message of 2018-06-04 17:41:10 -0400: On 02/06/18 13:23, Doug Hellmann wrote: Excerpts from Zane Bitter's message of 2018-06-01 15:19:46 -0400: On 01/06/18 12:18, Doug Hellmann wrote: [snip] Is that rule a sign of a

Re: [openstack-dev] [TC] Stein Goal Selection

Adding back the openstack-operators list that Matt added. On 06/04/2018 05:13 PM, Sean McGinnis wrote: On 06/04/2018 04:17 PM, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2018-06-04 15:38:48 -0500: On 6/4/2018 1:07 PM, Sean McGinnis wrote: Python 3 First ==

Re: [openstack-dev] [tc] Organizational diversity tag

On 04/06/18 17:52 -0400, Doug Hellmann wrote: Excerpts from Zane Bitter's message of 2018-06-04 17:41:10 -0400: On 02/06/18 13:23, Doug Hellmann wrote: > Excerpts from Zane Bitter's message of 2018-06-01 15:19:46 -0400: >> On 01/06/18 12:18, Doug Hellmann wrote: > > [snip] > >>> Is that rule a

Re: [openstack-dev] [TC] Stein Goal Selection

On 06/04/2018 04:17 PM, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2018-06-04 15:38:48 -0500: On 6/4/2018 1:07 PM, Sean McGinnis wrote: Python 3 First == One of the things brought up in the session was picking things that bring excitement and are obvious

Re: [openstack-dev] [tc] Organizational diversity tag

I am still curious to know which teams have the policy. If it is more widespread than I realized, maybe it's reasonable to extend it and use it as the basis for a health check after all. I think it's been an unwritten "guideline" in Cinder, but not a hard rule.

Re: [openstack-dev] [tc] Organizational diversity tag

Excerpts from Zane Bitter's message of 2018-06-04 17:41:10 -0400: > On 02/06/18 13:23, Doug Hellmann wrote: > > Excerpts from Zane Bitter's message of 2018-06-01 15:19:46 -0400: > >> On 01/06/18 12:18, Doug Hellmann wrote: > > > > [snip] > > > >>> Is that rule a sign of a healthy team dynamic,

Re: [openstack-dev] [tc] Organizational diversity tag

On 02/06/18 13:23, Doug Hellmann wrote: Excerpts from Zane Bitter's message of 2018-06-01 15:19:46 -0400: On 01/06/18 12:18, Doug Hellmann wrote: [snip] Is that rule a sign of a healthy team dynamic, that we would want to spread to the whole community? Yeah, this part I am pretty unsure

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

Zane, Not sure it is to be honest.:) Amy (spotz) On Mon, Jun 4, 2018 at 7:29 AM, Zane Bitter wrote: > On 04/06/18 10:19, Amy Marrich wrote: > >> Zane, >> >> I'll read in more detail, but do we want to add rollcall-vote? >> > > Is it used anywhere other than in the governance repo? We

Re: [openstack-dev] Forum Recap - Stein Release Goals

Excerpts from Matt Riedemann's message of 2018-06-04 15:26:28 -0500: > On 5/31/2018 3:59 PM, Sean McGinnis wrote: > > We were also able to already identify some possible goals for the T cycle: > > > > - Move all CLIs to python-openstackclient > > My understanding was this is something we could

Re: [openstack-dev] [TC] Stein Goal Selection

Excerpts from Matt Riedemann's message of 2018-06-04 15:38:48 -0500: > On 6/4/2018 1:07 PM, Sean McGinnis wrote: > > Python 3 First > > == > > > > One of the things brought up in the session was picking things that bring > > excitement and are obvious benefits to deployers and users

Re: [openstack-dev] [tripleo][puppet] Hello all, puppet modules

Hey, OVH is also using them as well as some custom ansible playbooks to manage the deployment. But as for red had, the configuration part is handled by puppet. We are also doing some upstream contribution from time to time. For us, the puppet modules are very stable and works very fine.

[openstack-dev] [tc] summary of joint leadership meeting from 20 May

On 20 May, 2018 the OpenStack foundation staff, board, technical committee, and user committee held a joint leadership meeting at the summit venue in Vancouver to discuss current events and issues related to the OpenStack community. Alan Clark, Melvin Hillsman, and I chaired the meeting together,

Re: [openstack-dev] [TC] Stein Goal Selection

+openstack-operators since we need to have more operator feedback in our community-wide goals decisions. +Melvin as my elected user committee person for the same reasons as adding operators into the discussion. On 6/4/2018 3:38 PM, Matt Riedemann wrote: On 6/4/2018 1:07 PM, Sean McGinnis

Re: [openstack-dev] [TC] Stein Goal Selection

On 6/4/2018 1:07 PM, Sean McGinnis wrote: Python 3 First == One of the things brought up in the session was picking things that bring excitement and are obvious benefits to deployers and users of OpenStack services. While this one is maybe not as immediately obvious, I think this is

[openstack-dev] [neutron][stable] Stepping down from core

Hi neutrinos and all, As some of you've already noticed, the last several months I was scaling down my involvement in Neutron and, more generally, OpenStack. I am at a point where I feel confident my disappearance won't disturb the project, and so I am ready to make it official. I am stepping

Re: [openstack-dev] Forum Recap - Stein Release Goals

On 5/31/2018 3:59 PM, Sean McGinnis wrote: We were also able to already identify some possible goals for the T cycle: - Move all CLIs to python-openstackclient My understanding was this is something we could do for Stein provided some heavy refactoring in the SDK and OSC got done first in

[openstack-dev] [ironic] Bug Day June 7th @ 1:00 PM to 2:00 PM UTC

Hey all, The first Thursday of the month is approaching which means it's time for a bug day yet again! As we discussed last time, we will shorten the call to an hour. Below is a proposed agenda, location, and time [0]. If you'd like to adjust or propose topics, please let me know. Thanks!

[openstack-dev] [Glace] Cores review open changes in glance-specs, please

Hi all, This week is the deadline week for Glance specs for Rocky! I'd like to get ack (in form of review in gerrit) for open specs [0] and I will start Workflow -+1 them as appropriate during the week. Thu meeting will be last call and anything hanging after that will be considered again for S

Re: [openstack-dev] [cinder] Removing Support for Drivers with Failing CI's ...

> > Our CI has been chugging along since June 2nd (not really related to > the timing of your e-mail, it just so happened that we fixed another > small problem there). You can see the logs at > > http://logs.ci-openstack.storpool.com/ > Thanks Peter. It looks like the reason the report run

Re: [openstack-dev] [cinder] Removing Support for Drivers with Failing CI's ...

Peter, Thank you for the update.  We are investigating why this shows up as failing in our CI tracking list. I will hold off on the associated patch. Thank you for the quick response! Jay On 6/4/2018 2:07 PM, Peter Penchev wrote: On Sat, Jun 02, 2018 at 06:13:23PM -0500, Jay S Bryant

[openstack-dev] [keystone] test storyboard environment

Hi all, The StoryBoard team was nice enough to migrate existing content for all keystone-related launchpad projects to a dev environment [0]. This gives us the opportunity to use  StoryBoard with real content. Log in and check it out. I'm curious to know what the rest of the team thinks. [0]

Re: [openstack-dev] [tc] Organizational diversity tag

Excerpts from Ed Leafe's message of 2018-06-04 13:41:36 -0500: > On Jun 4, 2018, at 7:05 AM, Jay S Bryant wrote: > > >> Do we have that problem? I honestly don't know how much pressure other > >> folks are feeling. My impression is that we've mostly become good at > >> finding the necessary

Re: [openstack-dev] [cinder] Removing Support for Drivers with Failing CI's ...

On Sat, Jun 02, 2018 at 06:13:23PM -0500, Jay S Bryant wrote: > All, > > This note is to make everyone aware that I have submitted patches for a > number of drivers that have not run 3rd party CI in 60 or more days.  The > following is a list of the drivers, how long since their CI last ran and >

Re: [openstack-dev] [requirements][daisycloud][freezer][fuel][solum][tatu][trove] pycrypto is dead and insecure, you should migrate part 2

On 18-05-13 12:22:06, Matthew Thode wrote: > This is a reminder to the projects called out that they are using old, > unmaintained and probably insecure libraries (it's been dead since > 2014). Please migrate off to use the cryptography library. We'd like > to drop pycrypto from requirements for

Re: [openstack-dev] [TC] Stein Goal Selection

Hi Sean, These goals look reasonable for me. On Mon, Jun 4, 2018 at 9:07 PM, Sean McGinnis wrote: > Hi everyone, > > This is to continue the discussion of the goal selection for the Stein > release. > I had previously sent out a recap of our discussion at the Forum here: > >

Re: [openstack-dev] [tc] Organizational diversity tag

On Jun 4, 2018, at 7:05 AM, Jay S Bryant wrote: >> Do we have that problem? I honestly don't know how much pressure other >> folks are feeling. My impression is that we've mostly become good at >> finding the necessary compromises, but my experience doesn't cover all >> of our teams. > In my

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

Sundar- We've been discussing the upgrade path on another thread [1] and are working toward a solution [2][3] that would not require downtime or special scripts (other than whatever's normally required for an upgrade). We still hope to have all of that ready for Rocky, but if

[openstack-dev] [TC] Stein Goal Selection

Hi everyone, This is to continue the discussion of the goal selection for the Stein release. I had previously sent out a recap of our discussion at the Forum here: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130999.html Now we need to actually narrow things down and pick a

Re: [openstack-dev] [tc] Technical Committee Update, 4 June

On Mon, Jun 4, 2018 at 1:16 PM, Jeremy Stanley wrote: > On 2018-06-04 11:30:17 -0400 (-0400), Doug Hellmann wrote: > [...] >> Jeremy has revived the thread about adding a secret/key store to >> our base services via the mailing list. We discussed the topic >> extensively in the most recent TC

[openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

Hi, Cyborg needs to create RCs and traits for accelerators. The original plan was to do that with nested RPs. To avoid rushing the Nova developers, I had proposed that Cyborg could start by applying the traits to the compute node RP, and accept the resulting caveats for Rocky, till we

[openstack-dev] [keystone] [tripleo] multi-region Keystone via stretched Galera cluster

Hey list - as mentioned in the May 11 Keystone meeting, I am working on one of the canonical approaches to producing a multi-region Keystone service, which is by having overcloud-specific keystone services interact with a Galera database that is running masters across multiple overclouds. The

Re: [openstack-dev] [tc] Technical Committee Update, 4 June

On 2018-06-04 11:30:17 -0400 (-0400), Doug Hellmann wrote: [...] > Jeremy has revived the thread about adding a secret/key store to > our base services via the mailing list. We discussed the topic > extensively in the most recent TC office hour, as well. I think we > are close to agreeing that

Re: [openstack-dev] [tc] how shall we track status updates?

On 06/04/2018 10:32 AM, Doug Hellmann wrote: During the retrospective at the forum we talked about having each group working on an initiative send regular status updates. I would like to start doing that this week, and would like to talk about logistics Should we send emails directly to this

Re: [openstack-dev] [nova][glance] Deprecation of nova.image.download.modules extension point

+openstack-operators to see if others have the same use case On 5/31/2018 5:14 PM, Moore, Curt wrote: We recently upgraded from Liberty to Pike and looking ahead to the code in Queens, noticed the image download deprecation notice with instructions to post here if this interface was in use. 

[openstack-dev] [tc] how shall we track status updates?

During the retrospective at the forum we talked about having each group working on an initiative send regular status updates. I would like to start doing that this week, and would like to talk about logistics Should we send emails directly to this list, or the TC list? How often should we post

[openstack-dev] [tc] Technical Committee Update, 4 June

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

On 04/06/18 10:19, Amy Marrich wrote: Zane, I'll read in more detail, but do we want to add rollcall-vote? Is it used anywhere other than in the governance repo? We certainly could add it, but it didn't seem like a top priority. - ZB Amy (spotz) On Mon, Jun 4, 2018 at 7:13 AM, Zane

[openstack-dev] [openstack-helm] OSH Storyboard Migration

OpenStack-Helm team, Heads-up: we are targeting migration of OpenStack-Helm into Storyboard for this Friday, 6/8! We've been discussing this for a while, and will sync on it in tomorrow's team meeting to ensure there are no surprises as we move. Following this move, please use Storyboard

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

Zane, I'll read in more detail, but do we want to add rollcall-vote? Amy (spotz) On Mon, Jun 4, 2018 at 7:13 AM, Zane Bitter wrote: > On 31/05/18 14:35, Julia Kreger wrote: > >> Back to the topic of nitpicking! >> >> I virtually sat down with Doug today and we hammered out the positive >>

Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project

Excerpts from Omer Anson's message of 2018-06-04 16:53:54 +0300: > Sure. No worries. The project is still active :) > > I tagged and branched out Queens. The build failed, see the other email thread for details. Doug > > Thanks, > Omer. > > On Mon, 4 Jun 2018 at 15:25, Sean McGinnis wrote:

Re: [openstack-dev] [Release-job-failures][release][dragonflow] Release of openstack/dragonflow failed

Excerpts from zuul's message of 2018-06-04 14:01:19 +: > Build failed. > > - release-openstack-python > http://logs.openstack.org/3b/3b7ca98ce56d1e71efe95eaa10d0884487411307/release/release-openstack-python/c381399/ > : FAILURE in 3m 46s > - announce-release announce-release : SKIPPED > -

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

On 31/05/18 14:35, Julia Kreger wrote: Back to the topic of nitpicking! I virtually sat down with Doug today and we hammered out the positive aspects that we feel like are the things that we as a community want to see as part of reviews coming out of this effort. The principles change[1] in

[openstack-dev] [masakari] weekly meeting time changed

Hi All, Gentle reminder about next Masakari meeting time. Form next meeting (5th June), meeting will be start at 0300UTC. Please find more details at [1]. [1] http://eavesdrop.openstack.org/#Masakari_Team_Meeting --- Regards, Sampath

Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project

Sure. No worries. The project is still active :) I tagged and branched out Queens. Thanks, Omer. On Mon, 4 Jun 2018 at 15:25, Sean McGinnis wrote: > On Sun, Jun 03, 2018 at 09:10:26AM +0300, Omer Anson wrote: > > Hi, > > > > If the issue is just the tagging, I'll tag the releases

[openstack-dev] [neutron] Bug deputy report May 28 - June 3

Last week we had a total of 14 bugs come in [1]; 2 of which are RFEs. Only 1 defect is high priority [2] and is already in progress. There are still a few bugs under discussion/investigation: - 1774257 "neutron-openvswitch-agent RuntimeError: Switch connection timeout" could use some input from

[openstack-dev] [stable][EM] Summary of forum session(s) on extended maintenance

Hi! We had a double session on extended maintenance at the Forum in Vancouver, here is a late summary of it. Feel free to add to it if you remember extra things. The first part of the session was to present the Extended Maintenance process as implemented after the discussion at the PTG in

Re: [openstack-dev] [cinder] [placement] cinder + placement forum session etherpad

On 6/1/2018 7:28 PM, Chris Dent wrote: On Wed, 9 May 2018, Chris Dent wrote: I've started an etherpad for the forum session in Vancouver devoted to discussing the possibility of tracking and allocation resources in Cinder using the Placement service. This is not a done deal. Instead the

Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project

On Sun, Jun 03, 2018 at 09:10:26AM +0300, Omer Anson wrote: > Hi, > > If the issue is just the tagging, I'll tag the releases today/tomorrow. I > figured that since Dragonflow has an independent release cycle, and we have > very little manpower, regular tagging makes less sense and would save us

Re: [openstack-dev] [neutron][api][graphql] Feature branch creation please (PTL/Core)

> On Jun 4, 2018, at 7:57 AM, Gilles Dubreuil wrote: > > Hi, > > Can someone from the core team request infra to create a feature branch for > the Proof of Concept we agreed to do during API SIG forum session [1] a > Vancouver? > > Thanks, > Gilles > > [1]

Re: [openstack-dev] [tc] Organizational diversity tag

On 6/2/2018 2:08 PM, Doug Hellmann wrote: Excerpts from Jeremy Stanley's message of 2018-06-02 18:51:47 +: On 2018-06-02 13:23:24 -0400 (-0400), Doug Hellmann wrote: [...] It feels like we would be saying that we don't trust 2 core reviewers from the same company to put the project's

[openstack-dev] [neutron][api][graphql] Feature branch creation please (PTL/Core)

Hi, Can someone from the core team request infra to create a feature branch for the Proof of Concept we agreed to do during API SIG forum session [1] a Vancouver? Thanks, Gilles [1] https://etherpad.openstack.org/p/YVR18-API-SIG-forum

[openstack-dev] [monasca] Nominating Doug Szumski as Monasca core

Hello Monasca team, I would like to nominate Doug Szumski (dougsz) for Monasca core team. He actively contributes to the project and works on adding Monasca to kolla-ansible. He has good project overview which he shares in his reviews. Best greetings Witek

Re: [openstack-dev] [tc] Organizational diversity tag

amrith.ku...@gmail.com wrote: -Original Message- From: Doug Hellmann Sent: Saturday, June 2, 2018 4:26 PM To: openstack-dev Subject: Re: [openstack-dev] [tc] Organizational diversity tag Excerpts from amrith.kumar's message of 2018-06-02 15:06:27 -0400: Every project on the

Re: [openstack-dev] [DragonFlow][TC] State of the DragonFlow project

Omer Anson wrote: If the issue is just the tagging, I'll tag the releases today/tomorrow. I figured that since Dragonflow has an independent release cycle, and we have very little manpower, regular tagging makes less sense and would save us a little time. Thanks Omer! For tagging, I suggest

[openstack-dev] [queens][ceilometer][gnocchi] no network resource, after installation openstack queens

Hello. I installed Openstack Queens version using Openstack-ansible. and I set gnocchi, ceilometer for metering. After installation, I got metric from instance, image, swift, etc. but, there is no metric by network I did by gnocchi cli, like this $ gnocchi resource-type list the network

Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

Hi, +1 from me, thanks for your works. Duong > -Original Message- > From: Borne Mace [mailto:borne.m...@oracle.com] > Sent: Friday, June 01, 2018 12:02 AM > To: openstack-dev > Subject: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli > core reviewer > > Greetings

Re: [openstack-dev] [tripleo] Containerized Undercloud by default

On Thu, May 31, 2018 at 9:13 PM, Emilien Macchi wrote: > > - all multinode scenarios - current blocked by 1774297 as well but also >> https://review.openstack.org/#/c/571566/ >> > This part is done and ready for review (CI team + others): https://review.openstack.org/#/c/571529/ Thanks! --

Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

+1 At 2018-06-01 01:02:27, "Borne Mace" wrote: >Greetings all, > >I would like to propose the addition of Steve Noyes to the kolla-cli >core reviewer team. Consider this nomination as my personal +1. > >Steve has a long history with the kolla-cli and should be considered its