15:00:45 #startmeeting openstack-cyborg 15:00:46 Meeting started Wed May 24 15:00:45 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng_. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:49 The meeting name has been set to 'openstack_cyborg' 15:00:52 morning everyone 15:00:56 #topic Roll Call 15:01:06 morning , evenning and afternoon :) 15:01:11 #info Howard 15:03:43 #info Justin 15:04:01 #info Rushil 15:05:23 anyone else ? 15:07:18 okey then let's proceed 15:07:40 we have 2 hours long meeting usually anyway :P 15:07:51 #topic BP Discussion 15:08:00 we should just have a 24 hour meeting and call it an IRC channel 15:08:06 hahaha 15:08:23 Anyways Rushil I think you need to wf 0 that commit then wf 1 it again to get the gates to rerun 15:08:25 automatic ending every 24 hours and then start again 15:08:46 i just did a recheck 15:08:56 sometimes the gate is just behaving weird 15:09:07 if they still don't work I'll go and talk to the people in #openstack-infra they are always helpful 15:09:30 conductor and agent look good. 15:09:45 cyborg nova needs a meeting of its own in my opinion 15:09:56 absolutely agree 15:10:28 i just +2 the agent one, looking at the conductor spec 15:11:16 I think the Cyborg/Nova spec might be served by having us play around with writing some code and trying stuff. But that's a cart/horse issue. 15:11:23 jkilpatr rushil I will nominate you guys as core reviewer as well today, so that we could move the development faster 15:11:53 cool, thanks zhipeng_ 15:11:57 jkilpatr you mean we do it in parallel ? 15:12:31 Is there a deadline for the code to get in? End of Pike? 15:12:42 zhipeng_, kinda I mean we start writing stuff with merged specs and play around with the nova stuff, when we have a decent idea of the pattern we want to use we can formalzie it and merge it. 15:12:55 I think the issue is that there are enough moving parts that's hard to think about in a totally abstract sense. 15:13:09 at the same time it's not really the best practice to do things like that. But whatever gets the code working 15:13:10 yes I agree 15:13:28 otherwise we would just be talking in abstraction 15:13:50 which in principle is fine, but right now we're talking in abstract circles on this spec.... 15:14:38 ah it seems I don't have the gerritbots here ..., but a quick update, jenkins shines upon the agent spec just now :P 15:14:51 jkilpatr agree 15:17:13 crushil, you started work on the driver? 15:18:00 jkilpatr, I am still deciding what hardware backend I should use as the prototype to start development 15:18:09 Any suggestions? 15:18:45 I asked this on the channel yesterday as well 15:18:53 ok this is a good subject to discuss 15:18:56 have you looked into virtio ? 15:19:18 how generic should the generic driver be? 15:19:48 maybe we need a stub driver that's literally nothing but stubs for all the required functions then a generic driver that's a very basic driver implementation for $something 15:20:39 Hmmm, would the "stub" driver require another spec? 15:20:48 nah it's just the current spec 15:21:12 I mean the current spec specifies driver concepts, the stub driver is just the simplest thing that implements those concepts but does nothing at all useful in life 15:21:23 I would think a ' 15:21:26 sorry 15:21:34 a 'generic' driver would be pci attachment though right? 15:22:05 That's my understanding 15:22:18 ok I see how virtio fits into that picture, just took some googlign. 15:22:49 sounds good, stub is lower priority (not that it should be any effort really) 15:23:21 What's the deadline for this development work though? End of Pike? 15:23:51 specs -> pike ; basic functionality -> qeens from what I understand 15:24:17 i was thinking basic functionality at the end of pike 15:24:21 at least we should try 15:24:46 isn't the pike deadline in like a month? or am I off 15:25:05 I guess that's possible 15:26:27 no that was the spec deadline 15:26:47 the end of cycle would be around Sep ? 15:26:49 Hmmm, that would be complicated. I will be on PTO between Mid June to Mid July. Gone for almost a month 15:27:16 August 28 is end of Pike I believe 15:27:28 anyways let's try to shoot for Sep finish 15:27:30 oh man we have more time than I thought 15:27:35 that's doable 15:27:37 Sep 11th is the PTG 15:27:39 ya 15:27:44 where is it this time? 15:27:49 lucky we are not doing actual releases :P 15:28:00 Denver 15:28:41 can't say for sure if I'll be there yet. 15:28:59 I'm still unclear on this, which backend should I use for the driver? VirtIO or a specific hardware? 15:29:23 well it's supposed to be generic, use virtIO 15:29:43 ok 15:30:07 i think virtio would be preferred choice now 15:34:04 crushil you might consider what justin suggested for the generic patch 15:34:14 gate god did not shine upon you today :P 15:34:19 Lol 15:34:28 two of J's specs are both merged 15:36:03 \0/ 15:36:40 I have experience pleasing Zull the linter god. 15:36:44 Zuul* 15:37:27 It's unable to install dependencies for some reason 15:37:50 yes but to what package? 15:38:25 Will probably do a reverify in a couple of hours 15:38:32 could not install deps [-r/home/jenkins/workspace/gate-cyborg-docs-ubuntu-xenial/test-requirements.txt, -r/home/jenkins/workspace/gate-cyborg-docs-ubuntu-xenial/requirements.txt] 15:40:43 crushil, test-requirements.txt is the file in cyborg repo 15:40:50 rebase your commit and see if an updated one works 15:41:07 or perhaps it's the other way around and my lack of rebasing means the old test-requirements.txt works and the new one doesn't 15:41:32 Well rebased it now. We'll see what it does 15:41:33 either way the correct soltuion is to open up a new dummy commit, see if the linters run, then edit test-requirements until they do, then merge that and rebase everything else 16:41:05 Anyways anything else? 16:41:13 I think we lose zhipeng again. 16:41:17 Lost* 16:41:28 i was lost .. 16:41:35 but managed to get back 17:03:35 endmeeting? 17:04:09 seems ok now 17:04:13 #endmeeting