01:02:23 #startmeeting Compass Status Syncup 01:02:25 Meeting started Thu Sep 10 01:02:23 2015 UTC and is due to finish in 60 minutes. The chair is xichengc. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:02:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:02:26 chigang: we are waiting on more detailed info on the status so that we can integrate the Compass metadata etc to support it 01:02:28 The meeting name has been set to 'compass_status_syncup' 01:02:51 #topic upstream ansible status 01:04:14 #info we have finished deploying AllinOne Openstack by OSAD 01:04:32 any further progress beyond all-in-one? 01:04:34 cool 01:04:46 #info but speed is too low 01:04:58 chigang could you provide us the paramters as we talked about? 01:05:12 chigang: we shall raise the question to the mailing list, on offline install option. 01:05:56 wshao: OSAD dont support offline installation 01:05:57 #action wshao and chigang to raise the installation speed question to the openstack-dev mailing list 01:06:05 xichengc: could you send a message with [Compass] and [Openstack-ansible-deployment] prefix? 01:06:33 wshao to the openstack-dev mailing list? 01:06:39 it does not support. But shall they support the use case of offline-install? 01:06:50 wshao: it is too slow installation in China, the network condition is not good for us 01:06:57 A common requirement for many data center installation. 01:07:46 yes. openstack-dev 01:08:30 wshao the question is "is OSAD responsible for supporting offline install or is it compass/fuel's responsibility to support it in our installers" 01:09:05 installers. but OSAD as a building block has to support it also. 01:10:29 OSAD will build repo, if installer do another, it may waste more time 01:10:39 xichengc, it's not who is responsible. There is a use case for offline install. The question is whether they plan to address the use case, or maybe someone can provide it to them 01:10:46 other than putting rpm repo urls and download links in config file instead of hardcoding it in ansible yml tasks, I am not sure what else they can do to support offline installation 01:11:00 the aim of OPNFV for installers is to support deployment offline, and compass4nfv is working on this 01:11:21 so I think OSAD need support also 01:11:24 ok. one way to do that is to have OSAD support two phases: build and install. 01:12:18 At build phase, internet access is assumed. but at install phase, it support offline. Let me study if that is possible, and then send out a question to them. 01:12:22 rockyg are they fully aware of this use case? Is there any installers that have already done it? 01:12:58 wshao: yes, build phase is not needed offline, but deployment need 01:13:00 xichengc: the requirement is valid, regardless of the current status. 01:13:15 chenshuai: thanks, 01:14:05 ok, let's move on 01:14:20 should i action it to you? 01:14:25 sure. 01:14:30 Don't know if they are aware. So, the way to write the email is to first state the use case and that it is a fairly common one. then to pose the question of whether they are planning to address it already or if a new spec needs to be written. 01:14:51 rockyg: thanks 01:14:54 thanks rockyg 01:15:09 move on to the topic of "plugin". 01:15:46 #action wshao to conduct research on the possibility of having two phases of installation: build and install 01:16:26 #topic status on OSAD as a compass plugin 01:16:56 current plugins are not cleanly separated from compass-core, Carl is looking into a better plugin mechanism. Fuel 6.0 has a clean way of adding plugin. It allows extensions from independent 3rd-party developers. 01:17:42 In our case, the Cobbler is tightly coupled from compass-core code, so is the snmp-based discovery, and Chef-based package installer. 01:18:13 hope to see some progress on this by next week. 01:19:01 thanks wshao. what about adding OSAD as a compass adapter? 01:19:21 a separate topic? 01:20:38 what's difference between as a plugin and as a adapter? 01:21:54 good question, a plugin is a code extension. where a single plugin may support more than one adapters. 01:22:27 eg., chef installer could be a plugin, but that pluging support two adapters => IceHouse chef cookbooks, and Kilo. 01:22:54 all right, thanks 01:23:05 ok. any other topics? 01:24:24 Has gyu received the paramters from baigk? 01:24:33 not yet 01:24:45 can we accelerate on that? chigang 01:24:52 xichengc: have an action on that. 01:25:01 baigk is leaving for apply passport 01:25:25 when he come back, I will tell to handle it 01:25:30 #action baigk to provide parameters to gyu for OSAD integration 01:25:34 thanks 01:25:35 thanks 01:26:04 maybe next month he will go to Santa Clara:) 01:26:27 welcome 01:26:45 great 01:26:54 wshao anything else? 01:29:48 wshao had to leave first 01:29:56 any other topics? 01:30:07 any other topics? 5.. 01:30:10 any other topics? 4.. 01:30:12 any other topics? 3.. 01:30:15 any other topics? 2.. 01:30:17 any other topics? 1.. 01:30:19 Thank you 01:30:21 #endmeeting