Re: [openstack-dev] [Infra] Gerrit performance time

On 2017-01-12 08:09, Lenny Verkhovsky wrote: > +1 > > > > *From:*Gary Kotton [mailto:gkot...@vmware.com] > *Sent:* Thursday, January 12, 2017 9:05 AM > *To:* OpenStack List > *Subject:* [openstack-dev] [Infra] Gerrit performance time > > > > Hi, > > It

Re: [openstack-dev] [Infra] Gerrit performance time

+1 From: Gary Kotton [mailto:gkot...@vmware.com] Sent: Thursday, January 12, 2017 9:05 AM To: OpenStack List Subject: [openstack-dev] [Infra] Gerrit performance time Hi, It takes forever to access gerrit. Anyone else hitting this issue? Thanks Gary

[openstack-dev] [Infra] Gerrit performance time

Hi, It takes forever to access gerrit. Anyone else hitting this issue? Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

Thanks John, I would really appreciate if you could tag me on the reviews. I will do the same for mine too. Regards, Saravanan KR On Wed, Jan 11, 2017 at 8:03 PM, John Fulton wrote: > On 01/11/2017 12:56 AM, Saravanan KR wrote: >> >> Thanks Emilien and Giulio for your

Re: [openstack-dev] [nova] Feature review sprint on Wednesday 1/11

On 1/5/2017 7:05 PM, Matt Riedemann wrote: We agreed in the nova meeting today to hold a feature review sprint next Wednesday 1/11. It's about the end of the day for me here so I wanted to post that we got 5 features approved today during the review sprint. There are also several other

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

Sorry I could not attend meeting due to TZ. But from meeting logs, it looks like impression was(if am not wrong) that Tempest test[1] is not doing the right thing and should be ok to change. I do not think this is the case, Tempest test is doing what API tells/behave. Below is what test does: 1.

Re: [openstack-dev] [nova] The py35 functional nova CI job failures

Matt, Hoping this works - https://review.openstack.org/#/c/419250/ -- Dims On Wed, Jan 11, 2017 at 10:04 PM, Matt Riedemann wrote: > The gate-nova-tox-db-functional-py35-ubuntu-xenial job was recently added as > non-voting to the nova check queue but I see that it's

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

On 1/9/2017 8:11 AM, Armando M. wrote: I would like to think that I was able to exercise the influence on the goals I set out with my first self-nomination [2]. "just like nations are asked to keep their sovereign debt below a certain healthy threshold." I'm not sure which Utopia you're

[openstack-dev] [nova] The py35 functional nova CI job failures

The gate-nova-tox-db-functional-py35-ubuntu-xenial job was recently added as non-voting to the nova check queue but I see that it's got a 100% failure rate. These are the tests that are failing:

Re: [openstack-dev] [infra] placement job is busted in stable/newton (NO MORE HOSTS LEFT)

On 1/11/2017 8:18 PM, Matt Riedemann wrote: On 1/11/2017 9:19 AM, Jeremy Stanley wrote: If you look in the _zuul_ansible/scripts directory you'll see that shell script which exited nonzero is the one calling devstack-gate, so we've got something broken near the end of the job as you surmise. I

[openstack-dev] [neutron] networking-sfc stable/newton branch broken

Hi, Please have a look at [1]. The branch has been broken for some time now. Thanks, Armando [1] https://review.openstack.org/#/q/status:open+project:openstack/networking-sfc+branch:stable/newton __ OpenStack Development

Re: [openstack-dev] [infra] placement job is busted in stable/newton (NO MORE HOSTS LEFT)

On 1/11/2017 9:19 AM, Jeremy Stanley wrote: If you look in the _zuul_ansible/scripts directory you'll see that shell script which exited nonzero is the one calling devstack-gate, so we've got something broken near the end of the job as you surmise. I think it might be the post_test_hook:

Re: [openstack-dev] [infra] placement job is busted in stable/newton (NO MORE HOSTS LEFT)

