08:00:35 #startmeeting vitrage 08:00:36 Meeting started Wed Jan 10 08:00:35 2018 UTC and is due to finish in 60 minutes. The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:39 The meeting name has been set to 'vitrage' 08:00:42 Hi :-) 08:00:47 \0/ 08:02:03 Hi 08:02:14 hi 08:02:33 Today’s agenda: 08:02:48 * Status, updates and Queens roadmap follow-up 08:02:53 * Open discussion 08:03:04 #topic Status, updates and Queens roadmap follow-up 08:03:11 Queens release timeframe: 08:03:16 The release deadline for python-vitrageclient: January 25 08:03:25 This is also the (recommended) feature freeze 08:03:30 The release candidate deadline is February 5-9 08:04:06 My updates: I almost finished the code for supporting get_attr function in the templates, and I verified that it works for Mistral workflow 08:04:32 All I have left to do is to update the validators with the function syntax, and add documentation. I will finish it today or tomorrow 08:04:41 #link https://review.openstack.org/#/c/532274/ 08:04:48 That’s it for me 08:06:06 I will update, for a few people not present here 08:06:26 We have three features at risk: 08:06:32 1. Graph persistancy - storing the events and acationalay the entire graph, so virtrage can be restarted and load from the database. 08:06:39 This is important for very large deployments. this is likly to finish on time, but will be turned off by default. 08:06:44 #link https://review.openstack.org/#/c/530650/ 08:06:50 2. Template crud - allow for template add/remove via api without restarting Vitrage. only the evaluator workers are restarted. 08:06:55 The work in this feature is onging and may not end in time, i it will be ready despite the complexity. 08:07:00 #link https://review.openstack.org/#/c/530640/ 08:07:07 3. Webhooks - allow the use to receive notifications according to filters, this is very close to being finished. 08:07:13 #link https://review.openstack.org/#/c/530587/ 08:07:25 I think these are important features, and we should try hard to finish on time, even if it will be at the end of the version. 08:08:18 I agree 08:08:23 +1 08:08:59 For the template CRUD, we should push the new API by January 25, if we believe that the backend will be ready (the backend development can delay a bit after that date) 08:09:30 I’m about to finish with my Mistral tasks this week, so I’ll be able to help if needed 08:09:31 Hi 08:10:02 Other tasks that I thought of taking are either the NetworkX 2.0, or to help with the tempest tests 08:10:22 We have only two weeks left for the feature freeze... 08:10:30 I will update 08:11:06 working with on separating the tempest tests from vitrage 08:11:21 this is an on going work will take some time 08:11:38 we already have 40 patches :-( 08:11:47 #link https://review.openstack.org/#/c/528528/ 08:12:12 only 40 :) 08:12:18 we also need to seperate the dependency between vitrage-tempest and vitrage 08:12:19 by now ;-) 08:12:41 which is a major refactoring 08:12:56 Any chance this will be done in Queens? 08:13:30 tempest is an e2e test should be able to run on a machine with no vitrage 08:13:32 And any chance the tempest separation can work without the complete refactoring? 08:13:47 maybe I dont know 08:13:59 for now it can work 08:14:05 with workarounds 08:14:56 So you are trying to fix the build failure and hoping it will work without the refactoring? 08:15:03 yes 08:15:13 OK 08:15:19 thats it 08:15:51 My updates. 08:16:12 I was inspecting the code about state aggregation and action tracker 08:16:38 Almost done 08:16:49 I will amend the suspect alarm blueprint after that 08:17:10 That's it 08:17:14 Ok, thanks 08:17:36 Are you planning to implement some of the new features in Queens, or will they be postponed to Rocky? 08:18:28 Some of the new features are easy to implement, but not as important as this one. 08:18:42 I want to clarify this one first 08:18:48 Makes sense 08:18:58 And during the document review, may got sometime to work on other small features. 08:19:53 Ok. So some of the specs will eventually move to Rocky folder (we can do it later) 08:20:09 Or maybe we can keep them under queens/approved 08:20:55 Yes, I think we can do the movement for Rocky after PTG 08:21:08 Ok 08:21:26 And speaking of the PTG - I have no updates yet. Didn’t see any email with a schedule for the PTG 08:21:34 I also see some projects holds a backlog directory for approved but suspended blue prints 08:21:41 But you are all welcome to start adding ideas for the discussions 08:21:51 Which encourage contributors to pick them up 08:22:21 #link http://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html 08:22:27 #link https://etherpad.openstack.org/p/vitrage-ptg-rocky 08:23:10 I didn't see update from PTG organizer 08:23:13 But I saw activity in other projects similar to us 08:23:44 The backlog could be an idea. But in your case I guess you plan to implement those specs, just in Rocky 08:23:45 #link https://etherpad.openstack.org/p/oslo-ptg-rocky 08:24:47 We may copy some of its format to make the schedule together 08:24:59 What do you mean? 08:25:17 I mean put driver, topic, description, who's interested and etc 08:25:33 Ok 08:26:22 We have more than a month to plan the PTG, but I think it’s a good time to start adding ideas 08:26:58 Anyone else has updates, before we move on? 08:27:10 Hi, I'll update for snmp parsing service. 08:27:23 I have finished distributing parsed snmp traps to the RabbitMQ queue and relative test cases. This bp is almost done.:) 08:27:58 Great. Do you think it will be finished for Queens? 08:28:09 Yes. 08:28:16 :-) 08:28:19 #link https://review.openstack.org/#/c/532381/ 08:28:20 Great :-) 08:28:31 Codes of alarm datasource processing snmp trap and config file are added in functional test case because there is no snmp triggered alarm in true environment for now. 08:28:40 Users can add the codes to their alarm datasource when true snmp triggered alarm is supported. 08:29:24 Ok, I’ll have a look later today 08:29:27 My updates. Still working on support Vitrage in TripleO. I try to install undercloud and then merge my code to deploy vitrage in overcloud. But many issues of installing undercloud, troubleshooting now : ( 08:29:37 Ok. 08:30:08 dwj: Thanks for taking care of it 08:30:20 Sounds complicated... 08:30:44 : ( 08:31:21 crying face~ 08:31:38 You’ll make me cry too… :-( 08:31:41 Is this on gerrit? 08:32:04 No, I want to pass the test and then post the code to gerrit 08:32:36 To tripleo gerrit? 08:33:02 Yes. 08:33:25 Ha, OK, good luck :) 08:33:56 Good luck 08:34:02 Anyone else wants to update? 08:34:13 I think it can not be finished in Queens release, so maybe it's better to pass the test and then post to TripleO gerrit . 08:35:07 I didn’t understand. The test is the first thing that you do, and then there are other tasks that you won’t finish for Queens? 08:37:53 Do you mean test with basic integration only? 08:38:05 And after it passed, there could be more steps 08:38:10 More than 3 projects are needed to fix and to deploy the env 08:39:34 So you are thinking of adding to Queens whatever you manage to finish by then, and the rest will be postponed to Rocky? I think it makes sense, but it probably depends on how TripleO manage it 08:40:54 Yes. 08:41:40 Ok 08:42:21 Any other updates? 08:43:40 #topic Open Discussion 08:44:45 I have one issue: I got an email regarding Story Board. Story Board should eventually replace launchpad, and some of the projects already migrated to it 08:45:10 I've used that before in another project 08:45:15 We were asked to migrate as well. We should think when would be a good time. Personally, I prefer to finish the Queens urgent tasks first. 08:45:28 If you already know how to work with it, it will definitely help 08:45:45 Anyway, I haven’t really checked it yet, just saw the email before the meeting 08:47:34 I also think it is not urgent. Maybe we can put it as a topic on PTG 08:47:35 That’s it for now, I think 08:47:42 Sounds good 08:47:58 Any other issue to discuss? 08:48:14 There is another event in March, the Open Networking Summit 2018 08:48:26 Are you attending it? 08:48:42 Probably 08:48:57 OPNFV Summit is merged into this event 08:49:22 Any of you plan to attend it? 08:49:31 I’m not sure 08:49:39 mayabe you can "sell" vitrage :-) ? 08:49:46 #link https://events.linuxfoundation.org/events/open-networking-summit-north-america-2018/ 08:49:47 I didn’t know about it until now... 08:50:40 The CFP ends on Jan 14, if you have any ideas to propose eyalb :-) 08:51:11 "vitrage the solution for your cloud " :-) 08:52:15 yujunz: are you going to submit session proposals? anything you had in mind? 08:52:51 I have a proposal submit about OPNFV Clover project which I am currently focusing on 08:52:55 BTW, I believe we will soon be asked to submit session propsals for Vancouver 08:53:07 What’s Clover? 08:53:22 Clover = Cloud Native for NFV 08:53:40 Isn’t it what OPNFV is all about? why is it a separate project? 08:54:13 And how does it integrate with Vitrage? ;-) 08:54:14 OPNFV is not about NFV integration and testing 08:54:55 Not much related so far 08:55:12 Ok 08:55:24 Any other issue? we have 5 more minutes 08:57:07 Let’s close the meeting 08:57:09 Bye :-) 08:57:18 bye 08:57:21 Bye 08:57:23 Bye 08:57:29 #endmeeting