09:10:46 #startmeeting multisite 09:10:46 Meeting started Thu Nov 5 09:10:46 2015 UTC. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:10:46 Useful Commands: #action #agreed #help #info #idea #link #topic. 09:10:46 The meeting name has been set to 'multisite' 09:11:17 #info zhipeng 09:11:28 first, I want to share the progress of the use case 2&3 bp in OpenStack summit 09:11:56 for quiesce.unquiesce, Nova team seems to accept to expose the API 09:12:08 the spec is working in progress 09:12:37 also talk to the cinder core about the disater revovery for using volume replication 09:13:33 and the core think the metadate filed in cinder for customization could be queried first 09:13:59 then to save the ref for disaster recover purpose, may have to work step by step 09:14:18 cross Neutron L2 networking not discussed in the summit yet. 09:14:43 neutron is a mine field :) 09:15:03 Dimitri, would you pls to contact some guys in Neutron for this? 09:16:08 I’ll try to reach them 09:16:09 And for the use case 1&2&3, the deadline has passed, would you mind to give +2 if no more comment for the output 09:16:29 yes, I will review. sorry for delay. 09:17:18 The ticket registered by Chris has been divided into smaller ticket for documentation about user guide and configuration 09:17:49 so we can pick some ticket to work by voluntering 09:18:34 And for Kingbird, we need to have weekly or bi-weekly meeting in OpenStack channel 09:19:31 We need initial core member for review and +2 +1 to merge patch 09:19:47 How do you think about the operation of Kingbird 09:20:13 in what sense? 09:20:45 shall we operate in stealth mode for a while ? 09:20:46 meeting, core member, code merge approve 09:20:54 or a full blown operation 09:21:05 from my side :P 09:21:06 what is strealth mode 09:21:25 meaning lay low 09:21:27 quietly 09:21:30 we can always make things more complicated :) 09:21:47 for the time being let’s focus on getting the code in 09:21:53 and make the build pass 09:22:18 I reckon, we lay low, just to grow some meat 09:22:59 Ok, but the code approve needs two core's +2, one +1 for workflow 09:23:13 so if lay low, then we propably don't need per week meetings 09:23:23 and joe and you could serve as the core 09:23:24 let's ok 09:23:26 for +2s 09:23:30 yes, we can just email if necessary 09:23:50 Should it be visible in OpenStack community 09:24:05 you mean the emails? 09:24:22 [openstack-dev][kingbird] ? 09:24:24 That's also a question, do we want this project to be OpenStack official project at last 09:24:46 I guess we’ll find out as we proceed 09:25:02 for now we know that some things are missing in OpenStack 09:25:05 if we want it become official project, we have to make it visisble 09:25:37 We can do it later, as the project has a little solid base 09:25:40 i don't think we need to do it like official projects right now 09:25:44 yes 09:25:56 +1 09:26:01 OK 09:26:09 we could always discuss via opnfv ml 09:26:17 So let's still talk in the OPNFV channel first 09:26:51 And first, Dimitri and I serve for the core reviewer 09:27:03 that should be fine 09:27:07 <_zhiyuan> ok 09:27:20 I was thinking more or less the same 09:27:36 we need collobration 09:27:54 but no too much politic 09:28:10 work the code :) 09:28:32 What's missing in my idea. Yes, I also like coding, make it work 09:29:48 ok 09:30:07 so why does the build fail? 09:30:22 pep8, doc gate ok 09:30:34 but the python27-gate failed 09:30:54 <_zhiyuan> py27 fails to run, there may be something wrong with the tox config 09:31:02 maybe the requirements conflict with OpenStack. I fixed some 09:31:30 But found other requirement conflict still there 09:32:20 I'll try to fix it tomorrow. I have to leave now. Dimitri, please review and let's close use case 1&2&3 ASAP, then do upstream work 09:32:55 ok 09:33:09 thanks for your time in the meeting. 09:33:14 #endmeeting