Tuesday, 2019-04-09

*** Liang__ has joined #openstack-meeting-400:56
*** igordc has quit IRC01:06
*** seajay has joined #openstack-meeting-401:24
*** yamahata has quit IRC01:29
*** iyamahat has quit IRC01:32
*** hongbin has joined #openstack-meeting-401:33
*** seajay has quit IRC01:39
*** njohnston has quit IRC02:05
*** roman_g has quit IRC02:29
*** Liang__ is now known as LiangFang02:30
*** hongbin has quit IRC02:35
*** diablo_rojo has quit IRC02:37
*** hongbin has joined #openstack-meeting-402:38
*** igordc has joined #openstack-meeting-402:40
*** hongbin has quit IRC02:49
*** hongbin has joined #openstack-meeting-402:51
*** yamahata has joined #openstack-meeting-402:59
*** yamamoto has quit IRC03:40
*** yamamoto has joined #openstack-meeting-403:55
*** hongbin has quit IRC04:05
*** LiangFang has quit IRC04:09
*** Liang__ has joined #openstack-meeting-404:11
*** iyamahat has joined #openstack-meeting-404:15
*** markvoelker has quit IRC04:31
*** Liang__ is now known as LiangFang05:11
*** igordc has quit IRC05:11
*** iyamahat has quit IRC05:23
*** e0ne has joined #openstack-meeting-405:25
*** e0ne has quit IRC05:29
*** LiangFang has quit IRC05:38
*** Liang__ has joined #openstack-meeting-405:43
*** Liang__ is now known as LiangFang05:44
*** LiangFang has quit IRC05:48
*** Liang__ has joined #openstack-meeting-405:49
*** Liang__ is now known as LiangFang05:49
*** radeks has joined #openstack-meeting-406:04
*** radeks has quit IRC06:28
*** radeks has joined #openstack-meeting-406:29
*** pcaruana has joined #openstack-meeting-406:30
*** markvoelker has joined #openstack-meeting-406:32
*** snapiri has quit IRC06:33
*** slaweq has joined #openstack-meeting-406:47
*** radeks has quit IRC06:55
*** markvoelker has quit IRC07:06
*** slaweq has quit IRC07:17
*** slaweq has joined #openstack-meeting-407:17
*** roman_g has joined #openstack-meeting-407:39
*** ralonsoh has joined #openstack-meeting-407:48
*** happyhemant has joined #openstack-meeting-407:48
*** ralonsoh has quit IRC07:58
*** gnuoy has quit IRC07:58
*** ralonsoh has joined #openstack-meeting-407:58
*** markvoelker has joined #openstack-meeting-408:03
*** e0ne has joined #openstack-meeting-408:13
*** yamamoto has quit IRC08:30
*** yamamoto has joined #openstack-meeting-408:36
*** markvoelker has quit IRC08:36
*** e0ne has quit IRC08:37
*** e0ne has joined #openstack-meeting-408:47
*** Luzi has joined #openstack-meeting-408:56
*** iyamahat has joined #openstack-meeting-409:08
*** k_mouza has joined #openstack-meeting-409:10
*** yamamoto has quit IRC09:16
*** e0ne has quit IRC09:25
*** e0ne has joined #openstack-meeting-409:44
*** yamamoto has joined #openstack-meeting-409:44
*** k_mouza has quit IRC09:47
*** yamamoto has quit IRC09:47
*** LiangFang has quit IRC09:48
*** k_mouza has joined #openstack-meeting-409:57
*** psachin has joined #openstack-meeting-409:59
*** salmankhan has joined #openstack-meeting-410:00
*** yamamoto has joined #openstack-meeting-410:02
*** yamamoto has quit IRC10:08
*** k_mouza has quit IRC10:11
*** k_mouza_ has joined #openstack-meeting-410:11
*** yamamoto has joined #openstack-meeting-410:15
*** yamamoto has quit IRC10:18
*** yamamoto has joined #openstack-meeting-410:21
*** yamamoto has quit IRC10:21
*** yamamoto has joined #openstack-meeting-410:22
*** yamamoto has quit IRC10:24
*** yamamoto has joined #openstack-meeting-410:24
*** markvoelker has joined #openstack-meeting-410:33
*** e0ne has quit IRC10:37
*** e0ne has joined #openstack-meeting-410:44
*** k_mouza_ has quit IRC10:44
*** k_mouza has joined #openstack-meeting-410:53
*** k_mouza has quit IRC10:58
*** yamamoto has quit IRC11:01
*** yamamoto has joined #openstack-meeting-411:03
*** markvoelker has quit IRC11:07
*** yamamoto has quit IRC11:07
*** yamamoto has joined #openstack-meeting-411:09
*** yamamoto has quit IRC11:09
*** yamamoto has joined #openstack-meeting-411:26
*** e0ne has quit IRC11:30
*** yamamoto has quit IRC11:41
*** yamamoto has joined #openstack-meeting-411:59
*** yamamoto has quit IRC11:59
*** seajay has joined #openstack-meeting-412:00
*** celebdor1 has joined #openstack-meeting-412:18
*** celebdor1 has quit IRC12:22
*** celebdor1 has joined #openstack-meeting-412:23
*** celebdor1 has quit IRC12:28
*** Liang__ has joined #openstack-meeting-412:34
*** Liang__ is now known as LiangFang12:34
*** arunkant has joined #openstack-meeting-412:35
*** yamamoto has joined #openstack-meeting-412:43
*** Luzi_ has joined #openstack-meeting-412:46
*** Luzi has quit IRC12:49
*** e0ne has joined #openstack-meeting-412:54
*** jroll has quit IRC12:55
*** jroll has joined #openstack-meeting-412:59
*** mjturek has joined #openstack-meeting-413:07
*** yamamoto has quit IRC13:10
*** yamamoto has joined #openstack-meeting-413:11
*** yamamoto has quit IRC13:11
*** howell has joined #openstack-meeting-413:12
*** Luzi_ has quit IRC13:17
*** mjturek has quit IRC13:35
*** mjturek has joined #openstack-meeting-413:35
*** lpetrut has joined #openstack-meeting-413:42
*** liuyulong|away is now known as liuyulong13:44
*** yamamoto has joined #openstack-meeting-413:51
*** e0ne has quit IRC13:53
*** sgrasley__ has quit IRC14:02
*** yamamoto has quit IRC14:02
*** sgrasley has joined #openstack-meeting-414:02
*** itxaka has joined #openstack-meeting-414:04
*** lpetrut has quit IRC14:04
*** celebdor1 has joined #openstack-meeting-414:13
*** klamath has quit IRC14:15
*** gagehugo has joined #openstack-meeting-414:15
*** celebdor1 has quit IRC14:20
*** pgaxatte has joined #openstack-meeting-414:23
*** bobh has joined #openstack-meeting-414:28
*** e0ne has joined #openstack-meeting-414:31
*** gcheresh_ has joined #openstack-meeting-414:33
*** igordc has joined #openstack-meeting-414:42
*** lemko has joined #openstack-meeting-414:46
*** lpetrut has joined #openstack-meeting-414:48
*** gcheresh has joined #openstack-meeting-414:50
*** gcheresh_ has quit IRC14:54
*** howell has quit IRC14:59
*** howell has joined #openstack-meeting-414:59
*** jsuchome has joined #openstack-meeting-414:59
evrardjpo/15:00
jsuchomeo/15:01
howello/15:01
portdirect#startmeeting openstack-helm15:01
openstackMeeting started Tue Apr  9 15:01:11 2019 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:01
openstackThe meeting name has been set to 'openstack_helm'15:01
evrardjp\o15:01
alanmeadowso/15:01
gagehugoo/15:01
pgaxatteo/15:01
portdirectlets give it a couple of mins for people to arrive15:01
*** prabhusesha has joined #openstack-meeting-415:01
itxaka\o o/15:01
portdirectthe agenda for today is here: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-04-0915:01
mattmceueno/15:01
portdirectplease add to it :)15:01
evrardjpitxaka: your blue is... quite punchy :D15:02
itxakaI know, I dont know what to change it to so its easily discernible but doesnt make eyes bleed15:02
evrardjp=)15:03
portdirectit reminds me of word processing in displaywrite415:03
*** dwalt has joined #openstack-meeting-415:04
evrardjpsouvenirs!15:04
srwilkerso/15:04
prabhuseshaHi15:05
portdirectok - lets go15:05
portdirect#topic Office hours15:05
*** openstack changes topic to "Office hours (Meeting topic: openstack-helm)"15:05
prabhuseshaThis is Prabhu from Juniper15:05
portdirectso after last weeks meeting I did a straw poll amongst cores15:05
evrardjpI thought you were sending this publicly in the ML?15:06
portdirectand we would like to run office hours on wednesday each week from 20:00-21:00UTC15:06
portdirectas this is the time that would allow us to ensure that we have at least a couple of cores present every week15:06
itxakais there no EU cores? seems a very late time for EUr people to ask questions :)15:07
evrardjpitxaka: there are none15:07
portdirectand that was the critical thing we needed to ensure to give us a chance of giving real value to these sessions15:07
portdirectitxaka: at the moment only lost europeans - though it would be great to change that15:08
evrardjpportdirect: that's correct, without cores, it's impossible to get mentored15:08
evrardjpLet's see if you have enough ppl to mentor. I am pretty sure jayahn will love this news :)15:08
evrardjpIt's a good step forward, thanks portdirect  for organising this!15:08
evrardjpitxaka: we can still have jhesketh as our representative for questions :)15:09
itxaka:)15:09
portdirectok - I'll send out a note to the ml after this and get the wiki updated15:09
jayahnI have been traveling, and someone mentioned my name. :)15:10
jayahnI am in Las Vegas for NAB show. Doing some exhibition. :)15:10
evrardjpI did -- Please don't hesitate to read the meeting log -- there is a proposal of office hours time.15:10
jayahnI will surely read through15:10
evrardjpportdirect: thanks15:10
*** angiewang has joined #openstack-meeting-415:11
jayahnportdirect: thanks as well. :)15:11
portdirectnp - im hoping that we can get some real flow out of these15:11
portdirectso lets move on15:11
portdirect#topic Status of Tempest chart15:11
*** openstack changes topic to "Status of Tempest chart (Meeting topic: openstack-helm)"15:11
itxakathats me!15:11
portdirectfloors yours :)15:12
itxakaSo looking yesterday at the tempest chart and trying to deploy I found out that it has some weird and missing default values which make it impossible to deploy15:12
itxakai.e: wrong image (does not exists), default null values which are not really null and so on15:12
itxakawas wondering if we need more testing in there as its currently not possible to deploy tempest with the default values properly15:13
itxakabtw, sent some patches already for those things, but makes me wonders which others may be broken as well15:13
portdirecti think this really speaks to the gaps we have in our testing atm15:14
srwilkerswe used to trigger an experimental job with the following: https://github.com/openstack/openstack-helm/blob/master/tools/deployment/multinode/900-tempest.sh15:14
itxakawhich links with the next point whiich is basically the same but for spiceproxy :)15:14
srwilkersalbeit, it's a bit dated at this point15:14
portdirectjayahn: i think you are currently using the tempest chart?15:14
itxakaIm not sure of what a solution could be, other than getting more people to use the tempest chart and report things :)15:15
evrardjpitxaka: making this part of the jobs, and voting?15:15
srwilkersnot voting15:15
srwilkersas currently it's not exercised at all15:15
evrardjpnot immediately15:15
evrardjpI mean as a long term goal15:15
itxakaif it doesnt vote it will get ignored forever :D15:16
srwilkersalso in my experience, running tempest as an experimental check previously would more often than not put a large amount of strain on the nodepool vms15:16
evrardjpif it's maintained, I don't see a reason to not make it voting15:16
srwilkersit needs a promotional period like all the other jobs we introduce15:16
evrardjpsrwilkers: I have noticed the impact when doing this in parallel, but running in serial is longer but with less impact.15:16
srwilkerswhere we can vet it and determine whether it's reliable or not15:16
portdirecti really think it would be great to make this a goal15:16
portdirectas tempest should be the de-facto way we validate the basic sanity of an osh deployed cloud15:17
srwilkersi dont disagree15:17
evrardjpsrwilkers: totally -- it's not like we should drop a new job and say "hey, it's the new world order"15:17
evrardjpit's up to cores to +w anyway :p15:17
itxakawell, if you make it sound that cool, maybe we will15:17
evrardjpportdirect: agreed15:17
itxakas/will/should/g15:17
*** gcheresh has quit IRC15:17
portdirectwhould anyone like to step up here?15:18
evrardjptempest has multiple tests, we don't need to run everything. I think we could run only smoke tests15:18
portdirect++15:18
jsuchome+1 for some tests15:18
evrardjpportdirect: I guess the first action point would be to fix things, and discuss it with jayahn?15:18
jsuchomesmoke15:18
portdirectevrardjp: yes15:19
srwilkerstempest is set up to run smoke tests by default if i recall15:19
itxakait is, srwilkers15:19
evrardjpif we get jayahn to review (as main user of said helm chart), we should be good to re-introduce a non voting job15:19
itxakaI can take that unless somebody really, really, *really* want it :)15:19
itxakafix, test, add job15:19
evrardjpsrwilkers: we should maybe whitelist until confidence, then move to more complete scenarios then15:20
evrardjpbecause there are lots of smoke tests in default test list15:20
srwilkersevrardjp: im fine with that.  however, id also like to see more individuals take interest in maintaining the jobs we currently have.  we've got a small subset of people actually looking at our periodic jobs and attempting to fix what's broken15:20
portdirectitxaka: i think from what jayahn just posted in openstack-helm, that would be great - and i'd add jaesang to reviews15:20
evrardjpsrwilkers: that's a fair point.15:20
evrardjpbut if those jobs are voting, people will have no choice than to fix things? :p15:21
srwilkersthats a lazy approach15:21
portdirectsrwilkers: you have been doing pretty much all the work here - and really deserve thanks for that15:21
itxakasrwilkers, should we bring that up in the agenda to discuss? Im interested in that15:21
evrardjpthe lazy approach IMO would be to make the jobs non voting or experimental when they start to fail...15:21
evrardjpbut I agree it's always the problem when new jobs are introduced15:21
srwilkersits not even new jobs evrardjp15:21
srwilkerswe've had failing voting jobs before, and my previous statement applies: it's a small set of people working to triage and fix them as soon as possible to get the pipes moving again15:22
srwilkerswhich is why im super skeptical about just jamming in new voting jobs, until that changes15:22
portdirectsrwilkers: agreed15:22
evrardjpthat's everyone's duty IMO.15:22
evrardjpyou see something failing you fix it15:23
portdirecti think we should probably try and implement what we planned at the last ptg evrardjp15:23
evrardjpsome people are just unaware of some of the issues though, and they don't monitor periodics15:23
portdirectbut aware that we are all time poor there15:23
* itxaka didnt even knew there were periodic jobs...15:23
*** e0ne has quit IRC15:23
itxakadid I drop or everyone went silent?15:25
evrardjphttp://zuul.openstack.org/builds?project=openstack%2Fopenstack-helm15:25
evrardjpthe scarier is here:15:26
evrardjphttp://zuul.openstack.org/builds?project=openstack%2Fopenstack-helm&pipeline=periodic15:26
*** e0ne has joined #openstack-meeting-415:27
itxakashould we...move onto the next point?15:27
evrardjpI would be fine with that15:27
portdirect#topic Status of Spiceproxy15:28
*** openstack changes topic to "Status of Spiceproxy (Meeting topic: openstack-helm)"15:28
portdirectitxaka: your up again :)15:28
itxakasame thing, different name15:28
portdirecthere i think jayahn has a production clouding usuing this for vdi?15:29
itxakaspiceproxy was missing serviceaccounts, which leads me to think that there was no testing in there for it15:29
*** lpetrut has quit IRC15:29
itxakadamn jayahn has everything which is broken :P15:29
portdirectno - i think this is just the tip of the iceberg15:29
portdirectthanks for digging into it itxaka15:29
itxakaso same thing as with tempest, should we fix, test, add non-voting?15:29
evrardjplgtm15:30
portdirecti think thats the prudent thing15:30
portdirectitxaka: you already added the svc account i think?15:30
*** iyamahat has quit IRC15:30
itxakaI could help there, unfortunately I have never used spiceproxy so Im not sure what the configs for it are15:30
itxakaportdirect, yep, I did15:30
evrardjpwould do this in two different patches though (fixing and change testing)15:30
portdirecti could take that on if you like, i used to use spice a bit15:30
itxakabut it still didnt work for me due to permission errors, so Im wondering what else is missing in there15:30
*** JamesBenson has joined #openstack-meeting-415:30
evrardjp (except if tempest testing of this is already present, which I doubt)15:31
srwilkersthe spice must flow15:31
itxakaportdirect, that sounds good, I'll post in openstack-helm the exact error that I got then15:31
portdirectthx - I'll update the etherpad15:31
portdirectok to move on?15:32
itxaka:+115:32
portdirect#topic status of image registry authentication15:32
*** openstack changes topic to "status of image registry authentication (Meeting topic: openstack-helm)"15:32
portdirectnot sure who added this?15:32
pgaxattethat would be me15:32
pgaxattei'm looking into using a private registry to pull images15:32
pgaxatteand i need to use authentication15:32
pgaxattestumbled upon angiewang's specs15:33
portdirectyeah - its a nice bit of work15:33
pgaxattebut it seems to need some work and i was wondering what was the status on it15:33
portdirectwe should chase up with Angie, but since its been merged i dont think we have managed to make any progress15:33
pgaxattei could not find any related patch in progress15:34
portdirectthough the spec makes pretty clear the work that needs done, so i think anyone could pick it up15:34
itxakawow that spec is pretty cool, the code is basically there :o15:34
pgaxattei would gladly try it but i have very little experience with helm15:34
angiewanghi currently, the implementation for the support private registry with auth has not started yet.15:35
itxakasounds like an opportunity for some mentoring no?15:35
evrardjpitxaka: +115:36
pgaxattethat would be great15:36
evrardjpportdirect: sorry to highjack the topic, but there is an onboarding session at the next summit for OSH, right?15:37
portdirectevrardjp: there is15:37
pgaxatteawesome15:37
evrardjpsadly those are not recorded, but the eventual slides can be re-used/shared.15:37
evrardjppgaxatte: will you be there?15:37
pgaxatteevrardjp: yes15:37
evrardjpperfect.15:38
portdirectangiewang: do you have time to work on this atm? it would be great if we could get a refence to spread out across charts15:38
evrardjpangiewang: and if you could bring pgaxatte along the way that would be helpful to grow the community15:38
evrardjp(no pressure though!)15:39
angiewangdo you mean pgaxatte will be implementing the changes in my spec and I will be helping with any issues15:40
*** dave-mccowan has joined #openstack-meeting-415:41
evrardjpI just mean there are opportunities to work together15:41
evrardjpfor example, pgaxatte could learn by reviewing15:41
portdirecttogether we can spread the load15:41
evrardjpor the other way around pgaxatte could learn by doing and you would mentor in the reviews15:41
pgaxatteanyway i'm ok with it15:42
evrardjpor what portdirect said.. but basically communication is key :)15:42
pgaxattelet it be noted that i still have a lot of things to understand on openstack-helm and openstack-helm-infra15:42
evrardjps/but//15:42
portdirectpgaxatte: dont worry - we all do :)15:43
pgaxatteespecially on helm-toolkit15:43
portdirectare you working on the tungesten-fabric charts atm pgaxatte ?15:43
angiewangI have other tasks right now, I am not available to implement this at the moment(in the next month). I can help pgaxatte in reviews though.15:44
pgaxatteportdirect: no we're looking at core components and mistral at the moment15:44
*** bobh has quit IRC15:44
pgaxatteangiewang: help with the reviews would be great too15:45
portdirectok - mistral falls well within that bucket of things that have regressed in tests since the last ptg - we should also work to restore that15:45
*** bh526r has joined #openstack-meeting-415:46
pgaxatteportdirect: that's something we plan on working on too, we'll probably have the occasion to contribute back15:46
angiewangpgaxatte Yeah, I can help in reviews.15:46
angiewangI can also help with implementing a month later15:47
angiewangIf it's not rush15:47
portdirectangiewang: will you be in denver at the end of the month?15:47
evrardjpI think the introductions are done now15:47
pgaxatteno problem we can bypass that for now in our roadmap15:47
angiewangportdirect, no15:48
portdirectpgaxatte: as a short term, you can add .dockercfg with the appropriate creds to the kubeletes home dir15:48
portdirectbut lets see if we can get the ball rolling on implementing the correct approach15:48
portdirectangiewang: thats a shame, would have been great to have you out there15:48
portdirectok to move on?15:49
pgaxatteok for me15:49
prabhuseshaSorry to jump in.15:49
prabhuseshaI'm Prabhu, first time to this mtg.15:49
prabhuseshaNeed some time at the end15:49
portdirectwill do prabhusesha15:50
prabhuseshaI didn't add my stuff to the agenda15:50
portdirectcan you add that now? https://etherpad.openstack.org/p/openstack-helm-meeting-2019-04-0915:50
prabhuseshathanks115:50
*** pmesserli has quit IRC15:50
portdirect#topic reviews15:50
*** openstack changes topic to "reviews (Meeting topic: openstack-helm)"15:50
portdirectso - we have quite a few outstanding reviews this week that could do with some love15:50
portdirecthttps://review.openstack.org/#/c/647493/ Add internal tenant id in conf (irc: LiangFang)15:51
portdirect^ would be great to get some more fb on this - would be really nice to have this feature15:52
portdirecthttps://review.openstack.org/#/c/651140/ WIP: Use real rpc methods to find out if the service is alive15:52
portdirectproblem - maybe not enough read-only RPC calls?15:52
portdirectproblem - RPC service versioning changes per objective and sometimes per release (versions could be tracked with release specific values overrides)15:52
portdirectjsuchome riases a good point here, and one we were painfully aware of when implementing the probes inititally15:52
jsuchomehi15:53
portdirectit would be nice to re-visit and see if theres a way we can implement this without causing tracebacks in logs15:53
jsuchomeoriginally I wanted to ask if it could be the right approach, to use some real methods instead of fake one15:53
jsuchomebut I was looking at it today15:53
portdirectit would be lovely is oslo.messgaing supported a `ping` but there we are ;)15:53
itxakamaybe a different approach? do we have to check for RPC aliveness? Is there any other places we can look at for how to do this?15:53
jsuchomeand it seems to me that some components like conductor and scheduler does not seem to support read-only rpc calls15:53
portdirectthis was the challenge we hit jsuchome :(15:54
jsuchomeah, so that explains weird implementation15:54
portdirectitxaka: with the absence of more rich reporting from the agents, im at a loss as to how we can do this another way15:55
portdirectbut would love to have one15:55
jsuchomeI guess it's wrong approach, trying to add such 'ping' calls to nova code... ?15:55
evrardjpget hypervisor status for compute?15:55
portdirectevrardjp: but that does not cover the hard ones15:56
evrardjpyeah. I suppose we should discuss this in self-healing15:56
portdirectwe need read-only rpc across the board15:56
jsuchomecompute actually is solvable, as proposed in that patch15:56
evrardjpbecause they probably have ideas there15:56
portdirectevrardjp: agreed15:56
evrardjplooks like a good collaboration topic for ptg15:56
jsuchomewould anyone else (apart from helm project) benefit from new calls?15:57
portdirectit would be awesome if we could move off this approach15:57
evrardjpwith oslo team15:57
portdirectjsuchome: if done properly - every deployment/management project could15:57
itxakaanything that implements monitoring would take advantage of that15:57
evrardjpit doesn't need to be a community goal, but something like that can be approach by a pop up team15:57
*** bobh has joined #openstack-meeting-415:57
evrardjpapproached*15:58
jsuchomehm, might be a good idea to bring it in nova meeting15:58
portdirectthere have been a few efforts in the past here, though normally they have stalled15:58
portdirectgetting a project like nova to lead the way would be great15:58
* portdirect we ok to run over a few mins15:58
evrardjpportdirect: in this room? I think it's better to continue in #openstack-helm if necessary15:59
evrardjpbeing a good citizen :)15:59
portdirectprabhusesha: you oke if we dicsuss your topic in the main #openstack-helm channel?  `Keystone failure with all-in-one setup`15:59
prabhuseshaok16:00
jsuchomeis anyone here active in nova? If not, I can try to ask there myself (still RPC topic)16:00
portdirectjsuchome: that would rock16:00
portdirectitxaka: did my comments in the etherpad help you with your questions re reviews?16:00
portdirectif not lets take it to the openstack-helm channel16:00
itxakaportdirect, yep feel free to ignore those, I got enough as to move them forward16:01
portdirectawesome - thanks :)16:01
jsuchomeI mean, it would be better if it would be someone better known to nova community, but I'd do that if no one else fits such description16:01
portdirectsorry we out of time folks16:01
portdirect#endmeeting openstack-helm16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:01
itxakao/16:01
openstackMeeting ended Tue Apr  9 16:01:35 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-04-09-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-04-09-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-04-09-15.01.log.html16:01
evrardjpthanks portdirect16:01
*** diablo_rojo has joined #openstack-meeting-416:01
itxakathanks all!16:01
angiewang:) I am really looking for the review on https://review.openstack.org/#/c/641518/ - Add aodh chart16:01
prabhuseshahello16:02
prabhuseshacan somebody help with the tungstenfabric review ?16:02
prabhuseshahttps://review.openstack.org/#/c/622573/216:03
*** jamesgu__ has joined #openstack-meeting-416:03
prabhuseshaportdirect, evrardjp, itxaka,16:04
prabhuseshaany volunteers16:05
portdirectprabhusesha: will do16:05
jsuchomeprabhusesha: I think you should move the discussion to #openstack-helm , this channel is reserved for meetings and ours ended16:05
*** pgaxatte has left #openstack-meeting-416:05
prabhuseshaok.  For the review,  i need some help16:05
*** jsuchome has left #openstack-meeting-416:05
*** mjturek has quit IRC16:05
prabhuseshathanks! portdirect16:06
portdirectprabhusesha: if you join openstack-helm channel we can help with the keystone issue16:06
*** e0ne has quit IRC16:08
*** dwalt has left #openstack-meeting-416:09
prabhuseshai already posted on helm-channel. i got some comments16:10
*** gagehugo has left #openstack-meeting-416:10
prabhusesha@Moh provided some comments.16:11
*** yamahata has quit IRC16:35
*** salmankhan has quit IRC16:39
*** mjturek has joined #openstack-meeting-416:50
*** mfuller_ has joined #openstack-meeting-416:54
*** prabhusesha has quit IRC16:56
*** gcheresh has joined #openstack-meeting-416:56
*** iyamahat has joined #openstack-meeting-416:57
*** psachin has quit IRC17:00
*** yamahata has joined #openstack-meeting-417:07
*** gcheresh has quit IRC17:24
*** yamamoto has joined #openstack-meeting-417:28
*** pmesserli has joined #openstack-meeting-417:30
*** bobh has quit IRC17:32
*** gmann is now known as gmann_afk17:40
*** ralonsoh has quit IRC17:44
*** pmesserli has quit IRC18:04
*** e0ne has joined #openstack-meeting-418:16
*** yamamoto has quit IRC18:19
*** gmann_afk is now known as gmann18:21
*** e0ne has quit IRC18:23
*** lpetrut has joined #openstack-meeting-418:25
*** lpetrut has quit IRC18:29
*** e0ne has joined #openstack-meeting-418:33
*** happyhemant has quit IRC18:38
*** yamamoto has joined #openstack-meeting-418:58
*** yamamoto has quit IRC19:09
*** e0ne has quit IRC19:15
*** e0ne has joined #openstack-meeting-419:44
*** angiewang has quit IRC20:04
*** mjturek has quit IRC20:18
*** pcaruana has quit IRC20:31
*** pcaruana has joined #openstack-meeting-420:33
*** pcaruana has quit IRC20:36
*** pcaruana has joined #openstack-meeting-420:39
*** lemko has quit IRC20:44
*** pcaruana has quit IRC20:47
*** howell has quit IRC21:23
*** igordc has quit IRC21:25
*** e0ne has quit IRC21:28
*** JamesBenson has quit IRC21:54
*** slaweq has quit IRC22:01
*** seajay has quit IRC22:06
*** hongbin has joined #openstack-meeting-422:13
*** slaweq has joined #openstack-meeting-422:14
*** slaweq has quit IRC22:18
*** k_mouza has joined #openstack-meeting-422:53
*** JamesBenson has joined #openstack-meeting-423:30
*** JamesBenson has quit IRC23:34
*** slaweq has joined #openstack-meeting-423:48
*** hongbin has quit IRC23:48
*** bh526r has quit IRC23:50
*** dklyle has quit IRC23:52
*** slaweq has quit IRC23:52
*** LiangFang has quit IRC23:56

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