15:12:06 #startmeeting openstack-cyborg 15:12:07 Meeting started Wed May 31 15:12:06 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng_. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:12:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:12:10 The meeting name has been set to 'openstack_cyborg' 15:12:22 jkilpatr about the packaging 15:12:30 could you elaborate a little bit more ? 15:12:36 #topic packaging options 15:12:52 So I was wondering how we easily setup the project while we're doing dev 15:13:19 I don't know what you guys have for test environments but I can stand them up and tear them down very easily, so an ansible playbook that just uses pip to install the components would make me happy. 15:13:39 I don't know what other sort of distribution system we would use. So suggestions are welcome. 15:14:19 pip would be the common practice for OpenStack, right ? 15:14:42 I'm not actually sure never installed a project not packaged by someone for me... 15:15:07 but yes it's python I don't see what else they would use, except maybe some sort of heat / mistral stuff. 15:15:29 I use devstack for dev or RDO if I want to test it in a production style environment 15:15:41 mistral got a different system ? 15:15:45 hey crushil 15:15:59 well you could do it with mistral I have no idea if it's a good idea, never did anything with it myself. 15:16:10 anyways sounds like no one has an issue with pip 15:16:19 yep I guess so 15:17:14 #agreed pip for packaging options 15:17:40 #topic development process 15:18:31 I will address ChirsD and Justin's comment on the api spec 15:18:51 so after spec freezes, how should we coordinate on the code development ? 15:19:07 shall we write each part first ? 15:20:10 I think we should start and put up a review quickly, wait until it's possible to use all the different reviews together and then merge them and move on from there. 15:20:18 it's important we have a good test/integration workflow 15:20:48 um what about standards, I assume most of pep8 (longer line length limit maybe) + some unit test coverage? 15:21:12 that would be reasonable 15:21:26 what do you mean by start and put up a review quickly ? 15:21:55 I mean don't go off and code everything then put it up for review. Ideally we start playing around with and testing each others code very early. 15:22:24 it's kinda embarassing to put up unfinished stuff, everyone want's to come in and micdrop great code. But it's not the best way to work. 15:23:30 okey that I agree 15:24:30 we will need multiple patches for the spec anyways 15:24:57 no patch would be too small :P 15:34:20 any other business? I know we still haven't managed to fully define the nova workflow but I need to find time to play with that, ideally with skeleton versions of the rest of cyborg, which is what we agreed on last week. 15:36:40 i don't have any other stuff on the plate 15:39:22 so I will leave the channel open for another hour, then I'll close it 15:39:59 Ok 15:40:01 cool, we can get the api commit in and meet next week to start putting things together sound good? 15:40:14 Sounds good to me 15:42:33 yes 15:42:56 Does nova accelerators work well with virtIO today? 15:43:33 I'm not aware Nova got vanila virtio based drivers 15:43:39 for accelerators 15:44:17 I think for Nova, it mainly means see if kvm got virtio support 15:44:21 Ok. I'll look. I have created stubs for the code that I am going to fill in the next couple months 15:45:20 i think as Justin suggested, if you got the stubs and basic virtio ops ready 15:45:29 you could commit the patch 15:45:35 and then iterate around it 15:45:58 since we need the stub to align with agent/conductor/api 22:25:27 #endmeeting