[openstack-dev] [TripleO] improved privilege escalation in py-scripts

Dear all, In order to improve the overall security in TripleO, we're currently creating a couple of specs, aiming Stein version. The first one concerns calls to "sudo" from shell scripts and the like: https://review.openstack.org/572760 The second one concerns privilege escalation inside python

Re: [openstack-dev] [sqlalchemy][db][oslo.db][mistral] Is there a recommended MySQL driver for OpenStack projects?

> > If you have a scaling issue that may be solved by eventlet, that's > one thing, but please don't adopt eventlet just because a lot of > other projects have. We've tried several times to minimize our > reliance on eventlet because new releases tend to introduce bugs. > > Have you tried the

Re: [openstack-dev] [tripleo] TripleO CI squad status 7/03/2018

Apologies, The dark theme in my browser changed the font color of the text. The email is available at http://lists.openstack.org/pipermail/openstack-dev/2018-July/131984.html Thank you! On Tue, Jul 3, 2018 at 7:13 PM Wesley Hayutin wrote: > Greetings > > The TripleO squad has just completed

[openstack-dev] [tripleo] TripleO Tempest squad status 07/03/2018

Greetings, The TripleO Tempest squad has just completed Sprint 15 (6-15 - 7/03). The following is a summary of activities during this sprint. Epic: # Sprint 15 Epic ( Tempest Squad): Finish the refactoring of the core OpenStack services in python-tempestconf, refstack certification tests, and

Re: [openstack-dev] [tc] Technical Committee Update for 3 July

> > Discussions about affiliation diversity continue in two directions. > Zane's proposal for requirements for new project teams has stalled a > bit. The work Thierry and Mohammed have done on the diversity tags has > brought a new statistics script and a proposal to drop the use of the > tags in

[openstack-dev] [puppet][tripleo] Why is this acceptance test failing?

I need another set of eyes. I have a review that keeps failing here: http://logs.openstack.org/47/575147/16/check/puppet-openstack-beaker-centos-7/3f70cc9/job-output.txt.gz#_2018-07-04_00_42_19_696966 It's looking for the regular expression:

Re: [openstack-dev] [tc] [all] TC Report 18-26

Replying inline in outlook. Sorry. :( Prefixing with KF> -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Tuesday, July 03, 2018 1:04 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [tc] [all] TC Report 18-26 I'll answer inline, so that it's

[openstack-dev] [tripleo] TripleO CI squad status 7/03/2018

Greetings The TripleO squad has just completed Sprint 15 (6-15 - 7/03). The following is a summary of activities during this sprint. Epic: # Sprint 15 Epic (CI Squad): Begin migration of upstream jobs to native zuulv3. For a list of the completed and remaining items for the sprint please refer

[openstack-dev] [tc] [all] TC Report 18-27

HTML: https://anticdent.org/tc-report-18-27.html This week's TC Report will be relatively short. I wrote a lot of OpenStack related words yesterday in [Some Opinions On Openstack](https://anticdent.org/some-opinions-on-openstack.html). That post was related to one of the main themes that has

Re: [openstack-dev] [tc] [all] TC Report 18-26

I'll answer inline, so that it's easier to understand what part of your message I'm responding to. On 07/03/2018 02:37 PM, Fox, Kevin M wrote: Yes/no on the vendor distro thing. They do provide a lot of options, but they also provide a fully k8s tested/provided route too. kubeadm. I can take

Re: [openstack-dev] [tc] [all] TC Report 18-26

I don't dispute trivial, but a self hosting k8s on bare metal is not incredibly hard. In fact, it is easier then you might think. k8s is a platform for deploying/managing services. Guess what you need to provision bare metal? Just a few microservices. A dhcp service. dhcpd in a daemonset works

Re: [openstack-dev] [tc] [all] TC Report 18-26

Heh. your not going to like it. :) The very fastest path I can think of but is super disruptive is the following (there are also less disruptive paths): First, define what OpenStack will be. If you don't know, you easily run into people working across purposes. Maybe there are other things

