14:01:15 #startmeeting smaug 14:01:18 Meeting started Tue May 17 14:01:15 2016 UTC and is due to finish in 60 minutes. The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:22 The meeting name has been set to 'smaug' 14:01:23 Hey 14:01:26 hi 14:01:29 hi 14:01:45 Are we waiting for anyone? 14:02:03 Does anyone know if yinwei wanted to attend? 14:02:12 hi 14:02:44 she is sick 14:03:27 xiangxinyong: I've heard I've spoken with her today and she was feeling fine. But she probably doesn't want to over exert herself. 14:03:36 So lets start 14:03:55 #topic meeting time 14:04:17 We want to make the meeting weekly but in different times. 14:04:27 hi 14:04:34 I've sent an email to the mailing list but I didn't get a lot of responses. 14:05:08 i think the time is very suitable for the eastern side 14:05:09 Does anyone have any objection to the suggestion of: 14:05:09 - 15:00 UTC for west, biweekly-even 14:05:09 - 09:00 UTC for east, biweekly-odd 14:05:19 +1 14:05:24 We can always change it later 14:05:24 +1 14:05:27 looks good to me 14:05:36 I think it is good. 14:05:41 sound good to me 14:05:46 :) 14:05:47 +1 14:05:55 Then I'll submit a patch to change it. 14:06:06 thanks saggi 14:06:27 Hopefully next week we'll have more west hemisphere people in here :) 14:06:50 #action send patch to update meeting time (saggi) 14:07:10 Is the bot asleep? 14:07:33 :) 14:07:41 ^-^ 14:07:44 #info test 14:07:55 Let's hope this is getting logged 14:08:17 saggi: :) 14:08:36 #topic Status updates 14:08:51 He's just being selective 14:09:37 Anyway, I just want to know what is everyone in china working on and to make sure no one is blocked. 14:10:34 nothing? 14:10:44 https://etherpad.openstack.org/p/smaug 14:10:55 saggi: you could take a look at this 14:11:47 chenying can you share about  Design and development of replication plug-in 14:11:49 I am working on the Integration Test on the master branch. It does not work now. Some patches need be merged. 14:12:01 xiangxinyong: thanks, but not everyone has a task there. 14:12:28 yeah. we will work on the important items first 14:12:32 do you agree? 14:12:35 chenying__: What patches? 14:12:41 xiangxinyong: yes. 14:12:42 which patches , you mean end to end integration fullstack test 14:13:11 luobin and hurong's plugins and workflow patches. 14:13:24 Yes 14:13:46 they are waiting for fixes on the comments 14:13:51 eran some fullstack test are developmented by other gays. 14:14:28 yeah 14:14:30 https://review.openstack.org/317209 14:14:43 After I finish the integration test on the master, These fullstack test can be submited. 14:15:18 Eran do you think I sould start working on  Design and development of replication plug-in? 14:15:26 https://review.openstack.org/#/c/317209/ 14:15:46 did you submit the CI job ? 14:15:50 The important item task xiangxinyong list have not finished yes. 14:15:54 https://review.openstack.org/#/c/312008/ 14:16:09 did you submit the CI job ? I have finished. I will submit later. 14:16:14 https://review.openstack.org/#/c/314925/ 14:16:53 sorry, the above patches are about the fullstack 14:17:01 xiangxinyong: this are all the fullstack test , but what rae the test that are missing for the integration 14:17:14 "luobin and hurong's plugins and workflow patches." 14:17:50 I have listed some on our irc channel. 14:17:55 yuval: What is the link to the trello board you opened. 14:18:02 ? 14:18:23 https://trello.com/b/Sudr4fKT 14:18:47 You can join in this link: 14:18:49 https://trello.com/invite/b/Sudr4fKT/826e3dcffc7259b1447d4ecc448c1a45/smaug 14:19:08 OK I will join it. 14:20:13 i have joined it 14:21:19 operation engine patches also need be reviewed and merged. 14:21:22 gampel: understood 14:22:40 I'm still not sure what the best way to organize it is. 14:22:44 I'll think about it. 14:23:29 But we need a better way to coordinate. 14:23:50 As I konw, replication API in cinder only be implemented for admin. They are designing API for tenant in N. 14:24:36 chenying__: I've spoken with them in the summit. And our name is even in the spec. They will give us a service token that will allow us to do some admin action on behalf of the tenant. 14:25:33 saggi:trello is a good tool 14:25:38 chenying_: what are the reviews that are blocking you ? 14:25:54 saggi: what about using the etherpad to coordinate? 14:26:29 xiangxinyong: The history on etherpad is a bit obtuse so it's hard to track changes. 14:26:54 saggi: ok 14:27:30 We tried to use it but we noticed that someone might just make a big change and it will be hard to figure out why\what 14:27:43 #topic Task flow improvements 14:27:43 We've spoken about it in the last meeting. We understand the the current patches are a bit hard to review and we are working on it. 14:27:43 But apart from the deleted code we do need to know if there are any technical objections. 14:27:43 Please try and ignore the deleted code and concentrate on the actual changes. 14:27:51 saggi: if we plan to use trello, as you said, should find a organization way. it just a tool 14:28:15 zhonghua-lee: I know 14:28:31 saggi: :) 14:29:04 I agree lets see if some one have comment on the design , Yuval can you share the spec 14:29:18 zhonghua-lee: If you or anyone has any suggestions or can point me to a good trello board to get inspiration from please send me an email. 14:29:31 It' 14:29:40 saggi: https://trello.com/inspiringboards 14:29:49 : I will focus on the design progress in cinder. And reivew the spec. 14:29:56 It's important to note that some of the changes are as a result from use cases I got during the summit. 14:30:28 chenying__: Look up the replication spec. I've commented on it but see if there are things you want to ask them about it. 14:30:49 are there any technical objections to the new TaskFlow workflow design by Yuval 14:30:49 saggi: ok 14:31:15 saggi: OK 14:31:24 saggi: perhaps we can discuss trello in the mailing list 14:31:38 xiangxinyong: sure 14:31:44 xiangxinyong: good idea 14:32:42 xiangxinyong: +1 14:32:52 Thanks. i can do it tomorrow 14:33:12 swift guys are using the trello 14:33:58 xiangxinyong: a good coordination tool. 14:34:13 yeah 14:34:48 new TaskFlow workflow design, I think it is good. There are maybe lots of plugins refactoring work to do. 14:35:00 Will the changes introduced in yuval's patches effect testing? 14:35:06 are there any technical objections to the new TaskFlow/workflow design by Yuval ? As saggi said we will fix the patch delete ... 14:35:08 https://review.openstack.org/#/c/310386/7/smaug/services/protection/resource_flow.py 14:35:44 https://review.openstack.org/#/c/316669/ 14:36:35 i think that it is critical that we agree on the design and get comments from all the team 14:37:42 gampel: i agree with you. it seems like a big change 14:38:04 It is a critical bottleneck , that will allow us to merge all the protection plugin 14:38:39 I think that the design is good and we should push it in as early as possible , to avoid extra work later 14:39:07 I think the changes may affect integration testing. Because lots of plugins need be refactored. could we do the integration test using the old design. 14:39:28 ? 14:39:58 All the new code is done by yuval and can be merged togther 14:40:07 chenying__: Does the integration test get that deep in the code? 14:40:08 chenying__: do integration tests with the old design benefit us? 14:40:27 the fullstack is testing the API layer 14:40:53 we will merge the new design only once it does not break the fullstack 14:41:24 Anyhow, we should pass the spec updates first 14:41:57 we could merge the fullstack and then yuval could run local integration here and we will merge the code only when it pass fullstack 14:42:04 I also think it is better using new design. If we can refactor the plugins ASAP. But now portect action does not work in the master branch yes. 14:42:33 yuval: +1 14:42:45 maybe we can merge these patches firstly. https://review.openstack.org/#/q/owner:luobin_smile%2540163.com+status:open 14:42:55 we could merge the fullstack and then yuval could run local integration It is a good idea. 14:43:09 what patches are missing for the fullstack? 14:43:14 chenying__: can you give the list? 14:43:16 It is a good idea. If yuval can do the fullstack test in his local. 14:44:17 yuval: what list? fullstack test or patches? 14:44:33 chenying__: the patches required for the fullstack tests to start running 14:44:41 chenying__: what patches block the full stack 14:45:06 wait a minute 14:45:13 I think this is the list ? am I correct chenying__ ?https://review.openstack.org/#/c/287572/ 14:45:13 https://review.openstack.org/#/c/316674/ 14:45:13 https://review.openstack.org/#/c/303355/ 14:46:14 open engine service 14:46:14 https://review.openstack.org/#/c/309898/ 14:46:14 https://review.openstack.org/#/c/282263/ 14:46:14 https://review.openstack.org/#/c/310394/ 14:46:14 restore workflow 14:46:15 https://review.openstack.org/#/c303277 14:46:16 https://review.openstack.org/#/c/287572/ 14:46:18 https://review.openstack.org/#/c316674 14:46:21 https://review.openstack.org/#/c307737 14:46:39 i think these patches are important for the fullstack test 14:46:59 The resource graph walker listener https://review.openstack.org/#/c/287572/ https://review.openstack.org/#/c/316674/ https://review.openstack.org/#/c/303355/ 14:47:16 chenying__: right. thanks. everybody please make sure you review these 3 patches\ 14:47:22 I think portect action need these patches. 14:47:32 lets start with fullstack only to the protection service 14:47:39 If we want to test restore action we need more. 14:48:03 this one https://review.openstack.org/#/c/287572/ need to be updated tomorrow by smile-luobin 14:48:50 gampel: we will tell him tomorrow 14:48:55 I will ask luobin to update tomorrow. 14:49:13 But sometime I also can not find him. 14:49:29 Also, everyone, please email me patches that you think are ready for final review or are blocking your tasks. I will try and get to those first. 14:49:44 Stuff get lost in the clutter. 14:49:49 Ok but anyway please review the spec we coudl merge it anyway if there are no comments 14:50:19 Ok we will try to focus on this 3 tomorrow , then we can merge the fullstack patches 14:50:41 Updated Trello with the patches to review 14:51:20 #topic open discussion 14:51:29 Anything else before we finish for today? 14:51:49 Yes, if anyone didn't join the Trello, please do 14:51:54 Ok thanks I think if we have fullstack job, we can start lots of optimization work. 14:52:16 https://trello.com/invite/b/Sudr4fKT/826e3dcffc7259b1447d4ecc448c1a45/smaug 14:53:40 I have joined it. 14:54:58 OK, than thanks everyone. hopefully in two weeks in an earlier time. 14:55:03 #endmeeting