Re: [openstack-dev] [neutron][horizon][fwaas][vpnaas] fwaas/vpnaas dashboard split out

Hi, I would like to announce a new repository for tap-as-a-service was created. Could you please take a look. http://git.openstack.org/cgit/openstack/tap-as-a-service-dashboard/ Regards, Kaz From: Akihiro Motoki Subject: [openstack-dev] [neutron][horizon][fwaas][vpnaas]

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Agree. Regards -steve On Thu, Jun 29, 2017 at 7:55 AM, Monty Taylor wrote: > On 06/28/2017 11:27 PM, Steven Dake wrote: > > >> >> On Wed, Jun 28, 2017 at 2:50 PM, Monty Taylor > > wrote: >> >> On 06/28/2017 09:50 AM,

[openstack-dev] [glance] priorities for the coming week (06/30-07/06)

(Light list this week because of a long holiday weekend in the USA.) As discussed at today's Glance meeting, the review priorities for this week are: 1 image download error https://review.openstack.org/#/c/460280 2 weirdness on the 'protected' property filter patch Strange test failure error

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Jun. 30 2017

1.ODL L2/L3 Integration 2.Scenario in JJB 3.Documentation task 4.AoB B. R., Zhijiang__ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Fri, Jun 30, 2017 at 12:18 AM, Jeremy Stanley wrote: > On 2017-06-29 18:58:09 +1000 (+1000), Joshua Hesketh wrote: > > So I apologise if this has already been suggested/discussed (the > > long threads are difficult to keep up with), but has it been > > considered to go back

Re: [openstack-dev] [tripleo] Plan description in the create/update plan form

On 06/29/2017 07:25 AM, Ana Krivokapic wrote: Resending with the [tripleo] tag, sorry... On Thu, Jun 29, 2017 at 2:22 PM, Ana Krivokapic > wrote: Hi TripleO devs, I am working on adding a description field to the "Crate Plan" form

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 2017-06-29 19:25:09 + (+), Tim Bell wrote: [...] > Can an ‘official’ project be deprecated? The economics say yes. > The consumer confidence impact would be substantial. [...] Does https://review.openstack.org/475721 count? What about https://review.openstack.org/452086 or, going back

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 29/06/17 10:18, Jeremy Stanley wrote: Gerrit's design assumes project names (including any prefixed namespace) never change. This means project renames in Gerrit are painful and disruptive (service outage for everyone, Git remote changes for anyone working on that repo, risk of breaking

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Part of the confusion is around what is allowed to use the term openstack and the various ways its used. we have software such as github.com/openstack/openstack-helm, which is in the openstack namespace, has openstack in its title, but not under tc governance.

Re: [openstack-dev] [User-committee] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

On Thu, Jun 29, 2017 at 3:12 PM, Mike Perez wrote: > On June 29, 2017 at 13:01:09, Amy Marrich (a...@demarco.com) wrote: > > First off it looks really sleek and I love the look! A few thoughts > though > > and I do realize it's just a mock up: > > > > 1) We have Sponsor just

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

+ OpenStack dev list On June 29, 2017 at 13:01:09, Amy Marrich (a...@demarco.com) wrote: > First off it looks really sleek and I love the look! A few thoughts though > and I do realize it's just a mock up: > > 1) We have Sponsor just to pick one but don't have Operators/Administrators > and their

Re: [openstack-dev] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

+ OpenStack dev list Hello all, Wes has just took my ugly mock up of the contributor portal idea and came up with this [1]. Here’s what he said: "The idea is to help get potential contributors to the right place, using the outline Mike put together. Rather than sending people to a different

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

> On 29 Jun 2017, at 17:35, Chris Friesen wrote: > > On 06/29/2017 09:23 AM, Monty Taylor wrote: > >> We are already WELL past where we can solve the problem you are describing. >> Pandora's box has been opened - we have defined ourselves as an Open >> community.

Re: [openstack-dev] realtime kvm cpu affinities