Re: [openstack-dev] [barbican][cinder][glance][nova] Goodbye from JHUAPL

Thanks so much for your contributions to our ecosystem, Brianna! I'm sad to see you go! :( Best, -jay On 07/03/2018 03:13 PM, Poulos, Brianna L. wrote: All, After over five years of contributing security features to OpenStack, the JHUAPL team is wrapping up our involvement with OpenStack.

[openstack-dev] [barbican][cinder][glance][nova] Goodbye from JHUAPL

All, After over five years of contributing security features to OpenStack, the JHUAPL team is wrapping up our involvement with OpenStack. To all who have reviewed/improved/accepted our contributions, thank you. It has been a pleasure to be a part of the community. Regards, The JHUAPL

Re: [openstack-dev] [tc] Technical Committee Update for 3 July

Excerpts from Chris Dent's message of 2018-07-03 19:31:43 +0100: > On Tue, 3 Jul 2018, Doug Hellmann wrote: > > > Chris and Thierry have been discussing a technical vision for OpenStack. > > > > * https://etherpad.openstack.org/p/tech-vision-2018 > > Just so it's clear and credit where credit

Re: [openstack-dev] [tc] [all] TC Report 18-26

Yes/no on the vendor distro thing. They do provide a lot of options, but they also provide a fully k8s tested/provided route too. kubeadm. I can take linux distro of choice, curl down kubeadm and get a working kubernetes in literally a couple minutes. No compiling anything or building

Re: [openstack-dev] [tc] Technical Committee Update for 3 July

On Tue, 3 Jul 2018, Doug Hellmann wrote: Chris and Thierry have been discussing a technical vision for OpenStack. * https://etherpad.openstack.org/p/tech-vision-2018 Just so it's clear and credit where credit (or blame!) is due: Zane has been a leading part of this too. -- Chris Dent

[openstack-dev] [tc] Technical Committee Update for 3 July

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 at:

[openstack-dev] [chef] State of the Kitchen: 5th Edition

HTML: https://s.cassiba.com/openstack/state-of-the-kitchen-5th-edition/ This is the fifth installment of what is going on with Chef OpenStack. The aim is to give a quick overview to see our progress and what is on the menu. Feedback is always welcome on the content and what you'd like to see.

[openstack-dev] [ironic] The state of the ironic universe - July 2nd, 2018

The state of the ironic universe This month we're trying a new format to keep those interested updated on what is going on in ironic. The intent is for our weekly updates to now take the form of a monthly newsletter to cover highlights of what is going on in the ironic community. If you have

Re: [openstack-dev] [tc] [all] TC Report 18-26

On Tue, Jul 3, 2018 at 1:06 PM Jay Pipes wrote: > > On 07/02/2018 03:31 PM, Zane Bitter wrote: > > On 28/06/18 15:09, Fox, Kevin M wrote: > >> * made the barrier to testing/development as low as 'curl > >> http://..minikube; minikube start' (this spurs adoption and > >> contribution) > > >

Re: [openstack-dev] [tc] [all] TC Report 18-26

On 07/02/2018 03:31 PM, Zane Bitter wrote: On 28/06/18 15:09, Fox, Kevin M wrote:   * made the barrier to testing/development as low as 'curl http://..minikube; minikube start' (this spurs adoption and contribution) That's not so different from devstack though.   * not having large

[openstack-dev] [sig][upgrade] Todays IRC meeting

Hi All Unfortunately I can't make todays IRC meeting at 1600 UTC. Should be back for next week, but I think we need todo some rescheduling to fit better with other ops and dev meetings. Cheers James __ OpenStack

Re: [openstack-dev] [sqlalchemy][db][oslo.db][mistral] Is there a recommended MySQL driver for OpenStack projects?

On 07/03/2018 08:47 AM, Doug Hellmann wrote: If you have a scaling issue that may be solved by eventlet, that's one thing, but please don't adopt eventlet just because a lot of other projects have. We've tried several times to minimize our reliance on eventlet because new releases tend to

Re: [openstack-dev] [neutron] autodoc and tox-siblings

