04:02:58 #startmeeting congressteammeeting 04:02:59 Meeting started Fri Apr 19 04:02:58 2019 UTC and is due to finish in 60 minutes. The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:03:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:03:02 The meeting name has been set to 'congressteammeeting' 04:03:18 ekcs: Hi 04:03:50 hi akhil_jain ! 04:04:14 How's everything? 04:05:13 not too bad. always interesting when preparing presentations. helps point out how much I don’t know about a particular application like nfv. 04:05:17 how are you? 04:06:02 topics list here as usual: https://etherpad.openstack.org/p/congress-meeting-topics 04:06:08 I am good. Yes seen your work for presentation, thats really cool 04:07:56 great! 04:08:01 well let’s get going then. 04:08:07 #topic lower constraints 04:08:47 so it turns out for some reason the lower constraints job wasn’t set up quite right. and congress unit tests fail on some of the lower constraints. https://review.openstack.org/#/c/650441/ 04:09:08 it’s going to take some effort to figure out whats failing and probbaly to raise to lower constraints appropriately. 04:10:22 just an update. don’t think there’s much to talk about here. 04:10:32 so moving on to next topic. 04:10:52 #topic monasca-tacker-congress talk 04:11:37 so akhil_jain I know you haven’t had much of a chance to look deeply yet. but if there’s any questions or comments to discuss now we could take the opportunity 04:14:09 yes I have made one comment. actually the main scenario is tacker respawn on detecting the fault. but as of now what tacker does is launches new instances with all new IPs assigned so from user perspective that wont be much useful. so i used nova evacuate. it is something missing from tacker end. we can add this point in session as well 04:15:07 ok I’ll make sure to mention that as a fault management action. 04:15:10 also for demo i have started created new env. old one is not working 04:16:01 also i will test respawn api once env is ready and let you know 04:16:02 oh got it any idea why? just something not right any more or maybe evidence of possible congress bug? 04:16:31 no it is from tacker side only 04:16:43 ok cool. 04:17:25 by the way, what’s wrong with a new instance with a different IP? I imagine usually there are many VNF instances behind a load balancer. so respawning a new instance with new IP works ok? 04:19:42 amm, i am not sure about it but while discussing with Ghanshyam mann he stated if instance is being used anywhere and it need to be recreated with all new network and resources. it wont be fulling its old use 04:20:07 like its whole identity will be changed 04:20:51 ok. I guess it all depends on the networking setup. there are cases when we want to keep that specific instance. 04:22:10 yes, that is case, but if you think ip doesnt matter. we can display respawn as well from tacker side 04:23:01 I’ll just mention it as a possible response along with the others. 04:23:21 well that’s helpful. do please leave more comments if you have any later. especially helpful would be any insight into the particular requirements of the nfv eco system that i am not clear on. 04:23:30 moving on then if nothing else on this topic? 04:23:48 yes nothing more as of now 04:24:19 ok! 04:24:23 #topic Train cycle feature targets 04:25:55 thanks for putting up the topic. good time to start thinking and discussing train targets. 04:27:21 yes I want to finalize my targets for this cycle and share with my client 04:28:53 need your help to get some features to work on 04:29:32 ok do you already have thoughts on what’s important for the client? maybe start with collecting that info. 04:31:26 its more on self-healing side. but nothing fixed as of now. so I want to continue the same till then 04:32:36 Do you have any feature on your mind pending to be implemented in congress. I would like to work on that 04:33:18 I’m in the process of updating this backlog: https://etherpad.openstack.org/p/congress-task-priority 04:34:14 the ones that have most to do with self healing seem like these: 04:34:16 feedback on action executions 04:34:21 results 04:35:01 execute-repeat semantic 04:35:32 and other execution semantics to be determined by that disucssion depending on use case. 04:36:14 I think priority really depends on client use case. 04:38:16 yes, but i have option to propose usecases and related development work as well 04:39:05 i will look into the features you shared, and thanks again for help as always 04:41:18 ok got it. why don’t we schedule another time to talk about this specifically? 04:41:34 yes that would be great 04:42:44 ok cool. should we stop here for today then? 04:42:50 also there is one more that to be discussed 04:42:53 https://review.openstack.org/#/c/652294/ 04:43:12 i think it is failing because of psycopg==2.5.1 04:43:37 which is not installable on bionic (i think) 04:44:16 we can discuss it on gerrit later on 04:44:34 hmm. that is a problem, but I don’t htink it’s the problem here. 04:44:55 because the psycopg==2.5.1 lower costraint should not affect the other jobs. 04:45:28 also we haven’t actually merged that patch on master branch. https://review.openstack.org/#/c/650095/ 04:46:20 hmm, i will look into it again 04:47:41 seems it DOES have to do with psycopg, but not the low version. 04:47:46 look at the end of this file: http://logs.openstack.org/94/652294/1/check/openstack-tox-py27/aa62bb4/tox/py27-1.log 04:48:50 I’m guessing this patch caused the failure: https://github.com/openstack/requirements/commit/a96ee0e258aafb2880149b3e25dd5959f7b37c09 04:49:56 yes that can be the reason 04:52:09 surprised I don’t see a discussion on ML already or a bug filed. should be breaking others as well. maybe not enough projects depend on it so it’ll take a little longer. 04:52:23 guess we’ll have to figure it out / start that conversation. 04:55:36 same problem discussed here, but not clear what the solution is yet: https://github.com/Cloud-CV/EvalAI/issues/1480 04:57:21 here’s a better discussion: https://github.com/psycopg/psycopg2/issues/699 04:59:20 ok time to end meeting =) 04:59:32 have a great weekend! 04:59:33 #endmeeting