Wednesday, 2017-04-05

*** ntpttr_mobile has joined #openstack-valence05:07
*** ntpttr_mobile has quit IRC05:14
*** ntpttr_mobile has joined #openstack-valence05:14
*** ntpttr_mobile_ has joined #openstack-valence05:18
*** ntpttr_mobile has quit IRC05:18
*** ntpttr_mobile has joined #openstack-valence05:20
*** ntpttr_mobile has quit IRC05:20
*** ntpttr_mobile_ has quit IRC05:20
*** ntpttr_mobile has joined #openstack-valence05:20
*** ntpttr_mobile has quit IRC05:23
openstackgerrithubian proposed openstack/valence-specs master: Spec for the refactor to fully support multi-podmanager  https://review.openstack.org/44899505:38
-openstackstatus- NOTICE: The Gerrit service on http://review.openstack.org is being restarted to address hung remote replication tasks, and should return to an operable state momentarily12:52
*** ntpttr_laptop has joined #openstack-valence14:48
*** HuBian has joined #openstack-valence14:53
*** ananth_n has joined #openstack-valence14:59
ntpttr_laptophello everyone15:00
HuBianhello ~15:00
lin_yanghello everyone15:01
ananth_nhi all15:02
ananth_nany agenda items for today15:02
ntpttr_laptopDoes anyone have topics they'd like to discuss?15:03
HuBianI've a mall topic here15:03
ntpttr_laptopI'd like to talk a bit about what's being discussed in HuBian's spec15:03
HuBianAbout removing the pod manager options from the config file15:03
ntpttr_laptopyep that's the one15:03
ntpttr_laptopI just left this comment on the patch, but I do agree with removing it from the config file15:03
HuBianyeah ~ thank you nate potter15:03
HuBianI've just seen it ~15:04
ntpttr_laptopI think since it's going to be a dynamically managed resource it's okay for an admin to add it first thing when the service comes up and add/remove more as needed15:04
ntpttr_laptopkeeping it in the config file when it could later go away is misleading15:04
HuBian+115:05
ntpttr_laptoplin_yang: what are your thoughts? I know you had some doubts earlier15:05
*** ramineni_ has joined #openstack-valence15:05
ntpttr_laptopananth_n: do you have an opinion one way or the other on it?15:05
ananth_ni agree with removing the podm details from the config15:06
ntpttr_laptopcool I think we can probably close the book on that one15:06
lin_yangI do agree it would be misleading if continue to keep the initial podm info in config file15:06
ananth_nthe same approach could be reused to support multi cloud - instead of PODM details, we'd have some info related to each cloud15:06
lin_yangone concern is it cannot keep all info needed in config file, which might be inconvenient to deploy15:07
*** ntpttr_laptop has quit IRC15:07
*** ntpttr_laptop has joined #openstack-valence15:07
ananth_n@lin_yang could you explain? do you think having an export-import option might help?15:08
lin_yangbut current i don't have another way to improve it15:08
ntpttr_laptoplin_yang: have you had a chance to test any functions on the rack scale hardware we were provided?15:08
ntpttr_laptopoops I think I missed something you said when I got disconnected for a moment15:08
lin_yangmy original thought is keep the podm info in config file, then allow admin to add/remove through api15:09
lin_yangbut i do agree this might be misleading for user15:10
lin_yangthis is trying to keep all needed info in config file15:11
lin_yanglet's remove it from config file at first15:11
ntpttr_laptopsounds good15:11
HuBianok , Thanks for your comments on this ~15:11
ananth_nmy question to lin_yang was that if providing an import-export functionality would help in the case of redeployment. Alternatively, as long at the etcd store is not erased, the data should persist.15:12
lin_yangntpttr_laptop: I didn't get chance to test against on real hardware, will try the sushy at first15:12
ntpttr_laptopah okay that makes sense15:12
ntpttr_laptoplin_yang: okay let me know how it goes, when I tried to run redfish commands on it through the passthrough proxy in valence the commands were hanging15:13
ntpttr_laptopI started working on fixing the systems API since something in the path is broken but my docker started acting up and now I'm trying to fix that15:13
lin_yangI has tried to ssh to that machine and test podm api there directly, still cannot work15:14
lin_yangthat's wired, podm listen on 8443 at that machine, but cannot work even on that machine15:15
ntpttr_laptopyeah something seems wrong15:15
ntpttr_laptopI'll investigate more when I get time, I'm still at the open network summit currently so my valence time is pretty limited15:15
ntpttr_laptoptring to prioritize the time I get on reviews15:15
*** jinxing has joined #openstack-valence15:16
ntpttr_laptopspeaking of which, does anyone have any other patches they'd like reviewed? I think I got to a lot yesterday15:16
ananth_nlin_yang was there any objection to your valence core proposal?15:16
lin_yangananth_n: good suggestion, however podm info in etcd, admin have to export info from etcd and re-import, if new deployment have to use another etcd instance15:17
lin_yangananth_n: no, didn't receive any objection15:17
ntpttr_laptopI think it's a good idea15:18
lin_yangcould you please response to mailinglist with +1 for core nomination?15:18
HuBianSo we could add new apis to import/export podms15:19
ntpttr_laptoplin_yang: I don't know if I got the mail.. I'll double check15:19
ntpttr_laptopdid you tag it <valence>? I don't think thats an official tag and I haven't been seeing those15:19
HuBianThank you for your nomination for me , thank you ~15:19
ntpttr_laptopwait there it is :)15:20
HuBian:)15:20
lin_yangntpttr: I sent to openstack-dev mailinglist, will double check15:20
lin_yangHuBian: you are well-deserved :)15:20
ntpttr_laptopresponse sent!15:20
ramineni_Thanks all for the nomination :)15:21
ntpttr_laptopwell deserved ramineni_!15:21
ntpttr_laptopit'll be good to have more cores in the team for more thorough reviews15:21
ntpttr_laptopmake sure not to +A a patch before it's recieved two +2s now, we have enough people on the team to follow that rule more strictly15:22
lin_yangBasically I do agree the import/export functionality, but may need more discussion on details15:22
ntpttr_laptoptwo +2s before workflow +115:22
openstackgerritMerged openstack/valence-specs master: Spec for the refactor to fully support multi-podmanager  https://review.openstack.org/44899515:22
ntpttr_laptopI apologize but I've got to go, the keynote presentations are beginning15:23
lin_yangthanks for the contribution, Hubian and ramineni_. It would be better if you can contribute more reviews, we need more opinions15:24
HuBianok , I'll15:24
ramineni_ntpttr_laptop: lin_yang: sure, will do15:24
lin_yangI will add both of you into core list today15:24
lin_yangthanks again, well deserved15:25
HuBian:)15:25
lin_yangany other topic?15:25
ananth_n+1 to HuBian and ramineni_15:25
*** ntpttr_laptop has quit IRC15:26
ananth_ni don't have any other topics15:26
HuBianthanks @ananth15:26
ramineni_ananth_n: thanks15:26
HuBianI don't have neither ~15:26
lin_yangif no other topic, we are done today15:26
lin_yangthanks everyone15:26
ananth_nlet's call it a meeting then. thanks all15:27
*** ananth_n has quit IRC15:27
HuBianbye ~ see you next meeting ~15:27
lin_yangbye15:27
*** ramineni_ has left #openstack-valence15:31
*** HuBian has quit IRC15:32
*** jinxing has quit IRC15:46
*** ntpttr_ has quit IRC18:26
*** ntpttr_ has joined #openstack-valence18:40
openstackgerritMerged openstack/valence master: Fix incorrect response example of flavor creation  https://review.openstack.org/45114223:00

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