[openstack-dev] [tc] Status update, July 21th

Hi! This is the weekly update on Technical Committee initiatives. You can find the full list of all open topics at: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee == Recently-approved changes == * Technical Committee 2019 vision [1][2][3][4] * Refreshed extra-ATC list for I18n

[openstack-dev] [glance] priorities for the coming week (07/21-07/27)

As discussed at today's Glance meeting, here are the priorities for the coming week. (1) The Pike release of the python-glanceclient We'd like to have the release ready to go by Wednesday. The list of patches to review is here: https://etherpad.openstack.org/p/glance-client-priority-reviews-pike

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Thu, Jul 20, 2017 at 9:52 PM, James Slagle wrote: > On Thu, Jul 20, 2017 at 9:04 PM, Paul Belanger wrote: >> On Thu, Jul 20, 2017 at 06:21:22PM -0400, James Slagle wrote: >>> Following up on the previous thread: >>>

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Thu, Jul 20, 2017 at 9:04 PM, Paul Belanger wrote: > On Thu, Jul 20, 2017 at 06:21:22PM -0400, James Slagle wrote: >> Following up on the previous thread: >> http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html >> >> I wanted to share some work I did

[openstack-dev] [release] Release countdown for week R-5, July 21 - 28

Welcome to our regular release countdown email! Development Focus - Teams should be wrapping up Pike feature work, in preparation for Feature Freeze for client libraries and services following the cycle-with-milestones release model. General Information ---

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Thu, Jul 20, 2017 at 06:21:22PM -0400, James Slagle wrote: > Following up on the previous thread: > http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html > > I wanted to share some work I did around the prototype I mentioned > there. I spent a couple days exploring this

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On 19/07/17 23:19, Monty Taylor wrote: Instance users do not solve this. Instance users can be built with this- but instance users are themselves not sufficient. Instance users are only sufficient in single-cloud ecosystems where it is possible to grant permissions on all the resources in

Re: [openstack-dev] [watcher] Stepping down as Watcher spec core

Hi Antoine, I am grateful for your support from my starting contributing to Watcher. Thanks to you I am contributing to Watcher actively now. I wish you live a happy life and a successful career. Hidekazu Nakamura > -Original Message- > From: Antoine Cabot

[openstack-dev] [keystone] [all] keystoneauth version discovery is here

Happy Thursday, We just released keystoneauth 3.0.0 [0], which contains a bunch of built-in functionality to handle version discovery so that you don't have to! Check out the documentation for all the details [1]. Big thanks to Eric and Monty for tackling this work, along with all the folks who

[openstack-dev] [TripleO] An experiment with Ansible

Following up on the previous thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html I wanted to share some work I did around the prototype I mentioned there. I spent a couple days exploring this idea. I came up with a Python script that when run against an in progress

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

Hi, I have missed the original email on this subject. We [Fault Genes WG] have been doing some machine learning analysis on Nova bugs/issues from 3 different sources (Launchpad, Stackoverflow, ask.openstack.org). We have been able to take all the issues and bring them down to 15 clusters. We

Re: [openstack-dev] [OpenStack-docs] [doc] dropping "draft" and series-specific publishing for docs.o.o

On 2017-07-20 21:11, Doug Hellmann wrote: > Docs team, > > We have two sets of changes happening in openstack-manuals that > will simplify managing the content there, and that will . > > Over the last couple of weeks we have removed several guides from > the repository. The remaining guides are

[openstack-dev] [doc] dropping "draft" and series-specific publishing for docs.o.o

Docs team, We have two sets of changes happening in openstack-manuals that will simplify managing the content there, and that will . Over the last couple of weeks we have removed several guides from the repository. The remaining guides are not version-specific, which allows us stop creating

Re: [openstack-dev] [infra][deb-packaging] Stop using track-upstream for deb projects

On 2017-06-18 11:06, Andreas Jaeger wrote: > On 2017-06-13 15:01, Paul Belanger wrote: >> Greetings, >> >> I'd like to propose we stop using track-upstream for project-config on >> deb-packaging projects. It seems there is no active development on these >> projects currently and by using

Re: [openstack-dev] [hacking] Propose removal of cores

On Tue, Jun 27, 2017 at 3:01 PM John Villalovos wrote: > I am proposing that the following people be removed as core reviewers from > the hacking project: > https://review.openstack.org/#/admin/groups/153,members > > Joe Gordon > James Carey > > +1 > > Joe Gordon: >

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

