03:03:36 #startmeeting openstack-cyborg 03:03:37 Meeting started Wed May 29 03:03:36 2019 UTC and is due to finish in 60 minutes. The chair is Sundar__. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:03:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:03:40 The meeting name has been set to 'openstack_cyborg' 03:03:46 #topic Roll call 03:04:17 #info Sundar 03:04:20 #info wangzhh 03:04:36 #info ikuo_ 03:04:49 #topic Agenda 03:04:52 https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting 03:04:53 #info Coco_gao 03:05:05 Anything to add to this agenda? 03:05:36 #topic Nova spec update 03:05:41 It's good 03:06:29 There was a feedback to move the Cyborg binding to Nova compute manager. I implemented it and made some measurements on 1 2-node system, but that doesn't predict scaling impact 03:07:11 Meanwhile, several folks gave that feedback. SO, I have changed the spec to match that 03:07:22 Does anybody have any concerns or comments? 03:08:17 The spec is close to finish, so please provide your comments soon 03:08:36 Where do you mean in the spec? 03:09:36 https://review.opendev.org/#/c/603955/13/specs/train/approved/nova-cyborg-interaction.rst,unified Line 240 03:10:01 Fine with me. 03:10:03 Lines 240-263 03:10:29 Good 03:10:44 #topic python cyborg client 03:10:54 Thanks to ikuo_ for starting http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006543.html 03:10:55 #info yikun 03:11:02 Hope you all had a chance to catch up 03:11:27 still need to some time to catch up, sorry. 03:11:50 Coico_gao, NP. I'll try to summarize. 03:12:26 python-cyborgclient should be rewritten as an OSC plugin or a new repo should be created for that: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006574.html 03:13:07 Dean tTroyer (http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006577.html) suggests we could write a plugin to OSC, as part of OSC repo itself. 03:13:39 #info Li_Liu 03:13:56 Thanks for the summay~ 03:14:00 So we should rewrite the whole cyborgclient.. In fact, I cannot imagine the impact. 03:14:05 Either way, it is good for Cyborg to implement OpenStack SDK, so that the client can use it to call the API 03:14:45 First, do we all agree that we should use the OpenStack SDK (independent of other options)? 03:15:26 #info xinranwang 03:15:35 Hi all, sorry for late 03:15:56 Is it other thing but OSC plugin? 03:16:24 ikuo_ : It seems like a large impact. In practice, current client is mostly v1. So its objects either don't exist (like accelerators) or have changed a lot (like deployables). Plus, there are new pones like device profiles 03:16:43 So, I suspect anyway it will be a big change 03:16:43 Sundar, if we rewrite cyborgclient as an OSC plugin, who guys are responsible for the milestone? 03:17:00 Agree to use openstack sdk first. 03:17:21 is this a train target? 03:17:35 wangzhh: Good question, I don't know :). It means we are not in control, as Dean says. Or, we could write our own plugin from scratch -- more work but more control. 03:17:42 Li_Liu: Yes 03:18:38 ikuo_: "Is it other thing but OSC plugin?" <-- OpenStack SDK and OSC plugin are 2 different things 03:18:50 SDK is a way for other services (or cyborg client) to call CYborg API 03:19:01 OK, I agree Use openstack sdk 03:19:10 Whereas OSC plugin is a way to implement the client using standard mechanisms 03:19:54 Coco_gao, ikuo_: Thanks for voting on SDK. Anybody disagrees? 03:20:31 Agree SDK +1 03:20:37 sounds good 03:20:52 Great :) I like consensus :) 03:21:03 Agree 03:22:06 But rewriting for OSC plugin by only NTT, it is difficult, I think. 03:22:50 ikuo_: I understand 03:23:11 Now, for the difficult question -- should we write a separate osc plugin (like many other projects have done) or try to make this a part of osc repo? Dean says: "if Cyborg were completely backed by the SDK we would consider adding its commands directly to the OSC repo." 03:23:37 Once we adopt the SDK, may be it gets easier? Plus, I agree others should support NTT 03:24:16 ikuo, can u help to split the task on storyboard? 03:24:45 I suspect there will be less UT and functional tests if we use the OSC repo. If there is concern about dependence and timelines, I could ask Dean. 03:24:56 (Or any of you could respond on the ML.) 03:26:43 Wangzhh: so we should split our cyborgclient task to 1) use openstacksdk and 2) OSC plugin /repo? 03:27:07 Maybe more smaller tasks. 03:28:19 Coco, Yep. So that others can take part of them to support NTT. 03:28:35 I got it. 03:29:10 I will first finish my part and then join you to finish other tasks. 03:29:22 Thx. ikuo_. 03:29:39 All right. thanks. 03:30:03 Sounds like a plan. Should I ask on the ML what is the risk to timeline from using osc repo? 03:30:21 Yes, please! 03:30:31 Will do 03:30:49 Yes 03:31:01 #agreed Cyborg will implement OpenStack SDK. The client will call the API through that 03:31:26 #action Sundar: gets pros and cons of using the osc repo, vs. writing a plugin 03:31:49 BTW, does engineering meeting still exist? 03:31:51 #action: ikuo_ will create storyboard tasks 03:32:41 Coco_gao: We can convene it any time if there is a need. IMHO, it is good to keep it as a placeholder. The networked FPGA stuff is still open 03:33:00 What do you all think? 03:33:12 Sounds good for me. 03:33:17 Yes, we should talk when we need. 03:33:49 OK, thanks 03:33:57 #topic Communication updates 03:34:26 I am still working on the nova's external_event_api patch 03:34:41 As you may know, there are some restrictions on communication, and some of us have been asked not to use WeChat by default 03:35:17 What do you suggest? 03:35:34 lol 03:35:37 Yes, my colleague cannot use WeChat. Thank you for proposing the topic. 03:35:41 It would be good to use IRC and ML by default. For IRC, does it make sense to have a window of time where we all login? For example, it could be morning 9-12 am by CHina time? 03:35:46 I think irc is our only option now 03:36:07 Li_Liu and all: yes 03:36:19 can we still talk in zoom meetings? 03:36:41 Sundar__: Hi Sundar, I have pull your pilot branch in local, and find some bugs, for example, we cannot delete extended_arq when deleting vm, and some other. I have done some bug-fix. Do you want me to leave comments where bug occurs , or I can co-author with you if you want. Which way you prefer? 03:36:59 Li_Liu: My guidelines are that public meetings are ok. I have put the Zoom URL in wiki along with the times. SO it is open to all 03:37:14 That's sounds good staying 9-12 am. 03:37:44 ikuo_: Thanks. Others ok with that time? 03:38:09 yup, I will be on irc all the time now 03:38:20 Cool. 03:39:46 xinranwang_: The Cyborg code to delete ARQs exists. Bu the Nova code to call the DELETE for ARQs is not done yet. If you want to take that up, NP. But please be aware that this will be on the critical path. 03:40:27 If you want to leave comments, that is also fine 03:40:53 Or you cold make it a patch on top of this patch series, kinda like what Li_Liu plans to do 03:41:23 xinranwang: ^ 03:42:05 Ok, it's fine for me to submit patch on your patch series. 03:42:16 Thanks, xinranwang. 03:42:23 NP :) 03:42:49 9-12am every day? 03:43:23 Coco_gao: :) As much as we can. Or perhaps you post on IRC and ping the other person on WeChat 03:43:45 I think it is not mandatory. Sundar's plan +1 03:43:55 This is just to facilitate communication -- not meant to be a binding rule 03:44:05 got that 03:44:27 9-12am sounds good 03:44:32 Li_Liu: For developing patches in a series, please look at https://docs.openstack.org/contributors/code-and-documentation/patch-series-tutorial.html 03:44:46 Thanks a lit 03:44:46 Sundar__: got it, thanks 03:44:49 lot* 03:45:54 Sorry that the pilot code is still not merged. I feel like I should write more UT and implement all comments. That has been a stretch. But I'll make it a priority 03:46:04 I remember there is a tools that can run irc background all the time, which nova guys usually use. I will check it 03:46:35 irccloud can notify when offline, but only in paid version, right? 03:47:09 I see, 5$ for permanet use. 03:47:13 I am not sure, cause i didn't pay for it. lol 03:47:16 I want to know such a tool, if possible, for free :) 03:47:47 I think the tools i mentioned before is a kind of extension 03:48:32 ikuo_: I will let you know if I find it :) 03:48:44 Thanks, xinranwang! 03:48:54 xinranwang: Please share after you find out about this. Thanks! 03:49:02 I paid for Irccloud 03:49:02 Sure 03:49:07 #topic Cyborg patches 03:49:09 it works great so far 03:49:45 https://review.opendev.org/659233 -- xinranwang, can you rewrite this to use our own placement calling code? 03:50:07 I see. thanks Li_Liu! 03:51:52 Sundar__: Yes, will do it. I am working on a cyborg DEMO which required by customers recently, and do not have much time on this. I will update it ASAP. 03:54:28 Thanks 03:54:46 I have provided some comments on other specs and patches 03:55:09 Any questions or comments on specs or patches? 03:55:17 I post some comments and questions to the spec yesterday, pls see them. 03:55:27 in here: https://review.opendev.org/#/c/659233/ 03:55:58 soryy 03:56:00 https://review.opendev.org/#/c/626057/ 03:57:09 Thanks, ikuo_ and all. Yes, I'll respond and fix them as much as practical. 03:57:37 #topic AoB 03:57:46 Anything else for today? 03:58:02 fine. thanks. 03:58:26 Have a good day (or night), everybody! 03:58:31 #endmeeting