01:01:58 <mikal> #startmeeting OpenStack core meetup 01:01:59 <openstack> Meeting started Tue Oct 22 01:01:58 2013 UTC and is due to finish in 60 minutes. The chair is mikal. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:02:00 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:02:03 <openstack> The meeting name has been set to 'openstack_core_meetup' 01:02:29 <clarkb> ++ to using irc for questions and discussion 01:02:55 <mikal> #info The hangouts URL is https://plus.google.com/hangouts/_/4661a0dc1ea9e2127f00a97cd86fe68d017aae46?authuser=0&hl=en 01:03:05 <zehicle> reference material http://robhirschfeld.com/2013/08/13/openstack-core-positions/ 01:03:34 <mikal> clarkb: I am not sure that's a battle I can win... 01:03:49 <mikal> But you can ask questions here if you want and I will try and relay to hangouts 01:04:17 <reed> it's noisy in my room 01:04:29 <clarkb> mikal: zehicle mentioned using IRC for questions and discussion 01:05:01 <clarkb> in any case I will follow along best I can here 01:06:21 <mikal> clarkb: fair enough 01:08:31 <mikal> Rob is jsut doing an intro at the moment 01:12:35 <mikal> Queued question: why do we need core at all? What do core projects get? What does it mean to be core? 01:17:19 <clarkb> I am curious about what "designated code frameworks" are and how they differ from the open reference implementations 01:18:13 <lifeless> clarkb: AIUI its a circuitous way of saying 'whats in the openstack/' git trees 01:18:23 <lifeless> clarkb: but we should get clarification of that :) 01:18:36 <lifeless> mikal: ^ 01:28:40 <mikal> Queued question: how do we handle vendor patchsets on top of "designated code"? 01:30:29 <mordred> zehicle: I can't join the hangout - non-free software, laptop that needs to be secure for openstack-infra purposes ... BUT 01:30:42 <lifeless> mordred: wintendo VM ! 01:30:44 <mordred> zehicle: I do still want clarification on the point you've got up in there about alternate implementations 01:31:01 <lifeless> mordred: can you hear us? 01:31:04 <zehicle> can you hear? 01:31:04 <mordred> zehicle: which I _believe_ you intend to be referring to the plugin architecture without saying plugin 01:31:07 <mordred> I cannot 01:31:14 <mordred> is there a dial-in number? 01:31:19 <lifeless> mordred: how are you aware of whats being shown ? 01:31:27 <mordred> I know zehicle's material :) 01:31:27 <clarkb> for the recent queued question why wouldn't vendor patchsets go through the normal code review process? 01:31:47 <mordred> lifeless: and http://robhirschfeld.com/2013/08/13/openstack-core-positions/ 01:32:06 <zehicle> https://secure.join.me/876-719-301 01:32:07 <zehicle> try this 01:32:25 <mordred> zehicle: thanks! 01:32:46 <mordred> zehicle: but it reads to me still like you're suggesting that someone can reimplement the API completely clean 01:33:01 <mordred> ths is in response to "Vendors may substitute alternate implementations" 01:33:04 <mordred> other than that - I love it 01:37:16 <mikal> So to summarize that tangent, "required code" would be somehting like the nova core code, and replacable bits are things like nova hypervisor drivers. 01:37:48 <mikal> ie. you might be required to run nova-api, nova-scheduler, etc, etc but with your choice of hypervisor 01:38:40 <lifeless> mikal: AIUI yes. 01:38:51 <lifeless> mikal: but are you running nova-api if you patch it? 01:39:07 <mikal> I think we dig into that later in the meeting, hence the queued question bit 01:39:17 <lifeless> mikal: I know :) 01:42:10 <mordred> my god. now I'm looking at your faces 01:58:38 <clarkb> before I forget, I think it is also worth mentioning that 6.B while noble doesn't seem enforceable 02:00:07 <zehicle> there's an expectation that the market will punish people 02:12:17 <zehicle> designated upsteam code 02:25:03 <reed> I need to go in 3 min 03:50:48 <zehicle> #end 04:12:27 <mikal> #endmeeting