Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

At Wed, 1 Feb 2017 16:24:54 -0800, Armando M. wrote: > > Hi, > > [TL;DR]: OpenStack services have steadily increased their memory > footprints. We need a concerted way to address the oom-kills experienced in > the openstack gate, as we may have reached a ceiling. > > Now the longer version: >

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

Has anyone tried: https://github.com/mgedmin/dozer/blob/master/dozer/leak.py#L72 This piece of middleware creates some nice graphs (using PIL) that may help identify which areas are using what memory (and/or leaking). https://pypi.python.org/pypi/linesman might also be somewhat useful to

[openstack-dev] [Horizon] Weekly wrap-up

Hi folks, The mad rush to RC1 concluded this week with RC1 now tagged and the stable/ocata branch created. We've got a couple of bugfixes that should have made the RC1 release but just missed out so we're going to try to get those in for RC2; otherwise RC1 is a good release, we can all be happy

Re: [openstack-dev] [openstack-community] OpenStack Summit Boston-CFP closes February 6th

Hi Erin, Thank you for the reminder and other info. In you previous mail, > Panels are allowed a total of four speakers plus one moderator, whereas > presentations and lightning talks are limited to two speakers. To the best of my knowledge, presentations limited to three speakers. Not sure

[openstack-dev] [nova] ocata rc1 is (almost) ready to go

I've got the patch up in the releases repo and the listed dependencies are all merged: https://review.openstack.org/#/c/428531/ I've got a WIP on it until tomorrow when we can talk through some of the last items in the etherpad: https://etherpad.openstack.org/p/nova-ocata-rc1-todos Thanks

Re: [openstack-dev] [TripleO] FFE for novajoin in TripleO's undercloud

On Thu, Feb 2, 2017 at 10:22 PM, Michael Still wrote: > What version of nova is tripleo using here? This wont work quite right if > you're using Mitaka until https://review.openstack.org/#/c/427547/ lands and > is released. TripleO Ocata will use Nova Ocata, using the release

[openstack-dev] [Gluon] Look Forward to Meeting You on Monday Feb 6 and Tuesday Feb 7 in Sunnyvale, CA

Hello team, As we discussed in [1] and [2], and announced in [3], we are all set for Monday Feb 6th and Tuesday Feb 7th in the EBC center at Juniper's office in Sunnyvale. Many thanks to Sukhdev and Juniper team for hosting this meeting. Please refer to [4] for more detailed logistic

Re: [openstack-dev] [TripleO] FFE for novajoin in TripleO's undercloud

What version of nova is tripleo using here? This wont work quite right if you're using Mitaka until https://review.openstack.org/#/c/427547/ lands and is released. Also, I didn't know novajoin existed and am pleased to have discovered it. Michael On Fri, Feb 3, 2017 at 11:27 AM, Juan Antonio

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 3 Feb. 2017 16:14, "Robert Collins" wrote: This may help. http://jam-bazaar.blogspot.co.nz/2009/11/memory- debugging-with-meliae.html -rob Oh, and if i recall correctly run snake run supports both heapy and meliae. ,-rob

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

This may help. http://jam-bazaar.blogspot.co.nz/2009/11/memory-debugging-with-meliae.html -rob On 3 Feb. 2017 10:39, "Armando M." wrote: > > > On 2 February 2017 at 13:36, Ihar Hrachyshka wrote: > >> On Thu, Feb 2, 2017 at 7:44 AM, Matthew Treinish

Re: [openstack-dev] [congress] congress 5.0.0.0rc1 (ocata)

RC1 released. Great job everyone for getting our fixes in! Let¹s continue testing and reporting bugs to make sure Ocata is a rock-solid release! On 2/2/17, 5:01 PM, "no-re...@openstack.org" wrote: > >Hello everyone, > >A new release candidate for congress for the end of

[openstack-dev] [nova] Final mascot

