| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2020-06-11 | |||
| 03:48:43 | xinranwang | 2. neutron create rp, cyborg use this rp to update acc related rc and traits. | |
| 03:49:51 | Sundar | First, you are assuming it is ok for one service to create an RP and another to update it by adding traits. Secondly, who will create the top-level RP for multi-component NICs? | |
| 03:51:28 | xinranwang | there is also solution by using provider-config.yaml | |
| 03:51:31 | Sundar | swp20: SOme traits cna be discovered from the device's PCI ID, like the type of NIC. Those can be added as traits by Cyborg. Others, like physnet or external network connecivity, are know only to the admin or the OpenStack installer. They are best left out of Cyborg. | |
| 03:51:45 | Sundar | The provider-config.yaml doe snot create RPs today. | |
| 03:52:07 | Sundar | It can be enhanced n the future to do that, but that will be another long discussion and development | |
| 03:52:16 | xinranwang | cyborg create rp and other update traits. | |
| 03:53:11 | xinranwang | I am investigating how neutron report physnet traits, it seems neutron has also create a logic rp. Not sure, need to verify this. | |
| 03:53:22 | Sundar | You are free to bring this up. Look at past IRC discussions before you spend time on this. | |
| 03:53:37 | Sundar | Yes, Neutron creates an RP for bandwidth provider feature. | |
| 03:54:31 | swp20 | Sundar: so how we scheduler the resources by these traits left out Cyborg? | |
| 03:55:01 | Sundar | Just one more point before I conclude: when we have multi-component NICs with different RPs, it is important that the resource classes and traits for the accelerator RP and the NIC RP be totally disjoint (no overlapping resource classes or traits. That will usually be the case. | |
| 03:55:15 | shaohe_feng | neutron has a create_pci_requests_for_sriov_ports | |
| 03:55:35 | Sundar | swp20: The admin can reference such traits in the device profile which he creates in Cyborg. | |
| 03:56:15 | Sundar | Ok, this has taken a bit longer than I thought :). I didn't mean to take up the whole meeting. | |
| 03:56:39 | xinranwang | Yes, every solution has it's pros & cons... Need more investigation | |
| 03:56:56 | Yumeng | Sundar, xinranwang and all: IMHO, If nova and neutron have no objections, I would prefer the solution which Cyborg create the top-level RP for multi-component NICs. Since Cyborg does the lifecycle management of NICs. So I personally prefer Cyborg should create all the RPs needed for a smart NIC. | |
| 03:57:38 | shaohe_feng | it should can create RP. but anyway, who create the RP, cyborg and neutron should have the same way, that means it know each other | |
| 03:57:43 | Sundar | Yumeng: Sure. We need to discuss with neutron folks on the bandwidth provider case, where they create the RP now | |
| 03:57:49 | xinranwang | Yes, I prefer this too. RP creation in cyborg seems reasonable. | |
| 03:58:35 | xinranwang | About the physnet trait. that's what we need to discuss more. | |
| 03:58:49 | shaohe_feng | admin can set physnet for both cyborg and neutron. Tenant does not need to know this. Neutron can get the detail and device profile from cyborg, and add physnet when neutron call create_pci_requests_for_sriov_ports | |
| 03:59:25 | xinranwang | And also need to discuss the consistency about rp created in neutron and cyborg. | |
| 03:59:41 | shaohe_feng | agree | |
| 04:00:19 | wangzhh | I think it's better to let cyborg ccreate RP. And for the traits, can cybog auto sync it from neuton? | |
| 04:00:29 | wangzhh | *cyborg | |
| 04:00:32 | swp20 | Sundar: not familar with this, i will track it. thanks | |
| 04:00:49 | xinranwang | Neutron need to provide an interface in this case. wangzhh | |
| 04:01:27 | shaohe_feng | 1. if we just let neutron the create set the physnet, that is convenient to admin. convenience maybe that need more change, more effort. | |
| 04:03:06 | shaohe_feng | actually, cyborg can not know the physical networks. | |
| 04:03:06 | wangzhh | It is bridge_mapping conf of neutron, not sure if we can get it from neutron net-show external-net. xinranwang | |
| 04:04:31 | xinranwang | neutron will report physnet trait only if bandwidth feature enabled, as my understanding. So I am not sure we can get info from these apis | |
| 04:05:27 | Sundar | I would suggest that we keep networking aspects out of Cyborg. That can only lead to complexity and trouble. | |
| 04:06:01 | Yumeng | agree. | |
| 04:06:39 | Yumeng | seems we have run out of time! let's continue discussion in wechat or ML. | |
| 04:07:12 | Yumeng | And I will quickly mention the left topics. | |
| 04:07:51 | Yumeng | #topic third-party driver CI | |
| 04:09:13 | Yumeng | we got three new drivers in victoria releases, do we need to require a CI for new drivers? what should be include in the tests? | |
| 04:11:43 | Yumeng | From my opinion, third-party driver CI is good. But not sure each vendor can provide. I think cyborg should at least require one or two main driver vendors to provide this kind of CI tests. | |
| 04:11:49 | Yumeng | what do you think? | |
| 04:12:31 | xinranwang | Hmmm, better to have 3rd CI. We can keep the dreiver as experimental until it has 3rd CI | |
| 04:13:05 | Sundar | Yumeng: sounds like a good idea, but how do we force vendors to provide it? We can only say that, if hey provide it, we will support it, otherwise it is an unsupported driver. | |
| 04:13:30 | Sundar | xinranwang: yes, I think we are aligned. | |
| 04:14:07 | Yumeng | Sundar: yes. we cannot require any vendor. sounds 'experimental' or 'supported' is a good idea.! | |
| 04:14:51 | Yumeng | anyway, we don't have to conclude it today. we can think more. and continue discussion. | |
| 04:15:10 | Sundar | Would ZTE provide 3p CI for their smart NIC? Just curious :) | |
| 04:15:11 | Yumeng | # topic storyboard usage | |
| 04:16:10 | Yumeng | Sundar: haha not sure. I need to check with the network team | |
| 04:18:52 | Yumeng | about the storyboard usage, we've got some complains in the PTG. I investigate some in it, and found it has a very flexible advantage in defining your own priority, worklists and so on. so it is worth use. | |
| 04:20:16 | Yumeng | so please check links in topic 3-7 https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda, and review the usage guide. We need to decide how we want to use the storyboard. | |
| 04:20:56 | Yumeng | Otherwise, if any other good solutions, we can also discuss. | |
| 04:21:24 | Sundar | I'm fine with whatever you all decide. | |
| 04:22:39 | Yumeng | ok. Thanks Sundar. | |
| 04:22:41 | Yumeng | #topic AoB | |
| 04:22:48 | Yumeng | Does anybody want to bring up anything else? | |
| 04:23:14 | Yumeng | seem nope. | |
| 04:23:47 | Yumeng | That's so great today we had a very effective meeting today. Thank you all! | |
| 04:24:05 | Sundar | Thank you all | |
| 04:24:06 | Yumeng | Let's meet next week. Have a good day/night! | |
| 04:24:12 | Sundar | Bye | |
| 04:24:27 | Yumeng | #endmeeting | |
| 04:24:29 | openstack | Meeting ended Thu Jun 11 04:24:27 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 04:24:30 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2020/openstack_cyborg.2020-06-11-03.04.html | |
| 04:24:31 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2020/openstack_cyborg.2020-06-11-03.04.txt | |
| 04:24:32 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2020/openstack_cyborg.2020-06-11-03.04.log.html | |
| 09:49:36 | openstackgerrit | Hervé Beraud proposed openstack/python-cyborgclient master: Use unittest.mock instead of mock https://review.opendev.org/734506 | |
| #openstack-cyborg - 2020-06-15 | |||
| 08:35:36 | openstackgerrit | YumengBao proposed openstack/cyborg master: Remove OPAE dependency in devstack https://review.opendev.org/735526 | |
| 11:56:55 | openstackgerrit | YumengBao proposed openstack/cyborg master: Remove OPAE dependency in devstack https://review.opendev.org/735526 | |
| #openstack-cyborg - 2020-06-16 | |||
| 01:26:28 | openstackgerrit | zhurong proposed openstack/cyborg master: Use uwsgi binary from path https://review.opendev.org/735756 | |
| 03:18:20 | openstackgerrit | Merged openstack/python-cyborgclient master: Fix image get to use new osc release https://review.opendev.org/734431 | |
| 03:42:33 | openstackgerrit | YumengBao proposed openstack/cyborg master: Remove future imports https://review.opendev.org/716910 | |
| 03:47:30 | openstackgerrit | YumengBao proposed openstack/python-cyborgclient master: Remove future imports https://review.opendev.org/723167 | |
| 03:48:14 | openstackgerrit | YumengBao proposed openstack/python-cyborgclient master: Use unittest.mock instead of third party mock https://review.opendev.org/720981 | |
| 03:56:27 | openstackgerrit | YumengBao proposed openstack/cyborg master: Use unittest.mock instead of third party mock https://review.opendev.org/716916 | |
| 06:25:52 | openstackgerrit | zhurong proposed openstack/cyborg master: Use uwsgi binary from path https://review.opendev.org/735756 | |
| 07:24:50 | openstackgerrit | Brin Zhang proposed openstack/cyborg master: Use unittest.mock instead of third party mock https://review.opendev.org/716916 | |
| 07:50:26 | openstackgerrit | zhurong proposed openstack/cyborg master: Use uwsgi binary from path and docs job fix https://review.opendev.org/735756 | |
| 10:16:47 | openstackgerrit | zhurong proposed openstack/cyborg master: Use uwsgi binary from path and docs job fix https://review.opendev.org/735756 | |
| 13:25:04 | openstackgerrit | Merged openstack/cyborg master: Use uwsgi binary from path and docs job fix https://review.opendev.org/735756 | |
| #openstack-cyborg - 2020-06-17 | |||
| 01:35:36 | openstackgerrit | Merged openstack/python-cyborgclient master: Remove unused osc_plugin environment https://review.opendev.org/727354 | |
| 01:36:34 | openstackgerrit | Merged openstack/cyborg master: Enable openstackdocs config to storyboard https://review.opendev.org/734401 | |
| 01:42:36 | openstackgerrit | Merged openstack/cyborg-specs master: Remove Babel https://review.opendev.org/723783 | |
| 02:36:50 | openstackgerrit | Merged openstack/cyborg master: Monkey patch original current_thread _active https://review.opendev.org/726316 | |
| 06:24:00 | openstackgerrit | Merged openstack/cyborg master: Remove OPAE dependency in devstack https://review.opendev.org/735526 | |
| #openstack-cyborg - 2020-06-18 | |||
| 00:59:04 | openstackgerrit | Brin Zhang proposed openstack/python-cyborgclient master: Remove translation sections from setup.cfg https://review.opendev.org/723207 | |
| 03:01:21 | chenke | #info chenke | |
| 03:01:34 | Yumeng | hi all | |
| 03:01:43 | brinzhang | \o | |
| 03:01:46 | Yumeng | #startmeeting openstack-cyborg | |
| 03:01:47 | openstack | Meeting started Thu Jun 18 03:01:45 2020 UTC and is due to finish in 60 minutes. The chair is Yumeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 03:01:48 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 03:01:50 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 03:02:06 | brinzhang | #info brinzhang | |
| 03:02:12 | Yumeng | #topic Roll call | |
| 03:02:17 | Yumeng | #info Yumeng | |
| 03:02:26 | Yumeng | #topic Agenda | |
| 03:03:14 | Yumeng | pls check the agenda for today. | |
| 03:03:48 | brinzhang | It seems not many people for today meeting... | |
| 03:04:36 | Yumeng | brinzhang: have you checked that if your browser blocked the captcha? | |
| 03:05:05 | brinzhang | Yumeng: I dont know why, and I cannt save it | |