[openstack-dev] [machine learning] Question: Why there is no serious project for machine learning ?

Hi, all, I'm wondering if there is a serious project for machine learning in Openstack ? For us to easily build a model in industrial operational level. Thanks, Andy Yan __ OpenStack Development Mailing List (not for usage

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

Hi, Root Causers In the implementation of static driver unit test, the most difficult part I've encountered is the mock driver and trace generator. Is there any particular reason to put all mock driver and transformer specs in the same file `trace_generator.py` and `mock_driver.py`? Would it be

Re: [openstack-dev] [neutron] Confusion around the complexity

Kevin Benton wrote: If you don't want users to specify network details, then use the get me a network extension or just have them boot to a public (or other pre-created) network. In your thought experiment, why is your iPhone app developer not just using a PaaS that handles instance scaling,

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Jan. 13 2017

Sorry for providing the agenda late. 1) Roll Call 2) OPNFV: Daisy CI Progress 3) OPNFV: Daisy Support Escalator 4) OpenStack: Kolla Image Versioning 5) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for

[openstack-dev] [ocatvia]Newton Octavia multinode setup

Hi all, Is there any documentation or ansible playbook to install octavia on multi-node or all-in-one setup? I am trying to setup in my lab but not able to find any documentation. Thanks, Santhosh __ OpenStack Development

Re: [openstack-dev] [neutron] Confusion around the complexity

If you don't want users to specify network details, then use the get me a network extension or just have them boot to a public (or other pre-created) network. In your thought experiment, why is your iPhone app developer not just using a PaaS that handles instance scaling, load balancing and HA?

Re: [openstack-dev] [neutron] Confusion around the complexity

Sean M. Collins wrote: Joshua Harlow wrote: So I don't want to start to much of a flame-war and am really just trying to understand things that may be beyond me (so treat me nicely, ha). The basic question that I've been wondering revolves around the following kind of 'thought experiment' that

Re: [openstack-dev] [neutron] Confusion around the complexity

Joshua Harlow wrote: > So I don't want to start to much of a flame-war and am really just trying to > understand things that may be beyond me (so treat me nicely, ha). > > The basic question that I've been wondering revolves around the following > kind of 'thought experiment' that asks something

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

hi, On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: > Hi > > As of today, the project neutron-vpnaas is no longer part of the neutron > governance. This was a decision reached after the project saw a dramatic > drop in active development over a prolonged period of time. >

[openstack-dev] [kolla] Adding jeffrey4l to kolla-kubernetes-core because he is release liason

We are busily releasing 0.4.0 of the Kolla deliverable kolla-kubernetes and have determined we can’t release the kolla-kubernetes milestone without the release liaison for Kolla being on the core reviewer sub-team to make last minute fine tuning adjustments to the release and approve other

Re: [openstack-dev] [tripleo] TripleO Squads - What's next?

On Fri, Nov 25, 2016 at 12:51 PM, Emilien Macchi wrote: > I'm happy to announce we officially accepted TripleO Squads in our project: > http://specs.openstack.org/openstack/tripleo-specs/specs/policy/squads.html > > We hope it will help us to scale our team and improve our way

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