On 19/07/17 20:24, Jeremy Stanley wrote: > For those who are unaware, Freenode doesn't allow any one user to > /join more than 120 channels concurrently. This has become a > challenge for some of the community's IRC bots in the past year, > most recently the "openstack" meetbot (which not only

Re: [openstack-dev] [tripleo] Intermittent Jenkins failures

On 2017-07-20 09:27:23 -0600 (-0600), Alex Schultz wrote: > (updated topic to include [tripleo]) > > On Thu, Jul 20, 2017 at 9:20 AM, Abhishek Kane > wrote: [...] > > and undercloud install: > > > >

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

Greetings OpenStack community, Most of the time in today's meeting was dedicated to discussing ideas for the Guided Review Process [0] (that link will expire in favor of a gerrit review soon) we are considering for the PTG. The idea is that projects which are enmeshed in debate over how to

Re: [openstack-dev] [nova] loss of WSGI request logs with request-id under uwsgi/apache - PLAN OF ACTION

On 07/20/2017 09:27 AM, Sean Dague wrote: > Here is a starting patch that gets us close (no tests yet) - > https://review.openstack.org/#/c/485602/ - it's going to require a paste > change, which is less than idea. After some #openstack-nova IRC discussion this morning, we decided the following:

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On 19/07/17 22:27, Monty Taylor wrote: I propose we set aside time at the PTG to dig in to this. Between Zane and I and the Keystone core team I have confidence we can find a way out. This may be a bad time to mention that regrettably I won't be attending the PTG, due to (happy!) family

Re: [openstack-dev] [kolla][TripleO] New areas for collaboration between Kolla and TripleO

On 20/07/17 08:18 -0700, Emilien Macchi wrote: On Thu, Jul 20, 2017 at 7:27 AM, Andy McCrae wrote: [...] Hopefully that is useful, happy to discuss this more (or any other collaboration points!) if that does sound interesting. Andy [1]

Re: [openstack-dev] [tripleo] Intermittent Jenkins failures

(updated topic to include [tripleo]) On Thu, Jul 20, 2017 at 9:20 AM, Abhishek Kane wrote: > Hi, > > > > Recently saw intermittent jenkins failures in difference scenarios for patch > https://review.openstack.org/#/c/475765/17. > > > > Current ones are- > > In

[openstack-dev] Intermittent Jenkins failures

Hi, Recently saw intermittent jenkins failures in difference scenarios for patch https://review.openstack.org/#/c/475765/17. Current ones are- In overcloud deploy: http://logs.openstack.org/65/475765/17/check/gate-tripleo-ci-centos-7-scenario001-multinode-oooq/685b8bd/console.html

Re: [openstack-dev] [kolla][TripleO] New areas for collaboration between Kolla and TripleO

On Thu, Jul 20, 2017 at 7:27 AM, Andy McCrae wrote: [...] > Hopefully that is useful, happy to discuss this more (or any other > collaboration points!) if that does sound interesting. > Andy > > [1] >

Re: [openstack-dev] [magnum] Architecture support for either VM or Ironic instance as Containers' Host ?

Hi Greg, You're correct - magnum features support for running on top of VMs or baremetal. Currently baremetal is supported for kubernetes on Fedora core only[1]. There is a cluster template parameter 'server_type', which should be set to 'BM' for baremetal clusters. In terms of how this works

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

Greg, This may not be exactly what your looking for but close. (Ocata - NB no inspector implementation) Ocata video (no audio): https://www.youtube.com/watch?v=rHCCUP2odd8=52s Or check out this more extensive (with audio track) video of real-world usage of ironic:

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

Hi Greg, > I’m an ironic newbie ... > First of, welcome to the community (-: > where can I find a good / relatively-current (e.g. PIKE) demo of Ironic > integrated within OpenStack ? > I would recommend deploying it with DevStack on a VM and playing with it, you can follow this document in

[openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

hey there, I’m an ironic newbie ... where can I find a good / relatively-current (e.g. PIKE) demo of Ironic integrated within OpenStack ? Greg. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla][TripleO] New areas for collaboration between Kolla and TripleO

On 20/07/17 15:27 +0100, Andy McCrae wrote: Hi all, Some areas of collaboration: * Kubernetes resources: Work on the same set of resources. In this case, resources means the existing templates in kolla-kubernetes. Find ways to share the same resources rather than having 2 different sets

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On 07/19/2017 09:27 PM, Monty Taylor wrote: > On 07/19/2017 12:18 AM, Zane Bitter wrote: >> On 18/07/17 10:55, Lance Bragstad wrote: Would Keystone folks be happy to allow persistent credentials once we have a way to hand out only the minimum required privileges?

Re: [openstack-dev] [kolla][TripleO] New areas for collaboration between Kolla and TripleO

Hi all, > > > Some areas of collaboration: > > * Kubernetes resources: Work on the same set of resources. In this case, > resources means the existing templates in kolla-kubernetes. Find ways to > share > the same resources rather than having 2 different sets of resources. > > * Configuration

Re: [openstack-dev] [tripleo] Logging in containerized services

On Wed, Jul 19, 2017 at 4:53 AM, Mark Goddard wrote: > Kolla-ansible went through this process a few years ago, and ended up with > a solution involving heka pulling logs from files in a shared docker volume > (kolla_logs) That's basically the same solution that we're

Re: [openstack-dev] [nova] loss of WSGI request logs with request-id under uwsgi/apache

On 07/19/2017 06:28 PM, Matt Riedemann wrote: > On 7/19/2017 6:16 AM, Sean Dague wrote: >> We hit a similar issue with placement, and added custom >> paste middleware for that. Maybe we need to consider a similar thing >> here, that would only emit if running under uwsgi/apache? > > For example,

Re: [openstack-dev] Access to keystone_authtoken config options (required for Sahara trust)

Hi, > I naively tried (see https://review.openstack.org/#/c/485521/ ) to simply > replace the old config key with the new ones, but this fails with: > oslo_config.cfg.NoSuchOptError: no such option project_name in group > [keystone_authtoken] > > I found this thread on this list, few months

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

On Thu, 2017-07-20 at 13:06 +, Jeremy Stanley wrote: On 2017-07-20 07:49:08 + (+), Dulko, Michal wrote: [...] Would it be possible to *add* #openstack-helm channel during those changes? [...] Absolutely! I've left a comment on your change linking this ML thread, but I expect

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

On 2017-07-20 07:49:08 + (+), Dulko, Michal wrote: [...] > Would it be possible to *add* #openstack-helm channel during those > changes? [...] Absolutely! I've left a comment on your change linking this ML thread, but I expect we'll have the situation (temporarily) resolved over the next

[openstack-dev] [sahara][keystone][oslo.config] Access to keystone_authtoken config options (required for Sahara trust)

Hi, I was trying to deploy Sahara/Pike using TripleO and the cluster creation does not work, while it works on Sahara gates. Cluster operation uses trust (see http://specs.openstack.org/openstack/sahara-specs/specs/liberty/cluster-creation-with-trust.html) The difference between the two

[openstack-dev] [kolla][TripleO] New areas for collaboration between Kolla and TripleO

Hello Team, The TripleO team and the Kolla team met on IRC yday to explore areas where collaboration is possible, now that TripleO is looking into jumping on the Kubernetes wagon. Below you can find a brief summary of the meeting and some of the action items that came out from it. But, before

Re: [openstack-dev] [nova] loss of WSGI request logs with request-id under uwsgi/apache

On 07/19/2017 06:28 PM, Matt Riedemann wrote: > On 7/19/2017 6:16 AM, Sean Dague wrote: >> We hit a similar issue with placement, and added custom >> paste middleware for that. Maybe we need to consider a similar thing >> here, that would only emit if running under uwsgi/apache? > > For example,

Re: [openstack-dev] [nova] loss of WSGI request logs with request-id under uwsgi/apache

On 07/19/2017 09:46 PM, Matt Riedemann wrote: > On 7/19/2017 6:16 AM, Sean Dague wrote: >> I was just starting to look through some logs to see if I could line up >> request ids (part of global request id efforts), when I realized that in >> the process to uwsgi by default, we've entirely lost the

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On 07/19/2017 10:00 PM, Adrian Turjak wrote: > The problem is then entirely procedural within a team. Do they rotate > all keys when one person leaves? Anything less is the same problem. All > we can do is make rotation less of a pain, but it will still be painful > no matter what, and depending

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

jd Thanks for your contribution for oslo, you are not alone on tooz, I would like to spent some time on it when I have time :-) 2017-07-20 18:24 GMT+08:00 Davanum Srinivas : > Thanks for all your help @jd !! yes of course (on tooz) > > -- Dims > > On Thu, Jul 20, 2017 at

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

Thanks for all your help @jd !! yes of course (on tooz) -- Dims On Thu, Jul 20, 2017 at 3:59 AM, Julien Danjou wrote: > Hi folks, > > I've not been reviewing or contributing to oslo.* stuff for a while and > I don't intend to change that in the near future. It seems only

[openstack-dev] [QA][tempest] New Tempest stable interfaces coming soon

We have been working on making more Tempest module stable, especially for Tempest plugins. Once this work is complete, plugins will benefit from backward compatibility on an extended set of Tempest API. This benefit comes at a small cost though, since we have to make a few changes to the modules

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

On Wed, Jul 19, 2017 at 3:54 PM, Chris Dent wrote: On Wed, 19 Jul 2017, Balazs Gibizer wrote: I added more info to the bug report and the review as it seems the test is fluctuating. (Reflecting some conversation gibi and I have had in IRC) I've made a gabbi-based

[openstack-dev] [oslo] Stepping down from oslo-core

Hi folks, I've not been reviewing or contributing to oslo.* stuff for a while and I don't intend to change that in the near future. It seems only fair to step down. As I'm currently the only maintainer of tooz, I'd still suggest to leave me on tooz-core though. :) Cheers, -- Julien Danjou #

Re: [openstack-dev] [all] Cleaning up inactive meetbot channels

On Wed, 2017-07-19 at 19:24 +, Jeremy Stanley wrote: > For those who are unaware, Freenode doesn't allow any one user to > /join more than 120 channels concurrently. This has become a > challenge for some of the community's IRC bots in the past year, > most recently the "openstack" meetbot

Re: [openstack-dev] [rpm-packaging][karbor]

Hello Chen, On Mon, Jul 17, 2017 at 12:41 PM, Chen Ying wrote: > Hi Chandan, > >Thank your work about packaging abclient . > Both the packages are now available in cbs. https://review.rdoproject.org/r/#/c/7711/ got merged in RDO. Thanks, Chandan Kumar