Wednesday, 2017-06-28

*** shubhendu has quit IRC05:22
*** shubhendu has joined #openstack-valence05:35
*** shubhendu has quit IRC06:53
*** shubhendu has joined #openstack-valence07:05
openstackgerritAnanth Narayan S proposed openstack/valence-specs master: Add task queueing to address scalability  https://review.openstack.org/47409907:11
openstackgerritAnanth Narayan S proposed openstack/valence-specs master: Add task queueing to address scalability  https://review.openstack.org/47409907:54
*** shubhendu has quit IRC10:02
*** shubhendu has joined #openstack-valence10:14
*** mrittika has joined #openstack-valence14:16
*** mrittika has quit IRC14:25
*** hubian has joined #openstack-valence14:26
*** ramineni_ has joined #openstack-valence14:26
ramineni_Hi All14:29
mkraiHi14:30
hubianhello all14:30
lin_yanghello everyone14:31
ramineni_I don´t see any agenda items , anyone have any topics to discuss today14:32
hubianThere is a topic I want to talk14:33
lin_yangI just added one14:33
hubianAbout  how to use the sushy lib ~14:33
*** mrittika has joined #openstack-valence14:33
lin_yangokay, almost the same one14:33
ramineni_hubian: lin_yang: ok14:34
mrittikaHi. Who is chairing today?14:34
lin_yangI discussed with sushy maintainer about create new branch for valence, to include those non-published redfish resource14:34
lin_yangramineni_: is chairing14:35
lin_yangthe problem is only master branch in sushy will be released14:35
mkrailin_yang: They will not accept the changes on master?14:36
*** shuquan has joined #openstack-valence14:36
lin_yangwill only accept those published redfish standard14:36
shuquanhi guys14:36
lin_yanginto master14:36
ramineni_lin_yang: ok, the only option is for us to maintain our own lib?14:37
ramineni_in valence repo I meant14:37
lin_yangso they suggest we submit those published standard to sushy master, and create new repo and extend sushy if we want to release it14:38
shuquansorry for the late due to some network issue14:39
mkraiI think its better to extend sushy and have our own repo inside/outside valence14:39
ramineni_shuquan: hi , no problem , we are discussing regarding usage of sushy lib14:39
lin_yang+1 for inside valence14:39
lin_yanghi shuquan14:39
lin_yangI think there is only valence will use this lib14:40
lin_yangothers, like valence-client will call valence api14:40
hubianok , that's the original thoutht that extend sushy ~14:40
ramineni_yes, we can use existing functionalities from the lib and extend additional functionalities inside valence repo14:40
lin_yanghubian: true, but push standard redfish to sushy, I can help with that part if you want14:41
ramineni_lin_yang: one question, once the standard is published, do you think we should pursue merging into master?14:41
lin_yangI think so14:42
ramineni_lin_yang: ok14:42
lin_yangif something is accept by DMTF, we should push to sushy master14:42
lin_yangAny other comments for this part?14:43
ramineni_So our final conclusion is use sushy lib for redfish standard functionalities, implement the others inside valence repo14:43
shuquananything new of RSD extend is accepted by DMTF recently?14:44
lin_yangshuquan: I am not clear about this part, but I heard other folks were trying to push something into DMTF14:45
lin_yangmay be the node composition14:45
lin_yangmrittika: do you know anything about this?14:45
mrittikaNetwork proposal14:46
shuquanin progress or get accepted?14:47
mrittikaThat was made to dmtf. Has been proposed to ietf14:47
mrittikaIt is not published as accepted.14:47
ramineni_hubian: do you have any other comments on using sushy lib?14:48
mrittikaWhat about storage -14:48
mrittikaIt is published in swordfish14:48
hubianramineni : it's ok ·14:49
lin_yangmrittika: good point, I guess we cannot mix the swordfish with sushy14:49
hubianExtended sushy , and implement our own requirement14:50
lin_yangany lib available for swordfish?14:50
ramineni_hubian: right14:51
lin_yangmrittika: I can dig it more for swordfish14:51
lin_yangmrittika: so it's impossible to push node composition to dmtf, right?14:52
mrittikaOk14:52
mrittikaNode composition is already proposed to dmtf14:52
mrittikaBoth composition and network will get released in dmtf soon14:53
shuquangood to hear that!14:53
lin_yangmrittika: cool.14:53
*** ramineni__ has joined #openstack-valence14:54
mrittikaI'll find out the approx timelines14:54
lin_yangjust wondering whether others need to use this extended redfish lib.14:54
lin_yanganyway, if need, we can split it from valence to seperate repo later14:55
hubianYeah , we could cat the timelines to see when we deal with our componsion requirement on the redfish part ~14:55
ramineni__lin_yang: +114:56
*** ramineni_1 has joined #openstack-valence14:57
ramineni__I have one topic on pooled resources API14:57
*** ramineni_ has quit IRC14:58
*** ramineni__ is now known as ramineni_14:58
ramineni_1can you guys review the same and post your comments on the spec https://review.openstack.org/#/c/471322/14:58
lin_yangsure, will do it today, sorry for the delay, was struggling with something before14:59
ramineni_1lin_yang: Thanks14:59
ramineni_1anyone have any other topics we have to discuss today?15:00
lin_yangI has some questions about storage spec, but Nate is on vacation this week, let's discuss it next week15:01
lin_yangno more topic from me15:01
ramineni_1lin_yang: right, me too :)15:01
lin_yangmrittika: do you have any other topics?15:02
*** mrittika has quit IRC15:03
shuquanno from me either15:03
hubianno from me ~15:03
ramineni_Ok then let's end early today :)15:04
lin_yangshuquan: one thing, could you please check the valence client15:04
shuquansure. i'm following that. these days we're busy with nvme pool storage integration15:05
*** ramineni_2 has joined #openstack-valence15:05
lin_yangshuquan: okay, thanks appreciated15:05
shuquanafter finish it, we will submit the patches15:05
lin_yangsure15:05
hubian+115:05
shuquanbtw, openstack summit is coming. are you guys still intesested at joint topics?15:06
ramineni_2shuquan: right, thanks for reminding , anyone joining for PTG ?15:06
lin_yangabsolutely yes for joint topics15:06
*** ramineni_1 has quit IRC15:06
lin_yangramineni_1: I cannot make it this time15:06
ramineni_2shuquan: +1 for joint topics15:07
shuquancool15:07
ramineni_2lin_yang: oh15:07
shuquanlet's figure it out. :)15:07
ramineni_2lin_yang: ok then mostly no PTG for valence right15:07
lin_yangGuess Nate also will not attend PTG15:07
lin_yangI guess so15:08
ramineni_2shuquan: last day is July 14 right, for submission15:08
shuquanwe can discuss the openstack topics next week15:08
shuquanone agenda15:08
ramineni_2+115:08
shuquanvalence have 2 topics get accepted last summit15:09
shuquanhope we can get more this summit15:09
lin_yang+1 please add this item into agenda15:09
shuquansorry guys, i gotta to go15:10
shuquansee you next week and have a good day15:10
*** shuquan has quit IRC15:10
lin_yangramineni_2: we are done here today, right?15:10
*** mrittika has joined #openstack-valence15:10
ramineni_2lin_yang: yes,15:11
ramineni_2mrittika: do you have any topics? we are about to end today15:11
mrittikaNone15:11
ramineni_2ok,15:12
ramineni_2Thanks All, see you next week :)15:12
lin_yangthanks everyone, bye15:12
mkraiThank you all15:12
hubianbye ~15:12
mrittikaBye15:12
*** hubian has quit IRC15:15
*** mrittika has quit IRC15:17
*** ramineni_2 has quit IRC15:29
*** ramineni_ has quit IRC17:23
*** shubhendu has quit IRC18:38
*** shubhendu has joined #openstack-valence18:51
openstackgerritLin Yang proposed openstack/valence master: Allow compose node with properties  https://review.openstack.org/47867423:08
openstackgerritLin Yang proposed openstack/valence master: Add missing header of Apache License 2.0  https://review.openstack.org/47867823:35
openstackgerritLin Yang proposed openstack/valence master: Clean valence.conf.sample generated by install_valence.sh  https://review.openstack.org/47868023:47
*** ramineni_ has joined #openstack-valence23:56

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