Earlier  
Posted Nick Remark
#openstack-cyborg - 2019-08-28
07:45:16 openstackgerrit Xinran WANG proposed openstack/cyborg master: Placement report https://review.opendev.org/659233
12:21:05 openstackgerrit chenker proposed openstack/cyborg master: Fix pep8 error in cyborg/*.py https://review.opendev.org/679042
12:22:33 openstackgerrit chenker proposed openstack/cyborg master: Fix pep8 error in cyborg/*.py https://review.opendev.org/679042
12:26:56 openstackgerrit chenker proposed openstack/cyborg master: Fix pep8 error in cyborg/*.py https://review.opendev.org/679042
12:49:29 openstackgerrit chenker proposed openstack/cyborg master: Fix pep8 error in cyborg/conf and cyborg/cmd https://review.opendev.org/679045
12:50:49 openstackgerrit chenker proposed openstack/cyborg master: P2: Fix pep8 error in cyborg/conf and cyborg/cmd https://review.opendev.org/679045
13:59:41 openstackgerrit chenker proposed openstack/cyborg master: P3: Fix pep8 error in cyborg/common and cyborg/conductor https://review.opendev.org/679062
#openstack-cyborg - 2019-08-29
02:06:02 openstackgerrit chenker proposed openstack/cyborg master: P4: Fix pep8 error in cyborg/api https://review.opendev.org/679172
02:20:37 openstackgerrit Xinran WANG proposed openstack/cyborg master: Fill "driver_name" field in Deployable object https://review.opendev.org/677952
02:46:14 openstackgerrit YumengBao proposed openstack/cyborg master: enable branch selection in devstack installation https://review.opendev.org/669303
02:59:18 openstackgerrit chenker proposed openstack/cyborg master: P5: Fix pep8 error in cyborg/accelerator https://review.opendev.org/679175
03:04:32 Coco_gao_ Hi all
03:04:46 Coco_gao_ Hi Sundar
03:04:51 Coco_gao_ Good evening
03:04:59 Sundar Hi Coco_gao_
03:05:10 shaohe_feng Good evening.
03:05:12 Sundar #startmeeting openstack-cyborg
03:05:13 openstack Meeting started Thu Aug 29 03:05:12 2019 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot.
03:05:14 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
03:05:16 openstack The meeting name has been set to 'openstack_cyborg'
03:05:18 Coco_gao_ #info Coco_gao_
03:05:20 Sundar Hi all
03:05:24 shaohe_feng morning Coco_gao_
03:05:33 s_shogo Hi all
03:05:35 Coco_gao_ morning shaohe
03:05:35 Sundar #topic Attendance
03:05:40 Sundar #info SUndar
03:05:47 s_shogo #info s_shogo
03:05:51 chenke Hi~
03:05:58 Sundar Hi all
03:05:59 chenke #info chenke
03:05:59 Coco_gao_ Hi chenke
03:06:01 shaohe_feng #info shaohe_feng
03:06:07 Yumeng #info Yumeng
03:06:08 yikun #info yikun
03:06:19 chenke Hi Coco_gao_
03:06:19 Sundar Agenda: https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda
03:07:53 Sundar Python 3: Since OpenStack Train release has some Python 3 goals, due by Milestone 3, and it seems that we are close to fixing Py3 issues for Cyborg,
03:08:17 Sundar I have requested s_shogo to make Python 3 tests as a voting job in Zuul.
03:08:27 Sundar Any objections or comments?
03:10:01 Sundar I'll take the silence as agreement. ;) There were requests for fixing Python 3 in the cyborg client too. Luckily, it has taken only 1 patch so far, so we don't need to spend much time on it.
03:10:21 chenke +1
03:11:05 s_shogo I'll do the py3 work in cyborg client, too.
03:11:19 chenke good job
03:12:16 chenke I had modify the tox.ini default env support py36,py37
03:12:22 Coco_gao_ thank you
03:12:26 Sundar s_shogo: The catch is, the current client is for v1 API code and not based on the openstacksdk method. Bringing it to v2 is more important, right?
03:12:27 Coco_gao_ s_shaogo
03:12:35 Coco_gao_ s_shogo
03:12:37 wangzhh Cool.
03:12:49 shaohe_feng https://review.opendev.org/#/c/673228/
03:13:06 shaohe_feng this is a python3 issue fix for client
03:13:25 Sundar But somebody else proposed a patch and it got merged.
03:13:50 s_shogo Sundar: I think so, My openstackSDK patch is made for the v2 Deployable API, now.
03:14:12 s_shogo And the P5-P9 patches doesn't include the migration code , "Deployable" API , from v1 to v2.
03:15:03 Sundar s_shogo: Great. Please add device profiles, as that is more importan IMHO. Operators need to create device profiles to use Cyborg, but doing that with curl is not easy
03:15:26 Coco_gao_ agree, Sundar
03:15:49 Sundar As 2nd priority, I'd say devices -- that will give an inventory of accelerator devices in the cluster
03:16:57 Sundar IMHO, when devices are asked for, we can return the components like deployables and attributes, so the client gets a full picture
03:16:59 shaohe_feng yes, client if more friendly than curl
03:17:25 s_shogo As related the client, the deadline for openstackSDK's commit seems to be near, so would like to begin commit to that, prior to the merge of APIv2 patches.
03:17:34 Sundar Yes, makes sense
03:17:48 Sundar Thanks, s_shogo!
03:18:28 Sundar The main thing that is holding me back is that I am testing P5-P9 with the notification and Placement report patches. Plus, Nova code changes to create a merge conflict for me.
03:18:46 Sundar Once those are resolved, hope we can merge the P5-P9 patches
03:19:01 Sundar ANy other comments on the client, anybody?
03:19:13 shaohe_feng yes, async job depends on P5-P9
03:19:25 s_shogo In my assumption,python-cyborg client and openstacksdk could to be completed before the Train release,
03:19:38 s_shogo but I'm anxious of sufficiency in my test codes, thus please review that in following patches, and help that if necessary.
03:19:38 shaohe_feng great
03:19:53 Sundar shaohe_feng: Agreed. I'll expedite as much as I can.
03:20:06 Sundar s_shogo: Agreed, we'll help for sure
03:20:23 s_shogo Thanks , Sundar
03:20:29 shaohe_feng maybe the test codes can be add later.
03:20:35 Sundar wangzhh: Thanks for proposing the RBAC patch. I had some concerns/questions in the patch. Please take a look.
03:20:50 shaohe_feng firstly let the client can work.
03:21:11 Coco_gao_ s_shogo, thank you . We will review the code.
03:21:28 wangzhh Yep. I have updated my code. May commit after meeting.
03:21:39 Sundar Thanks, wangzhh
03:22:03 s_shogo shaohe_feng : OK, I'll do that preferentially.
03:22:26 Sundar shaohe_feng: Part of the issue is that some Nova developers want to test Cyborg code with Nova code in theor env. Also, we need to show tempest working end-to-end.
03:23:41 Sundar Anybody else trying out the Placement report? With GPUs, AI chip, etc.?
03:23:42 Coco_gao_ What's the remaining work for tempest?
03:23:46 shaohe_feng yes, tempest can eliminate their concerns
03:24:07 Sundar Coco_gao_: It is mostly to get the patches to work together, I think
03:24:34 Sundar Xinran's patches look good IMO. Trying to make sure they work with P5-P9
03:24:51 Yumeng I have tried the Placement report With GPUs
03:25:20 Sundar Yumeng: Good to know
03:25:42 Sundar #topic Nova functional tests
03:26:40 Sundar There was talk at the PTG that we should propose functional tests for Nova, which mock CYborg API in a test fixture, and use that to test Nova patches
03:27:08 Sundar They seem to cover a few more scenarios than unit tests and tempest
03:27:52 Coco_gao_ mock cyborg API's return?
03:27:53 chenke I agree we need to import functional test for nova.
03:28:09 Sundar Coco_gao_: Yes
03:28:44 Sundar We have an entry in the Storyboard too. I have not any comments of late, but there is concern that it may come up at the last moment
03:29:11 Sundar Since there is lots of stuff in Nova runway, it can be tough to get a 2nd look if this issue comes up
03:29:38 Sundar DO we have any volunteers for writing Nova functional tests? I'll help as much as I can
03:31:35 Sundar Please think it over and LMK if you can.
03:32:33 Sundar shaohe_feng: Do you want to bring up the discussion about ARQ states and transitions, as followup? Or is it settled?
03:33:12 shaohe_feng yes

Earlier   Later