07:13:44 #startmeeting multisite 07:13:44 Meeting started Thu May 12 07:13:44 2016 UTC. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:13:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:13:44 The meeting name has been set to 'multisite' 07:13:58 #info Ashish 07:14:04 do you think that Sebastien will attend or not 07:14:10 #info joehuang 07:14:32 Guys, its 9 am cet 07:14:35 right? 07:14:40 I think so 07:14:45 yes 07:14:52 #info dimitri 07:15:05 I don’t think he will 07:15:18 Hi, Ashish, we are talking about the design summit in Berlin 07:15:29 okay 07:15:36 nice 07:15:58 so, we have to book a room there? decide Agenda? 07:16:23 And also to retrospect other use cases, to see if there is some other gaps in OpenStack 07:16:43 I asked in the M-L, but Raymond not answered yet 07:16:47 not sure 07:18:21 so, Dimitri please register some sessions in the design summit. If you and Ashish have other ideas, also submit please 07:18:30 ok 07:18:42 okay 07:19:00 #action register some sessions in the design summit in Berlin 07:19:34 ok, let's come back to today's agenda 07:20:21 #topic multisite deployment with centralized Keystone 07:20:47 Dimtri has done this I guess 07:20:50 Hi, Ashish, are you able to access the lab 07:20:52 Ashish will get access to the lab and install kb there 07:21:04 the m-r setup is in place 07:21:09 no fernet though 07:21:12 But I am not able to access the lab 07:21:23 I had to reopen ticket 07:21:24 I suggest we skip Fernet token 07:21:48 Fernet token is mainly to verify the use case one 07:21:55 we’ll see, i’ve no idea how to configure keystone, but perhaps it’s easy 07:22:00 which usecase? 07:22:12 UC1 07:22:15 but KB is able to run even without using Fernet token 07:22:24 Multisite identity service management? 07:22:29 yes 07:22:34 okay 07:22:40 It's not difficult, only need to do configuration 07:23:02 but the major concerns from mine is the automation for functest purpose 07:23:33 also, the automated deployment of kb with fuel 07:23:38 Do we need to dynamicly install a new multisite environment when functest for KB is triggered 07:24:07 to Ashish, +1 07:25:26 For other projects, usually will have a dynamically created SUT in functest (SUT, system under test) 07:25:51 or can we configure m-r environment upfront which can be pointed out by functest when running KB 07:26:35 You mean we have a static m-r envrionement, and just deploy KB when needed, and execute the test 07:27:15 something like that, I did not know how it happens in other projects 07:27:25 as you are saying there is SUT 07:27:34 then may be we need to follow that 07:28:45 to Dimitri, currently two region shared with same Keystone, and PKI or UUID token used? 07:29:06 UUID i think 07:29:11 need to check 07:29:27 It woks for test 07:30:17 to Dimitri, do you agree to skip the Fernet token configuration currently? 07:30:40 I’d first check if it’s easy to confiug 07:30:48 configure Fernet 07:30:50 ok 07:31:00 if so, then I don’t see why we should skip it 07:31:13 yes, if it is done then we can verify both 07:31:17 UC1 and KB 07:32:10 I found that at least 3 projects in Colorodo need mutlisite environments: Domino, IPv6 and Multisite 07:32:31 But each project using different installer 07:32:54 IPv6 Apex, Multisite now for KB is Fuel 07:33:21 Don't know which installer Domino wants to support 07:33:30 what’s domino? 07:33:41 Another project 07:34:07 https://wiki.opnfv.org/display/PROJ/Project+Proposals+Domino 07:34:28 https://wiki.opnfv.org/display/domino/Domino+Home 07:35:22 If each project need to support 4 installer ( Fuel, Apex, Compass4NFV, ), it's crazy 07:35:56 that’s not multisite’s concern 07:37:18 I think each installer should support multisite installation automation by themself, it's basic capability for other feature projects 07:37:57 +1 however none supports m-r yet 07:38:42 Fuel at least has the option to create multiple environments 07:38:59 that's the issue, gensis project is to set standard for installers to follow 07:39:04 which effectively could be used for m-r setup 07:39:08 yeah. the ISO installer 07:39:33 but how to connect the multisite envrioment with Functest 07:40:03 just point the test to a fixed keystone endpoint 07:40:09 tests* 07:40:25 assume there’s an existing deployment and use it 07:40:27 just mentioned that for single site functest, the OpenStack(and other components) as SUT are created dynamicly before the test 07:40:27 functest should have configurations 07:40:50 well, we could do the same, but different :) 07:41:15 we will considered a static m-r as SUT 07:41:42 creating 2 SUT dynamically shoudn’t be a problem. Centralizing keystone on the other hand can be hard 07:41:50 so, could Ashish help to check whether we can use pre-configured M-R enviroment as the SUT, just install KB / tempest for KB on demand 07:42:47 ashish will do the KB part. I thought you joe would look into functest and preconfigured m-r 07:42:52 to Dimitri, yes, "Centralizing keystone on the other hand can be hard" 07:43:09 am not sure with that 07:43:11 ok 07:43:19 I'll check that 07:43:26 I am still trying to understand the ecosystem 07:43:57 to Ashish, I 07:44:01 sorry 07:44:03 what works with whom, 07:44:08 :) 07:44:23 to Ashish, I will sent you the link of the material of Functest first 07:44:51 sent -> send 07:44:52 okay 07:45:23 #action look into functest to see if pre-configured m-r is possible 07:45:32 sorry I have to leave now 07:45:49 ok, we can conclude the meeting today 07:46:02 fine 07:46:24 thank you for attending the meeting 07:46:32 #endmeeting