I was sent a copy of the final mascot for Nova which is attached here. The Foundation wants to have the mascots finalized before the PTG. This is just an opportunity for people to raise issues with it if they have any. The original email: -- Hi Matt, I have a new revision from our

Re: [openstack-dev] [Openstack-operators] Large Contributing OpenStack Operators working group?

On Thu, Feb 2, 2017 at 1:14 PM, Jay Pipes wrote: > Hi, > > I was told about this group today. I have a few questions. Hopefully someone > from this team can illuminate me with some answers. > > 1) What is the purpose of this group? The wiki states that the team "aims to >

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On Thu, Feb 2, 2017 at 9:35 AM, Attila Darazs wrote: > On 02/01/2017 08:37 PM, John Trowbridge wrote: > >> >> >> On 01/30/2017 10:56 AM, Emilien Macchi wrote: >> >>> Sagi, you're now core on TripleO CI repo. Thanks for your hard work on >>> tripleo-quickstart transition, and

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Excerpts from Octave J. Orgeron's message of 2017-02-02 15:08:14 -0700: > Comments below.. > > On 2/2/2017 1:08 PM, Doug Hellmann wrote: > > Excerpts from Octave J. Orgeron's message of 2017-02-02 12:16:15 -0700: > >> Hi Doug, > >> > >> Comments below.. > >> > >> Thanks, > >> Octave > >> > >> On

[openstack-dev] [all] Upcoming tox 2.6.0 release

Hi All, I don't expect a problem but I also don't know how/if we control which tox version is installed in out images. Based on the thread here [1] It seems there will be a tox 2.6.0 release real soon now. Yours Tony. [1]

[openstack-dev] [congress] congress 5.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for congress for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/congress/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [TripleO] FFE for novajoin in TripleO's undercloud

Hello, I would like to request an FFE to properly support the novajoin vendordata plugin in TripleO. Most of the work has landed, however, we still need to add it to TripleO's CI in order to have it officially supported. This is crucial for TLS-everywhere configuration's usability, since it

[openstack-dev] [neutron] [stadium] subprojects on independent release cycle

Hi neutrinos, I have put a number of patches in the merge queue for a few sub-projects. We currently have a number of these that are on an independent release schedule. In particular: - networking-bagpipe - networking-bgpvpn - networking-midonet - networking-odl - networking-sfc

Re: [openstack-dev] [openstack-docs][security] Sec guide change

Nice work! L On 03/02/17 05:06, Alexandra Settle wrote: > Hi everyone, > > > > As of today, all bugs for the Security Guide will be managed by > ossp-security-documentation and no longer will be tracked using the OpenStack > manuals Launchpad. > > > > All tracking for Security Guide

[openstack-dev] [mistral] mistral-dashboard 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for mistral-dashboard for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [mistral] mistral 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for mistral for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On Feb 2, 2017, at 10:16 AM, Matthew Treinish wrote: > If that was intentional, it is the funniest thing I’ve read today. :) -- Ed Leafe __ OpenStack

[openstack-dev] networking-powervm 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for networking-powervm for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-powervm/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] nova_powervm 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for nova_powervm for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova-powervm/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

I'm referring to Apache sitting in between the services now as a TLS terminator and connection proxy. That was not the configuration before but it is now the default devstack behavior. See this example from Newton:

Re: [openstack-dev] [ironic] New mascot design

Hi, > I'm with the group here. > > Let's find something that looks nice and is not offensive to anyone. > +1 ... Also, Heidi, I forgot to ask in the previous emails and I couldn't find in the guidelines[0]: What license will these images have ? Will people be allowed to share and create

[openstack-dev] [telemetry] ceilometer-powervm 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for ceilometer-powervm for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/ceilometer-powervm/ Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

