Thursday, 2015-12-10

*** reldan has quit IRC00:30
*** reldan has joined #openstack-freezer00:44
*** memogarcia has quit IRC00:49
*** reldan has quit IRC01:17
openstackgerritsibaoli proposed openstack/freezer-web-ui: Fixes actions list can't be obtained when creating/editing jobs  https://review.openstack.org/25569807:18
*** openstackgerrit has quit IRC09:32
*** openstackgerrit has joined #openstack-freezer09:33
*** daemontool has joined #openstack-freezer09:37
daemontoolszaher:  https://review.openstack.org/#/c/252568/09:40
daemontoolsome minor chagne09:40
daemontoolchange09:41
daemontoolso we are completely breaking compatibility?09:41
*** memogarcia has joined #openstack-freezer09:55
*** memogarcia has quit IRC10:00
*** samuelBartel has joined #openstack-freezer10:08
*** reldan has joined #openstack-freezer10:11
*** vannif has joined #openstack-freezer10:18
daemontoolreldan:  vannif m3m0 Slashme  re https://review.openstack.org/#/c/252568/10:19
daemontoolis szaher there around?10:19
reldanYes, here10:19
daemontoolis https://review.openstack.org/#/c/252568/ breaking backwards compatibility with corrent options?10:20
daemontoolor are we going to support both and the old approach is deprecated?10:20
reldanDon’t know actually. He is speaking with Pierre10:20
daemontoolok10:20
reldanWhat about https://review.openstack.org/#/c/247840/ ?10:20
daemontoolreldan:  I'm reviewing it10:24
daemontooltoday we'll merge it10:24
reldanThank you10:24
daemontoolI think we need to find a way10:25
daemontoolto remove the version hardcoded10:25
daemontooland just use the vrsion number set in setup.cfg10:26
daemontoolreldan: what do you think10:28
daemontoolif we send in the oslo changes from szaher, and after that we merge the parallel with the same log approach?10:28
daemontoolso we make sure also the parallel backup works with that changes?10:29
reldandaemontool: 100% agree. I suppose we can сheck how it is implemented in nova or keystone10:29
daemontoolI think, probably that's what szaher  already checked10:29
reldandaemontool: Or accept parallel backup first10:29
reldanOtherwise I need to reimplement configuration file to oslo10:30
daemontoolreldan: I'm saying that10:30
daemontoolbecause for instance here https://review.openstack.org/#/c/247840/8/freezer/storage/multiple.py10:30
daemontoollike 1810:30
daemontooluses old logging approach10:30
daemontoolwhile after the szaher patch10:30
daemontoolwe should use config and log with oslo10:30
reldandaemontool: Yes, as well as config10:30
daemontoolreldan:  so I was wondering, as we need to do that anyway10:31
daemontoolwouldn't be better to do that now?10:31
daemontoolright after the oslo changes goes in?10:31
daemontoolI know you have to do changes, but I think it make sense10:31
reldanIn case of oslo changes goes before my changes, just my changes are waiting almost three weeks to be reviewed10:31
reldanYes, I will fix it10:32
daemontoolreldan:  so is that ok for you? or you want to send it in before the parallel?10:32
reldanI 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 etc10:34
reldanBut If you suppose that oslo goes first - I’m fine with that10:34
reldanI don’t think it is a big deal to replace log and config in my code to oslo10:34
daemontoolmy question is: if we send in the oslo config at anytime, does that break anything in the parallel code?10:35
daemontoolbreaking parallel is more critical I suppose...10:35
reldanYes, sure. I’m using old config, moving to oslo breaks parallel in this place10:36
reldanhttps://review.openstack.org/#/c/247840/8/freezer/config.py this code10:36
daemontoolreldan: excellent, good spot10:37
daemontoolszaher: you have few comments on your code10:37
daemontoolif you can do that changes asap, we can send the code in10:37
daemontoolthen reldan  you can rebase, we can do quick tests and send it in10:38
daemontoolsound? vannif Slashme you too?10:38
szaherdaemontool sorry I was checking that10:39
szaheractually there is no version file for freezer so I am going to create that10:39
szaherI 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 it10:39
daemontoolszaher: mmhhh....10:40
szaherwe have only one issue with backward compatibility which is -l option for passing the log file10:40
daemontool1 sec10:40
daemontoolI'm just seeign the other project does not have a version tag in setup.cfg10:42
daemontoolthey just uses tags on the git repo10:42
SlashmeWhat is the problem with the parralel backup change and oslo ? Saad's change for oslo only concerns the freezer-scheduler for now10:43
SlashmeNot the freezer-agent10:43
szaherdaemontool that how novaclient gets the version from pbr itself https://github.com/openstack/python-novaclient/blob/713b6f12e8ca3d4461b9dca12b71f899c53a7f23/novaclient/__init__.py10:46
szaherso I think we will use the same !10:46
szaheralso 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 app10:49
daemontoolSlashme: OK10:50
daemontoolszaher: perfect10:51
szaherOk, will that now ...10:52
szaherwill fix *10:53
Slashme/etc/freezer/scheduler.conf or /etc/freezer/freezer-scheduler.conf ?10:57
SlashmeOpinions ?10:57
daemontoolfreezer-scheduler.conf11:00
daemontoolso if someone with puppet or chef or ansible wants to put it on a different location11:00
daemontoolthe file can still be recognised11:00
SlashmeMakes sense :)11:00
Slashmeszaher: ^^11:01
daemontoolhere do you think we should create the feezer-specs repo?11:10
daemontools/feezer/freezer/11:11
daemontoolreldan: anyway, here https://review.openstack.org/#/c/247840/8 the code is really good11:11
reldandaemontool: Thank you11:12
reldanI can relocate imports, but changes to oslo.config should be after moving master to oslo.conf11:12
daemontoolreldan:  ok, I think it is a sensible way of doing it11:13
daemontoolI think we need a freezer-specs repo11:14
daemontoolbut we need to spend time on it11:17
daemontoolafter the python-freezerclient is in a reasonable shape, we can focus on that11:18
daemontoolI'll proceed on creating that repo after the creation and import of the python-freezerclient11:20
daemontoolrepo11:20
daemontoolalso, we need to integrate the freezerclient11:24
daemontoolwith openstack-client?11:24
daemontoolhttps://review.openstack.org/#/c/243348/11:24
daemontoolhttps://review.openstack.org/#/c/243348/2/specs/deprecate-cli.rst11:25
daemontoolso provavly we sould move directly to openstack client?11:25
daemontoolI'm asking that on #openstack-dev11:29
vannifI 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
vannifmaybe first define the options, the use cases ... and wait for enough people to agree on that11:36
daemontoolvannif:  well let's do that asap, as we need to move the freezerclient on a dedicated repo or onto openstack-client11:41
*** reldan has quit IRC11:42
*** emildi_ has joined #openstack-freezer11:48
*** sputnik13 has quit IRC11:57
*** reldan has joined #openstack-freezer11:59
*** vannif has quit IRC11:59
openstackgerritEldar Nugaev proposed openstack/freezer: Parallel backup  https://review.openstack.org/24784012:00
SlashmeWe should also start doing release notes (maybe using reno )12:02
daemontoolyes12:06
daemontool++12:06
*** emildi__ has joined #openstack-freezer12:08
*** emildi_ has quit IRC12:08
daemontoolehy can you read me?12:09
jokke_Slashme: reno is really good idea to go for right from the start12:13
jokke_no need to a) reinvent the wheel b) migrate to reno then later on12:13
*** emildi__ has quit IRC12:28
szaherdaemontool the setup.cfg for freezer is not updated. it has 1.2.0 .... https://github.com/openstack/freezer/blob/master/setup.cfg12:30
szaherSlashme12:30
openstackgerritSaad 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/25256812:41
*** daemontool has quit IRC12:44
*** openstackgerrit has quit IRC12:47
*** openstackgerrit has joined #openstack-freezer12:48
*** szaher_ has joined #openstack-freezer14:42
*** daemontool has joined #openstack-freezer14:46
daemontoolreldan: ping14:47
reldanYes, I’m here14:48
*** chenzeng has quit IRC14:49
*** chenzeng has joined #openstack-freezer14:49
szaher_Yes15:01
szaher_daemontool I did the patch and it's in the up stream now15:01
szaher_check plz15:01
szaher_Also -l option won't be available anymore because of oslo.log15:01
daemontoolmmhhh15:05
daemontoolszaher_:  ok15:05
daemontoolty15:05
daemontoolwell done btw :)15:05
szaher_Thanks :)15:06
*** memogarcia has joined #openstack-freezer15:20
*** memogarcia has quit IRC15:25
*** daemontool has quit IRC15:32
*** reldan has quit IRC15:48
*** reldan has joined #openstack-freezer15:55
m3m0hey guys who is ready for the weekly meeting?15:58
*** daemontool has joined #openstack-freezer15:59
m3m0#startmeeting openstack-freezer 10-12-201516:00
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'openstack_freezer_10_12_2015'16:00
m3m0All: meetings notes available in real time at: https://etherpad.openstack.org/p/freezer_meetings16:01
daemontoolok I'm sorry16:01
daemontoolsorry for the delay16:01
m3m0please raise your hand if you are here :)16:01
m3m0o/16:01
daemontool\o16:02
*** dschroeder has joined #openstack-freezer16:02
*** zhonghua-lee has quit IRC16:02
m3m0ok so far 2 :) the rest of the people are very busy around here16:03
m3m0daemontool, any news on the oslo logging?16:03
*** zhonghua-lee has joined #openstack-freezer16:03
daemontoolemildi: reldan  Slashme  szaher frescof16:03
reldanHere16:04
daemontoolm3m0:  I can start16:04
m3m0cool :) go ahead16:05
daemontoolI think this can be approved https://review.openstack.org/#/c/252568/ (oslo)16:05
daemontoolszaher:  did that, we need to do that also for the agent16:05
daemontoolafter that is merged16:05
daemontoolwe are going to merge16:05
daemontoolthe parallel16:05
daemontoolhttps://review.openstack.org/#/c/247840/16:06
daemontoolfrom reldan16:06
m3m0is that ready to merge? reldan?16:06
m3m0did you test it on windows as well?16:06
reldanAfter this is merged, I probably need to rebase atop of oslo and change config16:06
daemontoolok16:07
daemontoolafter taht16:07
daemontoolfrom my side16:07
daemontoolI'm working on creating a new python-freezerclient repo16:07
daemontoolnow16:07
daemontoolwe need to define16:07
daemontoolwhat stepd16:07
daemontoolwe need to take16:07
daemontoolfor taht16:07
daemontoolbecause there's a proposal16:07
daemontoolcan't find the review16:08
m3m0do you have a time for when the python-freezerclient will be ready?16:08
daemontoolto deprecate all the openstack clients16:08
daemontoolone sec16:08
daemontoolin favor16:09
daemontoolof python-openstackclient16:09
daemontoolso what do we do?16:09
*** szaher_ has quit IRC16:09
daemontoolare we going to create a separate repo or are we going only to contribute to openstackclient?16:09
daemontoolI've received16:09
m3m0we need to figure it out if there are guidelines to integrate us in that repo16:09
daemontoolcouple of feedback on this16:09
m3m0which is?16:09
daemontoolquite opposite16:09
daemontoolbut both good16:10
daemontoolone was to go for our client independent16:10
daemontoolbut the public proposal says otherwise16:10
daemontoolI think both make sense16:10
daemontoolbut probably we do not want to maintain both16:10
daemontooland go only for oen approach16:10
m3m0nope, and if the python-freezerclient will be deprecated there is no point to work on that16:11
daemontoolyes but we need to be sure about that16:11
daemontooland....16:11
daemontoolif we are going directly on openstackclient16:11
daemontoolwe really need to do a planning job16:11
daemontoolnow16:11
m3m0do you have a proposition for this planning?16:12
daemontoolall, any thoughts?16:12
daemontoolI have a blueprint16:12
daemontooland a first commit16:12
daemontoolbut needs to be extended16:12
m3m0could you send the link for both?16:13
daemontoolhttps://blueprints.launchpad.net/freezer/+spec/freezerclient16:13
daemontoolhttps://review.openstack.org/#/c/255349/16:13
daemontooland one sec16:14
daemontoolI'm trying to find16:14
daemontoolthe public proposal16:14
daemontoolfrom AJaeger16:14
daemontoolhere https://review.openstack.org/#/c/243348/16:14
daemontoolalso we need to create a freezer-specs16:15
daemontooland fill it16:15
m3m0Jokke_ comment make a lot of sense16:16
daemontoolas usual :)16:16
daemontoolanyway16:18
daemontoolthat's the thing16:18
m3m0so, should we wait to see what happens with that commit?16:18
daemontoolprobably we need to wait there16:18
daemontoolyes16:18
daemontoola part code reviews, and that two topics16:18
daemontoolthat's all from me16:18
m3m0so, in the meantime we continue working with parallel backups and oslo logging16:18
daemontoolthere's one disaster ecovery16:18
daemontoolyes16:18
daemontoolpage I've found16:19
daemontoolI think we should align16:19
daemontoolone sec16:19
m3m0send it please16:19
jokke_reminder about the osc ... it still needs the freezer-pythonclient16:19
jokke_osc is just the clie wrapper from it16:19
daemontoolhttps://wiki.openstack.org/wiki/DisasterRecovery16:20
daemontooljokke_:  thanks16:20
daemontoolok16:20
m3m0then lets move forward with the freezerclient16:20
daemontooland also this if we want https://wiki.openstack.org/w/images/4/49/Openstack_disaster_recovery_-_openstack_meetup.pdf16:20
daemontoolok16:20
m3m0ok, lots of material there, should we complement that info with freezer?16:22
daemontoolI think so16:24
m3m0do you want to do that?16:24
m3m0btw I'll be off the rest of the year so we need to find a temporary chairman :)16:25
daemontoolyes I think we can stop16:25
daemontoolthe weekly meeting16:25
daemontoolthe 17th16:25
daemontoolwill be the last one?16:25
daemontooland restart the 7th of Jan?16:26
m3m0ok sounds good but still someone needs to take care of this next week16:27
m3m0daemontool, reldan any plans for the tenant backup?16:27
daemontoolm3m0:  good one, we need that16:27
daemontoolm3m0:  please record on etherpad16:27
daemontoolalso16:27
daemontoolthank you16:28
daemontoolm3m0:  I'll do the chairman next week16:28
daemontoolwhere's Vanni?16:28
m3m0he's busy16:29
daemontoolah ok16:29
daemontoolm3m0: I think now we can support that16:31
m3m0we can iterate over this: https://blueprints.launchpad.net/freezer/+spec/tenant-backup16:31
daemontoolcan't remember now what was specifically needed16:31
daemontoolah yes....16:31
daemontoolsorry16:31
daemontoolgot it16:31
daemontoolwe need more time to think about it16:31
daemontoolbut for sure we can proceed16:32
daemontoolusing the othe rservice native apis16:32
daemontoolto get the information / dataat least from keystone, neutron, nova -> glance, cinder -> glance16:33
daemontooletc16:33
daemontoolreldan: we'll discuss about this next week16:33
m3m0yes because working only on a file system level could be very very difficullt16:33
reldanSure, it is really complex task. As far as I know there are no one cloud provider (amazon, azure … ) with functionality like that16:33
m3m0we will be the first :)16:34
m3m0anything else to say on this topic?16:34
reldanBut it’s really should be well defined ) At least because we cannot make a copy of tenant (ID is alway unique)16:34
daemontoolreldan:  that's one more good reason to do it :D16:34
daemontoolyes16:35
*** sputnik13 has joined #openstack-freezer16:36
*** szaher_ has joined #openstack-freezer16:36
m3m0do you have anything else to say today guys?16:39
daemontoolm3m0: you?16:40
daemontoolany news related to web ui or alike?16:40
daemontoolwindows side all good?16:40
m3m0I've been very busy in another project this week16:40
daemontoolok16:40
m3m0on the windows side there is an update that i would like to do to the scheduler to not need the user password to get installed16:41
daemontoolok16:41
m3m0but I need to do more testing there16:41
daemontoolthat's a good one16:41
m3m0so we can use this installer from cloud-init https://github.com/memogarcia/freezer-installer16:41
m3m0so when a windows vm gets deployed it already has freezer installed16:42
m3m0and maybe to register this automatically as well16:42
m3m0on the ui, I'm waiting for the parallel backups to implement the ui part of that16:42
m3m0but will be a big change on the ui16:43
daemontoolok16:44
daemontoolm3m0:  did we created a dedicated repo for that?16:44
daemontoolcalled openstack-freezer-utils?16:44
m3m0yes, but I haven't move the repos there16:44
m3m0I'll do that over the weekend16:44
m3m0and update the readmens16:45
daemontoolah ok16:45
m3m0readmes*16:45
*** sputnik13 has quit IRC16:48
m3m0that's pretty much all from my side16:48
daemontoolok16:52
m3m0ok guys thanks to all for participate :) I know we are all very bussy16:56
m3m0#endmeeting16:56
openstackMeeting ended Thu Dec 10 16:56:48 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_freezer_10_12_2015/2015/openstack_freezer_10_12_2015.2015-12-10-16.00.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_freezer_10_12_2015/2015/openstack_freezer_10_12_2015.2015-12-10-16.00.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_freezer_10_12_2015/2015/openstack_freezer_10_12_2015.2015-12-10-16.00.log.html16:56
*** fubi has joined #openstack-freezer17:10
*** fubi has left #openstack-freezer17:10
*** ig0r_ has joined #openstack-freezer17:11
*** samuelBartel has quit IRC17:15
daemontoolSlashme: ping17:30
*** daemontool has quit IRC17:35
*** szaher_ has quit IRC18:00
*** reldan has quit IRC18:04
*** reldan has joined #openstack-freezer18:33
*** reldan has quit IRC18:41
*** reldan has joined #openstack-freezer18:42
*** reldan has quit IRC18:43
*** sputnik13 has joined #openstack-freezer19:20
*** reldan has joined #openstack-freezer19:32
*** memogarcia has joined #openstack-freezer19:54
*** reldan has quit IRC20:09
*** reldan has joined #openstack-freezer20:11
*** reldan has quit IRC20:25
*** reldan has joined #openstack-freezer20:25
*** reldan has quit IRC20:28
*** reldan has joined #openstack-freezer20:29
*** zhonghua-lee has quit IRC20:36
*** zhonghua-lee has joined #openstack-freezer20:36
*** reldan_ has joined #openstack-freezer20:38
*** reldan has quit IRC20:38
*** reldan_ has quit IRC20:39
*** reldan has joined #openstack-freezer20:40
*** reldan has quit IRC20:53
*** reldan has joined #openstack-freezer21:24
*** reldan has quit IRC23:21

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!