| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2018-10-24 | |||
| 14:31:09 | Li_Liu | ok, sure. I will keep that in mind | |
| 14:31:27 | wangzhh | Yes, but we need explain it. Use doc or other way. Maybe someone use the old db schema. | |
| 14:31:43 | Sundar | Also, I was told that upgrade from Rocky to Stein should also be a rolling upgrade. We may need to check what that takes. | |
| 14:32:24 | Sundar | Does any of us have experience with OpenStack upgrades? | |
| 14:34:26 | Coco_gao | I think that will be fine since cyborg not intergrate with nova in Rocky, Rolling upgrade means you upgrade software while not breaking the VM's work. | |
| 14:34:31 | Li_Liu | I know how to write script for migrating DB | |
| 14:34:42 | Li_Liu | just in case it's needed | |
| 14:35:53 | Sundar | Li_Liu: Good to know. Also, we need to address database performance considerations -- creating indexes, joins/query optimizatons, etc. I did stuff that like that a decade ago but not with SqlAlchemy. | |
| 14:36:44 | Sundar | IMHO, documenting the tables in a spec is one thing. Going beyond that to address upgrades and performance will give us all a sense of comfort :) | |
| 14:37:17 | Coco_gao | That's nice to have. | |
| 14:37:55 | Sundar | Also, we may need to set rules/guidelines like, only the conductor can access the db, not the agent. Otherwise we have upgrade issues. | |
| 14:39:01 | Sundar | In the future, may be the API server can also access the db -- others do that for scalability apparently. May be we should keep that for the future till we understand upgrade issues fully | |
| 14:41:24 | Coco_gao | Sundar, may be we can mention that at beginning of your spec on db schema , just in case we forget some day. | |
| 14:42:23 | Li_Liu | I will try to upload the draft asap so that you guys can provide all the comment there :P | |
| 14:42:43 | Sundar | Li_Liu: Sounds good. | |
| 14:43:13 | wangzhh | Thx, Li. | |
| 14:43:53 | Li_Liu | npnp | |
| 14:44:02 | Sundar | The driver-agent API and discovery probably need a new spec. Some of the APIs are already in the spec I mentioned, but that doesn;t cover the driver report structure. | |
| 14:45:23 | wangzhh | Sundar, why we need a new discovery spec? | |
| 14:46:11 | Coco_gao | not discovery spec? | |
| 14:47:04 | Sundar | Sundar: First, it needs to be in cyborg-specs repo, not cyborg. Secondly, the new PTG discussion has to be reflected there, including references to new specs. Also, the relation to new db schema needs to be discussed. | |
| 14:47:50 | Sundar | It could be a single spec that covers the driver API, report structure, etc. | |
| 14:48:24 | wangzhh | So, the workflow of discovery is not different. | |
| 14:49:01 | Sundar | wangzhh: Yes | |
| 14:49:31 | wangzhh | OK, got it. | |
| 14:49:43 | Coco_gao | Can we abondon the old or not implemented specs? everytime I checked the website, I just don't know which spec should I look. | |
| 14:49:45 | wangzhh | Sundar: Thx. | |
| 14:50:25 | Coco_gao | abandon | |
| 14:50:34 | Sundar | Coco_gao: I understand. Do you all think that we should close the old ones? | |
| 14:50:59 | Coco_gao | Yeah | |
| 14:51:19 | wangzhh | I think so. | |
| 14:51:27 | Coco_gao | so many work you have be done on specs~ | |
| 14:52:25 | Coco_gao | Thanks | |
| 14:53:04 | Coco_gao | so many work you have been done on specs~ | |
| 14:53:34 | Sundar | Coco_gao: Welcome, np :) | |
| 14:53:54 | Coco_gao | Have the set-up docs ready? | |
| 14:54:29 | Sundar | Li_Liu: what do you think? Shall we record this as a conclusion? | |
| 14:55:12 | Coco_gao | since the summit is comming, I guess others may ask for the set-up docs or user-guide docs. | |
| 14:56:06 | Li_Liu | agree, we should try to keep it clean | |
| 14:56:24 | Li_Liu | if a spec is not needed, just deprecate it | |
| 14:56:40 | wangzhh | yumen said she had worked on the set-up docs. | |
| 14:56:49 | wangzhh | CoCo. | |
| 14:56:52 | Li_Liu | in case you wanna keep them for a while as reference, mark them | |
| 14:56:55 | Coco_gao | ok, that'll be great | |
| 14:57:36 | Sundar | Li_Liu: deprecate == abandon, right? | |
| 14:58:28 | Li_Liu | deprecate = about to be abandoned | |
| 14:58:49 | Sundar | OK. Thanks. | |
| 14:58:50 | Li_Liu | lol, that should be the exact translation | |
| 15:00:01 | Sundar | We have the devstack install doc. What other set up doc do we need? Until we get the code in, anyway, it is not usable, right? | |
| 15:00:52 | Coco_gao | Yes, devstack install doc is what I mean. | |
| 15:00:54 | Sundar | Li_Liu: I asked because Coco said abandon and you agreed but called it 'deprecate'. | |
| 15:01:59 | Coco_gao | I don't know whether 'abandon' is proper, sorry. | |
| 15:02:06 | Li_Liu | ah. I was just proposing in case we still wanna keep them for a while as reference. if we don't, just abandon the, | |
| 15:02:35 | Sundar | NP, just trying to understand. | |
| 15:03:31 | Sundar | Sorry, I need to drop off for my next call. | |
| 15:03:41 | Coco_gao | anything else to discuss? | |
| 15:03:51 | Coco_gao | Bye, Sundar | |
| 15:04:14 | Sundar | Bye, Coco and all | |
| 15:04:23 | wangzhh | Bye. | |
| 15:04:59 | wangzhh | Li_liu: anything else to disscuss? | |
| 15:07:00 | Coco_gao | bye | |
| 15:07:44 | wangzhh | Byebye. | |
| 15:10:12 | Li_Liu | I will need the meeting now | |
| 15:10:19 | Li_Liu | shall I ? | |
| 15:10:26 | Li_Liu | Sundar, you still there? | |
| 15:15:32 | Li_Liu | #endmeeting | |
| 15:15:35 | openstack | Meeting ended Wed Oct 24 15:15:32 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 15:15:36 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-10-24-14.18.html | |
| 15:15:37 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-10-24-14.18.txt | |
| 15:15:38 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2018/openstack_cyborg.2018-10-24-14.18.log.html | |
| #openstack-cyborg - 2018-10-25 | |||
| 03:28:58 | openstackgerrit | Merged openstack/cyborg master: use context to get project_id and user_id https://review.openstack.org/613012 | |
| 09:03:31 | openstackgerrit | YumengBao proposed openstack/python-cyborgclient master: Remove extra args that keystoneauth1 cannot recongnize https://review.openstack.org/613245 | |
| 09:28:59 | pvc | hi | |
| 09:29:03 | pvc | where should i install the cyborg | |
| 09:29:12 | pvc | on instance or compute node | |
| 09:30:26 | openstackgerrit | YumengBao proposed openstack/python-cyborgclient master: Remove extra args that keystoneauth1 cannot recongnize https://review.openstack.org/613245 | |
| 09:31:28 | openstackgerrit | YumengBao proposed openstack/python-cyborgclient master: Remove extra args that keystoneauth1 cannot recongnize https://review.openstack.org/613245 | |
| 10:44:03 | openstackgerrit | YumengBao proposed openstack/python-cyborgclient master: Remove extra args that keystoneauth1 cannot recongnize https://review.openstack.org/613245 | |
| 18:48:49 | openstackgerrit | ShaoHe Feng proposed openstack/cyborg master: bug fix: missing import keystoneauth1.exceptions https://review.openstack.org/613397 | |
| #openstack-cyborg - 2018-10-26 | |||
| 08:47:18 | openstackgerrit | ShaoHe Feng proposed openstack/cyborg master: bug fix: fix 2 bugs for image client https://review.openstack.org/613397 | |
| 08:49:22 | openstackgerrit | ShaoHe Feng proposed openstack/cyborg master: bug fix: fix 2 bugs for image client https://review.openstack.org/613397 | |
| 14:13:24 | openstackgerrit | Rajat Dhasmana proposed openstack/cyborg master: Add cyborg-status upgrade check command framework https://review.openstack.org/611368 | |
| #openstack-cyborg - 2018-10-27 | |||
| 00:53:43 | openstackgerrit | Sundar Nadathur proposed openstack/cyborg-specs master: Specification for Cyborg API workflows for instance operations. https://review.openstack.org/608624 | |
| 04:07:03 | openstackgerrit | Sundar Nadathur proposed openstack/cyborg-specs master: Specification for instance operations with accelerators. https://review.openstack.org/605237 | |
| 06:31:32 | pvc_ | hi guys | |
| 06:31:41 | pvc_ | i already enabled the VGPU on my openstack | |
| 06:31:46 | pvc_ | and my instance already have an VGPU | |
| 06:31:52 | pvc_ | how can i use cyborg? | |
| 15:10:03 | openstackgerrit | ShaoHe Feng proposed openstack/cyborg master: Added downloading bitstream when programming fpga https://review.openstack.org/611488 | |
| 15:27:38 | openstackgerrit | ShaoHe Feng proposed openstack/cyborg master: Added downloading bitstream when programming fpga https://review.openstack.org/611488 | |
| #openstack-cyborg - 2018-10-29 | |||
| 00:53:38 | pvc | hi | |
| 02:11:40 | pvc | Hello guys | |
| 02:28:34 | zhipeng | Hi pvc | |
| 02:32:21 | pvc | may i know how can i intergrade on my openstack | |
| 02:53:01 | zhipeng | We are still develop for an official integration with Nova for Stein release | |
| 04:01:13 | pvc | so for now i cant use it? | |
| 04:01:17 | pvc | even on my instance? | |
| 06:01:00 | zhipeng | You can use for standalone FPGA programming for example | |
| 08:01:42 | pvc | yes how? | |
| 08:02:26 | pvc | may i know how zhipeng | |