14:00:02 <ddieterly> #startmeeting freezer
14:00:03 <openstack> Meeting started Thu May 12 14:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is ddieterly. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:07 <openstack> The meeting name has been set to 'freezer'
14:00:08 <ddieterly> #topic attendance
14:00:13 <ddieterly> o/
14:00:33 <yangyapeng> :)
14:00:44 <saggi> hi
14:00:53 <slashme> Hi ddieterly
14:01:06 <ddieterly> bonjour!
14:01:50 <ddieterly> ok, hopefully others will trickle in
14:01:56 <ddieterly> let's get to it
14:02:11 <ddieterly> #topic specs repo
14:02:15 <ddieterly> what is that?
14:03:31 <ddieterly> whatever it is, it will be finished by eod
14:03:54 <zhangjn> :0
14:04:20 <slashme> We have a freezer-specs repo
14:04:35 <slashme> That should be used from now on to store the specs
14:04:49 <slashme> It needs to be initialized which is what I'm doing atm
14:05:16 <ddieterly> what is involved in initialization?
14:05:41 <slashme> The readme will contain information about the workflow to follow (specs, blueprint, approval, ...)
14:05:54 <ddieterly> oh, so you are adding content to it
14:06:07 <slashme> Initialization is writing the readme/doc + create the file hierarchy
14:07:29 <daemontool> o/
14:07:38 <thatsdone> o/
14:08:49 <daemontool> is there the Freezer meeting going on here?
14:09:02 <slashme> daemontool: yes
14:09:09 <ddieterly> ok, so slashme is adding a napoleonic twist to the freezer-spec repo by regimenting it
14:09:20 <ddieterly> daemontool supposedly
14:10:03 <slashme> We forgot to say that the agenda for the meeting is available here as usual : https://etherpad.openstack.org/p/freezer_meetings
14:10:14 <slashme> Feel free to add any topic you want to discuss
14:10:14 <ddieterly> slashme thanks
14:10:52 <ddieterly> what do we want to discuss about the freezer-specs repo?
14:12:22 <daemontool> we need to move the dr bp there after the specs repo setup
14:12:29 <ddieterly> nothing?
14:12:36 <ddieterly> can we move to the next topic then?
14:12:42 <slashme> Nothing right now. Just wanted to point out that when it'll ve ready, this will be the way to go to submit specs
14:12:45 <daemontool> sounds good for me
14:13:03 <ddieterly> how does that affect blueprints?
14:13:12 <daemontool> the bp cannot be approved
14:13:17 <daemontool> right now
14:13:28 <daemontool> that does not mean the implementation cannot be done
14:13:33 <daemontool> but the bp needs to be there
14:13:45 <ddieterly> so, the spec is the same thing as the bp?
14:14:03 <daemontool> the specs repo is where the project bp are placed
14:14:04 <ddieterly> just under review process?
14:14:14 <ddieterly> ok
14:14:14 <daemontool> ddieterly,  nope
14:14:22 <slashme> ddieterly: I'll point you to the workflow as soon as it is finished
14:14:23 <ddieterly> is that the way other projects do it?
14:14:24 <daemontool> so check the freezer-specs repo layout
14:14:27 <slashme> That will be simpler
14:14:37 <daemontool> and check the nova-specs layout
14:14:40 <daemontool> we have to do that
14:14:47 <daemontool> that's what we are referring to
14:14:57 <slashme> ddieterly: That's how most project procede, you can check the nova-specs repo
14:15:07 <ddieterly> ok
14:15:35 <thatsdone> FYI: https://github.com/openstack/nova-specs
14:15:54 <ddieterly> yep, looking now...
14:16:06 <ddieterly> beautiful
14:16:27 <daemontool> thatsdone, nice name :)
14:16:28 <ddieterly> beau
14:16:30 <ddieterly> bello
14:16:32 <daemontool> ok
14:16:35 <daemontool> next?
14:16:51 <ddieterly> #topic freezer DR
14:17:06 <ddieterly> where is the repo?
14:17:17 <szaher> Repo is created and available here https://github.com/openstack/freezer-dr
14:17:37 <daemontool> that is a great achievement
14:17:39 <daemontool> :)
14:17:47 <daemontool> we need to get approved this in governance https://review.openstack.org/#/c/314288/
14:17:57 <szaher> we have only one issue right now the code was written based on kilo release so we need to check with liberty and mitaka or at least mitaka
14:18:14 <daemontool> then add the diagrams form the austin preso to the repo
14:18:24 <daemontool> szaher, good, we need to tag it then
14:18:38 <daemontool> not a bad thing, as it works from kilo onwards
14:18:43 <daemontool> but I don-t think we can branch now
14:18:45 <ddieterly> the gate jobs need to be added
14:18:49 <daemontool> slashme, ?
14:18:52 <daemontool> ddieterly,  yes
14:19:10 <daemontool> ddieterly, they should be added
14:19:22 <daemontool> if you are referring to the governance repo
14:19:23 <szaher> we need to think about it
14:19:27 <slashme> daemontool: yes ?
14:19:38 <daemontool> slashme,  about tagging dr repo
14:19:43 <daemontool> for kilo, liberty, mitaka
14:19:50 <daemontool> I don't think we can branch now
14:19:56 <daemontool> but definetely we can tag
14:20:00 <szaher> as we need to have at least two compute nodes in our devstack deployment
14:20:23 <daemontool> ddieterly,  ah yes, the dsvm gate job is disabled there oyu are right
14:21:13 <ddieterly> did we get a lot of support for this project from the community?
14:21:28 <ddieterly> i heard 2 people voice concerns that this was out of scope
14:21:39 <daemontool> ddieterly,  from HP?
14:21:56 <ddieterly> dan dyer and there were 2 others in the dev meetup before slashme arrived
14:22:05 <daemontool> ok
14:22:10 <ddieterly> the 2 others were from different companies
14:22:22 <daemontool> I've heard 2 people too
14:22:24 <daemontool> from different companies
14:22:27 <daemontool> saying that
14:22:43 <daemontool> than I discovered they wanted to upstream their own new project in openstack
14:22:50 <daemontool> to do that
14:22:54 <ddieterly> lol
14:22:55 <daemontool> :)
14:23:15 <ddieterly> well, on the face of it, it does seem to go far afield of freezer's core mission
14:23:40 <ddieterly> wanders into monitoring and recovery/mitigation
14:23:46 <daemontool> well if you look at the mission in governance, we are there https://governance.openstack.org/reference/projects/freezer.html
14:24:21 <daemontool> so
14:24:22 <ddieterly> i think we would do better to focus on making recovery simpler
14:24:26 <daemontool> I agree
14:24:29 <ddieterly> that's what i heard at the conference
14:24:37 <ddieterly> ymmv
14:24:42 <daemontool> in my opinion, if we want to split it at some point
14:24:45 <daemontool> I'm OK
14:24:49 <daemontool> and I agree on the recovery also
14:25:31 <ddieterly> ok
14:25:34 <slashme> I agree with all of that
14:25:34 <daemontool> I agree on giving higher priority to abckup and restore though
14:25:41 <slashme> daemontool: +1
14:25:53 <szaher> daemontool: +1
14:25:56 <daemontool> that's definetely our main focus at least for now
14:26:09 <daemontool> but let's see if others are interested on contributing
14:26:20 <ddieterly> sure, sounds like a plan
14:26:27 <zhangjn> +1
14:26:28 <ddieterly> anything else on that topic?
14:26:30 <daemontool> glad we all agree :)
14:26:33 <slashme> :)
14:26:45 <ddieterly> oh, i wish i could give fausto a big hug right now
14:26:46 <thatsdone> +1
14:27:09 <daemontool> ddieterly, everytime I try to hug you in person you do not want that
14:27:12 <daemontool> haha
14:27:32 <ddieterly> it takes a while for americans to get used to physical contact
14:27:38 <daemontool> ok
14:27:45 <ddieterly> we have a large personal space
14:28:13 <ddieterly> i'll have to come to italy and get immersed in all the touching
14:28:19 <daemontool> haha
14:28:21 <daemontool> ok
14:28:39 <ddieterly> ok, anything else on dr?
14:28:41 <daemontool> next?
14:28:42 <zhangjn> what's the next?
14:28:54 <ddieterly> #topic ceph isssues
14:29:18 <zhangjn> what's issue?
14:29:30 <ddieterly> good question, glad you asked
14:29:43 <ddieterly> who put that topic on the agenda?
14:29:51 <daemontool> I thing there was someone
14:29:52 <yangyapeng> ping Silviu
14:29:56 <daemontool> askign the IRC channel
14:30:06 <daemontool> about a problem related to that
14:30:13 <daemontool> don-t know
14:30:24 <daemontool> let-s go next and we can come back to this later?
14:30:30 <daemontool> slashme, maybe knows about it?
14:31:06 <yangyapeng> SIlviu  meet a problem
14:31:29 <ddieterly> ok, next topic
14:31:47 <slashme> Yes, Silviu had a problem
14:31:47 <ddieterly> #topic PyPI
14:32:09 <slashme> We should implement something similar to https://review.openstack.org/gitweb?p=openstack/horizon.git;a=commitdiff;h=8201d65cf983f9c995dd653953ad1719f6df8459
14:32:54 <ddieterly> #topic PyPI
14:33:05 <slashme> In order to manage content lenght when doing swift upload
14:33:16 <daemontool> slashme, ok yes
14:33:30 <slashme> For the PyPI topic,
14:33:36 <daemontool> reldan, are you interested on doing that? or anyone else?
14:33:43 <slashme> We need to update our package in pypi
14:33:48 <daemontool> slashme, where you thinking about someone?
14:33:55 <slashme> I noticed that most of them are outdated
14:34:11 <slashme> daemontool: This is a pretty low hanging fruit
14:34:17 <daemontool> shouldn't be that update automatically by the bot?
14:34:25 <daemontool> slashme, yes ok
14:34:33 <slashme> Anyone that has acces to a ceph cluster can fix this
14:34:54 <daemontool> ok
14:36:10 <reldan> daemontool: I’m doing it right now
14:36:11 <reldan> yes
14:36:11 <daemontool> we can ask to Infra
14:36:24 <daemontool> about why the pypi packages are not updated
14:36:25 <daemontool> anymore
14:36:27 <yangyapeng> slashme:  we have a ceph cluster ,but it also in the performance test
14:36:54 <slashme> It shouldn't affect performance at all
14:37:08 <slashme> And it shouldn't cause any bug on the ceph side
14:37:10 <daemontool> well probably yangyapeng needs to ask permission and all that
14:37:26 <slashme> Do  you have a RadosGw ?
14:37:27 <daemontool> as that ceph instance is already used by another team
14:38:32 <ddieterly> process check, we need to move along
14:38:48 <zhangjn> we have not install radosgw.
14:38:49 <yangyapeng> the ceph cluster also used by another team. we can test it in next scrum. .
14:39:31 <ddieterly> can we move to next topic?
14:39:33 <zhangjn> What's worry with ceph?
14:39:41 <slashme> Okay. You need the radosgw in order to emulate the swift api if you want to use ceph with freezer.
14:40:04 <slashme> We should be able to find a ceph cluster here to test the patch.
14:40:12 <slashme> ddieterly: okay, next topic
14:40:18 <yangyapeng> next
14:40:33 <zhangjn> I got it, I will think about this Scenario.
14:40:39 <ddieterly> #topic nova, cinder backup to local/ssh issues
14:40:58 <ddieterly> szaher you have the floor
14:41:18 <yangyapeng> about backup nova and swift to local.
14:41:36 <yangyapeng> In the process of actual backup, there is no swift, but more NFS, etc.
14:41:42 <ddieterly> is szaher in the mtg today?
14:41:52 <yangyapeng> so, we have more need to backup it
14:41:54 <szaher> There is a patchset from yangyapeng that can do the backup but we won't be able to restore it as we didn't store the metadata
14:42:01 <szaher> ddieterly: Yes I am here :)
14:42:23 <ddieterly> szaher yay!
14:42:28 <yangyapeng> https://review.openstack.org/#/c/315085/
14:42:31 <zhangjn> how to store metadata?
14:42:43 <zhangjn> database or file?
14:43:02 <szaher> There is a patchset on freezer-metadata done by reldan I reviewed it with him to store the metadata with the backup file so we can restore everything according to this metadata file
14:43:38 <szaher> the metadata patch https://review.openstack.org/#/c/314209/ we need to review it by today as we need it urgently for another patchsets
14:44:14 <szaher> yangyapeng: This patchset we won't be able to restore the backup files https://review.openstack.org/#/c/315547/ ! as we don't have any metadata info available
14:45:06 <szaher> ddieterly: We need to merge the metadata patchset first then me and reldan are going to work on building cinder engine and nova engines
14:45:25 <ddieterly> ok
14:45:27 <szaher> so we will have tar engine for fs related backups, cinder engine for OS cinder and nova for OS nova backups
14:45:52 <yangyapeng> this patch I have a backup about instance._info, we restore backupfile  use it ,it is ok ?
14:45:56 <szaher> Also daemontools is working or rsync engine
14:47:06 <ddieterly> so, is everybody who needs to going to do the reviews?
14:47:38 <yangyapeng> I have a json to store it in uuid-meta. Although this is so humble 。
14:47:57 <szaher> everyone is welcome to review the patchset
14:48:10 <yangyapeng> thank you
14:48:12 <ddieterly> suound like you want it approved
14:48:21 <ddieterly> so, core members need to jump on it
14:48:28 <szaher> yangyapeng: we have blueprints so if you want you can work on some of them, the metadata one is here https://blueprints.launchpad.net/freezer/+spec/freezer-metadata
14:48:54 <ddieterly> next topic?
14:48:55 <szaher> ddieterly: core and non core are more than welcomed :) we need more eyes
14:49:14 <ddieterly> szaher of course
14:49:37 <ddieterly> #topic tripleO bp
14:49:51 <ddieterly> who owns that one?
14:50:24 <ddieterly> who is asking for that?
14:50:45 <ddieterly> why is it on the agenda?
14:50:45 <yangyapeng> This is anonymous ？
14:51:00 <ddieterly> (i'll keep asking questions until somebody responsds ;-) )
14:51:04 <daemontool> I added it
14:51:07 <slashme> I guess this is daemontool
14:51:13 <daemontool> sorry one sec
14:51:14 <ddieterly> ah ha!
14:51:18 <daemontool> someone come to by desk
14:51:22 <yangyapeng> 哈哈
14:51:25 <yangyapeng> haha
14:51:26 <daemontool> I'll give update
14:51:33 <daemontool> to the freezer channel
14:51:49 <daemontool> basically we need to support
14:52:09 <daemontool> rh osp
14:52:16 <daemontool> or that kind
14:52:20 <daemontool> of os distributions
14:52:26 <daemontool> that uses tripleo
14:52:35 <daemontool> and ironic
14:52:38 <thatsdone> Ah, that's why tripleo ? (OSP7 now uses tripleo)
14:52:50 <ddieterly> is this something that errickson is asking for?
14:53:54 <daemontool> ddieterly,  nope
14:53:58 <daemontool> ericsson uses Fuel
14:53:59 <daemontool> mirantis
14:54:02 <daemontool> that was requested
14:54:14 <daemontool> by users that use RH in their productino environment
14:55:00 <ddieterly> ok
14:55:14 <ddieterly> daemontool are you going to write the bp?
14:55:23 <daemontool> I should yes
14:55:31 <daemontool> also I have RH OSP available here
14:55:35 <ddieterly> excellent
14:55:36 <daemontool> slashme,  do you have the
14:55:42 <daemontool> contacts of that guy
14:55:49 <daemontool> Radoslaw if I remembe rwell
14:55:54 <daemontool> he had the ideas quite clear
14:55:59 <daemontool> he could write it
14:56:03 <daemontool> I can do it in case
14:56:19 <slashme> Let me check
14:57:31 <ddieterly> while he's off checking, how about the bp for dedup?
14:57:42 <ddieterly> daemontool you planning on writing that too?
14:57:51 <daemontool> I think
14:57:56 <daemontool> Fabrizio could probably write that
14:57:57 <zhangjn> first bp in freezer-spec
14:58:03 <zhangjn> :)
14:58:11 <daemontool> zhangjn,  :)
14:58:14 <ddieterly> which fabrizio?
14:58:18 <daemontool> Fresco
14:58:40 <ddieterly> 2 mins remainaing
14:59:07 <ddieterly> #topic pending reviews
14:59:24 <ddieterly> please take a look at the reviews in the agenda and review if possible
14:59:42 <daemontool> ok
14:59:55 <ddieterly> this one is particularly easy  https://review.openstack.org/#/c/315250/
15:00:23 <ddieterly> ok, out of time
15:00:30 <ddieterly> thanks everybody who participated
15:00:31 <daemontool> thanks ddieterly
15:00:36 <slashme> thank you ddieterly
15:00:38 <zhangjn> Time is always short, :)
15:00:39 <ddieterly> can continue discussion in freezer room
15:00:45 <ddieterly> ciao!
15:00:48 <ddieterly> #endmeeting