16:00:55 <m3m0> #startmeeting openstack-freezer 10-12-2015
16:00:56 <openstack> Meeting started Thu Dec 10 16:00:55 2015 UTC and is due to finish in 60 minutes.  The chair is m3m0. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:57 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:59 <openstack> The meeting name has been set to 'openstack_freezer_10_12_2015'
16:01:09 <m3m0> All: meetings notes available in real time at: https://etherpad.openstack.org/p/freezer_meetings
16:01:10 <daemontool> ok I'm sorry
16:01:15 <daemontool> sorry for the delay
16:01:25 <m3m0> please raise your hand if you are here :)
16:01:27 <m3m0> o/
16:02:27 <daemontool> \o
16:03:11 <m3m0> ok so far 2 :) the rest of the people are very busy around here
16:03:33 <m3m0> daemontool, any news on the oslo logging?
16:03:45 <daemontool> emildi: reldan  Slashme  szaher frescof
16:04:04 <reldan> Here
16:04:40 <daemontool> m3m0:  I can start
16:05:11 <m3m0> cool :) go ahead
16:05:24 <daemontool> I think this can be approved https://review.openstack.org/#/c/252568/ (oslo)
16:05:43 <daemontool> szaher:  did that, we need to do that also for the agent
16:05:46 <daemontool> after that is merged
16:05:49 <daemontool> we are going to merge
16:05:52 <daemontool> the parallel
16:06:07 <daemontool> https://review.openstack.org/#/c/247840/
16:06:12 <daemontool> from reldan
16:06:16 <m3m0> is that ready to merge? reldan?
16:06:27 <m3m0> did you test it on windows as well?
16:06:27 <reldan> After this is merged, I probably need to rebase atop of oslo and change config
16:07:03 <daemontool> ok
16:07:04 <daemontool> after taht
16:07:15 <daemontool> from my side
16:07:29 <daemontool> I'm working on creating a new python-freezerclient repo
16:07:30 <daemontool> now
16:07:32 <daemontool> we need to define
16:07:33 <daemontool> what stepd
16:07:37 <daemontool> we need to take
16:07:38 <daemontool> for taht
16:07:42 <daemontool> because there's a proposal
16:08:41 <daemontool> can't find the review
16:08:48 <m3m0> do you have a time for when the python-freezerclient will be ready?
16:08:50 <daemontool> to deprecate all the openstack clients
16:08:55 <daemontool> one sec
16:09:05 <daemontool> in favor
16:09:09 <daemontool> of python-openstackclient
16:09:14 <daemontool> so what do we do?
16:09:34 <daemontool> are we going to create a separate repo or are we going only to contribute to openstackclient?
16:09:41 <daemontool> I've received
16:09:41 <m3m0> we need to figure it out if there are guidelines to integrate us in that repo
16:09:52 <daemontool> couple of feedback on this
16:09:57 <m3m0> which is?
16:09:57 <daemontool> quite opposite
16:10:01 <daemontool> but both good
16:10:16 <daemontool> one was to go for our client independent
16:10:24 <daemontool> but the public proposal says otherwise
16:10:29 <daemontool> I think both make sense
16:10:47 <daemontool> but probably we do not want to maintain both
16:10:55 <daemontool> and go only for oen approach
16:11:07 <m3m0> nope, and if the python-freezerclient will be deprecated there is no point to work on that
16:11:30 <daemontool> yes but we need to be sure about that
16:11:32 <daemontool> and....
16:11:39 <daemontool> if we are going directly on openstackclient
16:11:46 <daemontool> we really need to do a planning job
16:11:48 <daemontool> now
16:12:18 <m3m0> do you have a proposition for this planning?
16:12:26 <daemontool> all, any thoughts?
16:12:32 <daemontool> I have a blueprint
16:12:39 <daemontool> and a first commit
16:12:41 <daemontool> but needs to be extended
16:13:12 <m3m0> could you send the link for both?
16:13:19 <daemontool> https://blueprints.launchpad.net/freezer/+spec/freezerclient
16:13:58 <daemontool> https://review.openstack.org/#/c/255349/
16:14:02 <daemontool> and one sec
16:14:05 <daemontool> I'm trying to find
16:14:08 <daemontool> the public proposal
16:14:12 <daemontool> from AJaeger
16:14:45 <daemontool> here https://review.openstack.org/#/c/243348/
16:15:03 <daemontool> also we need to create a freezer-specs
16:15:05 <daemontool> and fill it
16:16:19 <m3m0> Jokke_ comment make a lot of sense
16:16:33 <daemontool> as usual :)
16:18:19 <daemontool> anyway
16:18:21 <daemontool> that's the thing
16:18:22 <m3m0> so, should we wait to see what happens with that commit?
16:18:25 <daemontool> probably we need to wait there
16:18:29 <daemontool> yes
16:18:41 <daemontool> a part code reviews, and that two topics
16:18:48 <daemontool> that's all from me
16:18:49 <m3m0> so, in the meantime we continue working with parallel backups and oslo logging
16:18:57 <daemontool> there's one disaster ecovery
16:18:58 <daemontool> yes
16:19:03 <daemontool> page I've found
16:19:07 <daemontool> I think we should align
16:19:07 <daemontool> one sec
16:19:14 <m3m0> send it please
16:19:46 <jokke_> reminder about the osc ... it still needs the freezer-pythonclient
16:19:56 <jokke_> osc is just the clie wrapper from it
16:20:14 <daemontool> https://wiki.openstack.org/wiki/DisasterRecovery
16:20:24 <daemontool> jokke_:  thanks
16:20:25 <daemontool> ok
16:20:47 <m3m0> then lets move forward with the freezerclient
16:20:53 <daemontool> and also this if we want https://wiki.openstack.org/w/images/4/49/Openstack_disaster_recovery_-_openstack_meetup.pdf
16:20:57 <daemontool> ok
16:22:47 <m3m0> ok, lots of material there, should we complement that info with freezer?
16:24:17 <daemontool> I think so
16:24:49 <m3m0> do you want to do that?
16:25:10 <m3m0> btw I'll be off the rest of the year so we need to find a temporary chairman :)
16:25:42 <daemontool> yes I think we can stop
16:25:45 <daemontool> the weekly meeting
16:25:51 <daemontool> the 17th
16:25:59 <daemontool> will be the last one?
16:26:10 <daemontool> and restart the 7th of Jan?
16:27:07 <m3m0> ok sounds good but still someone needs to take care of this next week
16:27:24 <m3m0> daemontool, reldan any plans for the tenant backup?
16:27:48 <daemontool> m3m0:  good one, we need that
16:27:55 <daemontool> m3m0:  please record on etherpad
16:27:57 <daemontool> also
16:28:04 <daemontool> thank you
16:28:49 <daemontool> m3m0:  I'll do the chairman next week
16:28:55 <daemontool> where's Vanni?
16:29:36 <m3m0> he's busy
16:29:42 <daemontool> ah ok
16:31:06 <daemontool> m3m0: I think now we can support that
16:31:16 <m3m0> we can iterate over this: https://blueprints.launchpad.net/freezer/+spec/tenant-backup
16:31:17 <daemontool> can't remember now what was specifically needed
16:31:34 <daemontool> ah yes....
16:31:35 <daemontool> sorry
16:31:37 <daemontool> got it
16:31:51 <daemontool> we need more time to think about it
16:32:01 <daemontool> but for sure we can proceed
16:32:13 <daemontool> using the othe rservice native apis
16:33:01 <daemontool> to get the information / dataat least from keystone, neutron, nova -> glance, cinder -> glance
16:33:02 <daemontool> etc
16:33:11 <daemontool> reldan: we'll discuss about this next week
16:33:13 <m3m0> yes because working only on a file system level could be very very difficullt
16:33:57 <reldan> Sure, it is really complex task. As far as I know there are no one cloud provider (amazon, azure … ) with functionality like that
16:34:15 <m3m0> we will be the first :)
16:34:44 <m3m0> anything else to say on this topic?
16:34:53 <reldan> But it’s really should be well defined ) At least because we cannot make a copy of tenant (ID is alway unique)
16:34:59 <daemontool> reldan:  that's one more good reason to do it :D
16:35:04 <daemontool> yes
16:39:53 <m3m0> do you have anything else to say today guys?
16:40:16 <daemontool> m3m0: you?
16:40:34 <daemontool> any news related to web ui or alike?
16:40:41 <daemontool> windows side all good?
16:40:42 <m3m0> I've been very busy in another project this week
16:40:47 <daemontool> ok
16:41:13 <m3m0> on the windows side there is an update that i would like to do to the scheduler to not need the user password to get installed
16:41:23 <daemontool> ok
16:41:24 <m3m0> but I need to do more testing there
16:41:28 <daemontool> that's a good one
16:41:59 <m3m0> so we can use this installer from cloud-init https://github.com/memogarcia/freezer-installer
16:42:25 <m3m0> so when a windows vm gets deployed it already has freezer installed
16:42:38 <m3m0> and maybe to register this automatically as well
16:42:59 <m3m0> on the ui, I'm waiting for the parallel backups to implement the ui part of that
16:43:10 <m3m0> but will be a big change on the ui
16:44:15 <daemontool> ok
16:44:31 <daemontool> m3m0:  did we created a dedicated repo for that?
16:44:40 <daemontool> called openstack-freezer-utils?
16:44:52 <m3m0> yes, but I haven't move the repos there
16:44:59 <m3m0> I'll do that over the weekend
16:45:04 <m3m0> and update the readmens
16:45:04 <daemontool> ah ok
16:45:07 <m3m0> readmes*
16:48:52 <m3m0> that's pretty much all from my side
16:52:54 <daemontool> ok
16:56:46 <m3m0> ok guys thanks to all for participate :) I know we are all very bussy
16:56:48 <m3m0> #endmeeting