Wednesday, 2016-03-09

*** yangyapeng has quit IRC00:05
*** dschroeder has quit IRC00:07
*** ddieterly[away] has quit IRC00:17
*** ddieterly has joined #openstack-freezer00:18
*** ddieterly has quit IRC00:19
zhangjnrun this script in devstack dir: . openrc admin admin00:32
*** yangyapeng has joined #openstack-freezer01:08
yangyapengddieterly01:10
*** ddieterly has joined #openstack-freezer01:25
*** daemontool has joined #openstack-freezer01:37
*** ddieterly is now known as ddieterly[away]02:20
*** yangyapeng has quit IRC02:44
*** ddieterly[away] has quit IRC03:20
*** EinstCrazy has joined #openstack-freezer04:57
*** EinstCrazy has quit IRC05:28
*** ferhat has joined #openstack-freezer07:20
*** ferhat has quit IRC07:29
*** yangyapeng has joined #openstack-freezer07:46
*** yangyapeng has quit IRC07:49
*** yangyapeng has joined #openstack-freezer07:49
*** yangyapeng has quit IRC08:06
*** yangyapeng has joined #openstack-freezer08:13
*** daemontool_ has joined #openstack-freezer08:47
*** openstackgerrit has quit IRC08:47
*** openstackgerrit has joined #openstack-freezer08:48
*** daemontool has quit IRC08:49
daemontool_morning08:58
m3m0mrning09:04
daemontool_tody source code walkthrough09:21
daemontool_scheduler09:21
daemontool_is Vanni around?09:21
m3m0yes he is but I think he's having breakfast09:33
daemontool_good, full belly, let's hope he doesn't fall asleep09:37
daemontool_lol09:37
daemontool_yangyapeng, zhangjn09:48
daemontool_so you cannot use youtube right?09:48
yangyapengThe network is a bit slow09:49
yangyapengdaemontool_:09:50
*** fabv has joined #openstack-freezer09:52
daemontool_yangyapeng,  would be better to use some other tool?09:52
yangyapengwe use webex,09:55
yangyapengping  zhangjn09:56
zhangjnI can get a webex link for us.09:56
yangyapeng:)09:56
zhangjnwhen?09:57
jith_hi all, hi all initially, I enabled devstack plugin in ubuntu and it works fine.. Later in debian, I installed freezer and freezer-api from source then  keystone...registered freezer in keystone... but elastic search is creating problem.. I installed elasticsearch from pip.. but couldnt find anymeans to start it09:57
jith_sorry  for the twice "hi all" :)09:58
yangyapengelasticsearch install shoud use shell . because it have a check. wait09:59
jith_yangyapeng: sure10:00
*** fabv has quit IRC10:01
daemontool_zhangjn, yes fabv has to do it10:02
daemontool_one sec10:05
jith_daemontool: i didnt complete the README.rst work... Once done, will notify you..10:05
daemontool_jith_,  it's all right :)10:06
daemontool_ty!10:06
yangyapengfunction download_elasticsearch {10:07
yangyapeng    if is_ubuntu; then10:07
yangyapeng        wget_elasticsearch elasticsearch-${ELASTICSEARCH_VERSION}.deb10:07
yangyapeng    elif is_fedora; then10:07
yangyapeng        wget_elasticsearch elasticsearch-${ELASTICSEARCH_VERSION}.noarch.rpm10:07
yangyapengping jith_10:07
yangyapengELASTICSEARCH_BASEURL=${ELASTICSEARCH_BASEURL:-https://download.elasticsearch.org/elasticsearch/elasticsearch}10:07
*** vannif has joined #openstack-freezer10:07
daemontool_m3m0, does this commit needs to be backported to liberty and kilo? https://review.openstack.org/#/c/255698/10:08
jith_yangyapeng: ok thanks a lot.. but it is nowhere in docs... In freezer-api, elasticsearch is already in requirements.txt.. so it will get installed through pip... so I should remove it first???10:09
daemontool_jith_,  I think that is the python client to talk with elastic search10:10
jith_daemontool: :)10:10
daemontool_not the elasticsearch server itself10:10
jith_daemontool: oh fine10:11
daemontool_that is needed by the api10:11
daemontool_to load data onto es10:11
daemontool_vannif,  is the main man there ^^10:11
jith_daemontool: oh ok thanks i got.. so the above function is already there in freezer-api?? or i have to execute manually??... yangyapeng10:13
vannifhi. just dropped in. what is the issue ?10:15
daemontool_m3m0, ah, the source code walkthru is tomorrow... not today...10:16
daemontool_right?10:16
m3m0daemontool, no, it doesnt have to10:17
m3m0aaa yeah you're right today is wednsday10:17
daemontool_we said it was every Thursday10:17
daemontool_ok10:17
daemontool_vannif, sorry, my mistake10:17
daemontool_is tomorrow10:17
daemontool_today is Wed, I apologize all10:17
zhangjnping daemontool, what's the time to code review. I can book a meeting room.10:18
*** reldan has joined #openstack-freezer10:18
vannifnp :)10:18
reldanI’m back10:18
zhangjntomorrow?10:19
daemontool_reldan,  hi :)10:19
vannifeveryday is a good day when you work on freezer ;D10:19
reldandaemontool_: Hi!10:19
*** daemontool_ is now known as daemontool10:19
zhangjnping daemontool10:19
daemontoolzhangjn,  yes10:19
daemontooltomorrow10:19
zhangjn what's the time to code review. I can book a meeting room?10:19
daemontoolevery Thursday10:19
daemontoolit's 1 hour before the weekly meeting10:20
daemontoolone sec10:20
zhangjngood10:20
reldanStill no code review for me? https://review.openstack.org/#/c/288416/10:20
zhangjnI will book a meeting room.10:20
zhangjnwe have a maillist?10:20
daemontoolzhangjn,  yes I'm looking for it10:21
daemontoolreldan,  yes, yesterday we had a conversation with the guys10:21
daemontooland they are releasing with liberty something10:21
daemontoolso the point was to see the backport effort for that to liberty10:21
daemontooland I did that10:21
daemontoolbut it looks like to be more complex than I thought10:22
daemontoolhttps://review.openstack.org/#/c/290047/10:22
reldandaemontool: Let’s update our liberty with master10:22
reldanjust rewrite current liberty branch10:22
reldanby master10:22
daemontoolmmhhh10:23
reldanbecause our master is liberty10:23
daemontoolin theory we should only backport bug fix and minor improvement10:23
daemontoolnot features10:23
reldaninstead of backporting - we just can have the same code10:23
daemontoolmmhhh I don't know10:23
reldandaemontool: Otherwise we cannot merge any significant change in master10:23
daemontoolyes, but we just do not backport it10:24
daemontoolonly bugs10:24
reldandaemontool: Otherwise we will get diversity between liberty and master10:24
daemontoolreldan,  that is gong to happen10:24
daemontoolanyway10:24
daemontoolit is supposed to happen10:24
daemontoolthe problem10:24
daemontoolis10:24
reldanSo I vote to rewrite our liberty my master10:24
reldanAnd don’t care much about kilo10:25
daemontoolkilo is the same10:25
daemontoolonly bugs10:25
reldanOtherwise we need like more people. And some of them just to backporting10:25
daemontoolI think we need to reduce the backporting10:26
daemontoolat bare minimum10:26
reldandaemontool: Probably if we have a very mature project like - 4-5 years, yes it may have sense10:26
reldandaemontool: In that case our code base is very big10:27
daemontoolwe need to stabilize at some point10:27
daemontoolsooner the better10:27
daemontoolwe are touching very little kilo10:27
daemontoolwe have to stop touching liberty10:27
daemontoolfix only bugs10:27
daemontooland focus on mitaka10:27
daemontooland Newton10:28
reldandaemontool: So I suppose we just should rewrite our liberty with master. If you think it is better to stop pushing big changes to master, let’s do it. But I suppose it is not the best decision.10:28
daemontoolslashme,  ping10:28
daemontoolI think we ahve to do only bug fix for now on10:28
slashmeAnyway, we won't be able to do any backports from newton to mitaka with all the refactoring that is going to happem10:28
daemontoolso this change is too big to go https://review.openstack.org/#/c/290047/10:28
daemontoolslashme, we can, but the bugporting will diverge10:29
slashmeYep10:29
daemontoolthis change is too big https://review.openstack.org/#/c/290047/10:29
daemontoolit require a lot of effor and time10:30
daemontoolyesterday it was all day10:30
daemontooland still10:30
reldandaemontool: Yes, agree. It is crazy10:30
daemontoolmy opinion is to backport only bugs10:31
daemontooland if we diverge in order to fix bugs10:31
daemontoolbecause the code base changed a lot10:31
daemontoolthen it will diverge10:31
daemontoolalso porting big change10:33
daemontooldestabilize a branch that should be stable in theory10:33
slashmeThe thing in itself is that this kind of big refactoring should not happen at the end of a release cycle. And we have a refactoring cycle ahead. We can merge it and not backport it, but it should not have been there in the first place.10:34
daemontoolm3m0,  I think this needs to be backported https://review.openstack.org/#/c/255698/10:34
daemontoolslashme, I'm not sure about that, because past releases10:35
m3m0the problem is that patch broke the ui10:35
daemontoolshouldn't affect new features delivery10:35
daemontoolfor new releases10:35
m3m0so there was a new patch that fix it10:35
daemontoolok10:35
m3m0and that patch should be backported10:35
m3m0let me find it10:35
daemontoolm3m0, ok, I think that is what that guy is looking for10:35
reldandaemontool: I agree. I don’t like idea with feature freezes.10:36
daemontoolI can ask to Doug10:36
daemontoolreldan,  well this week is the last week10:36
daemontoolto send code in10:36
daemontoolthen it freeze10:36
daemontool:)10:36
reldandaemontool: But is crazy :)10:37
reldanLet’s have stable branch10:37
daemontoolthe openstack tc asked to each service to do that10:37
reldanand let it be freezed10:37
reldannot master10:37
m3m0this is the one: https://review.openstack.org/#/c/256383/10:37
daemontoolwell10:37
m3m0daemontool ^^10:37
daemontoolcurrent stable10:37
daemontoolsorry10:37
daemontoolcurrent master will be stable very soon10:37
daemontooltagged as stable/mitaka10:37
daemontoolso it is good10:37
daemontoolbecause we can focus the next 2 weeks10:38
reldandaemontool: master is cannot be very stable :) It is master10:38
daemontoolon testing and stability10:38
reldanWe can have major testing and then tag - this version is stable10:38
daemontoolreldan,  yes we can do that10:38
daemontoolactually is what I have to do10:38
daemontooladd a tag10:38
daemontoolat some tpoing10:38
daemontoolpoint10:38
reldandaemontool: I like it10:38
daemontoolI was thinking10:39
daemontoolthat starting from Tuesday next week10:39
daemontoolwe all focus on tempest tests10:39
daemontoolincrease coverage10:39
daemontooland so on10:39
daemontoolfor at least 6-7 days10:39
daemontoolthen tag10:39
daemontooland after that moving forward to Newton in master10:39
daemontoolthat would be marked after the tag10:40
daemontoolfrom the tag onwards10:40
daemontoolslashme, what do you think?10:42
reldanI actually doubt that we should have liberty and kilo branches. We have no resources to support them properly10:43
daemontoolreldan,  that is just a point in time branch10:43
slashmereldan: we don't have the choice for your last point10:43
slashmedaemontool: yes, seems okay10:43
reldanyes we have, we always have choice10:43
daemontoolreldan, if we would stabilize our testing10:43
reldanwe can use tags10:43
daemontoolthe workload needed for bugs backporting10:44
daemontoolwould be lower10:44
daemontoolreldan, for the workload there's no much difference10:44
reldanyes, but I suppose that our stable/liberty is less stable than master10:44
daemontoolI don't know that10:44
daemontoolI think they both have the same level of unstability :10:44
reldanbecause we have a bunch of cherry-picks10:44
daemontoolstability10:45
daemontoolis a result of testing10:45
daemontoolmore than a branching strategy10:45
daemontoolthere is where we need to focus10:45
reldandaemontool: agree10:45
daemontoolbut I agree10:46
daemontoolwe have to deal with the current situation of a new project10:46
daemontoolwith lots of changes10:46
daemontoolfixing10:46
daemontoolbackporting10:46
daemontooland testing10:46
daemontoolthat's what we have right now10:46
reldandaemontool: I just remember 2010 and status of nova10:46
reldanno branching at that time10:46
reldanyes, we had austin10:46
reldanbut every one was using master10:47
reldanwhat the point to support austin if the projects changes every day so rapidly10:47
daemontoolI agree10:47
daemontoolin os a release become EOL after 2 cycles from its stable branching10:47
daemontoolso I think in our case10:48
daemontoolthat problem in 1 or 2 cycles from now10:48
daemontoolwill be mostly solved, if we focus on testing10:48
daemontoolonce the cycle is eol10:48
daemontoolthen no need to do anything anymore10:48
daemontoolso liberty (EOL: 2016-11-17)10:49
daemontoolkilo  (EOL: 2016-05-02)10:49
daemontoolso we abandon https://review.openstack.org/#/c/290047/ ?10:50
daemontoolapprove https://review.openstack.org/#/c/288416/ and move forward?10:50
daemontoolstarting from Tuesday next week everybody focus on testing until mitaka release, sounds?10:51
daemontoolmitaka RC110:51
daemontooluntil Mar 1810:52
daemontoolit would be Fri next week10:52
daemontooleven more10:52
daemontoolwe focus on testing10:52
daemontooluntil Fri 25th of March10:52
daemontoolso this week we merge in all our current review unless there's something really wrong10:53
slashmeThat's the issue, with HP's release being pretty much at the same date, everyone here will be focused on liberty bug-fixing10:53
daemontoolslashme, that's ok10:53
slashmeBut I agree with what you said10:54
slashmebecause we need to do a lot of stabilization on mitaka10:54
daemontoolok10:55
daemontoolty10:55
reldan10:56
reldandaemontool: I don’t believe in testing without refactoring :)10:56
reldandaemontool: Because otherwise it has no sense10:57
reldandaemontool: For me testing should show that our code works accordingly. So if our code is hard to test we should rewrite it10:57
daemontoolI agree11:13
daemontoolall let's move this forward and do the round of what needs to go in https://review.openstack.org/#/c/288416/11:14
daemontoolI need that change for the rsync stuff11:14
*** reldan has quit IRC11:15
slashmeDependancies in a cloudimage ubuntu for the freezer-agent install: libffi-dev python-dev libssl-dev11:27
daemontoolslashme, probably we need to add that in the README?11:27
slashmeYup, I'l do that later11:28
slashmejust wanted to write it somewhere in the meantime11:28
daemontoolok11:28
daemontoolfor the record... :)11:28
*** reldan has joined #openstack-freezer11:33
reldandaemontool: Thank you11:33
reldanguys +workflow please https://review.openstack.org/#/c/288416/11:33
reldanm3m0: :) https://review.openstack.org/#/c/288416/11:41
*** yangyapeng has quit IRC11:42
daemontoolreldan, regarding the branching, probably you could have a conversation with Doug12:13
daemontooltell him your concerns12:13
daemontooland solutions12:13
*** reldan has quit IRC12:13
daemontoolissues you see12:13
*** EinstCrazy has joined #openstack-freezer12:15
*** reldan has joined #openstack-freezer12:20
reldandaemontool: Who is Doug?12:20
daemontoolDoug Hellmann12:22
reldanslashme, daemontool: My point of view is very-very simple. I actually don’t want to break stability or everything like that. I just suppose that our master is not less stable than “stable”. It is all. So my proposel. 1) Fix some version of master. 2) Test it 3) Update liberty to this point12:22
daemontoolreldan,  yes but we cannot do that every time12:22
daemontoolwe need to find a method of work12:22
daemontoolthat is usable12:22
*** daemontool_ has joined #openstack-freezer12:24
*** daemontool has quit IRC12:27
*** daemontool_ is now known as daemontool12:29
*** reldan has quit IRC12:35
slashmeI agree with daemontool . Syncing mitaka and liberty could work as a one time thing. But it is not a viable long-term solution12:40
daemontoolok, please let's move forward https://review.openstack.org/#/c/288416/  the more we wait to sent the code in, mre work I have to do later on to merge that change with the rsync one12:52
openstackgerritFausto Marzi proposed openstack/freezer: WIP block based incremntal support - rsync  https://review.openstack.org/29046112:52
jith_daemontool: code to download elastic search server is not there in freezer-api or freezer??.. I could see the script "download_elasticsearch" in devstack only13:20
*** yangyapeng has joined #openstack-freezer13:20
daemontooljith_,  nope, because freezer could be installed within a private network13:21
daemontoolproxies13:21
daemontoolcompanies wouldn't allow to download software directly from the internet13:21
daemontooland other cases13:21
daemontoolthat would be difficult to manage13:21
daemontooljith_,  your current issue is "how to download and install elasticsearch" ?13:22
daemontooljith_,  you can download es from here https://www.elastic.co/downloads/past-releases13:23
daemontoollike wget https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.7.5.deb13:24
daemontoolor the versino you ened13:24
daemontools/ened/need/13:24
daemontoolis that what you need?13:25
*** ferhat has joined #openstack-freezer13:27
ferhatping to all13:27
*** reldan has joined #openstack-freezer13:29
ferhatping m3m013:31
daemontoolferhat, yes13:33
daemontoolI think we need a settings.py inside freezer/freezer and put there all the constants13:34
ferhatcurrently I am testing stable/1.2.013:34
m3m0ferhat: tell me13:35
ferhatwhen I try to create job from freezer ui which is stable/k,lo13:35
ferhatI am getting following error from freezer-api13:35
ferhatroot ERROR u'f1f2faa69d67424398ce8c18f1846f55_freezer01.novalocal' does not match '^[\\w-]+$'13:35
m3m0mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm13:35
m3m0I think the mappings are not updated13:36
m3m0but I've never seen that error13:36
m3m0did you create a job successfully at some point?13:36
ferhatI have tried from cli13:36
ferhatbut from web ui I could not13:37
ferhatbut if I use stable/kilo release for all api, client and web ui13:37
m3m0is this the name of the job? f1f2faa69d67424398ce8c18f1846f55_freezer01.novalocal13:37
ferhatthere is no problem13:37
m3m0what's the setup in which is failing?13:37
ferhatweb-ui: stable/kilo13:38
ferhatclient and api: stable/1.2.013:39
m3m0is there a reason to not working with stable/kilo in all dependencies?13:40
ferhatIf I install stable/kilo than I am getting error on admin jobs13:41
ferhatin all stable/kilo release installation. nova backup does not work.13:41
daemontoolferhat, use stable/kilo or stable/liberty13:42
m3m0only from the ui? or the cli as well?13:42
daemontoolI have to remove that tag13:42
ferhatfrom ui13:43
ferhatthat means I need to stick with stable/kilo release13:44
ferhatbecause I am using OpenStack kilo13:44
m3m0ok just to understand this:13:45
m3m0if you use all the components as stable/kilo it works13:45
m3m0but if you use stable/kilo for the ui and stable/1.2.0 for the api it fails right?13:45
m3m0daemontool for testr is there any extra step that I should be doing in tox?13:46
*** ddieterly has joined #openstack-freezer13:46
ferhatcorrect13:47
m3m0I'll need to set that env and see what is happening13:48
daemontooldo not use stable/1.2.013:48
daemontoolI'll remove that tag / branch soon13:48
daemontoolm3m0, like the steps needed to have testr working ?13:48
ferhatthat means I need to go back to stable/kilo13:49
daemontoolferhat,  or forward13:49
daemontoolto stable/liberty13:49
m3m0ferhat: preferably yes13:49
m3m0daemontool: yes, any other steps need it?13:49
ferhatfor OpenStack Kilo, can I user stable/liberty13:49
daemontoolferhat, if you use virtualenv, you can use the liberty agent13:50
m3m0daemontool I'm getting this error: ERROR: InvocationError: '/home/memo/src/python-freezerclient/.tox/py27/bin/python setup.py testr --coverage --testr-args='13:50
ferhatI see.13:50
daemontoolthere are many steps13:50
zhangjnPlease give me email to source code walkthrough.13:50
ferhatand I am having problem with logging in to https://wiki.openstack.org/wiki/Freezer.13:51
ferhatas soon as I resolve this problem.I will start updating documents.13:51
daemontoolm3m0,  where's the email you send to the openstck ml13:52
daemontoolcan't find it13:52
daemontoolre: source code walkthru13:52
ferhatalso is there anyway to downgrade the installation?13:52
daemontoolferhat, what problem are you having?13:52
daemontoolferhat, if you use virtualenv that is quite easy13:53
daemontoolif you installed freezer system wide13:53
daemontoolnope13:53
daemontooldeinstall old version, reinstall new version13:53
m3m0I send it to your gmail account13:53
daemontoolwhat was the subject?13:54
daemontoolok ty13:54
daemontoolgot it13:54
ferhatso you suggest me to install everything in virtual env so if I need to use other version, I can switch to it easily13:54
m3m0ferhat: I think is way better to follow that approach13:55
daemontoolzhangjn,  http://osdir.com/ml/openstack-dev/2016-02/msg01933.html and http://osdir.com/ml/openstack-dev/2016-02/msg02085.html13:55
m3m0so you don't mess with the dependencies13:55
ferhatok. will do that.13:55
daemontoolferhat,  in that way you'll manage13:55
daemontoolservices and components13:55
daemontoolwhere each one has its own13:55
daemontoolenvironment13:55
daemontoolwith its own dependencies13:55
daemontoolrather than having system wide shared dependencies13:56
daemontoolacross all modules and services13:56
ferhatsounds good.13:56
ferhatbut that does not apply to elasticsearch and web ui13:56
daemontoolweb ui yes13:57
daemontoolelasticsearch not because is not a python module13:57
ferhatok. this was a really important information.13:58
ferhatI should doument it :D13:58
ferhatfor wiki page. I have never able to login with OpenID13:58
daemontoolferhat, yes thanks13:58
daemontoolso create an account there13:58
daemontooldo you have an account in launchpad?13:58
daemontoolcreate an account in launchpad13:59
daemontooland use the same account to login in the wiki13:59
m3m0help :) http://paste.openstack.org/show/489844/13:59
ferhatI have. and I have given proper permission from launchpad13:59
ferhatthan I return to wiki. on that page I see Login / create and accoun with OpenID14:00
ferhatI click on it. nothing happens.14:00
daemontoolferhat,  clore the browser and repopen it14:00
daemontoolor start a private browing tab with firefox14:00
daemontools/clore/close/14:00
zhangjnping daemontool14:01
daemontoolzhangjn, yes14:01
zhangjnmeeting num:513 551 64814:01
zhangjnMeeting Link: https://demo.webex.com.cn/demo/j.php?MTID=m72caa0d20f548aad76ab427a97d2e07f14:01
zhangjnMeeting Password: freezer14:01
daemontoolvannif, ^^ , also we need to send an email14:01
daemontoolto the ml14:01
daemontoolwith that information14:01
daemontoolexplaning that we are not using hangout because there are issues from users connecting from some geographic areas14:02
zhangjnI have not subscription the maillist, please resend meeting info by email.14:03
zhangjnthx daemontool14:03
*** daemontool_ has joined #openstack-freezer14:03
*** ddieterly has quit IRC14:04
m3m0I'm supposed to be doing something but I don't remember what14:07
*** daemontool has quit IRC14:07
daemontool_m3m0,  testr14:08
daemontool__14:08
daemontool_?14:08
m3m0hahaha I think it was something more dangerous14:09
openstackgerritEldar Nugaev proposed openstack/freezer: Broken level for incremental backups  https://review.openstack.org/29051714:11
reldanslashme, daemontool, vannif, m3m0. Guys, here is the fix for level https://review.openstack.org/290517 , here is may refactoring  https://review.openstack.org/#/c/288416/14:15
jith_ daemontool: yes thanks.. freezer api will work without elasticsearch??14:15
reldanAnd I’m going to start to work on mistral project for a while14:15
jith_daemontool: i got an error when i give freezer-db-init14:17
jith_"ERROR HTTPConnectionPool(host='localhost', port=9200): Max retries exceeded with url: /freezer (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f12c8870950>: Failed to establish a new connection: [Errno 111] Connection refused',)):14:17
jith_elasticsearch is giving problem... thats y worried14:17
zhangjnping daemontool, I have updated the Meeting info in the etherpad.14:19
daemontool_zhangjn,  ok14:19
daemontool_ty14:19
zhangjnYou'd better resend by maillist, :)14:19
daemontool_zhangjn, m3m0  is the chairman14:20
yangyapengping jith_  kill  establish and restart is ok?14:26
daemontool_reldan, before movign to mistral can you please finish the bp on the metadata so zhangjn yangyapeng  can start work on it?14:30
reldandaemontool_: Yes, I can invest some time. But I am not sure that they will be able to start immediatelly. Because I suppose there will be a lot of discussions about it.14:33
*** ddieterly has joined #openstack-freezer14:33
zhangjnwe have something to learn about this project.14:35
zhangjnwe are trying to do someting.14:36
daemontool_reldan, I think we have to start with something14:37
reldanyes, sure14:38
m3m0zhangjn: do you have anything in mind?14:38
daemontool_reldan,  the rsync stuff I'm working on is here freezer/storage/swift.py14:44
daemontool_everything is work in progress14:44
reldandaemontool_: Not quite understand should it be engine?14:44
daemontool_incremental_engine14:45
daemontool_but we can change the name14:45
daemontool_at anytime14:45
daemontool_an sorry14:45
daemontool_here https://review.openstack.org/#/c/290461/14:45
reldandaemontool_: Looks cool! :)14:47
daemontool_reldan,  here https://review.openstack.org/#/c/290461/2/freezer/main.py line 9514:48
daemontool_I think that could be abstracted14:48
daemontool_but for now14:49
daemontool_it's ok14:49
daemontool_now I can work14:49
daemontool_on the rsync code itself14:49
daemontool_and move forward14:49
reldandaemontool_: I would prefer to different implementation than one with if-s14:49
daemontool_reldan,  that's what I'm referring to14:49
reldanprobably we can find a lot of common code and extract it to abstract, yes14:50
daemontool_we can remove that ifs14:50
daemontool_those if14:50
reldanbecause previously I had only one implementation and was unable to see common parts14:50
daemontool_now that code is unusable yet14:50
daemontool_as I need to place the queue and pipes part14:50
daemontool_out14:50
*** ddieterly is now known as ddieterly[away]15:18
openstackgerritMerged openstack/freezer: Broken level for incremental backups  https://review.openstack.org/29051715:37
openstackgerritFabrizio Vanni proposed openstack/freezer: list backups stored in API  https://review.openstack.org/27735215:43
*** ddieterly[away] is now known as ddieterly15:47
openstackgerritFabrizio Vanni proposed openstack/freezer-api: add database status check  https://review.openstack.org/28993115:52
*** EinstCrazy has quit IRC15:56
ferhatI have installed freezer-web-ui with virtual env16:09
ferhatbut getting ImportError: No module named disaster_recovery16:09
daemontool_ferhat how did you install?16:20
daemontool_virtualenv freezer-web-ui-env-116:20
ferhatI have installed virtualenv wtih pip first16:20
daemontool_git clone .....16:20
daemontool_source freezer-web-ui-env-1/bin/activate16:20
daemontool_cd freezer-web-ui16:20
daemontool_pip install -e ./16:21
ferhatooo16:21
ferhatyes I have created new virtual env called freezer-liberty16:23
ferhatthan source freezer-liberty/bin/activate16:23
ferhatthan I have installed freezer, freezer-api and freezer-web-ui16:23
daemontool_with pip install -e ./16:27
daemontool_on each directory?16:27
daemontool_you-ll be sure all the deps are installed16:27
ferhatnot actually16:29
ferhatI have used pip install -r requirement.txt16:29
daemontool_ok16:29
daemontool_so what is the issue you are currently having?16:30
ferhatI am getting ImportError: No module named disaster_recovery16:30
ferhatit is only for web-ui16:30
ferhatfreezer-api and clients works like charm16:30
m3m0that should be installed in the same virtualenv as horizon16:31
ferhatthat was the problem.16:33
ferhatat the end. I must use stable/kilo release for OpenStack kilo16:33
ferhatit is confirmed16:33
daemontool_ferhat, for web ui and api for sure yes16:35
ferhatthis will go to documentation :D16:35
daemontool_ok :)16:36
ferhatunfortunatly, wiki.openstack.org OpenID intergation is broken16:42
ferhatI am not able to login16:42
daemontool_ferhat, can you ask on #openstack-infra some clarification about that?16:43
daemontool_brb16:44
daemontool_10 min break16:44
ferhatok16:44
ferhatwill ask them16:44
openstackgerritOpenStack Proposal Bot proposed openstack/freezer: Updated from global requirements  https://review.openstack.org/28869716:46
*** EinstCrazy has joined #openstack-freezer16:56
slashmeBug_fix for metadata level16:59
slashmeLiberty: https://review.openstack.org/29068416:59
slashmekilo: https://review.openstack.org/29068616:59
*** EinstCrazy has quit IRC17:03
*** daemontool has joined #openstack-freezer17:05
*** daemontool_ has quit IRC17:07
*** daemontool_ has joined #openstack-freezer17:23
*** daemontool has quit IRC17:23
*** clenimar has joined #openstack-freezer17:24
*** ddieterly is now known as ddieterly[away]17:25
*** ddieterly[away] is now known as ddieterly17:28
*** reldan has quit IRC17:36
*** reldan has joined #openstack-freezer17:36
openstackgerritJonas Pfannschmidt proposed openstack/freezer-api: Use six.moves.input rather than six.moves.builtin.input  https://review.openstack.org/29073218:02
*** reldan has quit IRC18:10
*** daemontool__ has joined #openstack-freezer18:10
*** daemontool_ has quit IRC18:13
*** daemontool__ has quit IRC18:16
*** jonaspf has joined #openstack-freezer18:25
*** ddieterly is now known as ddieterly[away]18:43
*** ddieterly[away] has quit IRC19:44
openstackgerritDeklan Dieterly proposed openstack/freezer-api: Add gate hooks  https://review.openstack.org/29081419:52
openstackgerritDeklan Dieterly proposed openstack/freezer-api: Add gate hooks  https://review.openstack.org/29081419:54
openstackgerritDeklan Dieterly proposed openstack/freezer-api: Add gate hooks  https://review.openstack.org/29081419:59
*** yangyape_ has joined #openstack-freezer20:08
*** yangyapeng has quit IRC20:09
*** daemontool has joined #openstack-freezer20:14
*** reldan has joined #openstack-freezer20:25
openstackgerritDeklan Dieterly proposed openstack/freezer-api: Add Freezer API Version Test  https://review.openstack.org/29084220:47
*** ddieterly has joined #openstack-freezer22:16

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