*** yangyapeng has quit IRC | 00:05 | |
*** dschroeder has quit IRC | 00:07 | |
*** ddieterly[away] has quit IRC | 00:17 | |
*** ddieterly has joined #openstack-freezer | 00:18 | |
*** ddieterly has quit IRC | 00:19 | |
zhangjn | run this script in devstack dir: . openrc admin admin | 00:32 |
---|---|---|
*** yangyapeng has joined #openstack-freezer | 01:08 | |
yangyapeng | ddieterly | 01:10 |
*** ddieterly has joined #openstack-freezer | 01:25 | |
*** daemontool has joined #openstack-freezer | 01:37 | |
*** ddieterly is now known as ddieterly[away] | 02:20 | |
*** yangyapeng has quit IRC | 02:44 | |
*** ddieterly[away] has quit IRC | 03:20 | |
*** EinstCrazy has joined #openstack-freezer | 04:57 | |
*** EinstCrazy has quit IRC | 05:28 | |
*** ferhat has joined #openstack-freezer | 07:20 | |
*** ferhat has quit IRC | 07:29 | |
*** yangyapeng has joined #openstack-freezer | 07:46 | |
*** yangyapeng has quit IRC | 07:49 | |
*** yangyapeng has joined #openstack-freezer | 07:49 | |
*** yangyapeng has quit IRC | 08:06 | |
*** yangyapeng has joined #openstack-freezer | 08:13 | |
*** daemontool_ has joined #openstack-freezer | 08:47 | |
*** openstackgerrit has quit IRC | 08:47 | |
*** openstackgerrit has joined #openstack-freezer | 08:48 | |
*** daemontool has quit IRC | 08:49 | |
daemontool_ | morning | 08:58 |
m3m0 | mrning | 09:04 |
daemontool_ | tody source code walkthrough | 09:21 |
daemontool_ | scheduler | 09:21 |
daemontool_ | is Vanni around? | 09:21 |
m3m0 | yes he is but I think he's having breakfast | 09:33 |
daemontool_ | good, full belly, let's hope he doesn't fall asleep | 09:37 |
daemontool_ | lol | 09:37 |
daemontool_ | yangyapeng, zhangjn | 09:48 |
daemontool_ | so you cannot use youtube right? | 09:48 |
yangyapeng | The network is a bit slow | 09:49 |
yangyapeng | daemontool_: | 09:50 |
*** fabv has joined #openstack-freezer | 09:52 | |
daemontool_ | yangyapeng, would be better to use some other tool? | 09:52 |
yangyapeng | we use webex, | 09:55 |
yangyapeng | ping zhangjn | 09:56 |
zhangjn | I can get a webex link for us. | 09:56 |
yangyapeng | :) | 09:56 |
zhangjn | when? | 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 it | 09:57 |
jith_ | sorry for the twice "hi all" :) | 09:58 |
yangyapeng | elasticsearch install shoud use shell . because it have a check. wait | 09:59 |
jith_ | yangyapeng: sure | 10:00 |
*** fabv has quit IRC | 10:01 | |
daemontool_ | zhangjn, yes fabv has to do it | 10:02 |
daemontool_ | one sec | 10: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 |
yangyapeng | function download_elasticsearch { | 10:07 |
yangyapeng | if is_ubuntu; then | 10:07 |
yangyapeng | wget_elasticsearch elasticsearch-${ELASTICSEARCH_VERSION}.deb | 10:07 |
yangyapeng | elif is_fedora; then | 10:07 |
yangyapeng | wget_elasticsearch elasticsearch-${ELASTICSEARCH_VERSION}.noarch.rpm | 10:07 |
yangyapeng | ping jith_ | 10:07 |
yangyapeng | ELASTICSEARCH_BASEURL=${ELASTICSEARCH_BASEURL:-https://download.elasticsearch.org/elasticsearch/elasticsearch} | 10:07 |
*** vannif has joined #openstack-freezer | 10: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 search | 10:10 |
jith_ | daemontool: :) | 10:10 |
daemontool_ | not the elasticsearch server itself | 10:10 |
jith_ | daemontool: oh fine | 10:11 |
daemontool_ | that is needed by the api | 10:11 |
daemontool_ | to load data onto es | 10: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??... yangyapeng | 10:13 |
vannif | hi. 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 |
m3m0 | daemontool, no, it doesnt have to | 10:17 |
m3m0 | aaa yeah you're right today is wednsday | 10:17 |
daemontool_ | we said it was every Thursday | 10:17 |
daemontool_ | ok | 10:17 |
daemontool_ | vannif, sorry, my mistake | 10:17 |
daemontool_ | is tomorrow | 10:17 |
daemontool_ | today is Wed, I apologize all | 10:17 |
zhangjn | ping daemontool, what's the time to code review. I can book a meeting room. | 10:18 |
*** reldan has joined #openstack-freezer | 10:18 | |
vannif | np :) | 10:18 |
reldan | I’m back | 10:18 |
zhangjn | tomorrow? | 10:19 |
daemontool_ | reldan, hi :) | 10:19 |
vannif | everyday is a good day when you work on freezer ;D | 10:19 |
reldan | daemontool_: Hi! | 10:19 |
*** daemontool_ is now known as daemontool | 10:19 | |
zhangjn | ping daemontool | 10:19 |
daemontool | zhangjn, yes | 10:19 |
daemontool | tomorrow | 10:19 |
zhangjn | what's the time to code review. I can book a meeting room? | 10:19 |
daemontool | every Thursday | 10:19 |
daemontool | it's 1 hour before the weekly meeting | 10:20 |
daemontool | one sec | 10:20 |
zhangjn | good | 10:20 |
reldan | Still no code review for me? https://review.openstack.org/#/c/288416/ | 10:20 |
zhangjn | I will book a meeting room. | 10:20 |
zhangjn | we have a maillist? | 10:20 |
daemontool | zhangjn, yes I'm looking for it | 10:21 |
daemontool | reldan, yes, yesterday we had a conversation with the guys | 10:21 |
daemontool | and they are releasing with liberty something | 10:21 |
daemontool | so the point was to see the backport effort for that to liberty | 10:21 |
daemontool | and I did that | 10:21 |
daemontool | but it looks like to be more complex than I thought | 10:22 |
daemontool | https://review.openstack.org/#/c/290047/ | 10:22 |
reldan | daemontool: Let’s update our liberty with master | 10:22 |
reldan | just rewrite current liberty branch | 10:22 |
reldan | by master | 10:22 |
daemontool | mmhhh | 10:23 |
reldan | because our master is liberty | 10:23 |
daemontool | in theory we should only backport bug fix and minor improvement | 10:23 |
daemontool | not features | 10:23 |
reldan | instead of backporting - we just can have the same code | 10:23 |
daemontool | mmhhh I don't know | 10:23 |
reldan | daemontool: Otherwise we cannot merge any significant change in master | 10:23 |
daemontool | yes, but we just do not backport it | 10:24 |
daemontool | only bugs | 10:24 |
reldan | daemontool: Otherwise we will get diversity between liberty and master | 10:24 |
daemontool | reldan, that is gong to happen | 10:24 |
daemontool | anyway | 10:24 |
daemontool | it is supposed to happen | 10:24 |
daemontool | the problem | 10:24 |
daemontool | is | 10:24 |
reldan | So I vote to rewrite our liberty my master | 10:24 |
reldan | And don’t care much about kilo | 10:25 |
daemontool | kilo is the same | 10:25 |
daemontool | only bugs | 10:25 |
reldan | Otherwise we need like more people. And some of them just to backporting | 10:25 |
daemontool | I think we need to reduce the backporting | 10:26 |
daemontool | at bare minimum | 10:26 |
reldan | daemontool: Probably if we have a very mature project like - 4-5 years, yes it may have sense | 10:26 |
reldan | daemontool: In that case our code base is very big | 10:27 |
daemontool | we need to stabilize at some point | 10:27 |
daemontool | sooner the better | 10:27 |
daemontool | we are touching very little kilo | 10:27 |
daemontool | we have to stop touching liberty | 10:27 |
daemontool | fix only bugs | 10:27 |
daemontool | and focus on mitaka | 10:27 |
daemontool | and Newton | 10:28 |
reldan | daemontool: 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 |
daemontool | slashme, ping | 10:28 |
daemontool | I think we ahve to do only bug fix for now on | 10:28 |
slashme | Anyway, we won't be able to do any backports from newton to mitaka with all the refactoring that is going to happem | 10:28 |
daemontool | so this change is too big to go https://review.openstack.org/#/c/290047/ | 10:28 |
daemontool | slashme, we can, but the bugporting will diverge | 10:29 |
slashme | Yep | 10:29 |
daemontool | this change is too big https://review.openstack.org/#/c/290047/ | 10:29 |
daemontool | it require a lot of effor and time | 10:30 |
daemontool | yesterday it was all day | 10:30 |
daemontool | and still | 10:30 |
reldan | daemontool: Yes, agree. It is crazy | 10:30 |
daemontool | my opinion is to backport only bugs | 10:31 |
daemontool | and if we diverge in order to fix bugs | 10:31 |
daemontool | because the code base changed a lot | 10:31 |
daemontool | then it will diverge | 10:31 |
daemontool | also porting big change | 10:33 |
daemontool | destabilize a branch that should be stable in theory | 10:33 |
slashme | The 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 |
daemontool | m3m0, I think this needs to be backported https://review.openstack.org/#/c/255698/ | 10:34 |
daemontool | slashme, I'm not sure about that, because past releases | 10:35 |
m3m0 | the problem is that patch broke the ui | 10:35 |
daemontool | shouldn't affect new features delivery | 10:35 |
daemontool | for new releases | 10:35 |
m3m0 | so there was a new patch that fix it | 10:35 |
daemontool | ok | 10:35 |
m3m0 | and that patch should be backported | 10:35 |
m3m0 | let me find it | 10:35 |
daemontool | m3m0, ok, I think that is what that guy is looking for | 10:35 |
reldan | daemontool: I agree. I don’t like idea with feature freezes. | 10:36 |
daemontool | I can ask to Doug | 10:36 |
daemontool | reldan, well this week is the last week | 10:36 |
daemontool | to send code in | 10:36 |
daemontool | then it freeze | 10:36 |
daemontool | :) | 10:36 |
reldan | daemontool: But is crazy :) | 10:37 |
reldan | Let’s have stable branch | 10:37 |
daemontool | the openstack tc asked to each service to do that | 10:37 |
reldan | and let it be freezed | 10:37 |
reldan | not master | 10:37 |
m3m0 | this is the one: https://review.openstack.org/#/c/256383/ | 10:37 |
daemontool | well | 10:37 |
m3m0 | daemontool ^^ | 10:37 |
daemontool | current stable | 10:37 |
daemontool | sorry | 10:37 |
daemontool | current master will be stable very soon | 10:37 |
daemontool | tagged as stable/mitaka | 10:37 |
daemontool | so it is good | 10:37 |
daemontool | because we can focus the next 2 weeks | 10:38 |
reldan | daemontool: master is cannot be very stable :) It is master | 10:38 |
daemontool | on testing and stability | 10:38 |
reldan | We can have major testing and then tag - this version is stable | 10:38 |
daemontool | reldan, yes we can do that | 10:38 |
daemontool | actually is what I have to do | 10:38 |
daemontool | add a tag | 10:38 |
daemontool | at some tpoing | 10:38 |
daemontool | point | 10:38 |
reldan | daemontool: I like it | 10:38 |
daemontool | I was thinking | 10:39 |
daemontool | that starting from Tuesday next week | 10:39 |
daemontool | we all focus on tempest tests | 10:39 |
daemontool | increase coverage | 10:39 |
daemontool | and so on | 10:39 |
daemontool | for at least 6-7 days | 10:39 |
daemontool | then tag | 10:39 |
daemontool | and after that moving forward to Newton in master | 10:39 |
daemontool | that would be marked after the tag | 10:40 |
daemontool | from the tag onwards | 10:40 |
daemontool | slashme, what do you think? | 10:42 |
reldan | I actually doubt that we should have liberty and kilo branches. We have no resources to support them properly | 10:43 |
daemontool | reldan, that is just a point in time branch | 10:43 |
slashme | reldan: we don't have the choice for your last point | 10:43 |
slashme | daemontool: yes, seems okay | 10:43 |
reldan | yes we have, we always have choice | 10:43 |
daemontool | reldan, if we would stabilize our testing | 10:43 |
reldan | we can use tags | 10:43 |
daemontool | the workload needed for bugs backporting | 10:44 |
daemontool | would be lower | 10:44 |
daemontool | reldan, for the workload there's no much difference | 10:44 |
reldan | yes, but I suppose that our stable/liberty is less stable than master | 10:44 |
daemontool | I don't know that | 10:44 |
daemontool | I think they both have the same level of unstability : | 10:44 |
reldan | because we have a bunch of cherry-picks | 10:44 |
daemontool | stability | 10:45 |
daemontool | is a result of testing | 10:45 |
daemontool | more than a branching strategy | 10:45 |
daemontool | there is where we need to focus | 10:45 |
reldan | daemontool: agree | 10:45 |
daemontool | but I agree | 10:46 |
daemontool | we have to deal with the current situation of a new project | 10:46 |
daemontool | with lots of changes | 10:46 |
daemontool | fixing | 10:46 |
daemontool | backporting | 10:46 |
daemontool | and testing | 10:46 |
daemontool | that's what we have right now | 10:46 |
reldan | daemontool: I just remember 2010 and status of nova | 10:46 |
reldan | no branching at that time | 10:46 |
reldan | yes, we had austin | 10:46 |
reldan | but every one was using master | 10:47 |
reldan | what the point to support austin if the projects changes every day so rapidly | 10:47 |
daemontool | I agree | 10:47 |
daemontool | in os a release become EOL after 2 cycles from its stable branching | 10:47 |
daemontool | so I think in our case | 10:48 |
daemontool | that problem in 1 or 2 cycles from now | 10:48 |
daemontool | will be mostly solved, if we focus on testing | 10:48 |
daemontool | once the cycle is eol | 10:48 |
daemontool | then no need to do anything anymore | 10:48 |
daemontool | so liberty (EOL: 2016-11-17) | 10:49 |
daemontool | kilo (EOL: 2016-05-02) | 10:49 |
daemontool | so we abandon https://review.openstack.org/#/c/290047/ ? | 10:50 |
daemontool | approve https://review.openstack.org/#/c/288416/ and move forward? | 10:50 |
daemontool | starting from Tuesday next week everybody focus on testing until mitaka release, sounds? | 10:51 |
daemontool | mitaka RC1 | 10:51 |
daemontool | until Mar 18 | 10:52 |
daemontool | it would be Fri next week | 10:52 |
daemontool | even more | 10:52 |
daemontool | we focus on testing | 10:52 |
daemontool | until Fri 25th of March | 10:52 |
daemontool | so this week we merge in all our current review unless there's something really wrong | 10:53 |
slashme | That's the issue, with HP's release being pretty much at the same date, everyone here will be focused on liberty bug-fixing | 10:53 |
daemontool | slashme, that's ok | 10:53 |
slashme | But I agree with what you said | 10:54 |
slashme | because we need to do a lot of stabilization on mitaka | 10:54 |
daemontool | ok | 10:55 |
daemontool | ty | 10:55 |
reldan | 10:56 | |
reldan | daemontool: I don’t believe in testing without refactoring :) | 10:56 |
reldan | daemontool: Because otherwise it has no sense | 10:57 |
reldan | daemontool: For me testing should show that our code works accordingly. So if our code is hard to test we should rewrite it | 10:57 |
daemontool | I agree | 11:13 |
daemontool | all let's move this forward and do the round of what needs to go in https://review.openstack.org/#/c/288416/ | 11:14 |
daemontool | I need that change for the rsync stuff | 11:14 |
*** reldan has quit IRC | 11:15 | |
slashme | Dependancies in a cloudimage ubuntu for the freezer-agent install: libffi-dev python-dev libssl-dev | 11:27 |
daemontool | slashme, probably we need to add that in the README? | 11:27 |
slashme | Yup, I'l do that later | 11:28 |
slashme | just wanted to write it somewhere in the meantime | 11:28 |
daemontool | ok | 11:28 |
daemontool | for the record... :) | 11:28 |
*** reldan has joined #openstack-freezer | 11:33 | |
reldan | daemontool: Thank you | 11:33 |
reldan | guys +workflow please https://review.openstack.org/#/c/288416/ | 11:33 |
reldan | m3m0: :) https://review.openstack.org/#/c/288416/ | 11:41 |
*** yangyapeng has quit IRC | 11:42 | |
daemontool | reldan, regarding the branching, probably you could have a conversation with Doug | 12:13 |
daemontool | tell him your concerns | 12:13 |
daemontool | and solutions | 12:13 |
*** reldan has quit IRC | 12:13 | |
daemontool | issues you see | 12:13 |
*** EinstCrazy has joined #openstack-freezer | 12:15 | |
*** reldan has joined #openstack-freezer | 12:20 | |
reldan | daemontool: Who is Doug? | 12:20 |
daemontool | Doug Hellmann | 12:22 |
reldan | slashme, 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 point | 12:22 |
daemontool | reldan, yes but we cannot do that every time | 12:22 |
daemontool | we need to find a method of work | 12:22 |
daemontool | that is usable | 12:22 |
*** daemontool_ has joined #openstack-freezer | 12:24 | |
*** daemontool has quit IRC | 12:27 | |
*** daemontool_ is now known as daemontool | 12:29 | |
*** reldan has quit IRC | 12:35 | |
slashme | I agree with daemontool . Syncing mitaka and liberty could work as a one time thing. But it is not a viable long-term solution | 12:40 |
daemontool | ok, 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 one | 12:52 |
openstackgerrit | Fausto Marzi proposed openstack/freezer: WIP block based incremntal support - rsync https://review.openstack.org/290461 | 12: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 only | 13:20 |
*** yangyapeng has joined #openstack-freezer | 13:20 | |
daemontool | jith_, nope, because freezer could be installed within a private network | 13:21 |
daemontool | proxies | 13:21 |
daemontool | companies wouldn't allow to download software directly from the internet | 13:21 |
daemontool | and other cases | 13:21 |
daemontool | that would be difficult to manage | 13:21 |
daemontool | jith_, your current issue is "how to download and install elasticsearch" ? | 13:22 |
daemontool | jith_, you can download es from here https://www.elastic.co/downloads/past-releases | 13:23 |
daemontool | like wget https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.7.5.deb | 13:24 |
daemontool | or the versino you ened | 13:24 |
daemontool | s/ened/need/ | 13:24 |
daemontool | is that what you need? | 13:25 |
*** ferhat has joined #openstack-freezer | 13:27 | |
ferhat | ping to all | 13:27 |
*** reldan has joined #openstack-freezer | 13:29 | |
ferhat | ping m3m0 | 13:31 |
daemontool | ferhat, yes | 13:33 |
daemontool | I think we need a settings.py inside freezer/freezer and put there all the constants | 13:34 |
ferhat | currently I am testing stable/1.2.0 | 13:34 |
m3m0 | ferhat: tell me | 13:35 |
ferhat | when I try to create job from freezer ui which is stable/k,lo | 13:35 |
ferhat | I am getting following error from freezer-api | 13:35 |
ferhat | root ERROR u'f1f2faa69d67424398ce8c18f1846f55_freezer01.novalocal' does not match '^[\\w-]+$' | 13:35 |
m3m0 | mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm | 13:35 |
m3m0 | I think the mappings are not updated | 13:36 |
m3m0 | but I've never seen that error | 13:36 |
m3m0 | did you create a job successfully at some point? | 13:36 |
ferhat | I have tried from cli | 13:36 |
ferhat | but from web ui I could not | 13:37 |
ferhat | but if I use stable/kilo release for all api, client and web ui | 13:37 |
m3m0 | is this the name of the job? f1f2faa69d67424398ce8c18f1846f55_freezer01.novalocal | 13:37 |
ferhat | there is no problem | 13:37 |
m3m0 | what's the setup in which is failing? | 13:37 |
ferhat | web-ui: stable/kilo | 13:38 |
ferhat | client and api: stable/1.2.0 | 13:39 |
m3m0 | is there a reason to not working with stable/kilo in all dependencies? | 13:40 |
ferhat | If I install stable/kilo than I am getting error on admin jobs | 13:41 |
ferhat | in all stable/kilo release installation. nova backup does not work. | 13:41 |
daemontool | ferhat, use stable/kilo or stable/liberty | 13:42 |
m3m0 | only from the ui? or the cli as well? | 13:42 |
daemontool | I have to remove that tag | 13:42 |
ferhat | from ui | 13:43 |
ferhat | that means I need to stick with stable/kilo release | 13:44 |
ferhat | because I am using OpenStack kilo | 13:44 |
m3m0 | ok just to understand this: | 13:45 |
m3m0 | if you use all the components as stable/kilo it works | 13:45 |
m3m0 | but if you use stable/kilo for the ui and stable/1.2.0 for the api it fails right? | 13:45 |
m3m0 | daemontool for testr is there any extra step that I should be doing in tox? | 13:46 |
*** ddieterly has joined #openstack-freezer | 13:46 | |
ferhat | correct | 13:47 |
m3m0 | I'll need to set that env and see what is happening | 13:48 |
daemontool | do not use stable/1.2.0 | 13:48 |
daemontool | I'll remove that tag / branch soon | 13:48 |
daemontool | m3m0, like the steps needed to have testr working ? | 13:48 |
ferhat | that means I need to go back to stable/kilo | 13:49 |
daemontool | ferhat, or forward | 13:49 |
daemontool | to stable/liberty | 13:49 |
m3m0 | ferhat: preferably yes | 13:49 |
m3m0 | daemontool: yes, any other steps need it? | 13:49 |
ferhat | for OpenStack Kilo, can I user stable/liberty | 13:49 |
daemontool | ferhat, if you use virtualenv, you can use the liberty agent | 13:50 |
m3m0 | daemontool I'm getting this error: ERROR: InvocationError: '/home/memo/src/python-freezerclient/.tox/py27/bin/python setup.py testr --coverage --testr-args=' | 13:50 |
ferhat | I see. | 13:50 |
daemontool | there are many steps | 13:50 |
zhangjn | Please give me email to source code walkthrough. | 13:50 |
ferhat | and I am having problem with logging in to https://wiki.openstack.org/wiki/Freezer. | 13:51 |
ferhat | as soon as I resolve this problem.I will start updating documents. | 13:51 |
daemontool | m3m0, where's the email you send to the openstck ml | 13:52 |
daemontool | can't find it | 13:52 |
daemontool | re: source code walkthru | 13:52 |
ferhat | also is there anyway to downgrade the installation? | 13:52 |
daemontool | ferhat, what problem are you having? | 13:52 |
daemontool | ferhat, if you use virtualenv that is quite easy | 13:53 |
daemontool | if you installed freezer system wide | 13:53 |
daemontool | nope | 13:53 |
daemontool | deinstall old version, reinstall new version | 13:53 |
m3m0 | I send it to your gmail account | 13:53 |
daemontool | what was the subject? | 13:54 |
daemontool | ok ty | 13:54 |
daemontool | got it | 13:54 |
ferhat | so you suggest me to install everything in virtual env so if I need to use other version, I can switch to it easily | 13:54 |
m3m0 | ferhat: I think is way better to follow that approach | 13:55 |
daemontool | zhangjn, http://osdir.com/ml/openstack-dev/2016-02/msg01933.html and http://osdir.com/ml/openstack-dev/2016-02/msg02085.html | 13:55 |
m3m0 | so you don't mess with the dependencies | 13:55 |
ferhat | ok. will do that. | 13:55 |
daemontool | ferhat, in that way you'll manage | 13:55 |
daemontool | services and components | 13:55 |
daemontool | where each one has its own | 13:55 |
daemontool | environment | 13:55 |
daemontool | with its own dependencies | 13:55 |
daemontool | rather than having system wide shared dependencies | 13:56 |
daemontool | across all modules and services | 13:56 |
ferhat | sounds good. | 13:56 |
ferhat | but that does not apply to elasticsearch and web ui | 13:56 |
daemontool | web ui yes | 13:57 |
daemontool | elasticsearch not because is not a python module | 13:57 |
ferhat | ok. this was a really important information. | 13:58 |
ferhat | I should doument it :D | 13:58 |
ferhat | for wiki page. I have never able to login with OpenID | 13:58 |
daemontool | ferhat, yes thanks | 13:58 |
daemontool | so create an account there | 13:58 |
daemontool | do you have an account in launchpad? | 13:58 |
daemontool | create an account in launchpad | 13:59 |
daemontool | and use the same account to login in the wiki | 13:59 |
m3m0 | help :) http://paste.openstack.org/show/489844/ | 13:59 |
ferhat | I have. and I have given proper permission from launchpad | 13:59 |
ferhat | than I return to wiki. on that page I see Login / create and accoun with OpenID | 14:00 |
ferhat | I click on it. nothing happens. | 14:00 |
daemontool | ferhat, clore the browser and repopen it | 14:00 |
daemontool | or start a private browing tab with firefox | 14:00 |
daemontool | s/clore/close/ | 14:00 |
zhangjn | ping daemontool | 14:01 |
daemontool | zhangjn, yes | 14:01 |
zhangjn | meeting num:513 551 648 | 14:01 |
zhangjn | Meeting Link: https://demo.webex.com.cn/demo/j.php?MTID=m72caa0d20f548aad76ab427a97d2e07f | 14:01 |
zhangjn | Meeting Password: freezer | 14:01 |
daemontool | vannif, ^^ , also we need to send an email | 14:01 |
daemontool | to the ml | 14:01 |
daemontool | with that information | 14:01 |
daemontool | explaning that we are not using hangout because there are issues from users connecting from some geographic areas | 14:02 |
zhangjn | I have not subscription the maillist, please resend meeting info by email. | 14:03 |
zhangjn | thx daemontool | 14:03 |
*** daemontool_ has joined #openstack-freezer | 14:03 | |
*** ddieterly has quit IRC | 14:04 | |
m3m0 | I'm supposed to be doing something but I don't remember what | 14:07 |
*** daemontool has quit IRC | 14:07 | |
daemontool_ | m3m0, testr | 14:08 |
daemontool_ | _ | 14:08 |
daemontool_ | ? | 14:08 |
m3m0 | hahaha I think it was something more dangerous | 14:09 |
openstackgerrit | Eldar Nugaev proposed openstack/freezer: Broken level for incremental backups https://review.openstack.org/290517 | 14:11 |
reldan | slashme, 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 |
reldan | And I’m going to start to work on mistral project for a while | 14:15 |
jith_ | daemontool: i got an error when i give freezer-db-init | 14: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 worried | 14:17 |
zhangjn | ping daemontool, I have updated the Meeting info in the etherpad. | 14:19 |
daemontool_ | zhangjn, ok | 14:19 |
daemontool_ | ty | 14:19 |
zhangjn | You'd better resend by maillist, :) | 14:19 |
daemontool_ | zhangjn, m3m0 is the chairman | 14:20 |
yangyapeng | ping 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 |
reldan | daemontool_: 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-freezer | 14:33 | |
zhangjn | we have something to learn about this project. | 14:35 |
zhangjn | we are trying to do someting. | 14:36 |
daemontool_ | reldan, I think we have to start with something | 14:37 |
reldan | yes, sure | 14:38 |
m3m0 | zhangjn: do you have anything in mind? | 14:38 |
daemontool_ | reldan, the rsync stuff I'm working on is here freezer/storage/swift.py | 14:44 |
daemontool_ | everything is work in progress | 14:44 |
reldan | daemontool_: Not quite understand should it be engine? | 14:44 |
daemontool_ | incremental_engine | 14:45 |
daemontool_ | but we can change the name | 14:45 |
daemontool_ | at anytime | 14:45 |
daemontool_ | an sorry | 14:45 |
daemontool_ | here https://review.openstack.org/#/c/290461/ | 14:45 |
reldan | daemontool_: Looks cool! :) | 14:47 |
daemontool_ | reldan, here https://review.openstack.org/#/c/290461/2/freezer/main.py line 95 | 14:48 |
daemontool_ | I think that could be abstracted | 14:48 |
daemontool_ | but for now | 14:49 |
daemontool_ | it's ok | 14:49 |
daemontool_ | now I can work | 14:49 |
daemontool_ | on the rsync code itself | 14:49 |
daemontool_ | and move forward | 14:49 |
reldan | daemontool_: I would prefer to different implementation than one with if-s | 14:49 |
daemontool_ | reldan, that's what I'm referring to | 14:49 |
reldan | probably we can find a lot of common code and extract it to abstract, yes | 14:50 |
daemontool_ | we can remove that ifs | 14:50 |
daemontool_ | those if | 14:50 |
reldan | because previously I had only one implementation and was unable to see common parts | 14:50 |
daemontool_ | now that code is unusable yet | 14:50 |
daemontool_ | as I need to place the queue and pipes part | 14:50 |
daemontool_ | out | 14:50 |
*** ddieterly is now known as ddieterly[away] | 15:18 | |
openstackgerrit | Merged openstack/freezer: Broken level for incremental backups https://review.openstack.org/290517 | 15:37 |
openstackgerrit | Fabrizio Vanni proposed openstack/freezer: list backups stored in API https://review.openstack.org/277352 | 15:43 |
*** ddieterly[away] is now known as ddieterly | 15:47 | |
openstackgerrit | Fabrizio Vanni proposed openstack/freezer-api: add database status check https://review.openstack.org/289931 | 15:52 |
*** EinstCrazy has quit IRC | 15:56 | |
ferhat | I have installed freezer-web-ui with virtual env | 16:09 |
ferhat | but getting ImportError: No module named disaster_recovery | 16:09 |
daemontool_ | ferhat how did you install? | 16:20 |
daemontool_ | virtualenv freezer-web-ui-env-1 | 16:20 |
ferhat | I have installed virtualenv wtih pip first | 16:20 |
daemontool_ | git clone ..... | 16:20 |
daemontool_ | source freezer-web-ui-env-1/bin/activate | 16:20 |
daemontool_ | cd freezer-web-ui | 16:20 |
daemontool_ | pip install -e ./ | 16:21 |
ferhat | ooo | 16:21 |
ferhat | yes I have created new virtual env called freezer-liberty | 16:23 |
ferhat | than source freezer-liberty/bin/activate | 16:23 |
ferhat | than I have installed freezer, freezer-api and freezer-web-ui | 16:23 |
daemontool_ | with pip install -e ./ | 16:27 |
daemontool_ | on each directory? | 16:27 |
daemontool_ | you-ll be sure all the deps are installed | 16:27 |
ferhat | not actually | 16:29 |
ferhat | I have used pip install -r requirement.txt | 16:29 |
daemontool_ | ok | 16:29 |
daemontool_ | so what is the issue you are currently having? | 16:30 |
ferhat | I am getting ImportError: No module named disaster_recovery | 16:30 |
ferhat | it is only for web-ui | 16:30 |
ferhat | freezer-api and clients works like charm | 16:30 |
m3m0 | that should be installed in the same virtualenv as horizon | 16:31 |
ferhat | that was the problem. | 16:33 |
ferhat | at the end. I must use stable/kilo release for OpenStack kilo | 16:33 |
ferhat | it is confirmed | 16:33 |
daemontool_ | ferhat, for web ui and api for sure yes | 16:35 |
ferhat | this will go to documentation :D | 16:35 |
daemontool_ | ok :) | 16:36 |
ferhat | unfortunatly, wiki.openstack.org OpenID intergation is broken | 16:42 |
ferhat | I am not able to login | 16:42 |
daemontool_ | ferhat, can you ask on #openstack-infra some clarification about that? | 16:43 |
daemontool_ | brb | 16:44 |
daemontool_ | 10 min break | 16:44 |
ferhat | ok | 16:44 |
ferhat | will ask them | 16:44 |
openstackgerrit | OpenStack Proposal Bot proposed openstack/freezer: Updated from global requirements https://review.openstack.org/288697 | 16:46 |
*** EinstCrazy has joined #openstack-freezer | 16:56 | |
slashme | Bug_fix for metadata level | 16:59 |
slashme | Liberty: https://review.openstack.org/290684 | 16:59 |
slashme | kilo: https://review.openstack.org/290686 | 16:59 |
*** EinstCrazy has quit IRC | 17:03 | |
*** daemontool has joined #openstack-freezer | 17:05 | |
*** daemontool_ has quit IRC | 17:07 | |
*** daemontool_ has joined #openstack-freezer | 17:23 | |
*** daemontool has quit IRC | 17:23 | |
*** clenimar has joined #openstack-freezer | 17:24 | |
*** ddieterly is now known as ddieterly[away] | 17:25 | |
*** ddieterly[away] is now known as ddieterly | 17:28 | |
*** reldan has quit IRC | 17:36 | |
*** reldan has joined #openstack-freezer | 17:36 | |
openstackgerrit | Jonas Pfannschmidt proposed openstack/freezer-api: Use six.moves.input rather than six.moves.builtin.input https://review.openstack.org/290732 | 18:02 |
*** reldan has quit IRC | 18:10 | |
*** daemontool__ has joined #openstack-freezer | 18:10 | |
*** daemontool_ has quit IRC | 18:13 | |
*** daemontool__ has quit IRC | 18:16 | |
*** jonaspf has joined #openstack-freezer | 18:25 | |
*** ddieterly is now known as ddieterly[away] | 18:43 | |
*** ddieterly[away] has quit IRC | 19:44 | |
openstackgerrit | Deklan Dieterly proposed openstack/freezer-api: Add gate hooks https://review.openstack.org/290814 | 19:52 |
openstackgerrit | Deklan Dieterly proposed openstack/freezer-api: Add gate hooks https://review.openstack.org/290814 | 19:54 |
openstackgerrit | Deklan Dieterly proposed openstack/freezer-api: Add gate hooks https://review.openstack.org/290814 | 19:59 |
*** yangyape_ has joined #openstack-freezer | 20:08 | |
*** yangyapeng has quit IRC | 20:09 | |
*** daemontool has joined #openstack-freezer | 20:14 | |
*** reldan has joined #openstack-freezer | 20:25 | |
openstackgerrit | Deklan Dieterly proposed openstack/freezer-api: Add Freezer API Version Test https://review.openstack.org/290842 | 20:47 |
*** ddieterly has joined #openstack-freezer | 22:16 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!