On 1/11/2017 7:17 AM, Sylvain Bauza wrote: On a separate change, I also have the placement job being -1 because of the ComputeFilter saying that the service is disabled because of 'connection of libvirt lost' :

[openstack-dev] [Ceilometer] Unable to add new metrics using meters.yaml

Hi I was following the instructions @ http://docs.openstack.org/admin-guide/telemetry-data-collection.html#meter-definitions to add new meters to Ceilometer, but not able to make it work. I verified meters.yaml file in meter/data folder:

Re: [openstack-dev] [qa] glance issue at QA team meeting on 12 January

Thanks Brian. Update on meeting time, 12th Jan meeting will be at 0900 UTC. I just sent mail about meeting invite. ​-gmann On Thu, Jan 12, 2017 at 2:10 AM, Brian Rosmaita wrote: > Hello QA Team, > > There wasn't an agenda for 12 January on the

[openstack-dev] [QA] Meeting Thursday Jan 12th at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, Jan 12th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Sad to see u step down, thanks so much Armando for taking a "How can I help remove any roadblocks so we can move forward" approach to leadership. As part of a smaller project, ur support has certainly helped us make progress. Thanks Sridar PS: I was wondering if there will be a farewell

Re: [openstack-dev] [os-ansible-deployment] Periodic job in infra to test upgrades?

OK - with https://review.openstack.org/#/c/418521/ we have at least a working POC of what we can do. The issue is that we're running into the Zuul timeout. Depending on how quickly the AIO is built, we can get to the point where we run the upgrade script[2]. However in some runs we don't get to

Re: [openstack-dev] diskimage-builder Package grub-pc is not available error running on Fedora 25 AArch64

On 01/11/2017 03:06 PM, Andre Florath wrote: Hello! Looks that you are testing a somewhat uncommon combination ;-) Understood. I am working primarily with 64-bit ARM, so much of what I try may be uncommon (being a relatively new architecture). The error points into the direction that

Re: [openstack-dev] [infra][diskimage-builder] containers, Containers, CONTAINERS!

On Wed, Jan 11, 2017 at 04:04:10PM -0500, Paul Belanger wrote: > On Sun, Jan 08, 2017 at 02:45:28PM -0600, Gregory Haynes wrote: > > On Fri, Jan 6, 2017, at 09:57 AM, Paul Belanger wrote: > > > On Fri, Jan 06, 2017 at 09:48:31AM +0100, Andre Florath wrote: > > > > Hello Paul, > > > > > > > >

[openstack-dev] [nova] No cells meeting next week (Jan 18)

Hi all, There will be no cells meeting next week, Jan 18 2017. I'll be in the wilderness and nobody else was brave enough to run it in my absence. Yeah, something like that. --Dan __ OpenStack Development Mailing List (not

Re: [openstack-dev] diskimage-builder Package grub-pc is not available error running on Fedora 25 AArch64

Hello! Looks that you are testing a somewhat uncommon combination ;-) The error points into the direction that Ubuntu Xenial for arm does not supply a 'grub-pc' package [1]. Would be good if you could file a ticket. Kind regards Andre [1]

Re: [openstack-dev] [infra][diskimage-builder] containers, Containers, CONTAINERS!

On Sun, Jan 08, 2017 at 02:45:28PM -0600, Gregory Haynes wrote: > On Fri, Jan 6, 2017, at 09:57 AM, Paul Belanger wrote: > > On Fri, Jan 06, 2017 at 09:48:31AM +0100, Andre Florath wrote: > > > Hello Paul, > > > > > > thank you very much for your contribution - it is very appreciated. > > > > >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Hey Brandon, So couple comments to your mail. Kolla at it's core is community which took on preparing deployment of openstack using docker containers. This same community now is working with both ansible and k8s as means to deploy these containers. So far we're preserving that single community to

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Sure – you asked me and I thought you wanted an answer from me (which fits under the do not use OpenStack properties (i.e. this mailing list) for promotion of candidates email that Mark sent out). Others are able to answer in the broader Kolla community. Regards -steve From: "Brandon B.