On 06/29/2017 10:59 AM, sfinu...@redhat.com wrote: Thus far, we've no clear conclusions on directions to go, so I've took a stab below. Henning, Sahid, Chris: does the above/below make sense, and is there anything we need to further clarify? The above is close enough. :) # Problem 1 From

Re: [openstack-dev] [glance] stepping down from glance core and other related groups

Hi Nikhil, I am very thankful for support and guidance you have provided to me and other new members. Hoping to work with you again in near future. All the best for your future activities. Cheers, Abhishek Sent from OWA on Android From: Nikhil Komawar

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 2017-06-29 08:49:19 -0500 (-0500), Jimmy McArthur wrote: [...] > If there is specifically confusion around Google searches, I'd > suggest as a first step to spend some time working on redirects > for dead projects and very clearly updating documentation. For all > of Google's magic, there are

Re: [openstack-dev] realtime kvm cpu affinities

On Tue, 2017-06-20 at 09:48 +0200, Henning Schild wrote: > Hi, > > We are using OpenStack for managing realtime guests. We modified > it and contributed to discussions on how to model the realtime > feature. More recent versions of OpenStack have support for realtime, > and there are a few

[openstack-dev] [keystone] stable/newton is broken

Keystone's stable/newton gate is broken [0] [1]. The TL;DR is that our keystone_tempest_plugin is validating federated mappings before updating the protocol [2]. The lack of validation was a bug [3] that was fixed in Ocata, but the fix [4] was never backported. Since stable/newton is in Phase II,

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Today's meeting was slightly longer than last week's, with a few more in attendance as well. There were no new major issues brought up and the main topics were last week's frozen change[4] and a few minor fixes[5][6] in the queue now. These fixes were considered

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 2017-06-29 17:33, Monty Taylor wrote: > On 06/29/2017 10:00 AM, Jimmy McArthur wrote: >> >> >>> Thierry Carrez >>> June 29, 2017 at 9:54 AM >>> >>> Unfortunately, those pages just exist -- those hundreds of projects >>> projects might be inactive, they still have

Re: [openstack-dev] [ceilometer][panko] Ocata ceilometer event storage configuration

Yes， and you need make sure ceilometer-agent-notification and panko was intalled in a same machine in your environment. Because ceilometer will load the publisher dispatcher panko from the module panko and use the database url[1] which configured in panko.conf to init the database connection. [1]

Re: [openstack-dev] How to test private patches on overcloud ?

On Thu, Jun 29, 2017 at 4:21 PM, Dnyaneshwar Pawar wrote: > Hi, > > while testing my patches i am getting errors with command 'openstack deploy > --templates' any idea what is wrong here? > > http://paste.openstack.org/show/614074/ This shows rabbit is failing to

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Excerpts from Chris Friesen's message of 2017-06-29 09:35:01 -0600: > On 06/29/2017 09:23 AM, Monty Taylor wrote: > > > We are already WELL past where we can solve the problem you are describing. > > Pandora's box has been opened - we have defined ourselves as an Open > > community. > > Our only

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/29/2017 09:23 AM, Monty Taylor wrote: We are already WELL past where we can solve the problem you are describing. Pandora's box has been opened - we have defined ourselves as an Open community. Our only requirement to be official is that you behave as one of us. There is nothing stopping

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/29/2017 10:00 AM, Jimmy McArthur wrote: Thierry Carrez June 29, 2017 at 9:54 AM Unfortunately, those pages just exist -- those hundreds of projects projects might be inactive, they still have git repositories and wiki pages. We could more actively clean

