Re: [Openstack] ceilometer alarm
Hi
I'd try with something simply first:
alarm_1:
type: OS::Ceilometer::Alarm
properties:
description: cpu_util alarm
meter_name: cpu_util
statistic: avg
period: 60
evaluation_periods: 1
threshold: 20
matching_metadata: {"metadata.user_metadata.stack": {get_param:
"OS::stack_id"}}
comparison_operator: gt
and then, I'd check "ceilometer alarm-show " in both cases
(ceilometer cli alarm definition vs heat alarm definition)
On 20/10/16 23:58, Denis Aleksandrov wrote:
> Hello,
> I user Kilo version of openstack and want to attach a ceilometer alarm
> to an instance by heat:
>
> si-vm1:
> type: OS::Nova::Server
> depends_on: [ instance_ip_left1, instance_ip_right1, instance_ip_mgt1 ]
> properties:
>name: { get_param: si_vm_name1 }
>image: { get_param: image }
>flavor: { get_param: flavor }
>availability_zone: { get_param: zone }
>networks:
> - port: { get_resource: vm_interface_mgt1 }
> - port: { get_resource: vm_interface_left1 }
> - port: { get_resource: vm_interface_right1 }
>
>vsrx1:
> type: OS::Ceilometer::Alarm
> depends_on: [ si-vm1 ]
> properties:
>description: vsrx1
>meter_name: cpu_util
>statistic: avg
>comparison_operator: gt
>period: 60
>evaluation_periods: 1
>threshold: 20
>alarm_actions: ['http://127.0.0.1:8197/alarms/api']
>ok_actions: ['http://127.0.0.1:8197/alarms/api']
>matching_metadata: {'resource_id': {get_resource: si-vm1}}
>repeat_actions: False
>
> It doesn't work properly and the alarm always shows "insufficient data" state.
> Whereas if I attach alarm to the instance through python ceilometer client:
>
> ceilometer.alarms.create(name='vsrx1',
> meter_name='cpu_util',
> threshold='20',
> comparison_operator='gt',
> statistic='avg',
> period='60',
> evaluation_periods='1',
>
> alarm_actions=['http://127.0.0.1:8197/alarms/api'],
>
> ok_actions=['http://127.0.0.1:8197/alarms/api'],
> matching_metadata={'resource_id':'
>
> a3e0aa8f-49b7-488a-9e58-06b1ae085c6c'},
> project_id=
> 'bad15bda17ea45ca9598f596ebef1148')
>
> it works fine.
> Could someone suggest how to reference a Nova Instance in the Ceilometer Alarm
> heat resource?
>
>
>
> Best Regards,
> Denis Aleksandrov
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Barcelona Food recommendations
Ed Leafe wrote: > Tickets is my absolute favorite. You'll need to get tickets to Tickets. > Google it and try and get it. The food is some of the best in the world > and for you get, not incredibly $$$. Unfortunately Tickets is fully booked until December :) -- Thierry Carrez (ttx) ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [Fuel] Deployment failed after applying updates in Fuel-8.0 .
Hi All, I will be thankful if someone can help me in below mentioned issue. i had openstack environment deployed using Fuel-8.0 and it got deployed fine and running without any issues. As i LMA node is not having good CPU resource so i thought of replacing the current LMA node. As i planned for maintenance so i applied maintenance-updates-3 also. My Environment Details : 3 Controller Nodes 4 Compute + Ceph Nodes 1 LMA node After updates applied the environment was working fine as expected but had issue while adding new LMA node. please find below steps i followed. Step i followed: 1. Deploy Environment using fuel 8.0 ( 3 Controller , 4 Compute + Ceph , 1 LMA node ). 2. remove 1 LMA node from deployment. ( I removed to replace with high performance Node ) 3. Deploy changes to environment 4. remove LMA plugins from FUEL CLI ( Version 0.10) 5. update environment with maintenance-updates-3 ( followed the document ) 6. now install LMA plugins ( updated Version 0.10.2) 7. add new LMA node to environment. 8. Deploy changes Expected Result : Deployment should be done with out any errors. Actual Result : Deployment failed. ** Error *** Error Deployment has failed. Method granular_deploy. Failed to execute hook 'override_configuration' Puppet run failed. Check puppet logs for details --- uids: - '11' - '2' - '5' - '4' - '7' - '6' - '9' - '8' parameters: puppet_modules: /etc/puppet/modules puppet_manifest: /etc/puppet/modules/osnailyfacter/modular/hiera/override_ configuration.pp timeout: 180 cwd: / priority: 2300 fail_on_error: true type: puppet id: override_configuration . Inspect Astute logs for the details Please let me know if you need more details. I tried to create diagnostic snapshot but its giving out timeout error. Thanks, Chandra ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [DefCore][Interop] Fall 2016 OpenStack Interoperability Issues Report
Hello Everyone, The DefCore Committee has been working to provide a periodic report on a tractable, small number of major barriers we have uncovered during the course of work to the community that we wish to focus attention on. The report is intended to be constructive rather than critical, and assist the community in recognizing barriers to interoperability so that they can be addressed. The full report is available here: https://github.com/openstack/defcore/blob/master/doc/source/periodic_report s/fall_2016.rst Our first report covers the following issues: * Issue 1: Testing Interoperability https://github.com/openstack/defcore/blob/master/doc/source/periodic_report s/fall_2016.rst#issue-1-testing-interoperability * Issue 2: Varying Models for API Evolution https://github.com/openstack/defcore/blob/master/doc/source/periodic_report s/fall_2016.rst#issue-2-varying-models-for-api-evolution * Issue 3: External Network Connectivity https://github.com/openstack/defcore/blob/master/doc/source/periodic_report s/fall_2016.rst#issue-3-external-network-connectivity * Issue 4: API and Policy Discoverability https://github.com/openstack/defcore/blob/master/doc/source/periodic_report s/fall_2016.rst#issue-4-api-and-policy-discoverability * Issue 5: Lack of Clarity on DefCore's Purpose and Abilities https://github.com/openstack/defcore/blob/master/doc/source/periodic_report s/fall_2016.rst#issue-5-lack-of-clarity-on-defcore-s-purpose-and-abilities Please let us know if you have any questions about the report. If you are attending OpenStack Summit in Barcelona, please join us for DefCore and RefStack sessions: * Interop (DefCore) Working Group Work Session: Tuesday, October 25, 2:15pm-2:55pm, AC Hotel - P14 - Pedralbes, https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1679 8 * OpenStack Interoperability Challenge: Running Unmodified Apps in Any OpenStack Cloud, Wednesday, October 26, 9:25am-9:35am, Keynote stage, https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1736 2 * RefStack Work Sessions Wednesday, Octover 26, 5:05 - 5:45 pm, 5:55 - 6:35 pm, AC Hotel - P3 - Gràcia , https://etherpad.openstack.org/p/refstack-ocata-summit * Interop? You Keep Using That Word, I Do Not Think It Means What You Think It Means. Thursday, October 27, 9:50am-10:30am, CCIB - Centre de Convencions Internacional de Barcelona - P1 - Room 117, https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1633 9 * Beyond Refstack: The Interop Challenge. Thursday, October 27, 11:00am-11:40am, Hilton Diagonal Mar - P0 - Ballroom A. https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1641 2 * Heat: Work Session (DefCore related) Friday, October 28, 11:00am-11:40am, AC Hotel - P3 - Gràcia, https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1706 3 Thank you, Egle Sigler ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
