| *** ddieterly has joined #openstack-freezer | 00:01 | |
| *** yangyapeng has quit IRC | 00:06 | |
| *** yangyapeng has joined #openstack-freezer | 00:06 | |
| *** yangyapeng has quit IRC | 00:11 | |
| *** daemontool has quit IRC | 00:15 | |
| *** dschroeder has quit IRC | 00:24 | |
| *** yangyapeng has joined #openstack-freezer | 01:09 | |
| *** yangyapeng has quit IRC | 01:14 | |
| *** reldan has quit IRC | 01:17 | |
| *** reldan has joined #openstack-freezer | 01:18 | |
| *** EinstCrazy has joined #openstack-freezer | 01:21 | |
| *** yangyapeng has joined #openstack-freezer | 01:28 | |
| *** ddieterly is now known as ddieterly[away] | 01:36 | |
| *** ddieterly[away] is now known as ddieterly | 02:02 | |
| *** reldan has quit IRC | 02:06 | |
| *** ddieterly is now known as ddieterly[away] | 02:13 | |
| *** ddieterly[away] has quit IRC | 03:14 | |
| yangyapeng | ping vannif | 07:49 |
|---|---|---|
| *** chenzeng has quit IRC | 07:52 | |
| *** c00281451 has joined #openstack-freezer | 08:11 | |
| *** EinstCra_ has joined #openstack-freezer | 08:13 | |
| *** EinstCrazy has quit IRC | 08:16 | |
| kelepirci_ | ping to all | 08:22 |
| kelepirci_ | I am working on new sphinx documentation | 08:23 |
| kelepirci_ | I have some questions | 08:23 |
| *** c00281451 is now known as chenzeng | 08:23 | |
| m3m0 | kelepirci_: tell me, what questions? :) | 08:30 |
| kelepirci_ | I am trying to decide which tempalte should I use? | 08:31 |
| kelepirci_ | current default is openstack themed template. | 08:31 |
| kelepirci_ | but docs.openstack.org has different template | 08:31 |
| kelepirci_ | and I want to use Read The Doc template for documentation | 08:32 |
| kelepirci_ | at the end. what template shall I use? | 08:33 |
| m3m0 | the sphinx default should be fine | 08:41 |
| openstackgerrit | Merged openstack/freezer-api: Add Freezer API Version Test https://review.openstack.org/290842 | 08:52 |
| kelepirci_ | ok. I will go with the default | 08:52 |
| kelepirci_ | than I should only include .rst files to source directory | 08:53 |
| *** reldan has joined #openstack-freezer | 08:53 | |
| openstackgerrit | Memo Garcia proposed openstack/freezer-web-ui: UX improvements https://review.openstack.org/291757 | 08:59 |
| openstackgerrit | Merged openstack/freezer: Start to introduce tempest tests. https://review.openstack.org/289443 | 09:02 |
| *** reldan has quit IRC | 09:03 | |
| *** openstackgerrit has quit IRC | 09:03 | |
| *** openstackgerrit has joined #openstack-freezer | 09:04 | |
| yangyapeng | ping m3m0 | 09:13 |
| yangyapeng | m3m0: https://review.openstack.org/#/c/293244/ please review it , devstack is fail | 09:13 |
| m3m0 | yangyapeng: there is a problem with the gates, there is a patch to fix this but is not merged yet | 09:21 |
| m3m0 | I think we need to wait a little bit | 09:21 |
| yangyapeng | OK thx m3m0 | 09:32 |
| *** daemontool has joined #openstack-freezer | 09:35 | |
| *** daemontool_ has joined #openstack-freezer | 09:36 | |
| *** daemontool_ has quit IRC | 09:36 | |
| openstackgerrit | Fausto Marzi proposed openstack/freezer: Cynthia's first commit https://review.openstack.org/295289 | 09:41 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer: Modify the vars display_name to 'name' https://review.openstack.org/293244 | 09:42 |
| *** reldan has joined #openstack-freezer | 09:50 | |
| m3m0 | we should add in the logs the id or name of the job that wrote the log | 09:52 |
| daemontool | good idea | 09:53 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer: Rename mode default to fs https://review.openstack.org/295230 | 09:54 |
| m3m0 | is it me or the scheduler stops after each run? | 10:00 |
| yangyapeng | freezer-scheduer job-stop is ok ? | 10:01 |
| yangyapeng | I exec job-stop, but the job runing still，unless job-delete | 10:02 |
| m3m0 | daemontool all the backups are incremental by default right? | 10:07 |
| *** EinstCra_ has quit IRC | 10:10 | |
| *** yangyapeng has quit IRC | 10:13 | |
| daemontool | m3m0, nope | 10:15 |
| daemontool | if you do not use max_level or always_level | 10:16 |
| daemontool | the backup shouldn't be incremental | 10:16 |
| m3m0 | ok ok I have --no-incremental by default in the ui | 10:16 |
| *** sharad has joined #openstack-freezer | 10:17 | |
| daemontool | --no-incremental does not generate any metadata for the incremental | 10:17 |
| daemontool | while without it it just generate always a level 0 | 10:17 |
| m3m0 | then is it better to have max-level = 0? | 10:18 |
| daemontool | that was in case a user wanted to do incremental backups, after | 10:18 |
| daemontool | like you generated a backup without incrementals | 10:18 |
| daemontool | then after the first run the user wants to generate an incremental from the previous | 10:18 |
| daemontool | that was the idea originally | 10:19 |
| daemontool | I think it make sense to not do incremental it the user simly does not set (max|always)_level | 10:20 |
| daemontool | probably by default the use --no-incremental can be right | 10:20 |
| *** frescof__ has quit IRC | 10:21 | |
| m3m0 | ok I'll do more tests first | 10:22 |
| m3m0 | by the way | 10:22 |
| m3m0 | the repo is created https://review.openstack.org/#/admin/projects/openstack/python-freezerclient | 10:22 |
| m3m0 | what's the next step? | 10:22 |
| *** sharad has quit IRC | 10:24 | |
| daemontool | m3m0, we need to have all our components use that module | 10:25 |
| daemontool | so we need to modify the existing namespace from apiclient to freezerclient | 10:25 |
| m3m0 | shouldn't be the other way around | 10:25 |
| daemontool | like what? | 10:25 |
| slashme | reldan: https://review.openstack.org/#/c/294536/ Please | 10:25 |
| m3m0 | first import the code to that repo | 10:25 |
| m3m0 | review it, create the github one | 10:26 |
| m3m0 | and then move the other compoenents | 10:26 |
| daemontool | the github will be created automatically soon | 10:26 |
| reldan | slashme: sure, please https://review.openstack.org/#/c/295230/ | 10:26 |
| daemontool | we do not have to do anything | 10:26 |
| daemontool | every repository under the openstack/ namespace | 10:26 |
| daemontool | is a mirror from the openstack git | 10:26 |
| m3m0 | ok, so how can we import the existing repo to review.openstack? | 10:27 |
| m3m0 | is it automatically? | 10:28 |
| daemontool | I'm not sure I'm following | 10:28 |
| daemontool | sorry | 10:28 |
| daemontool | one sec | 10:29 |
| m3m0 | just asking, now we have the repo in review.openstack, do we need to import the code that is in my repo? or is it done automatically? | 10:30 |
| daemontool | automatically | 10:31 |
| daemontool | https://review.openstack.org/#/c/255349/9/gerrit/projects.yaml line 3140 | 10:31 |
| m3m0 | :) nice | 10:31 |
| daemontool | It should have happened already | 10:32 |
| m3m0 | yep I just check it did | 10:32 |
| daemontool | ah it was approved | 10:32 |
| daemontool | this morning | 10:32 |
| daemontool | probably infra have a cron process | 10:32 |
| daemontool | to do that periodically | 10:33 |
| daemontool | we just need to wait a bit and the repos will be mirrored | 10:33 |
| daemontool | we need to fix our launchpad | 10:45 |
| daemontool | so if anyone wants to opena bug on kilo or liberty or mitaka it can eb done | 10:46 |
| daemontool | now all the bugs are opened to master | 10:46 |
| daemontool | jokke_, ping | 10:49 |
| daemontool | also now we are in mitaka rc1 | 10:49 |
| daemontool | but if we need to backport a feature in mitaka rc1 from master (Newton) what would be the version change... | 10:50 |
| jokke_ | daemontool: pong | 10:50 |
| daemontool | jokke_, so we branched stable/mitaka | 10:51 |
| daemontool | for rc1 | 10:51 |
| daemontool | now I need to backport a bug | 10:51 |
| jokke_ | daemontool: nice | 10:51 |
| daemontool | what would be the version change in setup.cfg? | 10:51 |
| daemontool | until mitaka release the version is still 2.0.0.0rc1 or rc2 rc3 | 10:52 |
| jokke_ | on the stable mitaka branch, correct | 10:52 |
| daemontool | no version bump? | 10:52 |
| daemontool | or the new backports will be part or rc2? | 10:53 |
| jokke_ | so if you have 2.0.0.0rc1 tagged and you think the bugfix warrants rc2, you can just change the setup.conf reflect to that already | 10:53 |
| jokke_ | but please do them in separate changes ;) | 10:53 |
| jokke_ | so don't change the version in the bugfix backport | 10:54 |
| jokke_ | that gets messy | 10:54 |
| daemontool | ah ok | 10:54 |
| daemontool | so we can backport all the changes we need to get in mitaka, and then submit a new patch with version bump | 10:55 |
| jokke_ | I'm not 100% sure if your gate will fail or not trying to submit patches to version that is already tagged, so you might need to make the version bump first and then depend all the backports to that | 10:55 |
| *** reldan has quit IRC | 10:58 | |
| daemontool | ah ok, brilliant | 10:59 |
| daemontool | thanks a lot Erno :) | 10:59 |
| *** reldan has joined #openstack-freezer | 11:00 | |
| jokke_ | NP | 11:02 |
| openstackgerrit | Merged openstack/freezer: Rename mode default to fs https://review.openstack.org/295230 | 11:02 |
| jokke_ | BTW I did not see candidacy e-mail, who is gonna be Freezer PTL next cycle? | 11:03 |
| daemontool | slashme, | 11:06 |
| daemontool | it's in the candidacy repo | 11:06 |
| daemontool | yes agree, we should have sent the email | 11:07 |
| daemontool | but I'm not sure I totally like the current ptl email step down :) | 11:08 |
| daemontool | the freezerclinent should be able to display information not only from the freezer-api | 11:10 |
| daemontool | but also from the storages | 11:10 |
| daemontool | any thought? | 11:10 |
| daemontool | or from the cinder/nova api when using related native backups api endpoints | 11:11 |
| slashme | daemontool: I agree, but how do you manage permission then ? In swift it is easy, your user can or cannot access objets, But with ssh for example, as long as you have the key, you are able to list all backups | 11:37 |
| *** yangyapeng has joined #openstack-freezer | 11:42 | |
| daemontool | yes | 11:44 |
| daemontool | if you have the key you can list it | 11:44 |
| daemontool | the user needs to use multiple users if all the backups | 11:45 |
| daemontool | does not have to be listed | 11:45 |
| openstackgerrit | Memo Garcia proposed openstack/freezer-web-ui: UX improvements https://review.openstack.org/291757 | 11:49 |
| m3m0 | please review :) https://review.openstack.org/291757 | 11:49 |
| m3m0 | and this: https://review.openstack.org/#/c/280811/ | 11:52 |
| m3m0 | and this as well: https://review.openstack.org/#/c/278407/ | 11:52 |
| *** reldan has quit IRC | 11:53 | |
| *** yangyapeng has quit IRC | 12:01 | |
| *** yangyapeng has joined #openstack-freezer | 12:02 | |
| *** yangyape_ has joined #openstack-freezer | 12:04 | |
| *** reldan has joined #openstack-freezer | 12:04 | |
| yangyape_ | job.event has two status, none or stop? | 12:06 |
| *** yangyapeng has quit IRC | 12:07 | |
| daemontool | yangyape_, I think {start,stop,abort,None} | 12:14 |
| daemontool | vannif, ping | 12:14 |
| daemontool | I think we need to create a CONSTANT list somewhere to list all the event, rather than hardcoding them | 12:15 |
| daemontool | yangyape_, https://github.com/openstack/freezer-api/blob/master/freezer_api/api/v1/jobs.py#L226 | 12:15 |
| yangyape_ | job.event = Job.NO_EVENT Job.STOP_EVENT Job.ABORT_EVENT | 12:16 |
| yangyape_ | I see it | 12:16 |
| yangyape_ | now it has a error cinder-vol-id when create_glance | 12:17 |
| yangyape_ | the function _get_endpoint_and_token is changed. | 12:17 |
| yangyape_ | freezer-scheduler is a must, reload of the action | 12:20 |
| openstackgerrit | Eldar Nugaev proposed openstack/freezer: Added --overwrite parameter for removing all files from restore directory. Default value --overwrite=False https://review.openstack.org/296404 | 12:26 |
| daemontool | m3m0, do you want to do tomorrow then web ui and source code walkthruough? | 12:27 |
| daemontool | also if vannif in holidays?] | 12:27 |
| daemontool | slashme, rolling-upgrades specs proposal from Cross-Project Laison https://review.openstack.org/#/c/290977/ | 12:30 |
| slashme | vannif seems to be in hollidays this week | 12:35 |
| daemontool | ok | 12:37 |
| daemontool | reldan, have you been thinking about implementing the listed-incremental in tarfile? :) | 12:40 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer: WIP block based incremntal support - rsync https://review.openstack.org/290461 | 12:41 |
| *** EinstCrazy has joined #openstack-freezer | 12:42 | |
| reldan | daemontool: what’s about listed-incremental? I just not sure I understand | 12:42 |
| daemontool | reldan, do you remember the conversatino we had | 12:46 |
| daemontool | few days ago? | 12:46 |
| daemontool | about removing completely the tar and related binaries | 12:47 |
| daemontool | and do that in pure python? | 12:47 |
| daemontool | it's not somethign super critical | 12:47 |
| daemontool | but it really is an interesting challenge | 12:47 |
| reldan | I remember :) | 12:47 |
| daemontool | like this https://docs.python.org/3/library/tarfile.html | 12:47 |
| daemontool | the only lacking thing would be the | 12:48 |
| daemontool | listed-incremental | 12:48 |
| daemontool | but it's not easy really | 12:48 |
| daemontool | because the data structure changes | 12:48 |
| daemontool | in the tar binary file and in the metadata file | 12:48 |
| daemontool | as that is a gnu extention | 12:48 |
| daemontool | while tarfile mostly implement posix format | 12:48 |
| daemontool | s/extention/format/ | 12:49 |
| reldan | daemontool: I suppose we can add python-tar engine. | 12:49 |
| reldan | But probably not now | 12:49 |
| reldan | Or I can fully focus on this task and implement it | 12:49 |
| reldan | I just should reimplement tar-metadata | 12:50 |
| reldan | But it should take some time | 12:50 |
| daemontool | it will take big time | 12:50 |
| daemontool | for sure | 12:50 |
| daemontool | and yes it is not critical at all | 12:51 |
| daemontool | or a priority | 12:51 |
| daemontool | but the challenge is amazing | 12:51 |
| reldan | Yes, agree with you. I just have added —overwrite now | 12:51 |
| reldan | It should help | 12:51 |
| reldan | But tar-incremental should be easy than rsync | 12:51 |
| *** ddieterly has joined #openstack-freezer | 12:52 | |
| daemontool | reldan, yes, it's easier also because there's the tarfile module to rely on | 12:53 |
| daemontool | ddieterly, well done on the tempest stuff | 12:53 |
| *** ddieterly is now known as ddieterly[away] | 12:53 | |
| *** reldan has quit IRC | 13:01 | |
| *** ddieterly[away] has quit IRC | 13:03 | |
| *** reldan has joined #openstack-freezer | 13:23 | |
| openstackgerrit | Memo Garcia proposed openstack/python-freezerclient: .gitreview updated to point new repo https://review.openstack.org/296436 | 13:31 |
| m3m0 | please review :) https://review.openstack.org/296436 | 13:32 |
| *** daemontool_ has joined #openstack-freezer | 13:33 | |
| *** daemontool has quit IRC | 13:33 | |
| *** reldan has quit IRC | 13:44 | |
| *** reldan has joined #openstack-freezer | 13:47 | |
| openstackgerrit | Ferhat Ozkasgarli proposed openstack/freezer: New Better & Well Formatted Docs with Sphinx https://review.openstack.org/296448 | 13:49 |
| kelepirci_ | hello guys. I have stared with documentation. I would appreciate if you comment on documentation. | 13:50 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer: Adds information for installation https://review.openstack.org/294903 | 13:50 |
| *** reldan has quit IRC | 13:50 | |
| daemontool_ | kelepirci_, thanks, is this commit still valid? | 13:50 |
| daemontool_ | https://review.openstack.org/#/c/294903/ | 13:50 |
| daemontool_ | or it is superseed by the other | 13:50 |
| kelepirci_ | it still valid. after I have finished documentation. it will be suppressed. | 13:51 |
| daemontool_ | ok brilliant | 13:51 |
| kelepirci_ | so it would be good to merge with master now | 13:51 |
| daemontool_ | kelepirci_, is there a comment here https://review.openstack.org/#/c/294903/ ? | 13:52 |
| kelepirci_ | actually there is not any comment from my side. | 13:53 |
| kelepirci_ | the commit was only contains some important warning for new installation | 13:54 |
| kelepirci_ | is* | 13:54 |
| *** reldan has joined #openstack-freezer | 13:59 | |
| openstackgerrit | Ferhat Ozkasgarli proposed openstack/freezer: New Better & Well Formatted Docs with Sphinx https://review.openstack.org/296448 | 14:01 |
| kelepirci_ | have just updated missing files | 14:01 |
| daemontool_ | kelepirci_, Jin Nan Zhang gave -1 | 14:01 |
| daemontool_ | for a too long line | 14:01 |
| daemontool_ | in https://review.openstack.org/#/c/294903/ | 14:01 |
| daemontool_ | ok | 14:02 |
| kelepirci_ | let me check | 14:03 |
| kelepirci_ | by the way. I am quite noob to this development process. so please correct me if I am doing something wrong | 14:03 |
| *** openstack has joined #openstack-freezer | 14:24 | |
| *** ddieterly is now known as ddieterly[away] | 14:25 | |
| daemontool_ | ddieterly[away], ah... | 14:29 |
| daemontool_ | all, unless this change is backported, not patches can be sent to stable/mitaka https://review.openstack.org/#/c/296361/ | 14:35 |
| slashme | reviewed. | 14:37 |
| slashme | Just require +A | 14:37 |
| daemontool_ | slashme, I'm not sure about the versioning there | 14:37 |
| daemontool_ | cause the version is not bumped | 14:37 |
| daemontool_ | it shouldn't be bumped probably until mitaka is fully released | 14:38 |
| slashme | I'd think the same | 14:39 |
| daemontool_ | let's hope we are not going to have conflicts | 14:39 |
| daemontool_ | but I'm not sure either | 14:39 |
| daemontool_ | what I'm saying is right | 14:39 |
| daemontool_ | cause I've seen other projects | 14:39 |
| daemontool_ | releasing other versions | 14:39 |
| slashme | Unsualy gerrit -1 when there is a version issue. But I'm not sure at all either | 14:39 |
| daemontool_ | ok | 14:39 |
| *** dschroeder has joined #openstack-freezer | 14:43 | |
| slashme | I guess we also need to backport it to liberty ? No ? | 14:44 |
| *** ddieterly[away] is now known as ddieterly | 14:49 | |
| daemontool_ | mmhhhh I'm not sure | 15:01 |
| *** EinstCrazy has quit IRC | 15:03 | |
| daemontool_ | reldan, ping | 15:29 |
| reldan | daemontool: yes | 15:30 |
| daemontool_ | in Kilo... do you remember the supported backups for vms and volumes? | 15:30 |
| daemontool_ | like do we support both | 15:30 |
| daemontool_ | cindernative | 15:30 |
| daemontool_ | and the other approach of downloading the volumes and process it by the agent? | 15:31 |
| reldan | daemontool_: I suppose yes | 15:31 |
| daemontool_ | or for volumes backup only cindernatives are supported | 15:31 |
| reldan | daemontool_: I suppose it contains the same code as master have | 15:31 |
| daemontool_ | ok | 15:31 |
| daemontool_ | yes but in kilo, it's not possible to execute snapshots while the volume is mounted, right? | 15:32 |
| reldan | daemontool_: yes in kilo we don’t have —force for cindernative | 15:33 |
| daemontool_ | I can't remember | 15:33 |
| daemontool_ | if we provide any way | 15:33 |
| daemontool_ | to do backups of volumes without umounting the volume in kilo | 15:34 |
| reldan | daemontool_: Cinder through glance | 15:34 |
| reldan | but non-incremental | 15:34 |
| daemontool_ | ok no prob for incremental | 15:34 |
| reldan | Cinder throught glance | 15:34 |
| daemontool_ | so we can snapshot a volume without having the volume unmounted? | 15:34 |
| reldan | Yes, for snapshotting we have —force in kilo | 15:35 |
| daemontool_ | ah ok | 15:35 |
| daemontool_ | brilliant | 15:35 |
| daemontool_ | ok so | 15:36 |
| daemontool_ | we can snapshot the volume, upload it to glance | 15:36 |
| daemontool_ | download it with the agent and upload it to swift? | 15:36 |
| daemontool_ | in stream | 15:36 |
| daemontool_ | ? | 15:36 |
| daemontool_ | can't rember sorry... | 15:37 |
| daemontool_ | I'm going to try it anyway | 15:37 |
| reldan | daemontool_: Yes, we should be able to do this | 15:38 |
| daemontool_ | what's the difference between Kilo and Liberty | 15:42 |
| daemontool_ | in the features we use | 15:42 |
| daemontool_ | for volumes backup | 15:42 |
| daemontool_ | it's just the use of the backup endpoint | 15:42 |
| daemontool_ | in cinder | 15:42 |
| daemontool_ | without downtime as in backup there's no --force | 15:42 |
| daemontool_ | right? | 15:42 |
| reldan | daemontool_: In liberty they have added —force for backupk | 15:44 |
| reldan | it is all | 15:44 |
| daemontool_ | ok | 15:44 |
| daemontool_ | so I've been asked to do volumes and vms backup in kilo with freezer, without downtime | 15:45 |
| daemontool_ | it does not matter if the incrementals are not available | 15:45 |
| daemontool_ | if yes, at least 1 person more will be allocated full time to freezer | 15:45 |
| daemontool_ | I think | 15:46 |
| daemontool_ | we could even use | 15:46 |
| daemontool_ | newer version of freezer | 15:46 |
| daemontool_ | like mitaka or liberty, while the rest of the infrastructure is kilo | 15:46 |
| daemontool_ | as we really do not use other fancy features | 15:46 |
| daemontool_ | from other services, other than that --force thing on cinder backups api endpoints | 15:47 |
| daemontool_ | reldan, we could use the new code, with rsync to compute the incremental | 15:50 |
| daemontool_ | while downloading the image from glance | 15:50 |
| reldan | daemontool_: Probably, but it should be a lot of work. Because in this case we should support incremental restore | 15:51 |
| daemontool_ | incremental restore is not that difficult | 15:51 |
| daemontool_ | because | 15:51 |
| reldan | daemontool_: We should download zero level image, then patch it with increments | 15:51 |
| daemontool_ | the vms and volumes | 15:51 |
| daemontool_ | are single files | 15:51 |
| daemontool_ | yes | 15:52 |
| reldan | then upload this image on glance | 15:52 |
| daemontool_ | yes | 15:52 |
| daemontool_ | that was the original idea | 15:52 |
| daemontool_ | :D | 15:52 |
| daemontool_ | do you rember? :) | 15:52 |
| reldan | Nope :) But it will be increment only for storage | 15:52 |
| reldan | and no increment for backup | 15:52 |
| reldan | so if you have 1TB data | 15:52 |
| daemontool_ | why? | 15:53 |
| reldan | each increment should - be full backup, full download | 15:53 |
| daemontool_ | well yes | 15:53 |
| daemontool_ | to glance yes | 15:53 |
| reldan | then calculate diff and upload | 15:53 |
| daemontool_ | yes | 15:53 |
| daemontool_ | but in the use case I've been asked | 15:53 |
| daemontool_ | it does not matter | 15:53 |
| daemontool_ | as long they can do it in Kilo | 15:53 |
| reldan | So we can have economy only for terms of storage, but big requirements for cpu and the same requirements for network | 15:54 |
| reldan | From my point of view cpu is more expensive, but probably I’m wrong :) | 15:54 |
| daemontool_ | the problem is where you do the restore? | 15:55 |
| daemontool_ | because the image needs to be prepared | 15:55 |
| daemontool_ | so it cannot be done in the same VM | 15:56 |
| reldan | I can do restore on any machine that have credentials to OpenStack | 15:57 |
| daemontool_ | I think we can make it happen.. | 16:32 |
| daemontool_ | :) | 16:32 |
| *** ddieterly is now known as ddieterly[away] | 16:38 | |
| *** ddieterly[away] is now known as ddieterly | 16:41 | |
| *** reldan has quit IRC | 17:33 | |
| *** ddieterly is now known as ddieterly[away] | 17:42 | |
| *** ddieterly[away] has quit IRC | 18:43 | |
| *** openstack has joined #openstack-freezer | 19:24 | |
| *** DuncanT_ is now known as DuncanT | 19:24 | |
| *** arobase has joined #openstack-freezer | 19:29 | |
| *** reldan has joined #openstack-freezer | 19:31 | |
| *** dims_ has joined #openstack-freezer | 19:43 | |
| *** reldan has quit IRC | 19:49 | |
| *** dims_ has quit IRC | 19:53 | |
| *** dims has joined #openstack-freezer | 19:56 | |
| *** openstack has joined #openstack-freezer | 20:34 | |
| *** reldan has joined #openstack-freezer | 20:35 | |
| *** arobase has quit IRC | 20:53 | |
| *** ddieterly has joined #openstack-freezer | 21:22 | |
| *** daemontool_ has quit IRC | 21:34 | |
| *** ddieterly is now known as ddieterly[away] | 21:36 | |
| *** daemontool_ has joined #openstack-freezer | 21:38 | |
| *** ddieterly[away] is now known as ddieterly | 21:40 | |
| *** reldan has quit IRC | 21:59 | |
| *** reldan has joined #openstack-freezer | 22:17 | |
| *** daemontool_ has quit IRC | 22:31 | |
| *** ddieterly has quit IRC | 23:02 | |
| *** reldan has quit IRC | 23:09 | |
| *** openstack has joined #openstack-freezer | 23:25 | |
| *** yangyapeng has quit IRC | 23:34 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!