07:08:22 #startmeeting multisite 07:08:22 Meeting started Thu Apr 14 07:08:22 2016 UTC. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:08:22 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:08:22 The meeting name has been set to 'multisite' 07:08:29 yes 07:08:33 sure will 07:08:43 I was busy with finalizing tempest and summit VISA thing 07:08:55 have to check VPN credentails 07:09:12 ok, so you will also attend Austin summit 07:09:26 till now it is not sure :) 07:09:46 For devstack, first to download devstack 07:09:59 okay 07:10:09 http://docs.openstack.org/developer/devstack/ 07:10:12 it's simple 07:11:07 and then copy and rename https://github.com/openstack/kingbird/blob/master/devstack/local.conf.sample to local.conf to the devstack folder you downloaded 07:12:44 Dimtri has pinged me 07:12:59 there is some problem with his IRC. He will join soon 07:13:16 ok, no problem 07:13:40 okay. so this local.conf is enough? 07:13:45 then run stack.sh? 07:13:50 yes 07:13:55 hey 07:14:00 finally joined 07:14:00 hey 07:14:05 #info dimitri 07:14:12 #info malla 07:14:14 so the code is picked from github and installed 07:14:15 #info joehuang 07:14:19 #info Ashish 07:14:31 The code will be picked automaticly 07:14:46 Hi, Dimitri, and Malla 07:14:52 Hi All 07:15:06 Ashish and I just talked about how to use devstack to do function test 07:15:24 I just fixed the bug and make devstack can work now 07:15:40 but the patch needs to be reviewed and merged for you to use devstack 07:15:48 yes 07:16:03 #link https://review.openstack.org/#/c/304368/ 07:16:27 when I try to fix the devstack issue, and find another issue must be addressed first 07:16:44 #link https://review.openstack.org/#/c/305593/ 07:17:13 the tables cannot be sync-ed to the database for the command is not executable 07:17:28 hm 07:17:42 good catch 07:17:45 so please review these two patches 07:18:18 KINGBIRD_ENGINE=$KINGBIRD_DIR/kingbird/cmd/engine.py KINGBIRD_ENGINE_CONF=$KINGBIRD_CONF_DIR/engine.conf KINGBIRD_ENGINE_LISTEN_ADDRESS=${KINGBIRD_JD_LISTEN_ADDRESS:-0.0.0.0} 07:18:26 wo dont have engine.conf right? 07:18:32 KINGBIRD_ENGINE_CONF=$KINGBIRD_CONF_DIR/engine.conf 07:18:33 After these two patches, curl request can be routing correctly 07:18:47 no, we don’t 07:18:52 it’s kingbird.conf 07:18:54 created in the devstack 07:19:01 it's same 07:19:27 ok, can rename these two conf to same , then devstack scripts need to update 07:19:47 yeah. reviewed 07:20:20 Joe, I have updated your comment for tempest 07:20:25 the file is created during the devstack, but not use tox -egenconfig to generate 07:20:27 create project for tests 07:20:31 ok 07:20:36 great 07:20:42 please review 07:20:53 #link https://review.openstack.org/#/c/304179/ 07:21:11 okay. so with tox it will create kingbird.conf 07:21:17 with devstack it creates engine.conf and api.conf 07:21:18 ? 07:21:32 we need to have same for both tox and devstack 07:23:10 hello, my previous connection seems to be lost 07:23:38 hi 07:24:28 ashish, yes we need to align, and we need to change the config filenames to kingbird, just like we have for a regular kingbird setup 07:25:12 hi joe 07:25:32 yes, have commented on Joe's patch, Joe will update that 07:25:36 I just said “yes we need to align, and we need to change the config filenames to kingbird, just like we have for a regular kingbird setup” 07:25:45 hi, just come back 07:25:54 Hi 07:26:01 agree, I'll change after the meeting 07:26:21 just use same kingbird.conf 07:26:25 yeah 07:26:57 ok, I got pgp from Intel lab, but no time to verify it works or not 07:27:05 try to run kingbird first 07:27:42 we have the intel lab till 24 I think 07:27:46 April that is 07:28:03 sorry 22. 07:28:07 You mean the lab will be shutdown after 24? 07:28:13 You mean the lab will be shutdown after 22? 07:28:15 I’ve asked jack if we get to keep the environment after that 07:28:31 I think it will be on maintenance for some time, and then it’ll be back 07:28:44 Jack’s intention is to put back the HDDs into the new servers 07:28:53 ok 07:29:04 how long it'll come back 07:29:11 that I don’t know 07:29:31 it shouldn’t be too long 07:29:49 I got VPN access to Huawei shanghai lab, two blades, one work, the other one can't access 07:30:09 try to access the Intel lab 07:30:15 I'll 07:30:19 the environment is already in place there 07:30:35 you can ping me when you’ve accessed and I can show you how to navigate there 07:30:38 Yes 07:30:47 that's great 07:31:05 Ashish, I suggest you also request a vpn access 07:31:08 I also think we don't need too much environment 07:31:18 it’s plain openstack 07:31:25 two openstacks with shared keystone to be precise 07:31:26 other wise, lab work will occupy too much effort 07:31:34 yes. I will do it today 07:32:09 Joe, agree, that’s why for now let’s use it for our immediate needs 07:32:27 Keystone there is not configured for Fernet tokens yet 07:32:45 There is a Galera cluster for controllers 07:32:53 hence for the Keystone database 07:32:58 And I found that if we integrate tempest into functest and installer, then the CI job will work automaticly 07:33:11 most work will on the installer part for integration 07:33:25 how’s that? 07:33:46 because Functest alreay in CI daily job 07:34:11 so if we integrate tempest in the Functest, it'll be part of Functest 07:34:27 will functest create two regions? 07:34:33 and Functest will call installer to install all package first 07:34:49 no, that's the installer does't do today 07:35:11 so, the big part is in installer 07:35:23 and support multi-region installation 07:35:38 what installer are we talking about? 07:36:03 I know there’s Fuel@OPNFV and some others 07:36:31 we need to select one for this release, we have no enough resource to work on all 07:36:40 I assume Fuel for the first one 07:36:55 correct 07:37:06 this will be quite easy with Fuel 07:37:18 however the tricky bit would be the postinstallation configuration 07:37:24 such as centralizing Keystone 07:37:50 yes 07:37:51 while Fuel can create two OpenStack environments, it currently doesn’t know how to share one Keystone in multiple envs 07:38:05 I’ll speak with the Fuel@OPNFV PTLs about it 07:38:30 great, it should be a feature of Fuel 07:38:39 latest is out last month 07:38:52 but for fuel plugin, we have to do by ourselves 07:38:57 not sure if they have this 07:39:04 no, they don’t 07:39:08 okay 07:39:11 but maybe they are willing to help us 07:39:29 in fact it will also benefit them by and large 07:39:39 for sure 07:39:59 ok, that's the information I would like to share and discuss 07:40:14 how to change the nickname back 07:40:21 lol 07:40:47 Dimtri 07:40:59 have you done "Submitting package information" 07:41:09 on pypi.org for kb 07:41:10 ? 07:41:14 not yet 07:41:18 there’s no release yet 07:41:39 to support pip install, need this 07:41:48 okay. will do it 07:42:09 #action register package in pypi.org 07:42:10 might need you people help in filling up the details 07:42:22 let’s finish with the present commits and tag the release 07:42:23 definately need help 07:42:29 then I’ll register it in pypi.org 07:42:40 will help as needed 07:42:58 before release taging 07:42:59 there are lot of information that we need to fill three 07:43:00 there 07:43:45 let's review and merge the tempest test cases first 07:43:50 now, If the current commits are through 07:43:54 then are we good to go? 07:44:07 I mean development wise for mitaka tagging? 07:44:17 and the bug reported 07:44:21 yeah 07:44:33 there are commits for each bug reported right? 07:46:12 yes 07:46:12 cool 07:46:12 for default configuration, I'll abandon it for Dimitri thinks it's no need 07:46:12 I wonder 07:46:12 I we have added openstackci user to pypi kingbird space 07:46:12 then shouldn’t it be published automatically? 07:46:12 but need to regirster in pypi,org first 07:46:12 https://pypi.python.org/pypi/kingbird/1.0.0 07:46:37 https://pypi.python.org/pypi/kingbird 07:46:37 you mean this? 07:46:37 yes 07:46:39 Package Index Owner: openstackci, sorantis 07:46:50 It should work like this, but not sure 07:47:19 but many things are missing 07:47:44 just replaced the version number 07:47:44 no pakage 07:47:44 license. downloaded link 07:47:44 Ashish, what exactly? 07:47:44 Name: Version: Author: Author email: Maintainer: Maintainer email: Home page: License: 07:47:47 Summary: Description: 07:47:57 Keywords: Platform: You should enter a full description here only if appropriate classifiers aren't available (see below). Download URL: Hidden: Bugtrack url: Requires: Provides: 07:48:12 that yes 07:48:17 I’ve just read New packages without any releases need to be manually registered on PyPI. 07:48:42 that's what Ashish mentioned 07:48:43 ok 07:48:46 yeah 07:48:50 Let’s register when we have a tag 07:49:07 before tag, dimitri 07:49:51 before release, so that a package is correspondent with the tag 07:49:59 ok 07:50:02 never done this 07:50:09 will do it this week 07:50:14 me too 07:50:16 me too :) 07:50:36 Guys, one more thing. 07:52:14 ok, let's conclude the meeting 07:52:14 please 07:52:14 I wanted to tell from last week. but forgot 07:52:14 nova keypair doesnot take tenant as argument 07:52:14 and also, keypair usage is not listed in nova limits 07:52:14 right now we are doing a len(nova.keypairs.list()) 07:52:14 nova ==> object created with admin user 07:52:26 so for all tenants, It will give count for number of keypairs in admin tenant 07:52:29 http://developer.openstack.org/api-ref-compute-v2.1.html#keypairs-v2.1 07:53:11 oh. It is not with CLI for sure 07:53:25 even the API call doesnot take any filter 07:53:32 CLI sometimes is later than API 07:54:00 but now also I am sure that 07:54:16 It's based on tenant 07:54:21 no 07:54:29 it is based on current nova object 07:54:43 the object with which the nova client object is created 07:55:05 You mean user? 07:55:06 # /v2.1/{tenant_id}/os-keypairs 07:55:17 here also, I feel you can change tenant_id 07:55:22 this is admin tenant Id 07:55:27 Lists keypairs that are associated with the account. 07:55:33 no, don't need admin api 07:55:41 can be general tenant 07:55:51 admin or any ID with which token is generated 07:55:53 Lists keypairs that are associated with the account. 07:56:06 you can use demo tenant in devstack to see if it works 07:56:08 account == the account with which token is created 07:56:54 the account is user_id 07:57:14 I will give use the count for the user with which the client object is created 07:57:20 see, 07:57:22 Eg: 07:57:29 like nova list we have search options 07:57:39 so that we can list servers for any tenants 07:57:44 we dnt have same for keypair 07:58:03 OK, understand, you mean no way to list other users keypair 07:58:04 keypair only lists current account/user list 07:58:09 exactly 07:58:24 this is an issue 07:58:27 It has to be there 07:58:48 yeah. There has to be bug on this 07:58:52 Even admin can't be able to list other user's keypair 07:59:03 exactly 07:59:14 We can discuss this in Austin with some core in Nova 07:59:47 to see if this is an issue, but from security perspective, I guess they intend to do so 07:59:48 but for our release? 08:00:06 use another quota items 08:00:06 we mention it in the release notes 08:00:15 okay. 08:00:16 fine 08:00:19 for test purpose 08:00:31 and this one just as what Dimitri proposed 08:00:31 yeah. have used ram, cores and instances count 08:00:31 ok 08:00:38 let’s close the meeting 08:00:43 ok 08:00:49 thanks for attending the meeting 08:00:49 let us review and close commits 08:00:52 see you next time 08:00:53 thanks guys 08:00:55 sure 08:00:59 #endmeeting