[openstack-dev] 答复: Re: [aodh] about alarm update with --query
Hi Julien Danjou,
Thanks for your suggestion.
Already report a bug:
https://bugs.launchpad.net/ubuntu/+source/aodh/+bug/1645694
BR,
dwj
Julien Danjou
2016-11-29 18:12
收件人
dong.wenj...@zte.com.cn
抄送
openstack-dev@lists.openstack.org
主题
Re: [openstack-dev] [aodh] about alarm update with --query
On Tue, Nov 29 2016, dong.wenj...@zte.com.cn wrote:
Hi dongwenjuan,
I'd suggest to open a bug against aodh on Launchpad. I've no idea if
it's a bug or not, but at least it'll be logged and we'll be able to dig
into that. :)
> Hi all,
>
> I use aodh cli to create a event alarm with query condition, the cli
runs
> successfully.
> But when i want to update the query condition, the cli runs failed.
> The help info about `--query` para with these two cli have no
difference.
>
> The information is as follows, Does anyone else know why? Thanks~
>
> stack@cloud:~$ aodh alarm create --name test --type event --event-type
> compute.instance.update --query
> "traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac49"
>
+---+---+
> | Field | Value |
>
+---+---+
> | alarm_actions | [] |
> | alarm_id | 8d1018bd-8f14-4f34-b47c-54588488d658 |
> | description | Alarm when compute.instance.update event
> occurred.|
> | enabled | True |
> | event_type| compute.instance.update |
> | insufficient_data_actions | [] |
> | name | test |
> | ok_actions| [] |
> | project_id| f0895991f44044ccba8e62b201b70360 |
> | query | traits.instance_id =
> 3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac49 |
> | repeat_actions| False |
> | severity | low |
> | state | insufficient data |
> | state_timestamp | 2016-11-29T06:31:50.094836 |
> | time_constraints | [] |
> | timestamp | 2016-11-29T06:31:50.094836 |
> | type | event |
> | user_id | 7d7531a2030d4537b60a5193bf6ab286 |
>
+---+---+
> stack@cloud:~$
> stack@cloud:~$
> stack@cloud:~$ aodh alarm update 8d1018bd-8f14-4f34-b47c-54588488d658
> --event-type computer.instance.delete --query
> "traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac88"
> Invalid input for field/attribute data. Value: '{'alarm_actions': [],
> 'event_rule': {'query':
> 'traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac88',
> 'event_type': 'computer.instance.delete'}, 'ok_actions': [], 'name':
> 'test', 'state': 'insufficient data', 'timestamp':
> '2016-11-29T06:31:50.094836', 'enabled': True, 'state_timestamp':
> '2016-11-29T06:31:50.094836', 'severity': 'low', 'alarm_id':
> '8d1018bd-8f14-4f34-b47c-54588488d658', 'time_constraints': [],
> 'insufficient_data_actions': [], 'repeat_actions': False, 'user_id':
> '7d7531a2030d4537b60a5193bf6ab286', 'project_id':
> 'f0895991f44044ccba8e62b201b70360', 'type': 'event', 'description':
'Alarm
> when compute.instance.update event occurred.'}'. Value not a valid list:
> traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac88 (HTTP
400)
> (Request-ID: req-ad8bd440-2784-43b7-98d7-7e0ae27dcebc)
> stack@cloud:~$
>
>
>
>
--
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info
signature.asc
Description: Binary data
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [aodh] about alarm update with --query
Hi all,
I use aodh cli to create a event alarm with query condition, the cli runs
successfully.
But when i want to update the query condition, the cli runs failed.
The help info about `--query` para with these two cli have no difference.
The information is as follows, Does anyone else know why? Thanks~
stack@cloud:~$ aodh alarm create --name test --type event --event-type
compute.instance.update --query
"traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac49"
+---+---+
| Field | Value |
+---+---+
| alarm_actions | [] |
| alarm_id | 8d1018bd-8f14-4f34-b47c-54588488d658 |
| description | Alarm when compute.instance.update event
occurred.|
| enabled | True |
| event_type| compute.instance.update |
| insufficient_data_actions | [] |
| name | test |
| ok_actions| [] |
| project_id| f0895991f44044ccba8e62b201b70360 |
| query | traits.instance_id =
3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac49 |
| repeat_actions| False |
| severity | low |
| state | insufficient data |
| state_timestamp | 2016-11-29T06:31:50.094836 |
| time_constraints | [] |
| timestamp | 2016-11-29T06:31:50.094836 |
| type | event |
| user_id | 7d7531a2030d4537b60a5193bf6ab286 |
+---+---+
stack@cloud:~$
stack@cloud:~$
stack@cloud:~$ aodh alarm update 8d1018bd-8f14-4f34-b47c-54588488d658
--event-type computer.instance.delete --query
"traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac88"
Invalid input for field/attribute data. Value: '{'alarm_actions': [],
'event_rule': {'query':
'traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac88',
'event_type': 'computer.instance.delete'}, 'ok_actions': [], 'name':
'test', 'state': 'insufficient data', 'timestamp':
'2016-11-29T06:31:50.094836', 'enabled': True, 'state_timestamp':
'2016-11-29T06:31:50.094836', 'severity': 'low', 'alarm_id':
'8d1018bd-8f14-4f34-b47c-54588488d658', 'time_constraints': [],
'insufficient_data_actions': [], 'repeat_actions': False, 'user_id':
'7d7531a2030d4537b60a5193bf6ab286', 'project_id':
'f0895991f44044ccba8e62b201b70360', 'type': 'event', 'description': 'Alarm
when compute.instance.update event occurred.'}'. Value not a valid list:
traits.instance_id=string::3ed4fbc1-023e-4c4e-85d3-cf6d73c9ac88 (HTTP 400)
(Request-ID: req-ad8bd440-2784-43b7-98d7-7e0ae27dcebc)
stack@cloud:~$
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: [vitrage] about aodh alarm notification
Hi all, Maybe call the get_all method in the AodhDriver constructor and cache all the alarms is a simple way. BR, dwj Yujun Zhang 2016-11-28 11:23 收件人 "OpenStack Development Mailing List (not for usage questions)" , "dong.wenj...@zte.com.cn" 抄送 "Hefetz, Idan (Nokia - IL)" , "zhang.yuj...@zte.com.cn" 主题 Re: [openstack-dev] [vitrage] about aodh alarm notification Hi, Alexey My comments inline. On Mon, Nov 28, 2016 at 1:52 AM Weyl, Alexey (Nokia - IL) < alexey.w...@nokia.com> wrote: Hi Dong, I can think of 2 solutions for this problem: 1. We can talk with the AODH developers and check if they can add additional data for the aodh notifications. I think it might not be easily accepted since sending only the changes on update notification looks more reasonable to me. 2. We can add a cache in the aodh driver, and call the get_all method in the AodhDriver constructor or when the first notification happens and fill the cache with the data. Then for each notification that arrives you will update that cache in the aodh notification service, and send then event with all the data you need. I doubt this will degrade the performance for the first notification since there will be additional conversation to retrieve the full data. My proposal is to share a cache between snapshot service and listener service and I think it is a common requirements for all datasource using PUSH method. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: RE: RE: [vitrage] about aodh alarm notification
EmThe solution goes back to my first question. Snapshot service calls get_all, and caches all the alarms. But listener service can't get the cache because there are two services and can't share the cache. BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-11-24 23:50 收件人 "dong.wenj...@zte.com.cn" 抄送 "Hefetz, Idan (Nokia - IL)" , "Afek, Ifat (Nokia - IL)" , "openstack-dev@lists.openstack.org" , "zhang.yuj...@zte.com.cn" 主题 RE: RE: [openstack-dev] [vitrage] about aodh alarm notification It seems that you will need to have a cache for that issue. Due to the fact that AODH alarms aren’t deleted, and stay alive (in AODH) when their state is changed to ok (but in this case aren’t supposed to appear in Vitrage), and then when the state is changed back to error (‘ alarm’) they are supposed to appear in Vitrage with all the data, the most simple way to do that (without touching the core processor and architecture) is by saving those alarms of AODH in cache in the AODH driver, update its data every change that arrive to the driver, and then when a notification arrives and if the state that arrived is different than OK and the state that was in the cache is OK then send an event with all the data updated in the cache to the queue, otherwise send only the data received from the oslo bus to the queue (don’t forget of course to update the cache each time an event received, and each time we call the get_all of aodh (every snapshot_interval time) we can update the data in the cache as well. Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, November 24, 2016 11:24 AM To: Weyl, Alexey (Nokia - IL) Cc: Hefetz, Idan (Nokia - IL); Afek, Ifat (Nokia - IL); openstack-dev@lists.openstack.org; zhang.yuj...@zte.com.cn Subject: 答复: RE: [openstack-dev] [vitrage] about aodh alarm notification Hi Weyl Alexey, Another question: If we received the alarm.creation notification with the 'ok' state, we filter it and don't create vertex in the Graph. The next received the alarm state_change notification, all the other alarm details are missing in the vertex. How can I handle this? Thanks~ BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-11-24 16:25 收件人 "dong.wenj...@zte.com.cn" , "Afek, Ifat (Nokia - IL)" , "Hefetz, Idan (Nokia - IL)" < idan.hef...@nokia.com>, "zhang.yuj...@zte.com.cn" 抄送 "openstack-dev@lists.openstack.org" 主题 RE: [openstack-dev] [vitrage] about aodh alarm notification Hi Dong, Good question, I will explain how you can handle this problem in Vitrage. You don't need the cache mechanism here, it is much more simplier. When you get a new alarm with get_all or by notification of 'alarm.creation' you will create the alarm with its correct data \ properties. Then when you receive a notification of 'alarm.rule_change', 'alarm.state_transition', 'alarm.deletion' all you need to do is only to update the correct property that has changed in the aodh vertex. Thus, When you create the Vertex in the transformer, you know the aodh uuid so you know the vitrage_id, and you can pass only the properties that you have received and want to update (and not all the properties that there in the aodh vertex). All the other properties that you haven't received that haven't changed you can pass them as None and they won't be changed in the graph. Hope this explains everything. If you have other questions, you are more than welcome to ask. Best Regrads, Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, November 24, 2016 9:39 AM To: Afek, Ifat (Nokia - IL); Weyl, Alexey (Nokia - IL); Hefetz, Idan (Nokia - IL); zhang.yuj...@zte.com.cn Cc: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] about aodh alarm notification Hi Vitrages, Currently there are four aodh alarm notifications we need to handle: 'alarm.creation', 'alarm.rule_change', 'alarm.state_transition', 'alarm.deletion' Only the alarm.creation notification carries the alarm detail info. So we need to cache the alarm info. When we receive other notifications, we can fill all fields from the cache. But if the alarm creates before vitrage servies startup, we can't get the alarm.creation notification. So we need to get_all when vitrage services startup. As `SnapshotsService` will get all alarms info when it startup. But `SnapshotsService` and `ListenerService` are two services, they can't share the cache data unless they communicate with each other. This wil be a big change. Are there any other better solutions? I need some help, thanks :) BR, dwj __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: RE: [vitrage] about aodh alarm notification
Hi Weyl Alexey, Another question: If we received the alarm.creation notification with the 'ok' state, we filter it and don't create vertex in the Graph. The next received the alarm state_change notification, all the other alarm details are missing in the vertex. How can I handle this? Thanks~ BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-11-24 16:25 收件人 "dong.wenj...@zte.com.cn" , "Afek, Ifat (Nokia - IL)" , "Hefetz, Idan (Nokia - IL)" , "zhang.yuj...@zte.com.cn" 抄送 "openstack-dev@lists.openstack.org" 主题 RE: [openstack-dev] [vitrage] about aodh alarm notification Hi Dong, Good question, I will explain how you can handle this problem in Vitrage. You don't need the cache mechanism here, it is much more simplier. When you get a new alarm with get_all or by notification of 'alarm.creation' you will create the alarm with its correct data \ properties. Then when you receive a notification of 'alarm.rule_change', 'alarm.state_transition', 'alarm.deletion' all you need to do is only to update the correct property that has changed in the aodh vertex. Thus, When you create the Vertex in the transformer, you know the aodh uuid so you know the vitrage_id, and you can pass only the properties that you have received and want to update (and not all the properties that there in the aodh vertex). All the other properties that you haven't received that haven't changed you can pass them as None and they won't be changed in the graph. Hope this explains everything. If you have other questions, you are more than welcome to ask. Best Regrads, Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, November 24, 2016 9:39 AM To: Afek, Ifat (Nokia - IL); Weyl, Alexey (Nokia - IL); Hefetz, Idan (Nokia - IL); zhang.yuj...@zte.com.cn Cc: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] about aodh alarm notification Hi Vitrages, Currently there are four aodh alarm notifications we need to handle: 'alarm.creation', 'alarm.rule_change', 'alarm.state_transition', 'alarm.deletion' Only the alarm.creation notification carries the alarm detail info. So we need to cache the alarm info. When we receive other notifications, we can fill all fields from the cache. But if the alarm creates before vitrage servies startup, we can't get the alarm.creation notification. So we need to get_all when vitrage services startup. As `SnapshotsService` will get all alarms info when it startup. But `SnapshotsService` and `ListenerService` are two services, they can't share the cache data unless they communicate with each other. This wil be a big change. Are there any other better solutions? I need some help, thanks :) BR, dwj __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: RE: [vitrage] about aodh alarm notification
Hi Weyl, Alexey, Oh, I made the issue complicated. Thanks for your explaintion~ I'll try again. Thank you very much~ BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-11-24 16:25 收件人 "dong.wenj...@zte.com.cn" , "Afek, Ifat (Nokia - IL)" , "Hefetz, Idan (Nokia - IL)" , "zhang.yuj...@zte.com.cn" 抄送 "openstack-dev@lists.openstack.org" 主题 RE: [openstack-dev] [vitrage] about aodh alarm notification Hi Dong, Good question, I will explain how you can handle this problem in Vitrage. You don't need the cache mechanism here, it is much more simplier. When you get a new alarm with get_all or by notification of 'alarm.creation' you will create the alarm with its correct data \ properties. Then when you receive a notification of 'alarm.rule_change', 'alarm.state_transition', 'alarm.deletion' all you need to do is only to update the correct property that has changed in the aodh vertex. Thus, When you create the Vertex in the transformer, you know the aodh uuid so you know the vitrage_id, and you can pass only the properties that you have received and want to update (and not all the properties that there in the aodh vertex). All the other properties that you haven't received that haven't changed you can pass them as None and they won't be changed in the graph. Hope this explains everything. If you have other questions, you are more than welcome to ask. Best Regrads, Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, November 24, 2016 9:39 AM To: Afek, Ifat (Nokia - IL); Weyl, Alexey (Nokia - IL); Hefetz, Idan (Nokia - IL); zhang.yuj...@zte.com.cn Cc: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] about aodh alarm notification Hi Vitrages, Currently there are four aodh alarm notifications we need to handle: 'alarm.creation', 'alarm.rule_change', 'alarm.state_transition', 'alarm.deletion' Only the alarm.creation notification carries the alarm detail info. So we need to cache the alarm info. When we receive other notifications, we can fill all fields from the cache. But if the alarm creates before vitrage servies startup, we can't get the alarm.creation notification. So we need to get_all when vitrage services startup. As `SnapshotsService` will get all alarms info when it startup. But `SnapshotsService` and `ListenerService` are two services, they can't share the cache data unless they communicate with each other. This wil be a big change. Are there any other better solutions? I need some help, thanks :) BR, dwj __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] about aodh alarm notification
Hi Vitrages, Currently there are four aodh alarm notifications we need to handle: 'alarm.creation', 'alarm.rule_change', 'alarm.state_transition', 'alarm.deletion' Only the alarm.creation notification carries the alarm detail info. So we need to cache the alarm info. When we receive other notifications, we can fill all fields from the cache. But if the alarm creates before vitrage servies startup, we can't get the alarm.creation notification. So we need to get_all when vitrage services startup. As `SnapshotsService` will get all alarms info when it startup. But `SnapshotsService` and `ListenerService` are two services, they can't share the cache data unless they communicate with each other. This wil be a big change. Are there any other better solutions? I need some help, thanks :) BR, dwj__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm
Hi All, I think it's clear now. We can start to implement the Aodh-message-bus-notifications BP. :) Thanks~ BR, dwj "Afek, Ifat (Nokia - IL)" 2016-10-21 01:23 收件人 gordon chung , "dong.wenj...@zte.com.cn" 抄送 "OpenStack Development Mailing List (not for usage questions)" 主题 Re: 答复: Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm On 20/10/2016, 20:14, "gordon chung" wrote: > >On 20/10/16 01:01 PM, Afek, Ifat (Nokia - IL) wrote: >> Well… long time ago I asked to add another notification topic to Aodh, and you said that you blocked it. If that’s not the case, everything is fine :-) >> Like I said before, we planned on implementing it in Newton, but unfortunately it didn’t happen. I really hope to improve the Vitrage-Aodh integration in Ocata. >> >> >> >> Ifat. > >i see. i wasn't being critical about no work but i'll be honest, i don't >remember what this is about since i was looking at other stuff so if you >have a patch/ML to refresh my memory, that'd help. > >this is the only thread[1] i recall, and even then, i don't remember >much about it. :( > >[1] http://lists.openstack.org/pipermail/openstack-dev/2016-June/098074.html > >cheers, > >-- >gord What I recall was a few months earlier, we had a chat on ceilometer IRC channel… not sure if I can find the exact date. Anyway, I guess it doesn’t matter now. If you think the change can be done, then great. Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm
Hi Gordon Chung, Could you please tell me why adding another notification topic is not a good choice? Thanks~ BR, dwj "Afek, Ifat (Nokia - IL)" 2016-10-19 16:20 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" , "g...@live.ca" 抄送 主题 Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm From: "dong.wenj...@zte.com.cn" Date: Wednesday, 19 October 2016 at 11:01 The BP of aodh-message-bus-notifications[1] was blocked as Aodh message bus notification. As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh alarm_deletion notification is missing. I proposed a patch to add the Aodh alarm_deletion notification.[3] Please help me to review this patch. Do the alarm.creation, alarm.state_transition and alarm.deletion satisfy the Vitrage requirement? I'd like to help to implement the aodh-message-bus-notifications BP if there is nobody interest in it. This is more complex. Aodh has a mechanism for registering a URL to be notified when the state of a specific alarm is changed. Vitrage asked for something else - a notification whenever *any* alarm state is changed. In Vitrage we don’t want to register to each and every Aodh alarm separately, so we prefer to get the notifications for all changes on the message bus (as we do with other OpenStack projects). In addition, there is currently no notification about a newly created alarm, so even if we register a URL on each alarm we will not be able to register it on the new alarms. [dwj]: If i understand correctly, Aodh already support a notification whenever *any* alarm state is changed. See https://github.com/openstack/aodh/blob/master/aodh/evaluator/__init__.py#L107 . We only need to config the vitrage_notifications topics in Aodh then Vitrage can get the notifications from Aodh. Let me know if i miss something. A few months ago I discussed it with Gordon Chung, and understood that he blocked the option to add another notification topic. Gordon? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm
"Afek, Ifat (Nokia - IL)" 2016-10-19 15:21 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" 抄送 主题 Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm From: "dong.wenj...@zte.com.cn" Date: Wednesday, 19 October 2016 at 09:21 The BP of aodh-message-bus-notifications[1] was blocked as Aodh message bus notification. As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh alarm_deletion notification is missing. I proposed a patch to add the Aodh alarm_deletion notification.[3] Please help me to review this patch. Do the alarm.creation, alarm.state_transition and alarm.deletion satisfy the Vitrage requirement? I'd like to help to implement the aodh-message-bus-notifications BP if there is nobody interest in it. This is more complex. Aodh has a mechanism for registering a URL to be notified when the state of a specific alarm is changed. Vitrage asked for something else - a notification whenever *any* alarm state is changed. In Vitrage we don’t want to register to each and every Aodh alarm separately, so we prefer to get the notifications for all changes on the message bus (as we do with other OpenStack projects). In addition, there is currently no notification about a newly created alarm, so even if we register a URL on each alarm we will not be able to register it on the new alarms. [dwj]: If i understand correctly, Aodh already support a notification whenever *any* alarm state is changed. See https://github.com/openstack/aodh/blob/master/aodh/evaluator/__init__.py#L107 . We only need to config the vitrage_notifications topics in Aodh then Vitrage can get the notifications from Aodh. Let me know if i miss something. About the Aodh custon alarm: What about the alarm type as `prompt` or something else like this, which means the alarm is fired with no evaluation. And the metedata include the `source_id` means which source the alarm is on? This is more or less what we had in mind. Be able to control the state change externally + add metadata to the alarm (resource_id and optimally other information). [1] https://blueprints.launchpad.net/vitrage/+spec/aodh-message-bus-notifications [2]https://etherpad.openstack.org/p/newton-telemetry-vitrage [3]https://review.openstack.org/#/c/387754/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm
Hi All, The BP of aodh-message-bus-notifications[1] was blocked as Aodh message bus notification. As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh alarm_deletion notification is missing. I proposed a patch to add the Aodh alarm_deletion notification.[3] Please help me to review this patch. Do the alarm.creation, alarm.state_transition and alarm.deletion satisfy the Vitrage requirement? I'd like to help to implement the aodh-message-bus-notifications BP if there is nobody interest in it. About the Aodh custon alarm: What about the alarm type as `prompt` or something else like this, which means the alarm is fired with no evaluation. And the metedata include the `source_id` means which source the alarm is on? Let me know if you have some good ideas. Thanks, [1]https://blueprints.launchpad.net/vitrage/+spec/aodh-message-bus-notifications [2]https://etherpad.openstack.org/p/newton-telemetry-vitrage [3]https://review.openstack.org/#/c/387754/ BR, dwj "Afek, Ifat (Nokia - IL)" 2016-10-13 17:31 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" 抄送 主题 Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm Hi dwj, Thanks for bringing this up. Aodh notifier plugin inside Vitrage is defined as a POC, and is disabled by default. We are aware that this integration is not working well, and its purpose was to demonstrate how it could work and start a discussion about other possible implementations. I know that in Austin there were discussions between Aodh and Vitrage teams, and a general agreement that Vitrage would suggest a design for Aodh custom alarm. Such an alarm could then be used by Vitrage instead of the event-alarm in a more natural way. Unfortunately, due to time limitations, we did not get to write the custom alarm blueprint in Aodh. It is still defined as a high priority in Vitrage roadmap, and I hope it will happen in Ocata. If you have some free time you are more than welcome to give a hand :-) Best Regards, Ifat. From: "dong.wenj...@zte.com.cn" Date: Thursday, 13 October 2016 at 04:20 Hi vitrages, In aodh notifier plugin, we receive a ACTIVATE_DEDUCED_ALARM_EVENT and then create a aodh event alarm. The event alarm with a `event_rule`, it should be include `event_type` and `query` which Aodh used to evaluator a alarm when it receives a specify event to filter with the query to fire a alarm. see [1] But we create a event alarm only with `query` in `event_rule`. The deduced alarm create with the `alarm` state so Aodh will skip to evaluator the fired alarm. The `event_rule` seems no necessary in the request body, am I right? Let me know if i miss something. :) [1] https://github.com/openstack/aodh/blob/master/doc/source/event-alarm.rst BR, dwj 董文娟 Wenjuan Dong 控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation 上海市浦东新区碧波路889号中兴通讯D3 D3, ZTE, No. 889, Bibo Rd. T: +86 021 85922M: +86 13661996389 E: dong.wenj...@zte.com.cn www.ztedevice.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm
Thanks a lot~ Julien Danjou 2016-10-14 17:52 收件人 dong.wenj...@zte.com.cn 抄送 "OpenStack Development Mailing List \(not for usage questions\)" 主题 Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm On Fri, Oct 14 2016, dong.wenj...@zte.com.cn wrote: > Is there any record about the discussion between Aodh and Vitrage? The notes are in the Etherpad: https://etherpad.openstack.org/p/newton-telemetry-vitrage -- Julien Danjou /* Free Software hacker https://julien.danjou.info */ [附件 "signature.asc" 被 董文娟00101742/user/zte_ltd 删除] __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm
Hi Ifat， Got it. Thanks for your reponse. Is there any record about the discussion between Aodh and Vitrage? BR, dwj "Afek, Ifat (Nokia - IL)" 2016-10-13 17:31 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" 抄送 主题 Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm Hi dwj, Thanks for bringing this up. Aodh notifier plugin inside Vitrage is defined as a POC, and is disabled by default. We are aware that this integration is not working well, and its purpose was to demonstrate how it could work and start a discussion about other possible implementations. I know that in Austin there were discussions between Aodh and Vitrage teams, and a general agreement that Vitrage would suggest a design for Aodh custom alarm. Such an alarm could then be used by Vitrage instead of the event-alarm in a more natural way. Unfortunately, due to time limitations, we did not get to write the custom alarm blueprint in Aodh. It is still defined as a high priority in Vitrage roadmap, and I hope it will happen in Ocata. If you have some free time you are more than welcome to give a hand :-) Best Regards, Ifat. From: "dong.wenj...@zte.com.cn" Date: Thursday, 13 October 2016 at 04:20 Hi vitrages, In aodh notifier plugin, we receive a ACTIVATE_DEDUCED_ALARM_EVENT and then create a aodh event alarm. The event alarm with a `event_rule`, it should be include `event_type` and `query` which Aodh used to evaluator a alarm when it receives a specify event to filter with the query to fire a alarm. see [1] But we create a event alarm only with `query` in `event_rule`. The deduced alarm create with the `alarm` state so Aodh will skip to evaluator the fired alarm. The `event_rule` seems no necessary in the request body, am I right? Let me know if i miss something. :) [1] https://github.com/openstack/aodh/blob/master/doc/source/event-alarm.rst BR, dwj 董文娟 Wenjuan Dong 控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation 上海市浦东新区碧波路889号中兴通讯D3 D3, ZTE, No. 889, Bibo Rd. T: +86 021 85922M: +86 13661996389 E: dong.wenj...@zte.com.cn www.ztedevice.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [附件 "ATT1.gif" 被 董文娟00101742/user/zte_ltd 删除][附件 "ATT2.gif" 被 董文娟00101742/user/zte_ltd 删除] __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] about aodh notifier to create a event alarm
Hi vitrages, In aodh notifier plugin, we receive a ACTIVATE_DEDUCED_ALARM_EVENT and then create a aodh event alarm. The event alarm with a `event_rule`, it should be include `event_type` and `query` which Aodh used to evaluator a alarm when it receives a specify event to filter with the query to fire a alarm. see [1] But we create a event alarm only with `query` in `event_rule`. The deduced alarm create with the `alarm` state so Aodh will skip to evaluator the fired alarm. The `event_rule` seems no necessary in the request body, am I right? Let me know if i miss something. :) [1]https://github.com/openstack/aodh/blob/master/doc/source/event-alarm.rst BR, dwj 董文娟 Wenjuan Dong 控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation 上海市浦东新区碧波路889号中兴通讯D3 D3, ZTE, No. 889, Bibo Rd. T: +86 021 85922M: +86 13661996389 E: dong.wenj...@zte.com.cn www.ztedevice.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: 答复: Re: 答复: [vitrage] can't get nagios datasource
Hi Alexey, Thanks a lot~ :-) BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-09-05 17:21 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" 抄送 主题 Re: [openstack-dev] 答复: Re: 答复: [vitrage] can't get nagios datasource Hi Dong, When you install from scratch it comes with nagios in the types property. Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday, September 05, 2016 8:53 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] 答复: Re: 答复: [vitrage] can't get nagios datasource Hi Alexey, There is a old vitrage.conf in my env, I didn't config Nagios in the datasources section. Is it can't be overwrited when i redeploy a new OS env? BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-09-05 15:24 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org> 收件人 "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org> 抄送 主题 Re: [openstack-dev] 答复: [vitrage] can't get nagios datasource Hi Dong, What was the problem? Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday, September 05, 2016 8:07 AM To: OpenStack Development Mailing List (not for usage questions) Cc: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] 答复: [vitrage] can't get nagios datasource I already found the problem, thanks~ dong.wenj...@zte.com.cn 2016-09-05 12:41 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org> 收件人 "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org> 抄送 主题 [openstack-dev] [vitrage] can't get nagios datasource Hi Vitrages, I deploy the Vitrage OS env with the latest code using devstack. And I config the Nagios and start my_site. I used the config two months ago, it works. But this time, it can not get the nagio datasource. In the function `prepare_service`, i add some log to print `conf.datasources.types` as follows: It seems that the oslo_config can't get the Nagios opts. I checked all the Nagios config and didn't find the error. Is there any change about the config? 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.host 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.instance 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.zone 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: static_physical 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: aodh 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: cinder.volume 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.network 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.port __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: 答复: [vitrage] can't get nagios datasource
Hi Alexey, There is a old vitrage.conf in my env, I didn't config Nagios in the datasources section. Is it can't be overwrited when i redeploy a new OS env? BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-09-05 15:24 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" 抄送 主题 Re: [openstack-dev] 答复: [vitrage] can't get nagios datasource Hi Dong, What was the problem? Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday, September 05, 2016 8:07 AM To: OpenStack Development Mailing List (not for usage questions) Cc: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] 答复: [vitrage] can't get nagios datasource I already found the problem, thanks~ dong.wenj...@zte.com.cn 2016-09-05 12:41 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org> 收件人 "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org> 抄送 主题 [openstack-dev] [vitrage] can't get nagios datasource Hi Vitrages, I deploy the Vitrage OS env with the latest code using devstack. And I config the Nagios and start my_site. I used the config two months ago, it works. But this time, it can not get the nagio datasource. In the function `prepare_service`, i add some log to print `conf.datasources.types` as follows: It seems that the oslo_config can't get the Nagios opts. I checked all the Nagios config and didn't find the error. Is there any change about the config? 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.host 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.instance 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.zone 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: static_physical 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: aodh 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: cinder.volume 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.network 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.port __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: [vitrage] can't get nagios datasource
I already found the problem, thanks~ dong.wenj...@zte.com.cn 2016-09-05 12:41 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" 抄送 主题 [openstack-dev] [vitrage] can't get nagios datasource Hi Vitrages, I deploy the Vitrage OS env with the latest code using devstack. And I config the Nagios and start my_site. I used the config two months ago, it works. But this time, it can not get the nagio datasource. In the function `prepare_service`, i add some log to print `conf.datasources.types` as follows: It seems that the oslo_config can't get the Nagios opts. I checked all the Nagios config and didn't find the error. Is there any change about the config? 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.host 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.instance 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.zone 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: static_physical 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: aodh 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: cinder.volume 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.network 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.port __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] can't get nagios datasource
Hi Vitrages, I deploy the Vitrage OS env with the latest code using devstack. And I config the Nagios and start my_site. I used the config two months ago, it works. But this time, it can not get the nagio datasource. In the function `prepare_service`, i add some log to print `conf.datasources.types` as follows: It seems that the oslo_config can't get the Nagios opts. I checked all the Nagios config and didn't find the error. Is there any change about the config? 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.host 2016-09-05 14:48:55.680 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.instance 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: nova.zone 2016-09-05 14:48:55.681 1288 INFO vitrage.service [-] -dwj-prepare_service: static_physical 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: aodh 2016-09-05 14:48:55.682 1288 INFO vitrage.service [-] -dwj-prepare_service: cinder.volume 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.network 2016-09-05 14:48:55.683 1288 INFO vitrage.service [-] -dwj-prepare_service: neutron.port __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [devstack] some compress error when deploy OS
Hi all,
When i use devstack to deploy a OS env, it raise the error.
The log is as follows.
Does anybody know how to resolve this problem? Thank you!~
12 static files copied to '/opt/stack/horizon/static', 1708 unmodified.
+lib/horizon:init_horizon:152
DJANGO_SETTINGS_MODULE=openstack_dashboard.settings
+lib/horizon:init_horizon:152 django-admin compress --force
Found 'compress' tags in:
/opt/stack/horizon/openstack_dashboard/templates/horizon/_scripts.html
/opt/stack/horizon/openstack_dashboard/templates/horizon/_conf.html
/opt/stack/horizon/openstack_dashboard/templates/_stylesheets.html
Compressing... CommandError: An error occurred during rendering
/opt/stack/horizon/openstack_dashboard/templates/horizon/_scripts.html:
'\"../build/dagre-d3.js\"' isn't accessible via COMPRESS_URL
('/dashboard/static/') and can't be compressed
+lib/horizon:init_horizon:1exit_trap
+./stack.sh:exit_trap:480 local r=1
BR,
dwj
ZTE Information Security Notice: The information contained in this mail (and
any attachment transmitted herewith) is privileged and confidential and is
intended for the exclusive use of the addressee(s). If you are not an intended
recipient, any disclosure, reproduction, distribution or other dissemination or
use of the information contained is strictly prohibited. If you have received
this mail in error, please delete it and notify us immediately.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: [probably forge email可能是仿冒邮件] [vitrage] failed to show graph topology on graphwithout root
Hi Eylon, I think this commit caused the problem. get topology API don't handle the parameter depth Change-Id: I68eac9e3d5c4bfddbbc6d4ed7dbcc5ccbf089fcd I'll check and fix it. Sorry for that. BR, dwj "Malin, Eylon (Nokia - IL)" 2016-05-26 22:38 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "openstack-dev@lists.openstack.org" 抄送 主题 [probably forge email可能是仿冒邮件][openstack-dev] [vitrage] failed to show graph topology on graphwithout root Hi all, I use vitrage without any root graph (In my case there is no root). Until few days ago I was able to request topology of type graph with no problems. But I can't, I got 404, and the log says it can't find openstack.cluster node. I think it have the problems since these commits : I1189047849f714d8435414cc48098d71837b3ed0, I1438713136c0177282e8ee8e19a651af5590feef Eylon __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [vitrage] the section of vitrage.transformersin setup.cfg is not used
Hi, OK, i will fix it. Thank you for your response. :) BR, dwj "Afek, Ifat (Nokia - IL)" 2016-05-09 14:47 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)" 抄送 主题 [probably forge email可能是仿冒邮件]Re: [openstack-dev] [vitrage] the section of vitrage.transformersin setup.cfg is not used Hi, You are right, it is an old configuration that we should delete. Thanks for reporting this bug, and you are welcome to contact us again with any questions or suggestions you might have J Best regards, Ifat. From: EXT dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday, May 09, 2016 9:29 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage] the section of vitrage.transformers in setup.cfg is not used Hi folks, I notice that in the setup.cfg file there is the `vitrage.transformers` section. It seems not be used. May I propose a bug to delete it? Thank you~ vitrage.transformers = nova.instance = vitrage.entity_graph.transformer.nova_transformer.instance_transformer.InstanceTransformer nova.host = vitrage.entity_graph.transformer.nova_transformer.host_transformer.HostTransformer nova.zone = vitrage.entity_graph.transformer.nova_transformer.zone_transformer.ZoneTransformer BR, dwj __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [vitrage] the section of vitrage.transformers in setup.cfg is not used
Hi folks, I notice that in the setup.cfg file there is the `vitrage.transformers` section. It seems not be used. May I propose a bug to delete it? Thank you~ vitrage.transformers = nova.instance = vitrage.entity_graph.transformer.nova_transformer.instance_transformer.InstanceTransformer nova.host = vitrage.entity_graph.transformer.nova_transformer.host_transformer.HostTransformer nova.zone = vitrage.entity_graph.transformer.nova_transformer.zone_transformer.ZoneTransformer BR, dwj ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: openstack-dev] [vitrage] vitrage alarms list
Hi
I'm not sure.
The cli can create nova, cinder, glance and etc users, but not vitrage, so
strange.
So i delete all source repos, and clean the env, then deploy the OS again.
It works now. :)
But there is a problems in vitrage dashboard.
I use vitrage topology show cli can get the topology,but it don't show in
dashborad.
The error log in dashboard is as follows:
Unable to fetch the Vitrage Topology service.
The vitrage topology show cli works well
stack@cloud:~$ vitrage topology show
{
"directed": true,
"graph": {},
"nodes": [
{
"category": "RESOURCE",
"is_placeholder": false,
"is_deleted": false,
"name": "cloud",
"update_timestamp": "2016-04-23 08:42:36.037947+00:00",
"sample_timestamp": "2016-04-23 08:42:36.037947+00:00",
"aggregated_state": "UNDEFINED",
"graph_index": 0,
"vitrage_id": "RESOURCE:nova.host:cloud",
"type": "nova.host",
"id": "cloud"
},
Do you know where is the problems?
Thank you~
BR,
dwj
Eyal B
2016-04-24 15:32
收件人
dong.wenj...@zte.com.cn
抄送
"OpenStack Development Mailing List (not for usage questions)"
主题
Re: openstack-dev] [vitrage] vitrage alarms list
Hi,
I understand it works now
What was the problem ?
Eyal
On Fri, Apr 22, 2016 at 4:55 AM, wrote:
Hi
I get the latest sources and delete the /etc/vitrage/vitrage.conf，do
unstack.sh and stack.sh.
But deploy failed. The local.cnof is the same as before.
Is there any vitrage configures i missed?
Use openstack user create cli to create nova,glance and etc is successful.
Thanks for your help. :)
Here is the error log:
2016-04-22 02:00:01.646 | Initializing Vitrage
++/opt/stack/vitrage/devstack/plugin.sh:source:255 init_vitrage
++/opt/stack/vitrage/devstack/plugin.sh:init_vitrage:179
_vitrage_create_accounts
++/opt/stack/vitrage/devstack/plugin.sh:_vitrage_create_accounts:69
is_service_enabled vitrage-api
++functions-common:is_service_enabled:2047 local xtrace
+++functions-common:is_service_enabled:2048 set +o
+++functions-common:is_service_enabled:2048 grep xtrace
++functions-common:is_service_enabled:2048 xtrace='set -o xtrace'
++functions-common:is_service_enabled:2049 set +o xtrace
++functions-common:is_service_enabled:2077 return 0
++/opt/stack/vitrage/devstack/plugin.sh:_vitrage_create_accounts:71
create_service_user vitrage admin
++lib/keystone:create_service_user:449 local role=admin
++lib/keystone:create_service_user:451 get_or_create_user vitrage
stack Default
++functions-common:get_or_create_user:798 local user_id
++functions-common:get_or_create_user:799 [[ ! -z '' ]]
++functions-common:get_or_create_user:802 local email=
+++functions-common:get_or_create_user:816 openstack user create vitrage
--password stack --domain=Default --or-show -f value -c id
Discovering versions from the identity service failed when creating the
password plugin. Attempting to determine version from URL.
Could not determine a suitable URL for the plugin
++functions-common:get_or_create_user:814 user_id=
+functions-common:get_or_create_user:1 exit_trap
+./stack.sh:exit_trap:474 local r=1
++./stack.sh:exit_trap:475 jobs -p
+./stack.sh:exit_trap:475 jobs=
+./stack.sh:exit_trap:478 [[ -n '' ]]
+./stack.sh:exit_trap:484 kill_spinner
+./stack.sh:kill_spinner:370 '[' '!' -z '' ']'
+./stack.sh:exit_trap:486 [[ 1 -ne 0 ]]
+./stack.sh:exit_trap:487 echo 'Error on exit'
董文娟 Wenjuan Dong
控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation
上海市浦东新区碧波路889号中兴通讯D3
D3, ZTE, No. 889, Bibo Rd.
T: +86 021 85922M: +86 13661996389
E: dong.wenj...@zte.com.cn
www.ztedevice.com
Eyal B
2016-04-20 16:34
收件人
dong.wenj...@zte.com.cn
抄送
"OpenStack Development Mailing List (not for usage questions)" <
openstack-dev@lists.openstack.org>
主题
Re: 答复: [probably forge email可能是仿冒邮件]Re: [openstack-dev] 答复:
[probably forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage
alarms list
Hi,
Can you send the vitrage-graph.log ?
Is the vitrage-graph process running ?
We fixed some bugs with the devstack installation
Do you have the latest sources from the vitrage git repo ?
Can you get the latest sources (just do git pull)
delete the /etc/vitrage/vitrage.conf
do unstack.sh and stack.sh
and let me know if it works
Eyal
On Wed, Apr 20, 2016 at 10:35 AM, wrote:
Hi,
I exec all the vitrage cli and get the same error.
The log error is from /var/log/apache2/vitrage.log
Here is my config file.Thanks for your help~
BR
dwj
Eyal B
2016-04-20 14:10
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)" <
openstack-dev@lists.openstack.org>
收件人
"OpenStack Development Mailing List (not for usage questions)" <
openstack-dev@lists.openstack.org>
抄送
主题
[probably forge email可能是仿冒邮
[openstack-dev] [devstack] [vitrage] install vitrage by devstack failed
Hi folks, While installing vitrage by devstack with a fresh clone I am hitting following error. What could be the problems here? Is there any configures i missed? Thank you for help~ ++./stack.sh:echo_summary:385 echo -e Initializing Vitrage 2016-04-22 07:38:02.311 | Initializing Vitrage ++/opt/stack/vitrage/devstack/plugin.sh:source:255 init_vitrage ++/opt/stack/vitrage/devstack/plugin.sh:init_vitrage:179 _vitrage_create_accounts ++/opt/stack/vitrage/devstack/plugin.sh:_vitrage_create_accounts:69 is_service_enabled vitrage-api ++functions-common:is_service_enabled:2047 local xtrace +++functions-common:is_service_enabled:2048 set +o +++functions-common:is_service_enabled:2048 grep xtrace ++functions-common:is_service_enabled:2048 xtrace='set -o xtrace' ++functions-common:is_service_enabled:2049 set +o xtrace ++functions-common:is_service_enabled:2077 return 0 ++/opt/stack/vitrage/devstack/plugin.sh:_vitrage_create_accounts:71 create_service_user vitrage admin ++lib/keystone:create_service_user:449 local role=admin ++lib/keystone:create_service_user:451 get_or_create_user vitrage stack Default ++functions-common:get_or_create_user:798 local user_id ++functions-common:get_or_create_user:799 [[ ! -z '' ]] ++functions-common:get_or_create_user:802 local email= +++functions-common:get_or_create_user:816 openstack user create vitrage --password stack --domain=Default --or-show -f value -c id Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Could not determine a suitable URL for the plugin ++functions-common:get_or_create_user:814 user_id= +functions-common:get_or_create_user:1 exit_trap +./stack.sh:exit_trap:474 local r=1 ++./stack.sh:exit_trap:475 jobs -p +./stack.sh:exit_trap:475 jobs= Here is my local.conf file: [[local|localrc]] ADMIN_PASSWORD=stack DATABASE_PASSWORD=stack RABBIT_PASSWORD=stack SERVICE_PASSWORD=stack enable_service heat h-api h-api-cfn h-api-cw h-eng disable_service tempest enable_plugin vitrage https://github.com/openstack/vitrage enable_plugin vitrage-dashboard https://github.com/openstack/vitrage-dashboard enable_plugin ceilometer https://github.com/openstack/ceilometer enable_plugin aodh https://github.com/openstack/aodh GIT_DEPTH=1 [[post-config|$NOVA_CONF]] [DEFAULT] notification_topics = notifications,vitrage_notifications notification_driver=messagingv2 ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] 答复: Re: 答复: [probably forge email可能是仿冒邮件]Re: 答复: [probably forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage alarms list
Hi I get the latest sources and delete the /etc/vitrage/vitrage.conf，do unstack.sh and stack.sh. But deploy failed. The local.cnof is the same as before. Is there any vitrage configures i missed? Use openstack user create cli to create nova,glance and etc is successful. Thanks for your help. :) Here is the error log: 2016-04-22 02:00:01.646 | Initializing Vitrage ++/opt/stack/vitrage/devstack/plugin.sh:source:255 init_vitrage ++/opt/stack/vitrage/devstack/plugin.sh:init_vitrage:179 _vitrage_create_accounts ++/opt/stack/vitrage/devstack/plugin.sh:_vitrage_create_accounts:69 is_service_enabled vitrage-api ++functions-common:is_service_enabled:2047 local xtrace +++functions-common:is_service_enabled:2048 set +o +++functions-common:is_service_enabled:2048 grep xtrace ++functions-common:is_service_enabled:2048 xtrace='set -o xtrace' ++functions-common:is_service_enabled:2049 set +o xtrace ++functions-common:is_service_enabled:2077 return 0 ++/opt/stack/vitrage/devstack/plugin.sh:_vitrage_create_accounts:71 create_service_user vitrage admin ++lib/keystone:create_service_user:449 local role=admin ++lib/keystone:create_service_user:451 get_or_create_user vitrage stack Default ++functions-common:get_or_create_user:798 local user_id ++functions-common:get_or_create_user:799 [[ ! -z '' ]] ++functions-common:get_or_create_user:802 local email= +++functions-common:get_or_create_user:816 openstack user create vitrage --password stack --domain=Default --or-show -f value -c id Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. Could not determine a suitable URL for the plugin ++functions-common:get_or_create_user:814 user_id= +functions-common:get_or_create_user:1 exit_trap +./stack.sh:exit_trap:474 local r=1 ++./stack.sh:exit_trap:475 jobs -p +./stack.sh:exit_trap:475 jobs= +./stack.sh:exit_trap:478 [[ -n '' ]] +./stack.sh:exit_trap:484 kill_spinner +./stack.sh:kill_spinner:370 '[' '!' -z '' ']' +./stack.sh:exit_trap:486 [[ 1 -ne 0 ]] +./stack.sh:exit_trap:487 echo 'Error on exit' 董文娟 Wenjuan Dong 控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation 上海市浦东新区碧波路889号中兴通讯D3 D3, ZTE, No. 889, Bibo Rd. T: +86 021 85922M: +86 13661996389 E: dong.wenj...@zte.com.cn www.ztedevice.com Eyal B 2016-04-20 16:34 收件人 dong.wenj...@zte.com.cn 抄送 "OpenStack Development Mailing List (not for usage questions)" 主题 Re: 答复: [probably forge email可能是仿冒邮件]Re: [openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage alarms list Hi, Can you send the vitrage-graph.log ? Is the vitrage-graph process running ? We fixed some bugs with the devstack installation Do you have the latest sources from the vitrage git repo ? Can you get the latest sources (just do git pull) delete the /etc/vitrage/vitrage.conf do unstack.sh and stack.sh and let me know if it works Eyal On Wed, Apr 20, 2016 at 10:35 AM, wrote: Hi, I exec all the vitrage cli and get the same error. The log error is from /var/log/apache2/vitrage.log Here is my config file.Thanks for your help~ BR dwj Eyal B 2016-04-20 14:10 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" < openstack-dev@lists.openstack.org> 收件人 "OpenStack Development Mailing List (not for usage questions)" < openstack-dev@lists.openstack.org> 抄送 主题 [probably forge email可能是仿冒邮件]Re: [openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage alarms list Hi, Can you send the local.conf file in your devstack folder ? Can you send the /etc/vitrage/vitrage.conf file ? If you do vitrage topology show do you get an error ? the log that you sent is it vitrage-api.log or vitrage.log ? Thanks Eyal On Wed, Apr 20, 2016 at 5:34 AM, wrote: Hi, Thanks for your response. There is no error about the request of alarms list in vitrage-graph log. Here is the vitrage-api log about the alarms error. Thank you for your help~ :) 2016-04-20 09:45:34.599585 2016-04-20 09:45:34.599 3700 DEBUG vitrage.service [-] static_physical.transformer= vitrage.datasources.static_physical.transformer.StaticPhysicalTransformer log_opt_values /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2525 2016-04-20 09:45:34.599844 2016-04-20 09:45:34.599 3700 DEBUG vitrage.service [-] log_opt_values /usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2527 2016-04-20 09:45:34.797687 2016-04-20 09:45:34.797 3700 INFO root [-] Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt 2016-04-20 09:45:34.848659 2016-04-20 09:45:34.848 3700 INFO root [-] Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt
[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: 答复: [probably forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage alarms list
Hi,
I exec all the vitrage cli and get the same error.
The log error is from /var/log/apache2/vitrage.log
Here is my config file.Thanks for your help~
BR
dwj
Eyal B
2016-04-20 14:10
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)"
收件人
"OpenStack Development Mailing List (not for usage questions)"
抄送
主题
[probably forge email可能是仿冒邮件]Re: [openstack-dev] 答复: [probably
forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage alarms list
Hi,
Can you send the local.conf file in your devstack folder ?
Can you send the /etc/vitrage/vitrage.conf file ?
If you do vitrage topology show do you get an error ?
the log that you sent is it vitrage-api.log or vitrage.log ?
Thanks
Eyal
On Wed, Apr 20, 2016 at 5:34 AM, wrote:
Hi,
Thanks for your response.
There is no error about the request of alarms list in vitrage-graph log.
Here is the vitrage-api log about the alarms error.
Thank you for your help~ :)
2016-04-20 09:45:34.599585 2016-04-20 09:45:34.599 3700 DEBUG
vitrage.service [-] static_physical.transformer=
vitrage.datasources.static_physical.transformer.StaticPhysicalTransformer
log_opt_values
/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2525
2016-04-20 09:45:34.599844 2016-04-20 09:45:34.599 3700 DEBUG
vitrage.service [-]
log_opt_values
/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2527
2016-04-20 09:45:34.797687 2016-04-20 09:45:34.797 3700 INFO root [-]
Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
2016-04-20 09:45:34.848659 2016-04-20 09:45:34.848 3700 INFO root [-]
Generating grammar tables from
/usr/lib/python2.7/lib2to3/PatternGrammar.txt
2016-04-20 09:45:34.950314 2016-04-20 09:45:34.950 3700 WARNING
oslo_config.cfg [-] Option "username" from group "keystone_authtoken" is
deprecated. Use option "user-name" from group "keystone_authtoken".
2016-04-20 09:45:34.951405 2016-04-20 09:45:34.951 3700 WARNING
keystonemiddleware.auth_token [-] signing_dir mode is 0755 instead of 0700
2016-04-20 09:45:35.351792 2016-04-20 09:45:35.351 3700 DEBUG
oslo_policy._cache_handler [req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] Reloading cached file
/etc/vitrage/policy.json read_cached_file
/usr/local/lib/python2.7/dist-packages/oslo_policy/_cache_handler.py:38
2016-04-20 09:45:35.352640 2016-04-20 09:45:35.352 3700 DEBUG
oslo_policy.policy [req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] Reloaded policy file:
/etc/vitrage/policy.json _load_policy_file
/usr/local/lib/python2.7/dist-packages/oslo_policy/policy.py:493
2016-04-20 09:45:35.353555 2016-04-20 09:45:35.353 3700 INFO
vitrage.api.controllers.v1.alarms
[req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] received list alarms with vitrage
id all
2016-04-20 09:45:35.376953 2016-04-20 09:45:35.376 3700 WARNING
oslo.messaging._drivers.impl_rabbit
[req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] Heartbeat support requested but it
is not supported by the kombu driver or the broker
2016-04-20 09:45:35.598523 End of script output before headers: app
Eyal B
2016-04-19 20:40
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)" <
openstack-dev@lists.openstack.org>
收件人
"OpenStack Development Mailing List (not for usage questions)" <
openstack-dev@lists.openstack.org>
抄送
主题
[probably forge email可能是仿冒邮件]Re: [openstack-dev] openstack-dev]
[vitrage] vitrage alarms list
Hi,
Thanks for your question.
Could you please look at the vitrage-graph log and send us the error
You can find this log in /opt/stack/logs
Eyal
On Tue, Apr 19, 2016 at 3:29 PM, wrote:
Hi vitrage folks,
I install virtage by devstack, but "vitrage --debug alarms list" cli
doesn't works.
I trace the code, and find where the code[1] caused the server error.
Does anyone have the problems? Thanks~
[1]
https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/alarms.py#L55
The cli log is as follows:
stack@OS:~/vitrage/vitrage/api/controllers/v1$ vitrage --debug alarms list
REQ: curl -g -i -X GET http://192.168.122.250:5000/ -H "Accept:
application/json" -H "User-Agent: keystoneauth1/2.4.0
python-requests/2.9.1 CPython/2.7.6"
Starting new HTTP connection (1): 192.168.122.250
"GET / HTTP/1.1" 300 599
RESP: [300] Content-Length: 599 Vary: X-Auth-Token Keep-Alive: timeout=5,
max=100 Server: Apache/2.4.7 (Ubuntu) Connection: Keep-Alive Date: Tue, 19
Apr 2016 12:40:59 GMT Content-Type: application/json
RESP BODY: {"versions": {"values": [{"status": "stable", "updated":
"2016-04-04T00:00:00Z", "media-types": [{"base": "application/json",
"type": "application/vnd.opens
[openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: openstack-dev] [vitrage] vitrage alarms list
Hi,
Thanks for your response.
There is no error about the request of alarms list in vitrage-graph log.
Here is the vitrage-api log about the alarms error.
Thank you for your help~ :)
2016-04-20 09:45:34.599585 2016-04-20 09:45:34.599 3700 DEBUG
vitrage.service [-] static_physical.transformer=
vitrage.datasources.static_physical.transformer.StaticPhysicalTransformer
log_opt_values
/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2525
2016-04-20 09:45:34.599844 2016-04-20 09:45:34.599 3700 DEBUG
vitrage.service [-]
log_opt_values
/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py:2527
2016-04-20 09:45:34.797687 2016-04-20 09:45:34.797 3700 INFO root [-]
Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
2016-04-20 09:45:34.848659 2016-04-20 09:45:34.848 3700 INFO root [-]
Generating grammar tables from
/usr/lib/python2.7/lib2to3/PatternGrammar.txt
2016-04-20 09:45:34.950314 2016-04-20 09:45:34.950 3700 WARNING
oslo_config.cfg [-] Option "username" from group "keystone_authtoken" is
deprecated. Use option "user-name" from group "keystone_authtoken".
2016-04-20 09:45:34.951405 2016-04-20 09:45:34.951 3700 WARNING
keystonemiddleware.auth_token [-] signing_dir mode is 0755 instead of 0700
2016-04-20 09:45:35.351792 2016-04-20 09:45:35.351 3700 DEBUG
oslo_policy._cache_handler [req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] Reloading cached file
/etc/vitrage/policy.json read_cached_file
/usr/local/lib/python2.7/dist-packages/oslo_policy/_cache_handler.py:38
2016-04-20 09:45:35.352640 2016-04-20 09:45:35.352 3700 DEBUG
oslo_policy.policy [req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] Reloaded policy file:
/etc/vitrage/policy.json _load_policy_file
/usr/local/lib/python2.7/dist-packages/oslo_policy/policy.py:493
2016-04-20 09:45:35.353555 2016-04-20 09:45:35.353 3700 INFO
vitrage.api.controllers.v1.alarms
[req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] received list alarms with vitrage
id all
2016-04-20 09:45:35.376953 2016-04-20 09:45:35.376 3700 WARNING
oslo.messaging._drivers.impl_rabbit
[req-beb876c2-edc0-4048-824d-df66ec926775 admin
6acd5010c0954e4388473acf8d133e25 - - -] Heartbeat support requested but it
is not supported by the kombu driver or the broker
2016-04-20 09:45:35.598523 End of script output before headers: app
Eyal B
2016-04-19 20:40
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)"
收件人
"OpenStack Development Mailing List (not for usage questions)"
抄送
主题
[probably forge email可能是仿冒邮件]Re: [openstack-dev] openstack-dev]
[vitrage] vitrage alarms list
Hi,
Thanks for your question.
Could you please look at the vitrage-graph log and send us the error
You can find this log in /opt/stack/logs
Eyal
On Tue, Apr 19, 2016 at 3:29 PM, wrote:
Hi vitrage folks,
I install virtage by devstack, but "vitrage --debug alarms list" cli
doesn't works.
I trace the code, and find where the code[1] caused the server error.
Does anyone have the problems? Thanks~
[1]
https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/alarms.py#L55
The cli log is as follows:
stack@OS:~/vitrage/vitrage/api/controllers/v1$ vitrage --debug alarms list
REQ: curl -g -i -X GET http://192.168.122.250:5000/ -H "Accept:
application/json" -H "User-Agent: keystoneauth1/2.4.0
python-requests/2.9.1 CPython/2.7.6"
Starting new HTTP connection (1): 192.168.122.250
"GET / HTTP/1.1" 300 599
RESP: [300] Content-Length: 599 Vary: X-Auth-Token Keep-Alive: timeout=5,
max=100 Server: Apache/2.4.7 (Ubuntu) Connection: Keep-Alive Date: Tue, 19
Apr 2016 12:40:59 GMT Content-Type: application/json
RESP BODY: {"versions": {"values": [{"status": "stable", "updated":
"2016-04-04T00:00:00Z", "media-types": [{"base": "application/json",
"type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.6",
"links": [{"href": "http://192.168.122.250:5000/v3/";, "rel": "self"}]},
{"status": "stable", "updated": "2014-04-17T00:00:00Z", "media-types":
[{"base": "application/json", "type":
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links":
[{"href": "http://192.168.122.250:5000/v2.0/";, "rel": "self"}, {"href": "
http://docs.openstack.org/";, "type": "text/html", "rel":
"describedby"}]}]}}
Making authentication request to http://192.168.122.250:5000/v2.0/tokens
"POST /v2.0/tokens HTTP/1.1" 200 4217
REQ: curl -g -i -X GET http://192.168.122.250:8999/v1/alarms/ -H
"User-Agent: keystoneauth1/2.4.0 python-requests/2.9.1 CPython/2.7.6" -H
"Accept: application/json" -H "X-Auth-Token:
{SHA1}2796e3695d7d641a96680ced6e85b55581745673"
Starting new HTTP connection (1): 192.168.122.250
"GET /v1/alarms/?vitrage_id=all HTTP/1.1" 500 613
RESP: [500] Date: Tue, 19 Apr 2016 12:40:59 GMT Con
[openstack-dev] openstack-dev] [vitrage] vitrage alarms list
Hi vitrage folks,
I install virtage by devstack, but "vitrage --debug alarms list" cli
doesn't works.
I trace the code, and find where the code[1] caused the server error.
Does anyone have the problems? Thanks~
[1]https://github.com/openstack/vitrage/blob/master/vitrage/api/controllers/v1/alarms.py#L55
The cli log is as follows:
stack@OS:~/vitrage/vitrage/api/controllers/v1$ vitrage --debug alarms list
REQ: curl -g -i -X GET http://192.168.122.250:5000/ -H "Accept:
application/json" -H "User-Agent: keystoneauth1/2.4.0
python-requests/2.9.1 CPython/2.7.6"
Starting new HTTP connection (1): 192.168.122.250
"GET / HTTP/1.1" 300 599
RESP: [300] Content-Length: 599 Vary: X-Auth-Token Keep-Alive: timeout=5,
max=100 Server: Apache/2.4.7 (Ubuntu) Connection: Keep-Alive Date: Tue, 19
Apr 2016 12:40:59 GMT Content-Type: application/json
RESP BODY: {"versions": {"values": [{"status": "stable", "updated":
"2016-04-04T00:00:00Z", "media-types": [{"base": "application/json",
"type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.6",
"links": [{"href": "http://192.168.122.250:5000/v3/";, "rel": "self"}]},
{"status": "stable", "updated": "2014-04-17T00:00:00Z", "media-types":
[{"base": "application/json", "type":
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links":
[{"href": "http://192.168.122.250:5000/v2.0/";, "rel": "self"}, {"href":
"http://docs.openstack.org/";, "type": "text/html", "rel":
"describedby"}]}]}}
Making authentication request to http://192.168.122.250:5000/v2.0/tokens
"POST /v2.0/tokens HTTP/1.1" 200 4217
REQ: curl -g -i -X GET http://192.168.122.250:8999/v1/alarms/ -H
"User-Agent: keystoneauth1/2.4.0 python-requests/2.9.1 CPython/2.7.6" -H
"Accept: application/json" -H "X-Auth-Token:
{SHA1}2796e3695d7d641a96680ced6e85b55581745673"
Starting new HTTP connection (1): 192.168.122.250
"GET /v1/alarms/?vitrage_id=all HTTP/1.1" 500 613
RESP: [500] Date: Tue, 19 Apr 2016 12:40:59 GMT Content-Length: 613
Content-Type: text/html; charset=iso-8859-1 Connection: close Server:
Apache/2.4.7 (Ubuntu)
RESP BODY:
500 Internal Server Error
Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator at
[no address given] to inform them of the time this error occurred,
and the actions you performed just before this error.
More information about this error may be available
in the server error log.
Apache/2.4.7 (Ubuntu) Server at 192.168.122.250 Port
8999
ZTE Information Security Notice: The information contained in this mail (and
any attachment transmitted herewith) is privileged and confidential and is
intended for the exclusive use of the addressee(s). If you are not an intended
recipient, any disclosure, reproduction, distribution or other dissemination or
use of the information contained is strictly prohibited. If you have received
this mail in error, please delete it and notify us immediately.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz
Hi Dulko, A VIM can't not detect certain NFVI fault. The external systems don't monitor the servise state. Fault as CPU failure, CPU condition not OK, Memory failure and network card failure, e.g. If the external systems detect the storage controller failure, Live migration if storage is still accessible; otherwise Hot Standby. So the c-v service state need to reflect it's real state. BR， dwj 董文娟 Wenjuan Dong 控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation 上海市浦东新区碧波路889号中兴通讯D3 D3, ZTE, No. 889, Bibo Rd. T: +86 021 85922M: +86 13661996389 E: dong.wenj...@zte.com.cn www.ztedevice.com ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Cinder] the spec of Add-ServiceGroup-using-Tooz
Hi all, I proposed the spec of Add-ServiceGroup-using-Tooz in Ciner[1]. Project doctor[2] in OPNFV community is its upstream. The goal of this project is to build fault management and maintenance framework for high availability of Network Services on top of virtualized infrastructure. The key feature is immediate notification of unavailability of virtualized resources from VIM, to process recovery of VNFs on them. But in Cinder, the service reports it's status with a delay. So I proposed adding Tooz as cinder ServiceGroup driver to report the service states without a dely. I'm a new in Cinder. :) So I wants to invite some Cinder exports to discuss the spec in the doctor's weekly meeting at 14:00 on Tuesday this week. Is anyone interested in it? Thanks~ [1]https://review.openstack.org/#/c/258968/ [2]https://wiki.opnfv.org/doctor 董文娟 Wenjuan Dong 控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation 上海市浦东新区碧波路889号中兴通讯D3 D3, ZTE, No. 889, Bibo Rd. T: +86 021 85922M: +86 13661996389 E: dong.wenj...@zte.com.cn www.ztedevice.com ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