That refers to the total length of the row. InnoDB has a limit of 65k and NDB is limited to 14k. A simple example would be the volumes table in Cinder where the row length goes beyond 14k. So in the IF logic block, I change columns types that are vastly oversized such as status and

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Comments below.. On 2/2/2017 1:08 PM, Doug Hellmann wrote: Excerpts from Octave J. Orgeron's message of 2017-02-02 12:16:15 -0700: Hi Doug, Comments below.. Thanks, Octave On 2/2/2017 11:27 AM, Doug Hellmann wrote: Excerpts from Octave J. Orgeron's message of 2017-02-02 09:40:23 -0700: Hi

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 02/02/2017 04:07 PM, Kevin Benton wrote: > This error seems to be new in the ocata cycle. It's either related to a > dependency change or the fact that we put Apache in between the services > now. Handling more concurrent requests than workers wasn't an issue > before. > > It seems that you

[openstack-dev] [freezer] freezer-api 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for freezer-api for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-api/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

[openstack-dev] [freezer] freezer-web-ui 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for freezer-web-ui for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-web-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [freezer] freezer-dr 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for freezer-dr for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer-dr/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [freezer] freezer 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for freezer for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/freezer/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Hi Doug, Comments below.. Thanks, Octave On 2/2/2017 12:52 PM, Mike Bayer wrote: On 02/02/2017 02:16 PM, Octave J. Orgeron wrote: Hi Doug, Comments below.. Thanks, Octave On 2/2/2017 11:27 AM, Doug Hellmann wrote: It sounds like part of the plan is to use the configuration setting to

[openstack-dev] [keystone] keystone 11.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for keystone for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/keystone/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

Note the HTTPS in the traceback in the bug report. Also the mention of adjusting the Apache mpm settings to fix it. That seems to point to an issue with Apache in the middle rather than eventlet and API_WORKERS. On Feb 2, 2017 14:36, "Ihar Hrachyshka" wrote: > The

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On Thu, Feb 2, 2017 at 12:28 PM, Jeremy Stanley wrote: > On 2017-02-02 04:27:51 + (+), Dolph Mathews wrote: >> What made most services jump +20% between mitaka and newton? Maybe there is >> a common cause that we can tackle. > [...] > > Almost hesitant to suggest this

[openstack-dev] [neutron] Drivers meeting cancelled today

Hi, With the release coming up, it's best to spend the time to polish what we have. Sorry for the short notice. Thanks, Armando __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On Thu, Feb 2, 2017 at 12:50 PM, Sean Dague wrote: > > This is one of the reasons to get the wsgi stack off of eventlet and > into a real webserver, as they handle HTTP request backups much much > better. > > To some extent I think this is generally true for *many* common

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

2017-02-02 9:38 GMT-08:00 Chris Dent : > > Greetings OpenStack community, > > In today's meeting [0] after briefly covering old business we spent nearly > 50 minutes going round in circles discussing the complex interactions of > expectations of API stability, the need to

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 2 February 2017 at 13:36, Ihar Hrachyshka wrote: > On Thu, Feb 2, 2017 at 7:44 AM, Matthew Treinish > wrote: > > Yeah, I'm curious about this too, there seems to be a big jump in Newton > for > > most of the project. It might not a be a single

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 2 February 2017 at 13:34, Ihar Hrachyshka wrote: > The BadStatusLine error is well known: > https://bugs.launchpad.net/nova/+bug/1630664 That's the one! I knew it I had seen it in the past! > > > Now, it doesn't mean that the root cause of the error message is the >

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On Thu, Feb 2, 2017 at 7:44 AM, Matthew Treinish wrote: > Yeah, I'm curious about this too, there seems to be a big jump in Newton for > most of the project. It might not a be a single common cause between them, but > I'd be curious to know what's going on there. Both Matt

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 2 February 2017 at 12:50, Sean Dague wrote: > On 02/02/2017 03:32 PM, Armando M. wrote: > > > > > > On 2 February 2017 at 12:19, Sean Dague > > wrote: > > > > On 02/02/2017 02:28 PM, Armando M. wrote: > > > > > > > > >

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

