Earlier  
Later
New Search
Posted Nick Remark
#openstack-cyborg - 2019-05-31
01:15:06 wangzhh For we use string as cpid_info, if we split it an convert to json, {"device": "2", "bus": "00", "function": "01"} is not enough.
01:15:59 wangzhh It should looks like {"device": "2", "bus": "00", "function": "01", "domain": "0000"}
01:17:28 wangzhh Am I clear?
01:19:33 wangzhh The cpid_info looks like 0000:00:02.0. The json_str in this patch lost domain.
01:20:14 Coco_gao yes, if cpid_info is a json string, what about the attach_info?
01:22:10 wangzhh I think it is the same.
01:24:05 Coco_gao And cpid_info is used to identify some of the devices, if its a json_str, then it will be hard to identify, because it' s hard to compare json_str.
01:25:26 Coco_gao what do you think?
01:25:39 Coco_gao @Sundar
01:27:23 wangzhh Sundar said he'll BRB in 30 min.
01:31:43 Coco_gao so will I
02:08:13 Sundar @Coco_gao @wangzhh Yes, domain should be included. attach_id also should be fixed in the same way: I'll do that. All good?
02:12:37 Sundar @Coco_gao: "if its a json_str, then it will be hard to identify, because it' s hard to compare json_str" Are you saying that we can store it as individual PCI BDF fields (domain, bus, etc.) in the db? That would not work for PowerVM, which represents PCI devices differently.
02:14:43 wangzhh Fine. Sundar.
02:16:38 wangzhh And do u install znc which xinran mentioned? I don't find windows version.
02:17:18 Sundar wangzhh: znc is linux only
02:18:07 wangzhh OK. Thx.
02:43:18 Sundar @yikun, @wangzhh, @Coco_gao and all, please respond to http://eavesdrop.openstack.org/irclogs/%23openstack-cyborg/%23openstack-cyborg.2019-05-31.log.html#t2019-05-31T00:45:51
07:29:24 wangzhh @yikun Is generic driver ready? New GPU driver depends on it. Or u just responsible for spec, I'm not sure.
#openstack-cyborg - 2019-06-02
06:46:45 openstackgerrit Brin Zhang proposed openstack/cyborg-specs master: Change openstack-dev to openstack-discuss https://review.opendev.org/622031
19:53:10 Sundar FYI: https://review.opendev.org/#/c/662643/ "Categorize Cyborg under Accelerators and update description"
#openstack-cyborg - 2019-06-04
05:12:52 Sundar @all, Shall we have a Zoom call this Thursday China time (Wed in Americas)? Agenda: Review the pending specs and patches.
05:17:21 Sundar Do we need the spec https://review.opendev.org/#/c/593726? We have already implemented discovery, right?
05:27:47 ikuo_o I can attend Thursday zoom meeting.
05:33:00 Sundar Thanks, ikuo_o
13:41:39 Li_Liu should be fine for me to attend the zoom meeting
15:13:06 Sundar Thanks, Li_Liu
15:30:38 Li_Liu Sundar, do we still have the irc meeting tonight then?
15:56:06 Sundar Li_Liu: Yes
18:50:27 openstackgerrit Donny Davis proposed openstack/cyborg master: Updating Index to reflect dependent projects and provide more information on Cyborg https://review.opendev.org/663121
#openstack-cyborg - 2019-06-05
03:00:48 Sundar Hi Biwei
03:00:55 Biwei Hi Sundar
03:01:09 Sundar Hi wangzhh
03:01:16 wangzhh Hi Sundar.
03:01:22 ikuo_o Hi Sundar
03:01:27 Sundar Hi ikuo_o
03:01:34 wangzhh Hi ikuo_o
03:01:44 Sundar Let's wait a min for others to join
03:01:49 ikuo_o Hi wangzhh
03:03:04 Sundar #startmeeting openstack-cyborg
03:03:05 openstack Meeting started Wed Jun 5 03:03:04 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:06 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
03:03:08 openstack The meeting name has been set to 'openstack_cyborg'
03:03:16 Sundar #topic Roll call
03:03:36 Sundar #info Sundar
03:04:24 Sundar wangzhh, ikuo_o, Biwei: o/
03:04:34 yikun #info yikun
03:04:41 wangzhh #info wangzhh
03:04:45 ikuo_o #info ikuo_o
03:04:47 Sundar Hi yikun
03:04:56 Biwei #info Biwei
03:04:58 yikun hey, Sundar
03:05:07 Sundar Agenda: https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda
03:05:13 Sundar ANything to add to that?
03:06:05 Sundar #topic Python cyborg client decision
03:06:10 wangzhh Coco said she has other bussiness. Will miss this meeting.
03:06:24 Sundar Please see the thread starting from http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006543.html
03:06:41 Sundar wangzhh, thanks for letting us know
03:07:38 Sundar For the client, we have 2 options: write our own plugin (as many other projects seem to have done) or integrate with openstackclient repo (less work, but need to depend on the repo owners for reviews)
03:08:56 Sundar For the 2nd option, there are some guidelines and rules, which seem ok to me. But we have to discuss with the repo owners about their opinions
03:08:57 xinranwang Hi all
03:09:04 xinranwang #info xinranwang
03:09:11 Sundar Hi xinranwang
03:09:34 Sundar Writing a plugin may not be that bad, given the previous examples
03:09:39 Sundar What do you all think?
03:09:58 yikun So, we have to choose one from these two option?
03:10:46 Sundar yikun, do you have any other option? These seem like the 2 ways that are recommended or have precedents. We could do neither and write our own client -- but that is not recommended
03:10:47 wangzhh yikun, I think so. Do u have other suggestions?
03:10:56 xinranwang I think writing our own plugin is better
03:11:16 ikuo_o Thanks for summarizing.
03:11:26 xinranwang More indenpendency
03:11:34 wangzhh Yes, I also vote the first one. Agree with xinran.
03:12:31 ikuo_o It is better to write plugin, but I heard the option is not prepared by OSC.
03:12:48 ikuo_o Maybe my misunderstanding...
03:12:49 yikun OK, just want to sure any other way to complete, and I also vote to the 1st
03:12:58 Sundar ikuo_o: "option is not prepared by OSC" -- what do you mean?
03:13:33 Sundar OSC folks are not recomending against plugin -- they gave us the options.
03:13:52 xinranwang please also consider the case where cyborg can run as a standalone project
03:14:24 Sundar xinranwang: Sure, both options should be compatible with standalone usage
03:15:17 ikuo_o If it is realized in other works, plugin is better I think.
03:15:17 ikuo_o I see. I thought the plugin option is difficult for OSC side, but maybe my misunderstanding
03:15:19 wangzhh Sundar, do u have any example of these two options? Maybe two different projects with two options.
03:15:51 xinranwang We do have the cyborgclient repo with some V1 APIs implemented, right?
03:16:00 Sundar wangzhh: There are many examples of plugins: https://docs.openstack.org/python-openstackclient/pike/contributor/plugins.html
03:16:06 wangzhh Thx.
03:16:20 Biwei https://github.com/openstack/python-cyborgclient is that what you are talking about? Xinran
03:17:11 xinranwang Biwei: Ah yes, thanks
03:17:14 Sundar wangzhh: Some examples of commands integrated with OSC: https://github.com/openstack/python-openstackclient/tree/master/openstackclient
03:17:22 yikun wangzhh: I think the nova is 2nd(https://github.com/openstack/python-openstackclient/blob/master/setup.cfg), and placement is 1st example
03:17:23 Sundar Includes compute, identity, etc.
03:17:52 wangzhh Cool, Thx Sundar, yikun.
03:17:52 yikun https://github.com/openstack/osc-placement
03:18:13 Sundar xinranwang: The cyborg client for v1 API is neither: it uses osc-like syntax but is not a plugin
03:18:34 yikun Can we complete it by 1st way first, and we our client is stable, and we switch it to 2nd way?
03:18:48 Sundar ikuo_o: IIUC, you are also voting for plugin? or are you still considering?
03:18:51 yikun Can we complete it by 1st way first, and when our client is stable, and we switch it to 2nd way?
03:19:15 ikuo_o Sundar: I vote plugin.
03:19:19 Sundar yikun: What would motivate us to switch like that?
03:20:03 yikun We need +2+a right at first, because we perhaps frequently at first version.
03:20:04 xinranwang Is there any necessity to switch to 2nd way?

Earlier   Later