04:01:43 <ekcs> #startmeeting congressteammeeting
04:01:44 <openstack> Meeting started Fri Oct 19 04:01:43 2018 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:01:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:01:47 <openstack> The meeting name has been set to 'congressteammeeting'
04:02:10 <ekcs> hi all! topics kept here as usual. feel free to add your topics =)
04:02:11 <ekcs> https://etherpad.openstack.org/p/congress-meeting-topics
04:03:27 <akhil_jain> ekcs: Hi
04:03:41 <ekcs> hi akhil_jain ! how’s it going?
04:04:18 <akhil_jain> Everything perfect. Its festive season in India
04:04:39 <akhil_jain> How about you?
04:04:44 <ekcs> oh great!
04:05:08 <ekcs> well why don’t we start with your topic akhil_jain ?
04:05:13 <ekcs> #topic tacker driver
04:06:04 <akhil_jain> yes, after that meeting with my team members. i have been working on achieving whole use case
04:06:43 <ekcs> that’s great! I see your patches coming in =)
04:06:44 <akhil_jain> so for that i have made one dummy policy and want you to look into that
04:07:16 <akhil_jain> openstack congress policy rule create classification "efinal(vnf_id) :- monasca_webhook:alarm_notification(alarm_id=x, state='ALARM'), monasca_webhook:alarms.metrics(alarm_id=x, dimensions=dim), monasca_webhook:alarms.metrics.dimensions(id=dim, key='hostname', value=value), nova:servers(id=n_id, host_name=value), nova:server.addresses(server_id=n_id, ip_address=ips), tacker:vnfs.instances(instance_ip=ips,
04:07:16 <akhil_jain> vnf_id=vnf_id), tacker:vnfs(id=vnf_id, status='ACTIVE')"
04:07:43 <akhil_jain> so for this I had to make changes in nova driver
04:08:33 <akhil_jain> that mainly involve getting IP addresses of all nova servers. to map them with vnf instances of tacker
04:09:21 <akhil_jain> So I am open for suggestion, if am going wrong. or some other approach is correct. please share
04:10:14 <ekcs> yes I see the nova patch you submitted. that makes sense!
04:10:22 <ekcs> I’m studying the rule a bit right now.
04:11:07 <ekcs> can you say roughly what efinal is meant to capture?
04:11:17 <akhil_jain> ok sure
04:11:26 <ekcs> looks like...
04:11:55 <ekcs> servers with alarm state which are also associated with active vnfs somehwo?
04:14:01 <akhil_jain> what i am trying to do is. first monasca will send alarm to congress with hostame,  then congress will fetch all servers from nova with that hostname and finally we will get ip from nova and using that ip we can get vnf id from tacker  that contain instances with that ip. and we can delete_vnf or anything  like respawn
04:14:28 <ekcs> got it!
04:14:59 <ekcs> yea that makes sense as far as I can see!
04:15:53 <akhil_jain> also it was one of thing that even if host is down, the vnf still show active state. so we have to tacke action on that as well. so i was trying to do that in last rule line
04:16:39 <ekcs> I see. if vnfs shows inactive then nothing needs to be done from congress because tacker already takes care of it somehow?
04:16:45 <akhil_jain> if for now it looks ok. i can document this rule in congress/library for further ref
04:16:57 <ekcs> yes that’d be great!
04:17:02 <akhil_jain> ya, right
04:18:54 <akhil_jain> so thats it from my side for tacker driver discussion
04:20:11 <ekcs> very cool! awesome progress!
04:20:22 <akhil_jain> thanks :)
04:20:27 <ekcs> I’m trying to figure out something about the addresses.
04:21:50 <ekcs> oh I see. it’s designed to capture only the addresses under ‘net_mgmt'
04:22:05 <akhil_jain> that also i discussed with tacker PTL, even he said we should add hostname field in tacker in future. so that nova doesnt come into picture
04:22:55 <akhil_jain> ya, right.
04:23:43 <ekcs> got it! yea that looks great overall! I have a suggestion I’ll put on gerrit.
04:24:02 <ekcs> I guess we’re done with this topic for now?
04:24:06 <akhil_jain> ok great
04:24:08 <akhil_jain> yes
04:24:24 <ekcs> great
04:24:27 <ekcs> #topic gate
04:24:53 <ekcs> so we already saw that gate was broken for a few days since middle of the week last week.
04:25:43 <ekcs> anyway it turns out to be a oslo-messaging bug. #link https://bugs.launchpad.net/bugs/1798241
04:25:43 <openstack> Launchpad bug 1798241 in oslo.messaging "transport_url without trailing '/' considered virtual host 'None'" [High,In progress] - Assigned to Ken Giusti (kgiusti)
04:25:59 <ekcs> gate was back working after we merged a work-around.
04:26:18 <ekcs> oslo-messaging is working on the bug on their side too.
04:26:54 <ekcs> I see a fix as already proposed and being reviewed.
04:27:29 <ekcs> the other thing is gate seems to have been extremely slow in recent days.
04:28:38 <ekcs> I’m not sure why exactly. Not sure if something changed on infra resource available. But I see some discussion on ML and maybe things will be clearer soon!
04:29:42 <ekcs> that’s all the update I have on the gate.
04:30:13 <akhil_jain> yes it is very slow. my patch that i pushed 21 hours ago is still running on gate
04:30:45 <ekcs> here’s the oslo-messaging patch btw #link https://review.openstack.org/#/c/611683/1
04:31:11 <ekcs> yup.
04:31:33 <ekcs> ok well that’s all from me unless we have more patches to discuss or anything else?
04:31:53 <ekcs> btw thanks akhil_jain for the work on upgrade check!
04:31:54 <akhil_jain> nothing from my side
04:32:23 <akhil_jain> yes, we can discuss on what checks we need
04:32:44 <ekcs> perfect.
04:32:53 <ekcs> alright why don’t we end for today then?
04:33:25 <akhil_jain> ya, its a placeholder patch anyways. we can keep updating that afterwards
04:33:55 <ekcs> great well have a great weekend!
04:34:18 <akhil_jain> Thanks and you too! Bye!
03:11:09 <truongnh___> Could anyone help me to list what metrics are using in Live Migration of Masakari, please
16:00:34 <openstack> mlavalle: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
16:01:22 <mlavalle> hi, will the Congress meeting be over soon?
16:01:29 <njohnston> o/
16:01:39 <rubasov> o/
16:01:52 <clarkb> mlavalle: anyone can stop a meeting after one hour. If you issue #endmeeting it should stop the existing meeting
16:02:10 <rubasov> mlavalle: there was not much said before
16:02:23 <mlavalle> clarkb: yhanks. I know. I was just trying to be polite
16:02:29 <rubasov> mlavalle: so I think they accidentally left it open
16:02:35 <mlavalle> #endmeeting