The BadStatusLine error is well known: https://bugs.launchpad.net/nova/+bug/1630664 Now, it doesn't mean that the root cause of the error message is the same, and it may as well be that lowering the number of workers triggered it. All I am saying is we saw that error in the past. Ihar On Thu,

[openstack-dev] [horizon] horizon 11.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for horizon for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/horizon/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] Large Contributing OpenStack Operators working group?

On 02/02/2017 20:17, Jay Pipes wrote: > Hi, > > I was told about this group today. I have a few questions. Hopefully > someone from this team can illuminate me with some answers. > > 1) What is the purpose of this group? The wiki states that the team > "aims to define the use cases and identify

Re: [openstack-dev] [Tripleo]FFE to update Eqlx and DellSc cinder templates

On Thu, Feb 2, 2017 at 2:05 PM, wrote: > Dell - Internal Use - Confidential > > > > > > I would like to request a freeze exception to update Dell EqualLogic and > Dell Storage Center cinder backend templates to use composable roles and > services in Triple-o. This work is

Re: [openstack-dev] [Tripleo] FFE to add ScaleIO to Triple-o

On Thu, Feb 2, 2017 at 2:00 PM, wrote: > Dell - Internal Use - Confidential > > > > I would like to request a feature freeze exception to ScaleIO cinder backend > support Triple-o. This work is done and pending review for the past three > weeks. The puppet-cinder work is

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

This error seems to be new in the ocata cycle. It's either related to a dependency change or the fact that we put Apache in between the services now. Handling more concurrent requests than workers wasn't an issue before. It seems that you are suggesting that eventlet can't handle concurrent

Re: [openstack-dev] [keystone] removing Guang Yee (gyee) from keystone-core

+1!!! Thanks Guang for all your hard work and your outstanding contributions to Keystone.   You were always a pleasure to work with. I wish you all the best on your new adventure!   --Brad Brad Topol, Ph.D.IBM Distinguished EngineerOpenStack(919) 543-0646Internet: bto...@us.ibm.comAssistant:

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 02/02/2017 03:32 PM, Armando M. wrote: > > > On 2 February 2017 at 12:19, Sean Dague > wrote: > > On 02/02/2017 02:28 PM, Armando M. wrote: > > > > > > On 2 February 2017 at 10:08, Sean Dague

[openstack-dev] [all][infra] Removal of tox-db- jobs and launching of MySQL/PostgreSQL

Hi, It seems infra is moving on on this project which was announced in November: http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html Andreas Jager kindly sent a bunch of patches with a bash script to setup MySQL/PostgreSQL. However, I just want to point out that a

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 2 February 2017 at 12:19, Sean Dague wrote: > On 02/02/2017 02:28 PM, Armando M. wrote: > > > > > > On 2 February 2017 at 10:08, Sean Dague > > wrote: > > > > On 02/02/2017 12:49 PM, Armando M. wrote: > > > > > > > > >

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

On 02/02/2017 02:52 PM, Mike Bayer wrote: But more critically I noticed you referred to altering the names of columns to suit NDB. How will this be accomplished? Changing a column name in an openstack application is no longer trivial, because online upgrades must be supported for

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 02/02/2017 02:28 PM, Armando M. wrote: > > > On 2 February 2017 at 10:08, Sean Dague > wrote: > > On 02/02/2017 12:49 PM, Armando M. wrote: > > > > > > On 2 February 2017 at 08:40, Sean Dague

[openstack-dev] Large Contributing OpenStack Operators working group?

Hi, I was told about this group today. I have a few questions. Hopefully someone from this team can illuminate me with some answers. 1) What is the purpose of this group? The wiki states that the team "aims to define the use cases and identify and prioritise the requirements which are

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Excerpts from Octave J. Orgeron's message of 2017-02-02 12:16:15 -0700: > Hi Doug, > > Comments below.. > > Thanks, > Octave > > On 2/2/2017 11:27 AM, Doug Hellmann wrote: > > Excerpts from Octave J. Orgeron's message of 2017-02-02 09:40:23 -0700: > >> Hi Doug, > >> > >> One could try to detect

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

