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? > > http://logs.openstack.org/24/425924/2/gate/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-

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 official guide for integration: > > h

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 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 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 > ovn_l3_scheduler = chance > ovn_l3_admin_ne

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 al

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, you will be aware

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 show" -> See if this command is s

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

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 mer

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 --db=tcp:192.168.

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

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 consistency of our cod

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

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

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 a

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] 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 think some further > dis

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 test Congress in Pu

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 should not take more

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 itself. A lot of this work is > done > > t

[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 puppet-tacker work is

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 puppet-congress work is comple

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 mailto:[email protected]>> wrote: > Hello all, > > there has been several ongoing efforts in TripleO reg

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 already done. The puppet-tripleo work is >

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] [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 > > where the change has

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] [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 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 not specified. ​ > Details

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 use case. > >

Re: [openstack-dev] [keystone] Do we really need two listening ports ?

Today the '-admin' version almost able to fully passing on tempest: http://logs.openstack.org/91/428091/1/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/9e4f5e6/logs/stackviz/#/stdin https://review.openstack.org/#/c/428091/ (Without the port merge, but it could be the next step ) At the firs

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

Thanks for everything Guang! We are already missing you. On Thu, Feb 2, 2017 at 10:13 AM, Steve Martinelli wrote: > 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 than

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

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 also helping by keeping CI in good shape, your work is amazing! Congrats! Note: I couldn't ad

[openstack-dev] [sahara] sahara-dashboard 6.0.0.0rc1 (ocata)

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

[openstack-dev] [sahara] sahara-image-elements 6.0.0.0rc1 (ocata)

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

[openstack-dev] [sahara] sahara 6.0.0.0rc1 (ocata)

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

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

Guang, it's been a pleasure working with you and getting to know you as a person. Best of luck in your new endeavors! On Thu, Feb 2, 2017 at 8:16 AM, Rodrigo Duarte wrote: > Thanks for everything Guang! We are already missing you. > > On Thu, Feb 2, 2017 at 10:13 AM, Steve Martinelli > wrote:

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

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 __ OpenStack Development Mailing List (not for usage questions) Unsubs

[openstack-dev] [sahara] sahara-extra 6.0.0.0rc1 (ocata)

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

[openstack-dev] [Sahara] No meeting today

We are not having the Sahara meeting. Just a few announcements, we just got RC1 ready and please take a look at [1] and add topics for the PTG. Thanks, [1] https://etherpad.openstack.org/p/sahara-ptg-pike -- [image: Red Hat] Telles Nobrega | Software Engineer Red Ha

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

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. My approach > is to have a single confi

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

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 deployments are on MySQL - and what's more, the code is written

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

Thanks, Guang, for your valuable contributions. Henry > On 2 Feb 2017, at 05:13, Steve Martinelli wrote: > > 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 Gua

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

On Thu, Feb 2, 2017 at 10:33 AM, Mike Bayer wrote: > > > well, let me blow your mind and agree, but noting that this means, *we > drop SQLite also*. IMO every openstack developer should have > MySQL/MariaDB running on their machine and that is part of what runs if you > expect to run database-re

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

On Thu, Feb 02, 2017 at 04:27:51AM +, Dolph Mathews wrote: > What made most services jump +20% between mitaka and newton? Maybe there is > a common cause that we can tackle. 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 si

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 ___

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

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 deploym

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 vas

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 /etc/kolla/config/domains/keystone.$DOMAIN.conf in > order to be pushed to th

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

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] [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 see the entire set of not

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 look like. I'm all for actually get

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 deploym

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

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

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 i

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] [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] [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] [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 on to the differences > between the > > gate and w

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 C

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 beca

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 02

[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

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

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 to the differences > between the > > gate and what

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

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 a single worker is how we recommend > people >

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 week but think I messed it up by >> sending

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 meta

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

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 implementing this 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 https://review.openstack.org/#/c/422238/

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

[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

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 patch

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

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: > > > > > > > > > > > We definitely aren'

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 fu

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 end of day. > Would be g

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 migratio

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

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

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

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: > > > > > > > > > On 2 February 2017 at 08:40, Sean D

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

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

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: [email protected]: Kendra

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 conne

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 already merged. > > > >

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 done and pending merge f

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 and

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

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

  1   2   >