[openstack-dev] [infra][diskimage-builder][glean] nodepool dsvm (non-voting) check jobs

Greetings, I'd like to mention we recently expanded our nodepool devstack jobs to include glean and diskimage-builder. Specifically, we now attempt to build, upload and SSH into DIBs produced by the jobs. You'll notice 2 jobs now: gate-dsvm-nodepool-debian-src-nv - ubuntu-precise -

Re: [openstack-dev] [tc][kolla] Adding new deliverables

I’m not entirely sure how the two relate, but anyone from Kolla can respond. Brandon B. Jozsa On January 11, 2017 at 2:49:07 PM, Steven Dake (stdake) (std...@cisco.com) wrote: Brandon, Your question is a mix of political and technical aspects that I am not permitted

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Brandon, Your question is a mix of political and technical aspects that I am not permitted to answer until Monday because of my parsing of this email from Mark Collier: http://lists.openstack.org/pipermail/foundation/2017-January/002446.html I will answer you Monday after the individual board

Re: [openstack-dev] [tc][kolla] Adding new deliverables

To your point Steve, then I’d image that Kolla would have no objection to the introduction of other Openstack-namespace projects that provide alternative image formats, integration choices, or orchestration variances for those in the larger community who do not want to use Kolla images. All of

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

Excerpts from Doug Hellmann's message of 2017-01-06 15:19:35 -0500: > > > 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 > >>

Re: [openstack-dev] [tc][kolla] Adding new deliverables

My sentiments exactly Michal. We’ll get there, but let’s not jump the gun quite yet. On 1/11/17, 1:38 PM, "Michał Jastrzębski" wrote: So from my point of view, while I understand why project separation makes sense in the long run, I will argue that at this moment it

[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 centos-master

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Doug, I apologize for not being able to reply inline. Bug in outlook. I am probably going to start posting/responding on the ml with my gmail account so I can properly communicate with ml. To your two points. I don’t want kolla to “own” all deployment with containers. I want kolla and

Re: [openstack-dev] [tc][kolla] Adding new deliverables

So from my point of view, while I understand why project separation makes sense in the long run, I will argue that at this moment it will be hurtful for the project. Our community is still fairly integrated, and I'd love to keep it this way a while longer. We haven't yet fully cleaned up mess that

Re: [openstack-dev] [nova] placement/resource providers update 7

On Fri, 6 Jan 2017, Chris Dent wrote: ## can_host, aggregates in filtering There's still some confusion (from at least me) on whether the can_host field is relevant when making queries to filter resource providers. Similarly, when requesting resource providers to satisfy a set of resources, we

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Steven Dake (stdake)'s message of 2017-01-11 14:50:31 +: > Thierry, > > I am not a big fan of the separate gerrit teams we have instituted inside the > Kolla project. I always believed we should have one core reviewer team > responsible for all deliverables to avoid not just

Re: [openstack-dev] [cinder] Deprecate Cinder Linux SMB driver

On Wed, Jan 11, 2017 at 05:28:16PM +, Lucian Petrut wrote: > Hi, > > We're planning to deprecate the Cinder Linux SMB driver. We're taking > this decision mostly because of its limitations and lack of demand, > unlike the Windows SMB driver which is largely adopted and the current > to-go

[openstack-dev] [cinder] Deprecate Cinder Linux SMB driver

Hi, We're planning to deprecate the Cinder Linux SMB driver. We're taking this decision mostly because of its limitations and lack of demand, unlike the Windows SMB driver which is largely adopted and the current to-go Cinder driver in Hyper-V deployments. We're going to mark it as

[openstack-dev] [keystone] 2017-1-11 policy meeting

Hey folks, In case you missed the policy meeting today, we had a good discussion [0] around incorporating keystone's policy into code using the Nova approach. Keystone is in a little bit of a unique position since we maintain two different policy files [1] [2], and there were a lot of questions

Re: [openstack-dev] 答复: [heat] glance v2 support?

Excerpts from Thomas Herve's message of 2017-01-11 08:50:19 +0100: > On Tue, Jan 10, 2017 at 10:41 PM, Clint Byrum wrote: > > Excerpts from Zane Bitter's message of 2017-01-10 15:28:04 -0500: > >> location is a required property: > >> > >>

Re: [openstack-dev] updating to pycryptome from pycrypto

-Original Message- From: Matthew Thode Reply: prometheanf...@gentoo.org , OpenStack Development Mailing List (not for usage questions) Date: January 11, 2017 at 04:53:41 To: OpenStack Development

[openstack-dev] [qa] glance issue at QA team meeting on 12 January

Hello QA Team, There wasn't an agenda for 12 January on the Meetings/QATeamMeeting page on the wiki, so I took the liberty of creating one. I added an item under the "Tempest" section to discuss a patch to modify a Glance test that is currently blocking a few Glance Ocata priorities (community

[openstack-dev] diskimage-builder Package grub-pc is not available error running on Fedora 25 AArch64

I am running Fedora 25 on a 64-bit ARM (AArch64) host, and tried testing the latest (F26) version of diskimage-builder, # cat /etc/redhat-release Fedora release 25 (Twenty Five) # rpm -q diskimage-builder diskimage-builder-1.26.1-1.fc26.noarch but I encountered an error with the

Re: [openstack-dev] [Congress] Installation/Deployment Docs

The reason we have devstack instructions under Users is because they are so easy and make it simple to test drive Congress. To test drive you need at least a couple of services besides Congress, which makes devstack a good fit. But maybe users don't care about install at all. Operators care about

Re: [openstack-dev] [openstack-ansible] Can someone run tomorrow's (2016-01-12) meeting for me?

On 01/11/2017 10:08 AM, Alexandra Settle wrote: > I can run the meeting tomorrow ☺ Thanks so much, Alex! :) -- Major Hayden __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all][ptls][goals] python3 devstack+functional tests

