14:00:23 #startmeeting freezer 14:00:24 Meeting started Thu Mar 3 14:00:23 2016 UTC and is due to finish in 60 minutes. The chair is ddieterl_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:28 The meeting name has been set to 'freezer' 14:00:36 hi everybody 14:00:45 can we get a show of attendees? 14:00:50 o/ 14:01:17 Today meeting not in openstack-meeting-alt? 14:01:23 ddieterl_, the meeting it on #openstack-meeting-alt 14:01:28 why do we meet in the alt room 14:01:29 s/it/is/ 14:01:40 #endmeeting 14:01:51 because in openstack the project use the common rooms to do the meetings 14:01:55 ok 14:02:19 ddieterly, http://eavesdrop.openstack.org/#Freezer_Meeting 14:20:17 Deklan Dieterly proposed openstack/freezer-api: Introduce tempest tests https://review.openstack.org/287369 14:33:27 frescof, ping 15:00:56 ping EinstCrazy 15:01:24 ok 15:01:26 yes? 15:01:27 so here we are 15:01:29 yangyapeng, 15:01:37 we can enable freezer-schedule in devstack. 15:01:38 would you like to make that better 15:01:41 yes 15:01:44 zhangjn, yes 15:01:48 I think we should do a good job in devstack 15:01:54 couldn't agree more 15:01:58 Can let others more simple to run freezer 15:02:47 some problem in freezer-web-ui use devstack to install. 15:03:55 freezer-web-ui is unavailable in master. 15:04:46 who can review our devstack patch? 15:07:32 zhangjn, which one 15:07:35 one sec 15:08:34 https://review.openstack.org/#/c/265111/ 15:09:25 This is obvious bug. 15:12:55 zhangjn, shouldn't be redirected to openstack/? 15:13:18 This patch is ok 15:13:21 ok 15:13:24 yes yes 15:13:25 sure 15:13:32 but when you hit stackforge/ 15:13:34 but it's nobody to review. 15:13:39 ok 15:13:41 LOL 15:13:54 the thing is the py34 job is failing 15:14:02 I've rechecked it 15:14:17 of course it can't be related to that change 15:14:22 as it is very simple 15:14:32 I got it, thx. 15:15:17 have someone to review all summit patch everyday? 15:16:08 Like other project 15:18:39 m3m0, freezer-web-ui use freezer project as freezer_client in devstack. 15:21:18 sudo -H -E pip install -e git+${FREEZER_CLIENT_REPO}@${FREEZER_CLIENT_BRANCH}#egg=freezer-origin_${FREEZER_CLIENT_BRANCH} to install is unnormal. 15:23:25 zhangjn, ok 15:26:39 the problem is that we don't have a pip version of freezer 15:26:59 so we need to do it by installing the source 15:27:25 zhangjn ^^ 15:29:00 I think install freezer-web-ui is not relate to freezer-client. 15:32:04 mmm it is, we need to install the freezer-client to communicate with the api 15:32:38 now I will install twice freezer. 15:34:23 otherwise freezer is not install in $DEST, it's unnormal in devstack. 15:38:15 but why twice? do you have 2 virtualenvs? 15:39:09 devstack enable freezer, freezer-api, freezer-web-ui 15:39:30 freezer install first, freezer-web-ui install another 15:43:06 oooook ok ok ok, so you think we should remove freezer installation from freezer-web-ui, do you want to do it? 15:46:13 now it can be removed 15:46:18 cause we have the python-freezerclient 15:46:23 so do not need the agent and scheduler anymore 15:47:49 we can define the require in requirements.txt. 15:48:21 when freezer-client is work. 15:48:57 ++ 15:58:41 https://review.openstack.org/#/c/287935/ 15:59:17 I summit a path set, pls to review it. 16:00:20 zhangjn, ok 16:01:10 pls add workflow in this review:https://review.openstack.org/#/c/282215/ 16:02:03 ddieterly, currently freezer-api fails on the dsvm https://jenkins03.openstack.org/job/gate-freezer-api-devstack-dsvm/1/console 16:02:29 daemontool_: +2 and +A respectively 16:02:36 zhangjn: +2 and +A respectively 16:02:59 thx 16:04:05 m3m0, referring to https://review.openstack.org/#/c/265111/ 16:04:30 zhangjn, as soon as it is verified I'll approve it 16:09:33 ddieterly, what's the tempest related gate job that is enabled now? 16:09:47 there's a path issue 16:23:55 that needs a rebase 16:24:01 sorry a recheck 16:24:10 it fail at the gates 16:27:38 ERROR: InvocationError: '/bin/bash tools/pretty_tox.sh --concurrency=4 freezer_api_tempest_plugin' 16:28:05 what about freezer_api_tempest_plugin? 16:29:41 there is no test for freezer-api? 16:30:33 post_test_hook.sh is null to test. 16:31:01 I think is related to this change https://review.openstack.org/#/c/287486/1/jenkins/jobs/freezer.yaml 16:31:43 daemontool_: yes, i'm working on it 16:32:03 here is the new gate job: https://review.openstack.org/#/c/287486/ 16:35:58 ddieterl_, np 16:36:07 take all the time you need 16:36:12 lol 16:36:13 ok 16:36:23 i think this next run will work 16:36:37 (fingerscrossed) 16:36:38 if the test fails, then the tests are running 16:36:39 lol 16:37:01 i put assertequals(1,2) 16:37:08 we should see that failure in the gate 16:38:31 ok 16:40:10 :) 16:42:32 success! 16:42:50 the tempest plugin is running in the gate in freezer-api 16:43:18 ============================== 16:43:18 2016-03-03 16:40:25.951 | Failed 1 tests - output below: 16:43:18 2016-03-03 16:40:25.951 | ============================== 16:43:20 2016-03-03 16:40:25.951 | 16:43:22 2016-03-03 16:40:25.951 | freezer_api_tempest_plugin.tests.api.test_api_version.TestFreezerApiVersion.test_api_version[gate] 16:43:24 2016-03-03 16:40:25.951 | -------------------------------------------------------------------------------------------------- 16:43:26 2016-03-03 16:40:25.952 | 16:43:28 2016-03-03 16:40:25.952 | Captured traceback: 16:43:30 2016-03-03 16:40:25.952 | ~~~~~~~~~~~~~~~~~~~ 16:43:32 2016-03-03 16:40:25.952 | Traceback (most recent call last): 16:43:34 2016-03-03 16:40:25.952 | File "/opt/stack/new/freezer-api/freezer_api/tests/freezer_api_tempest_plugin/tests/api/test_api_version.py", line 23, in test_api_version 16:43:36 2016-03-03 16:40:25.952 | self.assertEqual(1, 2, 'First test case') 16:43:38 2016-03-03 16:40:25.952 | File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 362, in assertEqual 16:43:40 2016-03-03 16:40:25.952 | self.assertThat(observed, matcher, message) 16:43:42 2016-03-03 16:40:25.952 | File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 447, in assertThat 16:43:44 2016-03-03 16:40:25.952 | raise mismatch_error 16:43:46 2016-03-03 16:40:25.952 | testtools.matchers._impl.MismatchError: 1 != 2: First test case 16:50:13 daemontool_: i fixed the test to pass. if it passes, we can +2 the patch. 16:50:27 then we can start to add tempest tests as needed 16:52:44 sure 16:57:48 Merged openstack/freezer: Add space to log message https://review.openstack.org/285991 17:04:05 Merged openstack/freezer: Add SSL support for freezer https://review.openstack.org/278367 17:05:22 vannif_, ping https://review.openstack.org/#/c/277352/ 17:21:49 hello all 17:22:01 I did not know this channel exist 17:22:14 ferhat: hello 17:22:24 thank you Fausto fro the info 17:23:13 and also thank for developing freezer. this is one of the most anticipated project from my side of view 17:23:53 I am having some trouble. I would be glad if some of you guys can lead me to right direction 17:24:10 daemontool_: this is working now https://review.openstack.org/#/c/287369/6 17:24:16 ferhat, I'm here 17:24:20 ddieterly, +2ed 17:24:28 if you have to send a new patchset 17:24:31 graci 17:24:35 please fix the README 17:24:35 ok 17:24:45 well done (thumbsup) 17:24:49 ferhat, 17:25:01 please do tell 17:25:03 :) 17:25:08 we are planning to use freezer for our openstack enviroment. 17:25:13 ok 17:25:24 which release? 17:25:44 I have installed freezer-api v1.2.0 to our one of the controller 17:26:03 our openstack is kilo 17:26:26 ok 17:26:40 vannif_, ping ^^ 17:26:47 I have followed the installation instruction on https://github.com/openstack/freezer-api/ 17:27:00 ok 17:27:13 and started freezer-api with "freezer-api 176.53.94.6" 17:27:26 did you registered the freezer api endpoint to keystone? 17:27:31 yes I did 17:27:33 ok 17:27:34 :) 17:27:36 with following commend 17:27:49 keystone endpoint-create \ --service-id $(keystone service-list | awk '/ backup / {print $2}') \ --publicurl http://176.53.94.6:9090 \ --internalurl http://176.53.94.6:9090 \ --adminurl http://176.53.94.6:9090 \ --region RegionOne 17:27:56 ok 17:28:11 and I am getting following error 17:28:12 http://176.53.94.6:9090/ 17:28:19 Authentication required 17:28:53 ok 17:29:01 so you have sourced your OS credentials right? 17:29:02 like 17:29:09 env | grep ^OS 17:29:14 you see OS_things 17:29:17 ? 17:29:21 I have not 17:29:32 ok so you need to have creedntials 17:29:37 to do that 17:29:43 do you have a user? 17:30:04 daemontool_: https://review.openstack.org/#/c/287999/1 17:30:45 otherwise from browser 17:30:48 let me check that 17:30:50 you need to install the freezer-web-ui 17:30:51 also 17:30:59 but I'd like to understand 17:31:09 what happen if you have the creds and try something like 17:31:09 https://review.openstack.org/#/c/287999/1 17:31:11 sorry 17:31:19 freezer-scheduler client-list 17:31:33 OS_REGION_NAME=RegionOne OS_PROJECT_NAME=admin OS_PASSWORD= OS_AUTH_STRATEGY=keystone OS_AUTH_URL=http://192.168.0.2:5000/v2.0/ OS_USERNAME=admin OS_TENANT_NAME=admin OS_ENDPOINT_TYPE=internalURL OS_NO_CACHE=true 17:31:47 I have sourced following 17:32:06 ok 17:32:56 can you get the list of services endpoints? 17:33:09 sure let me get them 17:33:26 something like 17:33:26 openstack endpoint list 17:34:27 | 1b4014505c8b4537929cb88b0bdb8696 | freezer | backup | Freezer Backup Service | 17:34:40 77c382ef33e145d7a90d2e23eb38551d | RegionOne | http://176.53.94.6:9090 | http://176.53.94.6:9090 | http://176.53.94.6:9090 | 1b4014505c8b4537929cb88b0bdb8696 | 17:34:51 ok 17:34:54 last one is endpiont list 17:34:57 if you execute the command 17:35:08 freezer-scheduler client-list 17:35:56 before we go further. I do not have freezer scheduler installed on this server 17:36:16 ok 17:36:28 and the freezer-agent? 17:36:32 or freezerc? 17:36:59 root@control01:~# freezer-scheduler client-list 2016-03-03 17:36:48.785 47531 ERROR freezer.scheduler.freezer_scheduler [-] Please provide valid keystone auth url with valid keystone api version to use Please provide valid keystone auth url with valid keystone api version to use 17:37:05 I get this 17:38:44 if you execute 17:38:48 swift list 17:38:51 what do you get? 17:39:26 I get nothing 17:39:38 no error 17:39:38 ok 17:39:38 but if I execute nova list 17:39:53 I get my vms 17:39:56 ok 17:40:12 I am also getting following error in the logs 17:40:12 2016-03-03 17:38:48,585 keystonemiddleware.auth_token INFO Rejecting request 17:41:43 mmhhh 17:41:46 keystonemiddleware.auth_token WARNING Configuring auth_uri to point to the public identity endpoint is required; clients may not be able to authenticate against an admin endpoint 17:41:49 and this one 17:42:00 keystonemiddleware.auth_token WARNING Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use memcache for the auth_ 17:42:08 also this warning 17:43:07 export OS_ENDPOINT_TYPE=publicURL 17:43:08 try that 17:43:19 and see if the error is still there 17:45:56 still getting same error 17:46:01 export OS_IDENTITY_API_VERSION=2 17:47:24 try that and then 17:47:43 freezer-scheduler client-list 17:47:49 ok 17:47:50 Saad Zaher proposed openstack/freezer: Adding option disable-exec to freezer-scheduler https://review.openstack.org/288008 17:48:08 szaher, ping 17:49:03 daemontool_: pong 17:49:18 szaher, do you have 10 minutes? 17:49:24 Yes Sure 17:49:25 I have to go home in 5 minutes it's 7 pm here 17:49:33 Ok take your time 17:49:34 can you provide some support to ferhat 17:49:39 ? 17:49:44 Ok 17:49:49 we need to understand 17:49:51 thx deamontool 17:49:51 if the scheduler 17:50:01 can complete the authentication against the freezer api 17:50:08 the freezer service is registered 17:50:14 Ok 17:50:28 with the other clients he can 17:50:29 auth 17:50:50 Ok no worries 17:50:55 ferhat: Hi 17:51:10 hello szaher 17:51:19 thank you daemon 17:51:38 Could you please, dump your config file and log file here http://paste.openstack.org/ 17:51:44 and pass me the link 17:52:14 freezer-ap.cfg? 17:53:19 http://paste.openstack.org/show/489198/ 17:53:26 /etc/freezer-api.conf 17:55:00 I can work with feezerc without any problem 17:57:12 hello. 17:57:21 hi vannif 17:57:23 yes. what about the freezer-api.conf ? 17:57:34 ferhat: Can you try this http://paste.openstack.org/show/489203/ ? 17:58:03 if has configuration options for the database endpoint and the keystonemiddleware which manages the authentication on behalf of the API 17:58:04 ferhat: Could you please, dump this log in paste and send us the link /var/log/freezer-api.log ? 17:59:37 ok will do 18:01:12 here is is the /var/log/freezer-api.log 18:01:17 http://paste.openstack.org/show/489204/ 18:02:08 I have installed freezer-api in our horizon dashboard server. 18:02:31 this server also contains keystone swift and some other services 18:03:00 did you try the new configurations I sent to you while ago ? 18:03:46 yes I did 18:04:09 the log file contains my last config change 18:04:59 are you using devstack ? 18:06:25 no I am using Mirantis OpenStack 7 18:06:27 kilo release 18:06:40 the nodes have deployed with fuel infra 18:09:07 and what is the problem you are facing for the time being ? 18:09:17 szaher, he cannot finalize the authentication 18:09:23 against the freezer-api 18:10:07 ferhat, OS_PASSWORD= you have something there right? 18:10:16 you just sanitized the value before is it? 18:11:23 ferhat: could you please source openstack credentials and try the following command and let me know the result. freezer-scheduler job-list 18:11:56 daemontool_: It's not an error. if you access freezer-api from http you will get the same message ! 18:12:12 ok let me get them 18:12:24 I have my password on OS_PASSWORD 18:12:27 it is correct 18:12:48 I have sourced following env 18:13:28 http://paste.openstack.org/show/489205/ 18:13:41 root@control01:~# freezer-scheduler job-list 2016-03-03 18:13:36.859 13850 ERROR freezer.scheduler.freezer_scheduler [-] Please provide valid keystone auth url with valid keystone api version to use Please provide valid keystone auth url with valid keystone api version to use 18:14:25 if you access freezer-api from http you will get the same message ! 18:14:32 Authentication required 18:14:36 ok ferhat 18:14:42 unset OS_PROJECT_NAME 18:14:43 and retry 18:15:06 so you have 18:15:06 export OS_TENANT_NAME='services' 18:15:06 export OS_PROJECT_NAME='admin' 18:15:15 unset OS_PROJECT_NAME 18:15:22 export OS_TENANT_NAME=admin 18:15:32 execute the last 2 18:15:48 but I don't understand, it should work anyway 18:16:22 ferhat: http://paste.openstack.org/show/489206/ run these commands in your terminal then freezer-scheduler job-list 18:17:17 ferhat: Please, let me know the results when there are some 18:20:57 http://paste.openstack.org/show/489207/ 18:21:04 getting 503 18:22:30 logs ? 18:22:35 api logs ? 18:23:22 ferhat: do you copy ? 18:24:11 daemontool_: can we get https://review.openstack.org/#/c/287369/ and https://review.openstack.org/#/c/287999/ out the door? 18:24:33 yes 18:24:38 let me get api logs 18:24:40 ferhat: can you try again with these credentials http://paste.openstack.org/show/489208/ 18:26:47 http://paste.openstack.org/show/489209/ 18:27:43 Saad Zaher proposed openstack/freezer: Adding option disable-exec to freezer-scheduler https://review.openstack.org/288008 18:29:16 ferhat: do you have keystone v3 enabled ? 18:29:59 http://176.53.94.3:5000/v3/ 18:30:05 please check this page 18:35:07 ferhat: Can you login to the dashboard ? 18:35:15 Can you try keystone user-list 18:35:20 can you try openstack user list 18:35:28 let me know what is the result 18:36:14 yes I can login to dashboard 18:36:39 http://paste.openstack.org/show/489212/ 18:37:30 do I have to install the api to same server horizon dashboard resides? 18:38:06 I am suspecting somethings is mixing up with openstack installation 18:41:25 [*] Critical Error: Container PUT failed: http://176.53.94.3:8080/v1/AUTH_c0852b6eb95b47e380446d26382a9f6d/freezer_backups 404 Not Found [first 60 chars of response]

