04:02:39 <ekcs> #startmeeting congressteammeeting
04:02:40 <openstack> Meeting started Fri Feb  8 04:02:39 2019 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:02:41 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:02:43 <openstack> The meeting name has been set to 'congressteammeeting'
04:02:46 <ekcs> hello!
04:03:03 <akhil_jain> ekcs: hello!
04:03:17 <ekcs> meeting topics here as usual. feel free to add yours! https://etherpad.openstack.org/p/congress-meeting-topics
04:03:42 <ekcs> hi akhil_jain !
04:03:51 <ekcs> how’s the week been?
04:04:49 <akhil_jain> Not much. Have been working on use cases mostly
04:05:17 <ekcs> ah that’s great.
04:05:40 <akhil_jain> What about you?
04:05:40 <ekcs> well let’s get started. might be a quick meeting.
04:05:58 <akhil_jain> Yes, seems so
04:06:05 <ekcs> I’m alright! keeping up with the usual project chores haha and working on the json things.
04:06:26 <akhil_jain> Haha. Yes i see
04:06:38 <ekcs> #topic feature freeze
04:06:58 <ekcs> just a heads up that feature freeze is less than 1 month away! 7 March 2019
04:07:56 <ekcs> that’s also the last week to release congress client. but afaik there isn’t something in the pipeline that’s going to require new client features. so we may not have to worry about thta.
04:08:35 <ekcs> what is important is that we try to prioritize so we get the features we most want reviewed and merged.
04:09:28 <ekcs> it may be helpful to do a quick inventory of what we’re hoping to finish in stein so we can prioritize.
04:10:23 <akhil_jain> One can be tacker driver BP
04:11:12 <ekcs> great I put that down in the meeting topic etherpad.
04:11:24 <akhil_jain> I will prioritise it and get it completed before release
04:11:29 <ekcs> all that’s left there is the tempest I think.
04:11:36 <akhil_jain> Ya right
04:12:29 <ekcs> some of the things like non-urgent bug fixes, doc changes, testing improvements can wait until the time between feature freeze and RC1 if necessary.
04:12:46 <ekcs> I think the upgrade check can wait.
04:13:16 <ekcs> there isn’t a whole lot of time there either (2 weeks), but it’s enough to get some last touches done before RC1.
04:13:41 <ekcs> I’ll be prioritizing json model implemenation.
04:14:00 <ekcs> if there’s something else I should also be prioritizing please let me know.
04:14:05 <akhil_jain> Oh great!
04:15:23 <ekcs> any questions or comments on feature freeze or RC dates?
04:15:43 <akhil_jain> Not from my side
04:16:14 <ekcs> cool. moving on then.
04:16:30 <ekcs> #topic patches
04:16:36 <ekcs> any patches we need to discuss here?
04:17:21 <akhil_jain> I think discussion on gerrit solved conflicts
04:17:32 <ekcs> great.
04:17:57 <akhil_jain> Any patch left to discuss?
04:18:28 <ekcs> just want to quickly mention this patch: simple one we can hopefully merge quickly because the person working on the hacking version-up does not seem very familiar with git rebasing to a new parent. so merging it would make things easier.
04:18:28 <ekcs> just want to quickly mention this patch: simple one we can hopefully merge quickly because the person working
04:18:31 <ekcs> https://review.openstack.org/#/c/634339/
04:18:32 <patchbot> patch 634339 - congress - move config init from congress_servers.py to bin/c... - 3 patch sets
04:18:51 <ekcs> that’s all for me.
04:19:31 <ekcs> ok moving on then.
04:19:38 <akhil_jain> Yes i have tested on my env. Was working
04:20:00 <akhil_jain> But not sure. About changes so didnt commented
04:22:21 <ekcs> ok got it. well I think I’ll go ahead and merge then if no objections. can always bring it back up if there are objections.
04:23:06 <ekcs> but if you have any potential concerns then we can hold off.
04:23:12 <akhil_jain> ok LGTM!
04:23:28 <akhil_jain> no please go ahead
04:23:40 <ekcs> thanks!
04:23:45 <ekcs> #topic open discussion
04:23:55 <ekcs> anything else on our minds?
04:24:21 <ekcs> is there anything you need on the use case front? def happy to help in this important work.
04:24:42 <akhil_jain> cfgValidator is one I am stuck at
04:25:26 <ekcs> ok. can you say a bit more about the problem?
04:26:12 <akhil_jain> not sure how to show its usage actually
04:26:48 <ekcs> I see. is it because it doesn’t actually cause any action?
04:26:54 <ekcs> so it’s a bit different?
04:27:16 <akhil_jain> so any basic idea is required. that we can do this with it.
04:30:20 <ekcs> hmmm. so the way I’m looking at it, a good test/demo is simply that it monitors the config according to our rules. If I were demoing, I would put in an example rule. install the congress-agent to monitor configs on an openstack controllers node (either same server as congress or not). then show that when I change the configs to violate the rule, then query congress, congress shows the violation.
04:31:50 <ekcs> one step further could be te define an alert action in congress so warn on config violations. mistral driver has many useful actions for alert such as email someone.
04:32:52 <akhil_jain> many thanks Eric, I think I can proceed with this
04:33:12 <ekcs> one question is: are you aiming do create automated tests? or manual demos?
04:34:14 <akhil_jain> manual only for now. as i need to give presentation on the same
04:34:31 <akhil_jain> so manual will be easier to explain
04:34:33 <ekcs> for automated tests, a congress policy table rows query would check that the violation is caught. for demo, the horizon monitoring pane could be helpful.
04:35:36 <akhil_jain> not using horizon acually.only via cli.
04:36:02 <ekcs> ah ok.
04:36:40 <akhil_jain> adding policy files here as of now. numbered according to google sheet
04:36:41 <akhil_jain> https://github.com/akhiljain23/congress_scenarios/tree/master/samples
04:36:45 <ekcs> well so the idea information on violations can be used by any tool querying congress. or checked manually, or seen in monitoring pane.
04:37:06 <ekcs> oh great!
04:38:06 <ekcs> ok well. as you already know feel free to ping me any time.
04:38:18 <akhil_jain> You mean we need to use row list from policy table . right?
04:38:26 <ekcs> yes.
04:38:54 <akhil_jain> thanks Eric. for supporting as always
04:39:02 <ekcs> =p
04:39:12 <ekcs> of course.
04:39:27 <ekcs> ok do we have anything else to talk about today?
04:39:35 <ekcs> i don’t have anything else.
04:39:47 <akhil_jain> That will be it, from my side as well
04:40:07 <ekcs> cool. lets wrap up then.
04:40:13 <ekcs> happy friday and have a great weekend!
04:40:44 <akhil_jain> Thanks and same to you, Bye!
04:40:50 <ekcs> bye!
04:40:52 <ekcs> #endmeeting