Team, To recap: * We have devstack/devstack-gate/tempest/rally have all gotten updates to support python 3.5 * We have a bunch of jobs already running as non-voting against master branches: gate-devstack-dsvm-py35-updown-ubuntu-xenial-nv gate-rally-dsvm-py35-cinder-nv

Re: [openstack-dev] [designate] Non Candidacy for PTL - Pike

Graham, We've been lucky to have you leading the project over the last few cycles. You've done really great work. I'll always appreciate you fighting for what you believed in and trying to make things better for everyone. I'll miss your heavy involvement on a professional and personal level.

Re: [openstack-dev] [openstack-ansible] Can someone run tomorrow's (2016-01-12) meeting for me?

Hey, I can run the meeting tomorrow ☺ Thanks, Alex On 1/11/17, 3:29 PM, "Major Hayden" wrote: Hey folks, A conflict came up and I won't be available to run tomorrow's weekly meeting in IRC. Would someone else be able to take over this meeting for me? --

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Steve, As a contributor to a kolla-* project, I disagree with your view that Kolla is not "themed". The more I work in the Kolla community, it's become apparent that Kolla is operating under the "Deploy containers" theme, and you state as much in your reply. I also disagree that separating the

[openstack-dev] [openstack-ansible] Can someone run tomorrow's (2016-01-12) meeting for me?

Hey folks, A conflict came up and I won't be available to run tomorrow's weekly meeting in IRC. Would someone else be able to take over this meeting for me? -- Major Hayden __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [infra] placement job is busted in stable/newton (NO MORE HOSTS LEFT)

On 2017-01-10 20:03:28 -0500 (-0500), Matt Riedemann wrote: > I'm trying to sort out failures in the placement job in stable/newton job > where the tests aren't failing but it's something in the host cleanup step > that blows up. > > Looking here I see this: > >

Re: [openstack-dev] [tripleo] Adding a LateServices ResourceChain

> 2. Do the list manipulation in puppet, like we do for firewall rules > > E.g see: > > https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/ceilometer-api.yaml#L62 > > https://github.com/openstack/puppet-tripleo/blob/master/manifests/firewall/service_rules.pp#L32 >

