Wednesday, 2017-07-12

openstackgerritMerged openstack/valence-specs master: Add vendor extensible framework  https://review.openstack.org/46981700:55
*** yufei has joined #openstack-valence01:10
openstackgerrithubian proposed openstack/valence master: Import sushy lib and extend it as well as show its usage for mutli-podm  https://review.openstack.org/47572001:39
*** yufei has quit IRC03:40
*** yufei has joined #openstack-valence05:04
*** spsurya__ has joined #openstack-valence06:27
*** openstackgerrit has quit IRC06:48
-openstackstatus- NOTICE: FYI, ask.openstack.org is down, review.o.o is slow - please have patience until this is fixed06:53
-openstackstatus- NOTICE: Gerrit is going to be restarted, due to low performance07:50
-openstackstatus- NOTICE: Gerrit has been successfully restarted07:58
*** ramineni has left #openstack-valence08:46
*** ramineni has joined #openstack-valence08:47
*** yufei has quit IRC09:58
*** zhenguo_ has joined #openstack-valence12:40
*** zhenguo has quit IRC12:41
*** zhenguo_ is now known as zhenguo12:41
*** mrittika has joined #openstack-valence14:23
mrittikahi14:23
*** ntpttr_laptop has joined #openstack-valence14:23
*** hubian has joined #openstack-valence14:25
*** ramineni_ has joined #openstack-valence14:26
lin_yanghi mrittika14:28
ramineni_Hi All14:29
hubianhello all14:29
*** shuquan_ has joined #openstack-valence14:29
mkraiHi All14:29
shuquan_hi14:29
ntpttr_laptophi o/14:29
lin_yanghi14:29
ntpttr_laptopi'm back from vacation and coming to meetings again14:30
ramineni_ntpttr_laptop: welcome back :)14:30
ntpttr_laptopthanks ramineni_14:30
mkraintpttr_laptop: Welcome back :)14:30
ntpttr_laptopthanks! is everyone here?14:31
lin_yangI think so14:31
ntpttr_laptopcool, let's get started then. Did anyone add any items to the agenda for today?14:32
lin_yangseems no one add the agenda, but four summit topic proposal14:32
ntpttr_laptoplooks like maybe not, I do see the summit proposals though very cool14:33
ntpttr_laptopI 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_yangI added this one, after discussed with shuquan_14:35
hubian+114:35
ntpttr_laptophow do you guys foresee cinder initiating calls to attach the storage to a node?14:35
*** akhil_jain32 has joined #openstack-valence14:35
ntpttr_laptopthrough the volume_attach API?14:36
shuquan_i think so14:36
ntpttr_laptopokay, 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 set14:36
lin_yangintegrate 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 ironic14:36
ntpttr_laptopand I don't think we can meet that feature set with valence and RSD14:37
lin_yangntpttr_laptop: I remember someone proposal to add nvme driver in cinder last year14:37
shuquan_there is feature in cinder to attach disk to baremetal14:37
ntpttr_laptoplin_yang shuquan_: yes, but through redfish? would those features work with RSD already?14:38
shuquan_no, we need to implement it14:38
ntpttr_laptopyeah 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 hardware14:39
mrittikashuquan: you were going to start the email thread on network generic switch14:39
ntpttr_laptopI'm trying to find that list14:40
ntpttr_laptophere's the basic page https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver#How_To_Contribute_a_driver_to_Cinder14:40
ntpttr_laptopanyways, just something to keep in mind14:40
shuquan_maybe it's the scope of os-brick. I'm not sure. need more time to dig in14:40
ntpttr_laptopfair enough14:40
ntpttr_laptopwe can move on to the topic mrittika is bringing up now14:41
shuquan_mrittika: sorry, I did not start since last meeting. :(14:41
mrittikalet's start that.. redfish release of network APIs will happen by end of July14:42
shuquan_sure14:42
ntpttr_laptopsounds good14:43
lin_yangthat's cool, I can start to push those networking API into sushy after that14:43
shuquan_the summit submission will be closed by this friday. anyone submit an abstract?14:43
ntpttr_laptopalright 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: yes14:44
ntpttr_laptopshuquan_: we talked about that yesterday in a meeting, I don't think we have yet but definitely could in the next couple days14:44
ramineni_ntpttr_laptop: so you are proposing having pointers would be more better14:45
lin_yangmrittika: 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 nodes14:46
shuquan_Valence: One Year Later14:46
ntpttr_laptopramineni_: 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 podm14:46
lin_yanglet's finish the DB entry thing at first, then back to summit topic14:46
shuquan_np14:46
ntpttr_laptopramineni_: 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 slow14:47
ntpttr_laptopwhat unique info would we put in there14:47
ntpttr_laptopramineni_: yeah that could work, theres always a chance that they could be out of sync I guess14:47
ramineni_i mean if we seperate nodes DB and devices DB , i can add additional inof of node_id and state to device db14:48
ntpttr_laptopramineni_: 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 entry14:49
lin_yangntpttr_laptop: ramineni_ sorry I didn't get chance to check your comments after last week, because working on the quick poc14:49
ntpttr_laptopnp lin_yang14:49
ramineni_ntpttr_laptop: in extra_info you mean?14:49
ntpttr_laptopramineni_: or just in their own node_uuid entry if we had resources and attachable_resources entries14:50
ntpttr_laptopI'm curious what other folks thoughts on this are14:50
hubianextral_info could be a very uaseful column that take all necessary properties14:51
ntpttr_laptophubian 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 there14:51
hubianthat your both thought could take in14:51
hubiani thought14:51
shuquan_sure.i'll check it later on14:51
ntpttr_laptophubian: 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_yangI will put it into my today todo list :)14:52
mrittikantpttr_laptop: i like the idea of a common db14:52
akhil_jain32ntpttr_laptop: sure I will check it14:52
ntpttr_laptopcool 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
hubianntpttr_laptop :i thought it is ok14:53
mrittikaakhil_jain32: are you working on adding any code?14:53
ntpttr_laptopokay we can continue that on gerrit then, why don't we return to the summit talk14:53
*** ramineni_ has quit IRC14:54
akhil_jain32I am working with ramineni14:54
ntpttr_laptophubian: yeah I think that might be good as well, a pretty clean way of doing it rather than splitting up the entries into two14:54
mrittikantpttr_laptop: what talk would you like to submit14:54
*** ramineni_ has joined #openstack-valence14:54
ramineni_Sorry ..got disconnected14:55
ntpttr_laptopmrittika: 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 anything14:55
lin_yangin boston summit, we demoed the basic node composition and integrate with ironic through redfish driver14:56
lin_yangso I think one possible topic is show these new features of redfish controller14:57
mrittikamkrai and submitted a demo of integrating ironic with valence to manage a swtich hardware14:57
ntpttr_laptoplin_yang: you mean like multipodm and sushy integration?14:57
mrittikalin_yang: good idea14:57
mrittikahubian will have to decide on multi-podm14:57
lin_yangntpttr_laptop: yes, also like the different version of podm on the backend14:58
hubianok14:58
mrittikalin_yang: diff versions will be difficult to address14:58
ntpttr_laptopthat sounds good, I think that's the best new talk we could give now14:58
mrittikawho wrote "managing pooled resources and dynamic workloads with usecase of achieving high performance computing"14:59
ramineni_o/14:59
lin_yangramineni_: I think14:59
ramineni_I thought presenting with usecase would be good14:59
mrittikait is cool!15:00
mrittikado you have any pieces of that?15:00
lin_yangramineni_: +1 It is cool topic, even we are a little bit far to there15:00
ntpttr_laptopyeah it's good to take the long view and talk about what we see as big picture goals15:01
hubianactually 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 sydeny15:01
mrittikaramineni_: if you need any help on that let me know15:01
ntpttr_laptopshould we take what's been put up on the etherpad and get some small groups to draft submissions?15:01
hubiani thought it.could be a user case15:02
lin_yangntpttr_laptop: +115:02
ntpttr_laptophubian: that's awesome, I think that would be a great thing to display15:02
ntpttr_laptopeven if it's not quite finished by then15:02
hubianok , i try to make it15:03
ramineni_mrittika: sure ..sorry getting disconnected frequently , some network issue15:03
mrittikahubian: you have time till october to finish it.. just submit the abstract15:04
hubianyeah i will submit it asap15:05
ntpttr_laptopI'd be happy to help with the abstract and the talk if you like hubian - does it include the multipodm stuff?15:05
hubianit.will15:05
shuquan_do we want to have a panel about talking the current status and typical use case like other project?15:06
hubianbtw, that may take the valence web ui into.consideration15:06
ntpttr_laptopcool, if you like I can help with the abstract15:06
hubianok let us talk more details by emails15:07
ntpttr_laptopsounds good15:07
ntpttr_laptopshuquan_: I think that would be cool to do15:07
ramineni_shuquan_: panel means discussion type15:07
mrittikashuquan_: please explain a little more15:07
hubianntpttr_laptop :thanks15:08
shuquan_there is a track called project update. we can submit a panel for project update.15:08
hubian+115:08
shuquan_have more people know about valence15:09
mrittikaexcellent idea15:09
shuquan_we can refer to other project to promote our project15:09
lin_yangI think panel is designed for specific technical topic15:09
hubianproject uodate seems would have more people like to attend15:09
ramineni_lin_yang: agree ..I think so too15:09
shuquan_because i see a lot of project update is held as panel.15:10
lin_yangdidn't see a panel for project status update15:10
lin_yangshuquan_: okay, so there is track called "status update", right15:10
shuquan_really? :)15:10
shuquan_no. it's project update15:10
ntpttr_laptopso 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_yangI guess the project update might be moved to ptg, but we can submit a general topic about valence and RSd as a panel discussion15:12
lin_yangntpttr_laptop: +115:12
shuquan_we can prepare some hot topics in the panel15:13
ntpttr_laptopthat 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_laptopshuquan_: I'd be happy to15:14
ntpttr_laptopsure15:14
shuquan_panlist :)15:14
mrittikaall of us :) :)15:14
shuquan_i suggest one people from one company in the abstract. :)15:15
lin_yangI suggest also include all partners here15:15
lin_yangshuquan_: +115:15
hubian+115:15
shuquan_because the abstract can only have 4 people, i thinks15:16
ntpttr_laptopokay, 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 max15:17
ramineni_Right?15:17
ntpttr_laptopramineni_: I feel like I've seen panels of 415:17
lin_yangfor panel it could be 4 speakers15:17
shuquan_Panel Max 4 speakers 1 moderator15:17
ramineni_ntpttr_laptop: yes15:17
ramineni_For presentation ,it's 3 topics per person max I suppose right15:18
ntpttr_laptopall that sounds like a good plan15:18
lin_yanganyone is interested in nvme stuff?15:18
mrittikawould brown bags be stiill there?15:18
shuquan_me15:18
ramineni_It's that way last time ..not sure about this time15:18
shuquan_lin_yang: let's do the nvme stuff. we have a demo already. :)15:19
lin_yangshuquan_: cool, sounds good15:19
ntpttr_laptopshuquan_: really, there's a demo? I don't think I've seen15:19
ntpttr_laptopis there any code for that upstreamed?15:19
shuquan_sorry, not yet.15:20
shuquan_we'll contribute it soon15:20
ntpttr_laptopcool15:20
ntpttr_laptopanything else guys or shall we wrap it up?15:20
shuquan_we implemented a demo for our customer. need more refactor15:21
ntpttr_laptopsweet!15:21
ramineni_shuquan_: I would like to join on that topic ..if max limit not exceed ed for speakers15:21
shuquan_sure. I'll add you15:22
ramineni_otherwise feel free to drop me out :)15:22
ramineni_Ok, great15:22
lin_yangcool, let's prepare this topic15:23
mrittikai would say 1 from each company15:23
shuquan_yes15:23
lin_yangmrittika: make sense15:23
ramineni_ntpttr_laptop: can I add your name for high performance computing one15:24
ramineni_Or anyone else welcome to join if interested15:24
ramineni_:)15:25
ntpttr_laptopramineni_: sure, but I'm already doing the one with hubian so maybe someone else would be better for this15:25
ramineni_Sure15:25
lin_yangramineni_: I would like to help on this topic15:26
ramineni_lin_yang: great15:26
ntpttr_laptopokay it looks like we have a good plan here15:27
hubian:)15:28
shuquan_effective meeting :)15:28
mrittikabye everyone!15:28
hubian+115:28
ramineni_Bye15:28
shuquan_see you next week15:28
ntpttr_laptopbye all!15:28
ntpttr_laptopthanks15:28
*** shuquan_ has quit IRC15:28
*** mrittika has quit IRC15:28
hubianbye15:28
lin_yangthanks everyone, bye15:28
*** ntpttr_laptop has quit IRC15:28
*** hubian has quit IRC15:28
akhil_jain32Bye15:29
*** akhil_jain32 has quit IRC15:46
*** akhil_jain32 has joined #openstack-valence16:00
*** akhil_jain32 has quit IRC16:01
*** ramineni_ has quit IRC18:14
*** spsurya__ has quit IRC19:20
*** openstackgerrit has joined #openstack-valence20:07
openstackgerritLin Yang proposed openstack/valence master: Allow compose node without properties  https://review.openstack.org/47867420:07

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!