03:09:18 #startmeeting openstack-cyborg 03:09:19 Meeting started Wed May 22 03:09:18 2019 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:09:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:09:22 The meeting name has been set to 'openstack_cyborg' 03:09:29 #topic Roll Call 03:09:42 #info liliu 03:09:46 #info wangzhh 03:10:11 #info Sundar 03:10:19 Hi Li_liu, wangzhh 03:10:34 Hi Sundar 03:10:37 Hi Sundar, Uncle Li. 03:11:15 Wait a min for other folks? 03:11:41 Yep. 03:12:34 #info xinranwang 03:12:45 Hi Xin-ran 03:13:00 HI all 03:13:14 Ok, let's get rolling 03:13:18 Agenda: https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda 03:13:24 Any thing to add to it? 03:14:07 looks good 03:14:23 #topic Cyborg specs 03:14:25 https://review.opendev.org/#/q/status:open+project:openstack/cyborg-specs 03:15:05 I have reviewed most of them 03:15:18 only one left is Yikun's patch 03:15:40 Cool. Any more comments on https://review.opendev.org/602978? 03:15:43 at a glance, it looks good. will look into it 03:16:28 Cool. I suspect that and https://review.opendev.org/658263 will be quasi-prerequisites to merging Nova spec 03:17:15 #Nova spec 03:17:30 #topic Nova spec 03:17:32 https://review.opendev.org/#/c/603955/ 03:18:37 I presume all of you have looked at it. The main issue now is that a quarum of Nova developers want to move the binding into nova compute, which gives less time for FPGA programming or other device prep 03:18:45 *quorum 03:19:11 It may work for Neutron, because port binding is not a time-consuming op. 03:19:36 when FPGA is programming, nova is waiting for the external event 03:19:58 is there a requirement on how long this process could take? 03:21:15 There are no firm requirements. We want to minimize the Nova wait of course. The times vary widely depending on the device, bitstream size, etc. Somewhere between seconds and a few tens of seconds would be in the ballpark 03:21:53 I think around 10s is totally acceptable 03:23:04 The VM spawn is held up for that period of time. That will cut into bulk VM creation rate, which matters for some scenarios 03:23:23 Anyways, Li_Liu, when can we have the patches for Nova notification? I was hoping to use them to do some measurements. 03:23:54 I am still working on it. 03:24:07 give me some time 03:24:29 still in China, my working hour is in pieces... 03:24:40 can we use os profile to test how long program will take? 03:24:55 is it helpful? 03:25:13 I see. Understand. The problem is, the Nova spec is held up for that time. 03:25:48 xinranwang: The question is not, how long programming will take. It is: how much of it can we overlap with other tasks? The older model overlapped more than the newer proposed model 03:26:11 Anyways, I'll try to hack up something meanwhile and get some data 03:27:18 Anything else to discuss about Nova spec? 03:27:47 #topic Pilot merge plan 03:28:33 If I understood correctly, the consensus is to apply some comments and merge the pilot into master? 03:28:57 i.e. no need to re-submit it as smalle rpatches into master, right? 03:30:58 Silence means yes? :) 03:31:51 Fine. 03:32:20 Thanks, wangzhh. 03:33:16 #agreed Merge pilot into master rather than re-submit it as patches. 03:33:29 #topic Python 3 transition 03:33:55 ikuo_o mentioned somebody else from NTT wll join 03:34:15 yuki is my colleague yes 03:35:02 ikuo_o: You are here ;) Cool. Do you want to discuss the steps for Python 3 transition? 03:36:28 It could be a multi-step process IMHO. You are all welcome to suggest changes or alternatives. 03:37:11 A. Submit some CI tests for Python 3 compliance. They may break at the start, so they may have to be disabled temporarily. 03:37:24 yeah, but gm now moving and have only my small phone. 03:37:39 B. Make the changes to let Py3 pass, and submit those patches. 03:38:29 C. While B is going on, developers may have submitted more patches, which may cause breakage because tests were disabled. So, perhaps another patch to fix them? 03:38:45 D. Enable CI tests, so that every patch will be Py3-compliant after that 03:38:51 Does that make sense? 03:39:13 yuki_t, do you understand the steps? 03:39:45 Welcome yuki_t :) 03:39:56 yes, i understand. 03:40:12 hi, sundar 03:40:35 Great. Thanks. wangzhh, Li_Liu, xinranwang: any comments? 03:41:22 It's great. 03:41:40 I am good 03:41:46 Thanks a lit 03:41:49 lot* 03:42:04 Thank you :) 03:42:17 #topic AoB 03:42:23 May I say the progress of python3 migration? 03:42:31 Do we have any topics for the Zoom call tomorrow? 03:42:37 I am good, thanks a lot 03:43:36 If there are no topics, shall we cancel the call tomorrow? 03:44:45 Sure. 03:45:23 Depends on others. 03:46:21 Sorry, lost connectivity briefly 03:46:31 No other topics, right? 03:47:22 Thanks everybody. Have a great day! 03:47:26 #endmeeting 03:47:32 Bye, all 03:48:04 Hmm, I will re-login with my old nickname to end the meeting later 03:49:07 #endmeeting