Earlier  
Posted Nick Remark
#openstack-cyborg - 2018-10-17
14:06:18 openstack Meeting started Wed Oct 17 14:06:18 2018 UTC and is due to finish in 60 minutes. The chair is Li_Liu. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:06:18 Li_Liu #startmeeting openstack-cyborg
14:06:19 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:06:21 openstack The meeting name has been set to 'openstack_cyborg'
14:06:29 Li_Liu #topic Roll Call
14:06:37 Sundar #info Sundar
14:06:38 Li_Liu #info Li_Liu
14:06:51 wangzhh #info wangzhh
14:07:51 Li_Liu Let's wait for shaohe
14:08:07 Sundar What is the agenda?
14:08:32 Li_Liu We will go over all the pending patches and tasks. and discuss the demo plan for the summit
14:08:48 Sundar I'd like to bring up the need to get reviews for: https://review.openstack.org/#/q/status:open+project:openstack/cyborg-specs
14:09:00 Sundar Next week is Stein-1 milestone
14:09:30 Li_Liu yes
14:09:50 Li_Liu we should get the pending one merged as much as we could
14:11:18 Li_Liu ok, let's get started first
14:11:35 Li_Liu #topic Pending patches
14:11:51 Li_Liu https://review.openstack.org/#/q/status:open%20project:openstack/cyborg
14:11:56 Sundar May be we can start with wangzhh's patch on drivers
14:12:16 Sundar https://review.openstack.org/#/c/596691/ ?
14:12:30 Li_Liu Added Glance Client for Image downloading --- Please help review this so that we can merge. The summit demo needs this one
14:12:55 wangzhh Of course. My patch is based on ovo now.
14:13:38 wangzhh And Sundar, I have sent an email about your questions. Did u get it?
14:14:27 Sundar wangzhh: Sorry, don't remember seeing it. When was it sent?
14:15:03 Li_Liu_ I am back
14:15:04 shaohe_feng #info shaohe_feng_
14:15:07 Li_Liu_ did I miss anything?
14:15:17 Li_Liu_ Hi shaohe
14:15:23 shaohe_feng morning Li_Liu_
14:15:47 wangzhh SundarMaybe this morning for you.
14:16:19 xinran #info xinran
14:16:24 xinran Hi all
14:16:38 Sundar wangzhh: OK. I haven't got it yet. I see your new patch set and responses. Thanks.
14:16:41 wangzhh Hi, xinran shaohe.
14:18:16 Li_Liu back again..
14:18:38 Li_Liu are we gonna merge Xinran's spec?
14:18:47 Li_Liu does it still depend on anything?
14:18:51 Sundar Li_Liu: Re. Glance client, I gave some reviews. Wondering why can't we just call Glance client directly? Do we need a wrapper?
14:19:09 Sundar Li_Liu: which spec?
14:19:20 xinran Li_Liu:
14:19:28 Li_Liu https://review.openstack.org/#/c/597991/
14:20:23 xinran Li_Liu: I have discussed with Sundar offline, the current solution after PTG is different with this one.
14:20:24 Li_Liu Sundar, of course, but I just wanna do it similar to Nova --> created a wrapper API for it
14:20:52 Li_Liu xinran: any plan on updating it?
14:22:15 Li_Liu did I drop?
14:22:24 Li_Liu ah.. i am good :)
14:22:29 xinran Sundar has a new spec https://review.openstack.org/#/c/603955/ in nova community
14:22:49 Li_Liu xinran, so that one will replace yours right?
14:23:04 shaohe_feng hi wangzhh
14:23:33 xinran yes in the future
14:23:49 wangzhh Didn't get the review email about this patch...
14:24:07 shaohe_feng seems I miss something
14:24:24 shaohe_feng something wrong with my net.
14:24:52 shaohe_feng no any message on the screen for a long time.
14:25:15 Sundar Thanks, Xinran. All, please review https://review.openstack.org/608624 . That is the proposed implementation (high-level design) of Cyborg APIs for Nova
14:25:43 xinran but you guys can use https://review.openstack.org/#/c/596187/ this API if it's urgent. It can works with nova, but of course need change code on nova side.
14:26:40 Li_Liu__ Sundar, could you help me run the meeting for now... my connection is so bad
14:26:53 Li_Liu__ I am going through all the patches in https://review.openstack.org/#/q/status:open%20project:openstack/cyborg
14:26:58 wangzhh xinran: So this patch should be abandoned? https://review.openstack.org/#/c/597991/
14:27:06 Sundar Li_Liu: Sure. NP.
14:29:00 Sundar Xinran: On https://review.openstack.org/#/c/601150/, this patch tries to create RP trees from the agent, IIUC. It is better to do it from the conductor
14:29:08 Sundar for the reasons we have discussed in the past
14:29:35 Sundar Also, it is desirable to have all db access from the conductor (and not from the agent)
14:29:52 xinran Hmmm, Sundar do you wanna continue work on this spec https://review.openstack.org/#/c/597991/ or you prefer to create a new one?
14:30:40 Sundar Xinran, I think this spec should be dropped -- that is a better use of your time and energy :)
14:31:01 shaohe_feng why dropped?
14:31:31 Sundar Shaohe: I already explained in the reviews. Basically, this is not in line with the Nova flow at all
14:32:03 shaohe_feng A patch is not perfect, every reviewers should give his comments and let the auther to improve it.
14:32:09 shaohe_feng that's the rule
14:32:30 Sundar I gave my comments
14:33:23 Sundar Think about how this even relates to the Nova spec
14:34:08 shaohe_feng so the summary of new cyborg design:
14:34:32 shaohe_feng 1. split the nova flavor to device profile
14:34:57 shaohe_feng 2. change the accelerator api to var api.
14:34:59 xinran Sundar: I can modify this spec according to your nova spec if you want once your spec is merged.
14:35:00 shaohe_feng right?
14:35:48 xinran Sundar: or you prefer to write a new one by yourself?
14:36:05 Sundar Xinran, Shaohe: we need to start with the Cyborg API signatures proposed for Nova, and work downwards into the details. That is what we do in https://review.openstack.org/#/c/608624/
14:36:51 shaohe_feng what is signatures?
14:37:34 Sundar Shaohe: API parameters, responses, HTTP return codes
14:38:53 Sundar Shahe: re. your question about 2 parts, the device profiles are an important part. So is the whole flow about creating VARs in an unbound state, then binding them, then attaching.
14:40:23 Sundar Aso, the device model where we map deployables to RPs, as we discussed last week
14:41:10 shaohe_feng I do not care you name is var or accelerator.
14:41:35 Sundar A VAR is not an accelerator.
14:41:54 shaohe_feng but as user var is puzzle, like vport.
14:42:35 shaohe_feng var is used for a choose a device to bind to a VM.
14:42:35 Sundar "var is puzzle" -- what does that mean?
14:43:43 Sundar A VAR is a Virtual Accelerator Request. It abstracts the state of the request, starting from user requirements, moving on to the Nova's selection of an alloc cand with device RPs, and then Cyborg bindings
14:43:54 shaohe_feng any project, you seen they expose a var object to user?
14:43:58 Sundar This is conceptually different from what we had before the PTG
14:44:10 shaohe_feng vport, vvolume?
14:44:38 Li_Liu_ shaohe, are you more concern with the naming or the concept?
14:44:56 shaohe_feng the initial design, is Request a Accelerator to VM.
14:45:33 shaohe_feng but we does not name it virtual accelerator, we just named it accelerator
14:45:40 shaohe_feng no need to use virtual
14:45:52 Sundar Shaohe: is this about names, or concepts?
14:46:27 shaohe_feng no need to emphasize virtual
14:46:41 shaohe_feng you can discuss with Li_Liu_ about the accelerator history
14:46:43 shaohe_feng about the name
14:46:48 Li_Liu_ I think "virtual" word indeed confuses a bit

Earlier   Later