Re: [openstack-dev] 答复: [heat] glance v2 support?

On Wed, Jan 11, 2017 at 3:34 PM, Emilien Macchi wrote: > On Wed, Jan 11, 2017 at 2:50 AM, Thomas Herve wrote: >> I think this is going where I thought it would: let's not do anything. >> The image resource is there for v1 compatibility, but there is no >>

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Thierry, I am not a big fan of the separate gerrit teams we have instituted inside the Kolla project. I always believed we should have one core reviewer team responsible for all deliverables to avoid not just the appearance but the reality that each team would fragment the overall community

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

On 01/11/2017 08:24 AM, Emilien Macchi wrote: On Wed, Jan 11, 2017 at 9:21 AM, Emilien Macchi wrote: Greetings, OpenStack has been using reno [1] to manage release notes for a while now and it has been proven to be super useful. Puppet OpenStack project adopted it in

Re: [openstack-dev] 答复: [heat] glance v2 support?

On Wed, Jan 11, 2017 at 2:50 AM, Thomas Herve wrote: > On Tue, Jan 10, 2017 at 10:41 PM, Clint Byrum wrote: >> Excerpts from Zane Bitter's message of 2017-01-10 15:28:04 -0500: >>> location is a required property: >>> >>>

Re: [openstack-dev] [tripleo] Mistral Workflow for deriving THT parameters

On 01/11/2017 12:56 AM, Saravanan KR wrote: Thanks Emilien and Giulio for your valuable feedback. I will start working towards finalizing the workbook and the actions required. Saravanan, If you can add me to the review for your workbook, I'd appreciate it. I'm trying to solve a similar

Re: [openstack-dev] [sahara] PTL non-nomination

We really appreciate all the hard work that you've put into Sahara. And will be missed leading this project. Thanks. On Wed, Jan 11, 2017 at 11:03 AM, Vitaly Gridnev wrote: > Hello, > > PTL self-nomination period is going to start soon (see release schedule, > that is

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

On Wed, Jan 11, 2017 at 9:21 AM, Emilien Macchi wrote: > Greetings, > > OpenStack has been using reno [1] to manage release notes for a while > now and it has been proven to be super useful. > Puppet OpenStack project adopted it in Mitaka and since then we loved it. > The path

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

Greetings, OpenStack has been using reno [1] to manage release notes for a while now and it has been proven to be super useful. Puppet OpenStack project adopted it in Mitaka and since then we loved it. The path to use reno in a project is not that simple. People need to get used of adding a

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

On 06/01/17 16:58, Emilien Macchi wrote: It's worth reiterating that TripleO still disables convergence in the undercloud, so these are all tests of the legacy code path. It would be great if we could set up a non-voting job on t-h-t with convergence enabled and start tracking memory use over

