08:02:56 #startmeeting multisite 08:02:56 Meeting started Thu Feb 16 08:02:56 2017 UTC. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:56 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:02:56 The meeting name has been set to 'multisite' 08:03:26 #info dimitri 08:03:33 Goutham may not be able to attend today's meeting 08:03:36 #info joehuang 08:03:47 yes 08:03:52 how about the multi-region environments 08:04:46 https://jira.opnfv.org/browse/FUNCTEST-721 08:05:50 So Juha will fix this issue 08:06:15 and I am afraid that no kingbird tempest test cases inside Functest container 08:06:28 the commit has been merged 08:06:31 what do you mean 08:06:57 we have old test cases 08:07:16 they should run 08:07:22 But it was installed by scripts in Functest container 08:07:37 but for the requirements dependency conflict 08:08:08 they may have already remove kingbird's installation(which load the tempest test cases into functest container) 08:09:31 I installed the Functest container, cannot find kingbird folder 08:09:52 the it will be the next ticket.. 08:10:13 the new mr environment is complete 08:10:21 all steps are automated 08:10:45 if functest needs to be updated, then it should be raised in jira 08:13:16 there is no good way to address the requirements conflict, because functest uses one old requirements set. But kingbird with new requirements 08:15:29 http://artifacts.opnfv.org/functest/brahmaputra/docs/devguide/#requirements-pip 08:16:22 we can keep running an older version of kb 08:16:55 even the old version has some requirements in-consistency 08:18:31 which particular requirement is inconsistent? 08:18:57 there is one page in Functest wiki, but I did not find that 08:20:05 ok, let’s see if the latest functest fix resolve current problem 08:21:00 need to consult Functest team 08:21:58 #info functest not include multisite test cases 08:22:12 I’ll tag a release for kb today 08:22:37 have you tested kb manually? 08:22:52 for the new function 08:22:59 and old quota function 08:23:57 yes, but not extensively 08:25:06 and python-kingbirdclient 08:25:07 I manually installed kingbird 08:25:24 the installation and usage guide were updated 08:25:50 #link https://gerrit.opnfv.org/gerrit/#/c/28217/ 08:26:09 #link https://review.openstack.org/#/c/434571/ 08:26:29 so please review the documentation update 08:27:24 yes, I will today 08:28:09 I'll update according to goutham's comment soon 08:29:12 ok 08:29:54 But I think for multisite stable branch creation, we may have to postpone several days. for the functest is not ready yet 08:30:43 test cases are ready(Goutham has submitted 08:32:15 There is one plugfest in Apirl held in France 08:32:48 and it may be good to plug the "multisite" 08:33:01 do you have plan to go there? 08:33:38 April is quite a busy month for me. It’ll depend on my load and the actual dates 08:34:49 https://jira.opnfv.org/browse/FUNCTEST-635?jql=text%20~%20%22kingbird%22 08:35:17 There is one ticket to use venv for kingbird in Functest container. but not addressed 08:36:40 kingbird quota detail ERROR (app) HTTPConnectionPool(host='127.0.0.1', port=8118): Max retries exceeded with url: /v1.0/d53c8d59ab6b4115ba6d402ab9ab389c/os-quota-sets/d53c8d59ab6b4115ba6d402ab9ab389c/detail (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) 08:37:50 the ticket is raised on functest 08:38:14 yes 08:38:55 how is it related to this output? 08:39:17 there is some error in my environment for kingbird. Could you test each API before you tag the release for kingbird? 08:39:29 It's running this morning 08:39:42 this looks like a connectivity issue 08:39:52 is your configuration correct? 08:40:11 if you try REST directly 08:40:18 I don't know why, didn't do anything 08:40:26 you mean kingbird client error 08:41:04 I don’t know 08:41:17 maybe conf issue 08:41:34 I'll try later, the more test, the better, so I hope that you can test it too 08:42:49 yes 08:42:59 I’ve got no other topics to discuss 08:43:04 no other topics, how about you 08:43:06 same 08:43:13 let’s end 08:43:15 ok, bye 08:43:18 bye 08:43:19 #endmeeting