*** reldan has quit IRC | 00:30 | |
*** reldan has joined #openstack-freezer | 00:44 | |
*** memogarcia has quit IRC | 00:49 | |
*** reldan has quit IRC | 01:17 | |
openstackgerrit | sibaoli proposed openstack/freezer-web-ui: Fixes actions list can't be obtained when creating/editing jobs https://review.openstack.org/255698 | 07:18 |
---|---|---|
*** openstackgerrit has quit IRC | 09:32 | |
*** openstackgerrit has joined #openstack-freezer | 09:33 | |
*** daemontool has joined #openstack-freezer | 09:37 | |
daemontool | szaher: https://review.openstack.org/#/c/252568/ | 09:40 |
daemontool | some minor chagne | 09:40 |
daemontool | change | 09:41 |
daemontool | so we are completely breaking compatibility? | 09:41 |
*** memogarcia has joined #openstack-freezer | 09:55 | |
*** memogarcia has quit IRC | 10:00 | |
*** samuelBartel has joined #openstack-freezer | 10:08 | |
*** reldan has joined #openstack-freezer | 10:11 | |
*** vannif has joined #openstack-freezer | 10:18 | |
daemontool | reldan: vannif m3m0 Slashme re https://review.openstack.org/#/c/252568/ | 10:19 |
daemontool | is szaher there around? | 10:19 |
reldan | Yes, here | 10:19 |
daemontool | is https://review.openstack.org/#/c/252568/ breaking backwards compatibility with corrent options? | 10:20 |
daemontool | or are we going to support both and the old approach is deprecated? | 10:20 |
reldan | Don’t know actually. He is speaking with Pierre | 10:20 |
daemontool | ok | 10:20 |
reldan | What about https://review.openstack.org/#/c/247840/ ? | 10:20 |
daemontool | reldan: I'm reviewing it | 10:24 |
daemontool | today we'll merge it | 10:24 |
reldan | Thank you | 10:24 |
daemontool | I think we need to find a way | 10:25 |
daemontool | to remove the version hardcoded | 10:25 |
daemontool | and just use the vrsion number set in setup.cfg | 10:26 |
daemontool | reldan: what do you think | 10:28 |
daemontool | if we send in the oslo changes from szaher, and after that we merge the parallel with the same log approach? | 10:28 |
daemontool | so we make sure also the parallel backup works with that changes? | 10:29 |
reldan | daemontool: 100% agree. I suppose we can сheck how it is implemented in nova or keystone | 10:29 |
daemontool | I think, probably that's what szaher already checked | 10:29 |
reldan | daemontool: Or accept parallel backup first | 10:29 |
reldan | Otherwise I need to reimplement configuration file to oslo | 10:30 |
daemontool | reldan: I'm saying that | 10:30 |
daemontool | because for instance here https://review.openstack.org/#/c/247840/8/freezer/storage/multiple.py | 10:30 |
daemontool | like 18 | 10:30 |
daemontool | uses old logging approach | 10:30 |
daemontool | while after the szaher patch | 10:30 |
daemontool | we should use config and log with oslo | 10:30 |
reldan | daemontool: Yes, as well as config | 10:30 |
daemontool | reldan: so I was wondering, as we need to do that anyway | 10:31 |
daemontool | wouldn't be better to do that now? | 10:31 |
daemontool | right after the oslo changes goes in? | 10:31 |
daemontool | I know you have to do changes, but I think it make sense | 10:31 |
reldan | In case of oslo changes goes before my changes, just my changes are waiting almost three weeks to be reviewed | 10:31 |
reldan | Yes, I will fix it | 10:32 |
daemontool | reldan: so is that ok for you? or you want to send it in before the parallel? | 10:32 |
reldan | I actually don’t know, probably it will be better to accept parallel first. I am using multiple sections in config file. After merging oslo, I need time to reimplement it in oslo. So I need to read about it first etc | 10:34 |
reldan | But If you suppose that oslo goes first - I’m fine with that | 10:34 |
reldan | I don’t think it is a big deal to replace log and config in my code to oslo | 10:34 |
daemontool | my question is: if we send in the oslo config at anytime, does that break anything in the parallel code? | 10:35 |
daemontool | breaking parallel is more critical I suppose... | 10:35 |
reldan | Yes, sure. I’m using old config, moving to oslo breaks parallel in this place | 10:36 |
reldan | https://review.openstack.org/#/c/247840/8/freezer/config.py this code | 10:36 |
daemontool | reldan: excellent, good spot | 10:37 |
daemontool | szaher: you have few comments on your code | 10:37 |
daemontool | if you can do that changes asap, we can send the code in | 10:37 |
daemontool | then reldan you can rebase, we can do quick tests and send it in | 10:38 |
daemontool | sound? vannif Slashme you too? | 10:38 |
szaher | daemontool sorry I was checking that | 10:39 |
szaher | actually there is no version file for freezer so I am going to create that | 10:39 |
szaher | I cannot get the version from setup.cfg because at some point I won't be here so the version file is the best way to do it | 10:39 |
daemontool | szaher: mmhhh.... | 10:40 |
szaher | we have only one issue with backward compatibility which is -l option for passing the log file | 10:40 |
daemontool | 1 sec | 10:40 |
daemontool | I'm just seeign the other project does not have a version tag in setup.cfg | 10:42 |
daemontool | they just uses tags on the git repo | 10:42 |
Slashme | What is the problem with the parralel backup change and oslo ? Saad's change for oslo only concerns the freezer-scheduler for now | 10:43 |
Slashme | Not the freezer-agent | 10:43 |
szaher | daemontool that how novaclient gets the version from pbr itself https://github.com/openstack/python-novaclient/blob/713b6f12e8ca3d4461b9dca12b71f899c53a7f23/novaclient/__init__.py | 10:46 |
szaher | so I think we will use the same ! | 10:46 |
szaher | also they have a version manager here https://github.com/openstack/python-novaclient/blob/fc2f4abf6c9fd9c297b61b9f4476102924006d7e/novaclient/v2/versions.py because they support multiple versions in the same app | 10:49 |
daemontool | Slashme: OK | 10:50 |
daemontool | szaher: perfect | 10:51 |
szaher | Ok, will that now ... | 10:52 |
szaher | will fix * | 10:53 |
Slashme | /etc/freezer/scheduler.conf or /etc/freezer/freezer-scheduler.conf ? | 10:57 |
Slashme | Opinions ? | 10:57 |
daemontool | freezer-scheduler.conf | 11:00 |
daemontool | so if someone with puppet or chef or ansible wants to put it on a different location | 11:00 |
daemontool | the file can still be recognised | 11:00 |
Slashme | Makes sense :) | 11:00 |
Slashme | szaher: ^^ | 11:01 |
daemontool | here do you think we should create the feezer-specs repo? | 11:10 |
daemontool | s/feezer/freezer/ | 11:11 |
daemontool | reldan: anyway, here https://review.openstack.org/#/c/247840/8 the code is really good | 11:11 |
reldan | daemontool: Thank you | 11:12 |
reldan | I can relocate imports, but changes to oslo.config should be after moving master to oslo.conf | 11:12 |
daemontool | reldan: ok, I think it is a sensible way of doing it | 11:13 |
daemontool | I think we need a freezer-specs repo | 11:14 |
daemontool | but we need to spend time on it | 11:17 |
daemontool | after the python-freezerclient is in a reasonable shape, we can focus on that | 11:18 |
daemontool | I'll proceed on creating that repo after the creation and import of the python-freezerclient | 11:20 |
daemontool | repo | 11:20 |
daemontool | also, we need to integrate the freezerclient | 11:24 |
daemontool | with openstack-client? | 11:24 |
daemontool | https://review.openstack.org/#/c/243348/ | 11:24 |
daemontool | https://review.openstack.org/#/c/243348/2/specs/deprecate-cli.rst | 11:25 |
daemontool | so provavly we sould move directly to openstack client? | 11:25 |
daemontool | I'm asking that on #openstack-dev | 11:29 |
vannif | I like the idea of the openstack client, but we need to define the modules and the options in a consistent and clear way. | 11:35 |
vannif | maybe first define the options, the use cases ... and wait for enough people to agree on that | 11:36 |
daemontool | vannif: well let's do that asap, as we need to move the freezerclient on a dedicated repo or onto openstack-client | 11:41 |
*** reldan has quit IRC | 11:42 | |
*** emildi_ has joined #openstack-freezer | 11:48 | |
*** sputnik13 has quit IRC | 11:57 | |
*** reldan has joined #openstack-freezer | 11:59 | |
*** vannif has quit IRC | 11:59 | |
openstackgerrit | Eldar Nugaev proposed openstack/freezer: Parallel backup https://review.openstack.org/247840 | 12:00 |
Slashme | We should also start doing release notes (maybe using reno ) | 12:02 |
daemontool | yes | 12:06 |
daemontool | ++ | 12:06 |
*** emildi__ has joined #openstack-freezer | 12:08 | |
*** emildi_ has quit IRC | 12:08 | |
daemontool | ehy can you read me? | 12:09 |
jokke_ | Slashme: reno is really good idea to go for right from the start | 12:13 |
jokke_ | no need to a) reinvent the wheel b) migrate to reno then later on | 12:13 |
*** emildi__ has quit IRC | 12:28 | |
szaher | daemontool the setup.cfg for freezer is not updated. it has 1.2.0 .... https://github.com/openstack/freezer/blob/master/setup.cfg | 12:30 |
szaher | Slashme | 12:30 |
openstackgerrit | Saad Zaher proposed openstack/freezer: Switch freezer-scheduler to oslo.config and oslo.log switch freezer-scheduler to use oslo.config and switch from native python logging module to oslo.log This commit includes: - using oslo.config for parsing cli and config files options - using oslo.log i https://review.openstack.org/252568 | 12:41 |
*** daemontool has quit IRC | 12:44 | |
*** openstackgerrit has quit IRC | 12:47 | |
*** openstackgerrit has joined #openstack-freezer | 12:48 | |
*** szaher_ has joined #openstack-freezer | 14:42 | |
*** daemontool has joined #openstack-freezer | 14:46 | |
daemontool | reldan: ping | 14:47 |
reldan | Yes, I’m here | 14:48 |
*** chenzeng has quit IRC | 14:49 | |
*** chenzeng has joined #openstack-freezer | 14:49 | |
szaher_ | Yes | 15:01 |
szaher_ | daemontool I did the patch and it's in the up stream now | 15:01 |
szaher_ | check plz | 15:01 |
szaher_ | Also -l option won't be available anymore because of oslo.log | 15:01 |
daemontool | mmhhh | 15:05 |
daemontool | szaher_: ok | 15:05 |
daemontool | ty | 15:05 |
daemontool | well done btw :) | 15:05 |
szaher_ | Thanks :) | 15:06 |
*** memogarcia has joined #openstack-freezer | 15:20 | |
*** memogarcia has quit IRC | 15:25 | |
*** daemontool has quit IRC | 15:32 | |
*** reldan has quit IRC | 15:48 | |
*** reldan has joined #openstack-freezer | 15:55 | |
m3m0 | hey guys who is ready for the weekly meeting? | 15:58 |
*** daemontool has joined #openstack-freezer | 15:59 | |
m3m0 | #startmeeting openstack-freezer 10-12-2015 | 16:00 |
openstack | Meeting started Thu Dec 10 16:00:55 2015 UTC and is due to finish in 60 minutes. The chair is m3m0. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
openstack | The meeting name has been set to 'openstack_freezer_10_12_2015' | 16:00 |
m3m0 | All: meetings notes available in real time at: https://etherpad.openstack.org/p/freezer_meetings | 16:01 |
daemontool | ok I'm sorry | 16:01 |
daemontool | sorry for the delay | 16:01 |
m3m0 | please raise your hand if you are here :) | 16:01 |
m3m0 | o/ | 16:01 |
daemontool | \o | 16:02 |
*** dschroeder has joined #openstack-freezer | 16:02 | |
*** zhonghua-lee has quit IRC | 16:02 | |
m3m0 | ok so far 2 :) the rest of the people are very busy around here | 16:03 |
m3m0 | daemontool, any news on the oslo logging? | 16:03 |
*** zhonghua-lee has joined #openstack-freezer | 16:03 | |
daemontool | emildi: reldan Slashme szaher frescof | 16:03 |
reldan | Here | 16:04 |
daemontool | m3m0: I can start | 16:04 |
m3m0 | cool :) go ahead | 16:05 |
daemontool | I think this can be approved https://review.openstack.org/#/c/252568/ (oslo) | 16:05 |
daemontool | szaher: did that, we need to do that also for the agent | 16:05 |
daemontool | after that is merged | 16:05 |
daemontool | we are going to merge | 16:05 |
daemontool | the parallel | 16:05 |
daemontool | https://review.openstack.org/#/c/247840/ | 16:06 |
daemontool | from reldan | 16:06 |
m3m0 | is that ready to merge? reldan? | 16:06 |
m3m0 | did you test it on windows as well? | 16:06 |
reldan | After this is merged, I probably need to rebase atop of oslo and change config | 16:06 |
daemontool | ok | 16:07 |
daemontool | after taht | 16:07 |
daemontool | from my side | 16:07 |
daemontool | I'm working on creating a new python-freezerclient repo | 16:07 |
daemontool | now | 16:07 |
daemontool | we need to define | 16:07 |
daemontool | what stepd | 16:07 |
daemontool | we need to take | 16:07 |
daemontool | for taht | 16:07 |
daemontool | because there's a proposal | 16:07 |
daemontool | can't find the review | 16:08 |
m3m0 | do you have a time for when the python-freezerclient will be ready? | 16:08 |
daemontool | to deprecate all the openstack clients | 16:08 |
daemontool | one sec | 16:08 |
daemontool | in favor | 16:09 |
daemontool | of python-openstackclient | 16:09 |
daemontool | so what do we do? | 16:09 |
*** szaher_ has quit IRC | 16:09 | |
daemontool | are we going to create a separate repo or are we going only to contribute to openstackclient? | 16:09 |
daemontool | I've received | 16:09 |
m3m0 | we need to figure it out if there are guidelines to integrate us in that repo | 16:09 |
daemontool | couple of feedback on this | 16:09 |
m3m0 | which is? | 16:09 |
daemontool | quite opposite | 16:09 |
daemontool | but both good | 16:10 |
daemontool | one was to go for our client independent | 16:10 |
daemontool | but the public proposal says otherwise | 16:10 |
daemontool | I think both make sense | 16:10 |
daemontool | but probably we do not want to maintain both | 16:10 |
daemontool | and go only for oen approach | 16:10 |
m3m0 | nope, and if the python-freezerclient will be deprecated there is no point to work on that | 16:11 |
daemontool | yes but we need to be sure about that | 16:11 |
daemontool | and.... | 16:11 |
daemontool | if we are going directly on openstackclient | 16:11 |
daemontool | we really need to do a planning job | 16:11 |
daemontool | now | 16:11 |
m3m0 | do you have a proposition for this planning? | 16:12 |
daemontool | all, any thoughts? | 16:12 |
daemontool | I have a blueprint | 16:12 |
daemontool | and a first commit | 16:12 |
daemontool | but needs to be extended | 16:12 |
m3m0 | could you send the link for both? | 16:13 |
daemontool | https://blueprints.launchpad.net/freezer/+spec/freezerclient | 16:13 |
daemontool | https://review.openstack.org/#/c/255349/ | 16:13 |
daemontool | and one sec | 16:14 |
daemontool | I'm trying to find | 16:14 |
daemontool | the public proposal | 16:14 |
daemontool | from AJaeger | 16:14 |
daemontool | here https://review.openstack.org/#/c/243348/ | 16:14 |
daemontool | also we need to create a freezer-specs | 16:15 |
daemontool | and fill it | 16:15 |
m3m0 | Jokke_ comment make a lot of sense | 16:16 |
daemontool | as usual :) | 16:16 |
daemontool | anyway | 16:18 |
daemontool | that's the thing | 16:18 |
m3m0 | so, should we wait to see what happens with that commit? | 16:18 |
daemontool | probably we need to wait there | 16:18 |
daemontool | yes | 16:18 |
daemontool | a part code reviews, and that two topics | 16:18 |
daemontool | that's all from me | 16:18 |
m3m0 | so, in the meantime we continue working with parallel backups and oslo logging | 16:18 |
daemontool | there's one disaster ecovery | 16:18 |
daemontool | yes | 16:18 |
daemontool | page I've found | 16:19 |
daemontool | I think we should align | 16:19 |
daemontool | one sec | 16:19 |
m3m0 | send it please | 16:19 |
jokke_ | reminder about the osc ... it still needs the freezer-pythonclient | 16:19 |
jokke_ | osc is just the clie wrapper from it | 16:19 |
daemontool | https://wiki.openstack.org/wiki/DisasterRecovery | 16:20 |
daemontool | jokke_: thanks | 16:20 |
daemontool | ok | 16:20 |
m3m0 | then lets move forward with the freezerclient | 16:20 |
daemontool | and also this if we want https://wiki.openstack.org/w/images/4/49/Openstack_disaster_recovery_-_openstack_meetup.pdf | 16:20 |
daemontool | ok | 16:20 |
m3m0 | ok, lots of material there, should we complement that info with freezer? | 16:22 |
daemontool | I think so | 16:24 |
m3m0 | do you want to do that? | 16:24 |
m3m0 | btw I'll be off the rest of the year so we need to find a temporary chairman :) | 16:25 |
daemontool | yes I think we can stop | 16:25 |
daemontool | the weekly meeting | 16:25 |
daemontool | the 17th | 16:25 |
daemontool | will be the last one? | 16:25 |
daemontool | and restart the 7th of Jan? | 16:26 |
m3m0 | ok sounds good but still someone needs to take care of this next week | 16:27 |
m3m0 | daemontool, reldan any plans for the tenant backup? | 16:27 |
daemontool | m3m0: good one, we need that | 16:27 |
daemontool | m3m0: please record on etherpad | 16:27 |
daemontool | also | 16:27 |
daemontool | thank you | 16:28 |
daemontool | m3m0: I'll do the chairman next week | 16:28 |
daemontool | where's Vanni? | 16:28 |
m3m0 | he's busy | 16:29 |
daemontool | ah ok | 16:29 |
daemontool | m3m0: I think now we can support that | 16:31 |
m3m0 | we can iterate over this: https://blueprints.launchpad.net/freezer/+spec/tenant-backup | 16:31 |
daemontool | can't remember now what was specifically needed | 16:31 |
daemontool | ah yes.... | 16:31 |
daemontool | sorry | 16:31 |
daemontool | got it | 16:31 |
daemontool | we need more time to think about it | 16:31 |
daemontool | but for sure we can proceed | 16:32 |
daemontool | using the othe rservice native apis | 16:32 |
daemontool | to get the information / dataat least from keystone, neutron, nova -> glance, cinder -> glance | 16:33 |
daemontool | etc | 16:33 |
daemontool | reldan: we'll discuss about this next week | 16:33 |
m3m0 | yes because working only on a file system level could be very very difficullt | 16:33 |
reldan | Sure, it is really complex task. As far as I know there are no one cloud provider (amazon, azure … ) with functionality like that | 16:33 |
m3m0 | we will be the first :) | 16:34 |
m3m0 | anything else to say on this topic? | 16:34 |
reldan | But it’s really should be well defined ) At least because we cannot make a copy of tenant (ID is alway unique) | 16:34 |
daemontool | reldan: that's one more good reason to do it :D | 16:34 |
daemontool | yes | 16:35 |
*** sputnik13 has joined #openstack-freezer | 16:36 | |
*** szaher_ has joined #openstack-freezer | 16:36 | |
m3m0 | do you have anything else to say today guys? | 16:39 |
daemontool | m3m0: you? | 16:40 |
daemontool | any news related to web ui or alike? | 16:40 |
daemontool | windows side all good? | 16:40 |
m3m0 | I've been very busy in another project this week | 16:40 |
daemontool | ok | 16:40 |
m3m0 | on the windows side there is an update that i would like to do to the scheduler to not need the user password to get installed | 16:41 |
daemontool | ok | 16:41 |
m3m0 | but I need to do more testing there | 16:41 |
daemontool | that's a good one | 16:41 |
m3m0 | so we can use this installer from cloud-init https://github.com/memogarcia/freezer-installer | 16:41 |
m3m0 | so when a windows vm gets deployed it already has freezer installed | 16:42 |
m3m0 | and maybe to register this automatically as well | 16:42 |
m3m0 | on the ui, I'm waiting for the parallel backups to implement the ui part of that | 16:42 |
m3m0 | but will be a big change on the ui | 16:43 |
daemontool | ok | 16:44 |
daemontool | m3m0: did we created a dedicated repo for that? | 16:44 |
daemontool | called openstack-freezer-utils? | 16:44 |
m3m0 | yes, but I haven't move the repos there | 16:44 |
m3m0 | I'll do that over the weekend | 16:44 |
m3m0 | and update the readmens | 16:45 |
daemontool | ah ok | 16:45 |
m3m0 | readmes* | 16:45 |
*** sputnik13 has quit IRC | 16:48 | |
m3m0 | that's pretty much all from my side | 16:48 |
daemontool | ok | 16:52 |
m3m0 | ok guys thanks to all for participate :) I know we are all very bussy | 16:56 |
m3m0 | #endmeeting | 16:56 |
openstack | Meeting ended Thu Dec 10 16:56:48 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:56 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_freezer_10_12_2015/2015/openstack_freezer_10_12_2015.2015-12-10-16.00.html | 16:56 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_freezer_10_12_2015/2015/openstack_freezer_10_12_2015.2015-12-10-16.00.txt | 16:56 |
openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_freezer_10_12_2015/2015/openstack_freezer_10_12_2015.2015-12-10-16.00.log.html | 16:56 |
*** fubi has joined #openstack-freezer | 17:10 | |
*** fubi has left #openstack-freezer | 17:10 | |
*** ig0r_ has joined #openstack-freezer | 17:11 | |
*** samuelBartel has quit IRC | 17:15 | |
daemontool | Slashme: ping | 17:30 |
*** daemontool has quit IRC | 17:35 | |
*** szaher_ has quit IRC | 18:00 | |
*** reldan has quit IRC | 18:04 | |
*** reldan has joined #openstack-freezer | 18:33 | |
*** reldan has quit IRC | 18:41 | |
*** reldan has joined #openstack-freezer | 18:42 | |
*** reldan has quit IRC | 18:43 | |
*** sputnik13 has joined #openstack-freezer | 19:20 | |
*** reldan has joined #openstack-freezer | 19:32 | |
*** memogarcia has joined #openstack-freezer | 19:54 | |
*** reldan has quit IRC | 20:09 | |
*** reldan has joined #openstack-freezer | 20:11 | |
*** reldan has quit IRC | 20:25 | |
*** reldan has joined #openstack-freezer | 20:25 | |
*** reldan has quit IRC | 20:28 | |
*** reldan has joined #openstack-freezer | 20:29 | |
*** zhonghua-lee has quit IRC | 20:36 | |
*** zhonghua-lee has joined #openstack-freezer | 20:36 | |
*** reldan_ has joined #openstack-freezer | 20:38 | |
*** reldan has quit IRC | 20:38 | |
*** reldan_ has quit IRC | 20:39 | |
*** reldan has joined #openstack-freezer | 20:40 | |
*** reldan has quit IRC | 20:53 | |
*** reldan has joined #openstack-freezer | 21:24 | |
*** reldan has quit IRC | 23:21 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!