09:00:18 <yuval> #startmeeting karbor
09:00:19 <openstack> Meeting started Tue Jul 18 09:00:18 2017 UTC and is due to finish in 60 minutes.  The chair is yuval. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:22 <openstack> The meeting name has been set to 'karbor'
09:00:30 <yuval> Hello and welcome to Karbor's bi-weekly meeting
09:01:44 <yuval> We have only a few things on the agenda
09:01:54 <yuval> Waiting a bit for people to arrive
09:03:25 <chenying> hi
09:03:29 <jiaopengju> hi
09:03:47 <yuval> #info chenying, jiaopengju in meeting
09:04:57 <yuval> zhonghua: coming?
09:05:06 <yuval> chenying: will chenzeng join us?
09:05:09 <zhonghua> hi
09:05:28 <zhonghua> sorry to be late
09:06:12 <yuval> zhonghua: will chenzeng join us?
09:06:33 <zhonghua> I think he will join later
09:06:43 <yuval> alright, let's begin
09:06:55 <zengchen> i am here
09:06:58 <yuval> #topic Freezer integration
09:07:08 <yuval> #info zhonghua, zengchen in meeting
09:07:16 <jiaopengju> I have added this agenda
09:07:27 <yuval> jiaopengju: have you added this item?
09:07:29 <yuval> jiaopengju: righ
09:08:23 <chenying> jiaopengju want to do this work about  Freezer integration in queens of karbor.
09:08:26 <jiaopengju> I think we can make this as a solution to support backup more resources.
09:09:27 <yuval> yes, that's on the roadmap
09:09:49 <yuval> very good
09:09:58 <yuval> jiaopengju: would you like to elaborate?
09:10:47 <chenying> so do we need discuss the solution or the scope about freezer integration?
09:11:49 <jiaopengju> yuval: I think we can see Freezer as a backup/restore software
09:12:27 <chenying> what resources about freezer protection should be  integrate with karbor?
09:12:35 <yuval> jiaopengju: I agree. One of the things we discussed, is that Freezer can be used for protecting volumes, but protecting files is trickier
09:13:04 <chenying> as we know, now freezer can backup  volume, vm , file, db(also file).
09:13:13 <jiaopengju> yuval: Yes
09:13:57 <chenying> yuval 'but protecting files is trickier'  yuval, you know too much. :D
09:14:14 <yuval> chenying: lol?
09:14:18 <yuval> chenying: :)
09:14:28 <yuval> chenying: we had so many discussions about that
09:15:41 <jiaopengju> yuval chenying: I will write a specs documentation to make it clear of freezer integration
09:16:08 <yuval> jiaopengju: great
09:17:26 <chenying> jiaopengju sound good.
09:17:29 <yuval> jiaopengju: anything else you'd like to discuss regarding freezer integration?
09:18:15 <chenying> I have only one quesiton, do we need cover file backup of freezer?
09:18:43 <chenying> do we need consider ntegrating file backup of freezer?
09:19:19 <chenying> jiaopengju  What's your oppion about it?
09:20:36 <jiaopengju> yuval chenying: File is just one resource in freezer, after freezer integration, karbor do not need to interactive with the file resource. So I think it is ok to cover the file backup
09:21:27 <yuval> jiaopengju: I don't think I understand. Karbor is protecting protectables. In order to protect files, we need a file protectable, which is one of the tricky aspects
09:22:30 <chenying> jiaopengju  You mean that you will provider a common frezer plugins, can support all the protectable resources in freezer?
09:23:06 <jiaopengju> chenying: yes
09:24:12 <yuval> jiaopengju: so, we are not speaking about adding new protectable plugins for that, right?
09:25:09 <chenying> yuval: That is what I worry about.  a file protectables make me confused.
09:26:17 <jiaopengju> yuval: yes, i think we can consider volume, instance in first step
09:26:25 <yuval> jiaopengju: great!
09:27:46 <yuval> #topic Pike Schedule
09:28:02 <yuval> #link https://releases.openstack.org/pike/schedule.html
09:28:16 <yuval> next week is the Pike-3 milestone
09:28:27 <yuval> together with final release for client libraries
09:29:03 <yuval> this means we will do another karborclient release in the beginning of the week
09:29:15 <yuval> and update the requirements in dashboard and karbor
09:30:00 <chenying> so operation log api need be included in karborclient before release.
09:30:59 <yuval> chenying: yes
09:31:26 <jiaopengju> shoud the swift full listing be included?
09:31:58 <yuval> jiaopengju: full listing is in karbor, not in karborclient
09:32:06 <yuval> jiaopengju: if I recall correctly
09:32:10 <chenying> jiaopengju: karborclient is released before karbor.
09:32:33 <jiaopengju> yuval karborclient need also to be updated.
09:32:47 <yuval> jiaopengju: hows that?
09:33:04 <jiaopengju> yuval the checkpoint list api
09:33:16 <yuval> jiaopengju: the checkpoint list api will retain the pagination
09:34:08 <chenying> jiaopengju: You mean that there may be some change about karborclint with full listing?
09:34:09 <jiaopengju> yuval: yes, you mean do the pagination in karbor, not in the dashboard?
09:34:22 <yuval> jiaopengju: we will not change the API, but we could mark the pagination arguments as 'deprecated'
09:35:46 <jiaopengju> chenying: maybe yes. but as yuval said, I think we can make it maintain current status.
09:36:07 <yuval> jiaopengju: the idea is to maintain checkpoint indexing out of the bank as well
09:36:24 <yuval> jiaopengju: so we should keep the checkpoint pagination in the api
09:37:39 <jiaopengju> yuval: ok
09:37:56 <yuval> jiaopengju: even if we wanted to make changes to the API, it is to late in
09:38:00 <yuval> jiaopengju: Pike for that
09:38:46 <jiaopengju> yuval: agree
09:39:27 <yuval> Alright, last one before open discussion
09:39:34 <yuval> #topic Queens Goals
09:39:58 <yuval> #link https://ethercalc.openstack.org/karbor-queens
09:40:06 <yuval> Let's start brainstorming about Queens goals
09:40:37 <yuval> Please add your ideas (with your name by items) to that ethercalc
09:41:03 <yuval> We will review it just before the beginning of the next cycle, assign priorities and people
09:41:40 <yuval> #topic Open Discussion
09:41:44 <yuval> anything else?
09:42:43 <chenying> yuval I see you have submmited a patch about 'dsvm gate prepare' in trove? It means that only the patch being merged, then you can start the patch about trove integration jenkins job?
09:43:41 <yuval> chenying: no point in sending a patch to project-config before trove guys will agree to this patch
09:44:20 <chenying> I see. Hope it can be merged to trove ASAP.
09:45:02 <yuval> chenying: me too
09:45:30 <yuval> thank you all for attending
09:45:41 <yuval> #endmeeting