| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2018-04-25 | |||
| 14:35:45 | Sundar | •An admission controller inserts an init container on seeing a FPGA resource. | |
| 14:35:59 | Sundar | •The scheduler picks a node based on the requested region type (and ignores the bitstream ID). | |
| 14:36:10 | Sundar | •The init container pulls the bitstream with that ID from a bitstream repository (mechanism TBD) and programs the selected device. | |
| 14:37:20 | Sundar | I have heard that, if we give a higher security context to the init container for programming, it may affect other containers in the same pod. I am still trying to find evidence for that | |
| 14:37:46 | zhipeng | lol this is just too complicated | |
| 14:38:07 | zhipeng | thx Sundar I think we have a good understanding of the status qup | |
| 14:38:10 | zhipeng | quo | |
| 14:38:18 | Sundar | Zhipeng, more complicated than other proposals out there? ;) | |
| 14:38:25 | zhipeng | anyone else got questions regarding k8s ? | |
| 14:38:54 | zhipeng | if you are attending KubeCon we could meet f2f, and give them hell XD | |
| 14:39:09 | Sundar | lol | |
| 14:41:04 | Li_Liu | if you guys have any dial-in-able meeting during kubecon, please loop us in | |
| 14:41:36 | shaohe_feng_ | yes, loop us in | |
| 14:42:02 | zhipengh[m] | Okey I will give a howler if a bridge is available | |
| 14:42:33 | zhipengh[m] | Seems like my PC irc client just died | |
| 14:43:05 | zhipengh[m] | #topic Sub team arrangements | |
| 14:46:08 | zhipeng | phew | |
| 14:46:13 | Sundar | :) | |
| 14:46:41 | zhipeng | cell phone irc bouncer crashed just now | |
| 14:46:57 | zhipeng | moving on | |
| 14:47:05 | zhipeng | #topic subteam arrangments | |
| 14:47:35 | zhipeng | okey so given recent events, I think it is necessary to reorg the subteams | |
| 14:48:23 | zhipeng | and also encourage subteam to organize their specific meetings | |
| 14:48:30 | zhipeng | for specific topics | |
| 14:48:45 | zhipeng | so I would suggest shaohe to help lead the driver subteam | |
| 14:49:10 | zhipeng | work with our Xilinx and lenovo colleagues on FPGA and GPU driver in Rocky | |
| 14:49:29 | shaohe_feng_ | Ok. | |
| 14:49:40 | zhipeng | Li Liu help lead the doc team, to work with our CMCC member and others to make documentation as good as your spec :) | |
| 14:49:49 | Li_Liu | sure | |
| 14:49:59 | zhipeng | I will keep on the release mgmt side | |
| 14:50:35 | zhipeng | shaohe_feng_ you can sync up with Chuck_ on a meeting time more suited for US west coast | |
| 14:50:55 | zhipeng | mainly China morning times I guess | |
| 14:51:13 | shaohe_feng_ | zhipeng: what is Chuck_? | |
| 14:51:28 | Chuck_ | I am Chuck_ :-) | |
| 14:51:37 | Chuck_ | Hi Shaohe, this is Chuck from Xilinx | |
| 14:51:44 | Sundar | lol | |
| 14:51:46 | shaohe_feng_ | Chuck_: hello | |
| 14:51:46 | Chuck_ | I work from US west time | |
| 14:51:54 | zhipeng | I will add Chuck_ into our wechat group as well | |
| 14:52:13 | zhipeng | talk in Chinese :) | |
| 14:52:47 | Li_Liu | count me in for those driver meeting shaohe_feng_ | |
| 14:52:52 | Li_Liu | :) | |
| 14:52:53 | Chuck_ | yes, look forward to working with you. | |
| 14:53:20 | shaohe_feng_ | Li_Liu: OK. | |
| 14:53:21 | zhipeng | and subteam plz send report to the mailing list, you can decide whether it is bi-weekly or weekly | |
| 14:53:26 | zhipeng | or monthly even | |
| 14:53:28 | zhipeng | up to you | |
| 14:53:56 | Sundar | Is it all WeChat in Chinse then? ;) I can join if that helps | |
| 14:54:10 | zhipeng | it is for the China region devs :P | |
| 14:54:20 | zhipeng | all in Chinese and crazy emoticons :P | |
| 14:54:24 | Li_Liu | WeChat has a translation feature tho :) | |
| 14:54:39 | shaohe_feng_ | Sundar: we speak Chinese there. :) | |
| 14:54:53 | shaohe_feng_ | Sundar: you can learn Chinese. | |
| 14:55:24 | Sundar | OK :) My daughters learnt Mandarin. I should have joined them | |
| 14:55:55 | zhipeng | haha will learn a lot | |
| 14:56:34 | Sundar | :) Do we have alignment on what use cases we will deliver in Rocky? | |
| 14:57:11 | zhipeng | CERN HPC PoC could be the one for GPU | |
| 14:57:12 | Sundar | Can we say we will deliver AFaaS pre-programmed, and FPGA aaS with request time programming? These are the simplest ones, and many customers want that | |
| 14:57:36 | Sundar | Zhipeng, yes, GPU POC too | |
| 14:57:41 | zhipeng | Sundar that is something we should be able to deliver | |
| 14:57:47 | zhipeng | for FPGA | |
| 14:57:47 | shaohe_feng_ | Sundar: oh, do we will have same RC name for VGPU and FPGA, and other accelerators in Rocky release? | |
| 14:58:49 | Sundar | Shaohe, yes our agreemnt with Nova is to use a generic RC for all accelerators | |
| 14:59:04 | Sundar | as in the spec | |
| 14:59:21 | Sundar | DO we have kosamara here? | |
| 14:59:34 | Sundar | Any input on the spec from GPU perspective? | |
| 14:59:58 | shaohe_feng_ | Sundar: But I'm worry about without nest provider. | |
| 15:00:28 | Sundar | Shaohe, without nRP, we will apply the traits etc. to the compute node RP | |
| 15:00:46 | Sundar | Do you see problems in doing that? | |
| 15:01:07 | shaohe_feng_ | how do we distinguish vGPU and FPGA in one host？ | |
| 15:02:02 | Li_Liu | hello? | |
| 15:02:08 | NokMikeR | welcome back | |
| 15:02:12 | Li_Liu | everyone quit? | |
| 15:02:21 | NokMikeR | net split a glitch in the matrix. | |
| 15:02:44 | Sundar | All traits will get mixed in the compute node. So, a flavor asking for resource:CUSTOM_ACCELERATOR=1 and trait:CUSTOM_GPU_<foo> will come to cyborg which needs to choose a GPU based on its Deployables | |
| 15:02:54 | Sundar | Li_Liu, I am still here :) | |
| 15:03:24 | shaohe_feng_ | Sundar: for example, we make a FPGA traits and GPU traits on host provider. | |
| 15:03:33 | zhipeng | okey this is a crazy night | |
| 15:03:42 | shaohe_feng_ | Sundar: and there is a one GPU and one FPGA | |
| 15:03:48 | Sundar | Sorry, i have another call at this time | |
| 15:04:04 | shaohe_feng_ | firstly we consume one FPGA | |
| 15:04:08 | Sundar | Shaohe, can we continue another time? | |
| 15:04:14 | shaohe_feng_ | Sundar: OK. | |
| 15:04:34 | zhipeng | okey moving on | |
| 15:04:45 | zhipeng | #topic critical rocky spec update | |
| 15:05:09 | zhipeng | xinran_ are you still around ? | |
| 15:05:48 | xinran_ | Yes I’m here | |
| 15:06:06 | zhipeng | could you provide a brief update on the quota spec ? | |
| 15:09:31 | xinran_ | Ok. Like we discussed with xiyuan, I think we should do the usage part first, so I want to separate the spec into two part. | |
| 15:09:45 | xinran_ | What do you think | |
| 15:11:13 | zhipeng | makes sense | |
| 15:11:24 | zhipeng | have you already updated it as two parts ? | |
| 15:12:20 | xinran_ | Not yet will update the usage part in this week | |
| 15:12:40 | zhipeng | sounds great :) | |
| 15:13:10 | zhipeng | #action xinran to update the quota spec into two parts and complete the usage one first | |
| 15:13:15 | xinran_ | For the limit part, i think it still need more discussion with xiyuan | |
| 15:13:29 | zhipeng | no problem | |
| 15:13:35 | Li_Liu | So that we will have 2 spec on this in stead of 1 right? | |
| 15:13:42 | zhipeng | yep | |
| 15:13:53 | zhipeng | but the limit one should be rather simple | |