Friday, 2017-02-03

*** hidekazu has joined #openstack-watcher00:33
*** hidekazu has quit IRC00:46
*** thorst_ has quit IRC01:20
*** thorst_ has joined #openstack-watcher01:21
*** thorst_ has quit IRC01:25
*** zhurong has joined #openstack-watcher01:52
*** thorst_ has joined #openstack-watcher02:00
*** thorst_ has quit IRC02:00
*** hidekazu has joined #openstack-watcher02:19
*** thorst_ has joined #openstack-watcher02:32
*** thorst_ has quit IRC02:32
*** zhurong_ has joined #openstack-watcher03:36
*** zhurong has quit IRC03:38
*** thorst_ has joined #openstack-watcher03:58
*** thorst_ has quit IRC03:58
*** zhurong_ has quit IRC04:11
*** thorst_ has joined #openstack-watcher04:21
*** thorst_ has quit IRC04:21
*** diga has joined #openstack-watcher04:40
*** gabor_antal_ has quit IRC06:10
*** thorst_ has joined #openstack-watcher06:22
*** thorst_ has quit IRC06:27
*** zhurong has joined #openstack-watcher06:45
openstackgerritZeyu Zhu proposed openstack/python-watcherclient master: Using jsonutils instead of json
openstackgerritAntoine Cabot proposed openstack/watcher master: Update release notes with Ocata branch
openstackgerritAntoine Cabot proposed openstack/watcher-dashboard master: Add Ocata release notes
*** alexchadin has joined #openstack-watcher08:20
*** thorst_ has joined #openstack-watcher08:23
*** vincentfrancoise has joined #openstack-watcher08:23
*** thorst_ has quit IRC08:28
openstackgerritZeyu Zhu proposed openstack/watcher master: Using items() instead of six.iteritems()
openstackgerritMerged openstack/watcher-dashboard master: Update reno for stable/ocata
openstackgerritMerged openstack/python-watcherclient master: Using jsonutils instead of json
openstackgerritMerged openstack/watcher master: Update reno for stable/ocata
openstackgerritMerged openstack/watcher master: Use RPC cast() to be asynchronous
openstackgerritAlexander Chadin proposed openstack/watcher master: Add Action Notification
*** dtardivel has joined #openstack-watcher09:33
openstackgerritMerged openstack/watcher master: Using items() instead of six.iteritems()
alexchadinvincentfrancoise: hi09:54
vincentfrancoisealexchadin: morning09:54
*** zhurong has quit IRC09:55
alexchadinI am trying to rebase my action notification patch set and found out that ActionPlanPayload now requires action_plan, audit, strategy to initialize09:56
alexchadinvincentfrancoise: actually, I don't need strategy and audit to build action payload09:56
vincentfrancoisealexchadin: let me see your code (1sec)09:57
vincentfrancoiseThe way I solved this in audit was by creating a new payload type that was TerseAuditPayload (as opposed to AuditPayload)09:58
vincentfrancoiseThe problem is that you need to load the UUIDs in your payload even though you don't want all the rest09:59
vincentfrancoiseso in your ActionPlanPayload, what you want is "strategy_uuid" and "audit_uuid" but not strategy and not "audit"10:00
alexchadinso, I need to get strategy_uuid and audit_uuid from action_plan to give it to __init__?10:01
vincentfrancoiseyes, it's a pain because we have the ID for both but not the UUIDs10:01
vincentfrancoiseso in my case I needed to do an extra query to get the UUID10:02
vincentfrancoisealexchadin: what you need to do should be similar to
vincentfrancoisealexchadin: and
alexchadinI see10:03
alexchadinIs there some notification agreements in OpenStack? Oslo.Messaging rules it?10:04
vincentfrancoisealexchadin: actually there was a bug in the audit notifications that missed the goal_uuid and strategy_uuid fields10:05
vincentfrancoisealexchadin: there is no real agreement per se, but implicitely everyone uses versioned notifications with oslo.versionedobjects and oslo.messaging10:06
*** hidekazu has quit IRC10:15
*** thorst_ has joined #openstack-watcher10:24
*** thorst_ has quit IRC10:29
alexchadinacabot: what is IRC Handle of Yumeng Bao?11:33
*** alexchadin has quit IRC11:42
*** diga has quit IRC12:32
*** alexchadin has joined #openstack-watcher12:33
*** thorst_ has joined #openstack-watcher12:37
*** alexchad_ has joined #openstack-watcher12:44
*** alexchadin has quit IRC12:47
*** vmahe has joined #openstack-watcher12:53
*** vmahe has left #openstack-watcher12:56
*** zhurong has joined #openstack-watcher13:09
vincentfrancoisealexchad_: it's YumengBao but he's not connected it seems13:09
chrisspencero/ hi all13:18
vincentfrancoisechrisspencer: hi13:18
*** alexchadin has joined #openstack-watcher13:18
*** alexchad_ has quit IRC13:20
*** Yumeng__ has joined #openstack-watcher13:38
*** edleafe is now known as figleaf14:07
*** alexchadin has quit IRC14:29
chrisspencervincentfrancoise: After reading through documentation for the last couple of days I noticed that there is a variable called logging_context_format_string that will need to change so we can display our context settings in our logging.  Currently for devstack (how we gate test?) we have a setup file in watcher/devstack/lib/watcher.   Do we want to change this14:29
chrisspencerinit value here to include our variables or should I dynamically change it in the code?  I feel like making the initialization change in the setup file makes it an easier change, and doing it dynamically probably requires me to figure out how to undo the modification (figure out what the initial value is in the conf file)14:29
chrisspencersorry for the length of the message :)14:29
vincentfrancoisechrisspencer: good question :p14:35
vincentfrancoisechrisspencer: IMHO, we should do it the same way other projects handle it in their devstack plugin14:35
chrisspencervincentfrancoise: meaning, leave the setup file like others have it, and just modify the setting when we need to?14:36
vincentfrancoisechrisspencer: so after looking at the nova devstack plugin I found this which executes this function
chrisspencerso they are changing the logging_context_format_string:
chrisspencerchanging is the incorrect word.  Setting the default*14:38
vincentfrancoisechrisspencer: yeah I understood you ;)14:39
vincentfrancoisechrisspencer: if I understand it correctly, setting the context like I proposed you should have affected logging_context_format_string set here:
vincentfrancoisechrisspencer: and you have set request_id which is also mentioned in "%(request_id)s"14:43
chrisspencervincentfrancoise: do we care about the event_type?  I was attempting to add the publisher and event in addition to the already captured items of  request, username, and project name.14:46
vincentfrancoisechrisspencer: the request ID is the least we need14:47
vincentfrancoisethe rest is bonus14:48
chrisspencerok sounds good. I'll work on getting at least that :)14:48
vincentfrancoisechrisspencer: this one
vincentfrancoisechrisspencer: it has its request ID logged (see
vincentfrancoisechrisspencer: so maybe the is_admin plays a role, I don't know14:55
chrisspencervincentfrancoise: good find! thanks.  I'll try it out14:58
*** gabor_antal has joined #openstack-watcher15:11
*** Yumeng__ has quit IRC16:01
*** zhurong has quit IRC16:34
*** vincentfrancoise has quit IRC17:08
pshedimbheads up to guys using devstack multi node to develop watcher17:18
pshedimbNova changed its work flow, and now introduced placement api as a mandatory companent17:19
pshedimbSo the latest devstack wouldn't work unless you include placement conf in nova.conf file17:20
pshedimbAnd need to run this command on controller after adding placement conf on compute nodes17:21
pshedimbnova-manage cell_v2 discover_hosts17:21
*** d34dh0r53 has quit IRC17:56
*** d34dh0r53 has joined #openstack-watcher17:56
*** dtardivel has quit IRC19:14
*** wootehfoot has joined #openstack-watcher21:49
*** thorst_ has quit IRC22:25
*** figleaf is now known as edleafe23:17
openstackgerritAlex Schultz proposed openstack/puppet-watcher master: Prepare ocata-rc1 release

Generated by 2.14.0 by Marius Gedminas - find it at!