03:02:31 #startmeeting openstack-cyborg 03:02:32 Meeting started Thu Mar 5 03:02:31 2020 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:02:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:02:35 The meeting name has been set to 'openstack_cyborg' 03:02:47 #topic Agenda 03:02:55 #info chenke 03:03:04 #info Sundar 03:03:14 #info Li_Liu 03:03:29 #info brinzhang 03:03:36 #info Yumeng 03:04:10 #info xinranwang 03:04:26 What do people have to discuss today? 03:05:18 About remove v1 API 03:05:19 https://review.opendev.org/#/c/711232/ 03:05:22 BTW, the time for PTG reservation is up. I didn't hear confirmation that even 3 people plan to go to Vancouver, SO I haven't confirmed anything. 03:07:27 encourage developers to access the PTG 03:07:31 if possible. 03:09:59 V1's API is now worthless, and v2 can also be seen. v2's deployable api, Shogo is also doing it, I think it can be removed. Even if the v1 api is retained, the call may not necessarily be as expected. https://review.opendev.org/#/c/698190/ 03:10:04 brinzhang 03:10:04 To have focused discussion on V release goals and plans, we could either do it in IRC and etherpads or in openstack-discuss ML. If we do a Zoom call. or WeChat discussion, they should be posted on IRC or ML. Otherwise, other projects will not have know what we do. 03:10:37 brnzhang, chenke: Agree v1 API can be removed. 03:10:47 brinzhang: ^ 03:10:52 OK 03:11:16 Sundar, but in v2 we dont have the deployable, right? 03:11:44 if we remove now, I think it's too early to do this. 03:11:52 https://review.opendev.org/#/c/698190/ 03:12:59 IMO, we should done all things in v2, then to deal with the v1 03:13:01 brinzhang: There is a deployable object in v2, but it means something else than the v1 deployable. 03:13:28 I think we plan to have APIs for patching deployables in v2. 03:14:00 Sundar: sure 03:14:32 If all agree to remove now, I am ok too. 03:15:15 brinzhang: I think it is better to remove api/controllers/v1/deployables.py and add api/controllers/v2/deployables.py 03:15:53 shogo is doing this 03:16:04 Sundar: I also agree, but I just think it's earlier 03:16:30 brinzhang: I see. What should we wait for, before we remove the v1 API? 03:16:46 I think so 03:18:00 do you use v1? 03:19:22 chenke, Sundar: Need a process here, right? 03:19:38 brinzhang: Brin, if I didn't remember it wrong, we've made an agreement Train version that we make an deprecation anounce and remove the code in U release. 03:21:05 Yumeng, Ah, if so, I think I missed this message, ignore my comments 03:21:24 But I forgot where the discussion was happen. 03:21:30 Yes, we followed the process of deprecating in Stein itself and reinforced the deprecation in Train. 03:21:53 yes, it's safe to remove now. Don't worry. 03:22:17 Yumeng: We have discussed this in IRC before (I need to look up when). But our API docs clearly say v1 is deprecated, both in Stein and Train. 03:23:37 ok. good that we have announcement! 03:24:18 Sundar: that should an ML or etherpad to recore this aggrement, otherwise will have different opinion 03:24:47 https://docs.openstack.org/cyborg/stein/admin/api.html 03:24:55 And we should add that links to the commit message, that reviewer can get more info 03:25:27 Ok. I will update message 03:26:34 Sundar, chenker, Yumeng: ok, we can continue next topic 03:26:36 brinzhang: The above link is published already. I have said this to Nova developers in ML too, not sure when. 03:26:54 ok 03:27:12 For example, Sean mooney and others are testing Nova with Cyborg v2. No expectation of v1 support. 03:27:39 #topic PTG 03:28:33 To reinforce what I said: To have focused discussion on V release goals and plans, we could either do it in IRC and etherpads or in openstack-discuss ML. If we do a Zoom call. or WeChat discussion, they should be posted on IRC or ML. Otherwise, other projects will not have know what we do. 03:29:02 Does anybody disagree? 03:29:31 We can create a ether pad 03:29:52 To list the goals 03:31:11 Ok, so everybody agrees to this ^, right? 03:31:19 agree. etherpad, zoom are always good. 03:31:31 agree, wWe can publish content on etherpad regularly 03:31:47 send that info to ML 03:32:07 agree. 03:32:22 #agree V release planning process above ^ 03:32:33 Thanks, all 03:32:55 Any other topic before I move to Nova and related stuff? 03:33:17 ^^ 03:33:24 Sundar, xinranwang, chenke: I will abandon this:https://review.opendev.org/#/c/709286/3 03:33:33 but we still need to update the valid controlpath_id_type values herehttps://github.com/openstack/cyborg/blob/master/cyborg/objects/control_path.py#L26, do you agree? 03:34:07 we should remove "MDEV" in cureent valid values 03:34:25 */from 03:34:43 Agree 03:34:47 https://github.com/openstack/cyborg/blob/master/cyborg/objects/control_path.py#L26 03:34:52 Yumeng: agree 03:35:00 to both 03:35:14 ok. great! will do. 03:35:38 agree 03:36:13 Agree 03:37:58 ok. thanks all! 03:38:29 Ok, on the Nova series: it is a bit mixed news. One patch got merged, one more got +2. But we are still spinning on UT details. Sometimes seems like too much detail or nits. 03:40:00 I was hoping to wrap this up by Feb. I have offers for a next role, but yet to decide. But I will be moving to a different role in March. So, I am looking to wrap it up one way or the other. 03:41:53 wow, congrats! 03:41:58 Sundar congratulate! 03:44:13 congrats! >> the merged patch 03:44:25 Thanks, mixed feelings for me, after putting so much effort into Cyborg. 03:45:07 Can one of you volunteer to be an additional PTL after I move on? 03:45:18 Sundar, congrats! That is a new beginning and it will be brilliant. 03:45:32 Thanks, brinzhang. 03:45:52 So what‘s your next role? 03:46:18 still about cloud related work? 03:46:38 Yes, you spend a lot of energy on cyborg, about 16 hours a day. Good luck cares for those who work hard. 03:47:44 Not decided on next role, yes still about cloud, 03:48:19 chenke: I was doing CYborg plus some Kubernetes work till about a month ago 03:48:37 That's why it took long hours 03:49:11 Got it. 03:49:13 Thanks for your great efforts! 03:50:19 Thanks, xinranwang 03:50:45 OK, maybe you all can discuss offline on additional PTL. We still have time. 03:50:50 Sundar: I can help with the rest work after you move on. But not sure if we need more volunteers. we can discuss the tasks and seperate them. 03:51:32 kubernets is popular in cloud. 03:51:42 Yumeng: Ok. We need to inform the OpenStack Foundation so that they can send all communication to two people, not just me alone. 03:52:30 That's all, folks. Anything else before we wrap up? 03:53:20 can anyone who attend PTG can tell something about Cyborg and Neutron integration? 03:53:59 on smartnic 03:54:11 I have look into it. 03:54:53 shaohe_feng: I have rescinded (cancelled, taken back) my proposals for Cyborg Neutron integ. It would not be easy to drive a 3-way change across Nova, neutron and Cyborg. 03:55:39 The next best approach would be to assume a static programming model, and use Nova to create the resource providers for smart NICs using the provider config (YAML-based) approach. 03:55:41 The neutron Docs tells us, it support a new vif type smartnic 03:56:29 that's means cyborg should not manage these kind of accelerators? 03:57:01 I have think it how to support it. 03:57:31 any method, nova can not do many help 03:58:03 some one want to know details about it. 03:58:13 or we can discuss offline 03:58:25 shaohe_feng: First, to my knowledge, most folks do not plan to dynamically program smart NICs, i.e., change its image based on VM type, traffic type, workload, time of day, etc. 03:58:55 Instead they'll do it statically, maybe even offline when no VMs are present and the host is in maintenance mode 03:59:14 The strength of CYborg is dynamic programming. 03:59:16 I know other company will support it. and maybe they are work in progress, not sure they will upstream. 03:59:51 the cyborg is only for program? 03:59:58 Ok, if you have concrete proposals, and plan to follow up with Nova/neutron community, along with other developers, that would be good. 04:00:19 Yea, we can take this offline, or in the next IRC call. 04:00:32 I need to go now. And it is lunch time for you all :) 04:00:40 No, it will do more not only program. 04:00:57 Anything else, folks? 04:01:48 nothing from me. 04:02:00 Have a good day! Bye for now. 04:02:03 #endmeeting