Earlier  
Posted Nick Remark
#openstack-cyborg - 2017-10-11
15:01:50 crushil \o
15:01:51 zhipeng #info howard
15:01:59 crushil #info crushil
15:02:28 zhipeng anyone else here for our project meeting ?
15:02:32 mpaolino #info Michele Paolino
15:02:39 mpaolino hello Howard!
15:02:51 zhipeng oh hi Michele !
15:02:55 zhipeng long time no see
15:03:03 jkilpatr monring.
15:03:15 mpaolino yes, busy times on my side, now I'm back
15:03:15 jkilpatr #info jkilpatr
15:04:02 Li_ HI Howard :)
15:04:18 zhipeng Hi :)
15:04:36 zhipeng could you put your info down using the info command ?
15:04:56 Li_ #info Li
15:05:11 Li_ #info Li Liu
15:05:34 zhipeng thx :)
15:05:45 zhipeng helloway you there ?
15:06:01 helloway yeah
15:06:27 zhipeng info plz
15:06:29 jkilpatr wow busy this week.
15:06:54 helloway #info helloway
15:07:16 zhipeng #topic Official Project Application Status Report
15:07:31 zhipeng so again, thanks to everyone's hard work
15:07:40 zhipeng we are now an official project
15:08:08 zhipeng altho nobody has contacted me for the mascot yet :P
15:09:00 jkilpatr cheetah with cyborg parts. I won't stop staying it until it happens ;)
15:09:20 zhipeng let's try to make it happen XD
15:09:42 zhipeng #topic New Core Team member confirmation
15:09:46 crushil I already have an unofficial mascot that I have been using in my slides
15:10:03 zhipeng crushil do send me the slides :P
15:10:22 zhipeng so I sent out the nomination email for zhuli as new core reviewer one week ago
15:10:39 zhipeng no objection received, so I guess we reach consensus on that
15:10:56 jkilpatr we're adding zhuli as core right?
15:11:01 zhipeng yep
15:11:16 zhipeng i will labor him more :P
15:11:23 jkilpatr someone just put a sticky note that says 'better commit messages' on his monitor and it's all good.
15:11:33 zhipeng hahaha
15:11:37 zhipeng i will do that
15:11:42 zhipeng physically
15:12:12 zhipeng #agreed zhuli will be added as a new core reviewer
15:12:40 jkilpatr do we all need to run that command or just you?
15:13:01 zhipeng that'd just be me
15:13:13 zhipeng if it is vote yall need to run that cmd
15:13:41 zhipeng #topic patch discussion: https://review.openstack.org/#/q/project:openstack/cyborg+status:open
15:14:08 zhipeng so we have two major patches
15:14:21 zhipeng and three trolling patches not necessary need discussion
15:14:34 zhipeng (sign of success maybe ?)
15:14:51 crushil Btw zhipeng this is what I have been using
15:14:51 crushil https://imgur.com/gallery/pRdGp
15:15:21 jkilpatr nice.
15:15:24 zhipeng cool
15:15:50 zhipeng first up, spdk spec
15:15:53 zhipeng #link https://review.openstack.org/498690
15:16:13 zhipeng any more questions or we are good to go ?
15:16:29 jkilpatr let me give it one last glance.
15:16:59 zhipeng the floor is yours senator
15:17:35 jkilpatr looks good, but I think we need to focus on drilling down on these specs. we have high level stuff (nova interaction, spdk) but next is spec'ing standard traits/flavors in nova placement.
15:17:45 jkilpatr like format and such.
15:19:31 zhipeng agree
15:20:25 zhipeng but spdk/dpdk is less of a concern on traits, since they are not directly related to the compute resource
15:20:46 jkilpatr not saying it's a concern for that spec specifically, but in general both of these need follow up specs to flesh out details.
15:21:03 crushil What is the timeline for the implementation of the Cyborg Nova interaction spec?
15:21:06 zhipeng oh definitely
15:21:35 zhipeng Q-2 if we are fast enough ?
15:22:02 jkilpatr it's just calling existing placement api stuff, hard part is getting the format for the tags we want to use then keeping track of all of them
15:22:26 crushil And don't we need to have a patch in Nova as well?
15:22:53 jkilpatr the live whitelist addition?
15:22:57 zhipeng we agreed in denver that we should experiment with nova extension first
15:23:08 zhipeng to get a sense of what we want to add
15:23:30 zhipeng attach/detach for hotplug to start with
15:23:57 zhipeng then we could have a formal proposal to the nova team
15:24:02 Li_ basically issue virsh attach in libvirt right?
15:24:10 zhipeng this is what we think nova api should be extended and why
15:24:31 zhipeng Li_ that would be the nova part
15:24:35 crushil If we are planning to have a patch in Nova, then we should be conservative as the Nova queue is already overloaded with patches and the review time will be months if not weeks
15:24:46 jkilpatr didn't think of that.
15:25:03 jkilpatr at the same time we don't want to make a nova patch first and then figure out we don't like it's workflow once we write the other code...
15:25:15 zhipeng yes exactly
15:25:18 crushil +1
15:25:33 zhipeng so what we want to have out of Queens is to function with placement
15:25:48 zhipeng and an unofficial hacky extension of nova
15:25:53 zhipeng to make it e2e working
15:26:00 crushil And have a semblance of a driver so that vendors have something tangible to play with
15:26:10 zhipeng then we could discuss with nova team about the api extension in Rocky
15:26:19 zhipeng yes crushil
15:26:51 crushil We basically want to end the vendor dependence on Nova for accelerators by the end of this release
15:27:09 zhipeng provide a leeway
15:27:12 zhipeng so to speak
15:27:27 zhipeng #link https://review.openstack.org/508572
15:27:48 zhipeng btw the conversation so far is about this magnificent beast
15:27:57 jkilpatr lol
15:30:37 zhipeng i will work with zhuli to add more resource provider related info to the spec
15:32:07 zhipeng jkilpatr for the spdk spec if it is ok plz green light it so that helloway could start code implementation
15:32:18 jkilpatr sounds good. I'm not sure we want the placement stuff in the same spec as high level nova cyborg interaction.
15:32:43 zhipeng and #action zhuli and howard will provide additional info on resource provider/trait design for the nova interaction spec
15:32:47 jkilpatr ok +3
15:33:26 zhipeng jkilpatr let's try and figure out then
15:33:34 crushil +3?
15:33:54 jkilpatr +2 cr +1 wf

Earlier   Later