(Top-posting, don't bother digging through for more.) We're following the tempest HACKING.rst procedure. The patch for step #2 is: https://review.openstack.org/#/c/419658/ Please review at your earliest convenience. thanks, brian On 1/12/17 3:34 PM, Brian Rosmaita wrote: > Ken, > > Thanks

[openstack-dev] [all] [goals] proposing a new goal: "Control Plane API endpoints deployment via WSGI"

Greetings OpenStack community, I have been looking for a Community Goal [1] that would directly help Operators and I found the "run API via WSGI" useful. So I've decided to propose this one as a goal for Pike but I'll stay open to postpone it to Queen if our community thinks we already have too

Re: [openstack-dev] [release] Release countdown for week R-5, Jan 16-20

Hello, Doug, One question, according to the guide for self-branch[1], the Ocata stable branch should be created for RC1 tag for projects using the cycle-with-milestone release model. The date for RC1 one is Jan 30 - Feb 03 according to the schedule [2]. Tricircle is one big-tent project with

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

On Fri, Jan 13, 2017 at 4:32 AM, Ken'ichi Ohmichi wrote: > 2017-01-12 5:47 GMT-08:00 Brian Rosmaita : > > On 1/11/17 10:35 PM, GHANSHYAM MANN wrote: > > > >> But from meeting logs, it looks like impression was(if am not wrong) > that > >>

[openstack-dev] What's Up, Doc? 13 January

Hi everyone, Welcome to 2017. I hope you all had a chance to rest up a little before we hurtle straight into another release, as Ocata is now only 40 days away! I'll be in contact with our lovely release managers Brian and Mariia over the next week or so to kick off release management tasks.

Re: [openstack-dev] [neutron] Confusion around the complexity

Actually we have a single call create for load balancers[1], so I think that addresses Josh's concern about complexity in the number of required calls. As for the complexity of the "concept" of a load balancer, I think we have improved that greatly with the LBaaSv2 API. That said, if there are

Re: [openstack-dev] [neutron] Confusion around the complexity

On Thu, Jan 12, 2017 at 3:46 PM, Joshua Harlow wrote: > So I don't want to start to much of a flame-war and am really just trying to > understand things that may be beyond me (so treat me nicely, ha). > > The basic question that I've been wondering revolves around the

[openstack-dev] [neutron] Is anybody using the "next_hop" field in FIP association update notifications?

Hi all, In reviewing the change [1], the question arose as to whether any project other than neutron-dynamic-routing has been using the "next_hop" field included in a callback notification emitted when FIP association is updated [2]. The question as to whether to deprecate or simply remove

Re: [openstack-dev] [neutron] Confusion around the complexity

On 01/12/2017 04:46 PM, Joshua Harlow wrote: So I don't want to start to much of a flame-war and am really just trying to understand things that may be beyond me (so treat me nicely, ha). The basic question that I've been wondering revolves around the following kind of 'thought experiment' that

Re: [openstack-dev] [neutron] Confusion around the complexity

On 12 January 2017 at 15:07, Armando M. wrote: > > > On 12 January 2017 at 14:46, Joshua Harlow wrote: > >> So I don't want to start to much of a flame-war and am really just trying >> to understand things that may be beyond me (so treat me nicely, ha).

Re: [openstack-dev] [neutron] Confusion around the complexity

On 12 January 2017 at 14:46, Joshua Harlow wrote: > So I don't want to start to much of a flame-war and am really just trying > to understand things that may be beyond me (so treat me nicely, ha). > > The basic question that I've been wondering revolves around the

[openstack-dev] [neutron] Confusion around the complexity

So I don't want to start to much of a flame-war and am really just trying to understand things that may be beyond me (so treat me nicely, ha). The basic question that I've been wondering revolves around the following kind of 'thought experiment' that asks something along the lines of: """

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

On a freshly stacked devstack (Jan 12), attempting to access `cfg.CONF.keystone_authtoken.project_domain_name` gave the error: NoSuchOptError: no such option project_domain_name in group [keystone_authtoken] I¹m a little confused because it¹s part of the [keystone_authtoken] config section

Re: [openstack-dev] Consistent Versioned Endpoints

On Thu, Jan 12, 2017 at 12:35 PM, Scott D'Angelo wrote: > Can we get to this "perfect world"? Let's discuss at the PTG. > It is my understanding that we do not have the ability to schedule a time or > room for such a cross-project discussion. Please chime in if

Re: [openstack-dev] [networking-sfc] Limitation on port chains + flow classifiers

This clash check was added on purpose to avoid the ambiguity of the following scenario (This is just one of many similar scenarios): VM2, VM3 hosted on Int-Bridge1 of Server1 VM4 hosted on Int-Bridge2 of Server2 VM5 hosted on Int-Bridge3 of Server3 Chain1: VM1, VM2, VM4 Chain2: VM1, VM3, VM5

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

Hello! > The end result of this would be we have distro-minimal which depends on > kernel, minimal-userspace, and yum/debootstrap to build a vm/baremetal > capable image. We could also create a distro-container element which > only depends on minimal-userspace and yum/debootstrap and creates a >

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

Ken, Thanks for the quick response ... we'll follow the procedure outlined in the tempest HACKING.rst that you pointed out. cheers, brian On 1/12/17 2:32 PM, Ken'ichi Ohmichi wrote: > 2017-01-12 5:47 GMT-08:00 Brian Rosmaita : >> On 1/11/17 10:35 PM, GHANSHYAM MANN

Re: [openstack-dev] [ironic] Stepping down as PTL after this cycle

Jim, (Now that the shock has worn off). Thanks for being such a great PTL. I very much appreciated what you did/do as PTL! And welcome back to the land of coding, etc. :) --ruby From: Jim Rollenhagen Reply-To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

>From my point of view, i've been using that either on infra with puppet-infracloud, glean.. and now with TripleO. So in my opinion, it shall be an independent project, with core contributors from both sides. On Thu, Jan 12, 2017 at 8:51 PM, Paul Belanger wrote: > On Thu,

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

This is awesome! I pretty much just 'Select All' deleted my other calendars I use for tracking this kind of information. Thank you, Doug! On Thu, Jan 12, 2017 at 12:41 PM, Emilien Macchi wrote: > On Wed, Jan 11, 2017 at 1:51 PM, Doug Hellmann >

[openstack-dev] Mapping Launchpad to Storyboard

Hello All! The storyboard team has created another blog post to help you learn how some of the more utilized capabilities of launchpad work in Storyboard so please take a look! [1] And if you missed our previous post discussing why we want to move to Storyboard please take a look at that too

Re: [openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

On Thu, Jan 12, 2017 at 02:11:42PM -0500, James Slagle wrote: > On Thu, Jan 12, 2017 at 1:55 PM, Emilien Macchi wrote: > > On Thu, Jan 12, 2017 at 12:06 PM, Paul Belanger > > wrote: > >> Greetings, > >> > >> With the containerization[1] of tripleo, I'd

[openstack-dev] [nova] Unit tests for a review

Hi I am looking into writing unit tests for a review https://review.openstack.org/#/c/387687/ Basically it modifies the deallocate for instance function to only deallocate ports to which this instance is bound to So this is more like a scenario test where the port is unbound outside of nova.

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

2017-01-12 5:47 GMT-08:00 Brian Rosmaita : > On 1/11/17 10:35 PM, GHANSHYAM MANN wrote: > >> 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

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

Hello Ken'ichi and the QA Team, Sorry about the confusion over today's meeting time. All I was going to say at the meeting was it would be great if some core reviewers could take a look at the glance tempest patch, https://review.openstack.org/#/c/414261/. I realize that you give each patch all

Re: [openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

On Thu, Jan 12, 2017 at 1:55 PM, Emilien Macchi wrote: > On Thu, Jan 12, 2017 at 12:06 PM, Paul Belanger wrote: >> Greetings, >> >> With the containerization[1] of tripleo, I'd like to know more about the >> future of >> diskimage-builder as it relates

Re: [openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

On Thu, Jan 12, 2017 at 12:06 PM, Paul Belanger wrote: > Greetings, > > With the containerization[1] of tripleo, I'd like to know more about the > future of > diskimage-builder as it relates to the tripleo project. > > Reading the recently approved spec for containers,

Re: [openstack-dev] [nova][keystone][cinder] Quota Implementation

Dear All, Quota as service or library .IMHO we have to fix one of the methods, so that we can go ahead with the implementation. best regards, sajeesh From: Sajeesh Cimson Sasi

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

On Wed, Jan 11, 2017 at 1:51 PM, Doug Hellmann wrote: > 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,

[openstack-dev] Consistent Versioned Endpoints

TL;DR: Let's discuss Version Discovery and Endpoints in the Service Catalog at the PTG in Atlanta. The topic of Versioning and the Endpoints discovered in the Service Catalog was discussed in today's API Working Group Meeting[1]. A previous ML post[2] claimed: In a perfect world, every endpoint

[openstack-dev] [release] Release countdown for week R-5, Jan 16-20

Focus - Feature work and major refactoring should be starting to wrap up as we approach the third milestone and various feature and release freeze dates. The deadline for non-client library releases is Thursday 19 Jan. We do not grant Feature Freeze Extensions for any libraries, so that is a

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

On 01/09/2017 05:29 AM, Chris Dent wrote: On Fri, 6 Jan 2017, Chris Dent wrote: * CORS support in placement API: https://review.openstack.org/#/c/392891/ This is one we should probably get in in Ocata because it enables the sole piece of configurability that is present in the WSGI

[openstack-dev] [neutron] Neutron Pike PTG

Hi neutrinos, The time for the PTG is approaching and if you are wondering about topics and various agenda arrangements, you should consider the PTG more like a mid-cycle on steroids: each project will be working on its own agenda, usually via etherpads, and publish updates over the ML, up until

Re: [openstack-dev] [networking-sfc] Limitation on port chains + flow classifiers

Thanks Bernard, Louis, IRC meeting, Given the encapsulation requirement when having SFC Graphs, there is then no need to call flowclassifier_basic_conflict() for the said graphs. I will see how to avoid calling flowclassifier_basic_conflict() specifically when creating graphs of port chains.

[openstack-dev] [trove][ptg] Pike PTG Etherpad

trove now has an etherpad for listing its PTG topics: https://etherpad.openstack.org/p/trove-pike-ptg-topics You can find it listed on the PTG Pike Etherpads wiki: https://wiki.openstack.org/wiki/PTG/Pike/Etherpads Feel free to add topics, Thanks! Trevor

Re: [openstack-dev] [all] New deadline for PTG Travel Support Program

Thierry, Thanks! As an independent contributor, it can be really hard to finance these international trips, especially when there is no commercial element. It is therefore really great, and appreciated, that you have extended this program from the Summit to cover the PTG. Cheers, Pete On Thu,

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Exciting meeting today, lots of people, lots of discussion[0]. We started out talking about the service-types-authority[4] and whether the api-wg should be more directly involved in it. Since there's a fair bit of overlap between participants in both groups, we

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary

On Thu, Jan 12, 2017 at 12:26 PM, Attila Darazs wrote: > We had our first meeting as the the CI Squad today. We re-purposed our > "Quickstart to Upstream Transitioning" meeting into the Squad meeting, so > the topics were and will be focused on the transition for the next

[openstack-dev] [tripleo] CI Squad Meeting Summary

We had our first meeting as the the CI Squad today. We re-purposed our "Quickstart to Upstream Transitioning" meeting into the Squad meeting, so the topics were and will be focused on the transition for the next month or so. Everybody interested in the TripleO CI and Quickstart is welcome to

[openstack-dev] [tripleo][diskimage-builder] Status of diskimage-builder

Greetings, With the containerization[1] of tripleo, I'd like to know more about the future of diskimage-builder as it relates to the tripleo project. Reading the recently approved spec for containers, container (image) builds are no longer under the control of tripleo; by kolla. Where does

Re: [openstack-dev] [kolla] Problem in Ubuntu check when building Kolla base image

On 2017-01-12 15:02:32 - (-), Edmund Rhudy (BLOOMBERG/ 120 PARK) wrote: [...] > 2) I don't know why the OSIC Ubuntu mirror is unsigned. I feel > like it should be a straight clone of Canonical's repos so that > the baked-in signing key for the Ubuntu base image will just work, > but

[openstack-dev] [all] New deadline for PTG Travel Support Program

Hi everyone, The PTG Travel Support Program helps contributors that are not otherwise funded to join their team gathering at the Project Teams Gathering. See http://www.openstack.org/ptg#tab_travel for more explanations. The Travel Support Program applications were organized in two phases, and

[openstack-dev] [openstack-ansible] CI/CD and Openstack deployment

Hey everyone, I am wondering how people are running CI/CD solutions for deploying and maintaining their Openstack Environments? I see the description for live upgrading from OSIC (https://osic.org/blogs/live-upgrade-openstack), but am intrigued by how others have set up their environments.

Re: [openstack-dev] [kolla] Problem in Ubuntu check when building Kolla base image

On Thu, Jan 12, 2017 at 03:02:32PM -, Edmund Rhudy (BLOOMBERG/ 120 PARK) wrote: > Here at Bloomberg, we're evaluating Kolla to replace our in-house OpenStack > deployment system, and one of our requirements is that we be able to do our > builds without touching the Internet - everything

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

Thierry, Cool thanks for the leeway here ☺ I agree wholeheartedly with your last sentiment. If an existing Kolla sub-team or an existing project (e.g. the Puppet team) in OpenStack or a new project wants to use Kolla images and feels they would operate more effectively without the structure

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

On 4.1.2017 09:13, Saravanan KR wrote: Hello, The aim of this mail is to ease the DPDK deployment with TripleO. I would like to see if the approach of deriving THT parameter based on introspection data, with a high level input would be feasible. Let me brief on the complexity of certain

[openstack-dev] [octavia]redirection and barbican config

Hi, Please consider the bug: https://bugs.launchpad.net/devstack/+bug/1655656 Thanks, Abed Abu dbai __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [networking-sfc] Limitation on port chains + flow classifiers

On 10 January 2017 at 14:13, Duarte Cardoso, Igor wrote: > Hi networking-sfc, > > > > While working on the SFC Graphs patch, I observed the following limitation > when creating port-chains: http://paste.openstack.org/show/594387/. > > > > My objective was to have 2

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

Hi, Ifat You comments is quite right. See my additional explanation inline. On Thu, Jan 12, 2017 at 5:12 PM Afek, Ifat (Nokia - IL) wrote: > > > One possible solution would be introducing a high level (abstract) > template from users view. Then convert it to Vitrage

[openstack-dev] [TripleO][Mistral][Ansible] Calling Ansible from Mistral workflows

Hey all, I just wanted to share a quick experiment that I tried out. I had heard there was some interest in native Ansible actions for Mistral. After much dragging my heels I decided to give it a go, and it turns out to be very easy. This code is very raw and has only been lightly tested - I

[openstack-dev] [kolla] Problem in Ubuntu check when building Kolla base image

Here at Bloomberg, we're evaluating Kolla to replace our in-house OpenStack deployment system, and one of our requirements is that we be able to do our builds without touching the Internet - everything needs to come from locally hosted repositories. A few weeks ago, I pushed up a PR

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

Hi Sean, Great to see you taking the initiative on this. I think the starting point we’d have to work from with the way the builds are executed now would be to have the upgrade job execute in a periodic pipeline that has a longer timeout. While it would be ideal to do on-commit tests it’s

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

On 2017-01-11 20:40:26 -0600 (-0600), Matt Riedemann wrote: [...] > Well I guess it's less sinister than all that, it was just a matter of when > the nova change landed, which was meant for newton but happened in Ocata: [...] Oh, good catch! I didn't even think to check whether that hook existed

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

On 1/11/17 10:35 PM, GHANSHYAM MANN wrote: > Sorry I could not attend meeting due to TZ. I wound up missing the meeting, too; I thought it was at 17:00 UTC. > 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

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

-Original Message- From: Ian Cordasco Reply: Ian Cordasco Date: January 11, 2017 at 11:09:11 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] updating to

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

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

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

On 11/01/17 10:01, Thomas Herve wrote: 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

[openstack-dev] [tripleo] Reminder: TripleO deep dive "how to contribute to the tripleo ui" starts in 2 hours

Hope to see many of you there! https://etherpad.openstack.org/p/tripleo-deep-dive-ui -- Regards, Ana Krivokapic Senior Software Engineer OpenStack team Red Hat Inc. __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

On Thu, Dec 1, 2016 at 1:02 AM, Armando M. wrote: > > > On 27 November 2016 at 20:50, Takashi Yamamoto > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: >> > Hi >> > >> > As of today, the project neutron-vpnaas is no

Re: [openstack-dev] How change a section name in oslo.config but keep compatibility with the old format

Thanks jordan for the quick answer, it looks interesting. I forgot a detail: the section name is defined when registering options with the cfg.CONF.register_opts method. -- Maxime Cottret - Consultant Cloud/DataOps @ OBJECTIF-LIBRE Mail : maxime.cott...@objectif-libre.com Tel : 05 82 95 65

Re: [openstack-dev] How change a section name in oslo.config but keep compatibility with the old format

Hi, Look at this file https://github.com/openstack/tempest/blob/master/tempest/config.py and search for "deprecated_opts" Not sure you can deprecate a whole section, but you can set the old location (old section/old config name) for each new config option. On Thu, Jan 12, 2017 at 11:01 AM,

[openstack-dev] How change a section name in oslo.config but keep compatibility with the old format

Hi every one, I'm a new developer on Cloudkitty project and I was wondering how I can depreciate a section name in oslo.config. I'd like to rename a section for consistency and depreciate the old name before removing its use in the next cycle. I've looked into oslo.config documentation

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

On 12 January 2017 at 03:28, Armando M. wrote: > 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 Indeed, it needs

Re: [openstack-dev] [nova] Inconsistency of parameter type in Nova API Reference

On 2017/01/10 20:35, Sean Dague wrote: On 01/10/2017 01:39 AM, Takashi Natsume wrote: Hi Nova developers. In Nova API Reference(*1), the following parameters' values are 'null' in HTTP request body samples. And their parameter types are defined as 'string'. * 'confirmResize' parameter in

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

Hi Yujun, See my comments inline. Ifat. From: Yujun Zhang Date: Wednesday, 11 January 2017 at 12:12 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

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

Hi Srikanth, As U've noticed those meters are derived from notifications emitted by other OpenStack services. So please check that 'cord.dns.cache.size' events are processed correctly. Also, the last sentences from the guide: ''' These meters are not loaded by default.  To load these meters,

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

On 11/01/17 16:01 +0100, Thomas Herve wrote: 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