Earlier  
Posted Nick Remark
#openstack-cyborg - 2019-06-26
03:28:43 Sundar Shall we cancel tomorrow's Zoom call then?
03:28:58 Coco_gao_ ok
03:28:59 xinranwang if no other topics
03:29:28 ikuo_o Unfortunately I cannot attend tomorrow...
03:30:14 ikuo_o And this time is my last cyborg meeting. Thank you for welcoming me.
03:30:23 Sundar If there is interest in knowing about developments in Placement for nested RP trees, same_subtree, device colocation, etc., I could invite efried or others
03:31:00 Sundar ikuo_o: Understand. Thanks for all your contributions. Happy to see NTT is so active
03:31:34 ikuo_o After July, Shogo Saito will succeed my cyborg work, and we will propose new features for next releases.
03:32:29 Sundar ikuo_o: "After July"? So, will there be participation in July?
03:32:52 ikuo_o No, Sundar. From July 1st, Saito will do.
03:33:21 Sundar Got it.
03:33:32 Sundar Thanks, ikuo_o and everybody. Have a good day and a good time at KubeCon, MWC, or wherever you are :)
03:33:37 Sundar #endmeeting
03:33:37 ikuo_o I'm sorry for not contributing to cyborg so much. I'm preparing handing over my work!
03:33:38 openstack Meeting ended Wed Jun 26 03:33:37 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
03:33:39 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2019/openstack_cyborg.2019-06-26-03.03.html
03:33:40 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2019/openstack_cyborg.2019-06-26-03.03.txt
03:33:41 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2019/openstack_cyborg.2019-06-26-03.03.log.html
03:33:45 ikuo_o Thank you all!
03:33:47 ikuo_o Bye.
03:33:53 Sundar ikuo_o: NP :) Welcome. Bye.
06:50:58 openstackgerrit Ikuo Otani proposed openstack/cyborg master: Python3 migration 1st patch https://review.opendev.org/667524
22:37:39 openstackgerrit Biwei Guo proposed openstack/cyborg-tempest-plugin master: squashing Xinran and Biwei's three commits together Cleaned up code and all tempest tests passing except for Delete Device Profile bug https://review.opendev.org/667231
#openstack-cyborg - 2019-06-28
00:57:19 Sundar ikuo_o and all: https://review.opendev.org/#/c/658263/1/specs/train/approved/cyborg-api.rst@306 "There is no API for image upload via cyborg." Shall we decide to keep these APIs for a future release once Cyborg gets adopted? For now, we can document what image metadata is expected and let operators do it themselves via Glance CLI/APIs.
01:29:05 openstackgerrit Sundar Nadathur proposed openstack/cyborg-specs master: Specification for Cyborg APIs Version 2. https://review.opendev.org/658263
01:32:50 openstackgerrit Sundar Nadathur proposed openstack/cyborg-specs master: Specification for Cyborg APIs Version 2. https://review.opendev.org/658263
02:30:41 openstackgerrit Merged openstack/cyborg-tempest-plugin master: Enable plugin list feature and add gate job to merge patches https://review.opendev.org/659687
02:48:26 openstackgerrit chenker proposed openstack/cyborg-tempest-plugin master: Switch to the new canonical constraints URL on master https://review.opendev.org/665678
03:38:23 xinranwang Hi, I agree to keep these APIs in future, we need to get cyborg/nova integration done first.
03:47:57 yikun +1, and we implements these API in future. And I prefer we don't upload the image using cyborg directly, the flow in my mind should be first upload to glance, and then use image_id to generate a cyborg image record.
03:48:46 yikun Otherwise we have to support all different upload styles in cyborg which are already done in glance
06:23:21 Sundar xinranwang, yikun: Thanks. Agree we can use Glance UUID in Cyborg.
12:46:07 wangzhh +1 Also agree to keep these APIs in future.
23:56:43 openstackgerrit Biwei Guo proposed openstack/cyborg-tempest-plugin master: squashing Xinran and Biwei's three commits together Cleaned up code and all tempest tests passing except for Delete Device Profile bug https://review.opendev.org/667231
#openstack-cyborg - 2019-07-01
03:07:52 openstackgerrit Merged openstack/cyborg master: Update json module to jsonutils https://review.opendev.org/667362
03:54:28 openstackgerrit Merged openstack/cyborg-specs master: Specification for device profiles. https://review.opendev.org/602978
11:15:26 openstackgerrit inspurericzhang proposed openstack/cyborg master: Mailing lists change openstack-dev to openstack-discuss https://review.opendev.org/668433
#openstack-cyborg - 2019-07-03
02:54:27 s_shogo I joined this team as successor of Ikuo Otani from NTT Corp, thank you.
03:04:11 Sundar #startmeeting openstack-cyborg
03:04:12 openstack Meeting started Wed Jul 3 03:04:11 2019 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot.
03:04:13 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
03:04:15 openstack The meeting name has been set to 'openstack_cyborg'
03:04:23 Sundar #topic Roll call
03:04:28 Sundar #info SUndar
03:04:29 Yumeng #info Yumeng
03:04:36 Biwei #info Biwei
03:05:04 Sundar Hi Yumeng, Biwei, xinranwang
03:05:27 Sundar Let us wait a min for others
03:05:48 Yumeng Hi sundar Biwei and xinran
03:05:55 xinranwang Hi all
03:06:04 xinranwang welcome back Yumeng
03:06:48 Yumeng ^ ^ thanks xinran
03:06:52 Sundar #topic Spec review
03:07:02 s_shogo Hi I joined this team as successor of Ikuo Otani from NTT Corp, thank you.
03:07:19 Sundar Hi s_shogo
03:07:24 Sundar Welcome to Cyborg
03:07:58 Yumeng welcome s_shogo
03:08:26 Sundar Nothing much on the agenda today except for completing the spec reviews: https://review.opendev.org/#/q/status:open+project:openstack/cyborg-specs+owner:Sundar+after:2019-04-01
03:08:42 yikun #info yikun
03:09:09 Sundar Please review and provide comments and/or a +1/+2
03:10:38 Sundar s_shogo: Hope you have got the information from Ikuo on the activities that NTT took up: Python 3 migration and Cyborg client
03:12:22 Sundar #topic AoB
03:12:40 Sundar Please continue the spec review. Any thing else to discuss today?
03:15:27 wangzhh Hi all.
03:15:40 Yumeng I just reviewed the tempest patch https://review.opendev.org/#/c/667231/ we may need add a zuul job to run it.
03:15:52 Sundar Hi wangzhh
03:16:04 Yumeng I can add it today.
03:16:47 yikun A question on the example on fake driver slot: https://review.opendev.org/#/c/665318/3/cyborg/accelerator/drivers/fake.py@42
03:17:53 Sundar yikun: Please see https://review.opendev.org/gitweb?p=openstack/cyborg.git;f=nova-integ/demo_setup.sh;hb=refs/changes/20/626420/24#l80
03:18:00 Sundar Yumeng: Thanks
03:18:13 yikun For now, we already use the string style slot like "0000:0c:00.0" in exist GPU/FPGA patch, so do you think we should change these to json something like "{domain:xx, slot:xx}"
03:19:05 Sundar yikun:Yes, that is what we concluded in our last IRC meeting: http://eavesdrop.openstack.org/irclogs/%23openstack-cyborg/%23openstack-cyborg.2019-06-19.log.html#t2019-06-19T03:32:48
03:20:52 yikun ok, sorry to miss that, then we should change it in GPU/FPGA and all other related patch, right?
03:20:52 xinranwang wangzhh: do we need this pci_addr string to name deployables in gpu driver
03:21:51 yikun and then we do NOT support string style slot anymore? only json format will be supported, right?
03:22:01 Sundar yikun: Yes
03:22:35 Sundar xinranwang:: The PCI string is for controlpath_id and attach_handle, not deployables.
03:22:50 yikun OK, It's okay to me, Let's see other idea, xinranwang, wangzhh,
03:22:53 wangzhh xintanwang: Yes. Checked it just now.
03:23:04 wangzhh *xinranwang
03:23:10 yikun : )
03:23:23 xinranwang Sundar: I mean “this string is used to name the deployable”
03:23:40 wangzhh Yes.
03:23:49 xinranwang wangzhh: ok, thanks.
03:23:59 wangzhh Just name of deployable.
03:24:03 yikun wangzhh: 'r' 't' is very close I know
03:24:31 yikun https://review.opendev.org/#/c/665318/3/cyborg/accelerator/drivers/fake.py@34
03:25:10 Sundar yikun: I'll reply in that patch too.
03:25:54 yikun Yes, so "driver_dep.name = pci.get('device', '') + '_' + pci["slot"]" the deploy name still should be "device_strstylepciaddr" like "device_0000_00_000"
03:27:29 Sundar A deployable may have more than one VF. Then which PCI address would we give it?
03:27:41 Sundar I mean, what name would be give it?
03:28:37 yikun not sure, wangzhh do you have any idea for GPU deployable name?
03:29:21 xinranwang it's gpu's case, in FPGA driver, currently we do not name deployable using pci addr.
03:29:48 xinranwang But I am not sure how OPAE will report VFs' name
03:31:03 yikun As I know, the deployable logic model is useless in GPU, so I guess the device name can be changed to other.
03:31:36 yikun anyway, we need wangzhh to confirm.
03:32:16 Sundar We may use the deployable name as part of the Placement RP name. So, should we have some uniform naming convention across devices?
03:32:19 wangzhh <ComputeNodeName>_<NumaNodeName>_ <Device_name>_<Device_address>
03:32:49 wangzhh yikun, Can we named it like this?
03:33:02 yikun deployable name?

Earlier   Later