16:24:12 <Slashme> #startmeeting openstack-freezer 03-12-2015 16:24:13 <openstack> Meeting started Thu Dec 3 16:24:12 2015 UTC and is due to finish in 60 minutes. The chair is Slashme. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:24:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:24:16 <openstack> The meeting name has been set to 'openstack_freezer_03_12_2015' 16:24:28 <Slashme> All: meetings notes available in real time at: https://etherpad.openstack.org/p/freezer_meetings 16:25:00 <Slashme> #topic Freezer_Arguments 16:25:17 <Slashme> ping: szaher szaher_ 16:25:52 <Slashme> With the move to olso comfig for the freezer-agent, we are thinking about reworking some freezer-agent parameters 16:26:16 <Slashme> The discussion about this is happening here: https://etherpad.openstack.org/p/Freezer_arguments 16:26:27 <Slashme> Feel free to participate 16:26:47 <szaher> Thanks 16:26:53 <szaher> Thanks Slashme 16:26:59 <reldan> I suppose we should delete absolete parameters. It may be the first step 16:27:39 <szaher> We need to group parameters in freezer agent to be able to manage them and to make the user life easy using theses parameters 16:27:39 <reldan> --list-containers, --list-objects, GET_OBJECT, DST_FILE, upload 16:28:03 <Slashme> I agree. 16:28:39 <Slashme> Also I think we should remove the info commanf. It is not the role of the freezer-agent to list swift containers 16:28:58 <szaher> once we grouped the parameters we can make them available as cli or in config files in the same time without any effort 16:28:58 <reldan> I agree 16:29:48 <reldan> Agree as well 16:30:10 <szaher> Ok, here https://etherpad.openstack.org/p/Freezer_arguments we need to group all related parameters together. Like some parameters are being used for lvm so it needs to be under lvm group in config opts 16:30:53 <szaher> and ofcourse there are some parameters which will be common parameters which can be used with any opteration backup, restore, like --debug for example 16:30:57 <reldan> I also think that restore-from-host == --hostname, --path-to-backup == --restore-abs-path 16:32:13 <Slashme> While we are speaking of parameters and options, do we want to support parallel storage with cli options or only using config files 16:33:22 <szaher> I don't think it will be applicable as we can miss which parameters to use with which storage 16:33:46 <szaher> or what do you think ? 16:34:19 <reldan> Parallel storage only with config file at the moment and no plans to add it to cli 16:34:33 <szaher> I think if we want to do it we can support it through an interactive cli which builds a config file and we pass it to freezer-agent as a normal job 16:36:12 <Slashme> I think it is good like this, only file for parallel backup. 16:36:13 <reldan> I actually cannot imagine a real guy, who wants to automate backup and interactive cli together :) 16:36:50 <drwho> +1 16:36:51 <Slashme> I don't like interactive stuff. Very hard to automate 16:37:16 <szaher> Agree :) 16:37:40 <Slashme> #topic DSVM gate job 16:38:31 <Slashme> We would like to activate DSVM testing on all repos : freezer and freezer-web-ui 16:38:42 <Slashme> How is that looking ? 16:38:49 <Slashme> ping daemontool vannif 16:39:12 <daemontool> currently it is only enabled as experimental on freezer-api 16:39:49 <daemontool> we need to have the same plugins usable on the other 2 repos 16:39:52 <daemontool> and have it voting 16:43:42 <Slashme> Okay. 16:44:21 <Slashme> Is it challenging? 16:48:16 <Slashme> Lets move on. 16:48:29 <Slashme> #topic liberty 16:48:49 <Slashme> On the wiki, we announced our liberty-compatible release for 18/12/2015 latest. 16:50:00 <Slashme> Are we still targeting this date ? There were some discussions about moving to sometime sooner. 16:50:27 <Slashme> What do we *need* to merge in liberty ? 16:50:27 <daemontool> I think we should 16:51:37 <Slashme> Plans were: 16:51:38 <Slashme> - parallel backup 16:51:38 <Slashme> - oslo.config and oslo.logging 16:52:32 <reldan> Parallel backup - I need your review https://review.openstack.org/#/c/247840/ 16:52:42 <Slashme> daemontool: Why? Is that to facilitate us meeting mitaka releases ? 16:54:26 <daemontool> yes 16:55:41 <Slashme> We already missed mitaka-1 (Dec 1-3) 16:55:46 <daemontool> yes 16:55:53 <daemontool> I think we can join mitaka-2 16:55:57 <daemontool> I need to talk with Doug 16:56:12 <Slashme> mitaka-2 is targeted at Jan 19-21 16:56:41 <daemontool> Slashme: yes 16:56:48 <daemontool> I think as soon as we have the parallel tested and working 16:56:52 <daemontool> we can branch 16:58:16 <daemontool> all, do you agree with that? 16:58:48 <Slashme> All: let's review and test the parallel storage patch: https://review.openstack.org/#/c/247840/ 16:58:55 <daemontool> Slashme: ty 16:59:00 <reldan> thanks 16:59:23 <Slashme> daemontool: So we would be targeting releasing liberty sometime next week ? 16:59:57 <daemontool> that's the idea yes 17:00:03 <daemontool> I think t is reasonable 17:00:47 <Slashme> Anyone against that ? 17:01:27 <Slashme> So let's try to do it next week and then work on Mitaka. 17:01:37 <Slashme> #topic free4all 17:01:58 <Slashme> Someone wants to add something ? 17:02:44 <Slashme> I know szaher wanted to create an interactive client to build configuration file for the freezer-agent. 17:03:26 <Slashme> I guess it could live in the freezer-agent repository as a utility. 17:04:18 <Slashme> szaher Do we already have a blueprint for that where we can discuss the feature ? 17:06:07 <szaher> No, I can create one if you want 17:06:34 <Slashme> We are running out of time. 17:06:57 <szaher> I will create it and will share it here in the room 17:07:10 <Slashme> That would be nice. Thank you 17:07:18 <Slashme> all: Thank you for your time. 17:07:42 <reldan> Thank you 17:07:48 <Slashme> #endmeeting