On 02/02/2017 02:16 PM, Octave J. Orgeron wrote: Hi Doug, Comments below.. Thanks, Octave On 2/2/2017 11:27 AM, Doug Hellmann wrote: It sounds like part of the plan is to use the configuration setting to control how the migration scripts create tables. How will that work? Does each

Re: [openstack-dev] [storlets] ocata branch

Apologies for the date confusion in the below mail. This should happen on the week of the 13th, and clearly we need to base our branch on Swift’s Ocata branch. > On Feb 1, 2017, at 10:37 AM, Eran Rom wrote: > > Hi all, > I will create the stable/ocata branch tomorrow my

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Hi Doug, Comments below.. Thanks, Octave On 2/2/2017 11:27 AM, Doug Hellmann wrote: Excerpts from Octave J. Orgeron's message of 2017-02-02 09:40:23 -0700: Hi Doug, One could try to detect the default engine. However, in MySQL Cluster, you can support multiple storage engines. Only NDB is

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 2 February 2017 at 10:08, Sean Dague wrote: > On 02/02/2017 12:49 PM, Armando M. wrote: > > > > > > On 2 February 2017 at 08:40, Sean Dague > > wrote: > > > > On 02/02/2017 11:16 AM, Matthew Treinish wrote: > > > > >

[openstack-dev] [release] Release countdown for week R-2, 6-10 Feb

Focus - We are in the release candidate phase of the cycle. All project teams should be fixing last minute release-critical bugs and testing the prepared release candidates for their deliverables. Release Tasks - The translation team will be increasing their work over the next

Re: [openstack-dev] [kolla] Domains support

Hi, we've done this last week at Linaro. I have documented the process in a blog post that is a walkthrough of a post by Steve Martinelli[1] from the keystone team: http://thetestingcorner.com/2017/01/30/ldap-authentication-for-openstack/ At the bottom of it there is a gerrit review with a

[openstack-dev] [openstack-docs][security] Sec guide change

Hi everyone, As of today, all bugs for the Security Guide will be managed by ossp-security-documentation and no longer will be tracked using the OpenStack manuals Launchpad. All tracking for Security Guide related bugs can be found here: https://bugs.launchpad.net/ossp-security-documentation

[openstack-dev] [Tripleo]FFE to update Eqlx and DellSc cinder templates

Dell - Internal Use - Confidential I would like to request a freeze exception to update Dell EqualLogic and Dell Storage Center cinder backend templates to use composable roles and services in Triple-o. This work is done and pending merge for the past few weeks. Without these we won't be

[openstack-dev] [Tripleo] FFE to add ScaleIO to Triple-o

Dell - Internal Use - Confidential I would like to request a feature freeze exception to ScaleIO cinder backend support Triple-o. This work is done and pending review for the past three weeks. The puppet-cinder work is already merged. Pending review

Re: [openstack-dev] [Tripleo] FFE for tripleo collectd integration

On Thu, Feb 2, 2017 at 1:07 PM, Lars Kellogg-Stedman wrote: > I would like to request a feature freeze exception for the collectd > composable service patch: > > > https://blueprints.launchpad.net/tripleo/+spec/tripleo-opstools-performance-monitoring > > The gerrit review

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 2017-02-02 04:27:51 + (+), Dolph Mathews wrote: > What made most services jump +20% between mitaka and newton? Maybe there is > a common cause that we can tackle. [...] Almost hesitant to suggest this one but since we primarily use Ubuntu 14.04 LTS for stable/mitaka jobs and 16.04 LTS

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Excerpts from Octave J. Orgeron's message of 2017-02-02 09:40:23 -0700: > Hi Doug, > > One could try to detect the default engine. However, in MySQL Cluster, > you can support multiple storage engines. Only NDB is fully clustered > and replicated, so if you accidentally set a table to be InnoDB

