Tuesday, 2018-07-17

*** mjturek|off has quit IRC00:18
*** yamahata has quit IRC01:54
*** roman_g has quit IRC01:55
*** iyamahat_ has quit IRC01:56
*** ricolin has joined #openstack-meeting-502:24
*** jgu has joined #openstack-meeting-504:02
*** jgu has quit IRC06:03
*** skazi has joined #openstack-meeting-506:09
*** yamamoto has joined #openstack-meeting-507:02
*** yamahata has joined #openstack-meeting-507:53
*** derekh has joined #openstack-meeting-507:55
*** skazi has quit IRC08:04
*** iyamahat has joined #openstack-meeting-508:05
*** iyamahat has quit IRC08:09
*** roman_g has joined #openstack-meeting-508:16
*** yamahata has quit IRC08:40
*** skazi has joined #openstack-meeting-508:58
*** derekh has quit IRC09:17
*** derekh has joined #openstack-meeting-509:17
*** yamamoto has quit IRC09:37
*** skazi has quit IRC09:42
*** skazi has joined #openstack-meeting-509:54
*** derekh has quit IRC11:22
*** skazi has quit IRC11:23
*** skazi has joined #openstack-meeting-511:24
*** skazi has quit IRC11:48
*** skazi has joined #openstack-meeting-511:50
*** roman_g has quit IRC12:05
*** roman_g has joined #openstack-meeting-512:05
*** skazi has quit IRC13:07
*** skazi has joined #openstack-meeting-513:20
*** mjturek has joined #openstack-meeting-513:33
*** annp_ has joined #openstack-meeting-513:42
*** hongbin has joined #openstack-meeting-514:00
*** jgu has joined #openstack-meeting-514:12
*** jgu_ has joined #openstack-meeting-514:14
*** jgu has quit IRC14:18
*** ricolin has quit IRC14:19
*** ricolin has joined #openstack-meeting-514:20
*** skazi has quit IRC14:21
*** piotrrrr has joined #openstack-meeting-514:36
*** mjturek_ has joined #openstack-meeting-514:38
*** mjturek has quit IRC14:39
*** ricolin has quit IRC14:42
*** gagehugo has joined #openstack-meeting-514:44
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Jul 17 15:00:15 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
mattmceuen#topic Rollcall15: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
*** openstack changes topic to "Rollcall (Meeting topic: openstack-helm)"15:00
mattmceuengood time-of-day, everybody15:00
portdirectmerry Christmas!15:00
jayahno/15:01
mattmceuenHere's our agenda for today, please add in anything additional you'd like to discuss!  https://etherpad.openstack.org/p/openstack-helm-meeting-2018-07-1715:01
jayahn? christmas?15:01
*** annp_ has quit IRC15:01
mattmceuenwishful thinking - it is hot in saint louis15:01
portdirecti celebrate Christmas every day of the year.15:01
portdirectits why im so jolly15:01
mattmceuenI will be expecting my present portdirect15:01
jayahni rather want to celebrate christmas eve everyday..15:01
*** gmmaha has joined #openstack-meeting-515:01
*** gema has joined #openstack-meeting-515:01
portdirectfair15:02
gemao/15:02
gmmahao/15:02
*** robertchoi80 has joined #openstack-meeting-515:02
jayahnso that i can get a gift from santa everyday. :)15:02
robertchoi80hi15:02
tdoctime appropriate greetings15:02
portdirectoh - in usa/uk its christmas day you get that15:02
jayahnthat is true. early in the morning..15:02
jayahnmy mistake..15:02
mattmceuenI still haven't figured out exactly what time santa comes down the chimney, I have a hard time staying awake15:03
mattmceuenjayahn could do it15:03
mattmceuen#topic Follow-up on Rally test gating15:03
*** openstack changes topic to "Follow-up on Rally test gating (Meeting topic: openstack-helm)"15:03
mattmceuen https://review.openstack.org/#/c/582463/15:03
jayahndoes US government tracks santa every year?15:03
jayahnah.. rally one.15:03
jayahnrobertchoi80 will do.15:03
mattmceuen^this guy -- big thanks to Jaesang on that15:03
mattmceuenIt's high on my list to give this a spin15:04
robertchoi80sounds good15:04
robertchoi80so, do you agree that we need a separate rally test on gate?15:04
portdirecti would move to experimntal15:05
portdirectjust as we have doen with tempest15:05
jayahnwe would like to ask. what would be difference between "rally test in each chart" vs. "rally test with a seperate chart like https://review.openstack.org/#/c/582463/.15:05
portdirectas otherwise i fear most failures will be oom15:05
portdirecteg: http://logs.openstack.org/63/582463/5/check/openstack-helm-armada-fullstack-deploy/860eb5f/job-output.txt.gz#_2018-07-16_00_07_15_41945215:05
portdirectjayahn: i think "rally test in each chart" would be better phased as "helm test on each chart"15:06
*** wxy| has joined #openstack-meeting-515:06
jayahnyes, correct15:06
portdirectit just happens that most helm tests are implemented via rally15:06
mattmceuendo we expect rally to use as much memory as tempest?15:06
jayahnture as well15:06
jayahntrue..15:06
portdirectso - helm test should be used (as per spec) to test basic chart functionaility15:06
portdirecti see great value in adding a rally test on the deployment15:07
portdirectas it can test the deployment as a whole15:07
robertchoi80that's true15:07
portdirectwhereas we keep the helm tests limited to a tool that DE's and OPs can run in prod sites to perform a quick sanity check on the service15:07
jayahnagreed. we can do more thorough test, but you said that you rather have a simple sanity check  for the deployment.15:07
portdirect(oh and Devs as well!)15:07
jayahnfor ops, we are planning to provide more thorough testing via rally. but I am curious we need that level of test on gating.15:08
robertchoi80ah, I guess the "simple sanity check" meant 'helm test'15:09
portdirectyup15:09
mattmceuenI like running as much testing as frequently as we can w/o getting in the way15:11
mattmceuenDo you know how much time the rally testing adds to the armada gate?15:11
robertchoi80that will depends on the number of rally test case.15:11
rwellumo/ (late - sorry)15:11
robertchoi80I should ask to Jaesang15:12
robertchoi80the current number of test cases for that rally chart isn't that large, and we can increase the number15:12
mattmceuencool - would be great to do it frequently.  But agree that until we can run it reliably in openstack infra it should be experimental15:13
robertchoi80that's totally fine15:13
jayahnno problem there15:13
mattmceuenrobertchoi80 also brought up this PS:  https://review.openstack.org/#/c/582338/15:14
mattmceuenThat's a good one to be aware of15:14
mattmceuenArmada is close to running "helm test" by default, as that's a best practice15:14
robertchoi80yes. that PS looks good to me15:15
mattmceuenSince Armada can't tell whether a chart supports helm test ahead of time, this means we'll need to turn -off- helm tests for charts that don't support it15:15
mattmceuen(explicitly)15:15
marshallmargenaunot quite!15:15
mattmceuenoho!15:15
marshallmargenauif there is no helm test, armada will still pass it15:15
mattmceuenwell that's great!15:15
marshallmargenauit reports back "No Tests Found" i believe, from tiller15:15
marshallmargenauyou will need to explicitly disable any helm tests that are not working15:15
robertchoi80yes, that's right15:16
mattmceuenI've never been so happy to be so wrong.  Thanks marshallmargenau :)15:16
marshallmargenauone more there's a semi-related change that folks may be interested in with https://review.openstack.org/#/c/581944/ (merged)15:16
marshallmargenauyou can now apply your wait labels without a timeout, which will fall into standard chartgroup processing flow15:17
robertchoi80thanks, I'll take a look15:18
marshallmargenaui.e. chartgroups will still wait until everything is happy, so they can use your labels now instead of just the namespace (from before this PS)15:18
mattmceuenthat's excellent15:18
mattmceuenrobertchoi80 anything else you'd like to chat about on this topic?15:19
portdirectmarshallmargenau / robertchoi80 : would you guys be able to update the osh manifests to take advantage of this feature?15:19
portdirectwould be awesome to get in the gates15:20
robertchoi80ah, sure. I'll tell Jaesang to do that :)15:21
mattmceuenhaha15:21
jayahnrobertchoi80 is becoming like me..... :(15:21
robertchoi80haha15:21
mattmceuenthanks robertchoi80 (and Jaesang in advance.....) love to take advantage of the lates armada features15:21
mattmceuenAlright - moving on!15:22
mattmceuen#topic Glance backing storage15:22
*** openstack changes topic to "Glance backing storage (Meeting topic: openstack-helm)"15:22
jayahnJaesang is getting married this satureday. probably will take some time to do that. :)15:22
mattmceuenpiotrrrr says: glance/deployment-api.yaml supports 'pvc' and 'rbd' storage out of the box. Do we want to add support for hostPath? This will allow for using host-mounted networked storage for storing glance images, e.g. GPFS.15:23
mattmceuenOH my!!!15:23
mattmceuenwe could give Jaesang a little time off I suppose -- please tell him Congrats!!!15:23
jayahnI will do. thanks. :)15:23
robertchoi80let's move on15:24
mattmceuenfor host-mounted network storage being used to back glance (rather than pvc or rbd) -- can that be done using a pvc driver for the networked storage?15:24
piotrrrrif you have a GPFS pvc driver, in theory yes, but (1) i don't think there is one (2) to take the advantage from copy-on-write in GPFS between glance and cinder you want your images to be stored in a well known location in your GPFS15:26
piotrrrras cinder's GPFS drivers needs to be then told where to look for those images15:26
piotrrrrand ofcourse GPFS is only on of the usecase, there's probably other networked storage solution which do not have pvc driver. Having a hostPath support as a fallback would potentially cover all of them15:27
mattmceuenI'm not against this.  One thought, though - would it be effort well-spent to add additional, well-behaved pvc drivers for things like GPFS?15:28
portdirectpiotrrrr: why not just use a local pv type?15:28
portdirectthere should be a provisioner for that i think15:29
portdirecthttps://github.com/kubernetes-incubator/external-storage/tree/master/local-volume15:29
piotrrrrmattmceuen: personally I wouldn't know where to start with that. But also, and I wouldn't be able to say now if it would allow cinder's GPFS driver (talking directly to GPFS) to take the advantage of copy-on-write.15:30
piotrrrrportdirect: I can't say I know much about the local persistent volumes. But again, my first concern would be possible lack of copy-on-write from glance to cinder. I might be wrong here though15:32
portdirectits just a awy of using the pv/pvc interface to get local bindmounts15:33
portdirecthas the advantage of knowing which nodes can have the pod scheduled on it15:33
portdirectand would also work with the current glance chart15:34
piotrrrrI can look into that. though if the PVs land under different directories, then it might not work for copy-on-write (where, i suspect, all images have to be in a fixed directory)15:34
portdirectby simply using the "pvc" backend, and specifiying the lass to match the local provisioner15:34
portdirectroger15:34
portdirects/lass/class15:34
mattmceuenAwesome.  Please bring it back up piotrrrr if that doesn't fit the bill for your copy-on-write use case15:35
piotrrrrWill do, thanks.15:35
mattmceuen#topic Supporting multiple versions of OpenStack15:35
*** openstack changes topic to "Supporting multiple versions of OpenStack (Meeting topic: openstack-helm)"15:35
tdocAs a short side question, what's the status of COW between glance and cinder with Ceph?15:35
tdoc(if anyone happens to know, otherwise let's move on)15:36
mattmceuenSorry I'm not sure tdoc - I'll add to the agenda as a topic for next time :)15:37
mattmceuenand we can try to figure it out by then...15:37
portdirecttdoc: if using rbd15:37
portdirectthen works as expected15:37
tdocok, thanks15:38
mattmceuen#topic Supporting multiple versions of OpenStack15:38
*** openstack changes topic to "Supporting multiple versions of OpenStack (Meeting topic: openstack-helm)"15:38
mattmceuenpiotrrrr poses: How will OSH handle supporting deployment of multiple different versions of openstack? values.yaml will differ between Newton and Rocky. E.g. no need to write out content of policy.json15:38
piotrrrrYeah, so basically I'm curious what's are the plans here.15:39
rwellum+2 piotrrrr15:39
mattmceuenFirst thing to be aware of -- release-specific reference overrides live here: https://github.com/openstack/openstack-helm/tree/master/tools/overrides/releases15:39
portdirectthese need to be expanded to include the default deltas that piotrrrr points out15:39
portdirectbut we currently gate on 3 releases of openstack15:39
portdirectwith miniumum common settings between them15:40
mattmceuenWould the policy.jasn get in the way?  Or just get ignored?15:40
mattmceuen(in Rocky)15:40
portdirectno15:40
portdirectrocky prob marks the point we need to move to osh 1.115:40
portdirectthings like that mean our current charts work newton - queens15:40
rwellumThat link drives images versions - what drives behavior differences? Like cells etc.15:41
portdirectbut i think will break beyond that15:41
mattmceuenwhat a segueway to our next topic15:41
portdirectrwellum: cells is a great example15:41
portdirect2 sec15:41
*** yamahata has joined #openstack-meeting-515:41
jayahnso it will be 1.1? not 2.0? .. any rules on versioning?15:41
*** felipemonteiro has joined #openstack-meeting-515:41
piotrrrrI see, so to rephrase: the plan is to have values.yaml have the values for lowest supported version of OS, and then maintain overrides for higher versions, and/or different types of deployments which apply the deltas needed, correct?15:41
portdirecthttps://github.com/openstack/openstack-helm/blob/master/nova/templates/bin/_db-sync.sh.tpl#L21-L4715:42
portdirectjayahn: the final spec is being worked on, along with the one for values over-rides15:42
portdirectand layout15:42
portdirectpiotrrrr: essentially yes15:43
portdirect:)15:43
piotrrrrportdirect: ok, so overrides plus some version specific if/else in various scripts15:43
portdirectyeah - we need to work out the max number of if/else we are prepared to go15:43
piotrrrrok, so maybe one last followup question, status of Queens overrides?15:44
portdirectstill in flight15:44
portdirectI hope to have the final ps up today15:44
mattmceuenthanks portdirect15:44
piotrrrrcool, thanks guys, that answers my questions here15:44
mattmceuenexcellent15:45
jayahnthanks portdirect. :)15:45
rwellumQueens and Master?15:45
mattmceuenOne more thing to add re: 1.0 readiness -- reminder that we have a TODO list for 1.0 readiness:  https://storyboard.openstack.org/#!/worklist/34115:45
mattmceuenLots of open items on that list, and it would be really great if folks could volunteer for some more of them!15:46
jayahnthat clears my question on "current status of osh release)15:46
mattmceuenpiotrrrr - I think the rest of your q's in the agenda are all tied up in the in-flight versioning spec; anything else you want to bring up in that area before we move on?15:47
piotrrrrI'm good, let's move on15:47
mattmceuencool15:47
mattmceuen#topic Source code copyright attribution15:47
*** openstack changes topic to "Source code copyright attribution (Meeting topic: openstack-helm)"15:47
jayahnbefore that..15:48
mattmceuenfloor is yours jayahn15:48
jayahnwe consider osh master branch as "stable"?15:48
mattmceuenthe goal of the 1.0 release is to get a stable interface for OSH15:48
jayahnthat was a quesiton from our ops team. they want to know what is policy of characterizing a branch.15:48
piotrrrr(sidenote: the "Questions, Clarification, and Current Status of osh release" was somebody else's topic, the color did not get preserved when I created the new etherpad)15:48
mattmceuenSo some things may change till then15:48
jayahnpiotrrrr: that is mine15:49
mattmceuenoops, sorry jayahn :)15:49
jayahnno problem. :)15:49
*** ricolin has joined #openstack-meeting-515:49
jayahnops team is confusing on the concept of master branch on osh.15:50
mattmceuenI would say we'll only change things in the OSH interface if it will add value (not arbitrarily) until we reach 1.0, but things may continue to change till 1.015:50
jayahnthey simply asked "is everyhing on master branch considered as stable once there is release 1.015:50
jayahnand.. just one quick check, osh version will cover multiple charts as portdirect described just before, but we will tag based on openstack version?15:51
jayahnoops will cover multiple openstack version..15:52
mattmceuenI am dusting off my memory on Dublin discussion - I believe this will be addressed by portdirect's spec as well - but I think we will be tagging master along the way with recommended stable markers, e.g. 1.1, 1.215:52
portdirectare you deploying to prod straight from usptream with no gate/internal repo?15:52
mattmceuenportdirect correct me if I'm remembering wrong15:52
portdirectmattmceuen: correct15:53
portdirectand those tags 1.1, 1.2 etc will correspond with a range of openstack versions15:54
jayahnportdirect: nope. we are not deploying to prod straight from upstream.15:54
mattmceuenanything else on this one jayahn?15:54
jayahni have a slight different memory on tagging policy. but it is okay for now15:55
jayahnI will dig up my memory again to make sure..15:55
mattmceuensounds like a plan15:55
mattmceuen#topic Source code copyright attribute15:55
*** openstack changes topic to "Source code copyright attribute (Meeting topic: openstack-helm)"15:55
mattmceuen^attribution15:55
mattmceuenAs discussed in OSH meeting a while back: http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-03-20-15.00.log.html#l-10115:55
mattmceuenWe're planning on replacing the "OpenStack-Helm Authors" copyright attribution with the "OpenStack Foundation", as the latter is a legal entity and the former isn't15:56
mattmceuenHeads up that I'm planning to put in PS this week unless that gives anyone heartburn -- lots of small changes to many files :)15:56
mattmceuenIf so -- please bring it up in the #openstack-helm channel today15:57
mattmceuen#topic Patchsets needing review15:57
*** openstack changes topic to "Patchsets needing review (Meeting topic: openstack-helm)"15:57
mattmceuen    Add ceph configuration for cinder-backup - https://review.openstack.org/#/c/574146/15:57
mattmceuen    Add sla check in rally task - https://review.openstack.org/#/c/580286/15:57
mattmceuen    Add rally test gate - https://review.openstack.org/#/c/582463/15:57
mattmceuen    Nova: add live_migration_interface option - https://review.openstack.org/#/c/577349/15:57
mattmceuen    [ingress] introduce keepalived sidecar for ingress vip - https://review.openstack.org/#/c/577353/15:57
mattmceuenLet's please get some reviews on these guys this week^^^ !15:58
mattmceuenI'll post them in the team channel as well15:58
mattmceuenwith one minute left -- any closing thoughts guys?15:58
roman_gSummit talks?15:58
mattmceuenLAST DAY FOR SUBMITTING SUMMIT TALKS15:59
jayahnah.. right. it ends today.15:59
mattmceuenthanks roman_g that's a good one :)15:59
roman_greminder to you to talk to Jared15:59
roman_gmattmceuen:15:59
mattmceuenAppreciate all your work and insight guys -- have a great week and see you in #openstack-helm15:59
mattmceuen#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Tue Jul 17 15:59:43 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-07-17-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-07-17-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2018/openstack_helm.2018-07-17-15.00.log.html15:59
*** gmmaha has left #openstack-meeting-515:59
roman_gAny one has submitted talks?15:59
*** gagehugo has left #openstack-meeting-516:00
*** piotrrrr has quit IRC16:04
*** robertchoi80 has quit IRC16:11
*** wxy| has quit IRC17:11
*** ricolin has quit IRC17:14
*** felipemonteiro_ has joined #openstack-meeting-517:26
*** felipemonteiro has quit IRC17:30
*** spiette has quit IRC17:53
*** spiette has joined #openstack-meeting-517:58
*** ianychoi has quit IRC18:14
*** yamahata has quit IRC18:15
*** jgu_ has quit IRC18:35
*** yamahata has joined #openstack-meeting-518:47
*** jgu has joined #openstack-meeting-519:05
*** jgu has quit IRC19:39
*** jgu has joined #openstack-meeting-519:40
*** jgu has quit IRC19:44
*** jgu has joined #openstack-meeting-520:01
*** mjturek_ has quit IRC20:55
*** felipemonteiro_ has quit IRC21:27
*** slaweq has quit IRC21:34
*** slaweq has joined #openstack-meeting-522:11
*** slaweq has quit IRC22:16
*** jgu has quit IRC22:56
*** slaweq has joined #openstack-meeting-523:11
*** slaweq has quit IRC23:16

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