| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2018-06-06 | |||
| 14:55:29 | Sundar | Yes, agreed with zhipeng | |
| 14:55:48 | Sundar | Here are the interfaces exposed by os-vif: https://github.com/openstack/os-vif/blob/master/os_vif/__init__.py | |
| 14:56:04 | zhipeng | it means that this is a VM related operation and we assume the Nova got the necessary previllage | |
| 14:56:04 | Sundar | I will try to locate how nova compute calls it | |
| 14:56:30 | zhipeng | we could focus on the details later, whether the lib itself could be called | |
| 14:56:45 | zhipeng | or something implement the lib interfaces should be called | |
| 14:57:35 | zhipeng | okey so everyone good on the os-acc spec ? | |
| 14:57:35 | Sundar | Nova compute calls the initialize API of os-vif directly here: https://github.com/openstack/nova/blob/master/nova/cmd/compute.py#L49 | |
| 14:59:05 | shaohe_feng | what does os_vif.initialize do? | |
| 14:59:27 | shaohe_feng | will it set up RPC client? | |
| 14:59:39 | Sundar | It sets up os_vif for further calls, like plug and unplug to attach/detach network ports to instances | |
| 15:00:06 | shaohe_feng | we want to know the plug detail | |
| 15:00:17 | shaohe_feng | how does it call neutron. | |
| 15:00:37 | shaohe_feng | by API or RPC? | |
| 15:00:51 | Sundar | shaohe: It seems to a direct call AFAICS> Here's the implementation: https://github.com/openstack/os-vif/blob/master/os_vif/__init__.py#L24 | |
| 15:01:51 | Sundar | shaohe: Could I ask whether it is important to settle this now before approving the spec? | |
| 15:02:18 | zhipeng | we could discuss this more in detail for implementation | |
| 15:02:27 | Sundar | The spec focuses on 2 things: behavior of accelerators during start/top/etc. and the os-acc interfaces | |
| 15:02:48 | shaohe_feng | Sundar, it should block the spec. | |
| 15:02:55 | Sundar | The implementation is up to us. There will be more comments on the code patch that implements this :) | |
| 15:03:10 | shaohe_feng | for if it can agent, we should be careful. | |
| 15:04:11 | shaohe_feng | s/for if it can agent/for if it call agent | |
| 15:04:13 | zhipeng | Sundar regarding nrp | |
| 15:04:21 | Sundar | We should be careful in the implementation. But the spec does not say RPC, API or whatever | |
| 15:04:26 | zhipeng | I think from the maillinglist discussion | |
| 15:04:31 | zhipeng | we should still go for it | |
| 15:04:38 | zhipeng | per your sched spec | |
| 15:05:02 | Sundar | Shaohe, if we don;t close on os-acc spec now, what is your proposed plan for Rocky? | |
| 15:06:04 | zhipeng | Sundar shaohe_feng let's moving on from the os-acc specifics | |
| 15:06:19 | shaohe_feng | OK | |
| 15:06:20 | zhipeng | actually let me put down a comment | |
| 15:06:51 | zhipeng | #action os-acc spec https://review.openstack.org/566798 after Li Liu remove -1 is ready to go | |
| 15:07:06 | zhipeng | so Li Liu still has to check :) | |
| 15:07:12 | Sundar | Thanks, zhipeng :) | |
| 15:07:21 | zhipeng | now back on the sched spec | |
| 15:07:31 | zhipeng | nrp | |
| 15:07:38 | zhipeng | I think we should still go for it | |
| 15:07:39 | Sundar | zhipeng, re. nRP, it may still take more time | |
| 15:07:50 | Sundar | We may not deliver anything if we keep waiting for it | |
| 15:08:13 | Sundar | Can we start by applying the traots on compute node RP and moving later when ever nRP is ready? | |
| 15:08:18 | Sundar | *traits | |
| 15:08:23 | zhipeng | given the impression from the Nova team | |
| 15:08:52 | zhipeng | nrp should be a worthy goal for Rocky, if we wait that's gonna be another cycle | |
| 15:09:12 | zhipeng | plus we have Alex here :P | |
| 15:09:45 | Sundar | What will be delivered in Rocky then? | |
| 15:10:17 | zhipeng | all the nrp based traits and rcs we discussed | |
| 15:10:28 | zhipeng | and placement will be ready i suspect | |
| 15:11:46 | shaohe_feng | Sundar, we have a discuss nRP on Monday's meeting. can you summary it? | |
| 15:14:20 | zhipeng | Sundar are you still around ? | |
| 15:14:22 | Sundar | shaohe: after Monday's meeting, I started a thread with Nova. Please see some of the responses, like: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131157.html | |
| 15:14:35 | zhipeng | the agent-driver api spec | |
| 15:14:52 | zhipeng | is this urgent for rocky as well ? | |
| 15:14:58 | Sundar | The virt-drivers need to be updated for nRP, and there are still some concerns around in-place upgrades with nRP | |
| 15:15:40 | Sundar | zhipenf, Just trying to understand :) -- if nRP is not ready in Rocky, what will Cyborg deliver in Rocky? | |
| 15:15:45 | Sundar | *zhipeng | |
| 15:16:37 | zhipeng | Sundar we could make a hack work | |
| 15:16:49 | shaohe_feng | zhipeng, we should make a decision on how we report the resource to placement. | |
| 15:17:14 | zhipeng | shaohe_feng specifically ? | |
| 15:18:36 | zhipeng | Sundar I see the feedbacks in the email thread, and the general feedback is that most of the stuff could be done | |
| 15:19:46 | Sundar | zhipeng: Say the nRP functionality is ready by mid-July. Would we have enough time to get it done after that? We have lots of people waiting to use Cyborg. Cyborg has got popular. ;) | |
| 15:20:02 | shaohe_feng | zhipeng, Must it be ready for resource report in R release? | |
| 15:20:08 | zhipeng | Sundar we have more than capable devs :) | |
| 15:20:42 | zhipeng | shaohe_feng basic functionality should be ready I presume | |
| 15:20:46 | zhipeng | nothing too fancy | |
| 15:21:04 | shaohe_feng | Sundar, yes, cyborg is becoming popular. | |
| 15:21:21 | Sundar | zhipeng: Definitely. :) But it may help to have a backup plan, right? Without that, we cannot get basic VM placement to work, AFAICS. | |
| 15:22:22 | zhipeng | yes we will have time for a backup plan, this could be planned together with Li Liu and Zhuli | |
| 15:23:10 | zhipeng | we shoot for NRP as priority, if Nova could not deliver it, then we could go backup | |
| 15:23:27 | zhipeng | but I don't want to drop NRP to a secondary concern at first | |
| 15:25:02 | Sundar | So, for development till then, we could invoke placement in some ad hoc way to populate inventory and traits ? | |
| 15:25:49 | zhipeng | i think so | |
| 15:27:07 | Sundar | OK, zhipeng. Your call. :) I had updated the spec to reflect compute node RP as a backup. I cna further clarify that nRP is the preferred way. Would that be enough? | |
| 15:27:37 | zhipeng | that'd be great :) | |
| 15:28:04 | zhipeng | btw all the specs we deemed ready today will be merge no later than the end of the week | |
| 15:28:31 | Sundar | Sure, thanks. :) Could we say that the spec is ready modulo that clarification? | |
| 15:29:06 | zhipeng | yes | |
| 15:29:16 | shaohe_feng | Sundar, another question about nRP | |
| 15:29:17 | zhipeng | that's actually more related to the implementation | |
| 15:29:30 | shaohe_feng | how we call placement? | |
| 15:29:49 | zhipeng | folks I got to drop, plz continue discussion, I will come back and terminate the meeting :) | |
| 15:29:55 | shaohe_feng | The placement client it ready? | |
| 15:30:13 | shaohe_feng | Sundar, I did not find it. | |
| 15:30:22 | Sundar | shaohe, I also need to drop for another call. Can we pursue in this IRC channel later? | |
| 15:30:31 | shaohe_feng | OK. | |
| 15:30:43 | shaohe_feng | then we can terminate the meeting | |
| 15:30:50 | shaohe_feng | ^ zhipeng | |
| 15:34:35 | zhipeng | okey then :) | |
| 15:34:42 | zhipeng | thx everyone for the discussion | |
| 15:34:45 | zhipeng | #endmeeting | |
| 15:34:47 | openstack | Meeting ended Wed Jun 6 15:34:45 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 15:34:48 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-06-06-14.00.html | |
| 15:34:50 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-06-06-14.00.txt | |
| 15:34:51 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-06-06-14.00.log.html | |
| 20:06:44 | openstackgerrit | Doug Hellmann proposed openstack/cyborg master: fix tox python3 overrides https://review.openstack.org/572953 | |
| 23:41:08 | openstackgerrit | Sundar Nadathur proposed openstack/cyborg master: Specification for Cyborg/Nova interaction for scheduling. https://review.openstack.org/554717 | |
| #openstack-cyborg - 2018-06-07 | |||
| 08:25:52 | openstackgerrit | sumitjami proposed openstack/cyborg master: add option collect_timing to keystone_authtoken https://review.openstack.org/573128 | |
| 08:52:03 | openstackgerrit | Merged openstack/python-cyborgclient master: base framework for cyborg client. https://review.openstack.org/565023 | |
| 09:20:41 | openstackgerrit | sumitjami proposed openstack/cyborg master: add option collect_timing to keystone_authtoken https://review.openstack.org/573128 | |
| 10:03:42 | openstackgerrit | sumitjami proposed openstack/cyborg master: use config options from keystoneauth1 under placement https://review.openstack.org/573161 | |
| 11:26:16 | openstackgerrit | Sundar Nadathur proposed openstack/cyborg master: Specification for Cyborg Agent-Driver API. https://review.openstack.org/561849 | |