Wednesday, 2017-09-20

*** openstackgerrit has joined #openstack-valence01:18
openstackgerritAnusha Ramineni proposed openstack/valence master: Update podmanager controller to use generic interface  https://review.openstack.org/49946803:56
openstackgerritAnusha Ramineni proposed openstack/valence master: WIP: Ironic generic  https://review.openstack.org/50548804:06
openstackgerritAkhil jain proposed openstack/valence master: Add new 'device' DB table to valence  https://review.openstack.org/49839504:47
*** openstackgerrit has quit IRC07:02
*** openstackgerrit has joined #openstack-valence14:00
*** ntpttr_mobile has joined #openstack-valence14:24
*** ramineni_ has joined #openstack-valence14:26
*** shuquan has joined #openstack-valence14:29
*** akhill_jain has joined #openstack-valence14:30
lin_yanghello everyone14:31
ntpttr_mobileHi Lin14:31
akhill_jainHello14:31
ramineni_lin_yang: ntpttr_mobile: hi14:31
shuquanhi14:32
ntpttr_mobileSo, I saw that Lin had a first email for something he'd like to discuss, Lin would you like to start?14:33
*** ntpttr_laptop has joined #openstack-valence14:34
ramineni_lin_yang: will you be able to make it to sydney for presentation?14:34
lin_yangsure, ramineni_ is here, so we can discuss more details about our session in summit14:34
lin_yangramineni_: sorry i will not be there, you know, the budget reason14:34
ntpttr_laptopah yeah that reminds me, I got word last week that I won't be going to Sydney14:35
ramineni_lin_yang: oh ok :(14:35
ntpttr_laptopbut mkrai I believe will be there14:35
shuquanlin_yang: you will be there, right?14:35
lin_yangramineni_: Madhuri will be there, so if you need any help we can discuss with her14:36
ramineni_hopefully myself or akhil  would be able to make it, if budget permits14:36
lin_yangshuquan: Bad news, I will not be there. How about you?14:36
ramineni_lin_yang: ok, sure14:36
shuquani think i should be there.14:37
ntpttr_laptopglad to hear it shuquan14:37
ntpttr_laptopI guess Sydney is too far/expensive for us this time14:38
shuquanagree14:38
lin_yangthat's true14:38
*** Mrittika has joined #openstack-valence14:38
ntpttr_laptophi Mrittika14:38
lin_yangshuquan: My manager JF will be there, so if you have any topic, you can discuss with him14:38
lin_yanghi Mrittika14:39
MrittikaHi14:39
ramineni_Mrittika: Hi14:39
lin_yangramineni_: for the presentation, do you start to prepare the slides? I am happy to help it14:39
MrittikaIs anyone doing a demo as part of the talks?14:39
ntpttr_laptopso shuquan, I also noticed that since our talk is a lightning talk, we'll only have 10 minutes. I doubt that will really leave time for a demo, unless you want to do the demo while discussing instead of slides?14:39
ntpttr_laptopmight make for a more interesting talk I guess if there's something going on like that for a quick lightning talk rather than 4 or 5 slides14:40
MrittikaDemos are generally not visible in the 10 min talks14:40
shuquanyou're right.14:40
ntpttr_laptopah okay, didn't know that Mrittika14:40
ramineni_lin_yang: sure, thanks.. havent started yet.. planning to start next week, ill send out the initial slides.. we can discuss more and take it from there?14:40
MrittikaThey cannot show your screen14:40
shuquanmaybe only some slides and a quick demo video14:41
lin_yangramineni_: sounds great! Thanks.14:41
ramineni_lin_yang: Mrittika:  I think we can plan for demo for our talk, as its 40 mins.. we will have enough time i suppose14:41
ntpttr_laptopMrittika: if they can't show screen, can we not even have slides for the 10 minute one?14:42
MrittikaCool! ramineni_ if you prepare and send we can review14:42
ramineni_hopefully, i would like .. the device orchestration part also to be ready by that time..14:42
Mrittikantpttr_laptop: you can have slides14:43
ramineni_Mrittika: great, thanks14:43
MrittikaYou have to send slides to them14:43
ntpttr_laptopgotcha14:43
MrittikaIf you embed a video in the slide which auto runs then that will work14:43
shuquanramineni_: I can aslo help to review it14:43
ramineni_shuquan: great , thanks .. will send out email once done14:44
ramineni_ntpttr_laptop: i have 2 more small topics to discuss, if we have time14:45
*** Mrittika_ has joined #openstack-valence14:45
ntpttr_laptopramineni_: yes, please14:45
lin_yangramineni_: one concern from our side is the abstract mentioned attach GPGPU and FPGA to composed node14:45
ramineni_lin_yang: yes14:46
Mrittika_What is the concern14:46
lin_yangramineni_: but Intel don't decide when podm will support it14:46
*** ntpttr_mobile has quit IRC14:46
shuquanramineni_: lin_yang: I only tried nvme before14:46
ramineni_lin_yang: they can be attached as PCI devices right14:47
ramineni_if PCI device support is there, it should be possible?14:47
lin_yangramineni_: So NEC already support it?14:47
shuquani saw some hardware vendor implement GPGPU14:47
ramineni_yes, i think so, it can support all kind of PCI devices, thats the reason added it14:48
*** Mrittika has quit IRC14:48
ramineni_heard they can be dynamically attached after node is composed..according to requirements14:48
ramineni_workload14:49
lin_yangramineni_: yeah, it should be possible, but Intel podm don't offically support it, so marketing folks don't want us to deliver wrong message for it14:49
lin_yangbut it's fine if OEC support it14:49
ntpttr_laptopI've seen it with NVMe, haven't tried it with others but for device endpoints I've seen entity_type field, for ours is only NVMe drive possible there lin_yang?14:49
ramineni_lin_yang: oohok14:49
Mrittika_But it believe ramineni_can present if you can show it working14:49
lin_yangntpttr_laptop: I think so14:50
Mrittika_You can specifically talk about ur use case ramineni_14:50
lin_yangMrittika_: totally agree14:50
ntpttr_laptopyeah, agree with Mrittika_. Sounds good14:50
ramineni_Mrittika_: sure , will note that point while preparing slides, and also will double check it, thanks for bringing that up14:51
Mrittika_Mention that it is possible with the controller and here is the benefit14:51
ramineni_Mrittika_: ok14:52
ntpttr_laptopramineni_: what were the other topics you wanted to discuss?14:53
ramineni_as we are now removing the CONF options for podm credentials, im updating ironic driver to take from podm DB, i found i think we might need to accept some additional parameters while creating podmanager, just need opinion on it14:53
ramineni_https://github.com/openstack/valence/blob/master/valence/provision/ironic/driver.py#L5514:53
ramineni_like in ironic driver info, i see some additional parameters are taken from CONF, CONF.podm.verify_ca14:54
ntpttr_laptopah yeah that makes sense, is verify_ca not currently accepted?14:54
ramineni_no14:54
ntpttr_laptopalso just so you know, we're looking into submitting an ironic driver for RSD-Lib14:54
ntpttr_laptopso that /Nodes can be manipulated by ironic14:55
ramineni_ok, nice.. so how the call will be then14:55
ramineni_directly calls rsd_lib for creating ironic node14:55
ramineni_?14:55
ramineni_from controller?14:56
ntpttr_laptopon the ironic plugin side in valence it'll be almost hte same, only instead of driver='redfish' it'll say driver='rsd' or something similar14:56
ntpttr_laptopthe difference will be what ironic itself sees when communicating with RSD hardware14:56
ramineni_im thinking something like this .. to make it used by multi-podm https://review.openstack.org/#/c/505488/1/valence/provision/ironic/driver.py14:57
ramineni_does that look ok?14:57
ntpttr_laptopI'll have to take a more detailed look but at first glance it does look ok14:57
ramineni_ntpttr_laptop: ok, sure,14:58
lin_yangokay this is the driver in valence to register node to ironic, right? It make sense to me14:58
ntpttr_laptopthe idea is definitely good14:58
ramineni_lin_yang: yes14:58
ramineni_does it makes sense for podm to accept additional parameters while creation like verify_ca etc?14:59
ntpttr_laptopyes, but they should have defaults14:59
ramineni_or do we need to pass while we run command registering node with ironic14:59
ntpttr_laptopveryfy_ca can default to True maybe15:00
ntpttr_laptopor wait15:00
ntpttr_laptopI'm going off of what Sushy was doing15:00
ntpttr_laptophttps://github.com/openstack/sushy/blob/master/sushy/main.py#L5115:01
ramineni_ntpttr_laptop: ok15:01
lin_yangmaybe we can follow the same way to implement it, it looks good to me15:02
ntpttr_laptopanything else ramineni_ :)?15:02
ramineni_lin_yang: ntpttr_laptop: thanks , will check15:02
ramineni_ntpttr_laptop: yes, :) https://review.openstack.org/#/c/505099/115:03
ramineni_small one..15:03
ramineni_lin_yang: i remember we added the updating with global requirements before for both valenceclient/valence15:03
ramineni_but i dont see those patches for valence, but valenceclient works fine15:04
ntpttr_laptopi'll give it a look ramineni_ !15:04
lin_yangramineni_: yes, but didn't get any update from global requiements recently, right?15:04
lin_yangramineni_: okay, I will take a look at it15:04
lin_yangit's wired15:04
ramineni_like this.. https://review.openstack.org/#/c/495270/15:05
ramineni_ntpttr_laptop: lin_yang: great, thanks.. i took a look at infra.. it includes both projects though15:05
ramineni_ntpttr_laptop: im done from my side15:05
ramineni_:)15:05
ntpttr_laptopokay, thanks ramineni_ :) I'll review your patches15:06
ramineni_ntpttr_laptop: thanks, all updated with comments.. @all please have a look :)15:07
lin_yangramineni_: will do it today, thanks a lot15:08
ramineni_lin_yang: thanks!!15:08
lin_yangntpttr_laptop: we are done here today?15:09
ntpttr_laptopyeah I think so15:09
ntpttr_laptopthanks guys15:09
ntpttr_laptophave a good one!15:09
shuquan8815:09
ramineni_Thanks All.. Bye :)15:09
lin_yangthanks all, bye15:10
*** shuquan has quit IRC15:10
Mrittika_Bye15:10
*** Mrittika_ has quit IRC15:10
*** ntpttr_laptop has quit IRC15:15
*** akhil_jainn has joined #openstack-valence15:16
*** ramineni_ has left #openstack-valence15:16
*** akhill_jain has quit IRC15:19
*** akhil_jainn has quit IRC15:43
*** ntpttr_laptop has joined #openstack-valence16:21
openstackgerritMerged openstack/valence master: Update Rack and Systems controller to be generic  https://review.openstack.org/50197317:26
*** ntpttr_laptop has quit IRC18:42

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