Tuesday, 2018-02-20

*** slaweq has joined #openstack-meeting-500:27
*** slaweq has quit IRC00:32
*** mjturek has quit IRC01:21
*** yamahata has quit IRC03:17
*** slaweq has joined #openstack-meeting-503:48
*** slaweq has quit IRC03:53
*** slaweq has joined #openstack-meeting-504:01
*** slaweq has quit IRC04:05
*** yamamoto has joined #openstack-meeting-504:34
*** slaweq has joined #openstack-meeting-504:38
*** ying_zuo has left #openstack-meeting-504:38
*** slaweq has quit IRC04:43
*** slaweq has joined #openstack-meeting-505:09
*** slaweq has quit IRC05:14
*** slaweq has joined #openstack-meeting-506:03
*** slaweq has quit IRC06:08
*** yamamoto has quit IRC06:23
*** yamamoto has joined #openstack-meeting-506:33
*** yamamoto has quit IRC07:42
*** yamamoto has joined #openstack-meeting-507:43
*** slaweq has joined #openstack-meeting-507:44
*** slaweq has quit IRC07:45
*** yamamoto has quit IRC07:46
*** yamamoto has joined #openstack-meeting-507:50
*** slaweq has joined #openstack-meeting-507:54
*** yamamoto has quit IRC07:59
*** yamamoto has joined #openstack-meeting-508:31
*** yamamoto_ has joined #openstack-meeting-508:54
*** yamamoto has quit IRC08:58
*** slaweq_ has joined #openstack-meeting-509:22
*** slaweq_ has quit IRC09:26
*** derekh has joined #openstack-meeting-509:41
*** MarkBaker has quit IRC11:14
*** yamamoto_ has quit IRC12:13
*** yamamoto has joined #openstack-meeting-512:28
*** yamamoto has quit IRC12:31
*** yamamoto has joined #openstack-meeting-512:31
*** yamamoto has quit IRC12:31
*** yamamoto has joined #openstack-meeting-512:36
*** MarkBaker has joined #openstack-meeting-513:05
*** yamamoto has quit IRC14:12
*** mjturek has joined #openstack-meeting-514:29
*** yamamoto has joined #openstack-meeting-514:53
*** d|k has joined #openstack-meeting-515:00
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Feb 20 15:00:11 2018 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
mattmceuen#topic Rollcall15:00
*** openstack changes topic to "Rollcall (Meeting topic: openstack-helm)"15:00
d|khihi!15:00
mattmceuenAgenda:  https://etherpad.openstack.org/p/openstack-helm-meeting-2018-02-2015:00
mattmceuenGM d|k !15:00
mattmceuenPlease add anything you'd like to discuss today to the agenda15:01
jayahno/15:01
mattmceuenhey jayahn!15:02
jayahnhey15:02
*** raymaika has joined #openstack-meeting-515:02
mattmceuenWe are missing some of the usual suspects, let me run around and throw things at some of them15:02
* srwilkers is a missing usual suspect15:03
srwilkerso/15:03
srwilkerscan confirm, mattmceuen throws things15:03
mattmceuenok here we go15:04
d|kif you're missing 'em, try leading the target with your throw.15:04
*** lamt` has joined #openstack-meeting-515:04
jayahntell them I even left in the middle of "drinking party" because of this meeting.15:04
alanmeadowso/15:05
mattmceuenoh man - jayahn why even leave15:05
jayahnfor irc meeting!!15:05
jayahn(officially)15:05
mattmceuenmultitasking : D15:05
mattmceuen#topic Ratify Mascot-Elect Ratel15:05
*** openstack changes topic to "Ratify Mascot-Elect Ratel (Meeting topic: openstack-helm)"15:05
icolwello/15:06
mattmceuentopic says it all - the Ratel has dominated the polls.  Ratified?15:06
mattmceuenrather, any challenges?15:06
lamt`o/15:07
jayahngoing once15:07
jayahngoing twice15:07
mattmceuendone.15:07
d|kbadgerified.15:07
mattmceuenmore done.15:07
mattmceuenbadgerified.15:07
mattmceuenThanks guys - I can't wait to see the stickers :)15:07
mattmceuenLet me get this next topic out of the way quick15:08
mattmceuen#topic PTG15:08
*** openstack changes topic to "PTG (Meeting topic: openstack-helm)"15:08
portdirecto/15:08
mattmceuenHere's the etherpad agenda for out PTG sessions -- https://etherpad.openstack.org/p/openstack-helm-ptg-rocky15:08
mattmceuenReminder to get anything we want to discuss in person on the etherpad15:08
mattmceuenAlso, team photo will be at 11:40 on Thursday15:08
mattmceuenso we can get lunch right after!15:09
portdirect:(15:09
srwilkersportdirect: :(15:09
srwilkersi will be sure to take a rather large copy of the unicorn picture to hold up with us15:09
srwilkersso you'll still be part of the picture15:09
portdirect"i believe"15:10
mattmceuenI vote we put portdirect's face on the unicorn15:10
mattmceuenI'm leaning toward skipping team meeting next week due to PTG, any objections?15:10
jayahnthen let's make it happen. just need large copy of the unicorn picture?15:10
jayahnno objection15:11
mattmceuenCool beans.  portdirect will be representing us at the Helm Summit this week, so he'll have to get a team picture of just him and a bunch of unicorns.15:11
mattmceuen#topic Full values YAML ordering example15:12
*** openstack changes topic to "Full values YAML ordering example (Meeting topic: openstack-helm)"15:12
mattmceuenThanks for putting this together srwilkers15:12
mattmceuen    https://review.openstack.org/#/c/543991/ prometheus as example15:12
mattmceuenLet us take a moment to observe the YAML in the wild15:12
srwilkersno problem -- there are a few instances where i see full ordering potentially being an issue15:12
srwilkersparticularly in cases where we define configuration files in the values.yaml when the configuration entries are expected to be in specific order15:13
srwilkersservices like prometheus, fluentd, and fluentbit being the obvious examples15:13
srwilkersgrafana too15:13
portdirecturg15:13
portdirectbad applications.15:14
portdirectI think the best 1st step would be to neaten up the yaml15:14
portdirectline 686 makes me so sad15:14
mattmceuenI won't lie it's a little ugly15:15
srwilkersyeah, it's not pretty15:15
srwilkersbut it's much better than when rules were defined in gotpl instead of yaml15:16
mattmceuenRight off the bat, dependencies and conditional_dependencies are far apart15:16
srwilkersive been working to make the prometheus rules more granular and neaten them up a little bit separately15:16
srwilkersbut that's a separate issue than addressing this15:16
portdirectI'll have a look at the deps15:16
d|kone (probably totally minor) issue i have with this is that it seems nice to me to have images: at the very start of the values file.  i dunno if i can make an argument beyond aesthetics for that.15:16
portdirectas id like to expand that - as we support more nova/cinder/neutron backends15:16
portdirectanother approach would be to write a spec15:17
portdirectfor the layout15:17
portdirectas i though this would be the simplest way15:17
srwilkersi think a spec might be the right approach here, and to agree to something we then enforce15:17
portdirectbut i wonder if the spec apprach may have merrit?15:17
srwilkersim leaning yes15:17
d|ki like that.  if not a spec, at least a style guide.15:17
jayahnim also leaning yes15:18
mattmceuenYeah, or a spec moving to a style guide even15:18
srwilkersas i started to be unhappy with the result halfway through working on prometheus's values15:18
portdirectjayahn: would one of your team be able to take this on?15:18
*** seaneagan has joined #openstack-meeting-515:18
jayahngood question (meaning I need some time to think)15:18
jayahnif it can happen after ptg, yes15:19
mattmceuenLet's discuss approaches at the PTG, at this point I think spec will be a mechanism to discuss different approaches to standard style.15:19
mattmceuenIf we can keep talking about it, maybe we can get more direction for the spec first, agree?15:19
*** STelkamp has joined #openstack-meeting-515:20
srwilkersworks for me15:20
mattmceuencool15:20
*** gagehugo has joined #openstack-meeting-515:21
mattmceuen#topic PS needing eyes and reviews15:21
*** openstack changes topic to "PS needing eyes and reviews (Meeting topic: openstack-helm)"15:21
mattmceuenWhat we got!15:21
jayahnjust rebased it to resolve merge conflict15:22
jayahnsrwilkers gave +2 before :)15:22
mattmceuenthanks srwilkers!15:22
jayahnhttps://review.openstack.org/#/c/538419/ >> Add template for Fluent logging index15:22
srwilkersnp15:22
*** slaweq has quit IRC15:23
jayahnsrwilkers: thanks for quickly review another one on updating fluent-bit version15:23
*** slaweq has joined #openstack-meeting-515:24
srwilkersnot a problem15:24
mattmceuenAny other PS y'all have been waiting on revies for, or recent ones we should get ahead of?15:25
portdirectI'll have one in today i hope for porting the image registry to osh15:26
srwilkershttps://review.openstack.org/#/c/546005/ this one should be quick15:26
portdirectand the one to abstract ingress rules finished15:26
portdirectalso over the next few days...15:27
portdirect...ocata gates15:27
jayahnyeah!!!15:27
mattmceuenBoom.15:27
jayahnocata gate15:27
portdirectwe will enter the victorian era15:27
mattmceuenLooking forward to those :)15:27
jayahnlet's start working on pike right away. :)15:27
mattmceuenhaha15:27
mattmceuenwe will get there sooner than later15:28
portdirectjayahn: we will be :)15:28
portdirectonce this is finished: https://review.openstack.org/#/c/545599/15:28
portdirectI's like to do that15:28
*** slaweq has quit IRC15:28
portdirectthen add gates that migrate from n-1 to 115:28
mattmceuenAny other PS before we move on?15:29
jayahnhyunsun is eager to have ocata to remove WIP from her two PS15:29
mattmceuenHer changes are compatible with newton, right?15:29
mattmceuenwe'll still want our version 1.0 to be compatible with Newton & Ocata per what we've discussed in the past (which is something to discuss further on PTG agenda)15:30
jayahnas long as i know, nope15:30
jayahni was going to tell that last time. there are things in ocata that not in newton.15:30
mattmceuenSure - it's ok not to take advantage of Ocata features in Newton15:31
mattmceuenBut we want the same OSH code base to support Ocata and Newton, even if it involves overriding certain manifests to not get rendered15:32
mattmceuenWhen we add Ocata gates, we'll still have the Newton gates ensuring Newton functionality15:32
mattmceuenCan you check w/ hyunsun and double check on whether the PS as is would support that?15:33
portdirectif not - I can draft a spec for how to handle these cases15:34
srwilkersI think a spec would be good so we can ratify a single approach for handling these things15:34
jayahnhttps://review.openstack.org/#/c/522162/15:35
jayahnhttps://review.openstack.org/#/c/545743/15:35
mattmceuen+1 on a spec15:36
mattmceuenties into defining and communicating our versioning strategy -- i.e. how developers contribute into it right15:36
*** STelkamp has quit IRC15:37
mattmceuenOk last thing -- jayahn added some good and detailed thoughts on improving team collab across time zones15:38
jayahnwe don't have versioning strategy yet. so, do you propose making spec doc on defining versioning strategy?15:38
mattmceuen#topic Future Topics15:38
*** openstack changes topic to "Future Topics (Meeting topic: openstack-helm)"15:38
mattmceuenjayahn, do we want to discuss that now, or shall we all look @ it, chew on it, and discuss next time?15:38
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-meeting-2018-02-2015:38
jayahnchew it and discuss on ptg.15:38
mattmceuenSounds like a plan :)15:38
portdirectI can make a draft spec for us to chew in dublin15:39
jayahnbut, basically, i start to have concern on this stuff15:39
jayahnand imo, it needs to be discussed, agreed, and resolved15:39
jayahnto make osh better community.15:39
portdirect++15:39
mattmceuenyes, agree 100%15:40
mattmceuenthanks for bringing it up jayahn15:40
mattmceuen#topic Roundtable discussion15:41
*** openstack changes topic to "Roundtable discussion (Meeting topic: openstack-helm)"15:41
mattmceuenAnything else we'd like to discuss this time team?15:41
mattmceuengoing once :)15:42
mattmceuengoing twice15:42
jayahnin skt, we are getting a commit per an hour, and deploy the entire openstack, and test it against our value overrides. After this test passed, we merge that commit into our repo. that gives us to chance each single change from upstream15:42
jayahnah..15:42
jayahntwice15:42
mattmceuenwe didn't make it to three, you're good15:42
jayahnif it fails test, we have a chnace to see what exact commit is breaking us. even jira ticket is automattically generated. :)15:42
mattmceuenthat's awesome15:43
mattmceuennice15:43
jayahnthat give us good chance to read changes, and we often get ideas from that on what is happening on upstream15:43
jayahnbut, this "getting know what is happening" should be done in upstream community very well.15:43
jayahnthat probably requires both att and skt, and other participants of this community look back how we work, and examine it, and improve it.15:44
jayahn(am i making sence?)15:44
jayahnthat is all :)15:45
mattmceuenYes, it does15:45
mattmceuenthat is a good topic to dig into15:45
mattmceuenThe CI is cool on its own though :)15:45
mattmceuenThanks jay15:45
mattmceuenalright guys, with that - we get 15 minutes back!  Jayahn, go back to your party15:46
jayahnno problem15:46
srwilkersits helpful, but it's hard to really diagnose these sorts of issues if what we're running in the gate differs significantly from the stuff you're running i think15:46
srwilkersespecially if the versions are different15:46
jayahnnope. my party is 40 min away from here.15:46
srwilkersbut definitely think we should discuss this more in dublin15:46
portdirectAgree15:46
portdirectI think the most prudent way to resolve any delta would be to add a third party gate15:46
portdirectunless the run time is too long15:47
portdirectand it would be great to get some more reviews/contributions from parties using osh :)15:47
srwilkersi think a third party gate would help immensely15:47
mattmceuenThanks everyone -- see some of you at the PTG!15:48
mattmceuen#endmeeting15:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:48
openstackMeeting ended Tue Feb 20 15:48:38 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-02-20-15.00.html15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-02-20-15.00.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-02-20-15.00.log.html15:48
*** d|k has left #openstack-meeting-515:49
*** STelkamp has joined #openstack-meeting-515:53
*** slaweq has joined #openstack-meeting-516:03
*** raymaika has quit IRC16:03
*** gagehugo has left #openstack-meeting-516:04
*** lamt` has quit IRC16:05
*** lamt` has joined #openstack-meeting-516:06
*** yamahata has joined #openstack-meeting-516:15
*** slaweq_ has joined #openstack-meeting-516:25
*** slaweq_ has quit IRC16:30
*** yamamoto has quit IRC16:38
*** yamamoto has joined #openstack-meeting-516:45
*** yamamoto has quit IRC16:50
*** yamamoto has joined #openstack-meeting-516:55
*** yamamoto has quit IRC16:59
*** slaweq has quit IRC17:03
*** slaweq has joined #openstack-meeting-517:34
*** slaweq has quit IRC17:39
*** derekh has quit IRC17:42
*** iyamahat has joined #openstack-meeting-517:49
*** sshank has joined #openstack-meeting-517:50
*** iyamahat has quit IRC17:51
*** slaweq has joined #openstack-meeting-517:52
*** yamamoto has joined #openstack-meeting-517:55
*** slaweq has quit IRC17:57
*** lamt_ has joined #openstack-meeting-517:58
*** lamt` has quit IRC17:58
*** yamamoto has quit IRC18:01
*** lamt_ has quit IRC18:06
*** lamt_ has joined #openstack-meeting-518:14
*** slaweq has joined #openstack-meeting-518:18
*** slaweq has quit IRC18:23
*** lamt_ has quit IRC18:24
*** lamt_ has joined #openstack-meeting-518:34
*** sshank has quit IRC18:42
*** sshank has joined #openstack-meeting-518:42
*** STelkamp has quit IRC18:55
*** Rockyg has joined #openstack-meeting-518:56
*** felipemonteiro has joined #openstack-meeting-518:57
*** yamamoto has joined #openstack-meeting-518:57
*** yamamoto has quit IRC19:02
*** Rockyg has quit IRC19:08
*** felipemonteiro has quit IRC19:14
*** STelkamp has joined #openstack-meeting-519:14
*** mjturek has quit IRC19:15
*** mjturek has joined #openstack-meeting-519:17
*** felipemonteiro has joined #openstack-meeting-519:28
*** slaweq has joined #openstack-meeting-519:31
*** slaweq_ has joined #openstack-meeting-519:34
*** yamahata has quit IRC19:35
*** slaweq has quit IRC19:36
*** slaweq_ has quit IRC19:43
*** sshank has quit IRC19:53
*** yamamoto has joined #openstack-meeting-519:58
*** mjturek has quit IRC20:00
*** yamamoto has quit IRC20:02
*** slaweq has joined #openstack-meeting-520:10
*** yamahata has joined #openstack-meeting-520:11
*** slaweq has quit IRC20:14
*** seaneagan has quit IRC20:14
*** slaweq has joined #openstack-meeting-520:22
*** lamt__ has joined #openstack-meeting-520:24
*** lamt_ has quit IRC20:24
*** lamt__ is now known as Guest431420:24
*** felipemonteiro_ has joined #openstack-meeting-520:53
*** felipemonteiro has quit IRC20:56
*** yamamoto has joined #openstack-meeting-520:59
*** Guest4314 has quit IRC21:03
*** Guest4314 has joined #openstack-meeting-521:03
*** yamamoto has quit IRC21:03
*** felipemonteiro_ has quit IRC21:04
*** felipemonteiro has joined #openstack-meeting-521:05
*** felipemonteiro_ has joined #openstack-meeting-521:07
*** felipemonteiro has quit IRC21:09
*** sshank has joined #openstack-meeting-521:27
*** slaweq_ has joined #openstack-meeting-521:52
*** slaweq_ has quit IRC21:57
*** yamamoto has joined #openstack-meeting-522:00
*** yamamoto has quit IRC22:04
*** STelkamp has quit IRC22:23
*** sshank has quit IRC22:41
*** Guest4314 has quit IRC22:53
*** Guest4314 has joined #openstack-meeting-522:53
*** felipemonteiro_ has quit IRC22:57
*** slaweq has quit IRC23:00
*** slaweq has joined #openstack-meeting-523:00
*** yamamoto has joined #openstack-meeting-523:00
*** slaweq has quit IRC23:06
*** yamamoto has quit IRC23:06

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