Re: [openstack-dev] [aodh] Tempest gate not working

2016-05-24 Thread Ryota Mibu
Hi Tony, That '' is not good for tempest jobs. DEVSTACK_GATE_TEMPEST is set 0 in that script, and default one seems better (devstack-gate/ . BR, Ryota > -Original Message- > From: Tony Breeds

Re: [openstack-dev] [aodh] Tempest gate not working

2016-05-24 Thread Ryota Mibu
Julien, Thank you for the heads up. I'll check aodh tempest tests, and also drop tempest full tests in ceilometer since the code for ceilometer was removed from tempest. BR, Ryota > -Original Message- > From: Julien Danjou [] > Sent: Tuesday, May 24, 2016

Re: [openstack-dev] [aodhclient] does the aodh have the feature for import/export batch alarms?

2016-05-19 Thread Ryota Mibu
Hi, I also agree with ZhiQiang. How about using Heat Template which improve portability of app and configs? Cheers, Ryota > -Original Message- > From: ZhiQiang Fan [] > Sent: Friday, May 20, 2016 11:42 AM > To: > Cc: OpenStack

Re: [openstack-dev] [Openstack] [AodhClient] "composite alarm" unit test missing in aodhclient ?

2016-05-19 Thread Ryota Mibu
Agree, we should have it. Could you propose the change, adding liusheng as a reviewer? He made this composite alarm and can check your patch properly. /Ryota > -Original Message- > From: [] > Sent: Thursday, May 19, 2016 5:36 PM > To:

Re: [openstack-dev] [Openstack] [AodhClient] "composite alarm" unit test missing in aodhclient ?

2016-05-19 Thread Ryota Mibu
Hi, The test case you pointed is for threshold alarm, so it is OK and expected that "composite_rule" is None. Checking test codes is good idea. You can add new tests when you found something missing by posting new patch. BR, Ryota > -Original Message- > From:

Re: [openstack-dev] [Openstack] [Aodh] add "meter-list" command in Aodh CLI

2016-05-17 Thread Ryota Mibu
Hi, We shouldn't have 'meter-list' in aodhclient. Nova have API and function to show image list, and 'nova image-list' is talking to nova, not glance. It would be strange if '$ aodh meter-list' (aodhclient) made request to ceilometer. On the other hand, I understand your concern. We can

[openstack-dev] [ceilometer][tempest] disabling 'full' tempest tests for ceilometer changes in CI

2016-04-12 Thread Ryota Mibu
Hi, Can we disable 'full' tempest tests for ceilometer? - gate-tempest-dsvm-ceilometer-mongodb-full - gate-tempest-dsvm-ceilometer-mysql-full - gate-tempest-dsvm-ceilometer-mysql-neutron-full - gate-tempest-dsvm-ceilometer-postgresql-full -

Re: [openstack-dev] [tempest] clients/manager in plugins

2015-12-16 Thread Ryota Mibu] > Sent: Saturday, December 12, 2015 11:32 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [tempest] clients/manager in plugins > > Hi Ryota, > > That is the one way as you mentioned. > > On Fri, Dec 11,

[openstack-dev] [tempest] clients/manager in plugins

2015-12-11 Thread Ryota Mibu
]. But, if there is a better approach to do the similar thing, please let me know. [1] [2] Thanks, Ryota --- "Ryota Mibu" <>

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

2015-12-08 Thread Ryota Mibu
Hi Ifat, > > Can we clarify use case again in terms of service role definition? > > Our use cases focus on giving value to the cloud admin, who will be able to: > > - view the topology of his environment, the relations between the physical, > virtual and applicative layer and the > statuses

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

2015-12-03 Thread Ryota Mibu
Hi Ifat, > > > Let me see if I got this right: are you suggesting that we create > > > on-the-fly alarm definitions with no alarm_actions, for every > > > deduced > > alarm that we want to raise? And this will spare us the extra alarm > > evaluation in AODH? > > > > Yes. But, please note that

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

2015-12-03 Thread Ryota Mibu
Hi Ifat, > > One approach we can take, is that you configure aodh to pass each row > > event (e.g. each VM downed) wrapped in alarm notification to vitrage, > > then do some operation (e.g. deducing, aggregating) and store > > resource- level alarm without any alarm_actions, so that users can

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

2015-12-02 Thread Ryota Mibu
raw alarms in admin space that is not visible from end user, or using relevant severity or tag so that user can filter out uninterested alarms. Best regards, Ryota --- "Ryota Mibu" <>

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

2015-11-24 Thread Ryota Mibu
Hi Ifat, Thank you for starting discussion how AODH can be integrated with Vitrage that would be a good example of AODH integration with other OpenStack components. The key role of creating alarm definition is to set endpoint (alarm_actins) which can be receive alarm notification from AODH.

[openstack-dev] [ceilometer] jenkis job failures

2015-08-25 Thread Ryota Mibu
/ Thanks, Ryota --- Ryota Mibu NEC Corporation __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Ceilometer][AODH] Timeout Event Alarms

2015-08-07 Thread Ryota Mibu
Hi, Sorry for my late response and my absent in weekly meetings... I'm not sure whether I captured your idea correctly, but I prefer the second approach now. I agreed the point Igor and liusheng mentioned that the second approach enables end users to have configurable expire-time. In

Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps

2015-07-02 Thread Ryota Mibu
Hi, I'd like to see how we can develop new alarm features, since I'm working on event-alarm. Having duplicated code bases may confuse developer too, so we should have some policies like: * aodh focus on making sure that it provides existing API and functionality as of kilo to end users *

Re: [openstack-dev] [ceilometer] RE: [all] how to send messages (and events) to our users

2015-04-15 Thread Ryota Mibu
Hi Gordon, Great! I put some generic questions regarding Alerting on events + immediate notification in gerrit. I'd like to capture high-level direction of this feature. If it's not right place to having such discussion and should move to mailing

[openstack-dev] [ceilometer] RE: [all] how to send messages (and events) to our users

2015-04-14 Thread Ryota Mibu
Hi Gordon and Ceilometer folks, I'm newbie in Ceilometer, but would like to get involved the contribution of alerting on events. in Liberty, we intend on support action/alerting on events so maybe it's something we should collaborate on to ensure the right functionality is provided. Could

[openstack-dev] [nova][neutron] bridge name generator for vif plugging

2014-12-15 Thread Ryota Mibu
Hi all, We are proposing a change to move bridge name generator (creating bridge name from net-id or reading integration bridge name from nova.conf) from Nova to Neutron. The followings are BPs in Nova and Neutron.

Re: [openstack-dev] [nova][neutron] bridge name generator for vif plugging

2014-12-15 Thread Ryota Mibu
Ian and Daniel, Thanks for the comments. I have neutron spec here and planned to start from Neutron side to expose bridge name via port-binding API. Thanks, Ryota -Original Message- From: Ian Wells []

Re: [openstack-dev] [nova] Configuring libivrt VIF driver

2014-08-27 Thread Ryota Mibu
Hi Daniel, For Juno the vif_driver option still exists can be used. In the current master branch, there is no 'vif_driver' option for libvirt. It has been deleted by [1], and I can't find any patches to enable 'vif_driver' config on gerrit. Is there plan to get the 'vif_driver' config

Re: [openstack-dev] [Baremetal][Neutron] SDN Solution for Openstack Baremetal Driver

2014-05-16 Thread ryota mibu
Hi Tim, NTT-docomo and VTJ developed network isolation in baremetal before they merging baremetal driver to upstream, and I also supported them by providing SDN(OpenFlow) controller plugin. I don't have good article to explain that for now, but I can have discussion if you are in the summit.