14:00:53 <m3m0> #startmeeting freezer
14:00:54 <openstack> Meeting started Thu Aug 25 14:00:53 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:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:57 <openstack> The meeting name has been set to 'freezer'
14:01:20 <ddieterly> o/
14:01:22 <slashme> \o/
14:03:26 <ddieterly> does not look like much on the agenda today
14:03:48 <slashme> Indeed
14:04:21 <timothyb89> hello all
14:04:26 <m3m0> and we are only 4
14:04:29 <ddieterly> has anyone heard from daemontool?
14:05:00 <yangyapeng> hello
14:05:31 <slashme> We had some news that he is okay after the earthquake in Italia. But appart from that, nothing work related.
14:05:54 <ddieterly> ok, good
14:05:57 <domhnallw_> Glad to hear that he's okay. That earthquake was terrible.
14:07:51 <yangyapeng> Good luck
14:08:25 <slashme> szaher, timothyb89 : What should we do with this: https://review.openstack.org/357289 ?
14:15:44 <szaher> slashme: I think this patch should be ready to go
14:16:07 <szaher> it's not refactoring of test cases but we needed to change some test cases and not all to make the change work
14:17:18 <timothyb89> slashme, szaher: I'll +1 if some details are added to the commit message :)
14:17:50 <szaher> fair enough, gonna do that now :)
14:18:05 <slashme> Thx timothyb89
14:18:10 <yangyapeng> i have review that patch. +1
14:19:07 <szaher> timothyb89: Can I add this to the FreezerBaseTestCase ?
14:19:20 <timothyb89> what do you mean?
14:19:20 <szaher> Like a description of the class or you want this in commit message anyway ?
14:19:35 <timothyb89> oh, really I just mean commit message
14:19:37 <szaher> description about test changes
14:20:12 <szaher> Ok
14:20:15 <timothyb89> no need for any code changes I don't think, just a quick blurb so we can see in the commit history if needed for debugging, etc
14:23:44 <szaher> timothyb89: Check now
14:23:52 <szaher> #link https://review.openstack.org/#/c/357289/
14:24:25 <timothyb89> szaher: thanks, +1 :)
14:24:52 <szaher> timothyb89: Thanks :)
14:30:34 <szaher> Can we review this small and quick change https://review.openstack.org/#/c/360529/1 ?
14:33:03 <yangyapeng> please review freezer-web-ui , backups https://review.openstack.org/#/c/357058/
14:33:21 <yangyapeng> thanks , small bug
14:38:49 <ddieterly> yangyapeng i'm not that familiar with the web-ui, so i'm not able to review your patch
14:39:11 <m3m0> yangyapeng: I know what you did there :)
14:39:35 <m3m0> it was like that before
14:39:45 <yangyapeng> thanks
14:39:51 <m3m0> list_all, will list backups regardless of the client
14:40:00 <yangyapeng> ddieterly: m3m0  :) yeah
14:40:01 <m3m0> list will only list backups tied to a client
14:41:15 <yangyapeng> m3m0: I have a common in your patch https://review.openstack.org/#/c/358677/8, but It is irrelevant in patch.
14:41:44 <yangyapeng> i have a irrelevant about freezer-scheduler
14:43:40 <m3m0> you mean, what happens if a the scheduler stops and the starts again, what will happen with the jobs?
14:43:49 <yangyapeng> Now, if freezer-scheduler have a restart, it should fetch job from freezer-api, and exec all nocomplete job right now,rather than by start_time and so on
14:43:49 <m3m0> yangyapeng: ^^
14:44:34 <yangyapeng> if i have a start_time in 12:00 PM sat ,interval 1 weeks.
14:44:49 <m3m0> could be that seems like another patch, right now there is a bug that all completed jobs gets executed again if the scheduler restarts
14:45:01 <m3m0> I'll fix that after the parallel execution
14:45:16 <yangyapeng> m3m0:   thanks .
14:45:25 <m3m0> but we should discuss this better
14:45:49 <yangyapeng> hnhn.
14:46:27 <m3m0> "if i have a start_time in 12:00 PM sat ,interval 1 weeks."
14:46:53 <m3m0> wanna finish the example?
14:47:12 <szaher> m3m0: Could you add +A here https://review.openstack.org/#/c/360529/
14:48:12 <m3m0> done
14:48:22 <yangyapeng> yeah, if I config it , and it have a backup, but i restart freezer-scheduler in today,  then all job should backup it in today and evey meek on Thursday. not sat
14:48:31 <m3m0> #topic  Core team update
14:49:45 <slashme> Just a small heads up, we are going to have a few updates on the core team, some cleaning and the addition of yangyapeng as a core. Please whatch out for the email on the mailing list (later today).
14:50:46 <yangyapeng> thanks slashme :)
14:50:53 <yangyapeng> m3m0: :)
14:50:55 <m3m0> thanks for the update slashme
14:51:08 <m3m0> and congratulations yangyapeng :)
14:51:46 <yangyapeng> :) thank you. all guys
14:52:11 <szaher> yangyapeng: Welcome to the Core team :)
14:52:18 <szaher> m3m0: https://review.openstack.org/#/c/357289/ :) :)
14:52:54 <yangyapeng> szaher: thank you.  thank you. :)
14:54:30 <m3m0> do you want to discuss the scheduler later mr core yangyapeng :)
14:55:13 <yangyapeng> m3m0: haha yeah.I'm very glad
14:56:36 <yangyapeng> channel #freezer  later
14:57:21 <m3m0> is there any other topic?
14:57:24 <m3m0> can we close the meeting?
14:57:54 <m3m0> #endmeeting