Excerpts from Takashi Yamamoto's message of 2018-07-03 13:12:53 +0900: > hi, > > - networking-midonet uses autodoc in their doc. > build-openstack-sphinx-docs runs it. > - build-openstack-sphinx-docs doesn't use tox-siblings. thus the job > uses released versions of dependencies. eg. neutron,

Re: [openstack-dev] [sqlalchemy][db][oslo.db][mistral] Is there a recommended MySQL driver for OpenStack projects?

Excerpts from Renat Akhmerov's message of 2018-07-03 18:33:44 +0700: > Hi, > > We’ve tried to address the bug [1] which is essentially caused > by the fact that we saw that MySQLDb driver wasn’t compatible with > eventlet’s green threads. In a nutshell, when we used the “eventlet” > RPC executor

Re: [openstack-dev] [sqlalchemy][db][oslo.db][mistral] Is there a recommended MySQL driver for OpenStack projects?

On 2018-07-03 18:33:44 +0700 (+0700), Renat Akhmerov wrote: [...] > So, I’m trying to understand if we have a “community recommended” > (or may be even mandatory) Mysql driver to use and what > consequences of the driver choice are. I’d appreciate any help > with clarifying this (may be links to

Re: [openstack-dev] [Puppet] Requirements for running puppet unit tests?

On 07/02/2018 08:57 PM, Lars Kellogg-Stedman wrote: On Thu, Jun 28, 2018 at 8:04 PM, Lars Kellogg-Stedman > wrote: What is required to successfully run the rspec tests? On the odd chance that it might be useful to someone else, here's the Docker image I'm using to

Re: [openstack-dev] [Edge-computing] [edge][glance][mixmatch]: Wiki of the possible architectures for image synchronisation

In-lined below, Greg From: "Csatari, Gergely (Nokia - HU/Budapest)" Date: Monday, July 2, 2018 at 7:15 AM To: Greg Waines , "openstack-dev@lists.openstack.org" , "edge-comput...@lists.openstack.org" Subject: RE: [Edge-computing] [edge][glance][mixmatch]: Wiki of the possible architectures

[openstack-dev] [sqlalchemy][db][oslo.db][mistral] Is there a recommended MySQL driver for OpenStack projects?

Hi, We’ve tried to address the bug [1] which is essentially caused by the fact that we saw that MySQLDb driver wasn’t compatible with eventlet’s green threads. In a nutshell, when we used the “eventlet” RPC executor (see [2]), the system would get stuck once in a while when dispatching green

Re: [openstack-dev] [tc] [all] TC Report 18-26

Zane Bitter wrote: [...] I think if OpenStack wants to gain back some of the steam it had before, it needs to adjust to the new world it is living in. This means:   * Consider abolishing the project walls. They are driving bad architecture (not intentionally but as a side affect of structure)

[openstack-dev] log-classify project update (anomaly detection in CI/CD logs)

Hello, This is a follow-up to the initial project creation thread[0]. At the Vancouver Summit, we met to discuss ML for CI[1] and I lead a workshop on logreduce[2]. The log-classify project bootstrap is still waiting for review[3] and I am still looking forward to pushing logreduce[4] source

Re: [openstack-dev] [neutron] autodoc and tox-siblings

On 2018-07-03 06:12, Takashi Yamamoto wrote: > hi, > > - networking-midonet uses autodoc in their doc. > build-openstack-sphinx-docs runs it. > - build-openstack-sphinx-docs doesn't use tox-siblings. thus the job > uses released versions of dependencies. eg. neutron, neutron-XXXaas, > os-vif,

[openstack-dev] [Openstack-sigs][self-healing][heat][vitrage][mistral] Self-Healing with Vitrage, Heat, and Mistral

Dear all Back to Vancouver Summit, Ifat brings out the idea of integrating Heat, Vitrage, and Mistral to bring better self-healing scenario. For previous works, There already works cross Heat, Mistral, and Zaqar for self-healing [1]. And there is works cross Vitrage, and Mistral [2]. Now we plan