09:02:41 #startmeeting karbor 09:02:42 Meeting started Tue Nov 8 09:02:41 2016 UTC and is due to finish in 60 minutes. The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:02:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:02:45 Hi everyone 09:02:46 The meeting name has been set to 'karbor' 09:02:55 hi 09:02:55 hello 09:03:09 hello guys. 09:03:30 Sorry for being a bit late, was busy looking at patches 09:03:30 hey 09:04:11 Speaking on patches.... 09:04:11 #topic The way to stability 09:04:37 I spent the last couple of days triaging all the bugs on launchpad 09:05:07 That means setting priorities and deciding what should get in Ocata. 09:05:48 Patch sets that relate to bugs should get a much higher priority in review than other patches. 09:06:04 Also, fixing bugs is of higher priority than cleanups. 09:06:43 Further more, please open bugs on things that you know are broken. I will triage bugs every morning so we know what we need to do. 09:08:03 ok 09:08:15 Currently what is being stable means is only in our heads. It's better that we have a list of things we need to fix. 09:09:59 do we need to mark them in the lauchpad? 09:10:00 Please make sure to make the bug reports detailed and easy to understand even out of context since someone else might fix the problem you found 09:10:22 xiangxinyong: It should be automatic 09:10:27 ok 09:10:29 If you set the proper headers in gerrit 09:10:47 https://wiki.openstack.org/wiki/GitCommitMessages 09:11:22 btw, chenying and zhonghua-lee here too? 09:12:23 they are not available 09:12:56 Just to sum up. If you see a problem and you can't send a patch immediately, open a bug. Otherwise things fall through the cracks. 09:13:16 I will send an email to the mailing list and CC chenying and zhonghua-lee about it 09:13:49 saggi:great 09:14:18 do you mean every patch needs a bug or bp? 09:14:35 we have some bugs with inactive assignee, I think 09:15:12 xiangxinyong: It will get higher priority review from me and yuval. Also if a bug exists for the problem you are fixing you will need to set the bug in the commit message. 09:15:40 saggi: agree 09:16:33 the Standard commit message is important 09:17:21 xiangxinyong:couldn't agree more. 09:17:35 :) 09:18:36 often be confused with the patch which doesn't contain any commit message :( 09:18:37 Needless to say, working on fixing bugs is top priority. 09:19:46 totally agree. 09:19:57 #topic Adding Karbor into Kolla and implementing container deployment (xiangxinyong) 09:20:44 we discuss the feature with kolla team members. zhanglei and caiwei 09:21:04 xiangxinyong: This relates to ease of installation so we might fit in the the O cycle. But I wonder what we need to change code wise for this to work. 09:21:32 zhanglei and caowei 09:21:33 zhangshuai: are you around? 09:22:03 zhangshuai is working on it 09:22:14 saggi:no 09:22:41 I guess we only need to give the installation documents to kolla team 09:23:12 xiangxinyong: can they convert the devstack scripts? 09:23:26 they make it as a docker image 09:23:48 xiangxinyong:you are right. 09:23:50 I believe working on OpenStack Ansible deployment first could help 09:24:22 yeah. caowei from 99cloud is an expert 09:24:24 zaneb: What is the the delta between kolla and openstack-ansible 09:25:29 but unfortunately caowei is not here today. 09:26:38 It is easy for him to submit a patch in kolla to do this work 09:27:07 it is very well for karbor and kolla 09:27:23 What will the patch do is it a Dockerfile? 09:28:39 saggi: not sure. but zhangshuai and caowei are working on it. 09:28:42 like https://review.openstack.org/#/c/374908 09:29:28 zhangshuai: thanks 09:29:52 :) 09:30:06 zhuangshuai:great 09:30:23 zhangshuai, xiangxinyong: Great, Please put me as a reviewer for any patches for Karbor in Kolla. 09:30:30 me too please 09:30:49 :) no problem. 09:31:16 saggi,yuval: ok, thank you. 09:31:34 #topic Karbor integrated with Freezer Plan (xiangxinyong) 09:31:34 we could keep touch with kolla's guys 09:31:45 xiangxinyong: sure 09:31:55 yangyapeng: are you around? 09:32:16 xiangxinyong: yeah 09:32:28 welcome to join this meeting 09:32:50 yangyapeng from 99cloud is the freezer's core member 09:32:52 :) 09:32:55 he is very kind 09:33:16 hi yapeng 09:33:27 hi yangyapeng 09:33:35 hey yangyapeng 09:33:43 hello guys :) 09:33:59 I have my ideas on how to integrate but I'd much rather hear what yangyapeng has to suggest. 09:33:59 saggi: do we have some plans to integrate with freezer.? 09:34:06 Yes 09:34:21 It depends on freezer plugins 09:35:16 whether it have a details in etherpad 09:35:22 * saggi is looking for the freezer etherpad 09:35:50 saggi: may we develop a freezer plugin to connect freezer? 09:35:57 yangyapeng: can't find the etherpads from BCN : https://wiki.openstack.org/wiki/Design_Summit/Ocata/Etherpads 09:36:10 https://etherpad.openstack.org/p/freezer_other_roadmap_ocata 09:36:13 https://etherpad.openstack.org/p/freezer_new_archi 09:36:51 The last one 09:37:25 So if we look at what we need from freezer. It's guest cooperation. 09:38:37 File level backups don't really make much since for the Karbor story. So what we want to do is invoke freezer and have it tell the applications to prepare for backup. 09:39:03 Than we create the backup the usual Karbor way. 09:40:25 The main question is if we can pass configuration about plugins in the API call itself. 09:40:38 Instead of creating plans in freezer 09:41:03 yangyapeng ^^ 09:41:20 saggi: I guess creating plans in freezer is not good 09:41:27 hi 09:41:44 I am 09:41:52 :) 09:41:53 xiangxinyong: We would like to user freezer as a stateless entity 09:41:54 I am late 09:42:03 chenying2016: :) 09:42:10 saggi: agree with you 09:42:48 saggi: it seems like we need to do more commuications with freezer team 09:42:49 yangyapeng left 09:43:32 xiangxinyong: You are right. I will add an item to their weekly meeting this week to talk about statelessness. 09:43:42 ^^ 09:44:02 yeah. yangyapeng and Pierre-Arthur Mathieu could help us. 09:44:18 saggi: we can simply use freezer to do what it does. just invoke its api. but the question is the configuration of freezer agent is a little complex. 09:44:35 saggi: thank you. 09:44:38 zengchen: What configuration 09:44:50 install 09:44:55 freezer 09:45:39 Yes, maybe we can also get them to have an agentless option. 09:45:42 We'll see 09:46:32 saggi:you can see there are a little more configurations for the freezer agent. the user should know how to use them. 09:46:34 chenying2016: In any case, freezer is not a mandatory requirement for karbor. We will only use it for application level consistency. 09:47:01 saggi:i had writed a plugin of freezer. 09:47:17 zengchen: great 09:48:20 this plugin architecture is not yet merged, right? 09:48:25 saggi:hope to see your detailf of solution. 09:48:32 #action talk to Freezer team about using freezer as a stateless entity preferably without setting up schedulers. 09:48:55 saggi: thanks 09:49:26 yuval:you asked me? 09:49:35 as a general question 09:50:02 yuval: IIRC it's in their roadmap for this cycle 09:50:07 But I'm not sure. 09:50:25 saggi: thumbs up emoji 09:50:51 #topic open discussion 09:50:54 Anything else? 09:51:46 i have came across a question 09:52:57 I hope the patches about the operationengine could be merged,\. 09:53:07 zengchen: ... 09:53:16 chenying. I'll try and do it today 09:53:21 about this patch (https://review.openstack.org/#/c/384062/). the unit test can pass if i use 'ostestr' to run, if it failed when i use 'tox - e py27' 09:53:31 The operationengine servcie could not work because of this patches. 09:54:16 zengchen: You are asking why it fails? 09:54:26 zengchen have a problom about tox -e to run unit test. 09:54:32 the reason is the 'mock' can not work when the run unit test with 'tox' 09:54:59 zengchen: It fails all version of python 09:55:56 saggi:i just want to ask who know the difference between the 'ostestr' and 'tox'. I think if the 'ostestr' can work, the 'tox' can work too. 09:56:23 It might be something in the configuration. I will have to look at it more closely to see what the problem is. 09:56:25 saggi:yes, both py27 and py34 failed. 09:57:02 saggi:thanks. I have spent a lot of time on it. but i failed to fix it. 09:57:27 zengchen: I'll try and squeeze it in my schedule. 09:57:52 Anything else? 09:58:12 saggi:thanks very much. 09:58:53 I would like to just to thank xiangxinyong for his great suggestions for topics for this meeting. And in general trying to get Kolla and Freezer's cooperation. 09:59:01 xiangxinyong: great job! 09:59:05 Good day everyone 09:59:19 bye bye. 09:59:22 #endmeeting