[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] [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] [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] [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] [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] [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

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] 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

[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] [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 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

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] [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] 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

[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] [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: > > > > >

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

[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] [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] [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] [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 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] [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] [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] [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] 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

[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] [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

[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

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

[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] [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-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-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] [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] [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] [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

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,

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

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

[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] [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

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] [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

[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

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

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] [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] [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] gate jobs - papercuts

On Wed, Feb 1, 2017 at 6:57 PM, Davanum Srinivas wrote: > Thanks Melanie! Since the last report 4 hours ago, the > ServersNegativeTestJSON failed 8 more times. > > Is the following one of the libvirt ones? > >

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

Adding openstack-dev ML with [networking-ovn] tag. Please see comments inline On Thu, Feb 2, 2017 at 3:01 PM, pranab boruah wrote: > Hi guys, > We have a OpenStack multi-node lab. Everything was working, until I tried > integrating with OVN. > Followed the

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

Numan, Details as requested: ___ ml2_conf.ini:| ``` ovn_nb_connection = tcp:192.168.10.10:6641 ovn_sb_connection = tcp:192.168.10.10:6642 ovn_l3_mode = True ovn_l3_scheduler = chance ovn_l3_admin_net_cidr = 169.254.128.0/30 ovn_native_dhcp = True Note: 192.168.10.10 is

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

On Thu, Feb 2, 2017 at 4:00 PM, pranab boruah wrote: > Numan, > Details as requested: > > ___ > ml2_conf.ini:| > ``` > ovn_nb_connection = tcp:192.168.10.10:6641 > ovn_sb_connection = tcp:192.168.10.10:6642 > ovn_l3_mode = True >

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

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

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

Numan, Thanks, but, the above commands didn't changed anything. Checked the logs and found this: LOG of NB database: 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10: bind: Address already in use 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10: bind: Address

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

I'd like to request a feature freeze exception to add Tacker to Triple-o. This work is mostly already done. The puppet-tripleo work is already merged, the packaging and puppet-tacker work is also already complete. It should not take more than a couple days to finish up. Current outstanding

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

Due to inactivity and a change in his day job, Guang was informed that he would be removed from keystone-core, a change he understands and supports. I'd like to publicly thank Guang for his years of service as a core member. He juggled upstream and downstream responsibilities at HP while bringing

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

On 02/02/2017 07:56 AM, Emilien Macchi wrote: > On Thu, Feb 2, 2017 at 6:52 AM, Dan Radez wrote: >> I'd like to request a feature freeze exception to add Tacker to >> Triple-o. This work is mostly already done. The puppet-tripleo work is >> already merged, the packaging and

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On 02/02/2017, 15:43, "gordon chung" wrote: > > On 02/02/17 06:30 AM, Afek, Ifat (Nokia - IL) wrote: > > I understand. So clearly the use case of Vitrage raising alarms in Aodh is > > not relevant at the moment. > > We will have to think if over and see how Panko fits in the

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

I'd like to request a feature freeze exception to add Congress to Triple-o. This work is mostly already done. The puppet-tripleo work is already merged and the puppet-congress work is complete. https://blueprints.launchpad.net/tripleo/+spec/congress-service-integration We hit a packaging snag

[openstack-dev] [cinder]Using DEFAULT section to configure drivers is not supported since Ocata

Hi! Because of the deprecated driver configuration in the DEFAULT section doesn't work anymore in Ocata, I would like to ask if any migration tool exists for using the previously created volumes? E.g. if the existing volumes have the attribute os-vol-host-attr:host like hostname#RBD, cinder

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

On 02/02/2017 07:53 AM, Emilien Macchi wrote: > On Thu, Feb 2, 2017 at 7:00 AM, Dan Radez wrote: >> I'd like to request a feature freeze exception to add Congress to >> Triple-o. This work is mostly already done. The puppet-tripleo work is >> already merged and the

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

On Thu, Feb 2, 2017 at 6:05 PM, pranab boruah wrote: > Numan, > Sorry for making this thread too long. > Kind of deadlock scenario here: > The process listening on port 6641 is ovsdb-server(not NB db). > ​This is strange. The default port should be 6640 I suppose if

Re: [openstack-dev] [craton] Proposing Harry Harrington for Craton core

Done. On Wed, Feb 1, 2017 at 6:05 PM, Jim Baker wrote: > +1 to both recommendations by Sulo. > > Let me also add: Harry has proven himself as a strong contributor to > Craton development. I have been especially impressed by how his work has > helped improve the quality and

Re: [openstack-dev] [tripleo] Deployment plan management efforts sync up

On Thu, Feb 2, 2017 at 6:56 AM, Jiri Tomasek wrote: > Hello all, > > there has been several ongoing efforts in TripleO regarding Deployment Plans > management and Deployment configuration itself. A lot of this work is done > to satisfy certain individual requirements but I

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

On Thu, Feb 2, 2017 at 6:52 AM, Dan Radez wrote: > I'd like to request a feature freeze exception to add Tacker to > Triple-o. This work is mostly already done. The puppet-tripleo work is > already merged, the packaging and puppet-tacker work is also already > complete. > > It

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

Excerpts from Armando M.'s message of 2017-02-01 18:13:46 -0800: > Hi, > > There is something puzzling about release notes. I don't see 8.0.0 [1], and > it looks like features released in Mitaka are being advertised as Newton > features [2]. For instance, [3] 'Agent availability zones' shows as a

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

Excerpts from Octave J. Orgeron's message of 2017-02-01 20:33:38 -0700: > 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. My approach

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

On Thu, Feb 2, 2017 at 4:44 PM, pranab boruah wrote: > Numan, > > Thanks, but, the above commands didn't changed anything. Checked the logs > and found this: > > ​ Could you run the below two commands and see how it goes - "ovn-nbctl --db=tcp:192.168.10.10:6641

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On 31/01/2017, 18:43, "gordon chung" wrote: > On 31/01/17 08:34 AM, Afek, Ifat (Nokia - IL) wrote: > > If you query Vitrage (or get a notification from Vitrage) and then you > > query Aodh, then Aodh will not return any additional information. But – if > > you query only Aodh,

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

Forgot to include the BP link: https://blueprints.launchpad.net/tripleo/+spec/tacker-service-integration On 02/02/2017 06:52 AM, Dan Radez wrote: > I'd like to request a feature freeze exception to add Tacker to > Triple-o. This work is mostly already done. The puppet-tripleo work is > already

Re: [openstack-dev] [tripleo] Deployment plan management efforts sync up

On Thu, Feb 2, 2017 at 1:46 PM, Emilien Macchi wrote: > On Thu, Feb 2, 2017 at 6:56 AM, Jiri Tomasek wrote: > > Hello all, > > > > there has been several ongoing efforts in TripleO regarding Deployment > Plans > > management and Deployment configuration

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On 02/02/17 06:30 AM, Afek, Ifat (Nokia - IL) wrote: > I understand. So clearly the use case of Vitrage raising alarms in Aodh is > not relevant at the moment. > We will have to think if over and see how Panko fits in the use case. if the use case is that you wanted to store history of Vitrage

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

NB db is not listening on the port 6641: # ovn-nbctl --db=tcp:192.168.10.10:6641 show 2017-02-02T11:35:10Z|1|ovsdb_idl|ERR|tcp:192.168.10.10:6641: requested schema not found ovn-nbctl: tcp:192.168.10.10:6641: database connection failed (No such file or directory) # ovn-sbctl

[openstack-dev] [tripleo] Deployment plan management efforts sync up

Hello all, there has been several ongoing efforts in TripleO regarding Deployment Plans management and Deployment configuration itself. A lot of this work is done to satisfy certain individual requirements but I think some further discussion needs to happen to make sure the solutions we

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

Numan, Sorry for making this thread too long. Kind of deadlock scenario here: The process listening on port 6641 is ovsdb-server(not NB db). Details: Start OVS: # /usr/share/openvswitch/scripts/ovs-ctl start --system-id="random" # netstat -putna | grep 6641 tcp0 0 192.168.10.10:6641

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

On Thu, Feb 2, 2017 at 7:00 AM, Dan Radez wrote: > I'd like to request a feature freeze exception to add Congress to > Triple-o. This work is mostly already done. The puppet-tripleo work is > already merged and the puppet-congress work is complete. It would be great to have to

Re: [openstack-dev] [tripleo] Deployment plan management efforts sync up

On 2.2.2017 13:57, Ana Krivokapic wrote: On Thu, Feb 2, 2017 at 1:46 PM, Emilien Macchi > wrote: On Thu, Feb 2, 2017 at 6:56 AM, Jiri Tomasek > wrote: > Hello all, > > there

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

On Thu, Feb 2, 2017 at 8:24 AM, Dan Radez wrote: > > > On 02/02/2017 07:56 AM, Emilien Macchi wrote: >> On Thu, Feb 2, 2017 at 6:52 AM, Dan Radez wrote: >>> I'd like to request a feature freeze exception to add Tacker to >>> Triple-o. This work is mostly

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

Excerpts from Dean Troyer's message of 2017-02-01 22:41:46 -0600: > On Wed, Feb 1, 2017 at 8:13 PM, Armando M. wrote: > > I suspect what happens is that someone revises the content at a later date > > and reno associated the last timestamp of the release note with release > >

Re: [openstack-dev] [ovs-discuss] [neutron][networking-ovn] OpenStack Newton using OVN as mechanism driver is giving error.

In the ovsdb logs I see 2017-02-02T11:07:12.366Z|00020|socket_util|ERR|6641:192.168.10.10: bind: Address already in use 2017-02-02T11:07:14.869Z|00021|socket_util|ERR|6641:192.168.10.10: bind: Address already in use 2017-02-02T11:07:16.182Z|00022|socket_util|ERR|6641:192.168.10.10: bind: Address

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] [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

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] [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] [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

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] [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] [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

[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] [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

[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

[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]

  1   2   >