15:02:05 <zhipeng> #startmeeting openstack-cyborg 15:02:06 <openstack> Meeting started Wed Mar 22 15:02:05 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:10 <openstack> The meeting name has been set to 'openstack_cyborg' 15:02:21 <crushil> cool. hi everyone 15:02:42 <zhipeng> :) after bugging and sending hate mails to the infra team 15:02:45 <mpaolino> it seems it works hello! 15:02:45 <zhipeng> we got a bot lol 15:02:51 <NokMikeR> #info Michael Rooke, Nokia 15:02:56 <zhipeng> #info Howard 15:03:07 <mpaolino> #info Michele Paolino, Virtual Open Systems 15:04:32 <jkilpatr> #info Justin Kilpatrick, Red Hat 15:05:33 <zhipeng> Roman has a meeting conflict, so I guess we could goahead and start 15:05:42 <zhipeng> #topic BP discussion 15:06:08 <zhipeng> the bot just glitched .. 15:07:02 <zhipeng> anyways, #link https://review.openstack.org/#/q/project:openstack/cyborg+status:open 15:08:47 <zhipeng> so we have 5 BPs on the fly as we discussed, great progress 15:09:14 <zhipeng> I think jkilpatr crushil _gryf and I have done a few reviews 15:09:37 <zhipeng> I do encourage other folks to review them as well 15:10:16 <zhipeng> crushil for your BP, I agree with jkilpatr's last comment and do not have any further comments at the moment 15:10:25 <zhipeng> plz update the patch when you got time :) 15:10:57 <crushil> zhipeng: I will update the patch accordingly and will have a new patchset in the next day or two 15:11:21 <zhipeng> cool 15:11:46 <zhipeng> Roman just submitted his BP today, plz also review it 15:12:05 <crushil> ack 15:12:09 <zhipeng> so any other outstanding questions at the moment ? (we got all the time) 15:12:55 <jkilpatr> um I need to read the nova interaction page, but anyone care to summarize it? 15:13:57 <jkilpatr> ok this doesn't include what I was looking or skimming it. 15:14:12 <jkilpatr> so we can set schedule hints for Nova but how do we know when nova uses them is my question 15:14:19 <zhipeng> i think _gryf could summerize later when he's availabe, but I think it was captured on the etherpad Roman provided before 15:14:31 <jkilpatr> I'll have to look at that. 15:16:11 <zhipeng> #link https://etherpad.openstack.org/p/cyborg-nova-interaction 15:17:06 <jkilpatr> zhipeng, so nova asks us where to put the instance? 15:17:26 <jkilpatr> I thought that's exactly what we where not doing. with regards to previous discussion on this matter. 15:17:26 <zhipeng> in general, yes 15:17:34 <jkilpatr> hmm clearly I'm confused. 15:17:35 <zhipeng> how so ? 15:19:15 <jkilpatr> I need to read the last couple of times we talked about this. Anyways so we have to select an appropriate host, just one? Might result in some code duplication from the normal scheduler but not too bad hopefully. 15:21:25 <zhipeng> I think we will be using the placement module for the scheduling, won't be too much of code duplication I guess ? 15:21:53 <zhipeng> we need to select one host with the best fit accelerators 15:22:03 <zhipeng> do we have scenarios for more than one host ? 15:23:41 <jkilpatr> zhipeng, not at the moment. Just trying to think ahead 15:23:54 <zhipeng> understood :) 15:24:26 <zhipeng> well we need to review it thoroughly , so any question is welcomed 15:31:36 <zhipeng> goldenfri hey dude you there ? 15:34:21 <goldenfri> hey yea I'm here 15:34:52 <zhipeng> martial hooked me up with Blair on email about one months ago, but haven't heard from Blair yet 15:35:05 <zhipeng> Has he shared any update on the GPU side yet ? 15:35:19 <goldenfri> Last I heard they are still working on it 15:35:30 <jkilpatr> context for the rest of us? 15:36:00 <zhipeng> searching the meeting archive now ... 15:36:18 <goldenfri> I believe you are talking about GPU specs for the cloud declaration? 15:36:54 <zhipeng> there is a wiki page 15:37:30 <zhipeng> #topic requirements from scientific working group 15:37:39 <zhipeng> #link https://wiki.openstack.org/wiki/ScientificWGGPUs 15:37:51 <zhipeng> #link https://etherpad.openstack.org/p/scientific-wg-gpu-config-guide 15:38:23 <zhipeng> jkilpatr I think I mentioned in the last meeting that the SWG is now working on GPU requirements 15:38:40 <zhipeng> it would be great to have a summerized input from them 15:38:58 <zhipeng> Blair is the one that is contributing the efforts on GPU 15:39:12 <zhipeng> goldenfri he's from a univ in Aus right ? 15:39:26 <goldenfri> yes, IIRC 15:40:17 <goldenfri> I'll follow up with Martial today to see if there are any recent updates 15:40:22 <zhipeng> I think I will need to ping him again 15:40:32 <zhipeng> okey that'd be great, thx goldenfri 15:41:33 <zhipeng> #topic Boston Summit Sessions 15:42:13 <zhipeng> so Boston Summit will have Forum sessions 15:42:34 <zhipeng> suppose to be a substitute for the good old design summit 15:43:02 <zhipeng> I don't think we need a dedicated Cyborg session, we could piggyback on many of the available sessions 15:43:17 <zhipeng> one is, again, from SWG 15:43:30 <zhipeng> #link https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg 15:44:24 <zhipeng> or do we need a cross-project session with Nova ? 15:46:39 <jkilpatr> zhipeng, I think we should have a firm grasp of what we need to do with nova and what we want and who's going to do it before we do a cross team session 15:46:58 <zhipeng> jkilpatr good suggestion 15:46:59 <jkilpatr> so maybe a couple of weeks from now? when these blueprints are mature? 15:47:08 <zhipeng> I agree 15:47:30 <crushil> zhipeng: I agree with jkilpatr. We need to have things streamlined on our end before we propose such sessions 15:48:08 <zhipeng> Nova will have a placement session anyway, so we could use that occasion even if we don't propose our session 15:48:16 <zhipeng> crushil agree :) 15:48:43 <zhipeng> #topic AoB 15:49:09 <zhipeng> any other buisnees before I could set the miserable bot loose ? lol 15:52:35 <zhipeng> okey I guess we could conclude the meeting early today 15:52:44 <zhipeng> thx everyone for participation ! 15:52:51 <zhipeng> #endmeeting