Wednesday, 2017-05-31

*** joseppc has joined #openstack-cyborg07:54
*** joseppc has joined #openstack-cyborg07:54
*** joseppc has quit IRC09:01
*** adreznec has quit IRC09:04
*** adreznec has joined #openstack-cyborg09:05
*** joseppc has joined #openstack-cyborg09:08
*** joseppc has joined #openstack-cyborg09:08
*** jkilpatr has quit IRC10:47
*** jkilpatr has joined #openstack-cyborg11:00
*** mikeH has joined #openstack-cyborg12:07
*** crushil has joined #openstack-cyborg13:35
*** zhipeng_ has joined #openstack-cyborg15:00
zhipeng_hey folks15:03
jkilpatrzhipeng_, you have a few typos to address on your commit, linters seem to have calmed down15:08
zhipeng_ya I saw the comment, will fix that tmr :)15:11
zhipeng_anyways let me start the meeting15:11
zhipeng_catch the discussion as people talk15:11
zhipeng_#startmeeting openstack-cyborg15:12
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:12
openstackThe meeting name has been set to 'openstack_cyborg'15:12
zhipeng_jkilpatr about the packaging15:12
zhipeng_could you elaborate a little bit more ?15:12
zhipeng_#topic packaging options15:12
jkilpatrSo I was wondering how we easily setup the project while we're doing dev15:12
jkilpatrI 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
jkilpatrI don't know what other sort of distribution system we would use. So suggestions are welcome.15:13
zhipeng_pip would be the common practice for OpenStack, right ?15:14
jkilpatrI'm not actually sure never installed a project not packaged by someone for me...15:14
jkilpatrbut yes it's python I don't see what else they would use, except maybe some sort of heat / mistral stuff.15:15
crushilI use devstack for dev or RDO if I want to test it in a production style environment15:15
zhipeng_mistral got a different system ?15:15
zhipeng_hey crushil15:15
jkilpatrwell you could do it with mistral I have no idea if it's a good idea, never did anything with it myself.15:15
jkilpatranyways sounds like no one has an issue with pip15:16
zhipeng_yep I guess so15:16
zhipeng_#agreed pip for packaging options15:17
zhipeng_#topic development process15:17
zhipeng_I will address ChirsD and Justin's comment on the api spec15:18
zhipeng_so after spec freezes, how should we coordinate on the code development ?15:18
zhipeng_shall we write each part first ?15:19
jkilpatrI 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
jkilpatrit's important we have a good test/integration workflow15:20
jkilpatrum what about standards, I assume most of pep8 (longer line length limit maybe) + some unit test coverage?15:20
zhipeng_that would be reasonable15:21
zhipeng_what do you mean by start and put up a review quickly ?15:21
jkilpatrI 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:21
jkilpatrit'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:22
zhipeng_okey that I agree15:23
zhipeng_we will need multiple patches for the spec anyways15:24
zhipeng_no patch would be too small :P15:24
jkilpatrany 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:34
zhipeng_i don't have any other stuff on the plate15:36
zhipeng_so I will leave the channel open for another hour, then I'll close it15:39
jkilpatrcool, we can get the api commit in and meet next week to start putting things together sound good?15:40
crushilSounds good to me15:40
crushilDoes nova accelerators work well with virtIO today?15:42
zhipeng_I'm not aware Nova got vanila virtio based drivers15:43
zhipeng_for accelerators15:43
zhipeng_I think for Nova, it mainly means see if kvm got virtio support15:44
crushilOk. I'll look. I have created stubs for the code that I am going to fill in the next couple months15:44
zhipeng_i think as Justin suggested, if you got the stubs and basic virtio ops ready15:45
zhipeng_you could commit the patch15:45
zhipeng_and then iterate around it15:45
zhipeng_since we need the stub to align with agent/conductor/api15:45
*** joseppc has quit IRC15:49
*** jkilpatr has quit IRC16:47
*** zhipeng_ has quit IRC17:00
*** jkilpatr has joined #openstack-cyborg17:04
*** mikeH has quit IRC17:18
*** mikeH has joined #openstack-cyborg18:01
*** crushil has quit IRC19:14
*** crushil has joined #openstack-cyborg19:17
*** jkilpatr has quit IRC19:41
*** jkilpatr has joined #openstack-cyborg19:54
*** crushil has quit IRC20:02
*** joseppc has joined #openstack-cyborg20:17
*** joseppc has joined #openstack-cyborg20:17
*** crushil has joined #openstack-cyborg20:17
*** crushil has quit IRC20:18
*** crushil has joined #openstack-cyborg20:19
*** crushil has quit IRC20:23
*** crushil has joined #openstack-cyborg20:24
*** crushil has quit IRC20:26
*** crushil has joined #openstack-cyborg20:27
*** crushil has quit IRC20:32
*** crushil has joined #openstack-cyborg20:33
*** joseppc has quit IRC20:54
*** crushil has quit IRC21:39
*** mikeH has quit IRC21:50
*** jkilpatr has quit IRC22:23
*** mikeH has joined #openstack-cyborg22:24
*** jkilpatr has joined #openstack-cyborg22:38
*** mikeH has quit IRC22:50

Generated by 2.15.3 by Marius Gedminas - find it at!