Earlier  
Posted Nick Remark
#openstack-cyborg - 2020-01-15
19:10:04 openstackgerrit Sundar Nadathur proposed openstack/cyborg master: Send a separate bind event to Nova for each ARQ in an instance. https://review.opendev.org/698846
#openstack-cyborg - 2020-01-16
00:32:14 openstackgerrit Brin Zhang proposed openstack/cyborg master: Add cyborg quickstart reference in devstack https://review.opendev.org/697419
00:59:36 openstackgerrit Merged openstack/cyborg master: Set ignore_basepython_conflict (fixes confusing pep8 message) https://review.opendev.org/696397
02:59:11 openstackgerrit chenker proposed openstack/cyborg master: Remove useless code for V1 https://review.opendev.org/702785
02:59:56 chenke Hi shogo
03:00:34 s_shogo Hi chenke
03:00:38 brinzhang hi
03:00:38 chenke will you update the client code recently
03:00:44 chenke hi bailin.
03:01:15 s_shogo Ues, correspond to sdk update, thank you for your review >> chenke
03:01:23 s_shogo s/Ues/Yes/
03:01:54 chenke Ok. After you update. I will learn it again.
03:02:13 brinzhang When start the meetting?
03:02:49 chenke maybe we need to wait for sundar,xinran.
03:03:43 brinzhang yeah \o
03:06:19 openstackgerrit Brin Zhang proposed openstack/cyborg master: Add Cyborg quickstart reference in devstack https://review.opendev.org/697419
03:12:29 chenke seems sundar is not here.
03:15:17 Sundar Hi all
03:15:23 s_shogo Hi Sundar
03:15:26 Sundar Sorry, I am late
03:15:30 brinzhang hi
03:15:39 Sundar #startmeeting openstack-cyborg
03:15:40 openstack Meeting started Thu Jan 16 03:15:39 2020 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot.
03:15:41 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
03:15:44 openstack The meeting name has been set to 'openstack_cyborg'
03:15:50 Sundar #topic Who's here
03:15:54 Sundar #info Sundar
03:16:02 s_shogo #info s_shogo
03:16:23 chenke #info chenke
03:16:26 brinzhang #info brnzhang
03:17:56 Sundar For the agenda today, apart from the patch reviews, I was thinking about the security policy refresh, microversions, and the spec for instance ops on accelerators.
03:18:08 Sundar Do any of you have something else to add?
03:18:28 brinzhang I want to talk about http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011990.html
03:18:46 brinzhang Do we need to use the launchpad
03:19:15 Sundar Oh yes. brinzhang, I was planning to reply to that
03:19:41 Sundar brinzhang, we had some discussions last year, and folks decided to go with storyboard.
03:19:57 brinzhang it's ok
03:20:00 Sundar We already have a lot at https://storyboard.openstack.org/#!/project_group/77
03:20:32 brinzhang Either way, as long as it can be managed uniformly, iam ok
03:20:34 Sundar Is there any string advantage to launchpad over storyboard that you want to bring u?
03:20:50 Sundar *strong
03:21:03 Sundar Ok
03:21:26 brinzhang I think the lauchpad was more intuitive
03:21:43 Sundar Is it signficantly faster? I find storyboard to be very slow
03:22:02 brinzhang ore intuitive
03:22:08 brinzhang As far as I know, more people use launchpad than storyboard
03:22:28 brinzhang yeah, launchpad is faster than storyboard
03:23:02 brinzhang sometime the storyboard always stuck
03:23:20 brinzhang so I recommand to use launchpad
03:23:37 Sundar We don't seem to have a quorum today to decide that, or even discuss it at length
03:24:00 Sundar I suggest you can bring it up in a future IRC meeting.
03:24:25 brinzhang yeah, I think this need more people to join, we talk about next topic, i think
03:25:00 Sundar Sure, I'll add this to the meeting agenda at https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting.
03:25:21 chenke Ye.
03:25:25 Sundar We don't have Yumeng today to discuss the policy refresh
03:25:49 chenke I think storyborad is clearer。
03:25:49 chenke I think storyborad is clearer。
03:26:00 Sundar There is a lot of discussions going to microversions. I'd just like to make sure we have a solid footing for the future
03:26:45 Sundar chenke, got it. I suspect folks will have different opinions.
03:26:49 brinzhang Reference the nova microversion, use microversion is more useful
03:26:55 chenke yumeng is out of office.
03:27:27 Sundar brinzhang: yes, microversions are necessary to add features and evolve the APis sommothly, which is important for a young project like Cyborg
03:27:28 brinzhang When a new feature changed in Cyborg, we can record this with a microversion
03:27:56 chenke Agree
03:28:26 brinzhang So about this spec, what are you worry about? Sundar
03:29:34 Sundar brinzhang: I think we all agree on the need for microversions. The questions would be, are we following the best practices etc. I invited Chris Dent etc. to review it. If you see any gaps, please bring it up. It is better to take the time and do this properly to avoid gaps. For example, adopting conventions like docmetning APi changes in release
03:29:34 Sundar notes, as you pointed out in the Nova patch review
03:29:52 Sundar *documenting
03:30:19 brinzhang I'm not sure if the existing Cyborg feature will be implemented after this SPEC merger, or in parallel with it?
03:31:21 Sundar The way I see it, we released v2.0 of APis in Train. Whatever comes out of Ussuri will/should be microversion-enabled and will probably be v2.1. After that, we have incremental changes.
03:31:24 brinzhang yes, we should consider more, such as the unit tests, documenting, functional test etc.
03:32:36 Sundar Until we get Nova integration done, any version bump in Cyborg is not of great significance as people are not yet putting it in production.
03:32:59 brinzhang Sundar, so while someone pushed a spec for Cyborg, we should require he/she to add a new microversion for that api (if the api changes)
03:33:32 Sundar Sure
03:34:14 brinzhang Sundar, Even so, we also need to maintain microversion step by step
03:34:56 Sundar The device v2 APis would be 2.0, because they are totally new. But existing APIs like device profiles and ARQs would get a bump if they are changed.
03:35:38 brinzhang This is my opion for this spec, I will review it again while I free, and refer the experience I was in Nova
03:35:54 Sundar Great, sounds good
03:36:03 Sundar #topic Spec for instance ops for accelerators
03:36:14 brinzhang agree "The device v2 APis would be 2.0"
03:36:29 Sundar https://review.opendev.org/#/c/605237/
03:37:14 brinzhang I was reviewed this spec, I agree with matt, this spec mostly seem description the documents?is right?
03:37:25 Sundar I wrote this last year as a way to get agreement between Nova and Cyborg sides. Some people did not see it as a spec per se, because it is not specifying any changes. It is only documented behavior.
03:37:27 brinzhang some operators are in nova
03:38:03 Sundar Yes, all these are instance ops in Nova, and the doc addresses what should happen if the instance has accelerators
03:38:06 brinzhang Sundar, yeah, it's document
03:38:27 Sundar It may make sense to retire it as a spec and make it a document
03:38:39 brinzhang yeah, it make sense
03:39:10 Sundar Ok, I'll take an action item for that
03:39:14 brinzhang I think we should ensure the accuracy of the description
03:39:58 Sundar Is something not accurate?
03:40:10 brinzhang So we need more nova core to review this, such as erifed, stephenfin, alex_xu, sean-k-moony to review it, make it better and better
03:40:39 brinzhang See my comment in PS4
03:41:02 Sundar They have all reviewed it to some extent or the other in Train. If it is recast as a Cyborg doc, it will be tougher to get their review, but we can try.
03:41:07 brinzhang about the rebuild action, I think you should re-word
03:41:54 Sundar ok, will go by the review
03:42:02 brinzhang Maybe we can send this to the nova meeting
03:42:34 brinzhang Next, i will review again, and check all instance ops
03:42:45 Sundar I'll ask the Nova PTL if that is feasible, after I recast it as a doc
03:43:06 brinzhang Sundar Above is my opinion on this

Earlier   Later