Wednesday, 2017-04-12

*** ramineni has quit IRC08:07
*** ramineni has joined #openstack-valence08:20
*** mkrai has quit IRC09:11
*** mkrai has joined #openstack-valence09:16
*** Raghav has joined #openstack-valence14:47
*** ntpttr__ has joined #openstack-valence14:56
*** HuBian has joined #openstack-valence14:58
*** HuBian has quit IRC14:59
ntpttr__hello everyone o/15:01
*** HuBian_ has joined #openstack-valence15:01
*** ntpttr__ is now known as ntpttr_laptop15:01
lin_yanghello15:01
HuBian_hello15:01
ntpttr_laptopare there any topics for today?15:02
ntpttr_laptopanything folks would like reviewed?15:02
Raghavhello15:03
Raghavregarding BP valence-openstack-flavor15:03
ntpttr_laptophi Raghav, sure15:03
Raghavhttps://review.openstack.org/#/c/454042/615:04
Raghavi got review comments from Stephen Finucane15:04
*** ananth_n has joined #openstack-valence15:04
ananth_nHi all15:05
ntpttr_laptopRaghav: yes, I think he gave some good comments with regard to resource providers and what's going on in nova15:05
*** jinxing has joined #openstack-valence15:05
Raghavyes15:06
Raghavwant to know how shall we proceed with BP15:06
ananth_nI15:07
ananth_nOops15:07
Raghavos-traits project work is in progress15:07
ananth_nI was wondering if we should go ahead and hve something at least15:07
*** ntpttr__ has joined #openstack-valence15:07
*** ntpttr_laptop has quit IRC15:08
ntpttr__the things that stephen mentions in his paragraph on things nova won't be able to do for you on pods and racks and such, since nov works at a host level15:08
ananth_nTill traits becomes fully functional15:08
*** jinxing has quit IRC15:08
ntpttr__ananth_n: what was the first thing you said there? I disconnected for a moment15:08
ananth_nI was saying that we probably should have the flavor part implemented15:09
ananth_nTill traits becomes mainstream15:09
ntpttr__Personally I don't know if adding things like exporting flavors that cover things like cpu architecture is worth it15:09
ntpttr__if we have RSD specific traits that nova won't cover, then that's great15:10
*** jinxing has joined #openstack-valence15:10
*** jinxing has quit IRC15:10
ntpttr__but for host-level things that nova will already be monitoring I'm not sure why it would be helpful15:11
RaghavRSD features like processor speed15:11
*** jinxing has joined #openstack-valence15:12
ntpttr__Raghav: but that's not really an RSD feature, that's just host-level metadata15:12
Raghavthat nova currently doesn't track15:12
*** jinxing has quit IRC15:12
ntpttr__and adding that to a flavor feels hacky when nova is working on a way to natively implement it15:12
ntpttr__I won't stop it from being implemented if everyone disagrees with me, I just want to get my opinion out there15:12
ananth_nI can see how traits & enhanced platform awareness help with scheduling15:14
ntpttr__I agree with Stephen that if we want to get this sort of thing into OpenStack we'd be better off working with the nova team to get resource providers up and running15:14
ntpttr__idk how many people would actually use this valence workaround15:15
lin_yangPodm 2.1 will add RSD specific hardware support, right?15:15
ntpttr__ananth_n: I agree15:15
ntpttr__lin_yang: what do you mean by that?15:16
ntpttr__what kind of RSD specific hardware15:16
lin_yanglike attach nvme storage and fpga via PCIE connection to composed node15:17
ananth_nNate, do traits get exposed as flavors to the end user? Do you know?15:18
ntpttr__ananth_n: no, I think they're exposed through resource providers15:19
ntpttr__and will have their own API15:19
ntpttr__here's some more info about them https://specs.openstack.org/openstack/nova-specs/specs/pike/approved/resource-provider-traits.html15:19
lin_yangfrom my current understanding, resource provider cannot expose this kinds of resource after attach them to node15:19
ananth_nThanks.15:20
ntpttr__lin_yang: I believe that's where custom traits will come in15:20
ntpttr__a user can define custom traits to be whatever they want if I recall right15:21
lin_yangthanks for clarification, will figure out more on traits15:22
ananth_nIt seems traits will eventually help. I am wondering if we should have something in the interim15:23
ntpttr__ananth_n: we can add something if everyone thinks it's a good idea, but do we know who will use it?15:24
ntpttr__do we have anyone at the moment actively wanting to use the flavor export feature that wouldn't want to wait to do it the openstack way?15:24
ntpttr__it feels like a duplication of effort, which is sort of a frowned upon thing in openstack, like if we want this feature in, why not help nova if we can to test or complete it?15:25
ananth_nntpttr_ the main reason was the showing something to REDHAT. And I agree that there is potential wasted effort15:26
ntpttr__sorry to play devil's advocate on this feature, I just want to make sure we've thought about all the options before going ahead15:26
ntpttr__ah okay fair enough15:27
ntpttr__at the same time though, if you're talking to folks in redhat who have any kind of openstack experience, I imagine they'll have the same questions15:27
ntpttr__for instance, stephen who left the review on the spec is from redhat15:27
ananth_n:-)15:28
ntpttr__sorry I really feel like a nay-sayer here15:28
ananth_nOk, let's go back to the other RH folks. And based on the15:30
ananth_nInput they give, take it forward15:30
ntpttr__that sounds good15:30
ntpttr__we can mention this dialogue we've been having, using nova traits/resource providers long term vs. exporting flavors now15:31
lin_yangsounds good15:31
ananth_nYup15:31
ananth_nAny other topics?15:31
ananth_nAll Boston attendees have booked their travel?15:32
ntpttr__is anyone here going to boston?15:32
ntpttr__ananth_n: are you going?15:32
lin_yangmy request is declined15:32
ananth_nNope, no funding. If my talk gets a slot, Madhuri will cover15:33
lin_yangI think 99cloud and Lenovo folks will go to boston15:33
HuBian_yeah ~ i'll be there15:33
ananth_nShe got travel funding from Openstack15:33
ntpttr__lin_yang: cool, the other folks on your talk will go?15:33
ntpttr__ananth_n: nice!15:33
HuBian_And i've booked hotel and air tickets ~15:34
ananth_nHuBian cool!15:34
HuBian_:)15:34
lin_yangntpttr: Shuquan from 99cloud will go to boston and cover the talk15:35
ntpttr__sounds like we will have some coverage :)15:35
ntpttr__anything else for today guys?15:36
ananth_nNone from me. And I need to drop15:37
ananth_nBye all15:37
ntpttr__okay sounds good, thanks everyone. If you have anything you'd like revewed feel free to drop the link here in irc15:37
HuBian_thank you ~15:37
HuBian_bye ~15:37
*** ananth_n has quit IRC15:38
ntpttr__bye!15:38
lin_yangthanks everyone, bye15:38
*** HuBian_ has quit IRC15:38
Raghavthank you..bye15:38
*** Raghav has quit IRC15:38
*** ntpttr__ has quit IRC16:48
*** ntpttr has joined #openstack-valence16:55
*** ntpttr__ has joined #openstack-valence17:07
*** ntpttr has quit IRC17:07
*** ntpttr__ has quit IRC17:56
*** ntpttr has joined #openstack-valence17:59
*** ntpttr has quit IRC18:30
*** ntpttr has joined #openstack-valence19:16
*** ntpttr has quit IRC19:18
*** ntpttr has joined #openstack-valence19:18
*** ntpttr has quit IRC21:08
*** ntpttr has joined #openstack-valence21:08
-openstackstatus- NOTICE: Restarting Gerrit for our weekly memory leak cleanup.21:27
*** ntpttr has quit IRC21:55
*** ntpttr has joined #openstack-valence22:02
*** ntpttr has quit IRC23:08
*** ntpttr__ has joined #openstack-valence23:08

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