Re: [openstack-dev] [ironic] New mascot design

Oh... I'm with the group here. Let's find something that looks nice and is not offensive to anyone. Mathieu On 2017-02-02 11:52 AM, Jay Faulkner wrote: https://en.wikipedia.org/wiki/Sign_of_the_horns came up in IRC, as the sign the bear is making. Obviously to me, I read it as the heavy

Re: [openstack-dev] [puppet] Thank you.

Thank you very much for your contributions Cody! =) 2017-01-24 17:59 GMT-03:00 Matt Fischer : > Cody, > > Thank you for your contributions over the years. > > On Fri, Jan 20, 2017 at 12:29 PM, Cody Herriges wrote: > >> I attempted to send this out last

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 02/02/2017 12:49 PM, Armando M. wrote: > > > On 2 February 2017 at 08:40, Sean Dague > wrote: > > On 02/02/2017 11:16 AM, Matthew Treinish wrote: > > > > > > > We definitely aren't saying running

[openstack-dev] [Tripleo] FFE for tripleo collectd integration

I would like to request a feature freeze exception for the collectd composable service patch: https://blueprints.launchpad.net/tripleo/+spec/tripleo-opstools-performance-monitoring The gerrit review implementing this is: https://review.openstack.org/#/c/411048/ The work on the composable

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 2 February 2017 at 08:40, Sean Dague wrote: > On 02/02/2017 11:16 AM, Matthew Treinish wrote: > > > > > > > We definitely aren't saying running a single worker is how we recommend > people > > run OpenStack by doing this. But it just adds on

[openstack-dev] [heat] heat 8.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for heat for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/heat/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

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

Greetings OpenStack community, In today's meeting [0] after briefly covering old business we spent nearly 50 minutes going round in circles discussing the complex interactions of expectations of API stability, the need to fix bugs and the costs and benefits of microversions. We didn't make a

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Hi Mike, I've sent out another email that gives some more insight into how this will work for the other OpenStack services. The hook in the oslo.db namespace gives a global configuration point for enabling the patches elsewhere. Thanks, Octave On 2/2/2017 9:24 AM, Mike Bayer wrote: On

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On 02/02/2017 11:42 AM, Sean Dague wrote: That's all fine and good, we just need to rewrite about 100,000 unit tests to do that. I'm totally cool with someone taking that task on, but making a decision about postgresql shouldn't be filibustered on rewriting all the unit tests in OpenStack

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Hi Monty, Thank you for the feedback. I'm excited about getting these patches upstream as everyone will be able to benefit from them. Thanks, Octave On 2/2/2017 8:25 AM, Monty Taylor wrote: On 02/01/2017 09:33 PM, Octave J. Orgeron wrote: Hi Folks, I'm working on adding support for MySQL

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On Thu, Feb 2, 2017 at 6:40 PM, Sean Dague wrote: > On 02/02/2017 11:16 AM, Matthew Treinish wrote: > > > > > > > We definitely aren't saying running a single worker is how we recommend > people > > run OpenStack by doing this. But it just adds

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

Hi Doug, One could try to detect the default engine. However, in MySQL Cluster, you can support multiple storage engines. Only NDB is fully clustered and replicated, so if you accidentally set a table to be InnoDB it won't be replicated . So it makes more sense for the operator to be explicit

Re: [openstack-dev] [ironic] New mascot design

