Wednesday, 2018-10-24

*** fanzhang has joined #openstack-cyborg02:08
*** openstackgerrit has joined #openstack-cyborg03:55
openstackgerritYumengBao proposed openstack/cyborg master: Deploy cyborg-api via uwsgi
openstackgerritMerged openstack/cyborg master: PY3 : Replice dict.iteritems() with dict.items()
openstackgerritMerged openstack/cyborg master: Don't quote {posargs} in tox.ini
openstackgerritMerged openstack/cyborg master: Deploy cyborg-api via uwsgi
openstackgerritYumengBao proposed openstack/cyborg master: [docs] Deploy cyborg api under WSGI server
*** helenafm has joined #openstack-cyborg07:21
*** sahid has joined #openstack-cyborg07:47
*** miniTurtle has joined #openstack-cyborg09:13
openstackgerritRajat Dhasmana proposed openstack/cyborg master: Fix imports in spdk driver
*** sahid has quit IRC10:12
openstackgerritShaoHe Feng proposed openstack/cyborg master: use context to get project_id and user_id
*** wangzhh has joined #openstack-cyborg13:56
*** Sundar has joined #openstack-cyborg14:02
Sundar#info Sundar14:02
wangzhh#info wangzhh14:04
sum12 #info sum1214:05
SundarHi Zhenghao14:05
SundarHas the meeting started?14:05
wangzhhHi sundar, Li said he would join after 10 minutes. Could help to start the meeting?14:06
SundarOK. Are you ok with the db schema we have discussed?14:06
*** Coco_gao has joined #openstack-cyborg14:08
SundarGreat. I still see many patches aimed at the old model. How do we make sure we are al aligned?14:09
SundarHi Coco14:09
wangzhhHi Coco.14:09
Coco_gaoThe old patches should be updated or merged first?14:10
wangzhhSundar, you mean the drivers?14:10
SundarCoco_gao: Yes. Also, newly proposed patches should be based on the new schema.14:11
Sundarwangzhh: No, db schema. Please see the link14:11
Coco_gaoxinran's patch and my patch are all based on the old db schema.14:11
*** Li_Liu has joined #openstack-cyborg14:12
Li_LiuHi guys14:12
Coco_gaoHi, Li14:12
Li_Liuanyone started the meeting already?14:12
Li_LiuHi Coco14:12
wangzhhEmmm, and my patch is based on CoCo's.14:12
wangzhhHi, LI.14:12
Li_LiuHi xiaohei14:13
SundarOK. The new patch is also based on old schema14:13
SundarIf I create some Storyboard tasks for new db schema and others, can you all please sign up?14:14
Coco_gaoI can14:14
wangzhhOf course.14:14
SundarGreat, thanks!14:14
Coco_gaoSo what's the conclusion?14:15
Coco_gaonew db schema first?14:15
SundarCoco: Yes, I would say so. Otherwise, lot of our work will be wasted.14:16
SundarLi_Liu: Can you start the meeting officially?14:17
Li_Liu#startmeeting openstack-cyborg14:18
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:18
*** openstack changes topic to " (Meeting topic: openstack-cyborg)"14:18
openstackThe meeting name has been set to 'openstack_cyborg'14:18
Li_Liu#topic Roll Call14:18
*** openstack changes topic to "Roll Call (Meeting topic: openstack-cyborg)"14:18
Sundar#info Sundar14:18
Li_Liu#info Li Liu14:18
wangzhh#info wangzhh14:18
Coco_gao#info Coco_gao14:18
SundarThanks, Li14:19
Li_Liu#topic DB schema work14:19
*** openstack changes topic to "DB schema work (Meeting topic: openstack-cyborg)"14:19
SundarRe-posted the link14:19
Li_Liuas we discuss earlier, Sundar will open a Storyboard and put DB tasks there.14:20
SundarLi_Liu: Yes.14:20
SundarThis is the same schema that was presented by Zoom a couple of weeks ago14:20
Coco_gaoThanks to break down the work14:20
wangzhhAnd we should start with the new DB schema first.14:21
SundarWelcome. The next big thing will be the driver-agent API. Some of the APis are already covered in
SundarThat is an important spec, because that is the core of the Cyborg implementation for Nova-Cyborg interaction. Can you all review it?14:22
Li_Liushall we start with a spec for the new DB schema?14:23
wangzhhLi_liu: I think so.14:23
SundarLi: OK. Does anybody else want to write that spec?14:24
Li_LiuI might be able to help14:25
wangzhhSundar, OK, could u help to add me as a reviewer.
Li_Liujust send all the stuff you got so far, Sundar14:25
Sundarwangzhh: Done14:26
SundarLi_Liu: That ink is the main one14:26
Li_Liuok, I will find some time at night to work on it14:27
SundarLi_Liu: Great, thanks14:27
SundarWhat would be covered in the spoec, apart from tables?14:27
SundarAre there versioning/upgrade issues, performance aspects (defining index etc.)?14:28
Li_Liuwell, shall we give a newer version of the DB?14:29
Li_LiuI though we agreed earlier, we don't need to worry about the upgrade for this change14:29
SundarYes, but upgrade from Stein to T may require versioning14:30
SundarWe can implement in phases but don;t we need some plan in Stein for upgrade to T?14:30
Li_Liuok, sure. I will keep that in mind14:31
wangzhhYes, but we need explain it. Use doc or other way. Maybe someone use the old db schema.14:31
SundarAlso, I was told that upgrade from Rocky to Stein should also be a rolling upgrade. We may need to check what that takes.14:31
SundarDoes any of us have experience with OpenStack upgrades?14:32
Coco_gaoI 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
Li_LiuI know how to write script for migrating DB14:34
Li_Liujust in case it's needed14:34
SundarLi_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:35
SundarIMHO, 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:36
Coco_gaoThat's nice to have.14:37
SundarAlso, we may need to set rules/guidelines like, only the conductor can access the db, not the agent. Otherwise we have upgrade issues.14:37
SundarIn 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 fully14:39
Coco_gaoSundar, may be we can mention that at beginning of your spec on db schema , just in case we forget some day.14:41
Li_LiuI will try to upload the draft asap so that you guys can provide all the comment there :P14:42
SundarLi_Liu: Sounds good.14:42
wangzhhThx, Li.14:43
SundarThe 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:44
wangzhhSundar, why we need a new discovery spec?14:45
Coco_gaonot discovery spec?14:46
SundarSundar: 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
SundarIt could be a single spec that covers the driver API, report structure, etc.14:47
wangzhhSo, the workflow of discovery is not different.14:48
Sundarwangzhh: Yes14:49
wangzhhOK, got it.14:49
Coco_gaoCan 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
wangzhhSundar: Thx.14:49
SundarCoco_gao: I understand. Do you all think that we should close the old ones?14:50
wangzhhI think so.14:51
Coco_gaoso many work you have be done on specs~14:51
Coco_gaoso many work you have been done on specs~14:53
SundarCoco_gao: Welcome, np :)14:53
Coco_gaoHave the set-up docs ready?14:53
SundarLi_Liu: what do you think? Shall we record this as a conclusion?14:54
Coco_gaosince  the summit is comming, I guess others may ask for the set-up docs or user-guide docs.14:55
Li_Liuagree, we should try to keep it clean14:56
Li_Liuif a spec is not needed, just deprecate it14:56
wangzhhyumen said she had worked on the set-up docs.14:56
Li_Liuin case you wanna keep them for a while as reference, mark them14:56
Coco_gaook, that'll be great14:56
SundarLi_Liu: deprecate == abandon, right?14:57
Li_Liudeprecate = about to be abandoned14:58
SundarOK. Thanks.14:58
Li_Liulol, that should be the exact translation14:58
SundarWe 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
Coco_gaoYes, devstack install doc is what I mean.15:00
SundarLi_Liu: I asked because Coco said abandon and you agreed but called it 'deprecate'.15:00
Coco_gaoI don't know whether 'abandon' is proper, sorry.15:01
Li_Liuah. 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
SundarNP, just trying to understand.15:02
SundarSorry, I need to drop off for my next call.15:03
Coco_gaoanything else to discuss?15:03
Coco_gaoBye, Sundar15:03
SundarBye, Coco and all15:04
*** Sundar has quit IRC15:04
wangzhhLi_liu: anything else to disscuss?15:04
*** Li_Liu has quit IRC15:06
*** Li_Liu has joined #openstack-cyborg15:10
Li_LiuI will need the meeting now15:10
Li_Liushall I ?15:10
Li_LiuSundar, you still there?15:10
*** openstack changes topic to "Pending patches (Meeting topic: openstack-cyborg)"15:15
openstackMeeting ended Wed Oct 24 15:15:32 2018 UTC.  Information about MeetBot at . (v 0.1.4)15:15
openstackMinutes (text):
*** munimeha1 has joined #openstack-cyborg15:58
*** helenafm has quit IRC16:29
*** irclogbot_1 has quit IRC17:08
*** Coco_gao has quit IRC17:08
*** wangzhh has quit IRC17:16
*** Li_Liu has quit IRC18:21
*** egallen has joined #openstack-cyborg18:42
*** sum12 has quit IRC18:48
*** egallen_ has quit IRC18:48
*** sum12 has joined #openstack-cyborg18:49
*** openstackgerrit has quit IRC19:06
*** irclogbot_1 has joined #openstack-cyborg19:24
*** irclogbot_1 has quit IRC20:21
*** openstack has quit IRC21:03
*** openstack has joined #openstack-cyborg21:07
*** ChanServ sets mode: +o openstack21:07
*** efried has quit IRC22:15
*** efried has joined #openstack-cyborg22:15

Generated by 2.15.3 by Marius Gedminas - find it at!