| openstackgerrit | Merged openstack/valence master: Fix podmanager create and update functions https://review.openstack.org/475659 | 00:05 |
|---|---|---|
| openstackgerrit | Merged openstack/python-valenceclient master: Updated from global requirements https://review.openstack.org/484588 | 00:08 |
| *** openstackgerrit has quit IRC | 08:49 | |
| *** ramineni_ has joined #openstack-valence | 14:24 | |
| *** ntpttr_laptop has joined #openstack-valence | 14:26 | |
| ramineni_ | Hi All | 14:28 |
| mkrai | Hi | 14:28 |
| lin_yang | Hi | 14:29 |
| ntpttr_laptop | o/ | 14:30 |
| ntpttr_laptop | hey everyone | 14:30 |
| ntpttr_laptop | looks like nobody has written any specific topics for today on the agenda | 14:31 |
| ntpttr_laptop | does anyone have something they'd like to discuss with the team? | 14:32 |
| ntpttr_laptop | glad we got all of our summit proposals in on time, and they looked good :) | 14:32 |
| mkrai | Yes waiting for the voting to open :) | 14:33 |
| ntpttr_laptop | thanks for everyone's work on that | 14:33 |
| lin_yang | when the voting will be open? | 14:33 |
| ramineni_ | ntpttr_laptop: mkrai: right :) | 14:33 |
| ntpttr_laptop | not sure, but probably won't be too long. I'll keep an eye out for it | 14:34 |
| mkrai | next week most probably | 14:34 |
| ntpttr_laptop | looks like shuquan and bian aren't here today, this may end up being a short meeting | 14:34 |
| mkrai | If I remember correctly its 25th july | 14:34 |
| ramineni_ | ntpttr_laptop: may be we can finalize on how to proceed with resource management, unified resource DB | 14:34 |
| ntpttr_laptop | I'll make sure to get reviews done for everything in my backlog | 14:34 |
| ntpttr_laptop | ramineni_: sure | 14:34 |
| ramineni_ | if have time | 14:34 |
| ntpttr_laptop | ramineni_: looks like we definitely do :) | 14:34 |
| ntpttr_laptop | I'm happy to implement a DB that contains more information, should we have an entry for each device or one for attachable devices in general? | 14:36 |
| ntpttr_laptop | what added info should be included? | 14:36 |
| ntpttr_laptop | obviously in use/not in use for attachable and composable resources | 14:37 |
| mkrai | I vote for seperate db in general but not sure of the information to be added in db | 14:38 |
| ramineni_ | ntpttr_laptop: once the node is composed , the resources which can be used for dymanic attachment after composing | 14:39 |
| lin_yang | agree, including node uuid if this device is in use will be helpful | 14:39 |
| ntpttr_laptop | I can rework the spec based on the comments you guys have left, I have a decent idea about what we want to do there | 14:39 |
| ramineni_ | we can include all resources in one DB? | 14:39 |
| ntpttr_laptop | ramineni_: probably not if we do this | 14:39 |
| ramineni_ | https://github.com/openstack/valence/blob/master/api-ref/source/valence-api-v1-pooled.inc | 14:39 |
| ramineni_ | these attributes specifed here looks useful to me for managing pooled resources, we can store in DB, | 14:40 |
| ntpttr_laptop | should we include things like details about stuff like systems in our DB, like memory amount and the like? | 14:40 |
| ramineni_ | ntpttr_laptop: i meant we have one sperate devices DB, | 14:40 |
| ramineni_ | no, pooled_group_id, resource state ,resource type | 14:41 |
| ramineni_ | i thought these would be useful | 14:41 |
| ntpttr_laptop | ramineni_: what is the pooled_group_id? | 14:41 |
| ramineni_ | ntpttr_laptop: in our hardware it would specify , which node it can be attached | 14:42 |
| lin_yang | ntpttr_laptop: for device detail, I am afraid that not all device have the same attributions | 14:42 |
| mkrai | lin_yang: I agree | 14:43 |
| ntpttr_laptop | true, they don't | 14:43 |
| ramineni_ | lin_yang: properties or extra info should be good? to categorize them if want to be stored | 14:43 |
| ramineni_ | otherwise we can leave it | 14:43 |
| *** Mrittika has joined #openstack-valence | 14:44 | |
| ntpttr_laptop | this design is left over from when we originally designed what we wanted from the DB with malini, and talked about not storing details like that on our side but pointing to them in the pod to be able to make calls and get details | 14:44 |
| ntpttr_laptop | for things like lists you'd list what we have in the db, pod, location, uuid, etc | 14:44 |
| ntpttr_laptop | and then to get details make calls to redfish to make sure the information is as up to date as possible | 14:45 |
| ntpttr_laptop | though I'd be okay with changing that and making our DB larger if that's what we think is best at this stage | 14:45 |
| ramineni_ | but does device detail change over time? except it is still accesible or not? | 14:46 |
| ntpttr_laptop | ramineni_: that's the thing, probably not | 14:46 |
| ntpttr_laptop | so yeah, I'm okay with expanding the DB | 14:47 |
| ntpttr_laptop | I'll rework what I have there and we can come back to this, does that sound good? | 14:48 |
| lin_yang | most likely the details will not change, but we have to double check the device is still accessible or not, right? | 14:48 |
| ntpttr_laptop | lin_yang: yes | 14:48 |
| ntpttr_laptop | that's the thing that we have to be careful of | 14:48 |
| lin_yang | so we can get all detail we needed at that time | 14:48 |
| ramineni_ | ntpttr_laptop: sounds great, thanks | 14:48 |
| ramineni_ | lin_yang: right | 14:48 |
| ntpttr_laptop | making sure the database is in sync with the pods on what's in use and what isn't | 14:48 |
| mkrai | ntpttr_laptop: sounds good | 14:48 |
| ramineni_ | ntpttr_laptop: can you review this spec and functionality , and add any comments https://review.openstack.org/#/c/471322/3/specs/pike/approved/device-management.rst , i will rework on the spec accoringly | 14:49 |
| ntpttr_laptop | sure, I'll open it up in a tab | 14:49 |
| ramineni_ | ill address the comments lin_yang pointed out | 14:50 |
| ramineni_ | ntpttr_laptop: great, thanks | 14:50 |
| ntpttr_laptop | anything else folks would like to discuss while we're here? | 14:51 |
| lin_yang | ramineni_: please make sure correct the db if found any mismatch for device status | 14:51 |
| ramineni_ | lin_yang: right , will add that | 14:52 |
| lin_yang | ramineni_: thanks | 14:52 |
| *** hubian has joined #openstack-valence | 14:52 | |
| Mrittika | We need to review all bps | 14:52 |
| ntpttr_laptop | Mrittika: yep | 14:53 |
| ntpttr_laptop | hi btw, and hi hubian | 14:53 |
| hubian | hello | 14:53 |
| hubian | sorry , i'm late | 14:53 |
| lin_yang | I will rework the task management spec https://review.openstack.org/#/c/474099/ | 14:54 |
| Mrittika | And mark approved or more | 14:54 |
| lin_yang | hubian: Hey | 14:54 |
| ntpttr_laptop | sure thanks lin_yang | 14:54 |
| hubian | hello lin_yang | 14:54 |
| Mrittika | Thanks lin-yang | 14:55 |
| hubian | I'll check the meeting record to see what i miss this meeting | 14:55 |
| ntpttr_laptop | hubian: not a ton - we discussed DB changes | 14:55 |
| hubian | ok | 14:56 |
| ntpttr_laptop | and said thanks to everyone for work in getting our summit submissions in - voting opens I think next week | 14:56 |
| Mrittika | Hubian are you demoing in flash summit? | 14:57 |
| hubian | flash summit ? | 14:57 |
| Mrittika | In august | 14:58 |
| hubian | waht's your mean here the summit of flash ? the flash storage summit ? | 14:58 |
| Mrittika | Yes | 14:58 |
| hubian | oh , maybe i will not | 14:59 |
| hubian | Seems it is my first time hear this ~ sorry ~ | 15:00 |
| Mrittika | Ok I heard there is a pooled nvme demo by Lenovo at the summit | 15:00 |
| Mrittika | So I wanted to know if that has Valence in it | 15:01 |
| hubian | OK , i could connect with our PodManager development team to see if it is theris demo | 15:02 |
| ntpttr_laptop | sounds good | 15:04 |
| ntpttr_laptop | any other topics folks? | 15:04 |
| ntpttr_laptop | next week I'll send out a reminder to fill out the etherpad agenda again so we can remember to use that :) | 15:05 |
| lin_yang | none from me | 15:05 |
| hubian | Thanks ntpptr_laptop for doing this ~ | 15:06 |
| hubian | :) | 15:06 |
| *** Mrittika has quit IRC | 15:06 | |
| ramineni_ | none from me | 15:06 |
| ntpttr_laptop | no problem! and thanks for your work on our summit submission | 15:06 |
| ntpttr_laptop | did you see the changes I ended up making by the way? | 15:06 |
| *** akhil_jain32 has joined #openstack-valence | 15:06 | |
| hubian | yeah ~ i saw it ~ | 15:07 |
| ntpttr_laptop | cool, hopefully you thought it was all right | 15:07 |
| hubian | much better | 15:07 |
| hubian | of course , it is ok ~ | 15:08 |
| ntpttr_laptop | well hopefully one of our talks is accepted! | 15:08 |
| ntpttr_laptop | okay last call for another topic, looks like it might be wrapping up | 15:08 |
| ntpttr_laptop | going once | 15:08 |
| ntpttr_laptop | going twice | 15:08 |
| ntpttr_laptop | looks like that's it for today. I've got tabs open for reviews that I'll make sure to do today, and I'll also take a look at our BPs outstanding | 15:09 |
| ntpttr_laptop | thanks everyone | 15:09 |
| *** Mrittika has joined #openstack-valence | 15:09 | |
| mkrai | Thanks everyone | 15:09 |
| lin_yang | thanks everyone, bye | 15:10 |
| hubian | thanks bye ~ | 15:10 |
| Mrittika | Bye | 15:10 |
| *** hubian has quit IRC | 15:10 | |
| *** ramineni_ has left #openstack-valence | 15:13 | |
| *** Mrittika has quit IRC | 15:14 | |
| *** akhil_jain32 has quit IRC | 15:18 | |
| *** ntpttr_laptop has quit IRC | 15:23 | |
| *** openstackgerrit has joined #openstack-valence | 20:24 | |
| openstackgerrit | Nate Potter proposed openstack/valence master: [WIP] Implement NVMe Device Functions https://review.openstack.org/485347 | 20:24 |
| *** ntpttr_laptop has joined #openstack-valence | 20:50 | |
| *** ntpttr_laptop has quit IRC | 23:30 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!