Re: [openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

On 11/01/17 08:06 AM, William M Edmonds wrote: > > After discussing with my team, I think we will need to propose a revert. > The deprecation process was not followed correctly here. We will start > working on moving to panko, but we are not sure we can contain that for > Ocata. Please follow

[openstack-dev] [sahara] PTL non-nomination

Hello, PTL self-nomination period is going to start soon (see release schedule, that is Jan, 23) and I have an important announcement to make. I have to announce that I'm not going to run for PTL role for the Pike release, but I will continue my duties as a core reviewer of the project. For

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Armando, thank you very much for all the work you've done as PTL, my best wishes, and happy to know that you'll be around! Best regards, Miguel Ángel. On Wed, Jan 11, 2017 at 1:52 AM, joehuang wrote: > Sad to know that you will step down from Neutron PTL. Had several f2f

Re: [openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

On Wed, Jan 11 2017, William M Edmonds wrote: > After discussing with my team, I think we will need to propose a revert. > The deprecation process was not followed correctly here. We will start > working on moving to panko, but we are not sure we can contain that for > Ocata. Please follow the

Re: [openstack-dev] [infra] placement job is busted in stable/newton (NO MORE HOSTS LEFT)

Le 11/01/2017 02:03, Matt Riedemann a écrit : > I'm trying to sort out failures in the placement job in stable/newton > job where the tests aren't failing but it's something in the host > cleanup step that blows up. > > Looking here I see this: > >

Re: [openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

On 01/10/2017 09:26 AM, gordon chung wrote: > On 10/01/17 07:27 AM, Julien Danjou wrote: > > On Mon, Jan 09 2017, William M Edmonds wrote: > > > >> I started the conversation on IRC [5], but wanted to send this to the > >> mailing list and see if others have thoughts/concerns here and figure out

Re: [openstack-dev] [Openstack-operators] [nova] [placement] Which service is using port 8778?

On Tue, 10 Jan 2017, Mohammed Naser wrote: We use virtual hosts, haproxy runs on our VIP at port 80 and port 443 (SSL) (with keepalived to make sure it’s always running) and we use `use_backend` to send to the appropriate backend, more information here:

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Mehdi, I'd support switching g-r to make oslo.messaging work. period. This is dragged on way too long. Thanks, Dims On Wed, Jan 11, 2017 at 2:25 AM, Mehdi Abaakouk wrote: > The library final release is really soon, and we are still blocked on > this topic. If this is not

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Thierry Carrez wrote: > [...] > The fact that you're having hard discussions in Kolla about "adding new > deliverables" produced by distinct groups of people indicates that you > may be using Kolla as an old-style "program" rather than as a single > team. Why not set them up as separate project

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Michał Jastrzębski wrote: > I created CIVS poll with options we discussed. Every core member should > get link to poll voting, if that's not the case, please let me know. Just a quick sidenote to explain how the "big-tent" model of governance plays in here... In the previous project structure

Re: [openstack-dev] [cinder] [infra] drbdmanage is no more GPL2

Jeremy Stanley wrote: > On 2017-01-10 09:44:06 -0600 (-0600), Sean McGinnis wrote: > [...] >> It doesn't look like much has changed here. There has been one commit >> that only slightly modified the new license: [1] >> >> IANAL, and I don't want to make assumption on what can and can't be >> done,

[openstack-dev] updating to pycryptome from pycrypto

So, pycrypto decided to rename themselves a while ago. At the same time they did an ABI change. This is causing projects that dep on them to have to handle both at the same time. While some projects have migrated, most have not. A problem has come up where a project has a CVE (pysaml2) and the

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

I have just realized abstract alarm is not a good term. What I was talking about is *fault* and *alarm*. Fault is what actually happens, and alarm is how it is detected (or deduced). On Wed, Jan 11, 2017 at 5:13 PM Yujun Zhang wrote: > Yes, if we consider the Vitrage

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

Yes, if we consider the Vitrage scenario evaluator as a pseudo monitor. I think YinLiYin's idea is a reasonable requirement from end user. They care more about the *real faults* in the system, not how they are detected. Though it will bring much challenge to design and engineering, it creates

Re: [openstack-dev] [docs][badges][all] Docs gate broken for projects that include README.rst in docs

On 09/01/17 17:35 +0100, Flavio Percoco wrote: On 09/01/17 15:02 +0100, Andreas Jaeger wrote: On 2016-12-12 09:22, Flavio Percoco wrote: On 11/12/16 13:32 +0100, Flavio Percoco wrote: On 09/12/16 17:20 +0100, Flavio Percoco wrote: Greetings, Some docs jobs seem to be broken by the latest

[openstack-dev] [tricircle]weekly meeting of Jan.11

Hello, team, Agenda of Jan.11 weekly meeting: 1. Ocata release preparation 2. shadow_agent for VxLAN L2 networking/L3 DVR issue 3. shared_vlan confusion when creating vlan network in some specified region 4. Open Discussion How to join: # IRC meeting:

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

You are right. But as I see it, the case of Vitrage suspect vs. the real Nagios alarm is just one example of the more general case of two monitors reporting the same alarm. Don’t you think so? From: Yujun Zhang Reply-To: "OpenStack Development Mailing List (not for