Re: [openstack-dev] [heat][tripleo] Heat memory usage in the TripleO gate during Ocata

On Fri, Jan 6, 2017 at 5:41 PM, Zane Bitter wrote: > On 06/01/17 16:58, Emilien Macchi wrote: >> >> On Fri, Jan 6, 2017 at 4:35 PM, Thomas Herve wrote: >>> >>> On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote: It's worth reiterating that TripleO still disables convergence in the

Re: [openstack-dev] [release] subscribe to the OpenStack release calendar

Awesome! 2017-01-07 4:19 GMT+08:00 Doug Hellmann : > > > On Jan 6, 2017, at 1:14 PM, Julien Danjou wrote: > > > > On Fri, Jan 06 2017, Doug Hellmann wrote: > > > > Hi Doug, > > > >> The link for the Ocata schedule is > >> https://releases.openstack.org/ocata/schedule.ics > >> > >> We will have a

[openstack-dev] [nova] Automatically disabling compute service on RBD EMFILE failures

A few weeks ago someone in the operators channel was talking about issues with ceph-backed nova-compute and OSErrors for too many open files causing issues. We have a bug reported that's very similar sounding: https://bugs.launchpad.net/nova/+bug/1651526 During the periodic update_available_r

[openstack-dev] Feature patches that need final +2

I've gone through the feature tracking etherpad again [1] and here are some patches that just need a final +2 to either close out the blueprint or get it close to being closed: 1. https://blueprints.launchpad.net/nova/+spec/add-os-xenapi-library Starts here: https://review.openstack.org/#/c/40

Re: [openstack-dev] [Performance] PTG?

Hey Andrey - Is there a shared etherpad for the Rally/Performance days? Thanks, Joe On Wed, Jan 4, 2017 at 11:01 AM, Andrey Kurilin wrote: > Hi, Joe! > > It is not a mistake. After a talk with Dina B., we decided to extend Rally > session for the wider > audience and I requested "Rally & Perform

Re: [openstack-dev] [nova] Feature patches that need final +2

On 1/7/2017 12:30 PM, Matt Riedemann wrote: I've gone through the feature tracking etherpad again [1] and here are some patches that just need a final +2 to either close out the blueprint or get it close to being closed: 1. https://blueprints.launchpad.net/nova/+spec/add-os-xenapi-library Start

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] [vitrage] how touseplaceholder vertex

Hi Yujun, A relationship is defined by the following trio: source id, target id and a label on the edge. In the processor, I add only edges that doesn't exists. Alexey From: Yujun Zhang [mailto:[email protected]] Sent: Thursday, January 05, 2017 4:32 PM To: OpenStack Development Mailing

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi Yujun, Thanks for the explanation, but I still don’t fully understand. Let me start with the current state: 1. introduce a flexible `metadata` dict in to ALARM entity [Ifat] Already exists. An alarm is represented as a vertex in the entity graph, with a dictionary of properties. 2.