Not Found

The resource could not be found.< 18:42:11 openstack user list 18:42:11 Could not determine a suitable URL for the plugin 18:43:04 It could be better if you installed the api on the same server where keystone resides 18:44:39 yes I have installed api in the server where keystone also installed 18:44:57 I think I am hitting some sort of bug. 18:48:42 ferhat: I think keystone has a problem 18:48:50 can you dump keystone logs ? 18:49:57 I will take a look at it after 20 minutes, is that Ok ? 18:50:43 that would be ok 18:50:49 thank you for your time 18:53:55 keystone log http://paste.openstack.org/show/489218/ 19:03:24 thank you for all of your help 20:26:41 hi, folks, I'm looking for daemontool, do you know when he's usually online? 20:29:57 are there any other freezer cores around who know about the release plans? I want to make sure you don't miss the release window today 21:13:19 dhellmann: daemontool is usually online in the morning in the us. he lives in italy. 21:29:23 ddieterl_ : we haven't seen a milestone release proposal for freezer, are you planning one? 21:33:09 not sure 21:34:17 daemontool has stated that we need to respect the mitaka release schedule, so i think there is a plan for a milestone release proposal 21:34:44 unfortunately, i can't speak for daemontool, and i'm not core on freezer 21:43:11 seeing this when trying to run freezer-api on mac os x 21:43:21 Connected to pydev debugger (build 143.1919) 21:43:22 Unable to start server: 'module' object has no attribute 'TCP_KEEPCNT' 21:43:30 anyone know of a workaround? 21:45:27 it looks like this problem https://bugs.launchpad.net/keystoneauth/+bug/1527131 21:45:28 Launchpad bug 1527131 in keystoneauth "AttributeError: 'module' object has no attribute 'TCP_KEEPCNT'" [Undecided,Fix released] - Assigned to Federico Ressi (federico-ressi-9) 01:06:48 who can add workflow this review:https://review.openstack.org/#/c/287935/