| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2019-06-06 | |||
| 03:40:14 | Sundar | xinranwang: ^ | |
| 03:41:11 | xinranwang | So no CI env need to be set up. Just code.(nova fixture, fake driver). Right? | |
| 03:41:55 | Sundar | Plus the tempest plugins for basic test cases which will call fake driver | |
| 03:42:55 | Sundar | We don't need the hardware-based CI, if that's what you mean | |
| 03:43:15 | Sundar | We do need a tempest CI env, which we are in the process of creating | |
| 03:44:10 | xinranwang | yes, sure. test_boot_vm_with_accl will be implemented in tempest plugin. I am working on this. | |
| 03:44:32 | xinranwang | But I will test it with real env. | |
| 03:47:02 | xinranwang | Hmmm, I think no need for tempest CI, we can use Zuul directly to run tempest. Just add a cyborg tempest plugin? what do you think? yikun | |
| 03:58:13 | yikun | yes, I think functional test need fake cyborg api, and tempest only need a tempest plugin, but I don't know how this plugin work in a real env. | |
| 04:01:34 | Sundar | yikun, xinwanwang: # openstack-qa is the IRC channel for tempest etc. We can ask there. | |
| 04:02:58 | Sundar | xinranwang: ^ | |
| 04:04:55 | xinranwang | OK | |
| 04:05:49 | Sundar | Please join that channel. I'll ask the question there, and you all can add/clarify | |
| 04:06:38 | xinranwang | I will go for lunch now. Will be back soon | |
| #openstack-cyborg - 2019-06-11 | |||
| 10:02:43 | openstackgerrit | huang liujie proposed openstack/cyborg master: Sync Sphinx requirement https://review.opendev.org/664548 | |
| 10:04:41 | openstackgerrit | huang liujie proposed openstack/cyborg master: Sync Sphinx requirement https://review.opendev.org/664548 | |
| #openstack-cyborg - 2019-06-12 | |||
| 01:34:44 | openstackgerrit | Merged openstack/cyborg master: Dropping the py35 testing https://review.opendev.org/659898 | |
| 01:54:07 | openstackgerrit | Merged openstack/cyborg-specs master: Replace git.openstack.org URLs with opendev.org URLs https://review.opendev.org/654984 | |
| 01:56:23 | openstackgerrit | Merged openstack/cyborg-specs master: Use opendev repository https://review.opendev.org/654924 | |
| 01:56:24 | openstackgerrit | Merged openstack/cyborg-specs master: Change openstack-dev to openstack-discuss https://review.opendev.org/622031 | |
| 03:01:09 | Sundar | Hi wangzhh, Biwei | |
| 03:01:17 | Biwei | Hi Sundar | |
| 03:01:23 | Sundar | Let's wait a couple of min for folks to join | |
| 03:01:39 | ikuo_o | Hi Sundar, Biwei | |
| 03:01:47 | Sundar | Hi ikuo_o | |
| 03:01:53 | yikun | Hi | |
| 03:01:59 | Sundar | Hi yikun | |
| 03:02:04 | Li_Liu | Hi Sundar | |
| 03:02:15 | Sundar | Hi Li_Liu | |
| 03:02:25 | wangzhh | Hi Sundar. | |
| 03:02:29 | Sundar | #startmeeting openstack-cyborg | |
| 03:02:30 | openstack | Meeting started Wed Jun 12 03:02:29 2019 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 03:02:31 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 03:02:34 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 03:02:51 | Sundar | #topic Roll call and agenda | |
| 03:02:51 | xinranwang | Hi all | |
| 03:02:58 | Sundar | #info Sundar | |
| 03:03:06 | wangzhh | #info wangzhh | |
| 03:03:10 | Biwei | #info Biwei | |
| 03:03:12 | ikuo_o | #info ikuo_o | |
| 03:03:34 | yikun | #info yikun | |
| 03:03:41 | Sundar | Agenda: https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda | |
| 03:03:43 | xinranwang | #info xinranwang | |
| 03:03:54 | Sundar | Anything to add to agenda? | |
| 03:04:27 | Sundar | #topic Cyborg CI | |
| 03:05:02 | Sundar | As we have said, we need two things to merge Nova patches: Nova functional test with fake Cyborg API, and tempest CI with fake driver | |
| 03:05:37 | Sundar | Taking the tempest one first, xinranwang and Biwei are working on the general framework and plugins. | |
| 03:06:13 | Sundar | For the fake driver, yikun has kindly agreed. But he needs help. I'll help as much as I know. | |
| 03:06:23 | Sundar | It would be great if others can also help him out. | |
| 03:06:43 | Sundar | yikun, please feel free to ask questions. | |
| 03:07:03 | Sundar | ANy comments or questions on fake driver and/or tempest? | |
| 03:07:18 | Li_Liu | #info Li_Liu | |
| 03:07:25 | ikuo_o | Thanks Yikun. | |
| 03:07:29 | yikun | I still don't know what is the real requirement of fake driver. I assume it's just a driver that will return empty or just pass | |
| 03:07:55 | xinranwang | Biwei and I are working on the tempest test case and general framework. We will test them in real env, once the fake driver is implemented, yikun can use these testcases. | |
| 03:08:26 | yikun | and also, we should merge these two patch, :) https://review.opendev.org/#/c/658986 https://review.opendev.org/#/c/658987 | |
| 03:08:38 | yikun | and then I can append the patch base on these two | |
| 03:08:42 | xinranwang | real env means an openstack env with fpga | |
| 03:08:49 | Sundar | yikun: The fake driver ill be a derivative of the generic driver, which will return some pre-defined driver OVO for discover() | |
| 03:09:52 | yikun | Sundar: ok, will summit a patch this week, and any detail comments can be happened in the patch | |
| 03:09:56 | Sundar | It can return success or NULL for other APIs. | |
| 03:10:21 | Sundar | yikun: Great, thanks. Please ensure the fake driver is added to the tempest repo. | |
| 03:10:25 | yikun | Sundar: got it | |
| 03:10:46 | Sundar | Now, for the Nova functional test | |
| 03:11:03 | Sundar | Can somebody take that up? | |
| 03:11:35 | Sundar | It will just mock the Cyborg APIs called by Nova -- get device profile, post/patch/delete ARQs | |
| 03:12:19 | yikun | “Please ensure the fake driver is added to the tempest repo.” not sure why it is tempest repo? | |
| 03:12:33 | yikun | I thought it should be in cyborg repo | |
| 03:13:22 | Biwei | yikun, there's a cyborg-tempest-plugin repo, living outside of the cyborg repo | |
| 03:14:12 | Sundar | The tempest plugins are going to call that fake driver. | |
| 03:14:22 | xinranwang | Sundar: what should fake driver return exactly, the info returned by this fake driver will be used in nova to boot vm, right ? | |
| 03:15:19 | Sundar | xinranwang: Yes. Its discover() API should return a pre-defined device OVO object | |
| 03:15:26 | yikun | Biwei: OK, https://github.com/openstack/cyborg-tempest-plugin | |
| 03:15:43 | xinranwang | Sundar: tempest has api test and scenario test, those 2 types only interact with API layers, I don't think tempest should call driver directly. | |
| 03:15:44 | Sundar | It could define a device with soem fake controlpath-IDs, 1 deployable and an attach handle, all with fake PCI addresses | |
| 03:15:51 | xinranwang | Biwei: what do you think? | |
| 03:16:17 | xinranwang | Sundar: yes, but what info stored in this OVO, like pci address | |
| 03:16:29 | Biwei | tempest will not call driver directly | |
| 03:17:26 | Sundar | Can be totally bogus PCI addresses. The VM may not boot up without the hardware. | |
| 03:17:51 | Sundar | To quote Eric Fried: "It should be sufficient to wait for the instance to go ACTIVE (according to Nova) (which will happen even if the guest OS boot pukes) and scrape its domain XML to assert that the correct PCI devices are present." | |
| 03:18:56 | yikun | Biwei: how to call driver directly, shouldn't it call cyborg api and cyborg api call the fake driver | |
| 03:19:00 | Sundar | Biwei Yes. Not sure if the CYborg agent will call driver API in tempest env, as it happens in real env | |
| 03:20:19 | Biwei | Sundar in tempest test, we only need to call the cyborg restful APIs. | |
| 03:20:25 | Sundar | The API invocation need not even call the driver -- as long as the driver has reported the device(s). | |
| 03:21:03 | yikun | Biwei: "Sundar in tempest test, we only need to call the cyborg restful APIs." < Yes, so the fake driver should be in cyborg repo, right? | |
| 03:21:27 | yikun | and tempest should do something config the cyborg to use the fake dirver | |
| 03:21:58 | Sundar | Biwei, if there were some way to set up the Cyborg database in tempest env, like I did with initial_setup.sh in pilot code, we may not even need a fake driver perhaps | |
| 03:22:27 | Sundar | Have you seen if tempest can run some script to set up the env? | |
| 03:22:37 | xinranwang | I have some discussion with others like Alex, Shaohe. We are not sure if the status will switch to active in that case. I test in local with fake device, it failed. | |
| 03:22:57 | Biwei | I haven't figured that out yet. I have done the steps including creating flavor and update the flavor with device and all working so far | |
| 03:23:39 | Biwei | but not sure how to do the database set up | |
| 03:24:44 | xinranwang | tempest run in an installed openstack env where already have cybrog db, every thing same as a real env | |
| 03:24:54 | Sundar | xinranwang: True, I think it goes to error state. However, if we can do 'virsh dumpxml' equivalent and look for the hostdev device, that should be good enough | |
| 03:26:20 | xinranwang | Sundar: yes, I agree, but nova api will return error directly to tempest. where should we got the xml from virt driver. | |
| 03:26:47 | Sundar | Can you run a comand like 'virsh dumpxml'? | |
| 03:27:04 | xinranwang | you mean in tempest? | |
| 03:27:08 | Sundar | Yes | |
| 03:28:49 | xinranwang | I am not sure if libvirt will really boot it, I wonder that libvirt may do pci | |
| 03:29:17 | xinranwang | I am not sure if libvirt will really boot it, I wonder that libvirt may do pci check first before boot a vm | |
| 03:29:48 | Sundar | I have tried to launch a VM inside a development VM. It will error out but the VM exists in error state as shown by 'openstack server list' | |