| *** dschroeder has quit IRC | 00:16 | |
| *** reldan has quit IRC | 00:54 | |
| *** yangyapeng has joined #openstack-freezer | 01:05 | |
| *** yangyapeng has quit IRC | 01:06 | |
| *** yangyapeng has joined #openstack-freezer | 01:26 | |
| yangyapeng | ping daemontool | 01:27 |
|---|---|---|
| *** EinstCrazy has joined #openstack-freezer | 04:32 | |
| *** EinstCrazy has quit IRC | 05:27 | |
| *** yangyape_ has joined #openstack-freezer | 05:28 | |
| *** yangyape_ has quit IRC | 05:28 | |
| *** yangyape_ has joined #openstack-freezer | 05:30 | |
| *** yangyapeng has quit IRC | 05:32 | |
| *** sc has quit IRC | 05:46 | |
| *** yangyapeng has joined #openstack-freezer | 06:21 | |
| *** yangyape_ has quit IRC | 06:22 | |
| *** yangyapeng has quit IRC | 06:25 | |
| *** yangyapeng has joined #openstack-freezer | 06:26 | |
| yangyapeng | ping daemontool | 07:26 |
| yangyapeng | hi daemontool | 08:05 |
| *** yangyapeng has quit IRC | 08:09 | |
| *** yangyapeng has joined #openstack-freezer | 08:10 | |
| daemontool | yangyapeng, yes | 08:12 |
| yangyapeng | i have a question about freezer job | 08:13 |
| yangyapeng | daemontool: freezer-agent --action restore --mode fs --storage local --restore-abs-path /opt/stack/restore --container /opt/stack/back/ --backup-name backup1 | 08:13 |
| yangyapeng | it is ok, bot i write a json , it have a job. schedule---> runing -->complete but it fail | 08:14 |
| daemontool | how's the content of the json file? | 08:15 |
| daemontool | the freezer-agent use ini format | 08:15 |
| daemontool | the scheduler use json format | 08:15 |
| yangyapeng | { | 08:16 |
| yangyapeng | "job_actions": [ | 08:16 |
| yangyapeng | { | 08:16 |
| yangyapeng | "freezer_action": { | 08:16 |
| yangyapeng | "action": "backup", | 08:16 |
| yangyapeng | "mode" : "fs", | 08:16 |
| yangyapeng | "backup_name": "backuptest", | 08:16 |
| yangyapeng | "path-to-backup": "/tmp/", | 08:16 |
| yangyapeng | "storage": "local", | 08:16 |
| yangyapeng | "container": "/opt/stack/backup/" | 08:16 |
| yangyapeng | }, | 08:16 |
| yangyapeng | "max_retries": 5, | 08:16 |
| yangyapeng | "max_retries_interval": 60, | 08:16 |
| yangyapeng | "mandatory": true | 08:16 |
| yangyapeng | } | 08:16 |
| yangyapeng | ], | 08:16 |
| yangyapeng | "job_schedule" : { | 08:16 |
| yangyapeng | }, | 08:16 |
| yangyapeng | "description": "freezer test backup" | 08:16 |
| yangyapeng | } | 08:16 |
| yangyapeng | [stack@dev49 devstack]$ freezer-scheduler job-list | 08:16 |
| yangyapeng | \+----------------------------------+---------------------+-----------+-----------+-------+--------+------------+ | 08:17 |
| yangyapeng | | job_id | description | # actions | status | event | result | session_id | | 08:17 |
| yangyapeng | +----------------------------------+---------------------+-----------+-----------+-------+--------+------------+ | 08:17 |
| yangyapeng | | 300aab1ad8264526ae393fc77be57f3f | freezer test backup | 1 | completed | | fail | | | 08:17 |
| yangyapeng | +----------------------------------+---------------------+-----------+-----------+-------+--------+------------+ | 08:17 |
| daemontool | yangyapeng, what's the output of | 08:20 |
| daemontool | freezer-scheduler client-list | 08:20 |
| yangyapeng | +----------------------------------------+----------+-------------+ | 08:21 |
| yangyapeng | | client_id | hostname | description | | 08:21 |
| yangyapeng | +----------------------------------------+----------+-------------+ | 08:21 |
| yangyapeng | | 2c6d384e530044fcb021e2d7d4d5f6f5_dev49 | dev49 | | | 08:21 |
| yangyapeng | +----------------------------------------+----------+-------------+ | 08:21 |
| yangyapeng | tenant_id_host | 08:21 |
| yangyapeng | freezer-schedule backup nova has a question too | 08:22 |
| daemontool | ok | 08:22 |
| daemontool | paste in paste.openstack.org the last 200 lines of /var/log/freezer-scheduler.log and /var/log/freezer.log | 08:23 |
| daemontool | or /var/log/freezer/freezer-scheduler.log | 08:23 |
| daemontool | or /var/log/freezer/freezer.log | 08:23 |
| yangyapeng | .freezer/freezer-api.log and freezer-api.log | 08:24 |
| yangyapeng | http://paste.openstack.org/show/489640/ | 08:29 |
| yangyapeng | ping daemontool | 08:29 |
| daemontool | lookins | 08:29 |
| daemontool | looking | 08:29 |
| daemontool | yangyapeng, I see the following line in the logs | 08:31 |
| daemontool | 2016-03-08 07:06:33.023 3399 CRITICAL freezer.main [-] [*] Critical Error: [Errno 13] Permission denied: '~' | 08:31 |
| daemontool | try to execute the following command please | 08:32 |
| daemontool | freezer-agent --storage local --path-to-backup /tmp --container /opt/stack/back/ --backup-name backup-fs-tmp-1 | 08:33 |
| daemontool | do you have permissions to write to /opt/stack/back ? | 08:34 |
| yangyapeng | oh it is ok | 08:37 |
| yangyapeng | [stack@dev49 1457401066]$ ls | 08:37 |
| yangyapeng | dev49_backup1_1457401066_0 tar_metadata_dev49_backup1_1457401066_0 | 08:37 |
| yangyapeng | [stack@dev49 1457401066]$ pwd | 08:37 |
| yangyapeng | /opt/stack/back/dev49_backup1/1457401066 | 08:37 |
| yangyapeng | [stack@dev49 1457401066]$ | 08:37 |
| yangyapeng | backup and restore is ok. use freezer-agent | 08:40 |
| ferhat | hello daemontool | 08:41 |
| ferhat | I want to change following wiki or at least I want to propose a change | 08:42 |
| ferhat | https://wiki.openstack.org/wiki/Freezer | 08:42 |
| ferhat | do I need to clone any source for this page? | 08:42 |
| daemontool | ferhat, nope | 08:44 |
| daemontool | the wiki is just a normal wiki | 08:44 |
| daemontool | so you need to create an account | 08:44 |
| daemontool | and edit it | 08:44 |
| ferhat | I see. but I think I am having a problem with creating account | 08:45 |
| daemontool | according to where you are doing your changes | 08:45 |
| daemontool | my advise would be to add that info also in the README | 08:45 |
| daemontool | of the related repo | 08:45 |
| daemontool | and to do that | 08:45 |
| daemontool | you need to clone the repo | 08:45 |
| daemontool | ferhat, what's the problem you are having? | 08:46 |
| ferhat | thx. I have cloned the repos. just need to configure garret | 08:47 |
| daemontool | gerrit | 08:49 |
| daemontool | ok | 08:50 |
| yangyapeng | Have I to use the freezer-agant backup nova . Is it ok use scheduler? | 08:51 |
| daemontool | yangyapeng, you can use the freezer-agent | 08:51 |
| daemontool | what really execute backups if the agent | 08:51 |
| daemontool | the scheduler is the component that execute the agent and report things to the api | 08:51 |
| *** reldan has joined #openstack-freezer | 08:52 | |
| ferhat | yes gerrit | 08:54 |
| daemontool | slashme, can you check please if this change works from your side? https://review.openstack.org/#/c/277352/ | 08:55 |
| yangyapeng | { | 08:55 |
| yangyapeng | "job_actions": [ | 08:55 |
| yangyapeng | { | 08:55 |
| yangyapeng | "freezer_action": { | 08:55 |
| yangyapeng | "action": "backup", | 08:55 |
| yangyapeng | "mode" : "fs", | 08:55 |
| yangyapeng | "nova-inst-id": "7a88855c-ab3d-41d5-8d40-fddd7816d3a7", | 08:55 |
| yangyapeng | "backup_name": "backuptest", | 08:55 |
| yangyapeng | "storage": "local", | 08:55 |
| yangyapeng | "container": "/opt/stack/backup/" | 08:55 |
| yangyapeng | }, | 08:55 |
| yangyapeng | "max_retries": 5, | 08:55 |
| yangyapeng | "description": "freezer test backup" | 08:56 |
| yangyapeng | } | 08:56 |
| yangyapeng | is it ok ? | 08:56 |
| daemontool | yes you just need to pass the nova-inst-id | 08:58 |
| daemontool | reldan, do you remember if nova-inst-id is the same if passed from cmd line or within a config file? | 08:59 |
| daemontool | freezer-agent --nova-inst-id 3ad7a62f-217a-48cd-a861-43ec0a04a78b | 08:59 |
| daemontool | yangyapeng, that would be enough | 08:59 |
| daemontool | as no actions currently are really recorded for vm backups | 08:59 |
| daemontool | it just execute the nova api call to execute the backup | 08:59 |
| yangyapeng | the job's status is running but i don't see it result to backup. container": "/opt/stack/backup/" is empty. | 09:05 |
| yangyapeng | backup_madia nova is ok？ or storage local is ok? | 09:06 |
| yangyapeng | If no work？ | 09:07 |
| daemontool | yangyapeng, nova | 09:12 |
| daemontool | I mean freezer uses the nova api | 09:12 |
| daemontool | to execute the backup of the vm | 09:12 |
| daemontool | so the files are not stored in the storage media used normally by freezer | 09:13 |
| daemontool | it's similar to the nova backup command | 09:14 |
| daemontool | the vm backup support is very basic | 09:15 |
| *** reldan has quit IRC | 09:16 | |
| yangyapeng | oh, the code .1. get instance_id 2. create snapshot image 3. upload 4. delete image | 09:17 |
| daemontool | yes | 09:17 |
| yangyapeng | I think this will upload directly to storage media,ha ha :) | 09:19 |
| yangyapeng | thx | 09:19 |
| *** reldan has joined #openstack-freezer | 09:24 | |
| *** reldan has quit IRC | 09:26 | |
| daemontool | yangyapeng, reldan implemented that part | 09:30 |
| daemontool | all can we review https://review.openstack.org/#/c/288416/ | 09:31 |
| daemontool | yangyapeng, in the README is reported | 09:32 |
| daemontool | "Nova backups | 09:32 |
| daemontool | To make a nova backup you should provide a nova parameter in the arguments. Freezer doesn't do any additional checks and assumes that making a backup of that instance will be sufficient to restore your data in future." | 09:32 |
| daemontool | that is one of the features | 09:33 |
| daemontool | we need to improve | 09:33 |
| yangyapeng | ok :) | 09:33 |
| daemontool | yangyapeng, hang on I see a bit of interesting code | 09:35 |
| daemontool | here https://github.com/openstack/freezer/blob/master/freezer/backup.py#L48 | 09:35 |
| daemontool | ah ok | 09:36 |
| daemontool | sorry yangyapeng | 09:36 |
| daemontool | so, there 2 approaches | 09:37 |
| yangyapeng | ok | 09:37 |
| daemontool | 1 is just executing a backup using the nova api | 09:37 |
| daemontool | the one I was mentioning | 09:37 |
| daemontool | then there's another one to reduce the risks of data inconsistencies | 09:38 |
| daemontool | with mysql db | 09:38 |
| daemontool | where you can execute a flush tables, before executing a nova image snapshot | 09:38 |
| daemontool | so the code there is for that use case | 09:38 |
| daemontool | this would be the example | 09:39 |
| daemontool | freezer-agent --mysql-conf /root/.freezer/freezer-mysql.conf | 09:39 |
| daemontool | --container freezer_mysql-backup-prod --mode mysql | 09:39 |
| daemontool | --backup-name mysql-ops002 | 09:39 |
| daemontool | --nova-inst-id 3ad7a62f-217a-48cd-a861-43ec0a04a78b | 09:39 |
| daemontool | same can be done with cinder | 09:39 |
| daemontool | flush the db and execute the snapshot | 09:39 |
| daemontool | now did you execute that with --mode fs? | 09:39 |
| daemontool | cause support 2 approaches | 09:40 |
| daemontool | novanative and cindernative | 09:40 |
| daemontool | what just uses the api | 09:40 |
| daemontool | so by using the --mode fs with the command you pasted here previously | 09:41 |
| daemontool | are you downloading the nova instance? | 09:41 |
| daemontool | that was what you were saying? | 09:41 |
| yangyapeng | backup_media = 'fs' | 09:54 |
| yangyapeng | if backup_args.cinder_vol_id: | 09:54 |
| yangyapeng | backup_media = 'cinder' | 09:54 |
| yangyapeng | elif backup_args.cindernative_vol_id: | 09:54 |
| yangyapeng | backup_media = 'cindernative' | 09:54 |
| yangyapeng | elif backup_args.nova_inst_id: | 09:54 |
| yangyapeng | backup_media = 'nova' | 09:54 |
| yangyapeng | I has a mod =fs and nova_inst_id=xxxx so, backup-madia = nova | 09:54 |
| yangyapeng | wait I look it again | 09:55 |
| *** fabv has joined #openstack-freezer | 10:03 | |
| daemontool | all, can we review please https://review.openstack.org/#/c/288416/ | 10:10 |
| *** openstackgerrit has quit IRC | 10:33 | |
| *** openstackgerrit has joined #openstack-freezer | 10:33 | |
| m3m0 | yangyapeng: in your job file path-to-backup should be path_to_backup, did you fix your problem already? | 10:38 |
| yangyapeng | ? the shoud replace auto the code | 10:39 |
| yangyapeng | command = attr[3:].replace('_', '-') | 10:40 |
| yangyapeng | oh i see , i have a try | 10:41 |
| yangyapeng | [stack@dev49 ~]$ freezer-scheduler job-get --job e089b3fd4bb64b67bf063e8fcc304348 | 10:43 |
| yangyapeng | { | 10:43 |
| yangyapeng | "user_id": "2aaa101aff584d5b962fd96c4f2db4a3", | 10:43 |
| yangyapeng | "description": "freezer test backup", | 10:43 |
| yangyapeng | "_version": 1, | 10:43 |
| yangyapeng | "job_schedule": { | 10:43 |
| yangyapeng | "time_ended": -1, | 10:43 |
| yangyapeng | "time_started": -1, | 10:43 |
| yangyapeng | "time_created": 1457433746 | 10:43 |
| yangyapeng | }, | 10:43 |
| yangyapeng | "client_id": "2c6d384e530044fcb021e2d7d4d5f6f5_dev49", | 10:44 |
| yangyapeng | "job_actions": [ | 10:44 |
| yangyapeng | { | 10:44 |
| yangyapeng | "user_id": "2aaa101aff584d5b962fd96c4f2db4a3", | 10:44 |
| yangyapeng | "freezer_action": { | 10:44 |
| yangyapeng | "backup_name": "backuptest", | 10:44 |
| yangyapeng | "container": "/opt/stack/backup/", | 10:44 |
| yangyapeng | "path_to_backup": "/tmp/", | 10:44 |
| yangyapeng | "storage": "local", | 10:44 |
| yangyapeng | "mode": "fs", | 10:44 |
| yangyapeng | "action": "backup" | 10:44 |
| yangyapeng | }, | 10:44 |
| yangyapeng | i have a Incorrect writing， thank you , | 10:45 |
| *** yangyapeng has quit IRC | 10:49 | |
| daemontool | fabv, would be good if the scheduler print in the log the option that is not correct | 10:57 |
| *** fubi has quit IRC | 10:59 | |
| daemontool | m3m0, slashme fabv frescof when you get the change can you review please https://review.openstack.org/#/c/288416/ | 11:04 |
| m3m0 | and remember we have code walkthrough this week | 11:11 |
| daemontool | fabv, ^^ | 11:12 |
| daemontool | we have the code walkthrough on the scheduler | 11:12 |
| szaher | daemontool: sorry I wasn't using the PC for a while :), If you added a non existing option to the config file, I think oslo.config won't consider this options | 11:18 |
| slashme | daemontool: reviewing https://review.openstack.org/#/c/288416/ and https://review.openstack.org/#/c/277352/ today | 11:20 |
| szaher | slashme: Can you take a look at this one https://review.openstack.org/#/c/288008/ ? | 11:23 |
| szaher | https://review.openstack.org/#/c/288422/ | 11:23 |
| daemontool | szaher, do we have somewhere the list of all the accepted options? | 11:25 |
| openstackgerrit | Saad Zaher proposed openstack/freezer-api: Updating freezer-api elk mappings https://review.openstack.org/288486 | 11:33 |
| szaher | daemontool: for the scheduler run this command inside freezer repo oslo-config-generator --config-file config-generator/scheduler.conf | 11:35 |
| szaher | this will generate all available opts and put it in etc/scheduler.conf.sample | 11:36 |
| daemontool | szaher, ok ty, can we put that in the README when you get the chance? | 11:36 |
| szaher | Sure | 11:37 |
| daemontool | the same apply for the agent? | 11:37 |
| szaher | It can apply to the agent but we agreed we are not going to have a config file for the agent | 11:37 |
| szaher | the functionality is there but I didn't provide a config file for the agent | 11:38 |
| szaher | daemontool: if you want to see all options available for the agent execute this command oslo-config-generator --namespace freezer --namespace oslo.log | 11:39 |
| daemontool | ok, but let's say there's a user that want to see all the available optinos for the agent | 11:39 |
| daemontool | ok | 11:39 |
| daemontool | that's what I was looking for | 11:39 |
| daemontool | please add that to the README when you can | 11:39 |
| daemontool | thanks a lot! | 11:39 |
| szaher | Ok, sure | 11:39 |
| m3m0 | that's a good point | 11:41 |
| szaher | daemontool: README or HACKING ? | 11:45 |
| daemontool | I think, in README goes the list of options and how to get it | 11:47 |
| daemontool | in HACKING goes what do I have to do to add a new option | 11:47 |
| daemontool | which is what I have to do right now :) | 11:48 |
| daemontool | both of them :) | 11:48 |
| szaher | OK :) | 11:48 |
| openstackgerrit | Merged openstack/freezer: Adding option disable-exec to freezer-scheduler https://review.openstack.org/288008 | 11:48 |
| m3m0 | freezer ui now uses python freezerclient :) | 11:51 |
| daemontool | brilliant | 11:52 |
| daemontool | m3m0, sorry today I'm going to upload the package to pypi | 11:52 |
| *** EinstCrazy has joined #openstack-freezer | 11:56 | |
| openstackgerrit | Saad Zaher proposed openstack/freezer: Updating README and HACKING files for oslo options https://review.openstack.org/289881 | 12:03 |
| szaher | daemontool: Please, take a look https://review.openstack.org/#/c/289881/ | 12:03 |
| daemontool | szaher, ++ | 12:04 |
| *** yangyapeng has joined #openstack-freezer | 12:10 | |
| openstackgerrit | Saad Zaher proposed openstack/freezer: Updating README and HACKING files for oslo options https://review.openstack.org/289881 | 12:18 |
| *** ferhat has quit IRC | 12:27 | |
| daemontool | szaher, not sure I totally got how I can add options to the agent | 12:27 |
| daemontool | I'm ok for the scheduler, and also how to add options to the scheduler | 12:28 |
| daemontool | but not the agent | 12:28 |
| daemontool | https://www.openstack.org/summit/austin-2016/summit-schedule/events/7211 | 12:55 |
| openstackgerrit | Memo Garcia proposed openstack/freezer-web-ui: Move from freezer to python-freezerclient https://review.openstack.org/289906 | 13:01 |
| daemontool | szaher, got it thanks | 13:02 |
| daemontool | I think it's worth to mention that new options for the agent needs to be added in common/config.py, while for scheduler in scheduler/arguments.py | 13:11 |
| openstackgerrit | Saad Zaher proposed openstack/freezer: Updating README and HACKING files for oslo options https://review.openstack.org/289881 | 13:21 |
| szaher | daemontool: https://review.openstack.org/#/c/289881/ | 13:22 |
| openstackgerrit | Saad Zaher proposed openstack/freezer: Updating README and HACKING files for oslo options https://review.openstack.org/289881 | 13:23 |
| daemontool | szaher, looks better now, thanks :) | 13:26 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer: Refactoring of code: https://review.openstack.org/288416 | 13:39 |
| zhangjn | ping daemontool | 13:53 |
| daemontool | zhangjn, yes | 13:56 |
| zhangjn | Some example is worry in README.rst | 13:59 |
| zhangjn | how to backup a file in local? | 14:00 |
| zhangjn | sudo freezerc --file-to-backup /data/dir/to/backup --container /tmp/my_backup_path/ --backup-name my-backup-name --storage local | 14:00 |
| zhangjn | freezerc is not option --file-to-backup | 14:01 |
| openstackgerrit | Fabrizio Vanni proposed openstack/freezer-api: add database status check https://review.openstack.org/289931 | 14:02 |
| daemontool | file-to-backup is deprecated | 14:03 |
| daemontool | --path-to-backup | 14:03 |
| zhangjn | thx | 14:06 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer: Refactoring of code: https://review.openstack.org/288416 | 14:20 |
| openstackgerrit | Fabrizio Vanni proposed openstack/freezer-api: add database status check https://review.openstack.org/289931 | 14:30 |
| zhangjn | how to check backup info by freezerc? | 14:31 |
| zhangjn | freezerc --action info --container /tmp/bak --backup-name my-backup-name --storage local | 14:31 |
| *** ddieterly has joined #openstack-freezer | 14:33 | |
| zhangjn | is right? | 14:33 |
| *** EinstCrazy has quit IRC | 14:34 | |
| m3m0 | as far as I know, you can;t do this now | 14:35 |
| m3m0 | but | 14:35 |
| m3m0 | in python-freezerclient you will be able to get individual backup information | 14:35 |
| zhangjn | I will try the README.rst operation, but something is not work. | 14:37 |
| zhangjn | how to use python-freezerclient | 14:38 |
| zhangjn | I can test it. | 14:38 |
| *** fabv has quit IRC | 14:40 | |
| m3m0 | is under development yet, but should be release this week I think | 14:41 |
| zhangjn | if the python-freezerclient is finish, whether the freezerc will be instead? | 14:42 |
| zhangjn | python-freezerclient in this repo:https://github.com/memogarcia/python-freezerclient | 14:44 |
| zhangjn | m3m0 | 14:44 |
| m3m0 | yes, I'm updating the README now | 14:45 |
| m3m0 | it should work now BTW | 14:45 |
| m3m0 | and you could be my first beta tester :) | 14:45 |
| zhangjn | my pleasure. | 14:48 |
| zhangjn | I have some doubt. | 14:53 |
| zhangjn | python-freezerclient is call freezer-api, is right? | 14:53 |
| m3m0 | yes | 14:54 |
| m3m0 | only for interacting with the api | 14:54 |
| m3m0 | is a complete different component than the agent | 14:54 |
| szaher | m3m0: +1 workflow here https://review.openstack.org/#/c/289881/4 | 14:55 |
| m3m0 | szaher: done | 14:56 |
| daemontool | the point is, how to show backup info if the api are not available... | 14:56 |
| daemontool | all can we review this commit please https://review.openstack.org/#/c/288416/ | 14:56 |
| szaher | szaher: thanx | 14:56 |
| szaher | m3m0: thanx | 14:57 |
| zhangjn | now I backup use freezerc. | 14:58 |
| zhangjn | where is backup info store? | 14:59 |
| *** fabv has joined #openstack-freezer | 15:05 | |
| zhangjn | I think backup/restore info and action info should be store in db. | 15:07 |
| openstackgerrit | Merged openstack/freezer: Updating README and HACKING files for oslo options https://review.openstack.org/289881 | 15:16 |
| daemontool | https://review.openstack.org/#/c/288416/ | 15:19 |
| daemontool | zhangjn, it is stored in a db | 15:19 |
| daemontool | if you have the api | 15:19 |
| zhangjn | all backup or other action must call api to do. | 15:21 |
| zhangjn | now I can use freezerc cli to backup file or other action. | 15:21 |
| daemontool | zhangjn, yes the agent (freezerc or freezer-agent) only talks to the storage media | 15:29 |
| daemontool | the scheduler and the freezerclient only talks ot he api | 15:29 |
| daemontool | s/ot he/to the/ | 15:30 |
| *** EinstCrazy has joined #openstack-freezer | 15:34 | |
| *** EinstCrazy has quit IRC | 15:41 | |
| *** dschroeder has joined #openstack-freezer | 15:53 | |
| *** daemontool_ has joined #openstack-freezer | 15:59 | |
| *** daemontool has quit IRC | 16:01 | |
| *** ferhat has joined #openstack-freezer | 16:12 | |
| daemontool_ | all, con you review this when you get the chance please https://review.openstack.org/#/c/288416/ | 16:34 |
| slashme | daemontool_: Hp has a release comming very quickly (liberty), I'm not very confortable merging this without its backport to liberty ready as it would hurt our capability to merge and backport fix quickly. | 16:39 |
| *** EinstCrazy has joined #openstack-freezer | 16:40 | |
| slashme | reldan: can you work on that backport please ? It shouldn't be too big of a job anyway | 16:40 |
| *** EinstCrazy has quit IRC | 16:46 | |
| daemontool_ | slashme, thanks for the clarification | 16:48 |
| *** ddieterly is now known as ddieterly[away] | 16:48 | |
| daemontool_ | slashme, I'm doing it | 16:48 |
| slashme | daemontool_: perfect :) :) | 16:48 |
| *** ddieterly[away] is now known as ddieterly | 16:51 | |
| *** daemontool_ has quit IRC | 17:16 | |
| *** daemontool has joined #openstack-freezer | 17:21 | |
| szaher | slashme: https://review.openstack.org/#/c/288422/ plz check this | 17:33 |
| slashme | i'm testing this atm | 17:33 |
| slashme | not working | 17:39 |
| *** EinstCrazy has joined #openstack-freezer | 17:44 | |
| *** EinstCrazy has quit IRC | 17:49 | |
| szaher | slashme: I added some logging stuff to check if it's working or not so can we take a look at the log ? | 17:58 |
| slashme | yep. lets do that in 5 | 17:58 |
| daemontool | slashme, https://review.openstack.org/#/c/290047/ but Eldar needs to review it also | 18:02 |
| *** ddieterly is now known as ddieterly[away] | 18:03 | |
| *** ferhat has quit IRC | 18:19 | |
| slashme | Speaking of bugs. Seems like we have some very weird behaviour with incremental when using the same backup_name and container_name | 18:21 |
| *** ddieterly[away] is now known as ddieterly | 18:24 | |
| *** ddieterly has quit IRC | 18:24 | |
| *** ddieterly has joined #openstack-freezer | 18:26 | |
| *** ddieterly has quit IRC | 18:39 | |
| *** fabv has quit IRC | 18:48 | |
| *** daemontool has quit IRC | 19:51 | |
| *** ddieterly has joined #openstack-freezer | 20:27 | |
| ddieterly | can someone show me how to get an auth token for freezer from keystone in devstack? | 20:27 |
| *** ddieterly is now known as ddieterly[away] | 20:58 | |
| *** ddieterly[away] is now known as ddieterly | 21:21 | |
| *** ddieterly has quit IRC | 22:47 | |
| *** ddieterly has joined #openstack-freezer | 23:19 | |
| *** ddieterly is now known as ddieterly[away] | 23:54 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!