Tuesday, 2017-05-23

*** gardlt has quit IRC00:07
*** zenirc369 has joined #openstack-meeting-500:07
*** marst_ has quit IRC00:09
*** felipemonteiro has quit IRC00:13
*** zenirc369 has quit IRC01:45
*** lamt has joined #openstack-meeting-501:57
*** zenirc369 has joined #openstack-meeting-502:23
*** ricolin has joined #openstack-meeting-502:31
*** lamt has quit IRC02:49
*** lamt has joined #openstack-meeting-502:56
*** zenirc369 has quit IRC03:10
*** lamt has quit IRC03:41
*** lamt has joined #openstack-meeting-503:46
*** LanceHaig has joined #openstack-meeting-504:35
*** marst_ has joined #openstack-meeting-504:49
*** zenirc369 has joined #openstack-meeting-505:17
*** LanceHaig has quit IRC05:21
*** LanceHaig has joined #openstack-meeting-505:53
*** rarcea has joined #openstack-meeting-505:57
*** zenirc369 has quit IRC06:04
*** JawonChoo has joined #openstack-meeting-506:04
*** zenirc369 has joined #openstack-meeting-506:16
*** rarcea has quit IRC06:20
*** rarcea has joined #openstack-meeting-506:33
*** lamt has quit IRC06:48
*** matrohon has joined #openstack-meeting-506:57
*** ralonsoh has joined #openstack-meeting-507:53
*** derekh has joined #openstack-meeting-508:36
*** aarefiev_afk is now known as aarefiev09:04
*** lamt has joined #openstack-meeting-510:25
*** lamt has quit IRC10:25
*** lamt has joined #openstack-meeting-510:40
*** ralonsoh_ has joined #openstack-meeting-511:32
*** ralonsoh_ has quit IRC11:32
*** lamt has quit IRC12:18
*** lamt has joined #openstack-meeting-512:59
*** zenirc369 has quit IRC13:00
*** lamt has quit IRC13:04
*** lamt has joined #openstack-meeting-513:04
*** JawonChoo has quit IRC13:09
*** ralonsoh has quit IRC13:47
*** ralonsoh has joined #openstack-meeting-514:01
*** LanceHaig has quit IRC14:05
*** JawonChoo has joined #openstack-meeting-514:05
*** JawonChoo has quit IRC14:10
*** LanceHaig has joined #openstack-meeting-514:15
*** marst_ has quit IRC14:17
*** zhipeng has joined #openstack-meeting-514:22
*** marst_ has joined #openstack-meeting-514:23
*** SamYaple has joined #openstack-meeting-514:25
*** LanceHaig has quit IRC14:36
*** LanceHaig has joined #openstack-meeting-514:37
*** LanceHaig has quit IRC14:37
*** zhipeng has quit IRC14:40
*** alraddarla has joined #openstack-meeting-514:43
*** zhipeng has joined #openstack-meeting-514:45
*** leifmadsen has joined #openstack-meeting-514:51
*** srwilkers has joined #openstack-meeting-514:58
*** jaugustine has joined #openstack-meeting-515:00
*** korzen has joined #openstack-meeting-515:00
*** lrensing has joined #openstack-meeting-515:01
v1k0d3n#startmeeting openstack-helm15:01
openstackMeeting started Tue May 23 15:01:53 2017 UTC and is due to finish in 60 minutes.  The chair is v1k0d3n. 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:02
v1k0d3nwelcome team15:02
v1k0d3nhttps://etherpad.openstack.org/p/openstack-helm-meeting-2017-05-2315:02
jaugustineo/15:02
v1k0d3nor those of you who have some items you wish to add to theagenda, please add them.15:02
*** eanylin has joined #openstack-meeting-515:02
*** anticw has joined #openstack-meeting-515:02
portdirectಠ‿ಠ15:02
alraddarla0/15:03
alraddarlao/415:03
SamYapleo/15:03
alraddarlai give up15:03
*** zhipeng has quit IRC15:03
korzenhello15:03
lrensingo/15:03
duleko/15:03
v1k0d3nhey SamYaple good to have you15:03
*** gagehugo has joined #openstack-meeting-515:03
SamYapleim my own person15:03
alanmeadows\o/ STEVE HOLT.15:04
*** mattmceuen has joined #openstack-meeting-515:04
v1k0d3nok, sorry...just getting started.15:07
v1k0d3nmostly some checks on where we're at with bugs and long standing reviews.15:08
dulek1692834 - I've checked this on Helm 2.3, it's fine. But I guess it's good to have 2.4 issues listed, right?15:08
v1k0d3nunless people have other things that they want to add15:08
v1k0d3ndulek: https://bugs.launchpad.net/openstack-helm/+bug/1690863 ?15:09
openstackLaunchpad bug 1690863 in openstack-helm "Helm 2.4.0 Issues with Openstack-Helm" [High,New]15:09
v1k0d3nsure, it's general. maybe we should get more specific in that launchpad bug?15:09
dulekv1k0d3n: Yeah, but this isn't listing the issues at all.15:09
dulekI'm fine with closing my bug and expanding description of 1690863.15:09
*** mcnanci_ has joined #openstack-meeting-515:09
*** LanceHaig has joined #openstack-meeting-515:10
*** LanceHaig has joined #openstack-meeting-515:10
v1k0d3nthis was really a placeholder. i thought that some folks were working against this issue. i'm completely fine with more details, and however the team wants to address doing that is fine with me.15:10
v1k0d3ndo we want to close 1690863 in favor of more detailed helm 2.4 related bug issues?15:10
srwilkersyes15:10
v1k0d3n(assuming that's a bit better).15:10
*** renmak_ has joined #openstack-meeting-515:11
v1k0d3ncool. done. so srwilkers are you aware of other 2.4 issues that could open launchpad bugs against?15:11
v1k0d3nthe 1690863 was really just a place holder to let users know that 2.3 is still recommended.15:12
srwilkersnot that im aware of, but if there are any, id rather see a verbose description of bugs15:12
portdirectthe only one I'm aware of is the hard failure of gotpl rendering errors15:12
srwilkerslaunchpad bugs aren't really appropriate for pinning to a helm version15:12
srwilkersshould just be noted in the docs15:12
anticwi'm using 2.4 and wondering what the issue is15:12
v1k0d3nsure, as long as we can recommend to users that for now the recommendation is to use 2.3 until we're able to resolve and work against them.15:12
portdirectlack of ceph secrets in helm-toolkit15:13
portdirectanticw: ^^15:13
portdirectrenders fine if they are present15:13
v1k0d3nright. +1 related to ceph issues.15:13
srwilkers2.3 is noted in the all-in-one docs and the multinode, so we should be good15:13
v1k0d3n(in etherpad).15:13
v1k0d3nok, i'll close out the general 1690863. dulek can you mention using 2.3 in your issue until resolved?15:14
portdirectv1k0d3n: i dont think we should close out 1690863?15:15
v1k0d3nok15:15
dulekv1k0d3n: I've commented.15:15
v1k0d3nthanks dulek. next then.15:15
v1k0d3nare there really any other ceph issues than what's already been described? anticw i thought you may have run into issues, or was that only networking?15:16
v1k0d3n(my brain is all over the place atm)15:16
alanmeadowsportdirect: really its the entire conversion of the ceph chart to the modern way -- from ceph.conf templates, secrets, to dependency checking15:17
lrensing+1 alanmeadows15:17
v1k0d3ngood point alanmeadows. +115:17
*** LanceHaig has quit IRC15:17
portdirectalanmeadows: agreed (I think) though did you mean to direct that at me?15:18
portdirectI'm 100% on the same page that it needs redone, but thought somone else was on it15:18
alanmeadowsi volunteered anticw, but just mentioning for awareness to all, ceph issues more then just the helm 2.4 secrets15:19
portdirect:) yeah - in addition the the points you raise we should also have a set of snae defaults for diff size clusters15:19
portdirects/snae/sane15:20
anticwportdirect: oh, i have some stuffs there15:20
portdirectnice :)15:20
*** renmak_ has quit IRC15:21
anticwlonger-term we should split multinode to mutinode.rst and largescale.rst15:21
portdirect+115:21
v1k0d3nok, moving on. networking issues. i think anticw has been working some of these as well. SK has some interest as well.15:21
anticwbut we don't know what the latter should really look like except in an abstract sense15:21
alanmeadowsTo finish off your question, there is probably a long list of ceph issues, but I think many of them can simply be summed up with the fact that the first priority is modernizing the chart and bring it inline with the rest of openstack-helm--you can't override anything, you must set the proper environment variables before running sigil (huh), and you need to15:22
alanmeadowshave magic stuff in helm-toolkit/secrets15:22
portdirect(plug) I think we should explore using the way i did secret gen for the upstream chart?15:23
portdirecteg: https://github.com/ceph/ceph-docker/blob/master/examples/helm/ceph/templates/jobs/configmap.yaml15:24
portdirectwhich removes the req for having anything installed on the host15:24
anticwv1k0d3n: the 'networking issue' i think is the choice if IPs again in ceph.conf magics15:24
*** renmak_ has joined #openstack-meeting-515:24
alanmeadowsworth a look, sure -- I'm frankly happy with starting simple, because this is a pain point for many -- static 'secrets' defined in values.yaml might be the best place to start that advanced users can override15:25
v1k0d3n+1. most of the issues that i hear about are related to preparing the environment for ceph (in BM installations).15:26
v1k0d3neasing this would be a huge win.15:27
portdirectan alternate to condsider may be passing this off to a plugin - which is what i do for my personal lab: https://github.com/portdirect/marina#quckstart15:28
v1k0d3n@alanmeadows we have all of the items we want on the roadmap for ceph, right?15:28
v1k0d3nperhaps we can get these items in as individual blueprints to work against.15:28
alanmeadowsThis is the full issue list that was created: https://docs.google.com/document/d/1uY8U1DZgGa-IT40fYmqNlpLqUnWGC0_CbwH_n2n21Aw/edit?usp=sharing15:29
*** renmak_ has quit IRC15:29
alanmeadowsIt needs to likely work its way into blueprints15:29
v1k0d3nok. i will get with the right folks, and work on getting these in.15:30
v1k0d3nwe can move on.15:30
*** gardlt has joined #openstack-meeting-515:30
portdirectis jayahn about?15:30
* portdirect must be too late over that side of the big blue ball...15:31
portdirectkorzen did some great work putting together an etherpad: https://etherpad.openstack.org/p/openstack-helm-meeting-neutron-multibackend15:32
*** renmak_ has joined #openstack-meeting-515:32
portdirectI think that jayahn was wanting to do the linuxbridge backend15:32
portdirectand in my own time I'd be very keen to do OVN, as I've worked on this quite a bit (and my old openstack-on-k8s was built around it)15:33
SamYaplealways pushing an agenda this one15:33
v1k0d3nfor each of these items that get worked, can we make sure there are blueprints for them?15:34
v1k0d3nthat would help the community keep track of what's outstanding and who's working it.15:34
portdirectyeah - what we really ned to determine is the path of least evil..15:34
portdirectlines 30:3215:34
alanmeadowsI saw him sipping coffee from an OVN mug.15:34
anticwi want coffee15:34
korzenI have published some draft: https://review.openstack.org/#/c/466293/15:34
portdirectwe discussed this quite a bit at the summit - but we need to prototype some things i think so determine the best path15:35
korzenLB can be incorporated in neutron chart15:35
v1k0d3ni think @alanmeadows should probably weigh in on that etherpad15:35
portdirectoh sweet nice korzen :)15:35
alanmeadowsI think the network node concept was something missing from the beginning, that is a welcome addition15:35
portdirect+115:35
portdirectmeans we can prob get rid of that ovs labeling weirdness15:36
korzenother SDNs need to have their separate charts15:36
korzenand labeling to mark which node should operate which Neutron backend seems like a solution15:36
alanmeadowswell, you still have the need to get ovs both on compute nodes, and now network nodes15:36
portdirectyeah - just that it could now be loosedned up a bit and made more generic15:37
portdirectie: sdn-agent or similar15:37
alanmeadowsso the same conundrum still exists, but with different names15:37
alanmeadowssure, openvswitch label becomes something more palatable15:37
alanmeadowsbut same requirement for that multi-category label, unless someone has better ideas15:38
portdirectwe could just make it that the sdn runs on compute and network nodes?15:38
portdirectand dump it altogether15:38
korzensdn can have separate labels15:40
alanmeadowsthats what we do today, with a third label, to have it scheduled to two separate labels, we would have to get more fancy then nodeSelector15:40
alanmeadowswhich sounds fine to me, I just couldn't be bothered15:40
portdirectlol - i think that should be a twenty min fix :P15:41
* alanmeadows starts the clock.15:41
* portdirect suspects that will bite him15:41
portdirect:)15:41
v1k0d3nso maybe the best approach alanmeadows is to weigh in on that etherpad?15:42
alanmeadowsi will, but with this etherpad15:42
alanmeadowsdid this group work out whether they feel all of these options listed here, which are pretty wide reaching15:42
alanmeadowsfrom calico, to (open)contrail to ovs15:42
portdirectnot yet its still a wip15:42
alanmeadowswhether they can be handled in a single neutron chart15:42
alanmeadowsor whether neutron-foobar would be inevitable15:43
portdirectnope - thats the fundimental question at this stage15:43
alanmeadowsok so more workthrough/attempts need to be done15:43
alanmeadowsfor us to answer that question15:43
portdirectat the summit we agreed that we would prototype both approaches in PS's and then determin the most paletable path forward15:43
alanmeadowsokay15:44
portdirectlines 34:47 are where korzen has done a great job of highlighting most of the areas we need to consider15:44
v1k0d3n15 minutes til top of the hour folks.15:45
v1k0d3nlet's talk aboutu these neutron improvements in the openstack-helm channel.15:46
v1k0d3none thing that i think may be creeping up are cinder issues.15:46
v1k0d3ni've heard a couple of folks mention this. can anyone go a bit deeper? anticw ?15:47
anticwv1k0d3n: couple of issues, the default endpoint15:47
anticwand secondly it doesn15:47
anticwgah stupid ' button15:47
anticwdo not work15:48
anticwthe endpoint is an easy fix, we get obscure 500s without it15:48
anticwdo not work = tries to use iscsi in nova-compute for unknown reasons15:48
SamYapleanticw: you cant do iscsi in network namespace for kernel reasons15:49
v1k0d3nanticw: are these things you have  fixes for that could be submitted/reviewed, or are you still in the process of testing through?15:49
anticwv1k0d3n: just local becuase i aren't sure if it's me or something larger15:49
anticwSamYaple: don't want iscsi ... it should be using ceph15:50
SamYapleah sorry misread that anticw15:50
anticwhttps://pastebin.com/5Uvjk7hR15:50
anticwSamYaple: fwiw, i think we could get iscsi working as most of that stuff seems to run in the host namespace15:51
anticw(but that's OT)15:51
v1k0d3nanticw: let me redeploy a bare metal install, test and see if i get some of the same. i can reach out and we can work through them if you want/have time?15:51
anticwv1k0d3n: no15:51
anticwerr, yes15:52
SamYapleanticw: iscsi runs in the host namespace fine, there is a kernel bug for running in network namespaces15:52
v1k0d3n:) haha15:52
v1k0d3n8 mins left15:52
portdirectSamYaple: the only thing that jumps out at me is this: https://github.com/openstack/openstack-helm/blob/master/nova/values.yaml#L32215:52
portdirectbut that should not effect volume attach right?15:52
alanmeadowsthat should be how nova stores ephemeral disks15:53
anticwcinder-api is giving cinder-volume some json which it's not dealing with right, unclear which end is to blame15:53
anticwwe can talk about this over <- there later if you like15:53
v1k0d3nthat works anticw15:53
anticwportdirect: really easy to repro if you have 5 mins15:54
v1k0d3none last thing too. i think SamYaple and alanmeadows: you guys are still exploring rootwrap use...is that correct?15:54
v1k0d3nor have you guys come to some form of agreement? maybe we should stand up an etherpad so we can take it offline?15:54
v1k0d3n(unless there already is one).15:55
SamYaplethe summation is i say rootwrap.conf is a config (hence why it is in /etc/) and it is not in the LOCI images15:55
SamYaplethe fear is it is image specific stuff, which i dont agree with that15:55
portdirect+115:55
alanmeadowsI have been going through OOTB rootwraps trying to discover something that would end up being quite image-centric15:55
SamYaplefor glance and cinder if you use ceph you dont even NEED rootwrap, so its also a greater attack surface15:56
SamYaplethe deploy tool would be able to limit that attack surface but it must control the rootwrap files15:56
portdirectfor cider you do for backup I think?15:56
SamYaplei dont think so, but i oculd be wrong15:56
SamYaplei could be wrong about ALL of this, but i havent seen anything to suggest i am15:56
SamYapleso this is really pending more info15:56
alanmeadowsI have not been able to find an example yet, so I am willing to concede on bringing these into the fold of OSH, provided we come up with a path to customize not only rootwrap.conf, but allow injection of additional rootwrap.d files15:56
SamYapleim happy to come back to it once/if an issue is found15:57
alanmeadowsto be honest, the main reason it was skipped for configuration overrides15:57
alanmeadowswas it was a substantial amount of work15:57
srwilkersalanmeadows, i can tackle that15:57
SamYapleyea sure alanmeadows, but to be fair it can be wholesale copied over at first15:57
SamYaplemaintenance on a straight copy is insigificant15:57
SamYapleany paramaterized rootwrap is a thing that comes later15:58
alanmeadowswell, but I mean if we're going to own it, we have to give end users the ability to do things with it (templates)15:58
portdirectthey are pretty well commented atm - should just be a case of wrapping in conditionals i think15:58
alanmeadowsif we own it, and then jam it in, we've done a disservice15:58
alanmeadowsin fact, I think because this is not oslo-gen capable15:59
SamYaple'dont let perfect be the enemy of good'15:59
SamYaplebut im with you, i dont want it to sit in there15:59
alanmeadowsthe function introduced with the cinder stuff, namely the helm-toolkit "toIni" function (casing correction needed)15:59
SamYaplethat doesnt mean it cant sit in there AT FIRST15:59
alanmeadowsmay be perfect for rootwrap.conf15:59
SamYaplereminder, openstack config files are not ini. that is all16:00
SamYaplei think rootwrap follows ini still though16:00
v1k0d3nwe unfortunately have to wrap up.16:00
alanmeadowsits standard [HEADER] item=foo16:00
v1k0d3nsorry that the meeting took a while today.16:00
v1k0d3nalanmeadows and SamYaple...want to continue in #openstack-helm?16:01
SamYaplesure i think we are basically done though16:01
v1k0d3nsounds good.16:01
v1k0d3nok calling the meeting folks. thanks everyone for coming and contributing!16:01
alanmeadowsI think we can close with saying srwilkers can own this, just an etherpad with some comments to start out a trial on this16:01
SamYapleo/16:01
srwilkersbai16:01
v1k0d3n#endmeeting16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:02
openstackMeeting ended Tue May 23 16:02:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
*** lrensing has left #openstack-meeting-516:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-05-23-15.01.html16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-05-23-15.01.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-05-23-15.01.log.html16:02
*** zenirc369 has joined #openstack-meeting-516:04
*** gagehugo has left #openstack-meeting-516:04
*** renmak_ has quit IRC16:08
*** matrohon has quit IRC16:15
*** ricolin has quit IRC16:24
*** renmak_ has joined #openstack-meeting-516:31
*** aarefiev is now known as aarefiev_afk16:45
*** derekh has quit IRC16:48
*** ralonsoh has quit IRC17:01
*** korzen has quit IRC17:17
*** renmak_ has quit IRC17:25
*** JawonChoo has joined #openstack-meeting-517:43
*** JawonChoo has quit IRC17:47
*** renmak_ has joined #openstack-meeting-517:51
*** renmak_ has quit IRC17:51
*** srwilkers has quit IRC18:06
*** felipemonteiro has joined #openstack-meeting-518:27
*** felipemonteiro_ has joined #openstack-meeting-518:28
*** renmak_ has joined #openstack-meeting-518:31
*** felipemonteiro has quit IRC18:33
*** krtaylor has quit IRC18:35
*** renmak_ has quit IRC18:36
*** alraddarla has left #openstack-meeting-518:41
*** zenirc369 has quit IRC18:41
*** renmak_ has joined #openstack-meeting-518:48
*** rarcea has quit IRC19:19
*** krtaylor has joined #openstack-meeting-519:28
*** JawonChoo has joined #openstack-meeting-519:31
*** JawonChoo has quit IRC19:36
*** mattmceuen has quit IRC20:34
*** gardlt has quit IRC20:36
*** renmak_ has quit IRC21:37
*** krtaylor has quit IRC21:41
*** jroll has quit IRC21:47
*** jroll has joined #openstack-meeting-521:47
*** jroll has quit IRC21:49
*** lamt has quit IRC21:51
*** jroll has joined #openstack-meeting-521:53
*** jaugustine has quit IRC22:01
*** JawonChoo has joined #openstack-meeting-522:14
*** JawonChoo has quit IRC22:18
*** felipemonteiro_ has quit IRC22:22
*** marst_ has quit IRC22:38

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