Re: [openstack-dev] [Openstack-operators] [doc[ptls] Doc meeting

Hi everyone, If you have any questions/concerns/comments/feelings you have about the doc migration, bring ‘em to #openstack-meeting at 1600UTC today :) I’ll be there to chat instead of our regularly scheduled meeting :) Cheers, Alex From: Alexandra Settle Date:

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/29/2017 03:00 AM, Thierry Carrez wrote: Monty Taylor wrote: On 06/28/2017 09:50 AM, Thierry Carrez wrote: [...] Removing the root cause would be a more radical move: stop offering hosting to non-OpenStack projects on OpenStack infrastructure altogether. We originally did that for a

[openstack-dev] [tripleo] I18n-themed Deep Dive - July 6th

Hi folks, As I mentioned during the weekly meeting on Tuesday, I'd like to do a short i18n-themed deep dive during next week's slot (Thu July 6th, 14:00 UTC). I'll use my BlueJeans at [1] and updated the deep dives etherpad [2] with that information. There should be two broad topics: - Life and

[openstack-dev] How to test private patches on overcloud ?

Hi, while testing my patches i am getting errors with command 'openstack deploy --templates' any idea what is wrong here? http://paste.openstack.org/show/614074/ Thanks, Dnyaneshwar __ OpenStack Development Mailing List (not

Re: [openstack-dev] [glance] stepping down from glance core and other related groups

On Thu, Jun 29, 2017 at 12:09 AM, Nikhil Komawar wrote: > I am thankful to the community for such amazing experience over the past few > years. And the Glance community is thankful for your service, which includes three cycles as the Glance PTL! > For the changes required

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Monty Taylor wrote: > I also continue to challenge the assertion. There are dead projects in > there for sure- but there are a LOT of non-dead live projects. It's not > like we have 6 live and 6 dead projects. The overwhelming majority of > the projects are not dead. Early results on my analysis

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Thierry Carrez June 29, 2017 at 9:54 AM Unfortunately, those pages just exist -- those hundreds of projects projects might be inactive, they still have git repositories and wiki pages. We could more actively clean them up (and then yes, adjusting the

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/28/2017 11:27 PM, Steven Dake wrote: On Wed, Jun 28, 2017 at 2:50 PM, Monty Taylor > wrote: On 06/28/2017 09:50 AM, Thierry Carrez wrote: Hi everyone, Two weeks ago, as a result of a discussion at the Board+TC+UC

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Jimmy McArthur wrote: > Thierry Carrez wrote: >> The confusion I'm talking about is not the passive-aggressive from >> people involved in openstack. It's from our prospective new users, who >> have no idea about our governance, making random searches on Google. >> It's from people getting hit by

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Manoj, It would be great if these teams were brought into this conversation. I am not averse to the evolutionary approach, merely observing that in the absence of commitment and contributors who wish to participate in this evolution, we will be unable to sustain the project. Regarding your view

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Anne Gentle June 29, 2017 at 9:17 AM On Thu, Jun 29, 2017 at 8:49 AM, Jimmy McArthur wrote: Thierry Carrez wrote: The confusion I'm talking about is not the passive-aggressive from people involved in openstack. It's from our

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/29/2017 02:35 AM, Thierry Carrez wrote: Sean McGinnis wrote: The central issue being discussed here is an issue of external perception. It's hard for newcomers to the OpenStack world to see what is a part of OpenStack and what's not. If you google "openstack machine learning", the first

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 2017-06-29 18:58:09 +1000 (+1000), Joshua Hesketh wrote: > So I apologise if this has already been suggested/discussed (the > long threads are difficult to keep up with), but has it been > considered to go back to using a stackforge namespace? [...] Back in the bad ol' days when we had a

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Thu, Jun 29, 2017 at 8:49 AM, Jimmy McArthur wrote: > > > Thierry Carrez wrote: >> >> The confusion I'm talking about is not the passive-aggressive from >> people involved in openstack. It's from our prospective new users, who >> have no idea about our governance, making

Re: [openstack-dev] [telemetry][ceilometer]Cannot get vmware virtual machine's disk usage rate via vsphere inspector

HI,gord Thanks for your infomation. But I think vmware driver already support my requirement because It's docs indicate it's already support the counter. Maybe just the vsphere inspector in ceilometer haven't implement the interface or we need add some other configuration in ceilometer. So, is

Re: [openstack-dev] [nova] Need volunteer(s) to help migrate project docs

On Mon, 2017-06-26 at 10:07 +0100, sfinu...@redhat.com wrote: > On Sat, 2017-06-24 at 14:22 +0800, Zhenyu Zheng wrote: > > On Sat, Jun 24, 2017 at 12:23 AM, Matt Riedemann > > wrote: > > > The spec [1] with the plan to migrate project-specific docs from > > >

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Thierry Carrez wrote: The confusion I'm talking about is not the passive-aggressive from people involved in openstack. It's from our prospective new users, who have no idea about our governance, making random searches on Google. It's from people getting hit by marketing message from projects

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Amrith: Some comments regarding the scarcity of deployments, and the proposed approach. We know of multiple teams that are now independently charging down and investing in a Trove path. They are at various stages of deployment and are beyond tire-kicking. They are beginning to build dev/test

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On Wed, 2017-06-21 at 07:01 -0400, Sean Dague wrote: > On 06/21/2017 04:43 AM, sfinu...@redhat.com wrote: > > On Tue, 2017-06-20 at 16:48 -0600, Chris Friesen wrote: > > > On 06/20/2017 09:51 AM, Eric Fried wrote: > > > > Nice Stephen! > > > > > > > > For those who aren't aware, the rendered

Re: [openstack-dev] [telemetry][ceilometer]Cannot get vmware virtual machine's disk usage rate via vsphere inspector

i'll be honest, i don't think any of the active developers on Ceilometer uses or knows anything about vmware driver. you will probably want to reach out to vmware themselves so they can provide support or fix the driver (or ideally move the vmware driver to their own repo). On 28/06/17 10:34

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 2017-06-29 11:28:10 +1000 (+1000), Tony Breeds wrote: [...] > In the meantime we could look at adding permissions such that the Stable > PTL (Well actually I guess eventually it'd be the same bot that does the > release tagging) can push tags and abandon changes on all projects. > > Right now

Re: [openstack-dev] [ceilometer][panko] Ocata ceilometer event storage configuration

On 29/06/17 07:24 AM, Yaguang Tang wrote: > sinks: > - name: event_sink > transformers: > triggers: > publishers: > - direct:// > - panko:// the publisher path is only available if you have Pike Panko. you need to either backport[1] or configure your

Re: [openstack-dev] [tc][all] Move away from meeting channels

On 28/06/17 14:02 +, Jeremy Stanley wrote: Anyway, I don't think we need to propose "moving away from meeting channels" but rather "allowing teams to not use meeting channels if it's inconvenient for them." I expect many (most even?) teams who continue to hold regularly scheduled meetings

Re: [openstack-dev] [masakari][nova] Allow evacuation of instances in resized state

Hi Chris, IMO we cannot perform auto-confirm as confirming or reverting is user's choice, whereas reverting is not possible as the node where the instance is resized is down. As suggested by you allowing this in nova require additional work. It is possible if we take power-state into

Re: [openstack-dev] [tripleo] Plan description in the create/update plan form

Resending with the [tripleo] tag, sorry... On Thu, Jun 29, 2017 at 2:22 PM, Ana Krivokapic wrote: > Hi TripleO devs, > > I am working on adding a description field to the "Crate Plan" form in the > TripleO UI [1]. The goal is to make it possible for the user to specify a >

[openstack-dev] Plan description in the create/update plan form

Hi TripleO devs, I am working on adding a description field to the "Crate Plan" form in the TripleO UI [1]. The goal is to make it possible for the user to specify a plan description using a form field when creating a plan. As the plan description lives in the plan-environment.yaml file[2], the

[openstack-dev] [ceilometer][panko] Ocata ceilometer event storage configuration

Hi all, I am using Ocata Ceilometer Gnocchi with Panko, Panko is configured to use MySQL as backend to store events, I configured Ceilometer event_pipeline.yaml as follow: sinks: - name: event_sink transformers: triggers: publishers: - direct:// -

Re: [openstack-dev] realtime kvm cpu affinities

Am Wed, 28 Jun 2017 11:34:42 +0200 schrieb Sahid Orentino Ferdjaoui : > On Tue, Jun 27, 2017 at 04:00:35PM +0200, Henning Schild wrote: > > Am Tue, 27 Jun 2017 09:44:22 +0200 > > schrieb Sahid Orentino Ferdjaoui : > > > > > On Mon, Jun 26, 2017 at

Re: [openstack-dev] [tc][swg] The future of the Stewardship Working Group

Colette, First of all, thank you for all that you have done in leading the charge around the SWG (since long before it got that name). I had the good fortune of being able to work with the first group of members of the TC who attended the training in Michigan at Zing Train and I think the

Re: [openstack-dev] diskimage builder works for trusty but not for xenial

Hello All, unfortunately os-refresh-config does not work because new diskimage-builder does not install dib-utils and jq in the centos7 image. Regards Ignazio 2017-06-28 15:28 GMT+02:00 Ignazio Cassano : > PS > PS > Unfortunately os-refresh-config is not working also

Re: [openstack-dev] [EXTERNAL] Re: [tripleo]: overcloud deploy --templates fails.

Hi Steve, I have used ‘ocata’ bits to created tripleo setup. Because don’t have pike bits yet. I am not sure only upgrading tripleo-common will be sufficient or not. Is there any wan where I can upgrade my setup to ‘master’ ? Thanks, Dnyaneshwar On 6/29/17, 1:56 PM, "Steven Hardy"

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Howdy, So I apologise if this has already been suggested/discussed (the long threads are difficult to keep up with), but has it been considered to go back to using a stackforge namespace? It seems to me that the role of stackforge to provide a proving ground or place for aligned projects/repos

Re: [openstack-dev] [heat] Deprecate/Remove deferred_auth_method=password config option

On Thu, Jun 29, 2017 at 4:13 AM, Kaz Shinohara wrote: > Hi, > >> No, I think we still need this, because it is disabled by default - >> this option allows you to enable defeating token expiry via trusts, > My understanding for the current implementation is.. >

Re: [openstack-dev] [tripleo]: overcloud deploy --templates fails.

On Thu, Jun 29, 2017 at 7:07 AM, Dnyaneshwar Pawar wrote: > Hi, > > > > I am getting following error. Do I need to specify anything else in the > command? > > This command was working fine before commit > 3e6147dee4497bbb607e6377bd588e32f62be2b7 . There is a

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

James E. Blair wrote: > Thierry Carrez writes: > >> Removing the root cause would be a more radical move: stop offering >> hosting to non-OpenStack projects on OpenStack infrastructure >> altogether. We originally did that for a reason, though. The benefits of >> offering

Re: [openstack-dev] [tripleo][kolla][puppet] DLRN maintenance on June 29, 8:00 AM UTC

The DLRN server maintenance has been completed. If you had any issue in a CI job, you can recheck now. Please contact me if you find any trouble accessing the RDO Trunk repos. Regards, Javier - Original Message - > This is also of interest for CI jobs in TripleO, kolla and >

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Monty Taylor wrote: > On 06/28/2017 09:50 AM, Thierry Carrez wrote: >> [...] Removing the root cause would be a more radical move: stop offering >> hosting to non-OpenStack projects on OpenStack infrastructure >> altogether. We originally did that for a reason, though. The benefits of >> offering

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Sean McGinnis wrote: >> >> The central issue being discussed here is an issue of external >> perception. It's hard for newcomers to the OpenStack world to see what >> is a part of OpenStack and what's not. If you google "openstack machine >> learning", the first hits are Cognitive and Meteos, and

Re: [openstack-dev] [nova] bug triage experimentation

On 28.06.2017 16:50, Sean Dague wrote: > On 06/28/2017 10:33 AM, Ben Nemec wrote: >> >> >> On 06/23/2017 11:52 AM, Sean Dague wrote: >>> The Nova bug backlog is just over 800 open bugs, which while >>> historically not terrible, remains too large to be collectively usable >>> to figure out where

[openstack-dev] [tripleo]: overcloud deploy --templates fails.

Hi, I am getting following error. Do I need to specify anything else in the command? This command was working fine before commit 3e6147dee4497bbb607e6377bd588e32f62be2b7 . --- $ openstack overcloud deploy --templates ~/tripleo-heat-templates 2>&1 |tee log.overcloud_deploy Exception