| *** yangyape_ has quit IRC | 00:02 | |
| *** dschroeder has quit IRC | 00:31 | |
| *** daemontool has quit IRC | 00:47 | |
| *** ddieterly has joined #openstack-freezer | 00:54 | |
| *** ddieterl_ has joined #openstack-freezer | 00:58 | |
| *** ddieterly has quit IRC | 00:58 | |
| *** yangyapeng has joined #openstack-freezer | 01:13 | |
| *** ddieterly has joined #openstack-freezer | 01:16 | |
| *** EinstCrazy has joined #openstack-freezer | 01:16 | |
| *** ddieterl_ has quit IRC | 01:19 | |
| *** yangyapeng has quit IRC | 01:39 | |
| *** EinstCrazy has quit IRC | 01:40 | |
| *** EinstCrazy has joined #openstack-freezer | 01:42 | |
| *** reldan has quit IRC | 01:45 | |
| *** ddieterly has quit IRC | 03:30 | |
| jith_ | hi all, when i try freezer-scheduler --help command to know its usage, i received the following error "ImportError: No module named apscheduler.schedulers.blocking" | 04:51 |
|---|---|---|
| *** ddieterly has joined #openstack-freezer | 05:01 | |
| *** ddieterly has quit IRC | 05:05 | |
| *** ddieterly has joined #openstack-freezer | 06:02 | |
| *** ddieterly has quit IRC | 06:07 | |
| *** ddieterly has joined #openstack-freezer | 07:03 | |
| *** yangyapeng has joined #openstack-freezer | 07:04 | |
| *** ddieterly has quit IRC | 07:08 | |
| EinstCrazy | how did you install the freezer? | 07:10 |
| jith_ | EinstCrazy: python setup.py install | 07:11 |
| EinstCrazy | It seems the apscheduler in the requirement not install or not install correctly | 07:11 |
| *** daemontool has joined #openstack-freezer | 07:31 | |
| *** hparekh has quit IRC | 07:55 | |
| *** zhangjn has quit IRC | 08:02 | |
| *** ddieterly has joined #openstack-freezer | 08:04 | |
| *** zhangjn has joined #openstack-freezer | 08:07 | |
| *** ddieterly has quit IRC | 08:09 | |
| *** daemontool has quit IRC | 08:35 | |
| *** daemontool has joined #openstack-freezer | 08:37 | |
| *** reldan has joined #openstack-freezer | 08:47 | |
| *** ddieterly has joined #openstack-freezer | 09:05 | |
| *** ddieterly has quit IRC | 09:11 | |
| jith_ | EinstCrazy: thanks.. sorry i was away | 09:23 |
| jith_ | in command line, we will use only freezerc??? then whats the use of agent and scheduler?? .. couldnt find any documentation regarding that.. sorry if i m wrong | 09:33 |
| daemontool | jith_, freezerc == freezer-agent | 09:39 |
| daemontool | it's the same | 09:39 |
| daemontool | freezerc is the old name, freezer-agent is the new name | 09:39 |
| daemontool | we keep both for compatibility | 09:39 |
| jith_ | daemontool: thanks.. i got | 09:40 |
| jith_ | daemontool: incremental backup is available for volumes and instances??? | 09:42 |
| *** yangyape_ has joined #openstack-freezer | 09:42 | |
| daemontool | jith_, this review deliver incremental backup for volumes https://review.openstack.org/#/c/276685/ | 09:44 |
| daemontool | instances we still do not support that | 09:44 |
| daemontool | the incrementals I mean | 09:45 |
| *** yangyapeng has quit IRC | 09:45 | |
| *** yangyape_ has quit IRC | 09:47 | |
| jith_ | thanks :) | 09:47 |
| *** reldan has quit IRC | 09:48 | |
| jith_ | daemontool: so as of now, it wil take the whole instance backup??? in scheduler, during the second backup, it will delete the previous one and take a new backup?? | 09:51 |
| *** EinstCrazy has quit IRC | 09:55 | |
| daemontool | it won't delete the old backup | 10:06 |
| daemontool | can't remember the details | 10:06 |
| daemontool | reldan implemented it | 10:07 |
| daemontool | sorry | 10:07 |
| daemontool | I can take a look at let you know asap tho | 10:07 |
| *** ddieterly has joined #openstack-freezer | 10:07 | |
| jith_ | daemontool: thanks, its ok | 10:12 |
| jith_ | if I use freezer for DR, I should be able to keep backup of nova instance and cinder volumes... is it? If so I should be able to take backup from outside of VM.. so scheduler is used for that purpose??? | 10:12 |
| jith_ | sorry for the trouble... :( | 10:12 |
| *** ddieterly has quit IRC | 10:12 | |
| frescof | jith_, the scheduler is needed if you want to use the api | 10:15 |
| frescof | but it will run on the compute nodes in that case | 10:15 |
| *** daemontool has quit IRC | 10:16 | |
| jith_ | frescof: thanks.. | 10:19 |
| jith_ | yes | 10:19 |
| jith_ | frescof: u meant freezer api right?? | 10:19 |
| *** reldan has joined #openstack-freezer | 10:24 | |
| frescof | ye | 10:38 |
| frescof | s/ye/yes/ | 10:38 |
| jith_ | frescof: thanks | 10:53 |
| *** jith_ has quit IRC | 10:54 | |
| *** ddieterly has joined #openstack-freezer | 11:08 | |
| *** ddieterly has quit IRC | 11:12 | |
| openstackgerrit | Eldar Nugaev proposed openstack/freezer: Removing defaults values from cli. https://review.openstack.org/284637 | 11:13 |
| *** EinstCrazy has joined #openstack-freezer | 11:32 | |
| *** reldan has quit IRC | 11:46 | |
| *** reldan has joined #openstack-freezer | 12:04 | |
| *** ddieterly has joined #openstack-freezer | 12:09 | |
| *** ddieterly has quit IRC | 12:13 | |
| *** daemontool has joined #openstack-freezer | 12:14 | |
| *** ddieterly has joined #openstack-freezer | 13:09 | |
| *** ddieterly has quit IRC | 13:14 | |
| *** daemontool has quit IRC | 13:15 | |
| *** daemontool has joined #openstack-freezer | 13:16 | |
| *** daemontool has quit IRC | 13:17 | |
| *** daemontool has joined #openstack-freezer | 13:18 | |
| *** daemontool has quit IRC | 13:24 | |
| *** reldan has quit IRC | 13:49 | |
| openstackgerrit | Fausto Marzi proposed openstack/freezer-api: Switch to testr from pytest https://review.openstack.org/260950 | 13:54 |
| *** reldan has joined #openstack-freezer | 13:54 | |
| *** daemontool has joined #openstack-freezer | 13:54 | |
| daemontool | reldan, ping | 13:56 |
| reldan | daemontool: yes | 13:56 |
| daemontool | I've added few more requirements here https://etherpad.openstack.org/p/freezer_meetings | 13:57 |
| daemontool | under other requirements | 13:57 |
| reldan | daemontool: Great, looks good. | 13:59 |
| reldan | daemontool: I only don’t see requirements for tenant | 13:59 |
| daemontool | I think any mention to vm instances and volumes | 14:00 |
| daemontool | can be considered probably related to tenant | 14:00 |
| reldan | daemontool: I can see only Backup on the instance level, volumelevel, Relational/Non-Relational database and BigData Cluster. | 14:01 |
| m3m0 | daemontool agentless backups? | 14:01 |
| reldan | but it is about instance level, volume level, not tenant level | 14:01 |
| daemontool | m3m0, well that's what they gave me | 14:01 |
| reldan | I see requirements from you and from ddieterly and don’t see any item related to tenant | 14:01 |
| daemontool | :) | 14:01 |
| daemontool | reldan, I think any tenant specific resources | 14:02 |
| m3m0 | I update the doc to have data consistency checks | 14:02 |
| daemontool | like volumes and instances | 14:02 |
| daemontool | is tenant | 14:02 |
| m3m0 | who gave it to you? | 14:02 |
| reldan | everything is good, but seems nobody ask about tenant | 14:02 |
| reldan | ES backup (logs and Freezer jobs) | 14:02 |
| reldan | Metering (esp Billing related ones) | 14:02 |
| reldan | Storage Quota management ( I am not sure how much we have here) | 14:02 |
| reldan | Vertica DB | 14:02 |
| reldan | Swift data backup | 14:02 |
| reldan | Container backup | 14:02 |
| daemontool | a friend architect in Ercisson | 14:02 |
| reldan | es backup - not tenant, additional mode like mysql or mongo | 14:03 |
| reldan | metering - don’t related to tenant | 14:03 |
| daemontool | agree | 14:03 |
| reldan | storage quota - great, but don’t related to tenant | 14:03 |
| reldan | vertica db - like mysql, mongo, es - don’t related to tenant | 14:03 |
| reldan | swift data backup - cool, but don’t related to tenant | 14:03 |
| daemontool | I think tenant is: any metadata (i.e. from keystone), volumes, instances and objects | 14:03 |
| reldan | container backup - suppose the same as swift bacup | 14:03 |
| reldan | daemontool: Yes! | 14:04 |
| reldan | daemontool: But I don’t see any item related to metadata - networks, volumes, vm-s, floating ip-s | 14:04 |
| daemontool | reldan, in the ones I've added there's | 14:04 |
| daemontool | Backup one instance daily and save for N days. | 14:04 |
| daemontool | · Backup another instance every M minutesand save backups for D days. | 14:04 |
| daemontool | Copy your snapshots to other OpenStack(Swift) | 14:05 |
| reldan | Good, but it is instance backup, not tenant | 14:05 |
| daemontool | Recover instances and volumes in otherregions with a few simple mouse clicks. | 14:05 |
| daemontool | well | 14:05 |
| daemontool | an instance is a tenant specific resource | 14:05 |
| reldan | Yes, it is | 14:05 |
| daemontool | in the strict sense you mean | 14:05 |
| daemontool | probably only the metadata is tenant only | 14:06 |
| daemontool | but I think we should backup and restore any tenant resources | 14:06 |
| daemontool | so you are right | 14:06 |
| daemontool | network, keystone, volumes, isntances, | 14:06 |
| daemontool | floating ips | 14:06 |
| daemontool | yes | 14:06 |
| daemontool | that | 14:06 |
| daemontool | I agree | 14:06 |
| reldan | Yes, but we need someone who needs this | 14:06 |
| reldan | who has real requirements for transition let’s say real applicatoin | 14:07 |
| reldan | from one OS installation to another | 14:07 |
| daemontool | yes | 14:07 |
| reldan | But I don’t see requirements for this. We have a lot of requirements and fields of improvement, but I don’t see requirements for such transition | 14:07 |
| *** zhangjn has quit IRC | 14:08 | |
| reldan | Like Backupscripts support for Linux & Windows servers – give your own hooks to backup applications consistently: MySQL, Oracle, MongoDB, XFS etc... | 14:08 |
| reldan | I understand what we should do this | 14:08 |
| reldan | And understand why it is important | 14:08 |
| reldan | We can define it and start to work on it | 14:09 |
| reldan | But I don’t understand what we want from tenant backup | 14:09 |
| *** zhangjn has joined #openstack-freezer | 14:09 | |
| daemontool | I think reldan you are right | 14:09 |
| daemontool | I intend it as you are | 14:09 |
| daemontool | so far | 14:10 |
| reldan | daemontool: Yes. I see a lot of requirements and we create many blueprints. But all hpe requirements are not tenant | 14:10 |
| *** ddieterly has joined #openstack-freezer | 14:10 | |
| reldan | It is about new modes | 14:10 |
| daemontool | what everybody wants is volumes and instances incremental backups from one OS deployment and restore to a different one | 14:10 |
| reldan | billing and metering integration | 14:10 |
| daemontool | that is the basic we can offer | 14:10 |
| daemontool | billing I think we can write the integratino with cloudkitty | 14:11 |
| daemontool | metering I have no idea | 14:11 |
| reldan | Yes, I can say. Tenant backup from our point of view - is creation of backup of one instance with attached volumes and relocation it to different OS cluster, without restore of network, sequrity rules and ip | 14:12 |
| reldan | And if we agree with this difinition - great, let’s go that way. | 14:13 |
| reldan | We will define metadata for this task | 14:13 |
| *** EinstCrazy has quit IRC | 14:14 | |
| *** ddieterly has quit IRC | 14:15 | |
| *** daemontool has quit IRC | 14:16 | |
| *** daemontool has joined #openstack-freezer | 14:16 | |
| openstackgerrit | Fausto Marzi proposed openstack/freezer-api: Switch to testr from pytest https://review.openstack.org/260950 | 14:16 |
| daemontool | reldan sorry got disconnected | 14:17 |
| reldan | daemontool: no worries. | 14:18 |
| reldan | reldan: Yes, I can say. Tenant backup from our point of view - is creation of backup of one instance with attached volumes and relocation it to different OS cluster, without restore of network, sequrity rules and ip | 14:18 |
| reldan | [2:13pm] reldan: And if we agree with this difinition - great, let’s go that way. | 14:18 |
| reldan | [2:13pm] reldan: We will define metadata for this task | 14:18 |
| reldan | [2:14pm] | 14:18 |
| *** daemontool_ has joined #openstack-freezer | 14:18 | |
| reldan | daemontool: I would prefer to check requirements list and create blueprints | 14:19 |
| reldan | then discuss it | 14:19 |
| reldan | I see that anyone wants different application hooks and modes - like vertica, elastic search, give your own hooks to backup applications consistently: MySQL, Oracle, MongoDB, XFS etc... | 14:20 |
| *** daemontool has quit IRC | 14:22 | |
| *** yangyapeng has joined #openstack-freezer | 14:26 | |
| m3m0 | reldan daemontool should the python-freezerclient be able to restore a backup? | 14:29 |
| m3m0 | daemontool any update on the python-freezerclient repo? | 14:30 |
| m3m0 | this is WIP: https://github.com/memogarcia/python-freezerclient/tree/cliff | 14:30 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer-api: Switch to testr from pytest https://review.openstack.org/260950 | 14:36 |
| daemontool_ | m3m0, let me finish the testr thing in the freezer-api and we'll work on that | 14:39 |
| m3m0 | kkk | 14:41 |
| *** ddieterly has joined #openstack-freezer | 14:49 | |
| *** ddieterly has quit IRC | 14:59 | |
| *** daemontool_ has quit IRC | 15:01 | |
| *** daemontool has joined #openstack-freezer | 15:05 | |
| *** ddieterl_ has joined #openstack-freezer | 15:08 | |
| ddieterl_ | daemontool: it looks like there currently are no integration tests for freezer-api, only unit tests | 15:09 |
| ddieterl_ | is that correct? | 15:09 |
| *** ddieterl_ is now known as ddieterly_ | 15:09 | |
| daemontool | ddieterly_, I think you are correct | 15:12 |
| daemontool | in theory the integration tests for the api, are the integration tests of the scheduler | 15:13 |
| daemontool | but integration tests like tempests | 15:13 |
| daemontool | nope, we do not have it | 15:13 |
| daemontool | at all | 15:13 |
| ddieterly_ | yea, ok, we need to get the unit tests to run in the gate for the freezer-api, correct? | 15:14 |
| ddieterly_ | right now, it looks like the unit tests are not running in the gate | 15:14 |
| daemontool | ddieterly_, exactly | 15:15 |
| daemontool | that's why I'm trying to do this https://review.openstack.org/#/c/260950/ | 15:15 |
| daemontool | before | 15:15 |
| daemontool | today should be ok to pass all the verifications | 15:15 |
| ddieterly_ | does that actaully make the tests run in the gate? | 15:16 |
| daemontool | ddieterly_, nope | 15:17 |
| ddieterly_ | i thought that there was some config in openstack-infra that needs to be done to get the tests to run | 15:17 |
| daemontool | but it solve the current issues | 15:17 |
| ddieterly_ | ok, that's what i thought | 15:17 |
| daemontool | that are blockers to do that | 15:17 |
| ddieterly_ | there aren't any blockers | 15:17 |
| daemontool | the dsvm gate job fails | 15:17 |
| ddieterly_ | just need to config openstack-infra, i believe | 15:17 |
| daemontool | testr is not being used | 15:18 |
| daemontool | the test-requirements | 15:18 |
| daemontool | are not part of the global-requirements | 15:18 |
| daemontool | so the verification fails | 15:18 |
| daemontool | there are multiple blockers :) | 15:18 |
| ddieterly_ | after you patch to use testr, then it shold work if we get it to run in the gates, yes? | 15:18 |
| daemontool | yes | 15:18 |
| daemontool | I mean the verification is ok | 15:19 |
| daemontool | but you are right | 15:19 |
| daemontool | the integration tests are not | 15:19 |
| ddieterly_ | so, is the problem that your patch is failing the gates? | 15:19 |
| daemontool | no, the problem is that master currently for the freezer-api is failing at the gates | 15:19 |
| daemontool | that change should fix it | 15:19 |
| ddieterly_ | https://review.openstack.org/#/c/260950/ should fix the gates? | 15:20 |
| daemontool | i.e. porting the freezer-api code to py34 | 15:20 |
| daemontool | yes | 15:20 |
| ddieterly_ | ok, so why is your patch not being +2? | 15:20 |
| daemontool | because it still doesn't verify | 15:20 |
| daemontool | as I'm working on it | 15:20 |
| ddieterly_ | ok, why does it not verify? | 15:21 |
| ddieterly_ | i don't see check jobs in the patch at the moment | 15:21 |
| daemontool | ddieterly_, http://status.openstack.org/zuul/ search for freezer-api | 15:21 |
| ddieterly_ | ok, so this is the failure? http://logs.openstack.org/50/260950/8/check/gate-freezer-devstack-dsvm/47df3c2/ | 15:22 |
| daemontool | that was one of the failures yes | 15:22 |
| daemontool | before there was pep8 | 15:22 |
| daemontool | before pylint | 15:22 |
| daemontool | before py34 | 15:22 |
| ddieterly_ | forgive me if i'm asking dumb questions | 15:22 |
| daemontool | not a prob at all | 15:22 |
| daemontool | cause | 15:23 |
| daemontool | after we enabled | 15:23 |
| daemontool | the python-jobs | 15:23 |
| daemontool | on openstack-infra | 15:23 |
| daemontool | and the check requirements jobs | 15:23 |
| ddieterly_ | is that gate that is failing automatically running the unit tests at this point or do we need to configure something in openstack-infra to get the unit tests to run? | 15:23 |
| daemontool | (which are necessary to be added in the project list in openstack/requirements and to add new deps in global-requirements) | 15:23 |
| daemontool | ddieterly_, I think we can fix the gate without modifying anything | 15:24 |
| daemontool | in project-config | 15:24 |
| ddieterly_ | ok, so nothing needs to change in openstack-infra (you think)? | 15:24 |
| daemontool | I think we do not have to change anything in infra | 15:24 |
| daemontool | to solve our curernt issues | 15:24 |
| daemontool | are matters of path | 15:24 |
| ddieterly_ | ok, do you need help with figuring out why that patch is failing? | 15:25 |
| daemontool | I think I did today | 15:25 |
| daemontool | what would be good | 15:25 |
| daemontool | is to automatically | 15:25 |
| daemontool | execute the integration tests | 15:25 |
| daemontool | in the freezer agent | 15:25 |
| daemontool | against the api, with the dsvm gate job | 15:25 |
| daemontool | but that would be after this | 15:26 |
| daemontool | cause if we do not enable tests to be executed automatically | 15:26 |
| daemontool | this is crap | 15:26 |
| ddieterly_ | yea, we need to get this patch working | 15:26 |
| daemontool | ok :) | 15:26 |
| ddieterly_ | agreed about the crap ;-) | 15:26 |
| daemontool | :) | 15:27 |
| ddieterly_ | if we don't have integration tests, then things will break when people modify code | 15:27 |
| daemontool | yes | 15:27 |
| ddieterly_ | ok, so you have this patch under control? | 15:27 |
| daemontool | I think so | 15:27 |
| daemontool | let's see hot it goes | 15:27 |
| daemontool | s/hot/how/ | 15:27 |
| ddieterly_ | ok | 15:27 |
| daemontool | the current verification | 15:28 |
| daemontool | I think something needs to be backported also to liberty | 15:28 |
| daemontool | on freezer-api after that | 15:28 |
| ddieterly_ | ok, then if that patch goes ok and is merged, then we can try to get some integration tests on the freezer-api | 15:28 |
| ddieterly_ | brb | 15:29 |
| daemontool | ty | 15:29 |
| ddieterly_ | to be all openstack-like, we would need tempest tests on the freezer-api, right? | 15:34 |
| ddieterly_ | daemontool: ^^ | 15:34 |
| ddieterly_ | (not that i like writing tempest tests) | 15:35 |
| daemontool | ddieterly_, yes | 15:35 |
| ddieterly_ | ok, i've been doing monasca, and we skirted a lot of openstack conventions, so i need to come up to speed on the official openstack way | 15:35 |
| ddieterly_ | so, a good place for me to start contributing would be tempest tests on freezer-api? | 15:36 |
| daemontool | yes | 15:36 |
| ddieterly_ | alright | 15:36 |
| daemontool | I think | 15:37 |
| daemontool | is we can define like 10 scenarios of real world backups | 15:37 |
| ddieterly_ | do you know what the mechanism is for the unit test to get run in the gate? where is that confgured in openstack-infra? | 15:37 |
| ddieterly_ | i looked last night, but i could not figure out how the unit tests get started in the gate | 15:37 |
| daemontool | ddieterly_, do you mean from the dsvm job_ | 15:39 |
| daemontool | ? | 15:39 |
| daemontool | or just | 15:39 |
| daemontool | the py27 tests? | 15:39 |
| daemontool | from tox.ini | 15:39 |
| ddieterly_ | in the dsvm gate job, the py27 tests get run, don't they? | 15:39 |
| daemontool | nope | 15:39 |
| daemontool | py27 has it's own job | 15:39 |
| daemontool | part of the python-jobs jobs group | 15:40 |
| daemontool | py27, py34, docs | 15:40 |
| daemontool | pep8 | 15:40 |
| ddieterly_ | ok, in this job http://logs.openstack.org/50/260950/8/check/gate-freezer-api-python27/f7f28e4/ how do the tests get started? | 15:40 |
| ddieterly_ | what in openstack-infra runs that gate and starts the tests? | 15:40 |
| daemontool | with tox | 15:40 |
| daemontool | execute tox | 15:41 |
| daemontool | with the content of tox.ini | 15:41 |
| daemontool | https://review.openstack.org/#/c/260950/11/tox.ini | 15:41 |
| ddieterly_ | where is that configured? is it explicity configured or is it just implicitly done? | 15:41 |
| daemontool | implicitly | 15:41 |
| ddieterly_ | so, if there is a tox.ini file, then openstack-infra will automatically run the unit tests? | 15:42 |
| ddieterly_ | again, sorry if this is a dumb question | 15:42 |
| daemontool | if there's setup.py | 15:43 |
| daemontool | and tox.ini file | 15:43 |
| ddieterly_ | is this all documented somewhere? | 15:43 |
| daemontool | and the jobs specified | 15:43 |
| daemontool | in the templates | 15:43 |
| daemontool | yes one sec | 15:43 |
| daemontool | in the project creators guide | 15:43 |
| daemontool | http://docs.openstack.org/infra/manual/creators.html | 15:43 |
| daemontool | under "Configure Zuul to Run Jobs" | 15:44 |
| ddieterly_ | thank you! | 15:44 |
| daemontool | yw | 15:44 |
| ddieterly_ | great, i'll read this instead of bombarding you with questions | 15:44 |
| ddieterly_ | then, i'll start looking into getting integration tests running | 15:45 |
| ddieterly_ | about mid-cycle | 15:46 |
| ddieterly_ | it would be better if we just meet at summit and i skip the mid-cycle | 15:46 |
| ddieterly_ | mid-cycle is too close to the summit | 15:47 |
| ddieterly_ | we can then plan to have another mid-cycle after the summit | 15:47 |
| daemontool | yes | 15:47 |
| daemontool | sure | 15:48 |
| daemontool | ddieterly_, let's talk with the others | 15:48 |
| daemontool | we should see who can go to the summit and who can't | 15:48 |
| ddieterly_ | ok, i did not think of that | 15:48 |
| ddieterly_ | would be good to meet everyone | 15:49 |
| ddieterly_ | but travelling to galway and then travelling to austin is a bit much for me | 15:49 |
| daemontool | ddieterly_, and for the record | 15:49 |
| daemontool | before I was mistaken | 15:49 |
| daemontool | to fix the dsvm error | 15:49 |
| *** ddieterly_ is now known as ddieterly | 15:49 | |
| daemontool | we need to modify something in the project-config repo in openstack-infra | 15:49 |
| ddieterly | yea, i thought that we needed to do something there | 15:50 |
| daemontool | precisely the jenkins/jobs/freezer.yaml | 15:50 |
| ddieterly | bash: line 1: ./post_test_hook.sh: No such file or directory | 15:53 |
| daemontool | ddieterly, https://review.openstack.org/#/c/285384/ | 15:53 |
| daemontool | yep | 15:53 |
| daemontool | that's the fix | 15:53 |
| ddieterly | ok | 15:54 |
| openstackgerrit | Fausto Marzi proposed openstack/freezer-api: Switch to testr from pytest https://review.openstack.org/260950 | 15:55 |
| ddieterly | cool, thanks, ttyl | 15:55 |
| *** yangyapeng has quit IRC | 15:56 | |
| *** yangyapeng has joined #openstack-freezer | 15:56 | |
| *** yangyapeng has quit IRC | 15:56 | |
| daemontool | ddieterly, it took many weeks to understand the jobs and infra related stuff | 15:58 |
| ddieterly | yes, i have wrestled with it before when i setup the gate for monasca-api | 15:59 |
| ddieterly | i hate it | 15:59 |
| daemontool | high maintenance | 16:00 |
| daemontool | I'll be back in 20 min | 16:03 |
| *** dschroeder has joined #openstack-freezer | 16:05 | |
| ddieterly | k | 16:05 |
| *** daemontool has quit IRC | 16:07 | |
| *** daemontool has joined #openstack-freezer | 16:40 | |
| daemontool | reldan, there's an interesting idea frescof had for incremental backups of of vms | 16:49 |
| daemontool | please have a conversation with him | 16:49 |
| daemontool | so we can write a bp | 16:49 |
| reldan | daemontool: good | 16:50 |
| daemontool | we need rsync code in tho | 16:51 |
| daemontool | doh! | 16:51 |
| daemontool | lol | 16:51 |
| daemontool | :) | 16:51 |
| daemontool | but the approach is quite smart | 16:51 |
| daemontool | as it leverage the same code base | 16:51 |
| daemontool | :) | 16:51 |
| daemontool | talk with him | 16:51 |
| reldan | daemontool: yes, what is about rsync? | 16:51 |
| reldan | daemontool: are we going to intergrate it? | 16:51 |
| daemontool | yes | 16:53 |
| daemontool | as soon as I finish this workload related to the repos | 16:53 |
| daemontool | that we have to do | 16:53 |
| daemontool | because we are an official openstack project now | 16:53 |
| daemontool | I'll invest hard on that | 16:53 |
| daemontool | there's some code | 16:53 |
| daemontool | I have been working locally | 16:54 |
| daemontool | after that commits were abandoned | 16:54 |
| daemontool | I have to submit for review | 16:54 |
| daemontool | also | 16:54 |
| daemontool | I'd like the freezer-agent | 16:54 |
| daemontool | execute with pypy | 16:54 |
| daemontool | I did few tests months ago | 16:54 |
| daemontool | and it was really worth | 16:54 |
| daemontool | more and more for rsync | 16:54 |
| daemontool | reldan, after the first release | 16:58 |
| daemontool | if you want we can work on the optimization | 16:58 |
| daemontool | how to make it better | 16:58 |
| daemontool | and so on | 16:58 |
| daemontool | but we need absolutely to have the following features | 16:59 |
| daemontool | 1) volumes incrementals, restorable on a another os | 16:59 |
| daemontool | 2) vms incrementals, restoreable on another os | 16:59 |
| daemontool | 3) block based (preferibly rolling checksum) | 16:59 |
| reldan | vm - how about floating ip - we cannot restore floating ip on different os | 17:00 |
| daemontool | 4) integration tests enhanced and executed from dsvm | 17:00 |
| daemontool | reldan, good point, we have to provide a solution for that | 17:00 |
| daemontool | like reassign floating ips | 17:01 |
| reldan | but I don’t think it is possible. you have an ip range per os installation | 17:01 |
| reldan | and cannot reassing ip from one os installation to another | 17:01 |
| reldan | by api | 17:01 |
| daemontool | you can have the same fqdn, same dns records and different ips | 17:02 |
| daemontool | that would be the limitation | 17:02 |
| daemontool | you can restore to a differnt os, same fqdn, same dns entried in designate | 17:02 |
| daemontool | but different floating ips | 17:02 |
| reldan | yes, agree but floating ip will be different. | 17:03 |
| daemontool | totally agree | 17:03 |
| daemontool | yes | 17:03 |
| daemontool | that wil be our limitation | 17:03 |
| *** reldan has quit IRC | 17:05 | |
| *** szaher_ has joined #openstack-freezer | 17:19 | |
| *** szaher has quit IRC | 17:20 | |
| *** reldan has joined #openstack-freezer | 18:57 | |
| *** ddieterly has quit IRC | 19:37 | |
| *** reldan has quit IRC | 19:39 | |
| *** ddieterly has joined #openstack-freezer | 19:41 | |
| *** reldan has joined #openstack-freezer | 19:56 | |
| *** reldan has quit IRC | 20:07 | |
| *** reldan has joined #openstack-freezer | 20:13 | |
| *** reldan has quit IRC | 20:32 | |
| *** ddieterly has quit IRC | 21:39 | |
| *** ddieterly has joined #openstack-freezer | 21:40 | |
| *** daemontool_ has joined #openstack-freezer | 23:10 | |
| *** daemontool has quit IRC | 23:13 | |
| *** ddieterly has quit IRC | 23:35 | |
| *** yangyapeng has joined #openstack-freezer | 23:35 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!