02:00:15 #startmeeting nimble 02:00:16 Meeting started Thu Nov 17 02:00:15 2016 UTC and is due to finish in 60 minutes. The chair is zhenguo. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:00:19 The meeting name has been set to 'nimble' 02:00:29 o/ 02:00:30 hi everyone 02:00:34 o/ 02:00:41 the agenda: 02:00:48 o/ 02:00:52 #link https://wiki.openstack.org/wiki/Meetings/Nimble#Agenda_for_next_meeting 02:01:14 shaohe_feng, yuntongjin: are you around? 02:01:16 hi 02:01:30 ok, let's jump in 02:01:36 #topic announcements and reminders 02:02:03 we have added db/object/scheduler tests last week and new functional tests work well now, thanks everyone who contributed to the tests work 02:02:36 hi all 02:02:41 good work 02:03:09 liusheng will work on both functional tests and tempest, anyone who wants to help can contact with him :) 02:03:30 and a new project nimble-specs is ready now, we can use it in futue 02:04:09 we have a new contributor luyao who is very active recently, let's welcome luyao :P 02:04:14 o/ 02:04:19 :-D 02:04:29 how much tests should be added before we announce the Nimble project? :P 02:05:06 liusheng: I'm not sure, but seems it's enough, we can continue to add tests after we are public 02:05:25 good to see new contributors 02:05:43 zhenguo: cool 02:06:02 shaohe_feng: do you think we need to add more tests before going public? 02:06:25 what about add a coverage jenkins job? 02:06:39 RuiChen: agree :) 02:06:49 maybe, one exmaple test case for authorization? 02:07:03 shaohe_feng: agree 02:07:20 shaohe_feng: we still have two days this week :P 02:07:54 zhenguo: yes. let add it these two days. 02:08:04 shaohe_feng: ok 02:08:18 not much of announcement, anyone else have a thing here? 02:08:37 we can continue to discuss about tests in open discussion topic :) 02:08:52 so what's the plan that we publish nimble in community? which day and what action? 02:09:15 RuiChen: hah, let's move on to next topic 02:09:21 #topic our next plan 02:09:24 the plan is before hackthon? 02:09:40 ok, let's talk about our next plan :P 02:09:54 maybe next week? 02:10:04 or at the end of this week 02:10:12 yuntongjin and shaohe_feng will join bug smash in Shenzhen? 02:10:19 we won't 02:10:21 hope we can attract new comer in hackthon :) 02:10:32 and lei-zh? 02:10:35 oh, that's a shame! 02:10:42 lei-zh will 02:10:42 I will be there 02:10:45 why you won't go? 02:10:54 lei-zh: hah 02:11:04 RuiChen: no. no budget for me. 02:11:24 shaohe_feng: it is a pity 02:11:31 shaohe_feng, yuntongjin: oh, that's a pity 02:11:33 some time in next week, like wendsday 02:11:54 to public Nimble 02:11:54 shaohe_feng, yuntongjin: I thought we can have a meetup in the hackthon 02:12:02 haha 02:12:17 that's shame, we can pick Beijing for next Bug Smash :-) 02:12:31 lol 02:12:46 the next boss is Intel :P 02:13:35 we can do bug smash remotely 02:13:47 zhenguo: you need to pr欧模特 02:14:03 It's great, yuntongjin, IRC connect us :-) 02:14:07 promote nimble in bug smach 02:14:14 smash 02:14:16 shaohe_feng: sure 02:14:27 maybe we will have a presentation there 02:14:50 there should be a presentation there 02:15:10 but you won't be there :( 02:15:50 i know it won;t be same, but i can almost hear it when you presenting 02:15:59 lol 02:16:18 lol 02:16:21 Live show for nimble presentation, hah 02:16:36 hah, ok let's continue 02:16:37 so, how about next Wendsday to public Nimble? 02:16:48 I think it should be ok 02:17:09 so we still have about a whole week 02:17:31 we can talk about the procedure of going public 02:17:51 firstly, I think we need a eamil to formally announce our project in the mailling list 02:18:06 should the tempest plugin be added before going public ? 02:18:27 liusheng: if you can, that would be wonderful 02:18:36 zhenguo: I will try 02:18:43 liusheng: thanks very much 02:18:43 yeah, procedure and time are important, zhenguo 02:18:56 RuiChen: yes 02:19:27 then, we need to use launchpad to track our bug and features and maybe use psecs for bp 02:19:43 s/psecs/specs 02:19:55 UT, funcational, Tempest, wiki, API doc, devref should be ready, anything else? 02:20:13 that is way of big-tent, hah 02:20:28 hah 02:20:43 good tips, we have a checklist for big-tent 02:20:59 liyongle draft it 02:21:19 and another important thing is review rules 02:21:45 we shouldn't merge directly after we are public :( 02:21:53 i like using specs to disuss new feature 02:22:02 yuntongjin: yes 02:22:39 all things should be changed, we should work like an official project 02:23:11 changes will be approved once 2 core +2 are posted 02:23:29 some official projects don't like official projetcs now, :( 02:23:42 liusheng: hah, 02:24:38 as we will restrict our review rules, everyone should try to do more reviews 02:24:50 especially core reviewers 02:24:50 agree, review should be match the community rules, even if It's slow 02:25:13 RuiChen: agree 02:25:33 but we can ping any core here for reviewing if needed 02:25:55 if our cores are all active enough, I think it will not be that slow 02:25:59 yeah we are in a same timezone 02:26:17 good point ^^ 02:26:33 I will paste the contribution report link here at every meeting 02:26:47 #link http://stackalytics.com/report/contribution/nimble/90 02:27:14 from the link above we can see that the activeties of every contributor 02:27:32 we will add/remove core reviewers according the contribution report there 02:27:39 wdyt? 02:27:56 that's also what offical project do now 02:28:00 agree 02:28:20 yeah, that's reasonable 02:28:46 oh, RuiChen mostly focuses on nimbleclinet, we should also paste the client contribution like here :P 02:29:38 oh, welcome fredli 02:30:10 Hi 02:30:19 fredli: o/ 02:30:26 Glad to join this amazing project 02:30:28 welcome :) 02:30:32 hi, fredli we talk about your contribute for big-tent checklist, thank you 02:30:53 fredli: we are talking about the procedure of going public now 02:31:17 fredli: do you have some suggestion here? 02:31:36 Please go ahead 02:31:42 ok 02:31:54 shaohe_feng, yuntongjin: do you have anything else here? 02:32:02 not much 02:32:09 ok, 02:32:15 we need prepare challenge from communit 02:32:25 z 02:32:31 yuntongjin: sure 02:32:57 ok, what's next 02:33:05 #topic Ocata priorities 02:33:06 and think about some killer feature 02:33:30 yuntongjin: sure, we can talk about it in our O priorites 02:33:57 I listed many things to do on our trello board 02:34:13 oh, do you think we should keep using our private trello board? 02:34:25 or track bugs and features using launchpad 02:34:33 I think RAID should one, and nova prepare to implement it, but it's difficult for nova 02:35:12 RuiChen: yes, but RAID depends on Ironic's RAID on deploy time feature 02:35:16 which is not finished yet 02:36:04 #link https://trello.com/b/FBsIvUTp/ironic-nimble-plan 02:36:05 I think it's not conflicted, we can set the trello to public and link it in launchpad 02:36:21 RuiChen: agree 02:36:27 zhenguo: may we can paste this link in our wiki ? 02:36:39 liusheng, RuiChen: yes 02:36:50 yep, liusheng 02:36:55 sure 02:36:57 liusheng, RuiChen: but should we create a new trello board? 02:37:14 let me check it 02:37:39 a public trello board for Nimble instead of an old with all our histroy there seems it's better 02:37:55 wdyt? 02:38:03 zhenguo: sure 02:38:28 wiki and etherpad would be more community way 02:38:32 I think it should be ok, fredli, any suggestion? 02:38:51 yuntongjin: yes, etherpad should be used 02:39:10 zhenguo: wiki, lp, etherpad 02:39:12 yuntongjin: but Ironic have a trello board for it's priorities features 02:39:37 we can add a etherpad for our Ocata priorites 02:39:55 let's keep it internel 02:40:08 yuntongjin: lol 02:40:39 move the info to spec/wiki/etherpat 02:40:52 yuntongjin: and launchpad 02:41:21 liusheng: you can register a bp for tempest in our launchpad 02:41:25 sounds good, that's task before annoucement 02:41:31 zhenguo: ok 02:41:55 ok, so after this meeting, we will try to use launchpad for bug or feature tracking 02:42:30 about the detailed priorites, I can prepare a list then we need to discuss more 02:42:51 do you prefer to use a etherpad or on our trello board 02:43:01 etherpad 02:43:10 agree 02:43:10 ok 02:43:46 ok, anything else here? 02:44:10 #topic open discussion 02:44:33 so do you have anything else want to talk about 02:44:38 open discussion :P 02:44:51 zhenguo: I think we more exception test for nimble. 02:45:05 shaohe_feng: agree 02:45:11 zhenguo: luyao has find a issue. 02:45:27 zhenguo: not sure her patch is ready. 02:45:27 shaohe_feng: I reviewed luyao's patch yesterday 02:45:47 shaohe_feng: that's all because we don't have test cases for engine service 02:46:14 shaohe_feng: so I think we need a volunteer work on engine service tests next week 02:46:41 zhenguo: agree. 02:47:03 shaohe_feng, liusheng: it should be in UT or functional tests? 02:47:41 zhenguo: more exception handle is very useful for a project stable 02:47:41 at least have some UT for it 02:47:48 shaohe_feng: it is about the functionality of engine services ? 02:48:06 yes, 02:48:19 UT first, then funcational 02:48:55 so we can add a coverage jenkins job as RuiChen suggested 02:49:03 agree, and when adding tests, I think you can find many bugs in our codes, please also fix that 02:49:05 I am not fimilar with the coverage job 02:49:20 liusheng: I'm not familiar as well 02:49:40 liusheng, RuiChen: seems we can add coverage job later 02:50:16 I think currently we highly need an dsvm job in our gate :P 02:50:27 fimilar is not the issue. seems all of us are good learner. :P 02:50:44 shaohe_feng: hah, 02:50:56 shaohe is a fast learner 02:50:58 zhenguo: that seems a part of tempest work 02:51:27 liusheng: oh sorry, 02:51:39 so, the proirity is ? UT > functional > dsvm > converage? zhenguo 02:51:53 RuiChen: I think so, 02:52:12 dsvm is part of tempest, haha 02:52:18 same to me, let's do it 02:52:47 ok 02:53:08 I can try to add coverage for python-nimbleclient, because the UT 02:53:09 only 8 minites left, do you have anything else want to discuss? 02:53:21 is ready for now, then do it for nimble 02:53:57 nothing from me 02:54:03 oh, I think everyone here can talk about what he wants to do after this meeting 02:54:05 nothing else 02:55:14 good start, we discuss in whole meeting time, thanks everybody 02:55:27 haha 02:55:33 do more review, will push scheduler test to merged, migrate trallo info to wikil/spec... 02:55:48 yuntongjin: ok thanks 02:56:14 yuntongjin will focuse on scheduler tests 02:56:31 I will work on engine service tests 02:57:04 shihanzhang and I merge the instance resource CLI today 02:57:35 RuiChen, shihanzhang: thanks, that should be done before we are public :P 02:57:55 of course, :-) 02:58:06 liusheng is working on fuctional tests and tempests 02:58:08 Zhong Luyao proposed openstack/nimble: bug fix: delete instance correctly https://review.openstack.org/398306 02:58:17 zhenguo: yeah 02:58:32 shaohe_feng, luyao: we can all help to add more tests 02:58:41 work hard, luyao, hah 02:58:56 oh, luyao just updated a patch, what a good contributor:P 02:59:35 next time you are in GTC, you will meet her in person 02:59:46 on time, first IRC meeting \o/ 02:59:57 yuntongjin: haha 03:00:15 thanks y'all 03:00:25 #endmeeting