openstackgerrit | Merged openstack/valence-specs master: Add vendor extensible framework https://review.openstack.org/469817 | 00:55 |
---|---|---|
*** yufei has joined #openstack-valence | 01:10 | |
openstackgerrit | hubian proposed openstack/valence master: Import sushy lib and extend it as well as show its usage for mutli-podm https://review.openstack.org/475720 | 01:39 |
*** yufei has quit IRC | 03:40 | |
*** yufei has joined #openstack-valence | 05:04 | |
*** spsurya__ has joined #openstack-valence | 06:27 | |
*** openstackgerrit has quit IRC | 06:48 | |
-openstackstatus- NOTICE: FYI, ask.openstack.org is down, review.o.o is slow - please have patience until this is fixed | 06:53 | |
-openstackstatus- NOTICE: Gerrit is going to be restarted, due to low performance | 07:50 | |
-openstackstatus- NOTICE: Gerrit has been successfully restarted | 07:58 | |
*** ramineni has left #openstack-valence | 08:46 | |
*** ramineni has joined #openstack-valence | 08:47 | |
*** yufei has quit IRC | 09:58 | |
*** zhenguo_ has joined #openstack-valence | 12:40 | |
*** zhenguo has quit IRC | 12:41 | |
*** zhenguo_ is now known as zhenguo | 12:41 | |
*** mrittika has joined #openstack-valence | 14:23 | |
mrittika | hi | 14:23 |
*** ntpttr_laptop has joined #openstack-valence | 14:23 | |
*** hubian has joined #openstack-valence | 14:25 | |
*** ramineni_ has joined #openstack-valence | 14:26 | |
lin_yang | hi mrittika | 14:28 |
ramineni_ | Hi All | 14:29 |
hubian | hello all | 14:29 |
*** shuquan_ has joined #openstack-valence | 14:29 | |
mkrai | Hi All | 14:29 |
shuquan_ | hi | 14:29 |
ntpttr_laptop | hi o/ | 14:29 |
lin_yang | hi | 14:29 |
ntpttr_laptop | i'm back from vacation and coming to meetings again | 14:30 |
ramineni_ | ntpttr_laptop: welcome back :) | 14:30 |
ntpttr_laptop | thanks ramineni_ | 14:30 |
mkrai | ntpttr_laptop: Welcome back :) | 14:30 |
ntpttr_laptop | thanks! is everyone here? | 14:31 |
lin_yang | I think so | 14:31 |
ntpttr_laptop | cool, let's get started then. Did anyone add any items to the agenda for today? | 14:32 |
lin_yang | seems no one add the agenda, but four summit topic proposal | 14:32 |
ntpttr_laptop | looks like maybe not, I do see the summit proposals though very cool | 14:33 |
ntpttr_laptop | I would be interested sometime in talking about the second proposal talk there, "dynamic attach of nvme drive to a node using cinder or ironic" | 14:34 |
shuquan_ | it's a cool feature! | 14:35 |
lin_yang | I added this one, after discussed with shuquan_ | 14:35 |
hubian | +1 | 14:35 |
ntpttr_laptop | how do you guys foresee cinder initiating calls to attach the storage to a node? | 14:35 |
*** akhil_jain32 has joined #openstack-valence | 14:35 | |
ntpttr_laptop | through the volume_attach API? | 14:36 |
shuquan_ | i think so | 14:36 |
ntpttr_laptop | okay, so we'll need to propose a new driver for cinder in that case, but I see a bit of a roadblock there, because any cinder driver needs to meet a minimum feature set | 14:36 |
lin_yang | integrate nvme with cinder is straight thought, and I think it would be better that we find a way to integrate with ironic, because current we already have redfish driver in ironic | 14:36 |
ntpttr_laptop | and I don't think we can meet that feature set with valence and RSD | 14:37 |
lin_yang | ntpttr_laptop: I remember someone proposal to add nvme driver in cinder last year | 14:37 |
shuquan_ | there is feature in cinder to attach disk to baremetal | 14:37 |
ntpttr_laptop | lin_yang shuquan_: yes, but through redfish? would those features work with RSD already? | 14:38 |
shuquan_ | no, we need to implement it | 14:38 |
ntpttr_laptop | yeah I think that might be a new driver then, meaning in order to be accepted by Cinder it will need to implement the entire core feature set and have a working CI on real RSD hardware | 14:39 |
mrittika | shuquan: you were going to start the email thread on network generic switch | 14:39 |
ntpttr_laptop | I'm trying to find that list | 14:40 |
ntpttr_laptop | here's the basic page https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver#How_To_Contribute_a_driver_to_Cinder | 14:40 |
ntpttr_laptop | anyways, just something to keep in mind | 14:40 |
shuquan_ | maybe it's the scope of os-brick. I'm not sure. need more time to dig in | 14:40 |
ntpttr_laptop | fair enough | 14:40 |
ntpttr_laptop | we can move on to the topic mrittika is bringing up now | 14:41 |
shuquan_ | mrittika: sorry, I did not start since last meeting. :( | 14:41 |
mrittika | let's start that.. redfish release of network APIs will happen by end of July | 14:42 |
shuquan_ | sure | 14:42 |
ntpttr_laptop | sounds good | 14:43 |
lin_yang | that's cool, I can start to push those networking API into sushy after that | 14:43 |
shuquan_ | the summit submission will be closed by this friday. anyone submit an abstract? | 14:43 |
ntpttr_laptop | alright I had one more topic having to do with a spec I've got up - ramineni_ did you get a chance to see my latest comments on https://review.openstack.org/#/c/476272/? | 14:43 |
ramineni_ | ntpttr_laptop: yes | 14:44 |
ntpttr_laptop | shuquan_: we talked about that yesterday in a meeting, I don't think we have yet but definitely could in the next couple days | 14:44 |
ramineni_ | ntpttr_laptop: so you are proposing having pointers would be more better | 14:45 |
lin_yang | mrittika: mkrai have submitted one topic “Let Ironic Manage Your Network Device” | 14:45 |
ramineni_ | ntpttr_laptop: but i didnt get for this part .. do you think two DB entries, one for composable resources and another for attachable makes sense? | 14:45 |
shuquan_ | I suggest we submit a panel about valence project update together. :) | 14:46 |
ramineni_ | ntpttr_laptop: my idea is to keep seperate DB entry for compose nodes | 14:46 |
shuquan_ | Valence: One Year Later | 14:46 |
ntpttr_laptop | ramineni_: I'm not totally sure yet, I'd like to talk about it I guess. If we start keeping track of if devices are attached in the valence DB we have the possibility of getting out of sync with the podm | 14:46 |
lin_yang | let's finish the DB entry thing at first, then back to summit topic | 14:46 |
shuquan_ | np | 14:46 |
ntpttr_laptop | ramineni_: why do you think we need a separate entry for composed nodes? | 14:46 |
ramineni_ | ntpttr_laptop: how about periodic task, fetching everytime from redfsih would be slow | 14:47 |
ntpttr_laptop | what unique info would we put in there | 14:47 |
ntpttr_laptop | ramineni_: yeah that could work, theres always a chance that they could be out of sync I guess | 14:47 |
ramineni_ | i mean if we seperate nodes DB and devices DB , i can add additional inof of node_id and state to device db | 14:48 |
ntpttr_laptop | ramineni_: I think we can do that anyways - since nodes are resources they've got their own UUIDs anyways and that UUID can be saved as the node_id in the attachable device entry | 14:49 |
lin_yang | ntpttr_laptop: ramineni_ sorry I didn't get chance to check your comments after last week, because working on the quick poc | 14:49 |
ntpttr_laptop | np lin_yang | 14:49 |
ramineni_ | ntpttr_laptop: in extra_info you mean? | 14:49 |
ntpttr_laptop | ramineni_: or just in their own node_uuid entry if we had resources and attachable_resources entries | 14:50 |
ntpttr_laptop | I'm curious what other folks thoughts on this are | 14:50 |
hubian | extral_info could be a very uaseful column that take all necessary properties | 14:51 |
ntpttr_laptop | hubian shuquan_ mkrai akhil_jain32: if you guys get a chance to check out the spec https://review.openstack.org/#/c/476272/ I'd value any thoughts you've got on the discussion going on in there | 14:51 |
hubian | that your both thought could take in | 14:51 |
hubian | i thought | 14:51 |
shuquan_ | sure.i'll check it later on | 14:51 |
ntpttr_laptop | hubian: do you think that would be a good place to have attachment info? like {'extra_info': 'attachments': {'state': attached, 'node_uuid': ,uUID>}} | 14:52 |
lin_yang | I will put it into my today todo list :) | 14:52 |
mrittika | ntpttr_laptop: i like the idea of a common db | 14:52 |
akhil_jain32 | ntpttr_laptop: sure I will check it | 14:52 |
ntpttr_laptop | cool thanks guys - I've also got the implementation patch up but want ot make sure we align on the spec https://review.openstack.org/#/c/475595/ | 14:53 |
hubian | ntpttr_laptop :i thought it is ok | 14:53 |
mrittika | akhil_jain32: are you working on adding any code? | 14:53 |
ntpttr_laptop | okay we can continue that on gerrit then, why don't we return to the summit talk | 14:53 |
*** ramineni_ has quit IRC | 14:54 | |
akhil_jain32 | I am working with ramineni | 14:54 |
ntpttr_laptop | hubian: yeah I think that might be good as well, a pretty clean way of doing it rather than splitting up the entries into two | 14:54 |
mrittika | ntpttr_laptop: what talk would you like to submit | 14:54 |
*** ramineni_ has joined #openstack-valence | 14:54 | |
ramineni_ | Sorry ..got disconnected | 14:55 |
ntpttr_laptop | mrittika: let me think for a second - I like some that are on the etherpad. What did the talks at the last summit cover? We want to make sure we aren't just repeating them or anything | 14:55 |
lin_yang | in boston summit, we demoed the basic node composition and integrate with ironic through redfish driver | 14:56 |
lin_yang | so I think one possible topic is show these new features of redfish controller | 14:57 |
mrittika | mkrai and submitted a demo of integrating ironic with valence to manage a swtich hardware | 14:57 |
ntpttr_laptop | lin_yang: you mean like multipodm and sushy integration? | 14:57 |
mrittika | lin_yang: good idea | 14:57 |
mrittika | hubian will have to decide on multi-podm | 14:57 |
lin_yang | ntpttr_laptop: yes, also like the different version of podm on the backend | 14:58 |
hubian | ok | 14:58 |
mrittika | lin_yang: diff versions will be difficult to address | 14:58 |
ntpttr_laptop | that sounds good, I think that's the best new talk we could give now | 14:58 |
mrittika | who wrote "managing pooled resources and dynamic workloads with usecase of achieving high performance computing" | 14:59 |
ramineni_ | o/ | 14:59 |
lin_yang | ramineni_: I think | 14:59 |
ramineni_ | I thought presenting with usecase would be good | 14:59 |
mrittika | it is cool! | 15:00 |
mrittika | do you have any pieces of that? | 15:00 |
lin_yang | ramineni_: +1 It is cool topic, even we are a little bit far to there | 15:00 |
ntpttr_laptop | yeah it's good to take the long view and talk about what we see as big picture goals | 15:01 |
hubian | actually i would have a commitment to finish that setup and run valence on lenovo pod manager hardware . but i.dont know could.finished before summit sydeny | 15:01 |
mrittika | ramineni_: if you need any help on that let me know | 15:01 |
ntpttr_laptop | should we take what's been put up on the etherpad and get some small groups to draft submissions? | 15:01 |
hubian | i thought it.could be a user case | 15:02 |
lin_yang | ntpttr_laptop: +1 | 15:02 |
ntpttr_laptop | hubian: that's awesome, I think that would be a great thing to display | 15:02 |
ntpttr_laptop | even if it's not quite finished by then | 15:02 |
hubian | ok , i try to make it | 15:03 |
ramineni_ | mrittika: sure ..sorry getting disconnected frequently , some network issue | 15:03 |
mrittika | hubian: you have time till october to finish it.. just submit the abstract | 15:04 |
hubian | yeah i will submit it asap | 15:05 |
ntpttr_laptop | I'd be happy to help with the abstract and the talk if you like hubian - does it include the multipodm stuff? | 15:05 |
hubian | it.will | 15:05 |
shuquan_ | do we want to have a panel about talking the current status and typical use case like other project? | 15:06 |
hubian | btw, that may take the valence web ui into.consideration | 15:06 |
ntpttr_laptop | cool, if you like I can help with the abstract | 15:06 |
hubian | ok let us talk more details by emails | 15:07 |
ntpttr_laptop | sounds good | 15:07 |
ntpttr_laptop | shuquan_: I think that would be cool to do | 15:07 |
ramineni_ | shuquan_: panel means discussion type | 15:07 |
mrittika | shuquan_: please explain a little more | 15:07 |
hubian | ntpttr_laptop :thanks | 15:08 |
shuquan_ | there is a track called project update. we can submit a panel for project update. | 15:08 |
hubian | +1 | 15:08 |
shuquan_ | have more people know about valence | 15:09 |
mrittika | excellent idea | 15:09 |
shuquan_ | we can refer to other project to promote our project | 15:09 |
lin_yang | I think panel is designed for specific technical topic | 15:09 |
hubian | project uodate seems would have more people like to attend | 15:09 |
ramineni_ | lin_yang: agree ..I think so too | 15:09 |
shuquan_ | because i see a lot of project update is held as panel. | 15:10 |
lin_yang | didn't see a panel for project status update | 15:10 |
lin_yang | shuquan_: okay, so there is track called "status update", right | 15:10 |
shuquan_ | really? :) | 15:10 |
shuquan_ | no. it's project update | 15:10 |
ntpttr_laptop | so the panel would have to be about valence and RSD as a technology, and we could talk about what's happening in the project? | 15:11 |
shuquan_ | it's open this summit. | 15:11 |
lin_yang | I guess the project update might be moved to ptg, but we can submit a general topic about valence and RSd as a panel discussion | 15:12 |
lin_yang | ntpttr_laptop: +1 | 15:12 |
shuquan_ | we can prepare some hot topics in the panel | 15:13 |
ntpttr_laptop | that sounds good to me - shuquan_ could you handle putting up the abstract for the panel? | 15:13 |
shuquan_ | sure. do you mind i add you as a speaker? | 15:14 |
ntpttr_laptop | shuquan_: I'd be happy to | 15:14 |
ntpttr_laptop | sure | 15:14 |
shuquan_ | panlist :) | 15:14 |
mrittika | all of us :) :) | 15:14 |
shuquan_ | i suggest one people from one company in the abstract. :) | 15:15 |
lin_yang | I suggest also include all partners here | 15:15 |
lin_yang | shuquan_: +1 | 15:15 |
hubian | +1 | 15:15 |
shuquan_ | because the abstract can only have 4 people, i thinks | 15:16 |
ntpttr_laptop | okay, so hubian and I will touch base via email on one talk, shuquan_ will help with the panel submission, ramineni_ are you submitting the high performance use case talk? | 15:17 |
ramineni_ | shuquan_: I think only 3 max | 15:17 |
ramineni_ | Right? | 15:17 |
ntpttr_laptop | ramineni_: I feel like I've seen panels of 4 | 15:17 |
lin_yang | for panel it could be 4 speakers | 15:17 |
shuquan_ | Panel Max 4 speakers 1 moderator | 15:17 |
ramineni_ | ntpttr_laptop: yes | 15:17 |
ramineni_ | For presentation ,it's 3 topics per person max I suppose right | 15:18 |
ntpttr_laptop | all that sounds like a good plan | 15:18 |
lin_yang | anyone is interested in nvme stuff? | 15:18 |
mrittika | would brown bags be stiill there? | 15:18 |
shuquan_ | me | 15:18 |
ramineni_ | It's that way last time ..not sure about this time | 15:18 |
shuquan_ | lin_yang: let's do the nvme stuff. we have a demo already. :) | 15:19 |
lin_yang | shuquan_: cool, sounds good | 15:19 |
ntpttr_laptop | shuquan_: really, there's a demo? I don't think I've seen | 15:19 |
ntpttr_laptop | is there any code for that upstreamed? | 15:19 |
shuquan_ | sorry, not yet. | 15:20 |
shuquan_ | we'll contribute it soon | 15:20 |
ntpttr_laptop | cool | 15:20 |
ntpttr_laptop | anything else guys or shall we wrap it up? | 15:20 |
shuquan_ | we implemented a demo for our customer. need more refactor | 15:21 |
ntpttr_laptop | sweet! | 15:21 |
ramineni_ | shuquan_: I would like to join on that topic ..if max limit not exceed ed for speakers | 15:21 |
shuquan_ | sure. I'll add you | 15:22 |
ramineni_ | otherwise feel free to drop me out :) | 15:22 |
ramineni_ | Ok, great | 15:22 |
lin_yang | cool, let's prepare this topic | 15:23 |
mrittika | i would say 1 from each company | 15:23 |
shuquan_ | yes | 15:23 |
lin_yang | mrittika: make sense | 15:23 |
ramineni_ | ntpttr_laptop: can I add your name for high performance computing one | 15:24 |
ramineni_ | Or anyone else welcome to join if interested | 15:24 |
ramineni_ | :) | 15:25 |
ntpttr_laptop | ramineni_: sure, but I'm already doing the one with hubian so maybe someone else would be better for this | 15:25 |
ramineni_ | Sure | 15:25 |
lin_yang | ramineni_: I would like to help on this topic | 15:26 |
ramineni_ | lin_yang: great | 15:26 |
ntpttr_laptop | okay it looks like we have a good plan here | 15:27 |
hubian | :) | 15:28 |
shuquan_ | effective meeting :) | 15:28 |
mrittika | bye everyone! | 15:28 |
hubian | +1 | 15:28 |
ramineni_ | Bye | 15:28 |
shuquan_ | see you next week | 15:28 |
ntpttr_laptop | bye all! | 15:28 |
ntpttr_laptop | thanks | 15:28 |
*** shuquan_ has quit IRC | 15:28 | |
*** mrittika has quit IRC | 15:28 | |
hubian | bye | 15:28 |
lin_yang | thanks everyone, bye | 15:28 |
*** ntpttr_laptop has quit IRC | 15:28 | |
*** hubian has quit IRC | 15:28 | |
akhil_jain32 | Bye | 15:29 |
*** akhil_jain32 has quit IRC | 15:46 | |
*** akhil_jain32 has joined #openstack-valence | 16:00 | |
*** akhil_jain32 has quit IRC | 16:01 | |
*** ramineni_ has quit IRC | 18:14 | |
*** spsurya__ has quit IRC | 19:20 | |
*** openstackgerrit has joined #openstack-valence | 20:07 | |
openstackgerrit | Lin Yang proposed openstack/valence master: Allow compose node without properties https://review.openstack.org/478674 | 20:07 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!