Wednesday, 2016-03-02

*** dschroeder has quit IRC00:30
*** reldan has quit IRC00:45
*** yangyapeng has joined #openstack-freezer01:05
*** EinstCrazy has joined #openstack-freezer01:09
*** yangyapeng has quit IRC01:43
EinstCrazyanyone can review https://review.openstack.org/#/c/264654/ for me? thanks01:52
*** c00281451_ has joined #openstack-freezer05:13
*** c00281451__ has quit IRC05:17
*** yangyapeng has joined #openstack-freezer05:54
*** Slashme_ has joined #openstack-freezer08:24
*** Slashme_ has quit IRC08:32
*** zhangjn has quit IRC08:43
*** zhangjn has joined #openstack-freezer08:48
*** daemontool_ has joined #openstack-freezer09:08
*** daemontool_ is now known as daemontool09:08
daemontoolEinstCrazy, re: https://review.openstack.org/#/c/264654/3 done09:09
EinstCrazyThanks09:09
daemontoolsomeone else needs to give +A still09:09
*** daemontool__ has quit IRC09:11
daemontoolall, can anyone review this change please https://review.openstack.org/#/c/264654/309:13
*** reldan has joined #openstack-freezer09:14
*** c00281451_ has quit IRC09:18
*** c00281451_ has joined #openstack-freezer09:18
daemontoolslashme, very important09:22
daemontoolwe need to provide an api endpoint09:22
daemontoolthat allows to do upgrades09:22
daemontoolm3m0, if the python-freezerclient code ready to be published to pypi?09:36
daemontoolI can do it, as long as we are sure it works09:36
openstackgerritEldar Nugaev proposed openstack/freezer: Refactoring of mysql, msserver and mongo code.  https://review.openstack.org/28060209:45
daemontoolreldan, ping09:56
reldandaemontool: yes09:56
daemontoolall, so finally I'm restart working on the rsync stuff09:57
daemontoolwanted to discuss some details09:57
reldandaemontool: yes, sure09:57
daemontoolhow do we differenciate the incremental_type ?09:57
daemontoolwith incremental_type? :)09:57
daemontoolso incremental_type>: {'tar', 'rsync', n}09:57
daemontool?09:57
reldandaemontool: currently we have only incremental_type, and only tar09:58
daemontoolyes09:58
daemontoolexactly09:58
daemontoolso we need to make that extendable&pluggable now09:58
reldanbut rsync is incremental as well09:59
daemontoolyes09:59
reldanfor non_incremental we can have level === 009:59
daemontoolso --incremental-type rsync09:59
daemontool--incremental-type tar?09:59
daemontoolsame for config09:59
daemontoolincremental_type09:59
daemontool?09:59
daemontoolwe need to provide an interface to the user where the user can decide if the incremental is block based or file based10:00
daemontool(inode change based)10:00
reldandaemontoll: I don’t know. Incremental-type sounds not very clear, but I have no other options10:00
reldanbackup-engine10:01
daemontoolincremental mode?10:01
reldanbut i don’t know10:01
reldandaemontool: I have doubts about word incremental.10:01
daemontoolslashme, frescof yangyapeng  EinstCrazy m3m0 sc zhangjn any thought?10:01
daemontoolok10:01
slashmeEngine10:02
reldandaemontool: because we can imagine some non-incremental mode10:02
slashmehttps://etherpad.openstack.org/p/freezer_new_archi10:02
daemontoolinsn't engine too general?10:02
daemontoolincremental_engine ?10:02
slashmeWe can have non-incremental, non-compressive, non-encrypting engine10:03
EinstCrazyincremental is supported in the cinder backup now10:03
slashmeThe engine takes data and apply whatever operations it wants to to it10:03
slashmeand sends it the the storage10:03
daemontoolslashme,  ok, my point is, that we need to provide to the user an easy way to say10:03
daemontoolI want to do backup using tar10:03
daemontoolor I want to do backup using rsync block changes10:04
daemontoolso if you have to use freezer as a user10:04
daemontooland you need to define that10:04
slashmeengine=tar / engine=rsync10:04
daemontoolwhat option would you like to have10:04
daemontoolok10:04
slashmeengine=noop10:04
daemontoolok, what do you think if we prepend a prefix to the engine word10:05
slashmeBy noop I mean no operation on the data. They would be sent as is10:05
daemontoolso if we have more engines10:05
daemontoolwe can differentiate?10:05
daemontoolok10:05
daemontoolor engine only is ok_10:05
daemontool?10:05
slashmePlease, check the etherpad I just sent. We already made a big amount of thinking about this10:05
slashmeWe can worry about the naming convention later10:06
daemontoolok10:06
daemontoolso engine10:06
daemontoolnow10:06
daemontoolnext thing10:06
slashmeOr data_engine10:06
daemontoolwe need a way to distinguish10:06
daemontoolthe metadata between tar and rsynx10:06
slashmeand we would have snapshot_engine, storage_engine, ...10:06
daemontoolrsync10:06
daemontoolso now we prepend the metadata as prefix of the file10:07
daemontoolI think we can prepend rsync_ or tar_10:07
daemontoolto identify metadata files generated by tar or rsync10:08
EinstCrazyI think the mode to be a meaningful name? such as backup_mode?10:09
daemontoolEinstCrazy, like adding the mode to the backup file names?10:10
slashmeIt needs to work for backup AND restore.10:11
daemontoolprobably a good idea, but we still need to define10:11
daemontoolhow to identify10:11
daemontoolthe metadata generated with tar or rsync10:11
daemontoolI was thinking about prepending10:11
daemontooltar_meta or rsync_meta10:12
daemontoolto the metadata file10:12
daemontoolor we can have10:12
yangyapengThis is easy to read10:12
daemontoolthe same file10:12
daemontooland parse the content10:12
daemontoolbut for tar10:12
daemontooland also for rsync10:12
daemontoolthe content is binary10:12
daemontoolI'd go for engine prefix10:13
daemontoolwe can change it later10:13
daemontooljust need this to move forward10:13
daemontooland start with10:13
daemontool(by later I mean before merging the code :) )10:13
daemontoolok so10:14
daemontoolengine=(tar,rsync)10:15
daemontooland (tar_meta|rsync_meta)10:15
daemontool?10:15
daemontoolI'm starting with that10:15
daemontoolit is also important to delete/retain backups10:15
daemontoolslashme, one thing we should implement is a better way to retain our old backups10:16
daemontoolnow we remove backup oldr than x10:16
daemontoolor older of certain date10:16
daemontoolon top of that we should probably also provide a feature like10:16
daemontoolretain 1 backup for the last 12 months, even if older than date or n days10:16
slashmeMakes sense10:16
daemontooldo you have bandwidth to do it?10:17
daemontoolor are you interested?10:17
daemontoolor anyone else is interested?10:17
daemontoollike retention_engine10:18
daemontool:)10:18
openstackgerritEldar Nugaev proposed openstack/freezer: Refactoring of mysql, msserver and mongo code.  https://review.openstack.org/28060210:23
slashmedaemontool: I don't see how this could be decorelated from the data_engine.10:37
daemontoolok10:42
daemontoollet's put it in the data_engine then10:43
daemontoolthe only think10:43
daemontoolwe need to have same code to manage delete and retention for backups stored on the storage media10:43
daemontooland also for backup taken using cinder and nova api10:43
daemontoolreldan,  all this is the modified pyrsync code http://paste.openstack.org/show/488924/10:44
reldandaemontool: Good!10:45
daemontoolthat is way faster and memory efficient than https://github.com/isislovecruft/pyrsync/blob/master/pyrsync.py10:45
daemontoolworking on that now10:45
daemontoolafter the first implementation10:45
daemontoolif we can manage to send blocks through pipes10:46
daemontoolrather yielding10:46
daemontooland have multiprocess/threads10:46
daemontoolI'm quite sure it will be way faster10:46
daemontoolthe only slow part will be the math computation for rolling checksum10:46
daemontoolbut that can be improved with pypy a lot10:46
reldandaemontool: Great10:47
reldanIf you need any help with engine - I can help10:47
reldanguys, can you give me +workflow please here https://review.openstack.org/#/c/286592/10:47
daemontoollet me put together the first code10:47
daemontooland we'll review it together10:47
daemontoolwhat I think is high priority from your side10:48
daemontoolis the vm incremental backups (I know we need the design and arch details : ) )10:48
daemontooland the volumes incrementals10:48
daemontooltoo10:48
reldandaemontool: good plan!10:48
daemontoolif we can work in parallel on, rsync incrementals,10:48
daemontoolretention10:48
daemontoolvolumes and instances incrementals10:49
daemontooland dsvm tests10:49
daemontoolin short time we'll be in a way better position10:49
daemontoolreldan,  if you try that pyrsync code when you have time10:50
daemontoolyou'll see10:50
daemontoolthat you have a binary file10:50
daemontoolthan you edit that file10:50
daemontooladd few random code in the middle10:50
daemontooland the alg only will yield that block10:50
daemontoolthere are some limitations tho10:50
daemontoolbut it works10:50
reldandaemontool: I remember that code actually. It was not very fast, but worked10:51
daemontoolreldan, yes10:51
daemontoolI've tried that with pypy10:51
daemontooland is a lot faster10:51
daemontoolthe math part10:51
daemontoolthis https://github.com/isislovecruft/pyrsync/blob/master/pyrsync.py#L162 and this https://github.com/isislovecruft/pyrsync/blob/master/pyrsync.py#L17310:52
daemontoolfunctions10:52
daemontoolare the slow part10:52
*** daemontool_ has joined #openstack-freezer11:15
openstackgerritMerged openstack/freezer: lvm snapshot unique name  https://review.openstack.org/28670511:15
openstackgerritEldar Nugaev proposed openstack/freezer: Refactoring of mysql, msserver and mongo code.  https://review.openstack.org/28060211:15
daemontool_pycharm5 rocks11:16
*** daemontool has quit IRC11:17
*** EinstCrazy has quit IRC11:24
*** yangyapeng has quit IRC11:30
*** daemontool_ has quit IRC11:39
*** daemontool_ has joined #openstack-freezer11:39
openstackgerritMerged openstack/freezer: Fix metadata curr_level  https://review.openstack.org/28659211:41
*** reldan has quit IRC11:43
*** reldan has joined #openstack-freezer12:05
jith_hi all, I tried to use freezer for local backup. I used12:16
jith_ sudo freezerc --path-to-backup original/sample.txt --backup-name backup --storage local --container freezer_backups --action backup12:16
jith_I found12:16
jith_1)No file is created in the given container path(freezer_backups), but a folder named freezer_backups is created in –path-to-backup folder(original) and it contains a file with bkp extension12:16
jith_2) when I tried to restore it with verbose option I got the following error”12:16
jith_ [*] Critical Error: [*] No matching backup name "hostname_backup" found12:16
jith_I am using the stable/kilo version12:17
*** EmilDi has joined #openstack-freezer12:35
reldanjith_: Hi12:37
reldanjith_: I see. Yes, it is bug. But it is expected bug12:38
reldanjith_: For —container for storage local you should use an absolute path to the directory where you want to store your backups12:38
reldanjith_: You have provided relative path and it was created from current directory (yes, it is wrong and should be fixed)12:39
reldanjith_: so please provide absolute path12:40
reldandaemontool_: Do you know what is wrong with py34? https://review.openstack.org/#/c/280602/12:58
daemontool_reldan,  looking13:01
reldandaemontool_: actually now it seems that this path have a merge conflict problem13:02
reldanbut it looks like some problem with github or gerrrit13:02
daemontool_reldan,  try to rebase the change13:02
daemontool_there are some conflicts to fix13:02
reldanyes, resolving conflicts now13:02
daemontool_ok13:03
openstackgerritEldar Nugaev proposed openstack/freezer: Refactoring of mysql, msserver and mongo code.  https://review.openstack.org/28060213:06
*** yangyapeng has joined #openstack-freezer13:19
*** yangyapeng has quit IRC13:22
reldanGuys, please review it https://review.openstack.org/#/c/280602/13:43
daemontool_reldan,  mod shouldn'd be called mode?13:45
reldandaemontool_: I don’t know. I had a review from Saad: “Can we rename Hook to Mod ? Can we use six and abc to abstract this class, just to enforce the Mod developers to follow the design guide lines and implements these functions “13:46
daemontool_ok13:46
daemontool_but if we are referring to modes13:46
reldandaemontool_: But if you suppose it should be mode13:46
daemontool_the correct world in english is mode13:46
reldandaemontool_: Sure, let me fix it13:47
daemontool_s/world/word/13:47
daemontool_is it that?13:47
daemontool_--mode right?13:47
*** yangyapeng has joined #openstack-freezer13:48
reldanyes13:49
slashme+1 let's use mode13:50
*** EmilDi has quit IRC13:50
reldandone13:50
reldandaemontool_ , slashme: done13:51
daemontool_ok13:51
openstackgerritEldar Nugaev proposed openstack/freezer: Refactoring of mysql, msserver and mongo code.  https://review.openstack.org/28060213:52
daemontool_m3m0,  can you test if https://review.openstack.org/#/c/280602/11 work as expected on windows?13:57
daemontool_it should, just to double check13:57
m3m0let me check daemontool13:59
*** daemontool_ is now known as daemontool13:59
m3m0BTW I have vagrant images for windows13:59
m3m0windows 7 8.1 and 1013:59
m3m0to test freezer13:59
daemontoolbrilliant13:59
daemontoolwe should have that test to execute automatically with dsvm13:59
daemontoolgetting the images from a github repo14:00
daemontoollike the one we are using for the binaries14:00
m3m0I'm not so sure if we can upload those images to github14:00
daemontoolok14:00
m3m0but let me check and on top of that is 4.5gb each14:00
daemontoolwhat's the size_14:00
daemontool?14:00
m3m0:(14:00
daemontoolah ok14:00
daemontoolmmhhh14:00
daemontool:(14:00
m3m0just give me a few min, I'm loading again the vms14:03
daemontoolok14:04
daemontoolreldan,  that is a good change...14:06
daemontool(thumbsup)14:06
*** EinstCrazy has joined #openstack-freezer14:06
reldandaemontool: Thank you!14:06
reldandaemontool: next step is extract lvm and shadow to classes14:07
daemontoolthat's anothe rgood one14:17
*** EmilDi has joined #openstack-freezer14:28
reldanGuys, please review https://review.openstack.org/#/c/280602/ Jenkins has +!14:31
reldan+114:31
daemontoolreldan,  yes, let's have m3m0  doing the tests on windows there14:32
daemontoolEmilDi,  hi14:32
reldansure, thank you!14:32
EmilDidaemontool: hi14:33
*** yangyapeng has quit IRC14:51
*** yangyapeng has joined #openstack-freezer14:52
*** yangyape_ has joined #openstack-freezer14:56
*** yangyapeng has quit IRC14:57
*** yangyape_ has quit IRC15:19
*** yangyapeng has joined #openstack-freezer15:19
*** yangyape_ has joined #openstack-freezer15:26
*** yangyape_ has quit IRC15:29
*** yangyapeng has quit IRC15:30
*** dschroeder has joined #openstack-freezer16:05
*** daemontool_ has joined #openstack-freezer16:12
*** daemontool has quit IRC16:13
*** smekel__ has joined #openstack-freezer16:13
*** smekel_ has quit IRC16:15
*** smekel__ is now known as smekel_16:15
*** EinstCrazy has quit IRC16:19
*** reldan has quit IRC17:02
*** yangyapeng has joined #openstack-freezer17:14
*** yangyapeng has quit IRC17:19
openstackgerritDeklan Dieterly proposed openstack/freezer-api: Introduce tempest tests  https://review.openstack.org/28736918:29
*** ddieterly has joined #openstack-freezer18:31
*** zhangjn has quit IRC18:37
*** zhangjn has joined #openstack-freezer18:38
*** EmilDi has quit IRC18:47
daemontool_ddieterly, that's a good one (thumbsup)18:51
*** daemontool_ has quit IRC19:10
ddieterlythanks19:48
*** dschroeder has quit IRC20:34
*** dschroeder has joined #openstack-freezer20:38
*** yangyapeng has joined #openstack-freezer20:50
*** yangyapeng has quit IRC20:57
openstackgerritDeklan Dieterly proposed openstack/freezer-api: Introduce tempest tests  https://review.openstack.org/28736921:14
*** yangyapeng has joined #openstack-freezer22:41
*** yangyapeng has quit IRC22:46
openstackgerritDeklan Dieterly proposed openstack/freezer-api: Introduce tempest tests  https://review.openstack.org/28736922:54
*** ddieterly has quit IRC23:39

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!