Earlier  
Posted Nick Remark
#openstack-cyborg - 2018-03-14
15:23:31 zhipeng Dutch
15:23:35 Dutch Okay ^ works
15:30:05 edleafe I have another meeting, so I have to drop
15:30:11 zhipeng thx ed !
15:41:35 zhipeng #action Sundar propose the weigher spec
15:42:56 zhipeng #action Jinghan python-cyborgclient, quota engine, experiment with oslo.limit
15:43:05 alex_xu sorry, I have to drop, thanks all!
15:44:29 zhipeng #action Li Liu programmability spec
15:45:08 kosamara Sorry, I have to go as well. Thanks!
15:45:32 zhipeng #action Dutch for Xilinx driver
15:46:14 zhipeng #action zhuli for os-acc spec
15:46:55 zhipeng #action yumeng create cyborg-specs repo, help polishing the docs
15:47:11 zhipeng #action metadata Li Liu spec
15:51:12 zhipeng #info spec freeze April 20 week
15:51:26 zhipeng #info driver freeze Jun 08 week
15:51:40 zhipeng #info feature freeze Jul 27 week
15:51:53 zhipeng #info oslo.limit could be an exception
15:52:48 zhipeng #info new repos (cyborgclient, cyborg-spec, os-acc) should be created as soon as possible
15:53:29 Li_Liu https://review.openstack.org/#/c/552734/
15:53:50 Li_Liu please help to review this change :)
15:54:09 zhuli sure
15:55:22 zhipeng #endmeeting
15:55:25 openstack Meeting ended Wed Mar 14 15:55:22 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:55:26 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-03-14-14.07.html
15:55:27 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-03-14-14.07.txt
15:55:28 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-03-14-14.07.log.html
#openstack-cyborg - 2018-03-15
16:13:41 openstackgerrit Nguyen Van Trung proposed openstack/cyborg master: Remove etc/cyborg/cyborg.conf.sample from project https://review.openstack.org/553460
16:21:06 openstackgerrit Nguyen Van Trung proposed openstack/cyborg master: Add default configuration files to data_files https://review.openstack.org/553463
20:51:18 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented all the APIs specified in cyborg-fpga-model-proposal.rst Added table Attribute Added Objects physical_function and virtual_function Added foreign key constrain for deployable to accelerator Added an API deployable_get_by_filters Added corespon https://review.openstack.org/552734
#openstack-cyborg - 2018-03-16
02:00:48 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented all the APIs specified in cyborg-fpga-model-proposal.rst https://review.openstack.org/552734
03:33:07 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented the Objects and APIs for vf/pf https://review.openstack.org/552734
03:58:37 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented the Objects and APIs for vf/pf https://review.openstack.org/552734
05:10:13 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented the Objects and APIs for vf/pf https://review.openstack.org/552734
05:37:02 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented the Objects and APIs for vf/pf https://review.openstack.org/552734
05:47:40 Sundar Hi Howard, if you are here, can we chat briefly?
06:05:27 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented the Objects and APIs for vf/pf https://review.openstack.org/552734
13:03:04 kosamara Hi! I tried getting cyborg on my devstack, but 'stack.sh' fails to start up the cyborg services. They complain that:
13:03:13 kosamara Exception: Versioning for this project requires either an sdist tarball, or access to an ups┤
13:03:15 kosamara tream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to ┤
13:03:17 kosamara pbr.version.VersionInfo. Project name cyborg was given, but was not able to be found.y
13:04:41 kosamara I've included the cyborg plugin in devstack's "local.conf" like this:
13:04:50 kosamara "enable_plugin cyborg git://git.openstack.org/openstack/cyborg stable/queens"
13:05:30 kosamara Does anyone have any suggestion on the cause and what to do? Thanks!
13:22:53 zhipengh[m] Hi kosamara , there is a bug with devstack and a patch is on the way to address that
13:33:13 kosamara thanks zhipengh!
#openstack-cyborg - 2018-03-19
15:23:39 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented the Objects and APIs for vf/pf https://review.openstack.org/552734
19:24:25 openstackgerrit Li Liu proposed openstack/cyborg master: Implemented the Objects and APIs for vf/pf https://review.openstack.org/552734
#openstack-cyborg - 2018-03-20
21:54:29 openstackgerrit Sundar Nadathur proposed openstack/cyborg master: Specification for Cyborg/Nova interaction for scheduling. https://review.openstack.org/554717
#openstack-cyborg - 2018-03-21
03:07:51 openstackgerrit YumengBao proposed openstack/cyborg-specs master: Create an initial cyborg-specs repository using cookiecutter https://review.openstack.org/554766
14:00:17 zhipeng #startmeeting openstack-cyborg
14:00:21 openstack Meeting started Wed Mar 21 14:00:17 2018 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:22 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:25 openstack The meeting name has been set to 'openstack_cyborg'
14:00:41 zhipeng #topic Roll Call
14:00:49 zhipeng #info Howard
14:01:11 shaohe_feng_ hi zhipeng
14:01:18 kosamara hi!
14:01:23 zhipeng hi guys
14:01:33 crushil \o
14:01:35 zhipeng please use #info to record you names
14:01:48 kosamara #info Konstantinos
14:01:50 Sundar #info Sundar
14:02:15 crushil #info Rushil
14:02:57 shaohe_feng_ #info shaohe
14:05:02 Sundar Do we have a Zoom link?
14:05:06 zhipeng let's wait for a few more minutes in case more people will join
14:05:14 zhipeng Sundar no we only have irc today
14:05:23 Sundar Sure, Zhipeng. Thanks
14:06:18 Yumeng__ #info Yumeng__
14:09:45 zhipeng okey let's start
14:09:57 zhipeng #topic CERN GPU use case introduction
14:10:08 zhipeng kosamara plz takes us away
14:10:41 kosamara I joined you recently, so let me remind that I'm a technical student at CERN, integrating GPUs into our openstack.
14:10:56 kosamara Our use case is computation only at this point.
14:11:31 kosamara We have implemented and are currently testing a nova-only pci-passthrough.
14:12:18 kosamara We intend to also explore vGPUs, but they don't seem to fit our use case very much: licensing costs, limited CUDA support (nvidia case both).
14:12:47 kosamara At the moment the big issues are enforcing quotas on GPUs and security concerns.
14:13:07 kosamara 1. Subsequent users can potentially access data on the GPU memory
14:13:39 kosamara 2. Low-level access means they could change the firmware or even cause the host to restart
14:14:23 kosamara We are looking at a way to mitigate at least the first issue, by performing some kind of cleanup on the GPU after use
14:14:55 kosamara But in our current workflow this would require a change in nova.
14:15:13 kosamara It looks like something that could be done in cyborg?
14:15:42 zhipeng i think so, i remember we had similar convo regarding clean up on FPGA in the PTG
14:15:43 Li_Liu are you try to force a "reset" after usage of the device?
14:16:02 kosamara Reset of the device?
14:16:32 kosamara According to a research article, in nvidia's case performing a device reset through nvidia-smi is not enough for the data leaks.
14:16:42 Li_Liu something like that. like Zhipeng said, "clean up"
14:16:49 kosamara - article: https://www.semanticscholar.org/paper/Confidentiality-Issues-on-a-GPU-in-a-Virtualized-E-Maurice-Neumann/693a8b56a9e961052702ff088131eb553e88d9ae
14:17:19 kosamara The additional complexity in pci passthrough is that the host can't access the GPUs (no drivers)
14:17:39 shaohe_feng_ so once the GPU devices are detached, cyborg should do clean up at once.
14:17:40 Sundar What kind of clean up do you have in mind? Zero out the RAM?
14:18:15 kosamara My thinking is to put the relevant resources in a special state after deallocation from their previous VM and use a service VM to perform the cleanup ops themselves.
14:18:21 Li_Liu memset() to zero for all ?
14:18:27 kosamara Yes, zero the ram
14:19:00 kosamara But ideally we would like to ensure the firmware's state is valid too.
14:19:13 shaohe_feng_ only this one method to clear up?
14:19:47 kosamara Sorry, I'm out of context. This method is from where?
14:19:58 shaohe_feng_ zero the ram
14:20:15 kosamara Yes for the ram.
14:20:30 shaohe_feng_ OK, got it.

Earlier   Later