07:03:08 #startmeeting multisite 07:03:08 Meeting started Thu Jun 9 07:03:08 2016 UTC. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:03:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:03:08 The meeting name has been set to 'multisite' 07:04:32 #info the functest container with kingbird temepest plugin can test the kingbird in Shanghai lab with one region installed 07:04:49 but some test cases failed 07:05:03 #info kingbird container installation in progress 07:05:03 yes, Did Meimei join? 07:05:21 I asked her for access 07:05:28 # default quota class in place 07:05:31 I will look into that 07:05:38 #info default quota class in place 07:05:38 and there are some resources like flavor, VMs, network are still there after the test failed 07:05:52 #info Jack finished Intel lab upgrade. Installation is ongoing 07:05:59 It's public holiday from today to tomorrow 07:06:01 Starting from next week we can run test there 07:06:19 Meimei will not process your request I guess 07:06:27 ohh 07:06:30 ok 07:06:54 okay, I will look into "there are some resources like flavor, VMs, network are still there after the test failed" 07:06:56 today 07:07:28 One more region can be added to Shanghai lab next week 07:08:03 I fixed some bugs in the code, but not update the patch yet 07:09:03 Good 07:09:05 okay. please update that 07:09:27 bugs for?? 07:09:34 I create an image of the container of FUNCTEST 07:10:00 bugs in tempest OR somewhere else? 07:10:17 load the kingbird tempest plugin specific configuration in tempest 07:10:36 It can be loaded now 07:10:48 okay, then is there any file kingbird.conf now? 07:10:54 for tempest 07:11:06 I changed the sync time to 20 seconds, and the printed value showed its loaded 07:11:06 or some conf file 07:11:22 not generated in the sample file 07:11:35 where have you changed the values? 07:11:40 which file 07:11:54 but if you add [kingbird] section and configuration items in the tempest.conf, then it'll be loaded together 07:12:20 yes, but that is not we should do it I feel 07:12:25 You can check that after I commit the patch 07:12:47 okay 07:13:13 we were doing it like this earlier. add [kingbird] section and configuration items in the tempest.conf 07:13:43 but there has to be separate config.py file for the plugin 07:14:01 you modified tempest/config.py and did? 07:14:07 It's very strange not generated in the sample file, will send a mail next week to tempest team 07:15:23 no, kingbird has its own config.py 07:15:49 okay, then where have you changed the value to 20? 07:15:53 which file 07:17:45 link broken? 07:17:56 I am there 07:18:19 in /etc/tempest/tempest.conf which was cp from generated file tempest.conf.sample 07:18:57 oh. so the kingbird section is generated in tempest.conf? 07:19:28 using config.py of kingbird plugin 07:20:07 not generated(it should be), just added manually, so need to consult tempest why 07:20:32 yeah. faced the same. 07:21:03 so, Can you help me in getting access to lab as Meimei is not available? 07:21:29 but if you add the items in the tempest.conf, it can be loaded 07:21:49 for that we need to change tempest/config.py file 07:22:14 The VPN access file is area restrict, not possible for to access the lab 07:22:30 okay 07:23:02 we can try on intel lab 07:23:15 it’s being installed 07:23:25 yes, just move the container to intel lab 07:23:25 Dimitri, Yesterday I was trying pip install kingbird locally 07:23:36 the size of the container is 1.3 GB 07:23:41 do we need to upgrade the kb package there? 07:23:55 I mean, it installs older version of kb 07:23:58 there’s no new tag 07:24:05 yeah 07:24:25 since we want to check master every time, it’s best if we git clone 07:24:29 you need to use git clone, then pip install -e kingbird, this way you can get the latest code installed 07:25:07 I was trying pip install kingbird 07:25:27 basically, I wanted to try all ways of installing kb 07:25:30 only install 0.1.0 07:25:34 too old 07:25:37 yeah 07:25:56 git clone 07:26:07 cd kingbird 07:26:09 pip install -r requirements.txt 07:26:09 pip install . 07:26:31 git -e genconfig 07:26:34 sorry 07:26:36 oslo-config-generator \ 07:26:36 --config-file /opt/stack/kingbird/tools/config-generator.conf \ 07:26:37 --output-file /home/kingbird/kingbird.conf 07:26:43 tox -egenconfig 07:26:52 no need 07:27:02 I can send you my dockerfile offline 07:27:22 great 07:27:32 okay, so the steps are automated 07:28:03 more or less 07:28:21 I’m still trying to figure out how to add keystone information to the .conf 07:28:41 as in? 07:28:51 endpoint details 07:28:53 ? 07:28:56 correct 07:29:14 I remmber use init set 07:29:16 sed? 07:29:38 :) not that. how to pass parameters to dockerfile 07:29:51 oh I see 07:30:08 or rather to a bash script that gets triggered from docker 07:30:38 maybe i’ll just create a local.conf file where this information will be hardcoded 07:30:47 but then, where would this file be stored 07:31:37 this way: RUN crudini --set /etc/keystone/keystone.conf token provider keystone.token.providers.uuid.Provider 07:32:00 crudini --set /etc/keystone/keystone.conf cache enabled true 07:32:21 crudini is to set the configuration file in .conf 07:33:30 can you explain me this RUN crudini --set /etc/keystone/keystone.conf token provider keystone.token.providers.uuid.Provider 07:34:02 I have a different issue 07:34:11 ok 07:34:13 Like Ashish said, sed will do just fine 07:36:06 So after Intel lab is ready, to have Functest container in Intel lab too 07:36:54 where’s this container? 07:37:00 And Dimitri and Ashish, the slides preparation for OPNFV summit, how do you think about it? 07:37:17 can be in jump host, or in the same blade 07:37:55 Joe, I’m assuming that the Tricircle activities are happening in parallel, and not officially related to OPNFV Multisite 07:38:24 Tricircle activities are running in OpenStack 07:38:25 we haven’t been discussing anything about it. however Tricircle is always in the OPNFV presentations 07:38:54 Then it should be stated what use cases tricircle tries to solve 07:38:55 but it's one of the candidate solution as we agreed and discussed 07:39:08 If you would like to discuss here, it's also ok 07:39:57 We have a co-presentation in OpenStack Austin summit to talk about this 07:40:58 Yes, I remember that :) 07:41:15 :) 07:41:22 we also had Tacker, if you remember, but it has nothing to do with OPNFV multisite, yet 07:41:36 different scenario 07:42:14 ok, nova is also not developed in OPNFV, but almost all of us in OPNFV talk about Nova 07:42:35 ok, whatever. I’ll stick to Kingbird. You can focus on the remaining parts 07:42:44 ok 07:42:57 I think giving some background would be good 07:43:02 and IPv6 team discuss about Tricircle in Austin meetup 07:43:08 sure 07:43:13 so we can reuse some slides from the previous presentation 07:43:29 together with multisite 07:43:37 I think so 07:44:16 I’d also change the title 07:44:35 I'll have a look at it 07:44:58 only 20 minutes for each project 07:45:03 do you know what river name they want to use for D release? 07:45:08 only 20 minutes for each project 07:45:16 no idea 07:45:54 And we also need to prepare configuration guide / user guide for kingbird 07:46:14 after the integration is almost done 07:46:43 hopefully finished before Jul.15 according to the plan 07:47:00 http://docs.openstack.org/developer/kingbird 07:47:11 can to edit this? 07:47:31 how to create those 07:47:40 how about this 07:47:41 Multisite: A Colorado Swim 07:47:47 not here, because kingbird is not OpenStack official project 07:48:20 to Dimitri: no problem, you always propose better title :) 07:48:46 we can mention plans for D-release in the talks itself 07:49:23 okayu 07:49:29 sure, and we can have one discussion in Jun 21(Tuesday) 07:49:45 I’ll update the presentation with Kingbird content 07:49:53 cool 07:50:08 tho, where we have to put the documentation? 07:50:17 tho => so 07:50:26 for now I suggest to follow the openstack structure 07:50:38 https://github.com/openstack/kingbird/tree/master/doc/source 07:50:39 inside readme ? 07:51:02 joe +1 07:51:15 after we finish it, copy to OPNFV repository for publish 07:52:38 yes, we will update here 07:52:58 IPv6 invited Multisite to join their design summit discussion, we can attend as needed 07:54:16 other topics? 07:54:32 none. let’s get to work 07:54:33 no from my side, I will look into tempest issue 07:54:50 ok, thank you very much 07:54:54 thanks 07:54:55 bye 07:54:57 thanks 07:54:59 let's conclude the meeting 07:55:04 by 07:55:05 bye 07:55:08 #endmeeting