| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2018-10-24 | |||
| 10:11:43 | miniTurtle | hello | |
| 13:06:57 | openstackgerrit | ShaoHe Feng proposed openstack/cyborg master: use context to get project_id and user_id https://review.openstack.org/613012 | |
| 14:02:38 | Sundar | #info Sundar | |
| 14:04:53 | wangzhh | #info wangzhh | |
| 14:05:20 | sum12 | #info sum12 | |
| 14:05:29 | Sundar | Hi Zhenghao | |
| 14:05:43 | Sundar | Has the meeting started? | |
| 14:06:02 | wangzhh | Hi sundar, Li said he would join after 10 minutes. Could help to start the meeting? | |
| 14:06:59 | Sundar | OK. Are you ok with the db schema we have discussed? | |
| 14:07:35 | Sundar | #link https://docs.google.com/document/d/1XLQtvyGJeEgo3ztBQiufWLF-E7S7yGLaYrme8iUPtA0/edit | |
| 14:08:39 | wangzhh | Yes. | |
| 14:09:20 | Coco_gao | Hi | |
| 14:09:35 | Sundar | Great. I still see many patches aimed at the old model. How do we make sure we are al aligned? | |
| 14:09:41 | Sundar | Hi Coco | |
| 14:09:45 | wangzhh | Hi Coco. | |
| 14:10:27 | Coco_gao | The old patches should be updated or merged first? | |
| 14:10:52 | wangzhh | Sundar, you mean the drivers? | |
| 14:11:17 | Sundar | Coco_gao: Yes. Also, newly proposed patches should be based on the new schema. | |
| 14:11:30 | Sundar | wangzhh: No, db schema. Please see the link | |
| 14:11:51 | Coco_gao | xinran's patch and my patch are all based on the old db schema. | |
| 14:12:33 | Li_Liu | Hi guys | |
| 14:12:40 | Coco_gao | Hi, Li | |
| 14:12:43 | Li_Liu | anyone started the meeting already? | |
| 14:12:48 | Li_Liu | Hi Coco | |
| 14:12:51 | wangzhh | Emmm, and my patch is based on CoCo's. | |
| 14:12:57 | wangzhh | Hi, LI. | |
| 14:13:02 | Li_Liu | Hi xiaohei | |
| 14:13:36 | Sundar | OK. The new patch https://review.openstack.org/613012 is also based on old schema | |
| 14:14:19 | Sundar | If I create some Storyboard tasks for new db schema and others, can you all please sign up? | |
| 14:14:40 | Coco_gao | I can | |
| 14:14:47 | Li_Liu | sure | |
| 14:14:54 | wangzhh | Of course. | |
| 14:14:58 | Sundar | Great, thanks! | |
| 14:15:13 | Coco_gao | So what's the conclusion? | |
| 14:15:21 | Coco_gao | new db schema first? | |
| 14:16:00 | Sundar | Coco: Yes, I would say so. Otherwise, lot of our work will be wasted. | |
| 14:17:04 | Sundar | Li_Liu: Can you start the meeting officially? | |
| 14:17:30 | Li_Liu | ah | |
| 14:17:31 | Li_Liu | ok | |
| 14:18:09 | Li_Liu | #startmeeting openstack-cyborg | |
| 14:18:10 | openstack | Meeting started Wed Oct 24 14:18:09 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:18:11 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 14:18:13 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 14:18:21 | Li_Liu | #topic Roll Call | |
| 14:18:29 | Sundar | #info Sundar | |
| 14:18:34 | Li_Liu | #info Li Liu | |
| 14:18:42 | wangzhh | #info wangzhh | |
| 14:18:56 | Coco_gao | #info Coco_gao | |
| 14:19:08 | Sundar | Thanks, Li | |
| 14:19:14 | Li_Liu | #topic DB schema work | |
| 14:19:33 | Sundar | #link https://docs.google.com/document/d/1XLQtvyGJeEgo3ztBQiufWLF-E7S7yGLaYrme8iUPtA0/edit | |
| 14:19:42 | Sundar | Re-posted the link | |
| 14:20:04 | Li_Liu | as we discuss earlier, Sundar will open a Storyboard and put DB tasks there. | |
| 14:20:23 | Sundar | Li_Liu: Yes. | |
| 14:20:41 | Sundar | This is the same schema that was presented by Zoom a couple of weeks ago | |
| 14:20:43 | Coco_gao | Thanks to break down the work | |
| 14:21:03 | wangzhh | And we should start with the new DB schema first. | |
| 14:22:21 | Sundar | Welcome. The next big thing will be the driver-agent API. Some of the APis are already covered in https://review.openstack.org/#/c/608624/ | |
| 14:22:55 | Sundar | That is an important spec, because that is the core of the Cyborg implementation for Nova-Cyborg interaction. Can you all review it? | |
| 14:23:09 | Li_Liu | shall we start with a spec for the new DB schema? | |
| 14:23:55 | wangzhh | Li_liu: I think so. | |
| 14:24:28 | Sundar | Li: OK. Does anybody else want to write that spec? | |
| 14:25:06 | Li_Liu | hmm | |
| 14:25:13 | Li_Liu | I might be able to help | |
| 14:25:20 | wangzhh | Sundar, OK, could u help to add me as a reviewer. https://review.openstack.org/#/c/608624/ | |
| 14:25:27 | Li_Liu | just send all the stuff you got so far, Sundar | |
| 14:26:14 | Sundar | wangzhh: Done | |
| 14:26:25 | Sundar | Li_Liu: That ink is the main one | |
| 14:26:29 | Sundar | *link | |
| 14:27:03 | Li_Liu | ok, I will find some time at night to work on it | |
| 14:27:18 | Sundar | Li_Liu: Great, thanks | |
| 14:27:44 | Sundar | What would be covered in the spoec, apart from tables? | |
| 14:28:26 | Sundar | Are there versioning/upgrade issues, performance aspects (defining index etc.)? | |
| 14:29:06 | Li_Liu | well, shall we give a newer version of the DB? | |
| 14:29:32 | Li_Liu | I though we agreed earlier, we don't need to worry about the upgrade for this change | |
| 14:30:00 | Sundar | Yes, but upgrade from Stein to T may require versioning | |
| 14:30:30 | Sundar | We can implement in phases but don;t we need some plan in Stein for upgrade to T? | |
| 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. | |