https://en.wikipedia.org/wiki/Sign_of_the_horns came up in IRC, as the sign the bear is making. Obviously to me, I read it as the heavy metal gesture. Apparently it is offensive in some cultures, so I change my vote to -1, since I don’t want to offend folks in other parts of the world :). -Jay

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On 02/02/2017 11:48 AM, Julien Danjou wrote: > On Wed, Feb 01 2017, Julien Danjou wrote: > >> My questions are simple and can be organized in a tree: >> >>Does Nova want to support PostgreSQL? >> / \ >>Yes No

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On Wed, Feb 01 2017, Julien Danjou wrote: > My questions are simple and can be organized in a tree: > >Does Nova want to support PostgreSQL? > / \ >Yes No >/ \ >Why

[openstack-dev] [designate] designate 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for designate for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [designate] designate-dashboard 4.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for designate-dashboard for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On 02/02/2017 10:33 AM, Mike Bayer wrote: > > > On 02/01/2017 10:22 AM, Monty Taylor wrote: >> >> I personally continue to be of the opinion that without an explicit >> vocal and well-staffed champion, supporting postgres is more trouble >> than it is worth. The vast majority of OpenStack

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On 02/02/2017 11:16 AM, Matthew Treinish wrote: > > > We definitely aren't saying running a single worker is how we recommend people > run OpenStack by doing this. But it just adds on to the differences between > the > gate and what we expect things actually

Re: [openstack-dev] [neutron] [release] misleading release notes

On Thu, Feb 2, 2017 at 7:42 AM, Doug Hellmann wrote: > As long as the edit happens on the branch where the note should appear, > it should be fine. Excellent! Just tried it and it does, thanks. I think https://review.openstack.org/427842 is doing what you intend, I can

Re: [openstack-dev] [oslo][oslo.db] MySQL Cluster support

On 02/02/2017 10:25 AM, Monty Taylor wrote: On 02/01/2017 09:33 PM, Octave J. Orgeron wrote: Hi Folks, I'm working on adding support for MySQL Cluster to the core OpenStack services. This will enable the community to benefit from an active/active, auto-sharding, and scale-out MySQL database.

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On Thu, Feb 02, 2017 at 11:10:22AM -0500, Matthew Treinish wrote: > On Wed, Feb 01, 2017 at 04:24:54PM -0800, Armando M. wrote: > > Hi, > > > > [TL;DR]: OpenStack services have steadily increased their memory > > footprints. We need a concerted way to address the oom-kills experienced in > > the

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

On Wed, Feb 01, 2017 at 04:24:54PM -0800, Armando M. wrote: > Hi, > > [TL;DR]: OpenStack services have steadily increased their memory > footprints. We need a concerted way to address the oom-kills experienced in > the openstack gate, as we may have reached a ceiling. > > Now the longer version:

Re: [openstack-dev] [kolla] Domains support

Try /etc/kolla/config/keystone/domains/keystone.$DOMAIN.conf Thanks On 2 February 2017 at 00:20, Christian Tardif wrote: > Will sure give it a try ! And from a kolla perspective, it means that this > file should go in

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On 02/02/2017 10:59 AM, Monty Taylor wrote: On 02/02/2017 09:33 AM, Mike Bayer wrote: On 02/01/2017 10:22 AM, Monty Taylor wrote: I personally continue to be of the opinion that without an explicit vocal and well-staffed champion, supporting postgres is more trouble than it is worth. The

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

On 02/02/2017 09:33 AM, Mike Bayer wrote: > > > On 02/01/2017 10:22 AM, Monty Taylor wrote: >> >> I personally continue to be of the opinion that without an explicit >> vocal and well-staffed champion, supporting postgres is more trouble >> than it is worth. The vast majority of OpenStack

[openstack-dev] [trove] trove-dashboard 8.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for trove-dashboard for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/trove-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [Tripleo] FFE to add Congress to Triple-o

ok FFE granted. On Thu, Feb 2, 2017 at 9:59 AM, Alan Pevec wrote: > > Waiting for Alan to give -1/+1 on the RDO side, but it's a +1 for me > on the TripleO side. > > > +1 from me, I should finish missing PuLP dependency in RDO today > > > -- Emilien Macchi

  1   2   >