| *** ddieterly[away] has quit IRC | 00:29 | |
| *** yangyapeng has joined #openstack-freezer | 01:01 | |
| *** EinstCrazy has joined #openstack-freezer | 01:21 | |
| *** ddieterly has joined #openstack-freezer | 01:41 | |
| *** ddieterly has quit IRC | 02:51 | |
| *** EinstCrazy has quit IRC | 03:00 | |
| jith_ | daemontool.. sorry i left for the day... shall i report it now if its a bug? | 04:31 |
|---|---|---|
| *** hparekh_ has joined #openstack-freezer | 04:40 | |
| *** EinstCrazy has joined #openstack-freezer | 04:58 | |
| *** EinstCrazy has quit IRC | 06:06 | |
| *** zhangjn has quit IRC | 07:15 | |
| *** zhangjn has joined #openstack-freezer | 07:20 | |
| *** c00281451_ is now known as chenzeng | 07:54 | |
| *** ferhat has joined #openstack-freezer | 08:43 | |
| ferhat | hi all | 08:43 |
| *** daemontool_ has joined #openstack-freezer | 08:44 | |
| *** daemontool has quit IRC | 08:47 | |
| daemontool_ | slashme, | 08:53 |
| daemontool_ | 2016-03-06 23:30:24.674 | ${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} ${OS_TEST_PATH:-./tempest/test_discover} --list | 08:53 |
| daemontool_ | 2016-03-06 23:30:24.674 | The test run didn't actually run any tests | 08:53 |
| daemontool_ | we need to backport also the tempest change | 08:53 |
| daemontool_ | https://review.openstack.org/#/c/287369/ | 08:55 |
| daemontool_ | I can do that | 08:55 |
| daemontool_ | jith_, yes please report a bug | 08:55 |
| ferhat | hello daemon | 08:56 |
| daemontool_ | hi ferhat | 08:57 |
| ferhat | I want to contribute to freezer | 08:58 |
| daemontool_ | did you manage to solve your issue last Friday? | 08:58 |
| daemontool_ | ferhat, you are most welcome :) | 08:58 |
| dmellado | daemontool_: what's the issue with tempest? | 08:58 |
| ferhat | I have solved every problem. now it is working with horizon dashboard | 08:58 |
| daemontool_ | dmellado, no issue, just that tempest code needs to be backported to stable/liberty otherwise the dsvm gate job fails | 08:59 |
| dmellado | daemontool_: I see | 08:59 |
| dmellado | so you just need to rebase upstream there | 08:59 |
| daemontool_ | we need to cherry-pick the change | 09:00 |
| daemontool_ | yes | 09:00 |
| daemontool_ | resolve the conflicts if any (and I'm pretty sure there's some conflict) | 09:00 |
| daemontool_ | one sec | 09:00 |
| daemontool_ | dmellado, from here http://docs.openstack.org/project-team-guide/stable-branches.html | 09:00 |
| daemontool_ | where it says | 09:01 |
| daemontool_ | $ git checkout -t origin/stable/tango | 09:01 |
| daemontool_ | $ git cherry-pick -x $master_commit_id | 09:01 |
| daemontool_ | $ git review stable/tango | 09:01 |
| ferhat | so daemon, where should I start? | 09:01 |
| daemontool_ | ferhat, | 09:01 |
| daemontool_ | my advise would be | 09:01 |
| daemontool_ | to check if the place you work | 09:01 |
| daemontool_ | needs some feature | 09:01 |
| daemontool_ | or have some priority on something | 09:01 |
| daemontool_ | like oracle backups | 09:01 |
| daemontool_ | or postgres backups | 09:01 |
| daemontool_ | or volumes, instances etc | 09:02 |
| daemontool_ | or if you are good on windows | 09:02 |
| ferhat | I am working in a company named Radore. It is one of the biggest data centers in Turkey. | 09:02 |
| ferhat | and unfortunately, I am the only person who is responsible for opensource software. | 09:03 |
| daemontool_ | great :) | 09:03 |
| ferhat | I can help on features and documentation | 09:03 |
| daemontool_ | ok | 09:03 |
| daemontool_ | I'd say pick the component you more feel fit your skills | 09:03 |
| daemontool_ | agent or scheduler | 09:04 |
| daemontool_ | api, web ui, python-freezerclient | 09:04 |
| ferhat | as Radore we are going to use all the components. so I need to get info for all the components. | 09:05 |
| daemontool_ | ok | 09:05 |
| daemontool_ | you are more a system engineer or a dev engineer | 09:06 |
| ferhat | but I think we will be using web ui mostly | 09:06 |
| daemontool_ | ? | 09:06 |
| yangyapeng | ferhat: welcome | 09:06 |
| ferhat | more system engineer. but I can write codes in intermediate level | 09:06 |
| daemontool_ | ferhat, good | 09:07 |
| daemontool_ | what's the db that is more used in your env? | 09:07 |
| ferhat | mysql | 09:07 |
| daemontool_ | probably you can add support for data consistent backup to more db? | 09:07 |
| daemontool_ | ah ok | 09:07 |
| daemontool_ | mysql is ok | 09:07 |
| ferhat | and mssql | 09:07 |
| daemontool_ | if you want to increase your dev skills | 09:08 |
| daemontool_ | and understand a lots of openstack | 09:08 |
| daemontool_ | you could work on writing tempest tests | 09:08 |
| ferhat | sounds good | 09:09 |
| ferhat | on the other hand documentation is need updating. and as system engineer, documentation is my real job. | 09:09 |
| daemontool_ | ferhat, that would be fantastic | 09:10 |
| daemontool_ | :) | 09:10 |
| daemontool_ | ferhat, we need to review and port to upstream | 09:10 |
| daemontool_ | the documentation from here | 09:10 |
| daemontool_ | https://docs.hpcloud.com/helion/bura/ | 09:10 |
| daemontool_ | that's helion specific | 09:11 |
| daemontool_ | we need to see what's not right | 09:11 |
| ferhat | se we need to create a new document set for general use of openstack | 09:12 |
| daemontool_ | general and specific | 09:12 |
| daemontool_ | the documentation needs to be reorganized | 09:12 |
| daemontool_ | for sure | 09:12 |
| daemontool_ | ferhat, we have the wiki also | 09:12 |
| daemontool_ | https://wiki.openstack.org/wiki/Freezer | 09:13 |
| daemontool_ | so we should have doc organized in a similar way | 09:13 |
| daemontool_ | as other project | 09:13 |
| daemontool_ | even here | 09:13 |
| daemontool_ | http://developer.openstack.org/api-ref.html | 09:13 |
| daemontool_ | like backup | 09:13 |
| ferhat | I see. I think https://wiki.openstack.org/wiki/Freezer is good place to start. because https://wiki.openstack.org/wiki/Freezer is the place I found you guys. | 09:14 |
| ferhat | and github | 09:14 |
| daemontool_ | ok | 09:14 |
| daemontool_ | would be good to have ops documentation http://docs.openstack.org/openstack-ops/content/openstack-ops_preface.html | 09:15 |
| daemontool_ | there are many things to do, just pick one :) | 09:15 |
| daemontool_ | ferhat, also try to be involved in the cod reviews | 09:15 |
| daemontool_ | so you will get more and more familiar with the source code over time | 09:15 |
| ferhat | that would be nice. but I should start slowly. because this will be my first open source project. | 09:16 |
| ferhat | and I have newly amazed how openstack ecosystem works. | 09:17 |
| ferhat | and how do I get in here: http://stackalytics.com/ :) | 09:18 |
| ferhat | and also I need to translate the web-ui to Turkish | 09:20 |
| daemontool_ | ah that's brilliant | 09:20 |
| daemontool_ | m3m0, ^^ | 09:21 |
| daemontool_ | ferhat, the changes in the wiki are not part of stackalytics | 09:21 |
| daemontool_ | so check sphinx and that alike on how the documentation is generated automatically | 09:22 |
| daemontool_ | we have already everything needed in place | 09:22 |
| daemontool_ | to build it | 09:22 |
| daemontool_ | check the other projects | 09:22 |
| daemontool_ | how they do that | 09:23 |
| daemontool_ | also for internationalization | 09:23 |
| daemontool_ | szaher, would be good to have it traslated also in Arabic? | 09:23 |
| daemontool_ | and Spanish | 09:23 |
| daemontool_ | fantastic... | 09:23 |
| ferhat | I like the sound of generating automatically :P | 09:24 |
| daemontool_ | we have a gate job | 09:26 |
| daemontool_ | gate-freezer-api-docs | 09:26 |
| ferhat | ok. for start. I will update openstack wiki side of freezer. than I will write a detailed installation document. than I will look in to sphinx for automatic document generation. | 09:26 |
| daemontool_ | and gate-freezer-docs | 09:26 |
| daemontool_ | ferhat, in the tox.ini in openstack/freezer | 09:26 |
| daemontool_ | there's a section | 09:27 |
| daemontool_ | for doc | 09:27 |
| daemontool_ | [testenv:docs] | 09:27 |
| daemontool_ | commands = | 09:27 |
| daemontool_ | python setup.py build_sphinx | 09:27 |
| daemontool_ | take a look there | 09:27 |
| daemontool_ | also how to upload auatomatically the documentation to public resources | 09:27 |
| daemontool_ | but after we made it better | 09:27 |
| daemontool_ | sounds good? | 09:27 |
| ferhat | yes. it sounds good. | 09:28 |
| ferhat | so is there any registration procedure for me to involve in freezer? | 09:29 |
| daemontool_ | nope | 09:30 |
| daemontool_ | after few months of consistent contributions | 09:30 |
| daemontool_ | you'll be proposed as core | 09:30 |
| daemontool_ | it's open, no need of registration | 09:30 |
| daemontool_ | make sure also the changes in the wiki are reported somewhere in the repo, like the README | 09:31 |
| ferhat | ok | 09:31 |
| ferhat | will do that | 09:32 |
| dmellado | daemontool_: if you need spanish I can have a look | 09:32 |
| ferhat | we do not have a project in zanata | 09:34 |
| ferhat | than I will be bugging you while creating new documents. | 09:41 |
| daemontool_ | ferhat, dmellado ok | 09:44 |
| daemontool_ | we need before to create a minimum structure in the web ui that allows to switch language | 09:44 |
| daemontool_ | https://wiki.openstack.org/wiki/Translations | 09:45 |
| ferhat | so we are going to use Zanata for translation? | 09:46 |
| ferhat | I have opened new project with freezer-web-ui id | 09:47 |
| ferhat | please let me know if you need access | 09:47 |
| daemontool_ | ferhat, if Zanata is the common way in openstack to do translations | 09:54 |
| daemontool_ | then yes we use it | 09:54 |
| daemontool_ | ferhat, yes we need access | 09:54 |
| ferhat | OpenStack is using a Zanata instance running at https://translate.openstack.org/ as translation management platform. | 09:54 |
| ferhat | pleas open account on zanata so I can add you guys as maintainer | 09:55 |
| daemontool_ | ok | 09:55 |
| *** reldan has joined #openstack-freezer | 09:58 | |
| daemontool_ | slashme, ping | 10:01 |
| daemontool_ | ferhat, registered | 10:05 |
| daemontool_ | thanks for this | 10:05 |
| ferhat | Fausto Marzi @daemontool added as maintainer | 10:06 |
| daemontool_ | ferhat, thanks going to get some food | 10:11 |
| daemontool_ | slashme, if you have time, can you backport https://review.openstack.org/#/c/287369/ ? | 10:12 |
| daemontool_ | I'd like to focus on the rsync stuff today if possible | 10:12 |
| daemontool_ | otherwise let me know as soon as you can and I'll do it | 10:12 |
| reldan | Guys, please +workflow ) https://review.openstack.org/#/c/288416/ | 10:14 |
| *** daemontool_ has quit IRC | 10:16 | |
| ferhat | when I try to backup nova instance. I am getting following error: root CRITICAL [*] Critical Error: Please provide a valid backup mode | 10:27 |
| *** yangyapeng has quit IRC | 10:28 | |
| *** daemontool has joined #openstack-freezer | 10:35 | |
| daemontool | slashme, I'm working on https://review.openstack.org/#/c/287369/ | 10:38 |
| daemontool | it's all right | 10:38 |
| slashme | Donme | 10:39 |
| slashme | 8d220b56a7a6ba06a396e7bfc569fe773700cbe8 | 10:39 |
| slashme | Oops | 10:39 |
| slashme | https://review.openstack.org/289251 | 10:39 |
| slashme | daemontool: ^^ | 10:40 |
| daemontool | ah ok | 10:40 |
| daemontool | ty | 10:40 |
| daemontool | slashme, brilliant :) | 10:42 |
| daemontool | on kilo we do not have the dsvm gate job enabled | 10:42 |
| daemontool | or dods | 10:42 |
| daemontool | docs | 10:43 |
| daemontool | so we won't have the issue | 10:43 |
| daemontool | slashme, circular dependencies... | 11:01 |
| slashme | ... | 11:02 |
| daemontool | so one commit depends on the code of the other | 11:02 |
| daemontool | so one option is to join the 2 changes in one | 11:05 |
| daemontool | so we should see if 2 cherrypicks can be done | 11:06 |
| slashme | daemontool: https://review.openstack.org/#/c/289254/ | 11:09 |
| daemontool | lol, ok :) | 11:11 |
| slashme | Getting there | 11:15 |
| daemontool | ok | 11:15 |
| daemontool | are you uploading a new patchset? | 11:16 |
| daemontool | not verified, not sure what's happening there | 11:16 |
| slashme | No | 11:16 |
| slashme | I don't know what the problem is | 11:17 |
| slashme | AttributeError: 'Requirement' object has no attribute 'extras' | 11:17 |
| daemontool | rechecked | 11:19 |
| jith_ | daemontool: sure.. before i will again try with a fresh install... | 11:21 |
| daemontool | jith_, it's a unicode things | 11:22 |
| daemontool | cause in the log we are not using i18n | 11:22 |
| daemontool | so it's a freezer problema for sure | 11:22 |
| jith_ | daemontool: oh ok | 11:22 |
| m3m0 | ferhat let me know if I can help you with anything | 11:30 |
| daemontool | all, https://review.openstack.org/#/c/288697/ | 11:34 |
| daemontool | it looks like requirements are update automatically now | 11:34 |
| reldan | +workflow please https://review.openstack.org/#/c/288416/ | 11:36 |
| daemontool | slashme, before we need to merge https://review.openstack.org/#/c/288697/ | 11:40 |
| daemontool | cause the global-requirements chagned | 11:40 |
| daemontool | changed | 11:40 |
| slashme | daemontool: does not matter, I'm working on liberty, global-reqs are different anyway. | 11:41 |
| daemontool | ok something changed, as the gate-freezer-api-requirements is failing | 11:42 |
| slashme | That patch (master auto change of the requirements) seems really weird. | 11:43 |
| slashme | You sure about merging it ? | 11:43 |
| slashme | It seems like it's putting back some very old code ... | 11:43 |
| daemontool | like that pbr? | 11:44 |
| daemontool | the global-requirements change dynamically | 11:44 |
| daemontool | I think is better if the changes are reflected in our requirements automatically | 11:45 |
| daemontool | that pbr change is good | 11:45 |
| daemontool | it's probably related | 11:45 |
| daemontool | to a dependencies issues with some global-requirement changes | 11:45 |
| daemontool | as it happened to us in the past | 11:45 |
| slashme | What about that copyright from 2013 ??? | 11:46 |
| *** reldan has quit IRC | 11:46 | |
| daemontool | that is wrong | 11:47 |
| daemontool | and infra probably need to fix it | 11:47 |
| slashme | Requirements and test-requirements are fine. | 11:47 |
| slashme | Just changes to setup.py seems odd | 11:47 |
| slashme | We don't need to import multiprocessing anymore, this was used for a very old hack where we used pip as a subprocess to install setuptool. We don't do that anymore | 11:49 |
| slashme | Oh well no | 11:49 |
| daemontool | slashme, I'm asking clarification on #openstack-stable | 11:56 |
| daemontool | for that requirements error | 11:56 |
| slashme | Thx | 11:57 |
| slashme | daemontool: I'm making some progress on https://review.openstack.org/#/c/289254/ | 12:00 |
| *** reldan has joined #openstack-freezer | 12:05 | |
| daemontool | reldan, hang on 1 hour for the refactor | 12:07 |
| daemontool | we are resolving a deps/backporting issue | 12:07 |
| daemontool | reldan, probably we should backport the refactor change | 12:09 |
| daemontool | to liberty also | 12:09 |
| daemontool | after the current changes | 12:09 |
| reldan | daemontool: I suppose it is too much efforts for backward compatibility | 12:09 |
| reldan | daemontool: I would prefer to concentrate our effort on master | 12:10 |
| daemontool | reldan, after our changes | 12:10 |
| daemontool | let's see if that patch can be backported without conflicts | 12:10 |
| daemontool | if yes, then we can backport | 12:11 |
| daemontool | otherwise nothing | 12:11 |
| daemontool | I'll do that | 12:11 |
| reldan | daemontool: Sure, but I like Scala approach - don’t invest much time in backward compatibility. Let’s use fresh version instead | 12:11 |
| daemontool | reldan, yes I agree | 12:11 |
| daemontool | the things is that in the current state | 12:12 |
| daemontool | if there's a bug in liberty | 12:12 |
| daemontool | we can't fix it :( | 12:12 |
| daemontool | so this would be the bare minimum to do | 12:12 |
| reldan | Yes, but we actually don’t use anything special from mitaka in our master | 12:12 |
| reldan | so frankly, our master is liberty | 12:12 |
| daemontool | in terms of features, yes | 12:12 |
| daemontool | in terms of how the code is organized | 12:13 |
| daemontool | there's are differencies | 12:13 |
| reldan | we can just rewrite liberty by master | 12:13 |
| daemontool | after these changes we are doing with slashme, yes | 12:13 |
| daemontool | but in the current state as it is now, not | 12:14 |
| daemontool | verification fails | 12:14 |
| reldan | Because I understand what’s for cinder or nova should support kilo liberty … etc. They have strong coupling with different projects. And changes in version may destroy everything | 12:14 |
| reldan | For us - we use only basic api stuff from other projects | 12:14 |
| daemontool | reldan, I agree | 12:15 |
| ferhat | my horizon installation is uder /horizon url | 12:19 |
| ferhat | and I am having quite problem with web-ui for stable/k,lo branch | 12:19 |
| ferhat | do you guys have any solution for this problem? | 12:19 |
| daemontool | ferhat, m3m0 is the man there | 12:20 |
| ferhat | is he here? | 12:20 |
| daemontool | it should be, he'll be back here shortly if not | 12:21 |
| daemontool | as is food time there | 12:21 |
| m3m0 | i'm here | 12:21 |
| *** EinstCrazy has joined #openstack-freezer | 12:21 | |
| m3m0 | what's the problem? | 12:22 |
| daemontool | frescof, ping | 12:26 |
| *** ferhat_ has joined #openstack-freezer | 12:27 | |
| ferhat_ | lost connection | 12:27 |
| ferhat_ | my horizon dashboard is installed in /horizon | 12:27 |
| ferhat_ | that is why I have changed /disaster_recovery/ ... uri to /horizon/disaster_recovery | 12:28 |
| ferhat_ | I am doing this change from the java codes | 12:28 |
| ferhat_ | I think my web-ui installation is some what broken because of this uri problem | 12:29 |
| *** ferhat has quit IRC | 12:29 | |
| daemontool | slashme, it works | 12:32 |
| slashme | Nice, let's merge it. | 12:33 |
| slashme | Worth noting that this is the second time I have to squash commits when backporting because of cyclic dependancies caused by modification in the gates done before backporting the code. We should be more carefull with this. | 12:35 |
| *** ferhat_ has quit IRC | 12:36 | |
| daemontool | yep | 12:37 |
| daemontool | today we are going to review also the other pending commits | 12:38 |
| daemontool | on the 3 repos | 12:38 |
| daemontool | please | 12:38 |
| *** ferhat has joined #openstack-freezer | 12:39 | |
| daemontool | all, can we move forward https://review.openstack.org/#/c/289254/ please | 12:43 |
| *** EinstCrazy has quit IRC | 12:43 | |
| *** ferhat has quit IRC | 12:44 | |
| *** EinstCrazy has joined #openstack-freezer | 12:45 | |
| *** ddieterly has joined #openstack-freezer | 12:45 | |
| *** ferhat has joined #openstack-freezer | 12:48 | |
| *** ddieterly has quit IRC | 12:50 | |
| ferhat | I am sorry m3m0 | 12:51 |
| ferhat | I am finally back | 12:52 |
| ferhat | did you get my message? | 12:52 |
| *** ddieterly has joined #openstack-freezer | 12:57 | |
| m3m0 | ferhat: yep but where did you change the uri? and what error are you getting ?\ | 13:01 |
| ferhat | I have changed in three different files | 13:02 |
| ferhat | freezer.jobs.sortable.js | 13:03 |
| ferhat | freezer.js | 13:03 |
| ferhat | freezer.restore.js | 13:03 |
| ferhat | I also had to put static directory in /usr/share/openstack-dashboard/static directory | 13:04 |
| ferhat | it does not work otherwise | 13:04 |
| m3m0 | mmmm are working in liberty right? because there was a patch fixing that | 13:05 |
| daemontool | I think he's working on kilo | 13:06 |
| ferhat | I am working on kilo | 13:07 |
| ferhat | yes | 13:07 |
| *** ddieterly is now known as ddieterly[away] | 13:09 | |
| ferhat | I should open a bug report for stable/kilo release | 13:10 |
| m3m0 | yes, we need to backport that patch then | 13:11 |
| ferhat | do you remember the bug report link of the old bug. | 13:13 |
| daemontool | m3m0, reldan frescof please review https://review.openstack.org/#/c/289254/ when you can | 13:14 |
| daemontool | and https://review.openstack.org/#/c/288416/ | 13:15 |
| ferhat | https://review.openstack.org/#/c/255698/ this was the patch | 13:16 |
| *** fubi has joined #openstack-freezer | 13:21 | |
| *** EinstCrazy has quit IRC | 13:28 | |
| *** ddieterly[away] is now known as ddieterly | 13:29 | |
| *** EinstCrazy has joined #openstack-freezer | 13:31 | |
| m3m0 | ferhat: this was https://review.openstack.org/#/c/256383/ | 13:35 |
| ferhat | so how should I apply this patch. | 13:37 |
| *** ddieterly is now known as ddieterly[away] | 13:38 | |
| *** ddieterly[away] has quit IRC | 13:39 | |
| *** EinstCrazy has quit IRC | 13:50 | |
| *** EinstCrazy has joined #openstack-freezer | 13:51 | |
| *** ddieterly has joined #openstack-freezer | 14:11 | |
| ferhat | how can I delete backup metadata | 14:44 |
| m3m0 | very good question | 14:50 |
| m3m0 | we have a bug in the api | 14:50 |
| m3m0 | that needs to be fixed | 14:50 |
| m3m0 | in order to delete that metadata | 14:51 |
| slashme | Hey guys, It's that time again: backport party. | 15:16 |
| slashme | Ready, Steady, Review ! | 15:16 |
| slashme | Freezer: | 15:16 |
| slashme | https://review.openstack.org/288539 Add SSL support for freezer | 15:16 |
| slashme | https://review.openstack.org/288540 Fix a mistake about function for install_freezer | 15:16 |
| slashme | https://review.openstack.org/288542 incorrect enable plugin url in doc | 15:16 |
| slashme | https://review.openstack.org/288545 Add space to log message | 15:16 |
| slashme | https://review.openstack.org/288547 Switch cinder api to v2 and add --force and --incremental | 15:16 |
| slashme | https://review.openstack.org/288550 Fix metadata curr_level | 15:16 |
| slashme | https://review.openstack.org/288555 lvm snapshot unique name | 15:16 |
| slashme | Freezer-web-ui: | 15:16 |
| slashme | https://review.openstack.org/288574 Add SSL support for freezer-web-ui | 15:16 |
| slashme | https://review.openstack.org/288578 fixed compilemessages error when install use devstack | 15:16 |
| slashme | https://review.openstack.org/288583 This is incorrect url in example doc and conf | 15:16 |
| slashme | https://review.openstack.org/288587 fixed incorrect directory install freezer-web-ui | 15:16 |
| daemontool | all, can we also review https://review.openstack.org/#/c/288416/ please | 15:21 |
| *** EinstCrazy has quit IRC | 15:25 | |
| *** ddieterly is now known as ddieterly[away] | 15:35 | |
| *** dschroeder has joined #openstack-freezer | 15:36 | |
| daemontool | reldan, ping | 15:38 |
| *** ddieterly[away] is now known as ddieterly | 15:38 | |
| reldan | daemontool: yes | 15:38 |
| daemontool | something I'm not understanding | 15:38 |
| daemontool | in the current tar logic | 15:38 |
| daemontool | where do you get the tar incremental file path | 15:38 |
| daemontool | from? | 15:38 |
| daemontool | I see | 15:39 |
| daemontool | def set_listed_incremental(self, absolute_path): | 15:39 |
| daemontool | from tar_builder | 15:39 |
| daemontool | ah from tar_engine | 15:40 |
| daemontool | tar_command.set_listed_incremental(manifest_path) | 15:40 |
| daemontool | ok | 15:40 |
| reldan | daemontool: in tar_engine tar_command.set_listed_incremental(manifest_path) | 15:40 |
| daemontool | ok | 15:40 |
| daemontool | from manifest_path | 15:40 |
| daemontool | ty | 15:40 |
| reldan | daemontool: and manifest from manifest = backup.storage.download_meta_file(backup) | 15:41 |
| daemontool | ty | 15:42 |
| daemontool | frescof, slashme m3m0 , all please review https://review.openstack.org/#/c/288416/ | 15:49 |
| ddieterly | does anyone have any objections to adding tempest tests to the freezer gate job? | 16:01 |
| ddieterly | daemontool m3m0 reldan ^^ | 16:02 |
| daemontool | ddieterly, no objections, do you want to add a dsvm gate job for openstack/freezer_ | 16:02 |
| daemontool | ? | 16:02 |
| ddieterly | i was planning on modifying the existing gate job | 16:03 |
| daemontool | ok | 16:03 |
| daemontool | ddieterly, what do you think if we use the same | 16:03 |
| daemontool | gate job layout | 16:03 |
| daemontool | for all our repos | 16:03 |
| ddieterly | ah, but the web-ui is using that -- gate-freezer-devstack-dsvm | 16:04 |
| daemontool | ok | 16:04 |
| ddieterly | so, yes, i guess i'll need to add another gate job like i did for the freezer-api | 16:04 |
| daemontool | ok | 16:04 |
| daemontool | why are we doing that? | 16:04 |
| ferhat | I am getting following error message while taking nova backup | 16:04 |
| ferhat | Critical Error: Please provide a valid backup mode | 16:04 |
| daemontool | not sure if I'm correct but | 16:04 |
| daemontool | what if we use the same gate job layout | 16:04 |
| daemontool | like the same gate job | 16:05 |
| daemontool | but what would change are the tests it self | 16:05 |
| daemontool | for each repo | 16:05 |
| daemontool | case the testing infrastructure after all is the same | 16:05 |
| daemontool | we need to the api and the storage media | 16:05 |
| daemontool | in most of the cases | 16:06 |
| daemontool | so we have the same gate job | 16:06 |
| daemontool | that build the same infrastructure for tests | 16:06 |
| daemontool | for all the repos | 16:06 |
| daemontool | then each repo would implement its own tests | 16:06 |
| ddieterly | there is an env var in the gate job that specifies which tests to run | 16:06 |
| daemontool | so, so why are we creating one gate job for each component? | 16:07 |
| daemontool | we need the storage media, the api and the env where we execute the tests from | 16:08 |
| ddieterly | to be honest, because it is the easiest thing to do and we know it works | 16:08 |
| ddieterly | but... if you know how to do it otherwise, that'd be great | 16:08 |
| daemontool | ddieterly, it's not that different from what you are doing | 16:09 |
| daemontool | it's just that rather than setting the different env in the gate job for each repo | 16:09 |
| daemontool | you leave the same gate job for all | 16:09 |
| daemontool | and adjust settings in the repos itself like hook files | 16:10 |
| ddieterly | in the settings file? or somewhere else? | 16:10 |
| daemontool | but if you feel more comfortable with that | 16:10 |
| daemontool | do that | 16:10 |
| ddieterly | yea, i actually feel more comfortable with the cut and paste at this pioint | 16:10 |
| ddieterly | we only have 3 components, so it should be limited | 16:10 |
| ddieterly | if it were more, then i'd feel bad about it | 16:11 |
| ddieterly | and then, in the future, if the gate jobs diverge, we will be ready | 16:11 |
| daemontool | ok | 16:12 |
| daemontool | we have 4 | 16:12 |
| daemontool | python-freezerclient | 16:12 |
| daemontool | agent, api and webui | 16:12 |
| ddieterly | some are all in the same repo aren't they? | 16:12 |
| ddieterly | we have 3 repos? right? | 16:12 |
| daemontool | agent, api and web ui one each repo | 16:12 |
| daemontool | this commit split the freezerclient from agent: | 16:13 |
| daemontool | can't find it | 16:14 |
| daemontool | m3m0, where-s the commit to split the freezerclient from agent repo? | 16:14 |
| daemontool | anyway ddieterly do what you thing is the best approach | 16:15 |
| daemontool | the only thing | 16:15 |
| ddieterly | ok, thanks | 16:15 |
| daemontool | let's try to avoid deuplicated things | 16:15 |
| daemontool | cause then we have to maintin it | 16:15 |
| daemontool | maintain | 16:15 |
| m3m0 | daemontool https://github.com/memogarcia/python-freezerclient | 16:15 |
| daemontool | ok but we need to have a commit | 16:15 |
| daemontool | I had oen | 16:15 |
| daemontool | one | 16:15 |
| m3m0 | working on the tests right now | 16:15 |
| m3m0 | a commit? where? | 16:15 |
| daemontool | there was a commit | 16:16 |
| daemontool | to split this code https://github.com/openstack/freezer/tree/master/freezer/apiclient | 16:16 |
| daemontool | that is the code we are placing out of the openstack/freezer repo | 16:17 |
| daemontool | to create the python-freezerclient repo | 16:17 |
| m3m0 | is not there yet, there is no point to split until we have the new repo setup and working | 16:18 |
| daemontool | ddieterly, this is the new repo creation request to infra https://review.openstack.org/#/c/255349/ | 16:20 |
| daemontool | m3m0, you created https://github.com/memogarcia/python-freezerclient from the apiclient code right | 16:21 |
| m3m0 | yes, but I had to clone a different repo | 16:21 |
| daemontool | with the git history of any commit related to files of that directory | 16:21 |
| daemontool | right? | 16:21 |
| m3m0 | yes, it contains the history | 16:21 |
| *** EinstCrazy has joined #openstack-freezer | 16:22 | |
| daemontool | ok | 16:22 |
| m3m0 | there is one more step but thats when the repo is created | 16:23 |
| m3m0 | I need to squash all the new commits | 16:23 |
| daemontool | ok | 16:23 |
| *** ddieterly is now known as ddieterly[away] | 16:36 | |
| *** ddieterly[away] is now known as ddieterly | 16:39 | |
| openstackgerrit | Deklan Dieterly proposed openstack/freezer: Start to introduce tempest tests. https://review.openstack.org/289443 | 16:49 |
| openstackgerrit | Deklan Dieterly proposed openstack/freezer: Start to introduce tempest tests. https://review.openstack.org/289443 | 16:51 |
| *** EinstCrazy has quit IRC | 16:55 | |
| *** ddieterly is now known as ddieterly[away] | 17:15 | |
| *** fabv has joined #openstack-freezer | 17:15 | |
| *** ddieterly[away] is now known as ddieterly | 17:18 | |
| *** EinstCrazy has joined #openstack-freezer | 17:53 | |
| *** reldan has quit IRC | 17:58 | |
| *** EinstCrazy has quit IRC | 18:02 | |
| ddieterly | daemontool does freezer have a milestone release plan for mitaka? | 18:19 |
| ddieterly | if so, where is it? thanks | 18:20 |
| ddieterly | doug hellman was asking about it in the room last week | 18:20 |
| ddieterly | now i'm curious about it | 18:21 |
| *** ddieterly is now known as ddieterly[away] | 18:32 | |
| *** fabv has quit IRC | 18:32 | |
| daemontool | the milestone release plan is the same as mitaka release | 18:34 |
| daemontool | as freezer follow the cycle release | 18:34 |
| daemontool | as per | 18:34 |
| daemontool | https://governance.openstack.org/reference/projects/freezer.html | 18:34 |
| daemontool | cycle-with-milestone | 18:34 |
| daemontool | I think he was asking for this: | 18:35 |
| daemontool | https://review.openstack.org/#/c/288322/ | 18:35 |
| daemontool | ddieterly[away], ^^ | 18:36 |
| daemontool | szaher, do we have currently a validation of the supported options? Like what happen if a non existent option is added to the config file | 18:43 |
| *** ddieterly[away] is now known as ddieterly | 18:57 | |
| ddieterly | daemontool ok, thanks | 18:57 |
| *** ddieterly is now known as ddieterly[away] | 18:58 | |
| *** reldan has joined #openstack-freezer | 19:14 | |
| *** ddieterly[away] is now known as ddieterly | 19:45 | |
| *** reldan has quit IRC | 19:59 | |
| *** reldan has joined #openstack-freezer | 19:59 | |
| *** ddieterly has quit IRC | 20:20 | |
| *** reldan has quit IRC | 22:29 | |
| *** reldan has joined #openstack-freezer | 22:37 | |
| *** reldan has quit IRC | 23:44 | |
| *** reldan has joined #openstack-freezer | 23:51 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!