Monday, 2016-04-11

*** reldan has quit IRC00:10
*** EinstCrazy has joined #openstack-freezer01:11
*** yangyapeng has joined #openstack-freezer01:13
*** EinstCrazy has quit IRC01:31
*** EinstCrazy has joined #openstack-freezer01:35
*** EinstCrazy has quit IRC01:35
*** EinstCrazy has joined #openstack-freezer01:35
*** yangyape_ has joined #openstack-freezer01:43
*** yangyapeng has quit IRC01:47
*** EinstCrazy has quit IRC02:10
*** EinstCrazy has joined #openstack-freezer02:15
*** yangyapeng has joined #openstack-freezer03:41
*** yangyape_ has quit IRC03:45
*** yangyapeng has quit IRC04:26
*** EinstCrazy has quit IRC04:57
*** EinstCrazy has joined #openstack-freezer05:01
*** yangyapeng has joined #openstack-freezer05:15
*** dimsum__ has quit IRC05:40
*** dims has joined #openstack-freezer05:47
*** EinstCrazy has quit IRC06:15
*** EinstCrazy has joined #openstack-freezer06:15
*** dims has quit IRC06:31
*** EinstCrazy has quit IRC06:35
*** EinstCrazy has joined #openstack-freezer06:35
*** daemontool has joined #openstack-freezer06:53
*** dims has joined #openstack-freezer06:54
*** dims has quit IRC06:58
*** dims has joined #openstack-freezer07:45
openstackgerrityapeng Yang proposed openstack/freezer: Deleted the tempfile freezer_job  https://review.openstack.org/30393907:53
*** reldan has joined #openstack-freezer07:55
*** reldan has quit IRC08:14
*** reldan has joined #openstack-freezer08:21
*** reldan has quit IRC08:31
*** dims has quit IRC08:48
*** dims has joined #openstack-freezer08:55
*** reldan has joined #openstack-freezer09:04
slashmeGood morning everyone. Hope you had a great weekend :)09:14
szaherGood morning slashme, hope you too had a nice weekend09:38
yangyapeng:)09:38
yangyapengGood morning09:38
yangyapenghttps://review.openstack.org/#/c/303939/  https://review.openstack.org/#/c/303701/  jenkins has a -1, so....09:39
szahervannif Could you please, take a look here https://review.openstack.org/#/c/303390/09:56
yangyapengping szaher hello10:23
yangyapengabout  https://review.openstack.org/#/c/303939/  freezer-scheduler schedule_interval 20 minutes, so  It create many tmp file.10:24
yangyapengszaher: you mean, we shoud  not to care about it ?10:25
*** EinstCrazy has quit IRC10:31
*** yangyapeng has quit IRC10:33
*** yangyapeng has joined #openstack-freezer10:36
szaheryangyapeng: Hello10:38
yangyapengszaher: the freezer-agent backup_args.conf   create the tmp _file , where is  used it ? I don't understand, thx10:39
szaheryangyapeng: We use this not every time freezer runs but we use it only when the user provides a up/down limits10:40
szaheryangyapeng: Your bug is about fixing the scheduler and you can find this here https://github.com/openstack/freezer/blob/864be88b6c864ced9018ee5d51819bd0600945c5/freezer/scheduler/scheduler_job.py#L29310:40
szaherit's already handled10:41
yangyapengszaher:  I see it , but when freezer-scheduler,  the  freezer_job_tmp is created, but it is not deleted auto.10:43
yangyapengWhether you have encountered this problem10:43
*** reldan has quit IRC10:45
szaheryangyapeng: I need to test that first, let me check it and will be back to you10:46
yangyapengOK thanks10:46
*** yangyapeng has quit IRC10:47
*** reldan has joined #openstack-freezer11:02
openstackgerritSaad Zaher proposed openstack/freezer: Allow freezer to use trickle installed system wide  https://review.openstack.org/30404711:20
*** kelepirci_ has joined #openstack-freezer11:22
*** kelepirci has quit IRC11:24
openstackgerritFabrizio Vanni proposed openstack/freezer-api: fix session-remove-job  https://review.openstack.org/29237311:25
*** clenimar has joined #openstack-freezer11:37
*** zhonghua-lee has quit IRC11:45
*** zhonghua-lee has joined #openstack-freezer11:46
*** kelepirci_ has quit IRC12:07
*** kelepirci_ has joined #openstack-freezer12:08
*** fozkasgarli__ has joined #openstack-freezer12:14
*** vannif has quit IRC12:14
*** yangyapeng has joined #openstack-freezer12:17
*** kelepirci_ has quit IRC12:17
*** vannif has joined #openstack-freezer12:17
*** dims has left #openstack-freezer12:20
openstackgerritFabrizio Vanni proposed openstack/freezer-api: fix session-remove-job  https://review.openstack.org/29237312:29
*** EinstCrazy has joined #openstack-freezer12:34
openstackgerritFabrizio Vanni proposed openstack/freezer-api: fix session-remove-job  https://review.openstack.org/29237313:04
openstackgerritFabrizio Vanni proposed openstack/freezer-api: fix session-remove-job  https://review.openstack.org/29237313:06
*** kelepirci_ has joined #openstack-freezer13:08
*** fozkasgarli__ has quit IRC13:09
openstackgerritFabrizio Vanni proposed openstack/freezer-api: fix session-remove-job  https://review.openstack.org/29237313:10
* vannif needs more coffe13:10
openstackgerritCynthia Lopes do Sacramento proposed openstack/freezer: Adds checksum before backup and after restore for consistency check.  https://review.openstack.org/30008013:48
*** ddieterly has joined #openstack-freezer13:49
daemontoolall, it would neat to do something like:13:59
daemontool1) backup this file13:59
daemontool2) execute this api call, get whatever metadata and store it with the file as part of the backup14:00
daemontoolbut more something genral...14:00
daemontoolfile -> api call14:00
daemontoolin theory sounds good, in practice does it make sense?14:00
*** ddieterly is now known as ddieterly[away]14:21
*** ddieterly[away] is now known as ddieterly14:23
vannifyou mean the backup metadata, right ?14:23
vannifthe text document containing json formatted information14:24
vannifbasically, the same information that gets uploaded to the api14:25
vannifwe were discussing that some days ago. it definitely makes sense.14:25
daemontoolyes14:27
daemontoolfile associated with metadata from openstack services api14:28
daemontoolnope I think I'm saying something different14:28
daemontoolyou backup a file or a directory in the fs, like an image file as /var/lib/nova/instances/2113424545/sdlfklsjfg.qcow14:29
daemontooland execute an api call that save the metadata related to that file14:29
daemontoolas part of the backup14:29
daemontoolsomething like that14:29
vannifyou mean: retrieving the openstack metadata information and save it along the backup ? that information belongs to the client, right ? it should be retrieved by the freezerclient and saved along the backup. the role of the api is minimal as it's only involved if you want to upload that metadata as part of the backup metadata.14:38
vannifor do you think the api should make use of the token provided by the client to access openstack informations belonging to the user whi makes the request ?14:39
vannifs/whi/who14:39
openstackgerritCynthia Lopes do Sacramento proposed openstack/freezer: Adds checksum before backup and after restore for consistency check.  https://review.openstack.org/30008014:42
daemontoolvannif,  I have no idea what you are saying lol :)14:43
daemontoolthe only thing I'm proposing is14:43
daemontoolwhen executing a fs backup14:43
daemontooladd also optionally an api call to nova (can be any service) to store metadata from a service api, as part of the backup14:44
daemontoolnothing more14:44
daemontoolso for nova and cinder, you can backup volumes and vms, directly from the storage filesystem if possible, and also associate the files with metadata from nova and&or cinder14:46
slashmeSorry daemontool, I'm not following you.14:50
slashmeWhat would be the purpose of this api call ?14:50
vannifto retrieve information about the backup, I guess. but how can freezer know that the file /var/lib/nova/instances/2113424545/sdlfklsjfg.qcow has some metadata associated in nova ?14:54
daemontoolvannif,  that part of the problem15:00
daemontoolthat is part of the problem to solve15:00
daemontoolit's just an idea15:04
daemontoolbut I think it's helpful15:05
*** dschroeder has joined #openstack-freezer15:06
*** openstackgerrit has quit IRC15:18
*** openstackgerrit has joined #openstack-freezer15:18
*** yangyapeng has quit IRC15:22
*** daemontool_ has joined #openstack-freezer15:26
*** daemontool_ has quit IRC15:26
*** daemontool_ has joined #openstack-freezer15:27
*** daemontool has quit IRC15:28
*** ddieterly is now known as ddieterly[away]15:48
*** ddieterly[away] is now known as ddieterly15:51
openstackgerritSaad Zaher proposed openstack/freezer: Allow freezer to use trickle installed system wide  https://review.openstack.org/30404716:11
*** reldan has quit IRC16:47
*** daemontool__ has joined #openstack-freezer16:57
*** daemontool_ has quit IRC17:00
*** sxc731 has joined #openstack-freezer17:18
*** ddieterly is now known as ddieterly[away]17:31
sxc731Hi there will Freezer work with Ceph RadosGW (in Swift emulation mode)?17:43
slashmeIt should. At least that's our expectation. I don't know if that was tested recently though.17:46
sxc731Great thanks!  I'm certainly interested in trying it out...17:47
slashmeAnd I'm certainly interested in any results.17:49
sxc731;-)17:49
sxc731I'm off to the datacentre tomorrow to install a 3-nodes/6-OSD Ceph cluster to use as a backup cluster for our Kilo environment17:50
sxc731Are there any caveats to installing the Freezer server-side components on top of a running Kilo cluster?17:51
slashmeHmm. It should be mostly okay. We have some running Kilo clusters that work fine.17:52
*** ddieterly[away] is now known as ddieterly17:53
sxc731OK thanks v.much I may be back with some q's in time...17:53
slashmeI'm still trying to merge that bug fix: https://review.openstack.org/#/c/298895/117:53
slashmeYou may want to apply it17:53
*** reldan has joined #openstack-freezer17:54
sxc731Thanks for the pointer. Seems no commit for the kilo branch; presumably it's not too hard to adapt?17:57
sxc731(sorry ignore me)17:58
slashmeBut now I'm thinking about it, if you only want to do testing, you should also be able to install a more recent freezer (liberty or mitaka) on top of your Kilo cluster. We did not test that though.18:00
sxc731The intention is certainly to use that in production at some point...18:00
sxc731Is there a big feature gap between the branches?18:01
slashmeFrom kilo to liberty, I'd say average.18:02
slashmeLiberty and Mitaka are almost the same.18:02
slashmeWe plan for some big features/refactoring in Newton.18:02
sxc731Life on the bleeding edge ;-)18:03
sxc731Which version is HPE using in production?18:04
slashmeKilo for HOS 2.0 and 2.1 (current productions).18:05
slashmeHOS 3.0 will release very soon with Liberty.18:05
slashmeHOS 4.0 should follow "pretty quickly" with Mitaka.18:05
sxc731Cheers! One last q: Freezer is now part of the "Big Tent" right?18:05
slashmeyes18:06
sxc731That's what I thought;, maybe the FAQ should be18:06
sxc731... adjusted. It says "we hope to get it in there soon" or smth similar18:06
slashmeOhh18:06
slashmeYes18:06
sxc731It's a nice milestone for sure!18:07
*** daemontool__ has quit IRC18:10
*** ddieterly is now known as ddieterly[away]18:16
*** ddieterly[away] is now known as ddieterly18:44
openstackgerritPierre Mathieu proposed openstack/freezer: Update the Freezer FAQ.rst  https://review.openstack.org/30428418:45
*** daemontool has joined #openstack-freezer18:46
sxc731nice one ;-)18:48
openstackgerritDeklan Dieterly proposed openstack/freezer: Add test of mysql backup  https://review.openstack.org/30429218:59
openstackgerritDeklan Dieterly proposed openstack/freezer: Add test of mysql backup  https://review.openstack.org/30429219:01
sxc731Curious: why is Freezer labelled as a "DR as a Service" solution (with the Horizon UI also claiming to be "Disaster Recovery")?  Presumably it covers more mundane backup/restore needs?19:16
m3m0sxc731: Hey, at the moment we have backup and restore functionalty of the infrastructure and we are working in a disaster recovery solution: https://review.openstack.org/#/c/278242/19:20
sxc731Hey m3m0: thanks!  Just so I'm sure I understand: I can use Freezer to backup/restore arbitrary filesystems (as well as select DBs) that live inside VMs provisioned by OpenStack, right?19:24
m3m0yep, you can do that, windows and linux vm's19:25
openstackgerritDeklan Dieterly proposed openstack/freezer: Add test of mysql backup  https://review.openstack.org/30429219:25
m3m0even mac :)19:25
m3m0for db we only support mysql, mongo, and sql server19:26
m3m0any suggestion of db's that we should support?19:26
*** ddieterly is now known as ddieterly[away]19:27
sxc731Good stuff! From my (obviously subjective) PoV: this use-case likely has more universal appeal than DR, which sounds a fair bit more sophisticated... I just wonder if the "DR" label (particularly in Horizon) might not turn away people, who may be looking for "plain" backups... Just my £.02 ;-)19:30
sxc731DBs-wise, Mongo and MySQL cover my current use-cases.  I seem to remember you also have ElasticSearch, right?19:31
m3m0we use elasticsearch in the backend :) and it make sense to name it backup and restore19:32
m3m0we'll do it in the next iteration, have you worked with the ui?19:33
sxc731Not yet, I'm contemplating installing the whole stack to use in a production environment.19:34
sxc731I need a backup solution for my cloud and I'm loath to buy into a $$$-proprietary solution, hence the appeal.  Plus Freezer looks like a reasonably young product so I'm hoping I can feedback & contribute along the way ;-)19:36
*** ddieterly[away] is now known as ddieterly19:50
*** ddieterly is now known as ddieterly[away]19:52
m3m0that could be great, the more the better and please don't hesitate in contacting us if you need help19:54
*** ddieterly[away] is now known as ddieterly19:55
*** sxc731 has quit IRC19:55
*** openstackgerrit has quit IRC20:05
*** openstackgerrit has joined #openstack-freezer20:28
*** ddieterly is now known as ddieterly[away]20:35
*** dschroeder has quit IRC20:36
*** openstackgerrit has quit IRC20:41
*** ddieterly[away] is now known as ddieterly20:42
*** openstackgerrit has joined #openstack-freezer20:55
*** dschroeder has joined #openstack-freezer21:00
openstackgerritDeklan Dieterly proposed openstack/freezer: Add test of mysql backup  https://review.openstack.org/30429221:20
ddieterlycan mysql be backed up if the host it is on is not using lvm?21:26
*** ddieterly is now known as ddieterly[away]21:48
*** EinstCrazy has quit IRC21:59
*** ddieterly[away] is now known as ddieterly22:37
*** ddieterly is now known as ddieterly[away]22:55
*** ddieterly[away] is now known as ddieterly22:55
*** ddieterly is now known as ddieterly[away]23:05
*** ddieterly[away] has quit IRC23:06
*** reldan has quit IRC23:48

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