08:17:12 #startmeeting multisite 08:17:12 Meeting started Thu Feb 25 08:17:12 2016 UTC. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:17:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:17:12 The meeting name has been set to 'multisite' 08:17:13 Hi DImitri 08:17:34 #topic rollcall 08:17:38 #info joehuang 08:17:43 #info Ashish 08:17:50 #info zhiyuan 08:17:59 #info zhipeng 08:18:36 #info dimitri 08:18:39 hi 08:18:42 Hello, just one information to share 08:19:22 before the meeting, just talked that the Glane community admit the use case for image replication between regions are legitimate use case 08:19:50 #info Malla 08:20:03 Hopefully this could be started in N release of OpenStack 08:20:10 in Glance? 08:20:38 Glance will provide "image cloning", "image import" and "image export" 08:21:01 ok, so in Kingbird 08:21:07 Now the "image import" is in refector 08:21:30 Kingbird can mainly focus on controll plane, but not to redirect the image bits 08:21:56 what do you mean 08:22:03 For example, replicate one image to n Regions, then clone this image to n Glance 08:22:24 yes 08:22:32 the image data bits will directly transfer from one Glance to others 08:22:45 export-import 08:22:51 otherwise, Kingbird has to touch images bits, it's awful 08:22:51 that will be provided by glance you are telling rigt? 08:22:58 Yes 08:23:12 fair enough 08:23:14 replicate image to n regions 08:23:18 But need developer to work on it, use case is accepted by one core 08:23:44 then it will not be part of Kingbird 08:24:08 I think it's good news at least, I'll forward the mail discussion to you 08:24:26 sure 08:24:33 There are still some work in Kingbird, but more lightweight 08:25:29 and will not become the bottleneck of data plane for the image data transfer 08:25:40 in Kingbird 08:26:04 yes 08:26:18 #topic environment setup in release C 08:26:19 but first let’s see if Glance actually implements it 08:26:25 yes 08:26:57 we need to define a limit set of features of Kingbird we want to bring in Rel C 08:27:04 How do you guys think about to setup a multisite environment in Release C. Currently all silo OpenStack installation 08:27:17 from past experience more conservative the better 08:27:34 To zhipeng, In release C quota management focus first 08:27:44 +1 08:27:50 yes 08:27:56 I think we can aim QM for Mitaka in OpenStack 08:28:04 and then for C 08:28:08 yes 08:28:15 agree 08:28:16 maybe preview release 08:28:30 however we do need to consider the test env for C 08:28:51 we need installers to support Multisite installation, and testing projects to support the testing 08:29:03 but before introducing Kingbird as a component in OPNFV we need to make sure there’s a MR environment in OPNFV 08:29:05 and we need to do it early on 08:29:05 maybe setup an test env ready for later release 08:29:24 "MR"? 08:29:29 multi-region 08:29:34 ok 08:30:07 yes need to talk to test team about that 08:30:08 yes MR env ready before introducing KB 08:30:53 more than kingbird we need to see if our other use cases are working 08:31:10 How many test labs/pods available now 08:31:14 multisite usecases 08:31:24 e.g. we have a design proposal for setting up centralized keystone 08:31:32 yes, at least identity management 08:31:49 so as a first step we can say: 08:31:52 for test labs, i think 3-4 labs are working 08:31:52 distribued KeyStone 08:32:02 - set up mutisite env 08:32:04 numbers of pods varies per lab 08:32:15 - set up centralized identity management 08:33:05 to Dimitri, which token format for KeyStone 08:33:46 our recommendation was to use PKI, right? 08:33:53 Fernet 08:33:53 fernet? 08:34:07 then Fernet 08:34:12 Fernet, for not so big like PKI 08:34:32 PKI could be used in limited regions 08:35:25 one question related to the lab setup 08:35:34 do we need to have a real multisite env? 08:35:44 for example to use Pharos projects 08:36:01 to have OPNFV labs across the world deploy Multisite 08:36:06 Does Pharos establish MR env? 08:36:21 no at the moment it just connects the labs i think 08:36:40 Multisite would be first to actually do so, if we decide to go this way 08:37:01 although I'm not favor of this, since this would be too much of work 08:37:06 coordination and such 08:37:28 yes. Would test team to verify this? 08:38:02 i will ask around Huawei OPNFV test teams to see what support we could get 08:38:28 I would recommend to do it in one lab, and setup a MR env 08:38:55 I’m ok with that 08:39:23 we don’t necessarily need multiple labs, we don’t test any WAN conncectivity related use cases 08:39:38 agree, in one lab is acceptable 08:39:56 sorantis yes 08:40:14 so Zhipeng, pls contact test team first to see if it's possible 08:40:29 joehuang sure 08:40:59 #action contact test team for multi-region env. establishment and test 08:41:51 so let's discuss this later after response we get 08:42:58 One more topic is about the volume replication 08:43:20 The Cinder team has re-design the volume replication 08:43:48 #link https://specs.openstack.org/openstack/cinder-specs/specs/mitaka/cheesecake.html 08:44:08 #link https://review.openstack.org/#/c/275797/ 08:46:09 this needs some proper reading :) 08:46:11 From the new design, we can renew the thinking in the 3rd option for VNF geo-site disaster recovery 08:47:05 yes, it's take time 08:47:16 it takes time to read 08:49:40 preservation of user data 08:50:09 so, what about the actual data? 08:50:37 the actual data is replicated by the backend 08:52:12 the patch was just uploaded Feb.4, and still in review process, 08:52:36 if merged, will it appear in M release? 08:53:22 I am not sure it can be merged, it's very limited time for M release, and it's only uploaded recently 08:53:24 yes. I guess 08:53:31 https://blueprints.launchpad.net/cinder/+spec/replication 08:53:39 It's a quite big refector 08:53:48 not sure.. 08:53:48 refactor 08:55:10 Please comment in this patch if needed 08:55:40 This patch was submitted by previous cinder PTL 08:56:51 So let's see if this patch can fulfill Multisite GR requirement 08:58:26 And last one, currently configuration sample file in Kingbird is maintained mannually 08:59:04 We can use oslo tools to generate the configuration sample file, but need some code and a patch 08:59:31 yes 08:59:50 I’ll have a look 09:00:00 We can do it later 09:00:20 okay. 09:00:28 just let's add it to the todo list to reminder 09:00:38 ok 09:00:43 other topics? 09:00:50 no from my side. 09:01:05 nope 09:01:08 Plese reviewt the commits 09:01:14 will do 09:01:28 so let's conclude the meeting 09:01:40 #endmeeting