14:00:56 <m3m0> #startmeeting freezer 14:00:57 <openstack> Meeting started Thu Jul 7 14:00:56 2016 UTC and is due to finish in 60 minutes. The chair is m3m0. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:01 <openstack> The meeting name has been set to 'freezer' 14:01:07 <yangyapeng> hello 14:01:13 <domhnallw> Howdy. 14:01:16 <m3m0> hello, who's here for the freezer metting 14:01:19 <timothyb89> hello all 14:01:22 * domhnallw is here 14:01:23 <yangyapeng> :) 14:02:05 <slashme> o/ 14:02:17 <m3m0> daemontool you here? 14:02:37 <domhnallw> He was in #openstack-freezer a few minutes ago... 14:02:41 <daemontool> o/ 14:03:23 <ddieterly> o/ 14:04:15 <m3m0> ok let's start 14:04:26 <m3m0> #topic Improve the volumes backup through the Cinder APIs (i.e retention, delete, list backups, metadata) (domhnallw: pulled from last weeks' agenda) 14:04:33 <m3m0> who proposed this? 14:04:46 <daemontool> I think yangyapeng 14:04:48 <daemontool> ? 14:05:00 <daemontool> that totally make sense 14:05:10 <yangyapeng> hn 14:05:17 <domhnallw> Yep, think so. I just did a copy pasta :) 14:05:52 <yangyapeng> we use freezer to manage cinder through Cinder APIs 14:06:18 <yangyapeng> cinder backup, delete, restore and so on . 14:06:23 <yangyapeng> ping iceyao_ 14:06:50 <daemontool> anyone is against improving the way we wrap the cinder API for volumes baas? 14:07:05 <daemontool> slashme, ping 14:07:23 <slashme> No problem for me. 14:07:35 <yangyapeng> :) 14:07:43 <daemontool> yangyapeng, iceyao_ do you want to work on that? 14:07:48 <yangyapeng> yeah 14:07:50 <slashme> The retention part would definilty be usefull 14:08:01 <daemontool> can you implement 1 API enpoint wrap at the time? 14:08:20 <yangyapeng> yeah we can. 14:08:22 <iceyao_> I'm gald to 14:08:27 <daemontool> ok 14:08:51 <daemontool> can you add a basic delivery sequence in the freezer-specs repo 14:08:54 <daemontool> ? 14:09:32 <daemontool> like: 1) list backup, we to x y z, 2) metadata we save this xzv, 3) retention.... 14:09:34 <daemontool> ok? 14:09:43 <daemontool> very schematic 14:09:57 <daemontool> no paralysis anlysis if possible :) 14:10:29 <daemontool> sounds good? 14:10:57 <yangyapeng> ping ceyao_ 14:11:01 <yangyapeng> iceyao_: 14:11:21 <yangyapeng> you can take a commit next time. 14:12:15 <daemontool> ok 14:12:20 <daemontool> next? 14:12:31 <daemontool> unless anyone has anything on say about that 14:12:42 <yangyapeng> thanks 14:13:12 <m3m0> #topic Add support for file storage (Manila) (domhnallw: pulled from last weeks' agenda) 14:13:36 <daemontool> I added this last time 14:14:11 <daemontool> I think Manila soon will get way more relevance in OS 14:14:25 <daemontool> it would be one storage media more 14:15:26 <daemontool> is anyone interested? 14:15:35 <liudan> ping yangyapeng 14:15:45 <daemontool> anyone thing it can be a priority? 14:16:20 <slashme> I don't see it as a priority 14:16:22 <daemontool> ok 14:16:28 <iceyao_> +1 14:16:29 <slashme> Rather a nice-to-have feature 14:16:29 <daemontool> then disregard it 14:16:32 <daemontool> ok 14:16:35 <yangyapeng> now ,we need to do it manila ? 14:16:56 <slashme> This is also something easier to integrate later when the agent refactoring is completed 14:17:00 <daemontool> ok 14:17:16 <daemontool> next 14:17:26 <m3m0> #topic Midcycle meetup 15 of July 14:17:43 <m3m0> next week is the mid cycle meetup 14:17:46 <m3m0> do we have an agenda? 14:18:43 <m3m0> link: https://etherpad.openstack.org/p/freezer_midcycle_meetup_newton 14:18:46 <m3m0> please review it 14:18:56 <m3m0> and add/remove topics accordingly 14:19:05 <m3m0> please let us know who propose changes 14:20:24 <daemontool> ok 14:20:58 <m3m0> can we move then? or should we discuss this ? 14:21:59 <daemontool> next 14:22:32 <m3m0> #topic Feedback from the Business 14:22:48 <daemontool> ok, I've added the last 2 topics 14:22:57 <daemontool> yesterday I had a very contructive conversation 14:23:14 <daemontool> with ATT 14:23:35 <daemontool> and basically they are evaluating 14:23:47 <daemontool> to use freezer or not in their production environments, allocating people etc 14:24:05 <daemontool> so they are concerned about the fact that we supports only tar 14:24:35 <daemontool> that also the deduplication was another point 14:25:09 <daemontool> the feedback was about also thinking of developing an additional component 14:25:14 <daemontool> for the storage 14:25:24 <daemontool> like the other enterprise solutions provide 14:25:45 <daemontool> to keep track of changed blocks, hash tables, etc etc 14:25:58 <daemontool> the positive feedback was about elasticsearch 14:26:29 <daemontool> it wasn't much welcome the idea of moving to mysql 14:26:47 <daemontool> the other poi of discussion was 14:27:07 <daemontool> about how to do backup, without moving the data form the back end storage, then process it and removing it to the storage again 14:27:13 <daemontool> as it is highly inefficient 14:27:32 <daemontool> one other point was the delay 14:27:52 <daemontool> of executions of jobs by the scheduler/agent 14:28:04 <daemontool> if we could find a way to reduce that delay to the minimum, it would be a big plus 14:28:10 <daemontool> also 14:28:21 <daemontool> they need a more advanced way for inclusion and exclusion 14:28:27 <daemontool> of files in the fs 14:28:32 <daemontool> when executing backups 14:28:41 <slashme> +1 on the last point 14:29:00 <daemontool> honestly, I think all the points are valid 14:29:10 <daemontool> IMHO 14:29:32 <daemontool> thoughts? 14:29:39 <daemontool> what do you think? :) 14:29:40 <slashme> I also agree. Some with higher priority though 14:29:54 <daemontool> DR wasn't covered 14:30:02 <daemontool> by there should be another conversation about it 14:30:09 <daemontool> sooner than later 14:30:31 <daemontool> adding engines should be easier than it is now 14:30:42 <slashme> That's our goal 14:31:08 <slashme> Ease the process of adding new engines, backends, snapshot mechanism 14:31:22 <daemontool> ah 14:31:32 <slashme> As well as integrating with application (not only for backup but also for restore) 14:31:38 <daemontool> also the windows GUI was another point of discussion 14:31:59 <daemontool> as they most probably wants to try to reduce costs 14:32:07 <daemontool> not a strong point thought, but a nice to have 14:32:20 <daemontool> the strong point was about 14:32:21 <daemontool> engine 14:32:27 <daemontool> and backend&dedup 14:32:31 <domhnallw> A Windows GUI? 14:32:34 <daemontool> yes 14:32:48 <daemontool> but let's not talk about that now please 14:32:52 <daemontool> it's more a business related thing 14:32:53 <domhnallw> Okay. 14:32:55 <daemontool> we can talk about it offline 14:33:01 <daemontool> :) 14:33:16 <daemontool> so 14:33:18 <daemontool> at some point 14:33:25 <daemontool> as they are quite good writing C doe 14:33:26 <daemontool> code 14:33:30 <daemontool> there was the idea 14:33:48 <daemontool> of using a backend with zfs, that can export the changed blocks hashtable 14:33:58 <daemontool> then a component of freezer 14:34:00 <daemontool> on top of that 14:34:04 <daemontool> that interact with the agent 14:34:12 <daemontool> for dedup/incrementals 14:34:44 <daemontool> so these was basically the conversation 14:36:55 <m3m0> so, are they going to contribute soon? :) 14:37:13 <daemontool> they are evaluating 14:37:14 <daemontool> with us 14:37:22 <daemontool> netbackup, avamar 14:37:25 <daemontool> and someone more 14:37:28 <daemontool> can-t remember 14:37:35 <daemontool> If they see potential, they will 14:37:53 <m3m0> that could be great :) 14:38:06 <daemontool> I think that would make big difference 14:38:18 <daemontool> because their production environment 14:38:19 <daemontool> are huge 14:38:29 <daemontool> the requirements will be challening 14:38:50 <daemontool> but the solution will be way more advanced 14:38:52 <daemontool> also 14:38:55 <daemontool> in Ericsson 14:39:10 <daemontool> there's a test in the lab 14:39:15 <daemontool> to evaluate it 14:39:21 <daemontool> so expext that 2 engineers 14:39:24 <daemontool> will be around here 14:39:27 <daemontool> starting from next week 14:39:37 <daemontool> mostly working on docs 14:39:43 <daemontool> and tests 14:39:49 <daemontool> that is confirmed 14:39:55 <domhnallw> Sounds good. 14:40:13 <daemontool> yes we need moe people 14:40:24 <daemontool> that's all from me 14:40:56 <m3m0> thanks a lot, we will help the new guys with everything they need 14:41:21 <m3m0> can we move forward? 14:41:39 <daemontool> yes 14:42:13 <m3m0> #topic Pending Reviews 14:42:19 <m3m0> https://review.openstack.org/#/c/329671/ (closes #1592046) 14:45:31 <m3m0> any more reviews? 14:46:40 <m3m0> can we close the meeting then? 14:47:12 <slashme> I think so. Thank you m3m0. 14:47:18 <domhnallw> Thanks. 14:47:25 <m3m0> thanks all :) 14:47:25 <m3m0> #endmeeting