14:00:27 <slashme> #startmeeting freezer
14:00:27 <openstack> Meeting started Thu Sep 22 14:00:27 2016 UTC and is due to finish in 60 minutes.  The chair is slashme. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:29 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:31 <openstack> The meeting name has been set to 'freezer'
14:00:50 <szaher> Hi slashme
14:00:53 <yangyape_> hello slashme
14:00:59 <szaher> \o/
14:01:03 <slashme> Hi everyone :)
14:01:05 <szaher> \m/
14:01:25 <slashme> Let's wait a few minutes to see if anyone else is connecting
14:01:43 <slashme> As usual, recap and agenda is available here: https://etherpad.openstack.org/p/freezer_meetings
14:02:25 <zhusz> Hi, slashme
14:02:51 <yangyape_> hi zhusz
14:03:00 <timothyb89> hi all
14:03:11 <zhusz> Hi yangpeng
14:03:16 <slashme> Hi zhusz and timothyb89
14:04:54 <domhnallw> o/
14:07:17 <slashme> Okay, lets start.
14:07:30 <ddieterly> hi
14:07:34 <slashme> The agenda is pretty empty today.
14:07:37 <slashme> hi ddieterly
14:07:44 <ddieterly> hi slashme
14:07:51 <slashme> #topic barcelona design sessions
14:08:20 <slashme> We have two design sessions room at the summit this cycle
14:08:42 <slashme> If there is no modification, our slots should be on the Tuesday
14:09:02 <yangyape_> congratulations
14:09:52 <slashme> We have one fishbowl room :Big room, open to the public, can host aroun 50 people, perfect for broader topic and to gather opinions from the community.
14:10:45 <slashme> And one Working room: Smaller, that can host aroud 15 people. These are more intended for engineering discussions between developpers
14:11:23 <slashme> For now, we are completly open to ideas about what you thing should be discussed arounf Freezer at the summit.
14:11:27 <slashme> https://etherpad.openstack.org/p/freezer_meetings
14:11:34 <slashme> Oops, wrong link
14:11:43 <slashme> Here: https://etherpad.openstack.org/p/barcelona_summit_preparation
14:12:14 <slashme> ddieterly and I will be at the summit. Is anyone else going ?
14:12:27 <ddieterly> we'll have a great time
14:19:35 <zhusz> we seem have no more topic
14:19:54 <slashme> zhusz: Indeed
14:20:11 <slashme> Is there anything that someone would like to discuss ?
14:23:30 <ddieterly> not from my end
14:23:47 <ddieterly> currrently working on cassandra schema for monasca
14:24:05 <ddieterly> the cassandra knowledge will transfer nicely to dedup in freezer
14:24:22 <slashme> Interesting :)
14:26:26 <zhusz> Will freezer-scheduler be deprecated next release?
14:28:14 <slashme> No
14:28:29 <slashme> The only thing we deprecate is the command line
14:28:37 <slashme> So basicaly :
14:28:53 <yangyape_> apiclient to python-freezerclient
14:28:57 <slashme> You will be able to do : freezer-scheduler [start/stop/status]
14:29:22 <slashme> and all other operation should be done through the "freezer" cli
14:29:28 <slashme> from python-freezerclient
14:29:57 <yangyape_> guys  if you have time please review freezerclient devstack   https://review.openstack.org/#/c/367251/
14:32:56 <zhusz> Ok. I see.
14:33:56 <zhusz> scheduler issue: https://review.openstack.org/#/c/368082/
14:35:29 <zhusz> freezer-scheduler stop/status is not available when the log file is set in config file.
14:36:13 <zhusz> Because the log info was written to /tmp/freezer-scheduler.pid file.
14:36:47 <zhusz> I'll provide a patch for this issue.
14:38:26 <zhusz> yapeng, I'm checking your patch.
14:38:51 <yangyape_> cli freezer-scheduler  --log-file  ti is ok, but have a config to scheduler.conf is it unavaible?
14:39:55 <yangyape_> zhusz: :)   it is very good to have a patch.
14:42:36 <zhusz> yapeng: Yes.
14:44:33 <slashme> Thank you for the patch zhusz
14:59:08 <slashme> Okay, That's all for today
14:59:13 <slashme> #endmeeting