| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2017-11-15 | |||
| 16:00:40 | masuberu | for example with memory and cpus I can "define" flavors, can I do same with FPGUs? | |
| 16:01:08 | LiLiu_ | yup | |
| 16:01:31 | LiLiu_ | That's one of the most common ways of managing FPGA in Openstack | |
| 16:01:46 | masuberu | like for instance 0.3Teraflops for one instance and 0.7Teraflops to another | |
| 16:01:49 | masuberu | ok | |
| 16:02:08 | LiLiu_ | That's totally doable | |
| 16:02:21 | masuberu | do you have experience with openhpc? | |
| 16:02:40 | LiLiu_ | I don | |
| 16:02:47 | masuberu | we run rocks cluster but the development is quite slow, I am wondering whether openhpc would be better option | |
| 16:02:50 | masuberu | ok | |
| 16:02:55 | LiLiu_ | but I know someone in my team might do | |
| 16:03:32 | masuberu | ok, thats ok, let try and focus on these tests comparing GATK4 on FPGUs vs Apache Spark | |
| 16:03:49 | masuberu | maybe this type of tests doesn't even makes sense, we will see | |
| 16:04:22 | masuberu | so I will get the cards tomorrow and connected to the servers | |
| 16:04:56 | LiLiu_ | sure | |
| 16:05:04 | masuberu | and from there if anyone know any document about how to integrate nova with fpgus or if there is any document/tool within cyborg project just let me know | |
| 16:06:44 | LiLiu_ | before cyborg is ready to use, I think the most naive way is just use PCI passthrough | |
| 16:07:17 | masuberu | sure | |
| 16:13:31 | crushil | zhipeng, Don't forget to close the meeting | |
| 16:13:50 | zhipeng | of course :) | |
| 16:14:01 | zhipeng | if nothing else, we had a great discussion today | |
| 16:14:07 | zhipeng | the meeting is adjourned | |
| 16:14:22 | zhipeng | and I will let everyone know the new ZOOM meeting time | |
| 16:14:28 | zhipeng | #endmeeting | |
| 16:14:30 | openstack | Meeting ended Wed Nov 15 16:14:28 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:14:31 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-11-15-15.00.html | |
| 16:14:32 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-11-15-15.00.txt | |
| 16:14:34 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-11-15-15.00.log.html | |
| 16:22:04 | masuberu | thank you all | |
| 16:22:28 | masuberu | and sorry I hijack the whole meeting, I guess you probably had other things to talk | |
| 16:22:47 | masuberu | it is 3.22am here so I am going to sleep now | |
| 16:23:30 | masuberu | please feel free to send me an email if any idea pops up manuel.sb@garvan.org.au or masber@hotmail.com | |
| 16:23:35 | masuberu | nite | |
| 16:26:56 | zhipeng | nite :) | |
| 16:50:23 | jkilpatr | did we start at 10am this time? I was off by an hour :( | |
| #openstack-cyborg - 2017-11-17 | |||
| 14:17:43 | zhipeng | jkilpatr ttk2[m] i've written a coarse draft for my idea mentioned last team meeting | |
| 14:17:48 | zhipeng | https://etherpad.openstack.org/p/cyborg-feature-tag | |
| 14:19:26 | ttk2[m] | zhipeng: so lets say we do this and people can schedule based on types, is their application now responsible fo rhandling supporting all the different types of accerlators they may get with the same request? | |
| 14:19:35 | ttk2[m] | I guss you can narrow it down | |
| 14:20:04 | ttk2[m] | deep learning + cuda X support = get different types of gpu's but the code alway sworks | |
| 14:24:55 | zhipengh[m] | That is another important part if the equation needs to be solved | |
| 14:25:19 | zhipengh[m] | But for HPC and NFV, it should work without too much trouble | |
| 14:26:12 | zhipengh[m] | For preloaded FPGA programs | |
| 14:29:38 | ttk2[m] | well yes, provided we handle compatibility checking behind the scenes some. | |
| 15:35:24 | zhipengh[m] | ttk2: the main point here is about scalability. Name and type won't get us far for accelerator, that is the fundamental problem for us | |
| 15:36:02 | ttk2[m] | how so? too specific? | |
| 15:37:12 | zhipengh[m] | Yep, especially for FPGA | |
| #openstack-cyborg - 2017-11-22 | |||
| 03:04:39 | zhuli | Rushil, Justin around? | |
| 14:59:16 | jkilpatr | zhuli, what's up? | |
| 14:59:29 | zhipeng | hey jkilpatr | |
| 14:59:45 | zhipeng | wonder if we could push tmr's ZOOM meeting one hour later ? | |
| 15:02:10 | jkilpatr | zhipeng, just so long as it doesn't go more than an hour or so. | |
| 15:02:25 | zhipeng | okey no problem | |
| 15:02:39 | zhipeng | so it will start 9:00pm your place | |
| 15:02:45 | zhipeng | i will send out ZOOM links | |
| 15:02:54 | zhipeng | let's wrap it up in 40mins | |
| 15:03:44 | crushil | \o | |
| 15:06:35 | zhipeng | #startmeeting openstack-cyborg | |
| 15:06:36 | openstack | Meeting started Wed Nov 22 15:06:35 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 15:06:37 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 15:06:39 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 15:07:01 | zhipeng | so i don't have perticular things in mind | |
| 15:07:10 | zhipeng | since we will do the ZOOM sprint later | |
| 15:07:20 | zhipeng | 9:00pm ET | |
| 15:07:31 | zhipeng | any topic you guys want to discuss ? | |
| 15:07:46 | zhipeng | I think zhuli and Intel dev are converging on something | |
| 15:08:03 | crushil | zhipeng, I have started working on the generic driver finally | |
| 15:08:16 | crushil | I will try to get something up during the thanksgiving weekend | |
| 15:08:21 | zhipeng | crushil gr8t news ! | |
| 15:11:28 | crushil | Let's meet up at 9pm and as a courtesy zhipeng if you can send the zoom invite on the ML too, that would be great | |
| 15:11:43 | zhipeng | no problem :) | |
| 15:21:53 | zhipeng | ok let me close the meeting now, see you guys later on ZOOM :) | |
| 15:22:18 | zhipeng | #endmeeting | |
| 15:22:20 | openstack | Meeting ended Wed Nov 22 15:22:18 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 15:22:21 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-11-22-15.06.html | |
| 15:22:22 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-11-22-15.06.txt | |
| 15:22:23 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2017/openstack_cyborg.2017-11-22-15.06.log.html | |
| 15:34:39 | Vipparthy | join | |
| 15:36:50 | vipparthy | Hi folks | |
| 15:36:56 | jkilpatr | hi | |
| 15:37:21 | vipparthy | is meeting on cyborg in progress or over ? | |
| 15:42:17 | jkilpatr | vipparthy, quick one today, so we're done now. Trying to do a video sprint tonight/early tomorrow though | |
| 15:42:32 | jkilpatr | see the ML | |
| 15:59:51 | vipparthy | can you please send me Video sprint meeting info | |
| 16:12:35 | crushil | vipparthy, It's on the mailing list | |
| #openstack-cyborg - 2017-11-27 | |||
| 21:34:36 | dims | zhipengh[m] : hey, can you ping diablo_rojo on #openstack-dev when you get a chance? she wanted to talk to you about the first contact sig | |
| #openstack-cyborg - 2017-11-29 | |||
| 15:06:27 | zhipeng | hi guys | |
| 15:06:38 | zhipeng | sorry running a bit late | |
| 15:06:47 | zhipeng | #startmeeting openstack-cyborg | |
| 15:06:48 | openstack | Meeting started Wed Nov 29 15:06:47 2017 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 15:06:49 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 15:06:51 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 15:07:45 | zhuli | hi | |
| 15:09:50 | zhipeng | hey | |
| 15:09:54 | zhipeng | anybody else | |
| 15:12:08 | crushil | here | |
| 15:13:04 | jkilpatr | 0/ | |
| 15:13:46 | zhipeng | :) | |
| 15:13:56 | zhipeng | #topic trello board | |
| 15:14:05 | jkilpatr | I finally moved my calender event to est instead of edt | |