Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

Apoorva, Sean, after some time i managed to bring up Quobyte CI last friday which tested fine [1,2,3] for a short time and then ran into the same issues with manage_snapshot related tempest tests Apoorva describes (Starting chronologically at [4]). >From here i see two steps: a) look into the

Re: [openstack-dev] [kolla] kolla-build building images that are known not to work for a given base/type

Hello David. Sounds reasonable. I transferred your mail into a Launchpad bug: https://bugs.launchpad.net/kolla/+bug/1656753 Christian. -- Christian Berendt Chief Executive Officer (CEO) Mail: bere...@betacloud-solutions.de Web: https://www.betacloud-solutions.de Betacloud Solutions GmbH

Re: [openstack-dev] [congress][oslo.config][keystone] NoSuchOptError: no such option project_domain_name in group [keystone_authtoken]

Did you search keyword in http://codesearch.openstack.org/. Hope that will help you. 2017-01-13 6:31 GMT+08:00 Eric K : > On a freshly stacked devstack (Jan 12), attempting to access > `cfg.CONF.keystone_authtoken.project_domain_name` gave the > error: NoSuchOptError:

Re: [openstack-dev] [kuryr] Ocata cycle ending and proposing new people as Kuryr cores

+1 for both. On Sun, Jan 15, 2017 at 12:42 PM, Gal Sagie wrote: > +1 for both. > > On Sun, Jan 15, 2017 at 9:05 AM, Irena Berezovsky > wrote: > >> >> >> On Fri, Jan 13, 2017 at 6:49 PM, Antoni Segura Puimedon < >> celeb...@gmail.com> wrote: >> >>> Hi

[openstack-dev] Patch for Eventlet so it will work IPv6 only, autodects ::1 etc

Hi! For when 127.0.0.1 is not there, soon to be. Roots out one last piece of IPv4 only in openstack. Please find patch attached. Thoughts please about approach. Github repo is here: https://github.com/grantma/deb-python-eventlet/tree/full-ipv6-defaults Thank you! Best Regards, Matt Grant

[openstack-dev] [tripleo] tripleoclient release : January 19th

https://releases.openstack.org/ocata/schedule.html It's time to release python-tripleoclient this week. We still have 15 bugs in progress targeted for ocata-3. https://goo.gl/R2hO4Z Please triage them to pike-1 unless they are critical or high, so we need to fix them afterward and backport it to

Re: [openstack-dev] [tripleo] Release notes in TripleO

On Sun, Jan 15, 2017 at 1:29 PM, wrote: > Does that applies to drivers also? It applies to every projects mentioned in the list, features / bugs related to drivers included. > -Original Message- > From: Ben Nemec [mailto:openst...@nemebean.com] > Sent:

Re: [openstack-dev] [nova][puppet][tripleo][kolla][fuel] Let's talk nova cell v2 deployments and upgrades

On 1/13/2017 6:56 PM, Matt Riedemann wrote: On 1/13/2017 2:05 PM, Matt Riedemann wrote: Documenting this is going to be a priority. We should have something up for review in Nova by next week (like Monday), at least a draft. Dan Smith has a start on the docs here:

Re: [openstack-dev] [RDO][DLRN] DLRN worker downtime during the weekend

> Hi RDO, > > We need to run some maintenance operations on the DLRN instance next weekend, > starting on Friday 13 @ 19:00 UTC. These are required to reduce the storage > usage of the master and newton workers. The impact is: > > - During the weekend, no new packages will be processed for the

[openstack-dev] [TripleO][CI]

Hi, all FYI, the periodic TripleO nonha jobs fail because of introspection failure, there is opened bug in mistral: Ironic introspection fails because unexpected keyword "insecure" https://bugs.launchpad.net/tripleo/+bug/1656692 and marked as promotion blocker. Thanks -- Best regards Sagi

Re: [openstack-dev] [Cinder] Marking Tintri driver as unsupported

Sean, We have resolved issues related to our CI infra[1][2]. At this point manage_snapshot related tempest tests (2) are failing, but Tintri driver does not support manage/unmanage snapshot functionalities. Could you please assist me on how to skip these tests? We are using sos-ci for our CI

Re: [openstack-dev] [tripleo] Release notes in TripleO

Does that applies to drivers also? -Original Message- From: Ben Nemec [mailto:openst...@nemebean.com] Sent: Wednesday, January 11, 2017 8:49 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tripleo]

Re: [openstack-dev] [heat][TripleO] Adding interfaces to environment files?

On 8.6.2016 11:15, Steven Hardy wrote: On Tue, Jun 07, 2016 at 03:57:31PM -0400, Jay Dobies wrote: All, We've got some requirements around adding some interfaces to the heat environment file format, for example: 1. Now that we support passing un-merged environment files to heat, it'd be

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

About fault and alarm, what I was thinking about the causal/deducing chain in root cause analysis. Fault state means the resource is not fully functional and it is evaluated by related indicators. There are alarms on events like power loss or measurands like CPU high, memory low, temperature

Re: [openstack-dev] [release][ptl] not planning to serve as release PTL for Pike

On Fri, Jan 13, 2017 at 03:00:17PM -0500, Doug Hellmann wrote: > I announced this at the release team meeting on 6 Jan, but thought > I should also post to the list as well: I do not plan to serve as > the Release Management team PTL for the Pike release cycle. > > It has been my pleasure to

[openstack-dev] bug #1655656

Hi, I updated the description accordingly https://bugs.launchpad.net/devstack/+bug/1655656 Thanks, Abed __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [vitrage] code organization for trace generator and

I heard the exrex story from Elisha, though I didn't quite understand the rule of allowed library in OpenStack. I have also kept it in static datasource, but it was not so convenient to jump over these long files to find the static datasource related function On Sun, Jan 15, 2017 at 5:24 PM

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

Hi Yinliyin, There are two use cases: One is yours, where you have a single monitor that generates “real” alarms, and Vitrage that generates deduced alarms. Another is where someone has a few monitors, and there might be a collision/equivalence between their alarms. The solution that you

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

From: Yujun Zhang Date: Thursday, 12 January 2017 at 17:37 On Thu, Jan 12, 2017 at 5:12 PM Afek, Ifat (Nokia - IL) > wrote: 'deduced' vs 'monitored' would be good enough for most cases. Unless we have identify some real

Re: [openstack-dev] [vitrage] code organization for trace generator and

Hi Yujun, The motivation in building the mocks this way was that we could easily generate a series of events which are different from one another. There used to be a distinction between ‘static fields’ and ‘dynamic fileds’, and a library named exrex was used to generate random values by regex

Re: [openstack-dev] [Octavia] - LBaaS and IPv6

Yes. On Sun, Jan 8, 2017 at 2:07 PM, Alex Stafeyev wrote: > Hi, > Does lbaas support LB in ipv6 network? > > tnx > > -- > Alexander Stafeyev > QE Engineer, Neutron, Openstack > Red Hat > > > __