Tuesday, 2016-11-29

sdakesbezverk idea is to make a common pattern thta people can copy00:00
sdakesbezverk so we can get an army of contribs to make microservices just as in done in kolla repo today00:00
portdirect^^ this would be great00:00
sdakerather packaged microservices00:00
sdakethe open source method doesn't f ind the optimal soltuion initially it finds it eventually00:01
sdakejrich523 write that one down ;)00:01
sbezverksdake: portdirect: we need to confirm the directory structure. so we DO follow  native helm's directory structure, right?00:01
sdakesbezverk thats what my patch is going to be doing00:01
*** TxGirlGeek has quit IRC00:02
sbezverksdake: so parent level is kolla-kubernetes or openstack?00:02
sdakeyou mean directory structure?00:02
sbezverksdake: yes00:03
sdakeyou tell me00:03
portdirectsbezverk: thats what I'm going for as well00:03
jascott1it currently looks like this in sbezverk's PS00:03
jascott1helm/kolla-kubernetes/charts/openvswitch/charts/openvswitch-ovsdb/00:03
jrich523whoa what now?00:03
*** yuanying_ has joined #openstack-kolla00:03
sbezverkI would suggest to keep: ./helm/kolla-kubernetes/charts/service-1/charts/microservice-1/charts00:04
sdakejrich523 nm - conversation from 2 hrs ago :)00:04
sdakeportdirect thoughts?00:04
sbezverkjascott1: :-) we are in sync then..00:04
jascott1sdake was droppin knowledge00:04
jascott1:)00:04
sdakejascott1 hard earned00:04
jrich523lol its ok, something interesting i should know about? :)00:04
jascott1"the open source method doesn't f ind the optimal soltuion initially it finds it eventually"00:05
jrich523lol was just reading that00:05
portdirectim fine with sbezverk's suggestion00:05
jrich523was going to ask if i should be quoting sdake when i use it or someone else? :)00:05
sdakethose are my words00:05
jascott1i like00:05
jascott1are there any corner cases with dir structure?00:06
* jrich523 saves that one00:06
portdirectjascott1: almost certainly - though I'm not sure what yet :)00:08
jascott1staring at it but cant see any now :)00:08
*** kristian__ has joined #openstack-kolla00:11
jascott1oh hey installing w kubeadm http://paste.openstack.org/show/590729/ <- legit?00:12
sdakefwiw from pervious experience with kolla docker files git mv of directory is easy git mv of files is hard00:12
sdakeif there are corner cases its easy to solve with a restructure without a bunch of pain00:12
portdirectjascott1: looks ok00:14
jascott1thx00:14
portdirectjascott1: https://github.com/att-comdev/halcyon-kubernetes/tree/master/kube-deploy/roles00:14
sbezverksdake: portdirect: where you want to store global values which is applicable to all microservices?00:15
*** kristian__ has quit IRC00:15
sbezverkthings like kolla_tag, kolla_base etc??00:15
portdirectsbezverk: I'm open to suggestions - where do you think we should have 'em?00:16
sdakedo you know how the ascii character set was created00:16
sbezverkportdirect: the only way I could see it now if we go per microservice approach, we need to copy them into values.yaml for each microservice00:17
sdakesbezverk there ya go thats how the ascii character set was created ;)00:17
sdakecommon DRY = o300:18
sdakewe can easily make a tool to handle that in the meantime00:18
sdakesince we are making all kinds of tools to workaround helm defeciencies00:18
portdirectok - finish each microservices yaml with @@COMMON@@ and then find/sed it in?00:19
sdakenope that won't compile with helm natively00:20
sdakegoal is helm native00:20
portdirectWET is is then00:21
sdakekfox1111 when you appear - you wlll want to read the above ^00:21
sbezverksdake: I bet kfox1111 will give -3 on this ps ;-)00:23
sdakethis is how the docker containers were developed00:23
sdakeit led to a great outcome00:24
sdakeit will be vastly sped up this time because we wont have to jerk around and figure out what to do00:24
sdakei already know what to do :)00:24
sdakefollowing same pattern as docker file creation during ramp up of kolla repo00:24
sdakeits unfortunate you fellas weren't around for that00:25
sdakehowever the rest of our community is up to speed on the methodology00:26
sdakejust have to take my word for it this will roll well - if not do your own thing :)00:26
sdakejascott1 you joining the party - if so recommend portdirect get you ramped up on the dev env00:28
sdaketook me about 45 minutes to get there00:29
portdirectsdake: it working ok for you know?00:29
jascott1def joining the party00:29
*** JRobinson__ is now known as JRobinson__afk00:29
sdakeportdirect seems to be00:29
jascott1definitely joining that is00:30
portdirectawesome :) what TZ you in?00:30
jascott1PST00:30
*** hfu has joined #openstack-kolla00:30
sdakeportdirect if you guys setup a hangout lemme know i'll join again so i can relive the experience ;)00:34
*** jtriley has joined #openstack-kolla00:35
portdirectnp, we should loop inc0 in as well00:36
*** yingjun has joined #openstack-kolla00:38
jascott1might not be around hes in CST00:39
*** jtriley has quit IRC00:40
sdakeportdirect 1:1 is better00:40
sdakeportdirect keeps everyone in sync :)00:40
sdakeand ya inc0 is not feeling well today i gathered from whta he said this morning in channel00:41
sdakei dont think he will feel well this week was my impression he said soething like "ok guys cut me some slack this week as I dont feel well" or something00:41
jascott1we are talking about the vagrant one right?00:43
sdakethats the one00:43
jascott1I had already started the non-vagrant one00:43
jascott1that was linked to00:43
*** vhosakot_ has quit IRC00:43
sbezverksdake: I prepped one microservice, just to make sure everybody agrees on approach, I will push it to the queue00:43
sdakesounds good00:44
portdirectanyone here a ceph guru - getting a bit confused about OSD_ID?00:45
portdirectcant work out how the osd container gets it on the 2nd (or subseqent start) https://github.com/openstack/kolla/blob/master/docker/ceph/ceph-osd/extend_start.sh#L3000:46
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP adding openvswitch-ovsdb microservice  https://review.openstack.org/40395900:47
sdakeportdirect no idea how that stuff works - kfox1111 has a good handle on it00:47
sdakesbezverk may as well - pretty sure he demoed it :)00:47
sbezverkportdirect: sdake: it is wip, I will clean it up more tonight.. before doing that I would like to get ok from the community00:48
sbezverkspecifically from kfox111100:48
sdakesbezverk might as well make it pretty00:49
sdakesbezverk qq, does this follow standard layouts expected of helm?00:49
sbezverksdake: yes00:49
Jeffrey4lsdake, re gnocchi + ceilometer, it works. i tested it.00:50
sdakeJeffrey4l roger00:50
sbezverkso when cleaned up you should be able to deploy it just by running helm install openvswitch-ovsdb00:50
*** jtriley has joined #openstack-kolla00:50
sdakecan you get it to that point so i can test it in my env00:50
sbezverkI will do it, but it is 8pm here so I will concentrator on it mostly later tonight and tomorrow early morning est00:51
sdakewhere do i run helm install openvswitch-ovsdb from?00:51
sdakesbezverk i need something to copy :)00:51
*** JRobinson__afk is now known as JRobinson__00:52
sbezverkfrom openvswitch-ovsdb folder00:52
sdakewill it deploy as is?00:52
Jeffrey4lsdake, any issue report?00:52
sdakeJeffrey4l its in today's log - something about continer not starting00:52
sbezverksdake: yes00:52
sdakedidn't have time to dig into it with him00:52
sdakesbezverk good enuf00:53
sdakedec20, we ogt a whole lot of microservices to crank out00:54
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP adding openvswitch-ovsdb microservice  https://review.openstack.org/40395900:54
Jeffrey4lsdake, could u post it out?00:55
sdakeJeffrey4l have to check logs i dont hve any data00:56
*** dave-mccowan has quit IRC00:56
Jeffrey4lsdake, ok. i will try to deploy it later. master branch ,right?00:57
sdakeJeffrey4l no clue - no time to investigate or question what he was using00:58
*** Pavo has quit IRC00:58
*** zhubingbing has joined #openstack-kolla00:58
*** tonanhngo has quit IRC01:01
*** jtriley has quit IRC01:01
portdirectJeffrey4l: you dont have any insight into my ceph q above do you?01:02
*** jtriley has joined #openstack-kolla01:02
jascott1haha got that vagrant based k8s going np but then busybox is doing the same thing01:03
Jeffrey4lportdirect, yep.01:03
Jeffrey4ltldr; did u have logs and error message? portdirect01:03
*** Pavo has joined #openstack-kolla01:03
portdirectjascott1: I'll be with you in two mins - could you past the dump of 'kubectl get --all--namespaces pods'?01:04
jascott1well I think I have it now but will to be sure01:04
portdirectJeffrey4l: working on kollo-k8s helm stuff and I cant work out how the osd container gets the OSD_ID on the 2nd (or subseqent start) https://github.com/openstack/kolla/blob/master/docker/ceph/ceph-osd/extend_start.sh#L3001:05
Jeffrey4lportdirect, what did u get when run `ceph osd create`?01:06
portdirectIt increments each time01:06
Jeffrey4lportdirect, yes. that how ceph osd create works.01:06
jascott1portdirect with vagrant its looking good http://paste.openstack.org/show/590734/01:07
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP adding openvswitch-ovsdb microservice  https://review.openstack.org/40395901:07
sdakesbezverk i'm curious about one thing, can we have a common file for the common code and then just copy that around?01:07
sbezverksdake: so the latest revision os PS gets rendered by helm correctly01:08
portdirectjascott1: from the busybox pod if you can run 'nslookup kubernetes' then you are good to go :)01:08
jascott1yes!01:08
portdirectjascott1: the cni driver can take a bit of time to come online, during whihc pod creation will fail01:08
jascott1it seems to be working01:09
portdirect:D01:09
jascott1thanks!01:09
sbezverksdake: wrt your question if values.yaml has ALL variables for all global and per microservice variables then yes01:09
*** tonanhngo has joined #openstack-kolla01:10
sdakesbezverk hmm let me look at your last patch set - i thought there was a common.tpl file somwhere in the mix01:10
*** tovin07 has joined #openstack-kolla01:10
*** schwicht has quit IRC01:10
portdirectJeffrey4l: whats confusing me is how the variable is populated here: https://github.com/openstack/kolla/blame/master/docker/ceph/ceph-osd/extend_start.sh#L72, on restarts when not bootstrapping: https://github.com/openstack/kolla/blob/master/docker/ceph/ceph-osd/extend_start.sh#L1201:11
*** zhurong has joined #openstack-kolla01:11
sbezverksdake: nope all common code was in _helpers.tpl01:11
sdakethats what i'm talking about then :)01:12
sbezverkand then each level has added its variables01:12
sdakeso can _helpers.tpl be copied around?01:12
sbezverksdake: _helpers.tpl has common code and not variables01:13
sdakeso that can be copied around?01:13
Jeffrey4lportdirect, https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/ceph/tasks/start_osds.yml#L3601:13
*** JRobinson__ has quit IRC01:13
sbezverksdake: yes it can be copied, what exactl you try to solve with this?01:14
*** tonanhngo has quit IRC01:14
jascott1sbezverk sdake or put in configmap?01:14
sdakemaking implementation simpler01:14
sdakewe need to make the implementation easy - so people can stamp em out01:14
sdakeif _helpers.tpl is common across the code base might as well just copy that around01:15
jascott1would it be bad to say 'install the utils' chart first? tif not we could load that once01:15
portdirectJeffrey4l: sweet cheers! (now I just need to work out how to k8s that effectively)01:15
Jeffrey4lportdirect, cool01:15
sbezverksdake: ok I need to step out now. will try to include helpers later today or first thing tomorrow morning..01:16
sdakeroger01:16
sdakejascott1 unknown - i think we want each microservice to standalone tho01:17
jascott1gotcha01:19
jascott1i *think* we can load files from root dir of a chart using Files. in templates. we might then only need to have common stuff in the middle level chart01:20
jascott1oh each MICRO service01:21
jascott1sorry01:21
sdakeanother short term hack is symlinks vs copying01:21
portdirectsdake: I think symlinks would be preferable01:22
sdakeyou think that :)01:22
alanmeadowsthought about that but then might break if someone rearranges structure, even if just locally01:22
alanmeadowscharts would no longer be "self-contained units"01:23
alanmeadowsgiven the links would be relative in this case01:23
sdakecopy sync is easily handled by a 1 liner find operation01:23
alanmeadowsmicro/templates/_common.tpl -> ../../../util-chart/templates/common.tpl01:23
alanmeadowsplus helm tars things up, didn't look closely at how its taring and whether it would follow links or (and this would be weird) preserve links ;-)01:24
sdakefind . -name _common.tpl -exec cp /tmp/common.tpl {} \;01:24
portdirecthmm01:24
sdakelets use that one liner for now i think01:24
portdirecti think i may be changing my mind...01:24
*** schwicht has joined #openstack-kolla01:25
*** jtriley has quit IRC01:25
alanmeadowsI only found three options to move forward 1) parent chart that all installs must go through, e.g. uberchart, subcharts cant install directly 2) clone globals to every values.yaml (difficult to maintain but helm native today) or 3) some sort of preparatory step taking a common set of defines and placing them within each subchart with my personal hope helm01:29
alanmeadowswill have a solution for this in the future01:29
sdakenot talking about common values talking about common code in daemonsets/etc01:30
sdakedoes a cp not work for that?01:30
alanmeadowswell 3) for us was about both01:30
alanmeadowsyou can define anything at the end of the day01:31
alanmeadowscommon global things you wish to reference everywhere, e.g. fqdn, and common manifest snippets01:31
alanmeadowsI thought kfox1111 was doing defines/includes of common code snippets at least within a single chart, e.g. logging in one review I looked at anyways, its just a matter of exposing that to all charts and back to the options above in this case only 1) or 3)01:34
alanmeadowscould be it was something else... too much whizzing by the last few days01:34
jascott1the problem with copying might be that any vars referenced in the common stuff are not going to be at the same hierarchal position in the var tree01:37
jascott1unless they are global01:37
jascott1https://review.openstack.org/gitweb?p=openstack/kolla-kubernetes.git;a=blob;f=helm/kolla-kubernetes/templates/_helpers.tpl;h=75977ce54ce5a43a8d0d5eb3b2d4a70f120b2de4;hb=883046b1cfed40595628116cb1cec4867c210c9e01:38
alanmeadowsjust as sdake was alluding too I think, I think you have to separate out whether the discussion is on common code or common values01:38
alanmeadowseven though in some directions, the paths could be the same01:38
sdakeso what is happening with the _globals.tpl is being optimized seprately from common values01:38
sdakewe can do _globals.tpl now because it is easy01:39
sdakecommon values harder01:39
alanmeadowswe are doing defines for common "global" values01:39
alanmeadowswhich is the same mechanism for shared snippets01:39
sdakeright - this method is helm native off the block01:40
sdakeif we really want to add some parser in the midst of o3 we can do that01:40
jascott1aic is using utils chart tho right?01:40
alanmeadowsyes, but as mentioned with kfox111101:40
alanmeadowsyou may be tricked into thinking utils chart can do defines, and you can include it as a dependency in subcharts01:41
alanmeadowsdepending on the chart load order, it may or may not work01:41
alanmeadowsso its not actually safe (if it did work reliably, that would be pretty much helm native)01:41
jascott1utils folder is gone ;)01:42
alanmeadowsits now openstack-base, probably soon to be "common" -- so what we have to do is the utils does some utils things like secrets01:42
alanmeadowsbut it also is responsible for generating "_common.tpl"01:42
alanmeadowswhich we copy to all charts01:42
alanmeadowsshhackery01:42
openstackgerritOpenStack Proposal Bot proposed openstack/kolla: Updated from global requirements  https://review.openstack.org/40077001:43
alanmeadowsi suppose one simple ask to helm devs01:44
alanmeadowswould be reliable chart ordering01:44
alanmeadowsso you can do defines in a child chart01:44
alanmeadowsreliably01:44
alanmeadowsobliterates the need for any copying01:44
alanmeadowsdoing defines isn't 100% optimal but at least its all helm and no "prep" copy step01:44
jascott1they probably using a map in golang (which is unordered) ;)01:44
alanmeadowsyup01:44
alanmeadowsbut its easy to prove out, do a child chart define, do a helm install --debug --dry-run and grep for your value01:45
alanmeadowshit and miss01:45
jascott1bummer01:45
alanmeadowsthat took me a while to realize what was going on ;-)01:45
jascott1i bet01:45
jascott1a requirement system without ordering01:46
alanmeadowsmy plan was to create an issue and see what Lachlan says01:47
alanmeadowsI have actually seen a number of charts01:47
alanmeadowswhere they are incorrectly depending on this behavior01:48
jascott1yikes01:48
jascott1ya most everyone seems to end up there01:48
alanmeadowshttps://github.com/kubernetes/helm/issues/1568 - looks like sbezverk beat me to it01:55
*** sdake_ has joined #openstack-kolla01:55
*** sdake_ has quit IRC01:55
*** sdake_ has joined #openstack-kolla01:55
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Move glance precheck into its own role  https://review.openstack.org/39935401:56
sdake_portdirect how abouts do i get my ssh private key into this vagrant environment?01:57
*** sdake has quit IRC01:58
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Enable cloudkitty ui when enable_cloudkitty is yes  https://review.openstack.org/40352001:59
portdirectsdake_: you need to modify the Vagrantfile to include 'config.ssh.private_key_path'02:01
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Enable sahara dashboard when enable_sahara is yes  https://review.openstack.org/40350402:01
portdirectsdake: https://github.com/att-comdev/halcyon-vagrant-kubernetes/blob/master/Vagrantfile#L4402:02
portdirectthough I've never tried it02:02
sdake_mey I just c&ped it :)02:03
portdirectthats the way :)02:04
*** MarMat has quit IRC02:04
*** schwicht has quit IRC02:07
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Enable ironic ui when enable_ironic is yes  https://review.openstack.org/40344602:07
sdake_i cloned sbezverk 's work02:07
sdake_wondering how i deploy it on my kube cluster02:07
sdake_portdirect ^^02:07
sdake_[vagrant@kube1 charts]$ helm install openvswitch-ovsdb02:08
sdake_E1129 02:08:23.435628   17426 portforward.go:209] Unable to create listener: Error listen tcp6 [::1]:45307: bind: cannot assign requested address02:08
sdake_Error: release honest-cardinal failed: namespaces "kolla" not found02:08
portdirectok the 2nd is easy02:09
portdirect'kubectl create namespace kolla'02:09
sdake_ok that deployed it02:10
sdake_portdirect how do i check it deployed?02:10
portdirecthelm ls02:10
portdirectbut i dont trust that02:10
sdake_it says deployed02:11
portdirectkubectl get --namespace=kolla all02:11
sdake_[vagrant@kube1 charts]$ kubectl get --namespace=kolla all02:11
sdake_[vagrant@kube1 charts]$02:11
sdake_shouldn't that print something out?02:12
portdirectone would hope02:12
sbezverksdake: kubectl get pods --namespace=kolla02:12
sbezverkshould show you running pod02:12
sdake_nada02:12
sbezverksdake: which command you use to deploy?02:13
sdake_[vagrant@kube1 charts]$ helm install openvswitch-ovsdb02:13
sdake_E1129 02:09:53.775311   18667 portforward.go:209] Unable to create listener: Error listen tcp6 [::1]:44673: bind: cannot assign requested address02:13
sdake_NAME: angry-ant02:13
sdake_LAST DEPLOYED: Tue Nov 29 02:09:53 201602:13
sdake_NAMESPACE: default02:13
sdake_STATUS: DEPLOYED02:13
sbezverkah it got deployed into default namespace02:13
sbezverkkubectl get pods --namespace=default02:13
jascott1btw you can use -n02:14
sdake_[vagrant@kube1 charts]$ kubectl get pods --namespace=default02:14
sdake_[vagrant@kube1 charts]$02:14
sbezverkhave you changed value for registry?02:15
sdake_nope02:15
*** ipsecguy has joined #openstack-kolla02:15
sbezverk:-)02:16
jascott1kubectl get pods --all-namespaces02:16
*** duonghq has joined #openstack-kolla02:16
portdirectsbezverk: told ya that would cause pain :P02:16
sdake_jascott1 that prints out a slew of kubesystem pods02:16
jascott1and all other pods02:17
duonghqmorning guys02:17
sdake_dup duonghq02:17
sdake_duonghq time to join the party dude!!02:17
jascott1just in case its in a weird namespace02:17
portdirectsdake_: you working from this pr: https://review.openstack.org/#/c/403959/3/helm/kolla-kubernetes/charts/openvswitch/charts/openvswitch-ovsdb/values.yaml02:17
sdake_we are rolling02:17
sdake_portdirect roger02:17
duonghqroger02:17
portdirectneed to change the docker_registry to docker.io02:17
portdirectthen rebuild & deploy02:18
duonghqportdirect, you mean now we use docker registry? or local register which signed with CN: docker.io?02:18
sdake_nada02:19
sdake_how do you rebuild?02:19
sbezverksdake you do not rebuild, you need to delete previous deploy and then start new one02:19
sdake_yup did that02:20
sbezverkhelm ls02:20
sbezverkhelm delete {old}02:20
portdirectduonghq: dont quite parse, I'm refering to this line here: https://review.openstack.org/#/c/403959/1/helm/kolla-kubernetes/charts/openvswitch/charts/openvswitch-ovsdb/values.yaml@6, which I think should be changed to docker.io?02:20
sdake_[vagrant@kube1 charts]$ helm ls02:20
sdake_E1129 02:20:10.884362   27368 portforward.go:209] Unable to create listener: Error listen tcp6 [::1]:41833: bind: cannot assign requested address02:20
sdake_[vagrant@kube1 charts]$02:20
sbezverksdake_: helm version?02:20
portdirectsbezverk:  that error looks nasty02:21
sdake_Server: &version.Version{SemVer:"v2.0.0", GitCommit:"04f203d2d081417bae8a61a8581f70d5ed652aca", GitTreeState:"clean"}02:21
sbezverksdake: it looks like your helm installation is not working02:21
duonghqportdirect, got it02:21
sdake_ya not sure what to make of that error listen tcp6 thing02:21
sbezverkhave you done "helm init"02:21
sbezverk?02:21
sdake_nope02:21
sbezverkplease do it02:21
sbezverkit will start tiller pod02:21
sdake_where do i do that02:21
portdirectwait - your using my vagrant seup right (as in from portdirect not att-comdev)?02:21
sdake_[vagrant@kube1 charts]$ helm init02:22
jascott1wow I see a new error - Error: transport is closing02:22
sdake_$HELM_HOME has been configured at $HOME/.helm.02:22
sdake_Warning: Tiller is already installed in the cluster. (Use --client-only to suppress this message.)02:22
sdake_Happy Helming!02:22
sdake_portdirect roger02:22
sbezverksdake: can you do now helm version?02:22
sdake_Client: &version.Version{SemVer:"v2.0.0", GitCommit:"04f203d2d081417bae8a61a8581f70d5ed652aca", GitTreeState:"clean"}02:22
portdirectthats a nightly build i think02:22
sbezverkhmm, it shold also print server version02:23
sdake_it does02:23
sdake_same thing02:23
sbezverkon the second line02:23
sdake_Server: &version.Version{SemVer:"v2.0.0", GitCommit:"04f203d2d081417bae8a61a8581f70d5ed652aca", GitTreeState:"clean"}02:23
sbezverkok, now helm ls02:23
portdirectsbezverk: wait 2 mins02:23
sdake_E1129 02:23:37.770817   30205 portforward.go:209] Unable to create listener: Error listen tcp6 [::1]:42407: bind: cannot assign requested address02:23
portdirectlets get you on a stable helm, thats a canary build that your using02:25
portdirectkubectl delete deployment tiller-deploy --namespace kube-system02:25
sbezverksdake_: not sure the cause of this message02:25
sbezverkportdirect: I use the same version 2.0.002:25
sdake_deployment "tiller-deploy" deleted02:25
portdirectsame git commit?02:26
sbezverkportdirect: that I am not sure02:26
sdake_happy to use a stable version :)02:26
jascott1helm init02:26
sbezverkServer: &version.Version{SemVer:"v2.0.0", GitCommit:"51bdad42756dfaf3234f53ef3d3cb6bcd94144c2", GitTreeState:"clean"}02:26
portdirectrm -rf /usr/local/bin/helm02:26
jascott1oh that just reinstates probaby02:26
portdirectdont do that02:27
portdirectas in the 'helm init'02:27
sdake_portdirect right- next step after the rm is what?02:27
duonghqhave we had docker registry in infra?02:28
sdake_duonghq nope02:28
duonghqgot it02:28
sbezverkhere is the link for official 2.0.0 release02:28
portdirectas root: curl -L https://kubernetes-helm.storage.googleapis.com/helm-v2.0.0-linux-amd64.tar.gz | tar zxv --strip 1 -C /tmp; chmod +x /tmp/helm; mv /tmp/helm /usr/local/bin/helm02:28
sbezverkcurl http://storage.googleapis.com/kubernetes-helm/helm-v2.0.0-linux-amd64.tar.gz | tar --strip-components 1 -C /usr/bin linux-amd64/helm -zxf -02:28
portdirectlol02:28
sbezverk:-)02:29
portdirectwas using: https://kubernetes-helm.storage.googleapis.com/helm-canary-linux-amd64.tar.gz before...02:29
portdirectthen run 'helm init'02:29
sdake_[vagrant@kube1 charts]$ helm init02:30
sdake_$HELM_HOME has been configured at $HOME/.helm.02:30
sdake_Tiller (the helm server side component) has been installed into your Kubernetes Cluster.02:30
sdake_Happy Helming!02:30
sdake_[vagrant@kube1 charts]$ helm install openvswitch-ovsdb02:30
sdake_Error: could not find a ready tiller pod02:30
portdirectgive it a min02:30
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: TEST_NO_MERGE  https://review.openstack.org/40397802:30
portdirectyou can gech the output of 'kubectl get -n kube-system pods' to see if its ready02:30
Jeffrey4lsdake_, could u review this https://review.openstack.org/403516 ?02:30
sdake_Jeffrey4l in a moment plz02:31
sdake_portdirect everything in running state02:31
portdirecttry the install again02:31
sdake_E1129 02:32:18.175603    4942 portforward.go:209] Unable to create listener: Error listen tcp6 [::1]:40713: bind: cannot assign requested address02:32
sdake_this error seeems to be problematic02:32
sdake_no running pod02:33
sbezverksdake_: curious why it tries to use ipv6 for communicating with tiller??02:33
sdake_no clue - didn't write the dev environmnet :)02:33
sbezverkportdirect: ;-) same question02:33
portdirectits a good one02:34
sdake_portdirect you said you turned off ipv6 during our conversation last night?02:34
sbezverkI do nto remember seeing much in terms of ipv6 support by kube02:34
sbezverkmaybe I just missed it02:34
portdirectyeah - as ceph was trying to bind to it, so i just disabled it to get it out of the way, - thats why I put it down to weirdness in a nightly build of helm02:35
sdake_wher edid you disable it02:36
sdake_on the host os or in vagrant?02:37
portdirectansible: https://github.com/portdirect/halcyon-kubernetes/blob/8d25f2104cca47c1a51aa344f21b38c31f6a0d4c/kube-deploy/roles/upgrade-os/tasks/centos.yml#L4502:38
sbezverkgood night gents, happy helming ;-)02:38
portdirectlaters sbezverk02:38
sdake_ok i ran that02:40
sdake_late sbezverk02:40
sdake_now wot :)02:40
sdake_need to stop tiller?02:40
jascott1what version of tiller now?02:40
sdake_kube-system   tiller-deploy-2241983194-xcut4          1/1       Running   0          12m02:41
portdirectsdake_: that should already have been active: 'ip a' shouldn't show any ipv6 addrs - which is why that error has me baffled02:42
sdake_ya - i think tiller is busted02:43
sdake_how do i remove it02:43
portdirect'kubectl delete deployment tiller-deploy --namespace kube-system'02:44
jascott1to get tiller image version you need something like: kubectl get pods -n kube-system -o yaml | grep tiller02:44
jascott1im using 2.0.0 tiller and client and am having problems on this vagrant so Id like to know what version you have02:44
portdirectbut I'm not sure thats gonna bring you joy - as it stores its config in a 3rd party resource afaik - and I have no idea how to delete that02:45
portdirectjascott1: your having issues as well?02:45
jascott1when I do helm install on that chart I get 'error transport is closing'02:46
sdake_portdirect what precisely did you do once you turned off ipv6?02:46
jascott1but this on the new vagrant setup02:46
sdake_the listen error comes from the server02:46
sdake_clients don't use listen typically02:46
portdirectsdake_: the link I provided above is the ansible script that vagrant ran to provision the machines.02:47
sdake_portdirect i just ran the ipv6 disable directly02:48
sdake_oh that was your branch we deployed my vagrant from02:48
sdake_i have no ipv6 addresses in my system02:48
portdirectcool that should not have made a difference in that case02:48
portdirectsdake_: yeah02:49
portdirectjascott1: that error you are getting is this: https://github.com/kubernetes/helm/issues/1589 (I'm intlabs, and v1k0d3n is aware of it as well)02:50
portdirectif you change this: https://github.com/att-comdev/halcyon-kubernetes/blob/master/kube-deploy/group_vars/all.yml#L26, to 'v1.4.6' then you'll be fine (i hope)02:51
*** JRobinson__ has joined #openstack-kolla02:51
sdake_https://github.com/docker/docker/issues/217402:51
jascott1going to eat w kids bbiab. thanks02:52
sdake_portdirect so i need to tear down my env and reubild it?02:53
portdirect:( thats prob the quickest way02:53
* sdake_ groans02:53
sdake_in my repo is this: kube_version: v1.4.602:57
sdake_already02:57
sdake_portdirect ok dude - bit lost02:58
portdirectthat comment above was for jascott102:58
*** Pavo has quit IRC02:58
sdake_about the tear down?02:59
sdake_you said change all.yml to v1.4.602:59
sdake_it looks like it is already 1.4.602:59
sdake_ /home/sdake/work/halcyon-vagrant-kubernetes02:59
sdake_i dont see how halcyon-kubernetes is being pulled in03:00
*** yuanying_ has quit IRC03:00
portdirectjascott1: used the att-comdev repo, not my fork03:00
portdirectyou should have: /home/sdake/work/halcyon-kubernetes03:00
portdirectas well03:00
sdake_i do03:00
sdake_it contains 1.4.603:00
sdake_on that all.yml version03:01
portdirectthats correct03:01
kfox1111wow...03:01
kfox1111long long long thread.03:01
kfox1111summery please03:01
sdake_so why tear down?03:01
kfox1111"I'm up to this point:"03:02
kfox111120:29 < alanmeadows> I only found three options to move forward03:02
kfox1111and I agree with his option 3.03:02
*** sayantan_ has joined #openstack-kolla03:02
sdake_i think you didn't read far back enough :)03:02
sdake_did you read the part where I pinged you?03:02
portdirectsdake_: can you give me 2 mins - sorry to keep you hanging03:02
kfox1111yeah read that part.03:03
sdake_portdirect all good03:03
sdake_kfox1111 lets crank this stuff out - we can reach perfection in o303:03
kfox1111I think sbezverk really wants native helm without any processing no matter what.03:03
sdake_i want native helm03:03
kfox1111I really want a clean api03:03
kfox1111followed by native helm when possible.03:03
*** Pavo has joined #openstack-kolla03:03
kfox1111but api trumps.03:03
sdake_agree, api has nothing to do with values.yml being copied around03:04
kfox1111cause I'm going to deploy this into production and do not want to have an issue when its time to upgrade.03:04
sdake_rather globals.tpl being copied around03:04
kfox1111yeah, I don't like globals at all for this use case.03:04
kfox1111the values are all for configuring a specific microservice.03:04
sdake_right03:05
kfox1111when that microservice is nested into a parent service, its config values should hang directly off of the child.03:05
sdake_we aren't nesting03:05
kfox1111nova's vars have:03:05
kfox1111novncproxy.foo = value03:05
kfox1111not,03:05
kfox1111globals.foo = value03:05
kfox1111or globals.novncproxy_foo = value03:05
sdake_i guess i dont understand that particular problem in detail03:06
kfox1111each microservice provides a flat value space.03:06
kfox1111sdake_: look up variable scoping in helm.03:06
kfox1111global vs package.03:06
kfox1111I'm aguing global is not a good fit for our use case. it presents what I think is a bad api.03:07
sdake_we agreed (I believed) that we want a package per microservice03:07
kfox1111package per microservice, non global variables.03:07
kfox1111is what I'm arguing for.03:07
kfox1111templated version numbers, and a common lib.03:07
portdirectsdake_: I now have a working helm setup - when your ready we can go through setting it up - though the easyest way to do that si gonna be a 'vagrant destroy' pulling the mods I've made and then 'vagrant up' again...03:07
kfox1111howerver we can best meet those goals.03:07
sdake_ok - cool - so lets sort that out after we have a functional microservice layer03:07
*** sp_ has joined #openstack-kolla03:07
sdake_kfox1111 we will get you there, yo uhave my word03:08
kfox1111sdake_: this won't look to be important until someone builds some of the nested packages.03:08
kfox1111:/03:08
alanmeadowsI still think there is one case for globals and that is microservices defining their service ports - combination from pulling the more 'common' fqdn from a common.tpl and service port from sister chart allows any service to build an endpoint for any other service and allow microservices to control their port binding/exposure03:09
sdake_kfox1111 this is the spinning out of control build tool i was speaking of ;)03:09
*** unicell has quit IRC03:10
kfox1111alanmeadows: I don't quite follow. shouldn't the services be looking it up from keystone?03:13
kfox1111we've been considering configmaps outside of the normal helm space. helm could create them, but it could be something else too.03:14
*** v1k0d3n has joined #openstack-kolla03:15
alanmeadowsI see, so something else generates those, not helm interpreted templates in your case (e.g. Keystone endpoint in neutron.conf)03:17
kfox1111right.03:24
kfox1111plus, there may be intermediate settings I need to be able to control.03:24
kfox1111so, endpoint that keystone thinks its listening on,03:24
kfox1111might be frontended by an external lb,03:24
kfox1111which nova would talk to.03:24
kfox1111so a global default, which is overridable at an individual package level would be ok.03:24
*** jtriley has joined #openstack-kolla03:25
alanmeadowsI wanted to empower helm to generate endpoints, that helps drive keystone bootstrapping (which requires them as input) and is a lightweight way for things to build them (template vs keystone query)03:26
alanmeadowsGranted those endpoints might actually be external e.g lb and that's fine but I wanted helm to be aware03:26
kfox1111I'm good with that. I don't want to criple helm based orchestration.03:27
kfox1111I just can't use it myself, so I don't want to be cripled by needing it.03:27
kfox1111I think we can come up with something that should work for both.03:32
kfox1111alanmeadows: do you know, with helm, if you instantiate a package with var override,s and then upgrade it, do the overridden vars stick?03:34
kfox1111or do they need to be respecified?03:34
alanmeadowskfox1111: actually didn't test that interesting to find out -- my guess is it stores them03:36
kfox1111I hope so.03:36
kfox1111it would be interesting to make confimap micropacakges too,03:36
kfox1111then reference a particular version with the microservice package.03:37
kfox1111for rolling updates, you would upgrade a configmap package, then update the vars on the microservice pacakge to point to the new configmap package.03:37
*** jtriley_ has joined #openstack-kolla03:38
*** jtriley has quit IRC03:41
jascott1im pretty sure I caught in #helm that it does store the values03:41
alanmeadowsSounds like you don't trust rollback :) isn't this the inherent functionality your suppose to get with helm upgrade and proper manifests that do rolling container upgrades though based on the iterative change, e.g config map update or maybe I'm missing something?03:44
jascott1thats the sell03:44
jascott1afaik03:44
jascott1my helm is busted atm but you can do helm get values <release name>03:44
jascott1portdirect I am not using 1.5 anymore since I switched to the vagrant deploy03:45
jascott1oh wai03:46
portdirectjascott1: I've made a gist to go through the setup I'm using: https://gist.github.com/intlabs/9ce71a4a6b93b4e2e90faec500ef70d003:48
jascott1ya I just saw that vagrant is using 1.503:48
portdirectalanmeadows: what version of k8s are you running with helm?03:49
*** jtriley_ has quit IRC03:53
*** Jeffrey4l has quit IRC03:54
*** Jeffrey4l has joined #openstack-kolla03:55
kfox1111alanmeadows: its not that I don't trust rollback. (though, questionable).03:56
kfox1111its one of who builds/ships/tests what, and what gets upgraded/applied when.03:56
kfox1111templates should be buildable/testable/shippable as an upstream.03:57
kfox1111say, I pay (insert name here) to support kolla-kubernetes helm package.03:57
kfox1111I should be able to helm repo add url-tosupport-repo03:57
kfox1111upgrades should come from them.03:57
kfox1111configmaps though, are very particular to my site.03:58
kfox1111more oddball then helm can ever be customizable to generate.03:58
kfox1111I do really like the atomicness of k8s.03:58
kfox1111so it is kind of bad to upload the configmap as x, then update it to x+1 and have half the cluster pods with the old config and half with the new, with no way to know the idfference.03:59
*** yuanying has joined #openstack-kolla03:59
alanmeadowsportdirect: 2.0.0rc204:00
portdirectalanmeadows: sorry k8s, not helm04:01
alanmeadows1.5.0beta1 tag - oldest with rbd dynamic pvc support04:01
jascott1ya 1.5beta1 was causing my pain. 1.4.6 working fine04:02
alanmeadowsThey changed a lot, including the client interface04:02
alanmeadowsMake sure to upgrade kubectl with it or things will be super weird04:02
kfox1111alanmeadows: did dynamic pvc for ceph make it finally in 1.5?04:02
*** mdnadeem has joined #openstack-kolla04:03
alanmeadowsIt did, we're using it to run aic-helm mariadb clusters per the readme04:03
alanmeadowsWorks like a....'charm' ?04:03
kfox1111nice. :)04:03
kfox1111I'll have to have a look at that. :)04:04
portdirectkfox1111: this image - quay.io/attcomdev/kube-controller-manager:v1.5.0-beta.104:04
alanmeadowsRequires some further finagling again in the readme04:04
kfox1111using petsets or individual instances?04:04
alanmeadowsYes that :)04:04
portdirectworks well :)04:04
*** f13o has quit IRC04:05
alanmeadowsIndividual instances, namely helm ranges around values.replicas * pod+pvc+pv to get mariadb-0 and so on04:05
portdirectthough I've not manged to get helm working with 1.5 - tiller crashes everytime i try and install a chart04:05
portdirectothers have reported the same on slack and github04:05
alanmeadowsPet sets is foobar'd in 1.5 pre ga release as they are renaming to state full set and helm is pinned to 1.4.1 client lib04:06
portdirecti'm talking *any* chart04:06
alanmeadowsHmm working for us.... that's strange  I can do a helm version for you tomorrow typing from my phone04:06
kfox1111alanmeadows: ah. ok. wondered about that.04:06
alanmeadowsI have a helm issue open for 1.5/statefulset support :)04:07
alanmeadowsI tried my hand at doing it but the interface changed quite a bit04:07
portdirectnp - that would be sweet - I've been running your controller=manger image with k8s 1.4.6 without any obvious side effects - but thats a recipy for sadness just waiting to happen.04:08
*** tonanhngo has joined #openstack-kolla04:08
alanmeadowsHehe04:08
alanmeadowsThis was also our first upgrade experience with kubeadm which has.... 0 upgrade support04:09
alanmeadowsThat was disappointing04:09
*** tonanhngo has quit IRC04:09
portdirectyeah - i think it'll get there but its super early days.04:10
alanmeadowsThe price of the bleeding edge!04:11
portdirectmostly painfull...04:12
portdirectanyway - better head - it's so late here it's almost early again :/04:14
alanmeadowsKfox1111: set aside some time in the AM to give your CR some proper review/comments04:14
alanmeadowsCatch you all tomorrow04:15
*** zhurong has quit IRC04:15
*** zhurong has joined #openstack-kolla04:15
*** portdirect is now known as portdirect_away04:16
jascott1have good ones04:17
*** portdirect_away is now known as portdirect04:17
*** portdirect is now known as portdirect_away04:17
*** jgriffith is now known as jgriffith_away04:21
*** tonanhngo has joined #openstack-kolla04:21
*** tonanhngo has quit IRC04:22
kfox1111alanmeadows: awesome. thanks. talk to you tomorrow.04:31
duonghqsdake_, ping, can you check the rabbitmq-server version in centos:7 image04:36
sdake_duonghq lots o people in channel :) - need to do review for jeffrey4l atm04:37
sdake_duonghq ok - done with that it was a 1 liner moment04:39
duonghqsdake_, I see your comment in the rabbitmq dockerfile, just want to make sure why the rabbitmq server in my setup is 3.3.5, it should be 3.604:42
sdake_rabbitmq-server-3.6.5-1.el7.noarch04:42
duonghqthank sdake_04:42
*** rock_ has quit IRC04:47
duonghqas I understand, centos:7 is using rabbitmq-server from epel repo, but it's 3.3.5, anybody can verify for me?04:52
*** Pavo has quit IRC04:58
*** jrist has quit IRC05:03
*** Pavo has joined #openstack-kolla05:03
*** tonanhngo has joined #openstack-kolla05:04
duonghqPavo,  ping05:05
*** tonanhngo has quit IRC05:06
openstackgerritMerged openstack/kolla: Bump Ubuntu cloud-archive repo to Ocata  https://review.openstack.org/40351605:09
*** kristian__ has joined #openstack-kolla05:13
*** kristian__ has quit IRC05:17
jascott1neato https://github.com/Boostport/kubernetes-vault05:24
*** JRobinson__ is now known as JRobinson__afk05:33
*** sdake_ has quit IRC05:52
*** williamcaban has joined #openstack-kolla05:54
*** sayantan_ has quit IRC05:57
*** JRobinson__afk is now known as JRobinson__06:01
*** Jeffrey4l has quit IRC06:12
*** Jeffrey4l has joined #openstack-kolla06:12
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: TEST_NO_MERGE  https://review.openstack.org/40397806:13
*** jascott1 has quit IRC06:15
*** jascott1 has joined #openstack-kolla06:40
*** kristian__ has joined #openstack-kolla06:42
*** saneax-_-|AFK is now known as saneax06:42
*** unicell has joined #openstack-kolla06:44
openstackgerritJeffrey Zhang proposed openstack/kolla: Add manila-ui in horizon image  https://review.openstack.org/40368906:44
*** unicell has quit IRC06:51
*** unicell has joined #openstack-kolla06:52
*** kristian__ has quit IRC06:52
*** JRobinson__ has quit IRC06:53
*** unicell1 has joined #openstack-kolla06:54
*** unicell has quit IRC06:56
*** Pavo has quit IRC06:58
*** Pavo has joined #openstack-kolla07:03
openstackgerritJeffrey Zhang proposed openstack/kolla: Use Dockerfile customization instead of include_header  https://review.openstack.org/40404907:09
*** kristian__ has joined #openstack-kolla07:13
openstackgerritMerged openstack/kolla: Updated from global requirements  https://review.openstack.org/40077007:20
*** yuanying has quit IRC07:20
*** pcaruana has joined #openstack-kolla07:21
*** f13o has joined #openstack-kolla07:25
*** yuanying has joined #openstack-kolla07:26
openstackgerritEduardo Gonzalez proposed openstack/kolla: Tacker Docker configuration  https://review.openstack.org/39639107:28
openstackgerritEduardo Gonzalez proposed openstack/kolla: Add strongswan to neutron-vpn-agent source image  https://review.openstack.org/40406107:31
*** kristian__ has quit IRC07:38
openstackgerritJeffrey Zhang proposed openstack/kolla: Install cloudkitty dashboard in horizon image  https://review.openstack.org/39653507:38
*** kristian__ has joined #openstack-kolla07:40
*** zhurong has quit IRC07:40
*** zhurong has joined #openstack-kolla07:41
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Enable cloudkitty ui when enable_cloudkitty is yes  https://review.openstack.org/40352007:42
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Enable cloudkitty ui when enable_cloudkitty is yes  https://review.openstack.org/40352007:42
openstackgerritJavier Castillo Alcíbar proposed openstack/kolla-ansible: Make sure heka-ceilometer.toml manages correctly apache and openstack ceilometer logs  https://review.openstack.org/40071607:43
*** kristian__ has quit IRC07:44
*** magicboiz has joined #openstack-kolla07:44
openstackgerritMerged openstack/kolla: Remove --include-header and --include-footer parameter  https://review.openstack.org/40230907:50
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Enable cloudkitty ui when enable_cloudkitty is yes  https://review.openstack.org/40352007:53
*** zhubingbing has quit IRC07:57
openstackgerritMerged openstack/kolla-ansible: Icrease haproxy timeouts for mysql connections  https://review.openstack.org/40342807:59
openstackgerritMerged openstack/kolla-ansible: Deprecate scheduler_max_attempts option in nova  https://review.openstack.org/39901107:59
openstackgerritwangwei proposed openstack/kolla: Add the function of docker login before pushing  https://review.openstack.org/39942608:01
*** f13o has quit IRC08:03
*** shardy has joined #openstack-kolla08:07
*** matrohon has joined #openstack-kolla08:08
*** rmart04 has joined #openstack-kolla08:16
*** yuanying has quit IRC08:17
*** Serlex has joined #openstack-kolla08:23
*** egonzalez90 has joined #openstack-kolla08:39
egonzalez90morning08:39
openstackgerritMerged openstack/kolla-ansible: use uuidutils instead of uuid.uuid4()  https://review.openstack.org/39984708:40
berendtmorning08:42
egonzalez90magicboiz: ping08:45
magicboizmorning egonzalez90!08:46
magicboizmorning everyone :)08:46
duonghqmorning egonzalez9008:48
duonghqanybody deploy kolla recently and use Horizon?08:48
egonzalez90btw duonghq , your change "Fix placement of policy.json " was not applied in kolla-ansible repo due to the split08:49
duonghqegonzalez90, moment, maybe I forgot this ps08:50
duonghqegonzalez90,  https://review.openstack.org/#/c/394260/ -> it's merged before repo split08:51
egonzalez90yup, but was merged after repository snapshot, is not present the change at kolla-ansible08:53
duonghqegonzalez90, understood08:54
duonghqegonzalez90, how do I move the bug to kolla-ansible launchpad?08:55
egonzalez90done08:57
egonzalez90in also affects project button08:57
duonghqegonzalez90, thank you08:58
*** Pavo has quit IRC08:58
openstackgerritDuong Ha-Quang proposed openstack/kolla-ansible: Fix placement of policy.json  https://review.openstack.org/40409209:00
*** Pavo has joined #openstack-kolla09:03
*** jascott1 has quit IRC09:08
*** jascott1 has joined #openstack-kolla09:09
openstackgerritcaoyuan proposed openstack/kolla: Remove the "nova-network" container file  https://review.openstack.org/40409909:10
*** zhubingbing has joined #openstack-kolla09:13
*** jascott1 has quit IRC09:14
bjolomorning09:14
*** hvlad has joined #openstack-kolla09:21
duonghqmorning bjolo09:23
zhubingbingsup sdake09:26
*** gfidente has joined #openstack-kolla09:29
*** kristian__ has joined #openstack-kolla09:29
*** senk has joined #openstack-kolla09:32
*** mkoderer has joined #openstack-kolla09:37
duonghqhi zhubingbing, long time no see09:38
zhubingbinghi09:39
zhubingbingi alway on irc ;)09:39
duonghqdo you deploy Kolla recently?09:40
zhubingbingyes09:40
zhubingbinghttp://docs.openstack.org/developer/castellan/installation.html09:40
*** yingjun has quit IRC09:41
zhubingbingdo you know castellan ?09:41
*** yingjun has joined #openstack-kolla09:41
*** yingjun_ has joined #openstack-kolla09:41
*** ram___ has joined #openstack-kolla09:41
zhubingbingDo you think  castellan  should  put it in docker alone ?09:42
*** hfu has quit IRC09:42
zhubingbingor put it in barbican docker container ?09:42
*** kristian__ has quit IRC09:44
*** kristian__ has joined #openstack-kolla09:44
*** kristian__ has quit IRC09:45
egonzalez90zhubingbing: castillan has not service?09:45
egonzalez90is only a CLI?09:45
zhubingbingyes09:45
*** yingjun_ has quit IRC09:45
*** yingjun has quit IRC09:45
zhubingbingnot service!09:45
zhubingbingI am very confused;)09:46
*** kristian__ has joined #openstack-kolla09:46
egonzalez90yup, no info about that09:47
duonghqzhubingbing, sorry, but does your Horizon work normally?09:47
zhubingbinghorizon is bad09:47
*** kristia__ has joined #openstack-kolla09:47
zhubingbingCompressing... CommandError: An error occurred during rendering /var/lib/kolla/venv/lib/python2.7/site-packages/openstack_dashboard/templates/_stylesheets.html: Couldn't find anything to import: ../../mixins09:48
zhubingbingExtensions: <NamespaceAdapterExtension>, <DjangoExtension>, <CompassExtension>09:48
zhubingbingSearch path:09:48
zhubingbingon line 21 of horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface-regular.scss09:48
zhubingbingimported from line 21 of horizon/lib/roboto_fontface/css/roboto/sass/roboto-fontface.scss09:48
zhubingbingimported from line 16 of themes/material/bootstrap/_styles.scss09:48
zhubingbingimported from line 16 of themes/material/_styles.scss09:48
zhubingbingimported from line 1 of u'string:c61b5d22d54bf56c:\n    // My Themes\n@import "/themes/material/variables";\n\n// Horizon\n@import "/dashboard/scss/horizon'09:48
zhubingbingsorry09:48
*** openstackgerrit has quit IRC09:48
duonghqzhubingbing, same here09:48
*** openstackgerrit has joined #openstack-kolla09:48
zhubingbingyes09:49
zhubingbingI  thought it was my problem, so I didn't pay attention to it.09:49
zhubingbing;(09:49
duonghqroger09:50
*** kristian__ has quit IRC09:51
zhubingbingduonghq  you can make  bug in kolla-ansible09:52
zhubingbing;)09:52
*** jrich523 has quit IRC09:52
zhubingbingegonzalez90   do you think about catillan ?09:53
zhubingbing;)09:53
duonghqzhubingbing, sure09:53
*** jrich523 has joined #openstack-kolla09:54
egonzalez90but if is not a service, maybe is on the user side09:58
egonzalez90zhubingbing: i will look about castillian to give you an opinion10:00
zhubingbingroger10:00
duonghqzhubingbing, https://bugs.launchpad.net/kolla/+bug/1645650 fyi10:00
openstackLaunchpad bug 1645650 in kolla "Horizon rendering failed at Compression" [High,New]10:00
zhubingbingok perfect10:00
zhubingbingthink you very much egonzalez9010:00
egonzalez90duonghq zhubingbing is an horizon bug https://bugs.launchpad.net/horizon/+bug/164563010:03
openstackLaunchpad bug 1645630 in OpenStack Dashboard (Horizon) "Material Theme in Newton Appears to be Broken" [Undecided,New]10:03
egonzalez90not to much to do in our side10:03
duonghqegonzalez90, got it10:04
*** zhurong has quit IRC10:05
zhubingbingthinks10:05
*** jascott1 has joined #openstack-kolla10:09
*** jascott1 has quit IRC10:14
*** senk has quit IRC10:18
*** kristian__ has joined #openstack-kolla10:20
*** kristia__ has quit IRC10:23
egonzalez90zhubingbing: if I understand right what castellan is, is "like" a olso.key_manager. There is not service10:24
egonzalez90if you want to use castellan for key management in sahara, you need to pip install castellan in sahara container10:24
zhubingbingyes,10:26
duonghqbye guys10:27
zhubingbingso we should add it  in openstack base docker file ?10:27
*** duonghq has quit IRC10:27
zhubingbingbye <duonghq10:27
*** kristian__ has quit IRC10:27
*** tovin07 has quit IRC10:29
egonzalez90depends, if is going to be use by several services yes, if is only for a service not10:30
*** senk has joined #openstack-kolla10:31
*** kristian__ has joined #openstack-kolla10:31
*** jmccarthy has quit IRC10:31
*** jmccarthy has joined #openstack-kolla10:32
*** kristia__ has joined #openstack-kolla10:34
*** kristian__ has quit IRC10:34
*** yingjun has joined #openstack-kolla10:35
*** yingjun has quit IRC10:38
*** yingjun has joined #openstack-kolla10:38
*** senk has quit IRC10:41
zhubingbingroger10:42
*** yingjun has quit IRC10:43
*** ram___ has quit IRC10:44
openstackgerritMerged openstack/kolla: Support adding customized plugin to keystone image  https://review.openstack.org/40114510:45
*** kristian__ has joined #openstack-kolla10:47
*** kristia__ has quit IRC10:47
*** kristian__ has quit IRC10:49
*** Pavo has quit IRC10:58
*** Pavo has joined #openstack-kolla11:03
*** kristian__ has joined #openstack-kolla11:05
*** kristian__ has quit IRC11:06
*** zhubingbing has quit IRC11:07
*** kristian__ has joined #openstack-kolla11:15
*** kristia__ has joined #openstack-kolla11:17
*** kristian__ has quit IRC11:18
*** kristia__ has quit IRC11:21
mliima_morning guys11:21
*** kristian__ has joined #openstack-kolla11:22
*** kristian__ has quit IRC11:22
*** ram____ has joined #openstack-kolla11:25
ram____Hi all. How do I make sure that kolla is configured to deploy magnum? along with the entire openstack config setup.11:25
ram____I am new to Kolla. I want to do a small POC . I think magnum is a service we can deploy it through kolla.11:28
*** hfu has joined #openstack-kolla11:28
*** ntpttr has quit IRC11:30
*** hfu has quit IRC11:30
*** ntpttr has joined #openstack-kolla11:31
*** YefimG has joined #openstack-kolla11:33
pbourkeram____: I'm unsure how well magnum works in Kolla11:34
*** mdnadeem has quit IRC11:34
egonzalez90ram____: you need to enable heat also11:35
YefimGJeffrey4l: Hello! sdake yesterday pointed, that you have more experience with ceilometer and gnocchi. I am trying to deploy ceilometer with gnocchi backend, but the bootstrap container fails. Is this configuration even supported? Thanks!11:36
Jeffrey4lYefimG, what error message did u get?11:36
Jeffrey4lYefimG, docker logs bootstrap_ceilometer11:37
Jeffrey4lI tried this, it works.11:37
ram____egonzalez90: Oh. If we run run Kolla-build, then all openstack services can be deployed. May be not magnum service. So how do I change/modify the kolla build config file to enable magnum. can you please provide me a detailed document for that.11:38
egonzalez90ram____: when do kolla-build all openstack images are built11:39
egonzalez90then when using kolla-ansible, need to edit /etc/kolla/globals.yml and configure the services as you like11:39
*** hvlad has quit IRC11:40
YefimGAfter debugging I noticed, that the first container, that fails is gnocchi-statsd. In logs there I found: http://pastebin.com/dvPEg48T11:40
Jeffrey4lYefimG, did u enabled ceph?11:41
Jeffrey4lcould u post your globals.yml file out?11:41
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla: Update Kibana documentation  https://review.openstack.org/40372911:41
ram____egonzalez90: when we do kolla-build then magnum service image can build automatically? If it is build here only then when we run kolla-ansible deploy then it will deploy magnum service also along with openstack service right11:45
YefimGJeffrey4l: no, this is a single node all-in-out testing environment with file backend. Here is my globals.yml: http://paste.fedoraproject.org/492625/8041989011:45
Jeffrey4lYefimG, seems like the gnocchi database is not created.11:46
Jeffrey4lYefimG, have u ever destroy the openstack and try again?11:47
YefimGJeffrey4l: will do that now and let you know how it goes, thanks11:47
Jeffrey4lYefimG, ok.11:47
Jeffrey4lbtw, run kolla-ansible with -vvv parameter and log all ansible s stdout11:48
Jeffrey4lYefimG, ^^11:48
YefimGJeffrey4l: ok!11:48
egonzalez90ram____: yes, but you need to enable_magnum in /etc/kolla/globals.yml, also configure IPs, networks and so on11:49
*** mdnadeem has joined #openstack-kolla11:50
Jeffrey4lpbourke, https://review.openstack.org/403446 please review ;)11:51
openstackgerritMerged openstack/kolla-ansible: Enable ironic ui when enable_ironic is yes  https://review.openstack.org/40344611:54
*** YefimG has quit IRC11:59
ram____egonzalez90: Ok. thank you. I will try the setup.12:03
*** sdake has joined #openstack-kolla12:09
sdakemorning peeps!12:10
openstackgerritJames McCarthy proposed openstack/kolla-ansible: Add more options for cinder-backup.  https://review.openstack.org/40291212:11
*** JoseMello has joined #openstack-kolla12:11
*** jascott1 has joined #openstack-kolla12:12
*** kristian__ has joined #openstack-kolla12:12
*** kristian__ has quit IRC12:14
*** kristian__ has joined #openstack-kolla12:14
*** kristia__ has joined #openstack-kolla12:15
*** jascott1 has quit IRC12:17
*** hfu has joined #openstack-kolla12:17
*** hfu has quit IRC12:17
sdakeThe door is jammed...  "GET IT OPEN"12:18
sdakeV such a fantastic movie, did so poorly in the boxoffice12:18
*** kristian__ has quit IRC12:19
sdakesrwilkers ping - you happen to be awake at this godawful hour?12:19
*** hvlad has joined #openstack-kolla12:19
*** kristia__ has quit IRC12:21
*** harbor has joined #openstack-kolla12:21
*** harbor is now known as portdirect___12:21
*** portdirect___ is now known as portdirect__12:22
*** portdirect__ is now known as portdirect_12:23
*** senk has joined #openstack-kolla12:24
openstackgerritMerged openstack/kolla: Word choice for back end  https://review.openstack.org/39078812:25
openstackgerritMerged openstack/kolla: shared mount added for /var/lib/nova/mnt to QSG  https://review.openstack.org/40219112:26
*** senk has quit IRC12:33
openstackgerritJames McCarthy proposed openstack/kolla-ansible: Add more options for cinder-backup.  https://review.openstack.org/40291212:33
*** egonzalez90 has quit IRC12:36
*** kristian__ has joined #openstack-kolla12:36
openstackgerritcaoyuan proposed openstack/kolla: Remove the "nova-network" container file  https://review.openstack.org/40409912:40
*** pbourke has quit IRC12:42
*** pbourke has joined #openstack-kolla12:42
openstackgerritcaoyuan proposed openstack/kolla-ansible: Remove the "nova-network" from the ansible  https://review.openstack.org/40420012:44
*** mdnadeem has quit IRC12:46
*** shardy is now known as shardy_lunch12:47
*** athomas has joined #openstack-kolla12:49
*** athomas has quit IRC12:49
*** mnasiadka has joined #openstack-kolla12:50
*** athomas has joined #openstack-kolla12:50
*** hfu has joined #openstack-kolla12:55
*** athomas has quit IRC12:57
*** zhubingbing has joined #openstack-kolla12:58
*** Pavo has quit IRC12:58
*** senk has joined #openstack-kolla12:59
*** kristian__ has quit IRC13:00
*** senk has quit IRC13:02
*** Pavo has joined #openstack-kolla13:03
*** athomas has joined #openstack-kolla13:07
*** eaguilar has joined #openstack-kolla13:09
*** duonghq has joined #openstack-kolla13:11
*** athomas has quit IRC13:14
*** athomas has joined #openstack-kolla13:15
duonghqevening my friends13:21
duonghqportdirect_, are you around?13:21
duonghqwhich helm version are we using?13:21
portdirect_duonghq: hey13:21
portdirect_I'd recommend the stable 2.0.013:22
duonghqportdirect_, got it13:22
*** jrist has joined #openstack-kolla13:23
*** yingjun has joined #openstack-kolla13:25
openstackgerritJames McCarthy proposed openstack/kolla-ansible: Add more options for cinder-backup.  https://review.openstack.org/40291213:27
*** shardy_lunch is now known as shardy13:28
*** ayoung has quit IRC13:29
*** mgiles has joined #openstack-kolla13:31
openstackgerritJames McCarthy proposed openstack/kolla-ansible: Add more options for cinder-backup.  https://review.openstack.org/40291213:31
duonghqportdirect_, did you get "ProvisioningFailedcannot find volume plugin for alpha provisioning" of pvc?13:33
duonghqwhen install mariadb with helm13:33
portdirect_yeah13:33
duonghqwhat reasons can raise this issue?13:34
portdirect_thats exepcted if you are trying to install mariadb from the helm repo13:34
portdirect_https://gist.github.com/intlabs/9ce71a4a6b93b4e2e90faec500ef70d013:34
portdirect_it's because there is not support for dynamic provisioning of pvc without cloudprovider atm with stock k8s install with kubeadm13:35
duonghqseem that not only kubeadm :)13:35
duonghqkube-deploy suffer it too13:35
duonghqhelm ls work fine for me, so I guess I got dev env13:35
portdirect_if you run 'kubectl get all' and see a mariadb sevice and a pod stuck in provsioning then you should be good to go13:36
*** kristian__ has joined #openstack-kolla13:36
duonghqportdirect_,  http://paste.openstack.org/show/590811/ <- this is what I got13:37
portdirect_untill we have provisiong of volumes sorted I'd use an 'emptydir' volume as a short term workaround if you need them in your chart13:38
duonghqokay13:38
portdirect_that paste looks good - it means that helm has successfully deployed an application, but the application it's deployed is broken13:39
duonghqthank youn13:40
portdirect_you should be able to clean up your env by running 'helm delete wandering-molly'13:40
duonghqalready do that :)13:41
*** kristian__ has quit IRC13:41
*** fguillot has joined #openstack-kolla13:43
*** mdnadeem has joined #openstack-kolla13:43
*** dave-mccowan has joined #openstack-kolla13:43
*** hfu has quit IRC13:45
*** egonzalez90 has joined #openstack-kolla13:45
*** jtriley has joined #openstack-kolla13:46
*** YefimG has joined #openstack-kolla13:46
sdakeportdirect_ - need help on dev env :)13:47
sdakeportdirect_ got any advice for me13:47
YefimGJeffrey4l: Hi again! I re-deployed Kolla from scratch and got the same error with gnocchi bootstrap container. I have run deploy with -vvv, here is the full deploy.log: http://gasels.com/deploy.log13:48
portdirect_sdake - lets get you rolling again13:48
portdirect_whats up with your env? It did not seem happy at all last night13:49
Jeffrey4lYefimG, OK. checking13:50
*** kristian__ has joined #openstack-kolla13:50
kristian__Hi. Can someone help me with installing custom version of libvirt on ubuntu containers? Container ver 3.0.1 and targer libvirt 1.2.17 or 2.113:51
kfox1111morning13:52
*** yingjun has quit IRC13:53
duonghqmorning kfox111113:53
kfox1111hi duonghq13:53
*** yingjun has joined #openstack-kolla13:54
*** portdirect_ is now known as portdirect_back_13:54
duonghqalright, 3-node k8s and current memory usage is around 60%13:55
duonghqof 16GB RAM13:55
*** jtriley has quit IRC13:55
*** lamt has joined #openstack-kolla13:56
*** jheroux has joined #openstack-kolla13:58
*** jtriley has joined #openstack-kolla14:01
sdakesup kfox111114:01
sdakekfox1111 have 1-2 hours to get into the api discussion if sbezverk and portdirect_back_ are about?14:02
kfox1111yeah14:02
sdakecool lets see if they are around14:02
*** portdirect_back_ is now known as portdirect_14:03
portdirect_back14:03
*** rmart04_ has joined #openstack-kolla14:04
sdakewell we need sbezverk to make a decision :)14:04
*** rmart04 has quit IRC14:04
*** rmart04_ is now known as rmart0414:04
kfox1111yeah.14:05
*** senk has joined #openstack-kolla14:05
sbezverkgood morning kfox111: sdake:14:05
sdakesup dude14:05
sdakeok lets get into it14:06
kfox1111morning. :)14:06
kfox1111ready.... go! :)14:06
sdakeok where we are - i think is as follows14:06
sbezverkso what is new and exciting?14:06
sdakeit is clear to me that people want helm native charts14:06
sdakeit is clear to me that people want common code14:06
sdakeso yesterday we finished up on the common code values.yaml14:07
sdakeis that fair assessment?14:07
kfox1111not sure about that.14:07
sdakewhich part14:07
kfox1111I think we are mostly in agreement on needing a common macros file?14:08
sdakei'm in agreement there14:08
portdirect_yep14:08
sbezverkwfm14:08
kfox1111k.14:08
sdakeso when i said above people want- i didn't say people agreed ;)14:08
kfox1111what about common vars to go along with the common macros?14:09
sdakeok common vars14:09
sdakethis is values.yaml right?14:09
portdirect_yes - afaik14:09
kfox1111yeah. values.yaml combining multiple files.14:10
sdakecoudl you expand on that combinging part14:10
kfox1111yeah. sec14:10
sbezverkkfox1111: could you clarify which multiple files you refer to?14:10
kristian__Hi where can I fix this error when I compiled libvirt 1.2.16? http://paste.openstack.org/show/590817/14:11
portdirect_kfox1111: could I try and then you correct me?14:11
kfox1111https://review.openstack.org/#/c/396296/27/helm/src/common_values.yaml14:11
sdakeportdirect_ dont sk for permission dude ask for forgiveness :)14:11
NachoDuckHi all, is there still support for LDAP auth in Kolla, has anyone used it?14:11
kfox1111for example, that file is appended to:14:11
kfox1111https://review.openstack.org/#/c/396296/27/helm/src/neutron/values/l3_agent_daemonset.yaml14:11
*** jtriley has quit IRC14:11
kfox1111when the l3_agent package is built.14:11
kfox1111and14:11
kfox1111https://review.openstack.org/#/c/396296/27/helm/src/neutron/values/openvswitch_agent_daemonset.yaml14:12
kfox1111when openvswitch-agent is built.14:12
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Enable cloudkitty ui when enable_cloudkitty is yes  https://review.openstack.org/40352014:12
kfox1111so the vars for the common stuff is defined just once, in the common vars file.14:12
sdakeok seems like a worthwhile thing to have14:12
sdakethe common vars part ;)14:13
sbezverkkfox1111: in general there will be just 2 logical type of variables: common and microservice specific right?14:13
kfox1111sbezverk: at the microservice level, yes.14:13
kfox1111when combined into service packages, no.14:13
*** senk has quit IRC14:13
sdakeok lets focus on microservice level at present14:14
sdakethinking about all the rpoblems is npcomplete ;)14:14
kfox1111sdake: the distinction is important as it determines if package vars, or globals should be used.14:14
*** jascott1 has joined #openstack-kolla14:14
*** yingjun has quit IRC14:14
Jeffrey4lYefimG, which branch code are u using?14:14
*** yingjun has joined #openstack-kolla14:15
*** v1k0d3n has quit IRC14:15
*** v1k0d3n has joined #openstack-kolla14:15
sbezverkkfox1111: I would agree with sdake to go by layer, it is easier imho14:17
kfox1111k14:17
sbezverkstarting from ground up14:17
sdakekfox1111 tbh you just melted my brain with that statement ;)14:17
sdakekfox1111 so lets learn this together - since you have context I dont :)14:18
sdakeone layer at a time14:18
kfox1111we'll table it for now.14:18
sdakesounds good14:18
kfox1111k.14:18
YefimGJeffrey4l: I am using 3.0.1 from docker hub14:18
sdakeok so back on the variables14:18
sdakecommon and microservice specific14:18
Jeffrey4lYefimG, docker logs bootstrap_gnocchi, what u get?14:18
*** jascott1 has quit IRC14:19
*** yingjun has quit IRC14:19
sdakeseems like this is doable in many different ways14:19
YefimGJeffrey4l: http://paste.fedoraproject.org/492994/80429173 (I am rebuilding with Ceph now)14:19
sdakei'd like to keep a helm-native packaging approach if at all possible14:19
sdakethis is something i personally want14:19
kfox1111sdake: not sure thats true.14:20
kfox1111if they are to be done as package vars, they have to be in variables.yaml.14:20
sdakekfox1111 not sure which is true14:20
kfox1111and there is only one file.14:20
kfox1111and its not templated. :/14:20
sdakeok templating - we can tackle next :)14:20
pbourkeberendt: ping14:20
sdakealanmeadows listed out 3 approaches yesterday14:21
berendtpbourke: pong14:21
sdakeare there any others?14:21
pbourkeberendt: could you fix up https://review.openstack.org/#/c/329487/ for merge?14:21
portdirect_not that im aware of14:21
sdakenone of those approaches provide native helm implementation14:21
Jeffrey4lYefimG seems there are some bug in centos+binary. checking14:21
kfox1111sdake: yeah.14:21
kfox1111but,14:21
portdirect_no :( the makefile solution they are using is probably the closest14:21
kfox1111something that could pretty easily be added to helm though I think.14:22
kfox1111all they need is like a vars.d magicdir.14:22
sdakeso i am working on combining native helm + our requirements for global and local variables14:22
sdakeyup but we can't wait on our upstreams14:22
kfox1111right.14:22
sdakewe chose our dependencies, we have to suck it up with what they deliver to us14:22
kfox1111I'm pretty sure its either or. :/14:22
kfox1111until helm matures.14:22
sdakeok so I kind of hda this wierd drema last night14:22
*** huzhengchuan_ has joined #openstack-kolla14:23
sdakeits a rift on your idea kfox111114:23
sdakei wont get into the wierd part of it14:23
sdakesince thats rated R:)14:23
kfox1111:)14:23
portdirect_oh god14:23
sdakeor probably X:)14:23
openstackgerritChristian Berendt proposed openstack/kolla: Install neutron-lbaas plugin in neutron-server container  https://review.openstack.org/32948714:23
Jeffrey4lYefimG, it is a bug in 3.0.1 . it is fixed on master ;(14:23
sdakeanyway14:23
sdakeback on topic14:23
*** mdnadeem has quit IRC14:23
sdakepart of that was the idea of a compiler14:23
berendtpbourke: done14:24
pbourkeberendt: thanks!14:24
pbourkeJeffrey4l: sdake: small review for approval https://review.openstack.org/32948714:24
sdakesomething that reads the helm files (pre-checkin) and builds the values.yaml file14:24
sdakethis would be a new option that is unexplored14:24
Jeffrey4lYefimG, two option. 1 build centos+binary using branch code   2. use centos+source.14:24
kfox1111pre-checkin?14:24
sdakeit would result in duplication14:24
kfox1111you mean git?14:24
sbezverksdake: I think this could work with native charts too14:25
sdakeya you run the compiler - it reads the template - it spits out a values.yaml - you check that into git14:25
Jeffrey4lpbourke, done. waiting for the gate.14:25
kfox1111oh....14:25
sbezverksdake: when you need to change variable?14:25
portdirect_ok - why pre git?14:26
kfox1111thats putting built things in git.14:26
sdakeportdirect_ that provides helm-native14:26
sdakejust values.yaml14:26
sdakenot hte whole pakage itself14:26
kfox1111yeah, helm native, but breaks a cardinal source code revision rule.14:26
YefimGJeffrey4l: good, thanks, will clone the master and build my own images and deploy kolla. Thanks! By the way, speaking of gnocchi, is it faster then ceilometer + mongodb? The ceilometer + mongodb was terribly slow last time I used it :(14:27
portdirect_i see - this works for that but sbezverk's point is where my concern come from here14:27
Jeffrey4lYefimG, yes. it is faster. and you can try gnocchi+ceph , it is more better ;)14:27
YefimGJeffrey4l: Thank you very much!14:27
Jeffrey4l;)14:27
kfox1111hmm...14:28
*** krtaylor has quit IRC14:28
sdakeportdirect_ i dont follow14:28
kfox1111my initial reaction is it feels a bit slimy. but, it would be a stop gap until helm supports templating.14:28
sbezverkportdirect_: sorry man which concern you are refering too, I had and lost so many it is hard to track ;-)14:28
portdirect_"sdake: when you need to change variable?"14:29
kfox1111so, I'm not against it.14:29
*** fguillot has quit IRC14:29
sbezverkportdirect_: got it, it was not a concenr, just question14:29
kfox1111sdake: question. would it be good to do the same for the docker containers?14:29
portdirect_sorry phrasing :)14:29
kfox1111prebuild the dockerfiles and check them into kolla so docker builds just work?14:29
sdakekfox1111 actually we did this same thing for docker containers :)14:29
sbezverkI think since this file is checked in, you could edit it manually and then check back in14:29
sdakeat one point in our history14:30
kfox1111sbezverk: thats the danger in the aproach.14:30
sdakenah rerun compiler14:30
kfox1111sdake: yeah, but if someone does it not knowing its a built file, then the nextg person rebuilding might drop the changes.14:30
kfox1111by mistake14:30
sbezverkkfox1111: that was just a thought, re-run looks doable from my point of view too14:30
sdakethat is what the 2 +2 gating is all about :)14:31
kfox1111sdake: k14:31
kfox1111sbezverk: yeah.14:31
portdirect_oh if we can do that - and changes ripple thorugh a checked out repo, then I'm down with it14:31
portdirect_could we create a gate that checked the default values dont change?14:31
kfox1111portdirect_: probably a gate taht does a 'make clean; make; git diff'14:32
sdakeok so there is helm native + global variables + local variables14:32
kfox1111if values change, then someone edited the wrong file.14:32
sdakeya linting that is easy -we also followed htis pattern in kolla early on (the linting part)14:32
kfox1111sdake: built charts, but prebuilt in the repo so helm native works out of the box.14:32
sbezverkportdirect_: what if we need to change defaults? would it not be more important to check if with new global variables it gets built/deployed?14:32
kfox1111sdake: but.14:32
kfox1111I'm not agreeing fully to it yet. just that this one use case is covered by that idea.14:33
kfox1111lets make sure it works with the rest.14:33
*** inc0 has joined #openstack-kolla14:33
sdakewhich rest, you mean services?14:33
inc0good morning14:33
v1k0d3nportdirect_: you there?14:33
sdakesup inc014:33
portdirect_sbezverk: then we would need to change the gate - a bit crusty but they should not change oftern14:34
kfox1111sdake: no. just the other pieces of the puzzle. we need to poc it and make sure it doesn't have any hiden gotchas.14:34
v1k0d3nlooking at your changes right now, and going to going to dive in a bit on this today.14:34
portdirect_v1k0d3n: hey man14:34
sdakekfox1111 right - so compiler idea14:34
sdakecomplicated14:34
sdakeis there a gotpl parser for python14:34
sdakedoubt i t14:34
kfox1111not taht I know of.14:34
sdakei could write a parser14:34
sdakei could write a compioelr14:34
inc0kfox1111, sdake v1k0d3n can you bried me on problem please?14:35
sdakeit would tkae a couple weeks14:35
kfox1111we could build one, but then would need go source in our repo.14:35
sdakei'd rather move faster14:35
inc0no...let's *not* write template parser14:35
sdakekfox1111 right - not going there14:35
sdakeinc0 please read scrollback14:35
kfox1111yeah. don't think we want to go there.14:35
v1k0d3ninc0: what's up man?14:35
kfox1111don't think we need much out of the build step either.14:35
sbezverksdake: question, if the compiler only deals with values.yaml which is native yaml, why would you need gotpl parser?14:35
kfox1111right now I was able to do everything I need to with a simple append or a str replace.14:35
sdakesbezverk to read the daemonset.yaml gotpl stuff14:36
kfox1111values, and chart too.14:36
*** krtaylor has joined #openstack-kolla14:36
kfox1111some kind of easy to manage version numbering system will be important too I think.14:36
v1k0d3ninc0: what do you mean by " bried me on problem please"?14:36
sbezverksdake: kfox1111: to get list of varibles used in the template and then build values.yaml for these varibles?14:37
inc0v1k0d3n, writing is hard - brief me on problem14:37
*** jascott1 has joined #openstack-kolla14:37
v1k0d3nportdirect_: have a feeling that the changes may not work on ubuntu...but i can change that.14:37
kfox1111sbezverk: yeah, for values. (if I understand the question right)14:37
inc0I barely waken up but already see argument14:37
v1k0d3ninc0: not sure of a problem. is there a problem?14:37
v1k0d3ni just got on.14:37
sdakeinc0 we are not arguing at all14:37
v1k0d3nwell...just started getting spun up i mean.14:38
kfox1111inc0: not argument. working on concensus on an architectural issue.14:38
portdirect_v1k0d3n: no probs - thought there might be a few issues14:38
sdakeinc0 we are working together -there is a difference14:38
sbezverkkfox1111: that is right, that was my question..14:38
v1k0d3nportdirect_: should be pretty easy.14:38
v1k0d3nshould have in a little bit.14:38
inc0fine...what are you working together on then? can I join?;)14:38
sdakeinc0 absolutelly14:38
sdakeread scrollback :)14:38
v1k0d3ninc0 kfox1111 sdake what is the issue?14:38
sdakeinc0 peoples brains are loaded with  state atm14:38
sdakeyou need to load yours14:38
sdakev1k0d3n scrollback ;)14:39
sbezverkkfox1111: I like this idea, it will generate very optimal values.yaml. I just hope it will not be super complicated to write it..14:39
v1k0d3nkfox1111 are you talking with alanmeadows on our side?14:39
*** dasm has quit IRC14:39
sdakeok guys - compiler = pita14:39
sdakeanything simpler?14:39
v1k0d3ni think a lot of the issues we have worked out, or have workarounds for now...knowing that some things will clean up soon.14:39
*** rhallisey has joined #openstack-kolla14:39
kfox1111v1k0d3n: yeah. talked with him for a while. both on the same page.14:40
v1k0d3nok cool14:40
sdakev1k0d3n we are on to a new pattern alanmeadows hasn't explored ;)14:40
sbezverkwhat about to have global values.yaml with sections per microservice?14:40
v1k0d3nhopefully we're working similar paths?14:40
sbezverkexample:14:40
sbezverkopenvswitch-ovsdb:14:40
kfox1111sdake: I'd say its the same pattern but a slightly different workflow.14:40
sbezverk- variable-1: "blah"14:40
kfox1111the build step is pushed before checkin rather hten after checkout.14:40
v1k0d3nsdake: that's why i asked if people are syncing up with him...14:40
sdakekfox1111 fair enough14:40
portdirect_v1k0d3n: yeah allanmeadows was really helpful14:41
kfox1111but architecturally is the same.14:41
inc0sbezverk, this file will be hard to maintain14:41
sdakeits helm native - i think that is one big architectural difference ;)14:41
sdakebut thats besides the point :)14:41
*** Marcellin__ has joined #openstack-kolla14:41
kfox1111sbezverk: thats possible, but might require a more complicated engine to parse out the irelevent bits?14:41
sbezverkinc0: we already have something similar in kolla-kubernetes service registry file14:41
v1k0d3nsdake: that is only a small part of a much larger open field honestly.14:41
v1k0d3nit's a good start.14:41
YefimGJeffrey4l: I am sorry for the lame question, but how do I correctly install kolla from the master branch? I have cloned it, installed dependencies, installed kolla (pip install kolla/), but it doesn't have anything else but kolla-build and it doesn't work.14:42
kristian__How can I install libvirt 2.1 on ubuntu kolla?14:42
*** jascott1 has quit IRC14:42
v1k0d3nbut after that...it can sprawl pretty significantly.14:42
Jeffrey4lYefimG, you can try centos+source + 3.0.1 now.14:42
Jeffrey4lnormally, source is well tested.14:42
sdakesbezverk ok file - lets focus on digging into that14:42
inc0YefimG, kolla will only have kolla-build, kolla-ansible will have deploy14:43
sdakehard to maintain - who cares14:43
inc0separate project now14:43
Jeffrey4lYefimG, for install from master branch, you can use ./tools/kolla-build.py script.14:43
sbezverkkfox1111: I am not sure it will add complexity, because to generate per microservice values all you need is to copy relevat section14:43
sdakeinc0 separate deliverable14:43
sbezverkto local micsroservice values.yaml14:43
kfox1111sbezverk: the complexity is in parsing. right now, I just append some files together and do str replace. thats simpler then doing some kind of switch in the file?14:44
YefimGJeffrey4l, inc0: Thank you, will try that.14:44
kfox1111we could use jinja2 for that. but thats more complicated.14:44
portdirect_but we would only need to modify the values.yaml on a 2nd run wouldnt we?14:44
kfox1111I'm ok with it. just want people to understand/accept the complexity.14:45
kfox1111as people were worried about the append/sed being complex.14:45
sdakekfox1111 ok - so helm native14:46
sbezverkkfox1111: sdake: maybe we could list possible scenarios of workflow to better understand complexities.14:46
kfox1111sbezverk: yeah. good idea14:46
sdakeok workflow I see is this14:46
sdake1. dev creates a new chart14:47
sdake2. dev adds values to some global file somewhere that contains the values that should be yaml.loads()'ed and chopped up into a values.yaml in 114:47
sdake3. dev runs some type of tool that does the chopping14:47
sdake3 = not a compiler but a simple parser14:48
sdakeanother workflow14:48
sdake1. dev modifies a chart14:48
sdake2. dev adds values to some global file somewhere just like 214:48
sdake3. dev runs some type of tool thatdoes the chopping14:48
kfox1111yeah.14:49
sdakeso its the same workflow?14:49
sbezverksdake: make sense, in 3 chopping is done only on values.yaml file right?14:49
sdakewith 1 being a delta14:49
kfox1111yeah. if you make any changes to vars, then you run the tool.14:49
*** srwilkers_ has joined #openstack-kolla14:50
kfox1111sbezverk: I'd kind of like to see it done with charts too.14:50
sdakeand if someone makes changes to vars manually the linting -1's their patch14:50
kfox1111bumping a version should be easy for an op to do.14:50
sbezverkkfox1111: not sure about you but I could live with running tool when value needs to be changes since it does not change too often14:50
kfox1111I like your single file idea. what about putting all the package version numbers in one file?14:50
kfox1111sbezverk: me too.14:50
portdirect_I could live with that as well14:51
kfox1111sbezverk: it being yaml solves the parsing complexity too.14:51
*** rmart04 has quit IRC14:51
sbezverkwow we are getting somewher ;-)14:51
kfox1111you just select the root level key for your package, and common.14:51
kfox1111easy to parse...14:51
*** lrensing has joined #openstack-kolla14:51
v1k0d3nsdake: to be honest...we're doing everything via jenkins builds...and we're providing that as a helm chart.14:52
kfox1111v1k0d3n: yeah. thats one of hte use cases I'm shooting for.14:52
kfox1111having it easy for a ci/cd bump versions of charts.14:52
v1k0d3nso jenkins fires up a kubernetes node for testing, building, etc.14:52
sdakev1k0d3n np-complete problem :)14:52
YefimGJeffrey4l: sorry, but what do mean by centos+source?14:52
*** rmart04 has joined #openstack-kolla14:52
sdakev1k0d3n i am solving an O(n) problem atm :)14:52
*** srwilkers has quit IRC14:53
kfox1111thats why I think we need to template the chart.yaml too14:53
*** srwilkers has joined #openstack-kolla14:53
v1k0d3nok...i'll back down then.14:53
sdakesup srwilkers14:53
kfox1111(until helm gets a command line override for version number)14:53
sdakeMarcellin__ was looking for ya14:53
v1k0d3ni'll be around if anyone pings me. can't watch IRC though...14:53
sdakeok so back on the api14:53
sdakev1k0d3n roger that - we should be done shortly nayway14:53
sdakedoes this deliver an api that is stable?14:54
*** srwilkers_ has quit IRC14:54
portdirect_i think it could14:54
kfox1111sdake: I think so, provided we're careful not to rename vars too.14:54
*** srwilkers_ has joined #openstack-kolla14:54
sdakeapi wins all arguments here14:54
sdakeso if it doesn't this solution isn't viable14:55
sbezverkkfox1111: what exactly you want to change in chart?14:55
kfox1111sbezverk: just the version number.14:55
sbezverkkfox1111: let me re-phrase do you mean Chart.yaml ot template?14:56
kfox1111I'd like it to be very easy to release updated versions.14:56
*** srwilkers has quit IRC14:56
kfox1111Chart.yaml contains the version number.14:56
*** srwilkers has joined #openstack-kolla14:56
srwilkers_hey everyone -- hope you had a decent enough holiday14:56
sdakesrwilkers_ welcome back14:56
sdakesrwilkers_ Marcellin__ was looking for you14:56
sdakesrwilkers_ i think he mentioned something about taking over the documentation blueprint you had14:57
sbezverkkfox1111: ah, got it, sure thing.. if it makes your life easier and not break any native support I do not see why not!14:57
sdakenot sure, you will have to tlak to him - feel freee to use the channel :)14:57
kfox1111cool.14:57
sdakeok well i'm not totally up to speed on the Chart.yaml thing14:58
portdirect_I concurr - so we limit the files the parser touches to varibles.yaml and Chart.yaml?14:58
sdakei'll take on implementing this parser14:58
sdakesince i'm dead in the water without a dev environment anyway14:58
*** Pavo has quit IRC14:58
sdakewhat shall we call the tool14:58
sdake"chop"? :)14:58
kfox1111portdirect_: +1. I think thats all thats needed. the rest helm can deal with.14:59
kfox1111sdake: I think the build tool from my review is pretty close already.14:59
sbezverkportdirect_ +114:59
sdakekfox1111 you want to tackle it then?14:59
kfox1111I think theres one more thing to talk through?15:00
sdakeok before we get on to the next thing15:00
sdakewhatever tht may be ;)15:00
kfox1111k.15:00
sdakeare we in general agreement this approach is better then others - it sort of checks all the tickboxes everyone wants15:00
kfox1111sdake: yeah. I can make a few tweaks and get it into the agreed aproach this morning I think.15:00
sdakekfox1111 fantastic15:01
portdirect_sdake: I'm a happy camper atm15:01
sdakeit would take me a couple days15:01
sdakesbezverk do you agree with approach?15:01
kfox1111sdake: I'll let you know when its ready, then you can double check it for me?15:01
sbezverkkfox1111: you will change templates to be native templates and not macros right?15:01
sdakekfox1111 just push it in review queue15:01
sdakekfox1111 then everyone can doublecheck it :)15:02
kfox1111sbezverk: want to be extra sure what your talking about. you talking about the common_main thing from my review?15:02
*** Pavo has joined #openstack-kolla15:03
portdirect_sbezverk, kfox1111: yeah it would need to use common templates and dir structure, so the only 'non' standard part was values.yaml15:03
sbezverkkfox1111: each your microservice template starts with {{ define "blah" }} which makes is as a macro, helm does not use it in this way as it needs to be included somewhere15:04
sdakeportdirect_ nah values.yaml would be standard because it was checked into rpeo that way15:04
kfox1111sbezverk: that is actually a helm native thing.15:04
portdirect_and even that should be standard (damn stake you beat me)15:04
sdakeagree helm native15:04
*** TxGirlGeek has joined #openstack-kolla15:04
sbezverkkfox1111: right but it requires additinal manipulation by your build tool15:05
kfox1111helm is parsing the macro.15:05
kfox1111it requires one file, common_main to be added to the chart.15:05
kfox1111and that one file can contain all the common var building logic.15:05
kfox1111so, for example, kollaToolboxImageFull needs to be built and used in a lot of templates.15:05
kfox1111that var building can either be copy pasted into all of the templates, or put in one place.15:06
sbezverkkfox1111: I thought we agreedd that all common variables will be in values.yaml file15:06
kfox1111sbezverk: there are two parts to it.15:06
sdakesbezverk you mean a global-values.yaml15:06
kfox1111variable defintions. thats what variables.yaml is for in helm.15:06
kfox1111then there is logic. like:15:07
kfox1111{{- $kollaToolboxImageBuilt := printf "%s/%s/%s-%s-kolla-toolbox:%s" .Values.docker_registry .Values.docker_namespace .Values.kolla_base_distro .Values.kolla_install_type .Values.kolla_toolbox_image_tag }}15:07
kfox1111{{- $kollaToolboxImageFull := .Values.kolla_toolbox_image_full | default $kollaToolboxImageBuilt }}15:07
sbezverksdake: the problem to make kfox1111 temaplate to be deployable by helm it rquires manipulation with temaplte15:07
kfox1111kind of a common-lib kind of thing,15:08
kfox1111but helm does not allow a macro to return anything.15:08
kfox1111:/15:08
sbezverkkfox1111: why we cannot use _helper.tpl for common code?15:08
portdirect_^^15:08
kfox1111sbezverk: because vars are one directional.15:08
kfox1111from caller to callee.15:08
kfox1111so if you define kollaToolboxImageFull in _helper.tpl,15:08
kfox1111then the main template can't use it for its init container.15:09
kfox1111it has to build the variable itself.15:09
*** jtriley has joined #openstack-kolla15:09
kfox1111its a current helm limitation. :/15:09
sdakeok so does that mean your proposing having a diferent workflow then the two i listed above?15:09
kfox1111uness we can find a different workaround.15:09
*** Jeffrey4l has quit IRC15:09
portdirect_I think we just need to accept that - and have templates that are a bit less DRY than you would like - as otherwise we are moving awa from sdakes suggested workflow i think15:10
kfox1111sdake: not really? its just a proposal to have the build tool drop in one more file.15:10
sdakeok lets dig into that kfox111115:10
kfox1111it has the build tool drop in https://review.openstack.org/#/c/396296/27/helm/src/common_main.yaml15:10
sdakesounds promising15:10
sbezverkkfox1111: but this file is code file not variables/values15:10
kfox1111and then wrap the main template in a macro.15:11
kfox1111everything else is the same.15:11
kfox1111sbezverk: true.15:11
sbezverkit means any changes in code would require to run tool again15:11
kfox1111but its copied verbatim.15:11
kfox1111true.15:11
sdakechanges in which code15:11
kfox1111but would we do the same for common lib?15:11
sbezverkhow then it is native to helm?? I fail to see15:11
alanmeadowsis this just about yaml merging some top level input?15:11
sdakerun which tool15:11
kfox1111we have to copy _helper.tpl in to the package too, which then has the same issue there too.15:12
kfox1111if you change the common code, you have to run the build tool again to copy it everywhere.15:12
sbezverkkfox1111: it is done only once15:12
sdakekfox1111 right - to copy that _helper.tpl is easy - its a find operaiton away to resync the whole tree15:12
kfox1111sbezverk: same with common_main.yaml?15:12
*** jtriley has quit IRC15:12
inc0alanmeadows, as I'm trying to follow this discussion, it seems that's it's about reusing a variables across multiple charts15:12
inc0which helm doesn't feel like doing15:13
kfox1111the tool builds variables.yaml and charts.yaml (version only), then drops in common_main and common_lib ?15:13
kfox1111inc0: right.15:13
alanmeadowsagain separating out values from defines you can merge even in a helm native way without an uber chart15:13
inc0can helm templates be rendered with more than one yaml or that's the problem?15:13
alanmeadowshelm install --values=global-uber-values-to-merge-in.yaml foo/bar --namespace=blah15:13
sbezverkbuilding variables/values/code file on the fly does not sounds as good approach15:13
kfox1111inc0: helm templates can, but vars are one direction.15:14
inc0kfox1111, what do you mean by one direction?15:14
sdakekfox1111 that seems workable - if the tool only needs to be run once - pre commit15:14
*** jtriley has joined #openstack-kolla15:14
kfox1111inc0: in gotl a template can define vars, but can't return them to the parent.15:14
sdakekfox1111 i'd encourage you to simplify things into multiiple patches if your going to do the implementation15:14
kfox1111sdake: yeah. onece on precommit.15:14
kfox1111sdake: I can do that.15:15
sdakekfox1111 one for values.yml15:15
sdakethen add on each patch from there15:15
sdakei understand your idea15:15
inc0kfox1111, but don't we define variables in yaml?15:15
sdakewhen its mixed up in one big ball of tool its hard to understand ;)15:15
kfox1111inc0: two different pieces.15:15
kfox1111vars are defined/defaulted in variables.yaml.15:15
kfox1111logic in the templates can devine other vars based on them.15:16
kfox1111so, templates can do this:15:16
kfox1111{- $kollaToolboxImageBuilt := printf "%s/%s/%s-%s-kolla-toolbox:%s" .Values.docker_registry .Values.docker_namespace .Values.kolla_base_distro .Values.kolla_install_type .Values.kolla_toolbox_image_tag }}15:16
kfox1111{{- $kollaToolboxImageFull := .Values.kolla_toolbox_image_full | default $kollaToolboxImageBuilt }}15:16
kfox1111and then use $kollaToolboxImageFull15:16
inc0ahh I understand, in ansible we do have jinja2-based yamls15:16
kfox1111but that can't be done in an included file.15:16
kfox1111right.15:16
kfox1111hmm....15:16
kfox1111though...15:17
inc0we could use genconfig15:17
kfox1111a macro can return just some text...15:17
inc0kinda15:17
sdakelets keep it simple to start plz :)15:17
kfox1111and I don't think we really need the var to be non text for the common bits...15:17
alanmeadowskfox1111: thats what we''re doing15:17
kfox1111so we could maybe just make a macro15:17
kfox1111that returns the kollaToolboxImageFull value,15:17
kfox1111then call it inline.15:17
sdakekfox1111 question15:18
kfox1111the template will look a bit uglier, as its calling a macro, not a var.15:18
kfox1111but wouldn';t need the common_main thingy.15:18
kfox1111I can prototype that...15:18
kfox1111sdake: sure.15:18
sdakekfox1111 i htink we are in agreemenet on a global-variables.yml file that gts chopped up15:18
kfox1111alanmeadows: have an example?15:18
alanmeadowsto be sure though what I am thinking is _common.tpl includes common macros that really are macros, for actual strings that belong in yaml for chart straddling values I am leaning toward requiring helm install --values=aic-helm-big-default.yaml ...15:19
kfox1111sdake: yeah.15:19
alanmeadowshttps://github.com/att-comdev/aic-helm/blob/master/openstack-base/templates/_hosts.tpl15:19
alanmeadowsfqdn in that case15:19
alanmeadowsif I am following what you are saying15:19
alanmeadowsbut there is no reason that cant be in15:19
sdakekfox1111 the idea is helm native - what i'm not clera on with your approach is do you plan to render a complete helm file?15:19
kfox1111alanmeadows: then you include them?15:19
sbezverkalanmeadows: multiple file can be specified in command line?15:19
sdakea complete helm subtree15:20
kfox1111brb.15:20
alanmeadowskfox1111: right15:20
alanmeadowssbezverk: reading through https://github.com/kubernetes/helm/blob/62df1ad3588e8d4791423aec19d46bc383438c4f/pkg/chartutil/values.go#L131-L16315:20
alanmeadowsseems to merge, priority given to --values=... not sure about multiples15:20
*** senk has joined #openstack-kolla15:20
sbezverkalanmeadows: that is for multiple layers15:21
sbezverkalanmeadows: but then to access them they must be defined as global, is it not the case ?15:21
*** huzhengchuan_ has quit IRC15:22
alanmeadowswhy would they need to be globals?15:22
kfox1111alanmeadows: nice.15:22
alanmeadowscoalesce seems to me to merge it directly into the namespace15:22
kfox1111alanmeadows: that eleviates the need to do the common_main thing I was doing.15:22
kfox1111coalesce?15:22
sdakekfox1111 ok so before  we go chase more shinies :)15:23
sbezverkalanmeadows: when I tried to do that, it was not rendering values if variable was not defined at the same level as template15:23
sdake(my daughter is a fan of pokemon if you didn't get the shinies rreference)15:23
*** saneax is now known as saneax-_-|AFK15:23
*** mnasiadka has quit IRC15:24
sdakelets focus on our immediate problem - which is helm native + API15:24
*** cliles has quit IRC15:24
*** bmace has quit IRC15:24
sdakethe API problem raised is solved by chopping up a global-values.json15:25
kfox1111sbezverk: he found a way to do it with amacro instead of a var.15:25
sdakethis also solves the helm native problem15:25
kfox1111with an {{include macroname}} instead of "{{$varname}}"15:25
sbezverkkfox1111: Just to be clear, the only reason I am being pain is because I want to preserve two options of deploying chart without any additional twiking. your approach force to do it, which makes me feel very uncomfortable..15:25
*** cliles has joined #openstack-kolla15:25
sdakesbezverk hows that?15:26
kfox1111I think we're down to just common_lib now.15:26
kfox1111prebuild tool does: variables.yaml, chart.yaml (version) and drops in common_lib.15:26
sbezverkkfox1111's template is not a template which can be deploy by just runing helm install15:26
*** hvlad has quit IRC15:26
kfox1111sbezverk: yeah. you want to skip the helm pacakge step.15:27
sbezverkit always requires some manipulation to be done with CODE, not just varaibles15:27
kfox1111I get that.15:27
sdakeok i think there is another requirement that is hidden around in here15:27
sbezverkIf we could some to an option where we could have both, that would be fantastic using sdake parlor15:28
sdakebesides helm native + helm API15:28
sbezverksome/come15:28
kfox1111sbezverk: I think the prebuild tool covers the deploy from raw chart case.15:28
alanmeadowsTo be clear, that _hosts.tpl example is an example of how we're doing it now, I wanted to experiment with requiring operators to do helm install --values=required-big-cross-chart-values.yaml (effect of uber chart without the pain).  sbezverk mentions there may be namespace problems but its possible to work within that limitation15:28
sdakeand that is whaty ou just said kfox1111 :)15:28
*** hvlad has joined #openstack-kolla15:29
sdakeso helm native + helm API + deploy from raw chart15:29
sbezverkkfox1111: again pre-build for var/val works for me, pre-built for code does not..15:29
*** jtriley has quit IRC15:30
sdakesbezverk mind digging in to the rationale there of the prebuilt for code does not15:30
kfox1111sbezverk: arae you completely against a common lib then?15:30
portdirect_kfox1111: I think its important that what we have in git can be built into a chart using only helm from a checkout15:30
sdakeportdirect_ ++15:30
portdirect_at the start of this convo felt otherwise but this has convinced me that this is a criteria we should have15:30
kfox1111portdirect_: not sure that will work well with workflows, as you typicaly will want to bump versoins/revisions etc.15:31
kfox1111but sure. its fine to be able to.15:31
kfox1111so:15:31
kfox1111prebuild generates varaibles and charts, and drops in _common_lib.tpl.15:32
kfox1111thjen it gets git checked in.15:32
*** msimonin has joined #openstack-kolla15:32
sbezverksdake: when you develop a template, we need to test it so you change code more often than change data. Running a tool for every change you do on template to see looks very not optimal to me..15:32
sdakeis _common_lib.tpl manipulated in any way?15:32
kfox1111then on checkout, they should all be valid charts.15:32
kfox1111no manipulation. just copied.15:32
sdakesbezverk so the workflow would be as crazy ass this sounds15:33
sdake1. tool15:33
kfox1111sbezverk: don't you have to bump the version to redeploy your test code anyway?15:33
*** mdnadeem has joined #openstack-kolla15:33
sdake2. add stuff to global-values.yaml15:33
*** tonanhngo has joined #openstack-kolla15:33
sdake3. tool15:33
sdake4. deploy15:34
sbezverkkfox1111: if your template defained as macro, it has to be included soemwhere right? I guess you do it in common_main. Would it not this operation considered as on the fly code modification before the template gets deployed??15:34
sdakerather git checkout for 4 :)15:34
*** huzhengchuan_ has joined #openstack-kolla15:34
kfox1111sdake: no, I think we're past that. no common_main.15:34
sdakeself-modifying code is very very very very bad ;)15:34
kfox1111just _commmon_lib.tpl/_helpers.tpl for the shared code that15:35
kfox1111gets included15:35
*** jtriley has joined #openstack-kolla15:35
sdakeso lets look at the developer workflow for a  minute15:36
sdakekfox1111 mind defining that for us15:36
sbezverkkfox1111: could you answer my question?15:36
sdakekfox1111 on firing line :)15:36
kfox1111sbezverk: with the old poc it was staring with a raw included file and macro'ed in. not self modifying code.15:37
kfox1111but alanmeadows has a better workaround then that.15:37
kfox1111so not important anymore.15:37
kfox1111we just include the common lib like https://review.openstack.org/#/c/401394/8/helm/kolla-kubernetes/charts/openvswitch/charts/openvswitch-vswitchd/templates/openvswitch-vswitchd-daemonset.yaml15:38
* alanmeadows backs away slowly.15:38
kfox1111sbezverk: so, doing it your wya.15:38
kfox1111way15:38
sdakealanmeadows backing away from an audience isn't good alan :)15:38
alanmeadows;-)15:38
*** senk has quit IRC15:38
sdakekfox1111 then the workflow for developers looks like what?15:39
sdakehere is where i'm struggling and maybe you guys are thinking :)15:41
sdakei hear sbezverk question the concept of having a globals.tpl file, and i hear kevin say to have a globals.tpl file15:42
sdakeis that an accurate refelction?15:42
kfox1111sorry. internet crapped out.15:42
sdakeor is it more a matter of the tool should not copy it15:42
kfox1111dev checks out kolla-kubernetes,15:42
kfox1111goes to chart dir,15:42
kfox1111edits l3-agent template.15:43
kfox1111tweaks someting.15:43
kfox1111runs helm install on it.15:43
*** JoseMello has quit IRC15:43
kfox1111tests it.15:43
kfox1111git commits.15:43
portdirect_that misses a few steps?15:43
sdakeok that sounds good to me ifthose are the steps for an existing code base15:43
kfox1111if they need to edit common code,15:43
kfox1111the tweak that,15:43
kfox1111run prebuild. then helm install15:43
*** Jeffrey4l has joined #openstack-kolla15:44
kfox1111if tehy want to add a brand new microservice,15:44
kfox1111they add anything needed ito global-vars.yaml,15:44
*** jtriley has quit IRC15:44
kfox1111run prebuild,15:44
sbezverkkfox1111: what does prebuilt?15:44
kfox1111add their template yaml,15:44
kfox1111and run helm install15:44
kfox1111then when happy, git review.15:44
kfox1111prebuild does: creates variables.yaml from globals.yhaml, sets version in charts.yaml, and copies in common_lib.15:45
kfox1111I've gota to in 5 min.15:45
sdakekfox1111 me too15:45
sdakein about 1515:45
sbezverkkfox1111: cool it is something like helm create with extra15:45
sdakeso lets wrap this up15:45
kfox1111does that sound like it covers all the workflow?15:45
sdakei think that sounds good to me15:46
sdakesbezverk does that alleviate your concerns?15:46
portdirect_so only files edited are variables.yaml, version in carts.yaml and copying in common_lib to approprate place?15:46
sdakeportdirect_15:46
kfox1111portdirect_: yeah.15:46
sdakei want to be absolutely clear on one point15:46
sdakecommon_lib.yaml should not be modified by the prebuild step15:46
sbezverksdake: if what portdirect_ just mentioned holds true then yes15:46
portdirect_back to being a happy camper i think :)15:46
sdakeI think if we want to have that conversation we can later15:46
kfox1111sbezverk: right. common_lib is not modified. just copied in.15:46
sbezverkkfox1111: then 100% wfm15:47
kfox1111sdake I mean.15:47
kfox1111k. cool.15:47
portdirect_yeah - this sounds good15:47
sdakesweet15:47
sdakevictory declared :)15:47
*** fguillot has joined #openstack-kolla15:47
kfox111198% there. :)15:47
kfox1111there's one more thing to talk about, but minor, and can wait till later.15:47
kfox1111gota head out.15:48
sdakeok well lets not mix that up with this work ;)15:48
sdakekfox1111 quick q15:48
sdakewhen will bild tool be ready15:48
kfox1111sdake: it will come up in review. :)15:48
sdakesounds good15:48
kfox1111I should be able to get things rekergiggered around this monring I hope.15:48
kfox1111probably by noon.15:48
sdakethanks dude15:48
sdakeyou rock15:48
portdirect_sweet, cheers man15:48
*** sayantan_ has joined #openstack-kolla15:48
portdirect_sdake, when do you wanna get your vagrant stuff sorted?15:49
kfox1111thanks all for the discussion. it was great to work through all the issues, and get everyhone happy. :)15:49
kfox1111l8r15:49
sdakeportdirect_ hrm... let me check calednar15:49
*** jtriley has joined #openstack-kolla15:50
*** Jeffrey4l has quit IRC15:51
sdakeportdirect_ i am booked until about 3pm have a meeting in 15 mins but can cancel if you can get me sorted out in the next 1 hr15:51
*** Jeffrey4l has joined #openstack-kolla15:51
sdakethe other meetings i cant cancel15:52
portdirect_what time is where you are?15:52
sdake8:52 am15:52
portdirect_lets do after 3pm your time - I have a meeting in 30 that i cant cancel15:53
sdakecool15:53
sdakethanks :)15:53
sdakedid duounghq get his env rolling?15:53
portdirect_wont take an hour long - but I dont want to run out of time if anything weird crops up15:53
sdakeya i need to SSS anyway15:54
*** sayantani01_ has joined #openstack-kolla15:54
*** portdirect_ has quit IRC15:54
*** portdirect_ has joined #openstack-kolla15:54
*** adrian_otto has joined #openstack-kolla15:55
sdakekfox1111 thanks dude ;) ttyl15:55
*** TxGirlGeek has quit IRC15:56
*** TxGirlGeek has joined #openstack-kolla15:56
rhalliseysdake, yo15:58
*** jascott1 has joined #openstack-kolla15:59
duonghqsdake, my k8s cluster and helm is rolling15:59
*** goldyfruit has joined #openstack-kolla15:59
duonghqI'm diving in to kfox1111 and sbezverk PoC15:59
duonghqand your guys conversation15:59
*** tovin07 has joined #openstack-kolla15:59
*** portdirect_ has quit IRC16:02
YefimGGuys, I have installed kolla and kolla-ansible from master branch and it looks, like in both setup.cfg files package name is kolla, so they are uninstalling each other. Is it correct? I have changed kolla to kolla-ansible in it's setup.cfg and it went ok.16:02
*** strigazi_AFK is now known as strigazi16:02
*** jascott1 has quit IRC16:03
*** duonghq has quit IRC16:09
kristian__sdake portdirect_ great news about my gpu bug :D, guys in libvirt have helped me and told me to move the ethernet adapter because its causing chaos in the iommu groups16:09
sdakekristian__ sweet :)16:10
kristian__we will see16:10
inc0kristian__, so not a version issue at the end of the day?16:10
kristian__it looks like no16:10
kristian__at first they thought there isnt a feature in the cpu but after investigation on current normal build of libvirt it looks like chaos in iommu groups16:11
kristian__we will see16:11
egonzalez90sean-k-mooney: know if the guys working on opendaylight still doing it? https://blueprints.launchpad.net/kolla/+spec/opendaylight-support16:13
*** TxGirlGeek has quit IRC16:16
*** eaguilar has quit IRC16:17
mliima_need act here https://review.openstack.org/#/c/403689/ and https://review.openstack.org/#/c/401222/16:18
sean-k-mooneyegonzalez90: currently i dont think so. after i get the ovs-dpdk stuff done i might loop back to it but honestly i wont have time to look at it until pike16:19
*** mdnadeem has quit IRC16:21
*** YefimG has quit IRC16:21
sean-k-mooneyegonzalez90: if you want to take a crack at it or know someone else who does feel free16:22
openstackgerritMerged openstack/kolla-ansible: Move glance precheck into its own role  https://review.openstack.org/39935416:26
kfox1111back.16:26
*** huzhengchuan_ has quit IRC16:26
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: clean up kolla related files  https://review.openstack.org/40433016:29
*** jtriley has quit IRC16:30
sbezverkkfox1111: how do you want to deal with kind of PoC?16:30
sbezverkfor what we discussed this morning16:31
kfox1111sbezverk: I"m going to split up the https://review.openstack.org/#/c/396296/ into a few patches real quick,16:32
sbezverkkfox1111: for build/prebuild tool do you think you could put it together in one small PS without dependency on the gate etc? in this case we can start making templates and dealing with gates in parallel?16:32
openstackgerritMerged openstack/kolla-ansible: Add solum ansible role  https://review.openstack.org/40222516:32
kfox1111and tweak the build script into the prebuild script we talked about.16:33
sbezverkkfox1111: sounds good16:33
kfox1111was going to pull out the helm gate support to a trunk level patch.16:33
kfox1111so it can be reviewed independently.16:33
kfox1111then do the poc on top.16:33
kfox1111I also was thinking about it on the drive in,16:33
kfox1111I think we can actually do the common lib as a pure helm package,16:33
kfox1111rather then copy it in.16:34
kfox1111due to the macro/include trick.16:34
sbezverkkfox1111: I think it will be impotrant to be able to merge build script asap16:34
kfox1111sbezverk: yeah. I'm going to try and get something posted by noon. if not sooner.16:34
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: clean up kolla related files  https://review.openstack.org/40433016:34
sbezverkkfox1111: ok16:34
*** pcaruana has quit IRC16:36
*** sbezverk has quit IRC16:37
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Initial Helm support in the gate  https://review.openstack.org/40433216:37
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Initial Helm support in the gate  https://review.openstack.org/40433216:39
*** unicell1 has quit IRC16:40
*** tovin07 has quit IRC16:40
openstackgerritMauricio Lima proposed openstack/kolla-ansible: Move manila precheck into its own role  https://review.openstack.org/40433816:42
*** sbezverk has joined #openstack-kolla16:43
*** unicell has joined #openstack-kolla16:43
*** unicell has quit IRC16:43
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Initial Helm support  https://review.openstack.org/39629616:44
*** unicell has joined #openstack-kolla16:44
*** bmace has joined #openstack-kolla16:46
openstackgerritMerged openstack/kolla: Update Percona repo to current release  https://review.openstack.org/40088916:46
*** jtriley has joined #openstack-kolla16:47
*** jascott1 has joined #openstack-kolla16:47
openstackgerritMerged openstack/kolla: Add strongswan to neutron-vpn-agent source image  https://review.openstack.org/40406116:47
*** rmart04 has quit IRC16:47
*** vhosakot has joined #openstack-kolla16:49
kfox1111oh...16:50
kfox1111and doing a common lib package would let us break the lib up into multiple files.16:50
kfox1111that would be much cleaner looking.16:50
kfox1111hmm...16:51
openstackgerritMerged openstack/kolla: Use kolla-ansible deploy_aio in gate  https://review.openstack.org/40189116:51
kfox1111any helm experts awake?16:51
kfox1111oh.  I think it loads all files first, then processes macro's.16:52
kfox1111so Ithink we're good.16:52
v1k0d3nhey guys have a question ssl related again (sorry already).16:53
sbezverkkfox1111: would it be acceptable for you to use the same folder structure as in my PS? it looks like people liked it since it is very easy to view and follow16:53
v1k0d3ni've generated certs, run deploy, post-deploy, added cert path to /etc/kolla/admin-openrc.sh, but get an error 'X509' object has no attribute '_x509'. has anyone seen this?16:54
v1k0d3nany ideas?16:54
kfox1111sbezverk: thats the other thing I wanted to talk about.16:54
*** portdirect_away is now known as pd_away16:54
kfox1111it assumes we know the exact layout of a super package, and that there wont be other types.16:55
kfox1111I'm not sure we know either. :/16:55
*** sayantan_ has quit IRC16:55
kfox1111what about /helm/microservices/neutron-l3-agent, /helm/microservices/neutron-openvswitch-agent, etc? where each one is a chart?16:55
kfox1111then for super packages, we can do /helm/service/neutron or something like that?16:56
*** sayantan_ has joined #openstack-kolla16:56
kfox1111and use helm dependencies in the neutron package16:56
sbezverkkfox1111: what if by some reason we need a package per service as well?16:56
sbezverkexample neutron package including all neutron components16:56
kfox1111yeah. I think a helm dep will solve that?16:57
kfox1111oh.16:57
kfox1111I mean, requirements.yaml16:57
kfox1111https://github.com/kubernetes/helm/blob/master/docs/charts.md16:57
kfox1111"Managing Dependencies with requirements.yaml ?16:58
jascott1heh16:58
sbezverkkfox1111: I think if we go with 3 level it will give better flexibility in terms of future packaging16:58
jascott1good morning kolla peeps16:58
*** Pavo has quit IRC16:58
sbezverkbrb16:58
kfox1111sbezverk: I'm worried if we start nesting things then we will be rearanging it when we want to go to 3, or 4 levels.16:58
kfox1111if we keep the microservice packages at a place all on their own, we can include them with requirements in the places they need. potentially including the same subpackage in multiple service packages if need be.16:59
kfox1111rabbit for example.16:59
*** eaguilar has joined #openstack-kolla16:59
jascott1using requirements?16:59
kfox1111yeah.17:00
jascott1each service would have its own rabbit if you use requirements like that right?17:00
kfox1111yeah.17:00
kfox1111which is something I want on my cloud.17:00
kfox1111when a rabbit dies, less is affected that way.17:00
*** TxGirlGeek has joined #openstack-kolla17:01
kfox1111a herd of rabbits. :)17:01
kfox1111flock...17:01
kfox1111whats the right term.17:01
jascott1warren?17:01
kfox1111"A group of rabbits is called a "herd", just like a group of cattle. A herd of rabbits lives in a warren."17:01
*** adrian_otto has quit IRC17:01
kfox1111I guessed right the first time. :)17:01
*** jtriley has quit IRC17:01
kfox1111but, this brings up an interesting point.17:02
kfox1111where helm isn't very flexible.17:02
*** egonzalez90 has quit IRC17:02
kfox1111what if you wanted to have a nova service package with an optional embeded rabbit?17:02
kfox1111I don't think helm can handle that today.17:02
kfox1111so you'd have to build two different service packages. one with rabbit and one without. :/17:02
inc0herd of rabbits?17:03
inc0duh...17:03
jascott1thats what sbezverk's plugin idea would handle17:03
kfox1111yeah. that might work.17:03
*** Pavo has joined #openstack-kolla17:03
*** eaguilar has quit IRC17:03
*** sdake_ has joined #openstack-kolla17:03
rhalliseykfox1111, why have helm embed anything at all?17:04
kfox1111rhallisey: some folks want that. (non operator use case)17:04
sbezverkkfox1111: but what forces them to bundle these together and not install one and then another? it is kind of artifial requirements17:05
rhalliseykfox1111, how about micro service helm charts with no deps17:05
kfox1111sbezverk: I don't follow.17:05
rhalliseykfox1111, then charts that have the deps17:05
kfox1111rhallisey: I'm thinking microservices helm charts with just one dep. kolla-common, where we put all of our common code.17:06
sbezverkkfox1111: covering base and adding reasonable flexibility (that works for your case) should be ok for now imho17:06
*** sdake has quit IRC17:06
kfox1111sbezverk: yeah.17:06
kfox1111sbezverk: just sayin,g I couild see a case for sure where you might want to have more then one implementation of "nova" service package.17:06
*** eaguilar has joined #openstack-kolla17:06
kfox1111so putting the microservice inside the nova service package physically on the filesystem might not be a good fit.17:07
kfox1111so the requirements.yaml thing might be the way to go with /helm/microservices17:07
sbezverkkfox1111: ok but now this scenario is not even handled by openstack17:08
sbezverkso we do not do any less than already is17:08
kfox1111sbezverk: some operators deploy that way.17:08
rhalliseyhelm -> nova chart w/ deps -> nova micro service charts with no deps17:08
kfox1111with rabbit per service.17:08
*** jtriley has joined #openstack-kolla17:08
rhalliseystill complex tho17:08
kfox1111we also do a secondary rabbit for ceilometer.17:08
kfox1111rhallisey: in ha, everythings complex. :/17:08
rhalliseykfox1111, ya but were talking about packaging here17:08
jascott1dont we want HA rabbit clusters?17:09
rhalliseywere packaing 2 models17:09
kfox1111jascott1: for some things. for oslo notifications, I want ha.17:09
kfox1111jascott1: for rpc things, maybe not. k8s restarting a container might be good enough, and simpler.17:09
rhalliseykfox1111, so in your rabbit scenario how would you add a rabbit per service17:09
kfox1111helm install --name nova-rabbit kolla/rabbitmq17:10
kfox1111helm install --name neutron-rabbit kolla/rabbitmq17:10
kfox11112 rabbits. :)17:10
sbezverkkfox1111: for HA, it is not the only option to bundle right? you can still achieve HA with individual deployment no?17:10
rhalliseykfox1111, does nova-rabbit depend on nova?17:10
rhalliseyor nova-*17:10
kfox1111rhallisey: no.17:10
kfox1111sbezverk: right.17:11
jascott1kfox1111 but thats not using deps17:11
kfox1111jascott1: right17:11
jascott1ok17:11
rhalliseygiven that, I would define helm as a set of pods for a service to run17:11
sbezverkkfox1111: in near future, your build tool could evolve and package together components based on required components list17:11
rhalliseyi.e. rpm17:11
kfox1111sbezverk: I think helm can do that natively already.17:12
kfox1111haven't tried it yet though.17:12
kfox1111helm dependency update17:12
sbezverkkfox1111: me neither I want base working and start making temapltes for now ;-)17:12
kfox1111will pull the subcharts.17:13
kfox1111gona try poc'int that real quick.17:13
*** adrian_otto has joined #openstack-kolla17:13
kfox1111hmm...17:16
openstackgerritAlexis Rivera proposed openstack/kolla-ansible: renaming-kolla-build-command  https://review.openstack.org/40100517:16
openstackgerritAlexis Rivera proposed openstack/kolla-ansible: renaming-kolla-build-command  https://review.openstack.org/40100517:19
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible: Tacker NFV Ansible support  https://review.openstack.org/39917917:19
kfox1111arg.. helm definitely doesn't like symlinks. :/17:20
kfox1111a symlink would have worked beutifully here...17:20
openstackgerritAlexis Rivera proposed openstack/kolla-ansible: renaming-kolla-build-command  https://review.openstack.org/40100517:20
sbezverkkfox1111: yeah portdirect mentioned that idea but it looks like helm does agree with him ;-)17:21
inc0kfox1111, please...no symlinks17:21
inc0it worked really really bad in kolla back in a day17:21
kfox1111inc0: it just complicates things not using it in this case.17:22
*** jtriley has quit IRC17:22
inc0yeah, just supporting this in repo and stuff is really hard17:23
inc0also effectively closes lots of doors17:23
kfox1111helm was built for making it easy to build a single package, with prebuilt dependencies.17:23
kfox1111its not really tooled yet to easily build lots of packages.17:24
inc0same as docker build really17:24
inc0we had to write overarching tool (kolla_build) for it17:24
kfox1111yeah. and am getting pushback for trying to go down that route. :/17:25
inc0maybe we could reuse similar pattern?17:25
kfox1111I really want to use the same pattern.17:25
*** zhubingbing has quit IRC17:25
inc0I mean each chart will be self-contained right?17:25
inc0we will just do helm build in a loop17:25
inc0how wrong am I with this statement?17:26
kfox1111but deps have to be built before things that depend on them.17:26
kfox1111so tree. :/17:26
*** matrohon has quit IRC17:26
kfox1111so, kolla-common, thjen microservice packages, then service packages.17:26
*** vhosakot has quit IRC17:27
kfox1111the requirements stuff looks nice.17:27
kfox1111but it looks like you have to have a working mirror running.17:27
kfox1111so the build step would be:17:27
kfox1111build kolla-common, copy to local repo.17:27
kfox1111build microservices packages. copy to repo.17:27
jascott1if we dont use helm's deps we dont need a repo17:28
inc0thats how kolla-build works really17:28
kfox1111build service packages. copy to repos.17:28
inc0also true, what value do we get from helm native deps?17:28
kfox1111jascott1: then we gota manually copy the build packages into the other subdirs.17:28
pbourkeJeffrey4l: would you expect your dynamic dashboard changes to work with reconfigure?17:28
kfox11116 of one.17:29
kfox1111do we use helm to do the copying, or python?17:29
*** krtaylor has quit IRC17:29
kfox1111I thought we were "helm native" as much as possible.17:29
jascott1inc0 helm deps will download your sub charts and install them with the values you have for them. but thats it and really doesnt handle ordering of those deps iirc17:30
sbezverkkfox1111: copy is the part of your built script17:30
sbezverkso it is pre-helm step17:30
*** vhosakot has joined #openstack-kolla17:30
mliima_pbourke, https://review.openstack.org/#/c/401222/17:30
kfox1111sbezverk: so, I think we can do common lib as a kolla-common package,17:30
mliima_can you review?17:30
mliima_:)17:30
kfox1111and break up the lib into multiple files for easier maintenence/readability.17:30
mliima_https://review.openstack.org/#/c/403689/17:30
kfox1111but then we probably don't want to copy the whole kolla-common subpackage into each microservice on prebuild?17:31
kfox1111rather, go helm native and do a17:31
kfox1111helm dependency update; helm package . ?17:31
*** diogogmt has joined #openstack-kolla17:31
sbezverkkfox1111: just to be sure I follow you idea kolla-common is kind of global chart/template with bunch of smaller templates per macro?17:31
kfox1111sbezverk: exactly.17:32
mliima_thanks pbourke17:32
kfox1111then its pure helm.17:32
sbezverkkfox1111: I think that what we agreed, copy common into microservice17:32
kfox1111sbezverk: yeah. but as I was copying more and more stuff into common_lib just now, it was starting to get unwealdy. looking at alternative ideas.17:33
jascott1i dont see how deps will work until we get sbezverk's plugin to skip a dep. if you embed rabbit in a service then how do I use that service with my existing rabbit cluster for example?17:33
sbezverkso when microservice gets packaged/deployed common code will be used by helm rendering tool17:33
sbezverkjascott1: we kind of agree to go with microservice level17:34
kfox1111yeah. and I think a helm dep will do the same. but helm native.17:34
sbezverkand then prebuilt tool will add dependencies in terms of variable/values to the microservice chart17:34
kfox1111so no prebuild touching templates/* at all. just charts/values17:34
kfox1111so, even more helm native.17:35
sbezverkkfox1111: right17:35
sbezverkjascott1: it seems we can achive even without plugin17:35
jascott1so flat charts with external tooling, im down with that17:36
sbezverklater when plugon will become available, current templates still can be used for going funcy with this plugin as they are completely helm native17:36
*** eaguilar has quit IRC17:37
kfox1111heh. now there's a helm bug...17:38
sbezverkkfox1111: so back to file structure :-)17:38
kfox1111helm dep update17:38
kfox1111...Unable to get an update from the "local" chart repository (http://127.0.0.1:8879/charts):17:38
kfox1111echo $?17:38
kfox1111017:38
kfox1111:/17:38
kfox1111broken.17:38
jascott1ya the name has to match exactly17:38
jascott1127.0.0.1 != localhost17:38
*** unicell has quit IRC17:38
*** zhubingbing has joined #openstack-kolla17:38
kfox1111no, the brokenness is if it cant download something important, it still returns success. :/17:38
jascott1oh ha17:39
kfox1111meeting. bbiab17:40
openstackgerritMerged openstack/kolla-ansible: Remove fragments of docker files  https://review.openstack.org/40122217:43
*** matrohon has joined #openstack-kolla17:43
*** TxGirlGeek has quit IRC17:48
sbezverkkfox1111: I read through requirements.yaml doc and it seems it can be used for the use case you mentioned like nova+rabbit, by specifying rabbit in this file helm is supposed to add it at the rendering time..17:50
*** msimonin has quit IRC17:51
*** TxGirlGeek has joined #openstack-kolla17:52
kfox1111sbezverk: yeah, it can be done by changing the charts, but not by using a prebuilt package. :/17:52
kfox1111one of my goals is to make it so that users don't normally have to build charts. just use prebuilt packages.17:52
kfox1111I hardly ever build an rpm from source.17:52
*** adrian_otto has quit IRC17:53
jascott1"but when I do, I do it in PRD"17:53
jascott1kfox1111 are you saying you cannot install a dep without a package?17:53
*** strigazi is now known as strigazi_AFK17:54
kfox1111jascott1: no, I'm saying if you want to make add/remove rabbit from nova service package, you gota edit a file and rebuild the package from source.17:54
kfox1111rather then be able to do helm install nova --set no_rabbit=true17:54
jascott1gotcha. cause reqs wants to pull the package17:55
sbezverkkfox1111: well this limitation is not clear from reading the doc, but I guess you tried and it did not work17:55
kfox1111it would be nice if there were optional deps. :/17:55
kfox1111or optional instantiation really...17:56
kfox1111maybe we can do somethign with a macro though, in the rabbit package.17:56
kfox1111make an override that skips launching the template if a var is set.17:56
jascott1but if you have that chart in subfolder it still pulls?17:56
kfox1111yeah. all subcharts always get instantiated.17:56
*** zhubingbing has quit IRC17:56
jascott1i thought it was using my local subchart17:57
jascott1hmm17:57
kfox1111oh. I didn't understand the question.17:57
kfox1111if you have a subchart already in there, I think it uses that.17:57
kfox1111meting next. bbiab.17:58
*** harbor has joined #openstack-kolla17:59
*** unicell has joined #openstack-kolla18:00
*** pd_away has quit IRC18:01
*** TxGirlGeek has quit IRC18:02
*** unicell has quit IRC18:05
*** jgriffith_away is now known as jgriffith18:05
pbourkeJeffrey4l: any chance you can double check the lbaas dashboard is working for you?18:05
pbourkeJeffrey4l: have it enabled and can see the enabled files but its not showing up18:06
pbourke(in horizon)18:06
*** kristian__ has quit IRC18:06
*** JoseMello has joined #openstack-kolla18:07
*** TxGirlGeek has joined #openstack-kolla18:08
*** gfidente is now known as gfidente|afk18:08
sdake_jascott1 is intel stlil running management by objectives? (MBO?)18:09
sdake_jascott1 surprised intel still running product requirements documents (PRD)18:10
*** mkoderer has quit IRC18:13
*** tonanhngo has quit IRC18:14
inc0sdake_, I'm from intel and I have no idea what are you talknig about18:15
sdake_[10:53:21]  <jascott1>"but when I do, I do it in PRD"18:16
sdake_maybe PRD has some other magic tla inside intc now :)18:17
*** papacz has quit IRC18:23
*** TxGirlGeek has quit IRC18:24
*** athomas has quit IRC18:25
*** inc0 has quit IRC18:26
*** sayantan_ has quit IRC18:30
jascott1sorry I meant PROD18:31
jascott1but yes MBOs are still a thing at Intel18:31
jascott1but not so much in our org afaik.. idk new to the org18:31
sdake_jascott1 oh got it :)18:32
jascott1http://imgur.com/gallery/y7Hm918:32
sdake_lol18:33
*** shardy has quit IRC18:34
jascott1we have a lot of agile in the software group18:34
jascott1no idea what the chip makers use18:35
sdake_copy exactly18:35
sdake_Wendy Vittori led a session on "Whats wrong with strategy" when i was a young tike out of school18:36
sdake_it fundamentally changed how i viewed the world18:36
sdake_too bad it wasn't recorded :(18:36
sdake_it took a few years to sink in18:37
sdake_maybe 5 ;)18:37
sdake_i think it was geared at the old dogs like you and me jascott1 :)18:37
*** eaguilar has joined #openstack-kolla18:38
jascott1woof18:38
sdake_that old idiom old dogs can't be taught new tricks doesn't apply to humans :)18:39
*** hvlad has quit IRC18:39
*** jgriffith is now known as jgriffith_away18:40
jrich523lol, i kinda feel like it applies more to human than any other creature18:40
jascott1no doubt18:40
*** inc0 has joined #openstack-kolla18:41
*** kristian__ has joined #openstack-kolla18:42
jascott1mammals rule!18:44
*** unicell1 has joined #openstack-kolla18:44
inc0reptilians rule, you just don't know it18:46
*** krtaylor has joined #openstack-kolla18:46
jascott1lol... would agree reptilian part of our brains seems to call the shots too often18:49
*** lrensing has quit IRC18:52
*** lrensing has joined #openstack-kolla18:53
*** athomas has joined #openstack-kolla18:55
*** Pavo has quit IRC18:58
openstackgerritcaoyuan proposed openstack/kolla-ansible: Move aodh precheck into its own role  https://review.openstack.org/40438919:02
*** Pavo has joined #openstack-kolla19:03
sean-k-mooneyhi. has anyone used manila?19:03
*** athomas has quit IRC19:03
*** kristian__ has quit IRC19:04
*** eaguilar has quit IRC19:05
mliima_\o19:09
mliima_sean-k-mooney,19:09
sean-k-mooneyhi19:10
mliima_hi19:10
mliima_any problem with manila?19:10
mliima_I used and i can try to help you19:11
sean-k-mooneymliima_: am yes basically i was trying to create a share on stable/newton but it fails.19:12
mliima_hmm19:12
sean-k-mooneyon the manila-share container i am seeing the follwoing message  ServiceInstanceException: SSH connection has not been established to 10.254.0.7 in 300s. Giving up.19:12
mliima_nova list --all-tenants19:13
mliima_please19:13
mliima_are you using generic driver?19:13
*** matrohon has quit IRC19:14
sean-k-mooneyyep i am. one sec i deleted the vms because i also could not delete the shares from error state19:14
*** tonanhngo has joined #openstack-kolla19:14
*** inc0 has quit IRC19:15
mliima_sean-k-mooney, which image are you using to build an instance?19:15
sean-k-mooneyi was using the one in the docs following https://github.com/openstack/kolla/blob/master/doc/manila-guide.rst19:16
mliima_ok19:16
*** athomas has joined #openstack-kolla19:17
*** inc0 has joined #openstack-kolla19:18
mliima_try to create a share again19:18
mliima_and run nova list --all-tenants19:19
mliima_:)19:19
sean-k-mooneyhttp://paste.openstack.org/show/590871/19:20
mliima_sean-k-mooney,19:21
mliima_run cat /etc/kolla/config/manila-share.conf19:21
mliima_"BadRequest: Flavor 100 could not be found."19:21
sean-k-mooneyya i have fixed that19:22
*** jtriley has joined #openstack-kolla19:22
kfox1111back.19:22
sean-k-mooneyi updated the flavoer which cased the id to chagne but i deleted and recreated it19:22
sean-k-mooneymliima_: do i have to create a /etc/kolla/config/manila-share.conf is if i create the flavor with id 10019:23
mliima_no19:23
sean-k-mooneyhttp://paste.openstack.org/show/590872/19:24
sean-k-mooneythat is my manila conf19:24
sean-k-mooneykolla@silpixa00385225:~$ openstack flavor list19:24
sean-k-mooney+--------------------------------------+-----------------------+-------+------+-----------+-------+-----------+19:24
sean-k-mooney| ID                                   | Name                  |   RAM | Disk | Ephemeral | VCPUs | Is Public |19:24
sean-k-mooney+--------------------------------------+-----------------------+-------+------+-----------+-------+-----------+19:24
sean-k-mooney| 100                                  | manila-service-flavor |   128 |    0 |         0 |     1 | True      |19:24
sean-k-mooney| 1132d6d1-0a12-4f62-9ad4-7aae93d21109 | all-in-one            | 14336 |   50 |         0 |    10 | True      |19:24
sean-k-mooney| 616b1e9a-4419-414a-8c46-8e737a4bcc39 | medium                |  4096 |   20 |         0 |     4 | True      |19:24
sean-k-mooney| 62d0625d-ba94-4679-8619-42735db9d8fb | large                 |  8192 |   40 |         0 |     8 | True      |19:24
sean-k-mooney| 795a70b9-cd96-40a3-90c5-c3b114bb8d4c | cirros                |    64 |    1 |         0 |     1 | True      |19:24
sean-k-mooney| 9403c6a1-ff39-406c-9915-d3fa19896742 | smoke-test            |  4096 |   10 |         0 |     2 | True      |19:24
sean-k-mooney| f25d0593-037e-4a47-8b69-dc5154110bee | small                 |  1024 |   10 |         0 |     1 | True      |19:24
sean-k-mooney+--------------------------------------+-----------------------+-------+------+-----------+-------+-----------+19:24
mliima_ok, its right sean-k-mooney19:24
mliima_docker restart manila_share19:25
mliima_and try to create another share again19:25
sean-k-mooneyam sure i can do that one sec19:25
*** jtriley has quit IRC19:26
*** eaguilar has joined #openstack-kolla19:27
*** sayantan_ has joined #openstack-kolla19:28
sdake_sup kfox111119:28
kfox1111sdake_: hi19:29
sean-k-mooneymliima_: it has a different error "ServiceInstanceUnavailable: Service instance is not available."19:29
kfox1111sdake_: so, had an idea for an even more helm native thing,19:29
kfox1111it needs more of a build step.19:29
kfox1111kind of a hard call.19:29
sean-k-mooneymliima_: the nova instance is there though19:29
kfox1111but the more I pla ywith it, the more I think we will want a build step anyway. as helm doesn't have a good way to build multiple packages anyway.19:29
kfox1111need a command to build all microservices for example.19:30
sdake_ok - so i think my default respones here would be lets tackle what we agreed to - and sort it out in the gerrit reiew :)19:30
mliima_manila list sean-k-mooney19:30
sdake_and then sort out that idea next19:30
kfox1111hmm...19:30
kfox1111k.19:30
mliima_manila try to build an instance at the same time try to connect using ssh19:30
sean-k-mooneykolla@silpixa00385225:~$ manila list19:30
sean-k-mooney+--------------------------------------+-------------+------+-------------+----------+-----------+--------------------+---------------------------------+-------------------+19:30
sean-k-mooney| ID                                   | Name        | Size | Share Proto | Status   | Is Public | Share Type Name    | Host                            | Availability Zone |19:31
sean-k-mooney+--------------------------------------+-------------+------+-------------+----------+-----------+--------------------+---------------------------------+-------------------+19:31
sean-k-mooney| 0ed0aa91-4f97-4bc6-8081-cd5744c2a00a | demo-share1 | 200  | NFS         | deleting | True      | default_share_type | silpixa00385226@generic#GENERIC | nova              |19:31
sean-k-mooney| 84730297-a9dc-4247-a61d-d22270b355e6 | demo-share1 | 200  | NFS         | creating | True      | default_share_type | silpixa00385226@generic#GENERIC | nova              |19:31
*** TxGirlGeek has joined #openstack-kolla19:31
sean-k-mooney+--------------------------------------+-------------+------+-------------+----------+-----------+--------------------+---------------------------------+-------------------+19:31
sdake_sean-k-mooney any chance you can use a paste service ;)19:31
mliima_manila try to build an instance at the same time try to connect using ssh until timeout19:31
sean-k-mooneysdake_: ya sorry19:31
sdake_sean-k-mooney itso k i do it too19:31
sdake_although usually 1-3 short lines19:31
mliima_so,this is normal19:31
sdake_thats really hard to read in irc anyway :)19:31
mliima_just wait19:31
mliima_:)19:31
sean-k-mooneymliima_: roughly how long should it take?19:32
*** fguillot has quit IRC19:33
mliima_It depends19:33
mliima_2 minutes19:34
*** fguillot has joined #openstack-kolla19:34
mliima_but this depends on your resources sean-k-mooney19:34
mliima_run manila list19:34
sean-k-mooneyit just went into error state.19:34
mliima_oh god19:34
mliima_let me see manila_share logs19:35
sean-k-mooneymliima_: so far all shares i have create end in error state19:35
mliima_let me see manila_share logs sean-k-mooney19:36
sean-k-mooneyhttp://paste.openstack.org/show/590877/19:36
sean-k-mooneysame issue ServiceInstanceException: SSH connection has not been established to 10.254.0.8 in 300s. Giving up.19:36
*** harbor_ has joined #openstack-kolla19:37
*** kristian__ has joined #openstack-kolla19:37
sdake_sup harbie19:37
sdake_harbor19:37
sdake_harbor_ :)19:37
mliima_sean-k-mooney, neutron net-list19:37
harbor_wait for the transformation - just shedding my lizard skin19:37
*** harbor_ is now known as portdirect19:38
mliima_manila share-network-list19:38
portdirecthey sdake_ :)19:38
mliima_and which command are you using to create a share?19:38
sdake_portdirect have meetings for next couple hours then should be good to go19:39
sdake_on env setup19:39
sdake_need to get rolling :)19:39
sean-k-mooneymliima_: ill put it in the paste19:39
mliima_ok19:40
sdake_portdirect i'm on your schedule after that :)19:40
sean-k-mooneymliima_: http://paste.openstack.org/show/590880/19:40
portdirectsdake_: I'm reverting to full mad scientist :/ getting a centos and ubuntu box set up right now so will be able to play in all the sandpits :)19:40
sdake_tarpits ? :)19:40
*** kristian__ has quit IRC19:41
mliima_sean-k-mooney, can you ping  10.254.0.8 ?19:41
*** kristian__ has joined #openstack-kolla19:42
mliima_from your host?19:42
sean-k-mooneyno that network would conflict with my lab network19:42
sean-k-mooney10.254.0.8 is on the private tenant network created by manila19:42
sean-k-mooneymliima_: i could try from the network namespace of the dhcp server19:43
alanmeadowskfox1111: interesting, I can't reproduce the "inconsistency" with a sub chart define in v2.0.019:43
alanmeadowsI wonder if this was an rc2 thing19:43
mliima_you need to run this command from a vm that can ping manila-instance19:45
mliima_sean-k-mooney,19:45
kfox1111alanmeadows: which do you mean. defining in a subchart, then using in a main template?19:45
kfox1111defining a var I mean.19:45
alanmeadowsright19:45
kfox1111maybe their hashing has just gotten a bit more consistant, but will still have issues.19:45
kfox1111we should see if we can find a bug for it.19:45
kfox1111if its fixed, thats great.19:46
kfox1111if its just more consistatnly randomly working, thats bad. :/19:46
alanmeadowsmaybe the stars are aligning for this particular inclusion ordering19:46
sdake_kfox1111 :)19:46
alanmeadowsnot sure if its because im in a different template combo19:46
kfox1111I had one that worked 10 tims in a row, then broke on the 11th. :/19:46
alanmeadowsor if it was rc2 only19:46
sdake_kfox1111 welcome to my world ;)19:46
mliima_it is clear that this is a problem in the network configuration, "SSH connection has not been established to 10.254.0.8 in 300s"19:47
alanmeadowssame... but now consistent I don't know what to believe anymore ;-)19:47
mliima_I have to go now, but tomorrow I can keep trying to help you sean-k-mooney19:48
kfox1111sdake_: yeah. got bit by that so often, I'm really leary of it. if I ever see it, then I don't trust it to workf or a long time, or someone showing me the bug fix notes. :)19:48
*** portdirect has quit IRC19:48
*** portdirect has joined #openstack-kolla19:48
sean-k-mooneymliima_: i guess i will have to read up on manila then as i dont understand how manila instance withc is connected to a different neutron network is ment to be pinable form the private network in the kolla docs example19:48
sean-k-mooneymliima_: thanks for your help19:49
*** portdirect has quit IRC19:49
mliima_perhaps this may be a bug sean-k-mooney19:49
sean-k-mooneyperhaps ill try to do a littl more diging thanks19:50
mliima_or I may have done some step that is not in guide19:50
mliima_bye19:51
*** mliima_ has quit IRC19:51
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Run docker registry in gate  https://review.openstack.org/40440519:55
openstackgerritcaoyuan proposed openstack/kolla: Replaces uuid.uuid4 with uuidutils.generate_uuid()  https://review.openstack.org/40440619:56
*** jgriffith_away is now known as jgriffith19:56
*** portdirect has joined #openstack-kolla19:56
*** msimonin has joined #openstack-kolla19:59
*** senk has joined #openstack-kolla20:00
*** unicell1 has quit IRC20:01
*** jascott1 has quit IRC20:01
*** sayanta__ has joined #openstack-kolla20:03
*** sayantan_ has quit IRC20:05
*** jascott1 has joined #openstack-kolla20:05
*** senk has quit IRC20:06
*** msimonin has quit IRC20:06
*** unicell1 has joined #openstack-kolla20:09
*** msimonin has joined #openstack-kolla20:09
kfox1111Error: YAML parse error on neutron-openvswitch-agent/templates/l3_agent_daemonset.yaml: error converting YAML to JSON: yaml: line 77: mapping values are not allowed in this context20:11
kfox1111arg... really not helpful helm...20:12
kristian__sdake_ what do you think this means and a possible fix20:12
kristian__vfio: error, group 1 is not viable20:12
kfox1111helm needsa good way to dump out a macro expanded template, before processing. :/20:17
alanmeadowskfox1111: apparently a newer version of Go in 2.0.0 build (vs rc2)20:19
alanmeadowsand (I quote) "that could have had an impact... but my money's on luck."20:19
alanmeadowsnot sure if like me you were using 2.0.0rc220:19
alanmeadowsas we are in production20:19
kfox1111i may still be using 2.0.0rc2 on this box.20:20
kfox1111I think we should assume luck then and just ckeep using the include trick.20:20
kfox1111I saw some place in the documentation that said it shouldn't work either.20:20
kfox1111cant remember exactly where though.20:20
inc0"assume luck" makes me worried...should I be worried?20:21
alanmeadowshaha thats what I said ;-)20:21
alanmeadowsThe expert helm developer response20:21
alanmeadowsleaves me no more confident then before I arrived20:21
sbezverkkfox1111: can you push what you have so far, so we could give it a spin in different environment to see if this issue is a test bed specific?20:22
inc0how fun based our very architecture on not-released stuff20:22
kfox1111sbezverk: I don't have a reporducer for that behavior. just something I tried a couple weeks ago to see what would work and what not.20:22
kristian__inc0 sdake_ portdirect: it booted with GPU :D :D :D gonna check from the host if there is gpu attached in the vm20:23
inc0good news20:23
inc0:)20:23
kristian__yeaaah20:24
kristian__its in the host20:24
kristian__finallllyyyyy20:24
kristian__00:05.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)20:24
kristian__right from the output20:24
sbezverkkfox1111: just one more thing, would it not be a bit more managable still to have all microservice under the same service folder. Example rabbit: I have 5 separate charts, if these all are under microservices folder then missing one would be very easy, but if the are under rabbit/ then it becomes more visible, what do you think?20:24
kristian__going to fix cinder and I can go and make the gaming server :D20:25
inc0kristian__, which game?20:26
kristian__watch dogs 220:26
portdirectkristian__: fingers crossed dude :D20:26
kfox1111sbezverk: I think it will be highly unlikely someone would be building every one manually, risking missing one.20:26
inc0I couldnt handle watch dogs 120:26
kfox1111there will just be too many to build that way.20:26
kristian__and others I think20:26
kristian__thanks20:26
kristian__thank you for all of your help20:26
inc0not very captivating20:26
kfox1111helm bilding takes like under a second.20:26
inc0but good luck:)20:27
kfox1111so a build_microservices.py should be real quick.20:27
kristian__Im so hyped about that game20:27
kfox1111we could do microservices/neutron/neutron-openvswitch-agent I guess, but more typing.20:27
kfox1111I guess I don't have muhc of a preference there.20:27
*** jtriley has joined #openstack-kolla20:28
kristian__also I want it to be on openstack because first I want to learn it and second I want to use it as a gaming server for new games20:28
portdirectkristian__: could you close that bug you opened? It's really usefull to get the info of how you managed to fix the issue incase someone else hits the same thing :)20:28
kristian__yes I will20:28
portdirectnice one20:29
kristian__give me some time so I can quickly fix my cinder problem20:29
sdake_meh who cares on the directory layout20:31
kfox1111ok. this seems to work about right...20:32
kfox1111a few more min and should be able to post something.20:32
alanmeadowsjust fyi, according to helm devs, defines in subchart, accessed in parents is a use case that is supposed to work, so if it does not, its a bug20:32
alanmeadowsI like confirmation I'm not using unintended magic ;-)20:33
kfox1111really?20:33
kfox1111very cool.20:33
kristian__portdirect: where can I close the bug?20:33
kfox1111alanmeadows: and thats with $foo style vars?20:34
kfox1111fyi, I am using beta2 on my test box.20:34
alanmeadowsthats with {{ define }}20:34
alanmeadowsand if you use a --values=foo.yaml during install, its suppose to merge with the charts defaults20:35
kfox1111define is for macro's touhg.20:35
kfox1111not variables?20:35
alanmeadowsit is, one mans macro could be another man's variable ;-)20:35
kfox1111alanmeadows: well, yeah. we're using them to tranfer vars.20:35
alanmeadowsbut just thinking out loud20:35
kfox1111but not explicitly {{ $foo = "some value in child template }}20:35
kfox1111{{ $foo }} in parent20:36
alanmeadowsI actually haven't tried that, given there is some pre "global evaluation" in order to accomplish the defines20:36
alanmeadowsI wonder.20:36
alanmeadowsthe context would be messed up20:36
alanmeadowsyou'd have to Child.$foo20:36
alanmeadowsbut anyways20:37
alanmeadowsgiven two things20:37
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Run docker registry in gate  https://review.openstack.org/40440520:37
alanmeadows1) you can depend on child defines bubbling up for macros, and 2) you can merge in a top level set of common values with --values=cross-chart-values.yaml.20:37
alanmeadowsif those were to reliably hold true20:37
alanmeadowsno precopy step20:37
sdake_portdirect i've got a direct dependency on your work and kevins work - so as soon as your ready to go, can you help me get my dev env setup :)20:38
alanmeadowsand you can refer to common values without redefining them everywhere or relying on globals20:38
alanmeadowsit just requires the operator to always install charts with --values=...20:39
sdake_without those two things, i can't do mariadb which is critical path20:39
*** diogogmt has quit IRC20:40
kristian__sdake_ can you help me close the bug?20:40
sdake_kristian__ link?20:40
sdake_was the bug user error?20:40
kristian__https://bugs.launchpad.net/nova/+bug/164241920:40
openstackLaunchpad bug 1642419 in kolla-ansible "GPU Passthrough isn't working" [Low,Confirmed]20:40
kristian__kinda yes20:40
kristian__its written there at the end20:41
*** msimonin has quit IRC20:41
sdake_kristian__ cool - i dont have access to close nova bugs20:41
sdake_so the nova bug triage team will have to handle that20:41
kristian__ok going there now20:41
*** diogogmt has joined #openstack-kolla20:42
sdake_portdirect ? :)20:42
sdake_paying 1 AUD for documentation on a development environment20:42
portdirectportdirect, studiously ignores sdake_ for 10 mins :/20:43
portdirecthopfully 520:43
sdake_portdirect roger20:43
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: Run docker registry in gate  https://review.openstack.org/40440520:45
kfox1111alanmeadows: I prototyped making the whole thing just a kolla-common subpackage to the mircroservices. it works.20:47
kfox1111but I we agreed apon something else, so I'll suggest that as a followon patch.20:48
kfox1111Its much more clean I think, but has more steps/requirements of the build system.20:48
kfox1111as helm is't very good at building multilple packages.20:48
alanmeadowsmakes sense to me20:50
kfox1111really close now. :/20:51
kfox1111./helm_build_microservices.py ~/.helm/repository/local/20:51
kfox1111Error: open /home/kfox2/.helm/repository/local/index.yaml: no such file or directory20:51
kfox1111not sure why it should care.. hmm....20:51
*** msimonin has joined #openstack-kolla20:54
kfox1111ok. got it to work...20:54
portdirectsdake ping20:54
sdake_wound me portdirect20:54
portdirectI taught i saw a wappit20:55
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Initial Helm support  https://review.openstack.org/39629620:56
kfox1111ok.20:56
sdake_cool lets get to it20:56
kfox1111first pass at a poc with the discussed layout.20:56
sdake_cool lets get to it was at portdirect  :)20:56
kfox1111got a meeting to go to now though.20:56
portdirectI've thrown up an updated gist of the setup I'm using: https://gist.github.com/intlabs/9ce71a4a6b93b4e2e90faec500ef70d020:56
kfox1111sdake_: alanmeadows sbezverk please have a look at that review.20:56
kfox1111bbl.20:57
*** YefimG has joined #openstack-kolla20:57
*** eaguilar has quit IRC20:57
*** matrohon has joined #openstack-kolla20:57
sdake_kfox1111 will do20:57
portdirectwhere were we with your setup before? - we had go you up with vagrant but is was not happy?20:57
sdake_right ipv620:57
sdake_was imploding20:57
sdake_portdirect is that README.md your original work?20:58
portdirectok - that was prob my bad and docker weirdness20:58
portdirectyes20:58
sdake_cool looks like i owe you one AUD20:58
sdake_can you get those docs in a review20:58
portdirectnp20:58
*** Pavo has quit IRC20:58
portdirectbefore I do that lets get you running then I'll fire them straigt in20:59
sdake_sounds good21:00
sdake_let me run through them21:00
sdake_need to switch networks to make that happen21:00
*** adrian_otto has joined #openstack-kolla21:00
*** kristian__ has quit IRC21:00
*** kristian__ has joined #openstack-kolla21:01
*** JoseMello has quit IRC21:03
sdake_portdirect let me have a quick look at kevin's review - its failing the gate, to unblock me i need to unblock him :)21:03
*** Pavo has joined #openstack-kolla21:03
*** TxGirlGeek has quit IRC21:05
srwilkers_sdake_, looks like pep8 errors21:05
srwilkers_some unused imports and lines too long21:06
*** adrian_otto1 has joined #openstack-kolla21:06
*** TxGirlGeek has joined #openstack-kolla21:06
*** dave-mccowan has quit IRC21:06
*** adrian_otto has quit IRC21:07
*** fguillot has quit IRC21:07
*** gfidente|afk has quit IRC21:07
portdirectnp - kubeadm throwing a hissyfit too :/21:08
*** inc0 has quit IRC21:09
*** jtriley has quit IRC21:09
mgilesWhew - Finally got my kubernetes dev setup working (after many failed attempts - been working on it all day)21:12
sdake_mgiles ya its rough :)21:12
sdake_mgiles still working on it :)21:13
mgilesportdirect Those instructions look like a good start but  probably won't work behind a proxy/firewall.  There were a bunch of extra steps for me to work around that.21:13
sdake_srwilkers_ what helps when you find the gate error is to add a comment to the review with a link to the gate failure location21:13
portdirectmgiles: yeah - I'm not needing a proxy - but had to openup quite a bit on firewalld for my fedora boxen21:14
sdake_that helps the author understand what needs fixing in the python code exposed by the linter21:14
srwilkers_still doing my review sdake_, got a snippet pasted inline already21:14
sdake_srwilkers_ sweet21:14
srwilkers_been making it a point to get more familiar with the gates and whats inside -- havent done that much in the past21:14
*** jtriley has joined #openstack-kolla21:16
mgilesportdirect Are you going to add this to the docs?  Would be useful for others starting out.  If you do, we can then edit with instructions to accommodate a proxy21:17
sdake_bb-10 need to collect child21:17
*** sdake_ has quit IRC21:17
portdirectmgiles: I'll get a pr in soon - if you could add any addtional steps you needed then I'll happly put them in21:17
*** msimonin has quit IRC21:18
portdirectmgiles: Would also be great to cover mac/ubuntu vagrant setups as well21:18
mgilesI did this on ubuntu.  my steps were slightly different, but substantially similar.  Haven't tried it on my Mac yet, but can try that sometime if it would help.21:19
*** TxGirlGeek has quit IRC21:19
jascott1I did on mac yesterday without problems21:20
*** TxGirlGeek has joined #openstack-kolla21:20
srwilkers_yeah, halcyon should work mostly out of the box with the vagrant set up, as long as youve got everything listed in config.rb21:21
srwilkers_this worked fine for me portdirect21:21
*** TxGirlGeek has quit IRC21:22
portdirectsrwilkers_/jascott1: great :)21:22
portdirectI'll aslo tidy up the ansible mod's I've made and get them over into your repo is poss - seems messy/confusing to work from a fork?21:23
srwilkers_helm repo update21:24
srwilkers_oops21:24
portdirectlol21:24
*** krtaylor has quit IRC21:26
srwilkers_gotta head home -- be back in an hour or so21:28
*** inc0 has joined #openstack-kolla21:29
*** sdake has joined #openstack-kolla21:31
sdakesrwilkers i can show you if you like21:32
*** adrian_otto1 has quit IRC21:32
srwilkers_yeah sdake, thatd be awesome21:32
*** msimonin has joined #openstack-kolla21:32
sdakesrwilkers htis is the top level file: http://logs.openstack.org/96/396296/29/check/gate-kolla-kubernetes-pep8-ubuntu-xenial/8ab0b44/console.html21:32
sdakesrwilkers to figure out where it went wrong, hunt to the correct location and click21:33
sbezverksrwilkers_: you made the same mistake :-) as I did, we need to use helm_prebuilt.py21:33
srwilkers_sbezverk, whoops21:33
*** adrian_otto has joined #openstack-kolla21:33
sdakesrwilkers http://logs.openstack.org/96/396296/29/check/gate-kolla-kubernetes-pep8-ubuntu-xenial/8ab0b44/console.html#_2016-11-29_20_57_27_32328421:33
*** goldyfruit has quit IRC21:34
sdakesrwilkers to get the corerct time stamp in there just click on the timestamp21:34
sdakesrwilkers then paste that into the log21:34
sdakesrwilkers its fantastic when people analyze gate failures for others21:34
sdakeit makes the commit process go much faster21:34
sdakeyou paste the url into the log that is :)21:34
*** Jeffrey4l has quit IRC21:35
sdaketo get to that top level page, click the gate job that failed21:35
sdakepep8 = linters21:35
sdakethere was an effort to rename pep8 to linters but it was overwhelming for the infra team to tackle so they left it as pep821:35
sdakeok portdirect lemme read ure docs and try to reproduce :)21:36
*** rhallisey has quit IRC21:37
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP adding openvswitch-ovsdb microservice  https://review.openstack.org/40395921:37
sbezverksdake: just pushed ps based on new agreement21:38
*** sdake_ has joined #openstack-kolla21:38
sbezverkit is missing values.yaml as I could not generate one using kfox1111 prebuilt script21:39
*** sdake has quit IRC21:41
*** YefimG has quit IRC21:42
*** jtriley has quit IRC21:42
*** diogogmt has quit IRC21:46
*** srwilkers_ has quit IRC21:46
*** lrensing has quit IRC21:47
*** Jeffrey4l has joined #openstack-kolla21:47
*** sdake has joined #openstack-kolla21:47
sdakeok portdirect - now kubernetes ;)21:47
sdakeportdirect i'll report back my findings - should take about 10 mins21:47
sdakeportdirect good to have people test out the docs :)21:48
portdirectnice - my vagrant is busted :/21:48
sdakedoesn't sound inspiring :)21:48
portdirectall the tests in that readme passed?21:48
sdakei haven' tstarted yet21:48
sdakegetting there21:48
sdake- starting now21:48
*** sdake_ has quit IRC21:51
*** matrohon has quit IRC21:54
*** matrohon has joined #openstack-kolla21:54
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: WIP: packing and uploading registry  https://review.openstack.org/40443521:57
*** TxGirlGeek has joined #openstack-kolla21:57
*** JRobinson__ has joined #openstack-kolla22:03
*** jrist has quit IRC22:08
*** TxGirlGeek has quit IRC22:09
*** diogogmt has joined #openstack-kolla22:12
*** Serlex has left #openstack-kolla22:13
*** athomas has quit IRC22:17
*** inc0 has quit IRC22:20
mgilesportdirect regarding the instructions: I had problems with the vagrant plugin install within the Vagrantfile.22:21
mgilesI had to manually install the plugins and then comment these lines out of the Vagrantfile.22:21
mgilesHad the problem on a couple of different systems so not sure why others aren't hitting it.  Maybe a different version of vagrant?22:21
portdirectthink thats an issue - I'm not that familiar with vagrant :( what version are you using?22:22
*** matrohon has quit IRC22:22
mgiles1.9.022:22
portdirectmy f24 comp has 1.8.1 whihc seems to work fine - but 1.7.x was giving me problems on centos22:23
mgilesseemed to cause a recursive vagrant call22:23
portdirectwhat platform you using/virt backend?22:23
*** TxGirlGeek has joined #openstack-kolla22:23
mgilessaw it on ubuntu and then again on my mac22:23
mgilessame problem22:23
portdirectvbox virt?22:24
mgilesyes22:24
portdirectbut your env works now with the changes you have made?22:24
mgilesyes, it did. I'm retrying following your instructions though.22:25
*** jtriley has joined #openstack-kolla22:25
*** TxGirlGeek has quit IRC22:25
portdirectgreat - I'm gonna grab a bite to eat then I'll get them up on gerrit so we can work properly on them22:27
mgilessounds good.  I may be offline by then, but will post comments in the morning.22:27
*** msimonin has quit IRC22:28
*** msimonin1 has joined #openstack-kolla22:28
*** msimonin1 has quit IRC22:28
portdirectsdake: (if your about - you need vagrant 1.8.1 (i've tested it) on centos for this to work - if your running the 1.7.x that I had in the gist then you may have issues with the workers getting added to k8s: uninstall the vagrant rpm and 'rm -rf ~/.vagrant.d' and start over - sorry dude..22:29
*** jtriley has quit IRC22:29
portdirectsdake: though if you've not touched vagrant since we set it up the other day then i think you should be ok22:30
portdirectmgiles: cheers22:30
*** chas has joined #openstack-kolla22:30
*** srwilkers_ has joined #openstack-kolla22:31
*** adrian_otto has quit IRC22:31
mgilescheers portdirect22:31
*** chas has quit IRC22:34
sdakeportdirect i started over ;)22:39
*** TxGirlGeek has joined #openstack-kolla22:39
sdakeportdirect hang tight - seem to have some progress22:39
*** jheroux has quit IRC22:45
*** goldyfruit has joined #openstack-kolla22:51
sdakeportdirect got rolling :)22:51
sdakeportdirect had errors with running outside vagrant22:52
sdakeportdirect had to ssh into the vagrant node to get any work done :)22:52
portdirectok - so almost home and dry22:52
portdirectwhat errors you getting?22:53
sdakemoment let me log out and i'll tell you22:53
sdakenote i was able to get ovsdb-server running by labeling the node properly22:53
sdakewhich is in the rest of the docs22:54
sdakeor ovsdbsomething or naother ;)22:54
sdakelike we were doing yesterday22:54
sdakei do see this: openvswitch-ovsdb-compute-rkrkj   0/1       Init:0/1   0          14m22:55
sdakestuck in init state22:55
sdakeis that normal?22:55
sdakeso two problems ;)22:55
sdakeportdirect note i am using vagrant 1.7.z from the magic place you mentioned yesterday22:55
portdirectok - lets look at them one at time - you pick whihc one first :)22:55
sdakelets look at outsideth e vagrant box first22:56
portdirectoh - ok didnt work for me on a fesh node - but good to know it's working for you :)22:56
sbezverksdake: not it is probably missing something22:56
*** slagle has quit IRC22:57
sbezverkthe easiest way to find out what is to run kubectl describe pod openvswitch-ovsdb-compute-rkrkj -n kolla22:57
*** unicell1 has quit IRC22:57
sdake[root@minime-03 halcyon-vagrant-kubernetes]# kubectl get pods22:58
sdakeThe connection to the server localhost:8080 was refused - did you specify the right host or port?22:58
*** Pavo has quit IRC22:58
sdakesbezverk lets tackle that one next22:58
portdirectok - did you run './get-k8s-creds.sh' ?22:58
sdakei ran . ./get-k8s-creds.sh22:59
sdakeand ./get-k8s-creds.sh22:59
sdakebut let me log out of root context22:59
sdakeand try just ./get-k8s-creds.sh22:59
sdakeportdirect [root@minime-03 halcyon-vagrant-kubernetes]# ./get-k8s-creds.sh23:01
sdakeConnection to 192.168.121.62 closed.23:01
jascott1sdake you have to label a node kolla_compute=true also for sbezverk's PS23:01
sdakejascott1 yup i got that :)23:01
jascott1kewl23:01
portdirecttry a kubectl command again23:01
*** diogogmt has quit IRC23:01
portdirectshould work this time23:02
sdakeok it works23:02
*** Pavo has joined #openstack-kolla23:02
sdakeso - i think kubernetes was still doing its setup23:02
portdirectI'll add better feedback to that script: https://raw.githubusercontent.com/portdirect/halcyon-vagrant-kubernetes/master/get-k8s-creds.sh23:02
Pavoevening23:02
sdakesup pavo23:03
Pavogotta question23:03
srwilkers_yo pavo23:03
portdirectcould you also run kubectl get nodes? just to satisfy my paranoia that they are all checking in?23:03
Pavohow hard would it be to use ESXi VMWare as a hypervisor using kolla-ansible?23:03
sdakeportdirect 4 nodes in ready state23:04
sdakepavo no idea23:04
jascott1thats a nova question right23:04
Pavowas just wondering if would be possible23:04
sdakeopenstack config = black magic to me :)23:04
sdakenot an operator23:04
Pavolol23:04
sdakenot clear to me how we orchestrate a system using helm23:05
sdakepod labeling etc23:05
sdakeoh well - problem for later ;)23:06
srwilkers_baby steps ;)23:06
sdakethats right23:06
portdirectsdake: wanna have a look at that pod now?23:07
sdakeportdirect which one23:07
sdakemariadb?23:07
portdirectthe one stuck in init23:07
sdakeoh right23:07
sdakesorry - mortal form grows weary :)23:07
sdakeneed sustinance23:08
sdakeso lets rock on that pod stuck :)23:08
portdirectnp, sbezverk you around too?23:08
sbezverksdake: kubectl describe pod openvswitch-ovsdb-compute-rkrkj -n kolla23:08
sdakehttp://paste.fedoraproject.org/493523/48046094/ -> http://paste.fedoraproject.org/493523/4804609423:09
sdakefailedmount23:09
sbezverksdake: you need to create one config map23:09
sdakeok - why?23:09
sdakefor the external config maps?23:10
sbezverkwhich is used for a workaround we have for dns and pods with net=host23:10
sdakepods with net=host = dataplane?23:10
sbezverksdake: It is long type I would prefer to exaplain verbally23:10
openstackgerritcaoyuan proposed openstack/kolla-ansible: Move barbican precheck into its own role  https://review.openstack.org/40446523:10
portdirecti can quickly try23:10
sbezverkbut let's do it differently23:11
sbezverkyou can disable workaround in values.yaml23:11
portdirectas I have worked round this on that k8s setup sdake is using23:11
sbezverkand then pod will not require this config map23:11
portdirectso it's not needed anymore23:11
sdakeok shall i delete this helm install then?23:11
portdirect(I'll shut up for a bit)23:12
sbezverksdake: change values.yaml for enable_resolve_conf_net_host_workaround: false23:12
sbezverksdake: yes helm ls23:12
sbezverkthen helm delete {what you see in previous output}23:12
sbezverkportdirect: what workaround you found for this?23:13
sdakesbezverk yup i know ls nd delete ;)23:14
portdirectsbezverk: https://github.com/portdirect/halcyon-kubernetes/blob/kolla_dev/kube-deploy/roles/kube-prep/templates/resolv.conf.j223:14
sdakeis only my second rodeo :)23:14
portdirectsbezverk: and I set up a route to the k8s dns service ip range from the hosts23:14
sbezverkportdirect: great, will work too.23:15
sbezverksdake: when you change that values please run helm install again23:16
kfox1111back.23:16
portdirectsbezverk: this is required for the kubelet to be able to mount RBD devices and a few other things as well23:16
*** yuanying has joined #openstack-kolla23:16
sbezverkkfox1111: can you check the error I saw when try to run helm_prebuild?23:16
sdakerunning23:17
kfox1111sbezverk: yeah. just starting to look at the reviews again.23:17
sdakesup kfox111123:17
sdakeok ready for m0ar!23:17
sdakekfox1111 any chance ou can bet your review into shape23:17
sdakekfox1111 i think it looks pretty close as is23:17
portdirectI'm gonna grab that food - back in 3023:18
sbezverkkfox1111: thanks, I reformated my openvswitch ps for new format, just waiting to get values.yaml generation23:18
sdakekfox1111 know your tired and whatnot :)23:18
sdakebet/beat23:18
kfox1111sbezverk: I didn't check in the results of tools/helm_prebuild.py  as I didn't want to complicate the initial review.23:18
openstackgerritcaoyuan proposed openstack/kolla-ansible: Move gnocchi precheck into its own role  https://review.openstack.org/40446823:18
kfox1111did you try that first?23:18
sbezverkkfox1111: Yes I ran helm_prebuild and it gave me some weird error23:19
kfox1111hmm...23:19
kfox1111maybe I missed checking in a file...23:19
kfox1111I'll do a fresh checkout of it to test.23:19
sdakekfox1111 might check the review comments sa well23:20
sdakenot passing pep8 gate etc23:20
sdakeok lets leave kfox1111 to it :)23:20
kfox1111yeah. was just lookingn for general idea of it was the right aproach. can polish once thats ok. :)23:21
sdakekfox1111 there is only one question in the review from me about api related thing23:21
sdakerest looks good to me - minus the not working part ;)23:21
kfox1111so, fresh checkout, tools/helm_prebuild.py worked for me.23:22
kfox1111and tools/helm_build_microservices.py ~/.helm/repository/local/ too.23:22
sdakehmm my review was rushed i don't recall seeing two tools23:22
sdake(had to pick up kids)23:22
sbezverkhm, not sure what it is then :-(23:23
sbezverkkfox1111: to create a new microservice do I need to add anything in all_values.yaml?23:23
sdakesrwilkers_ you went all out in the review :)23:24
kfox1111helm install kolla/neutron-openvswitch-agent --dry-run --debug --set selector_key=kfoxwashere | grep kfox23:24
kfox1111kfoxwashere: "true"23:24
kfox1111overrides seem to work too.23:24
sdakesrwilkers_ typically its just good enough to point to the gate failure not mark each indivdiual line23:24
sdakesrwilkers_ but up to you :)23:24
*** sayanta__ has quit IRC23:24
kfox1111sbezverk: yeah. it looks for a key based on the service name.23:24
sdakesrwilkers_ maybe you can make some new workflows for us :)23:24
kfox1111we could make that optional too.23:24
srwilkers_whoops23:24
kfox1111oh. maybe thats whats failing for you maybe.23:25
sdakesrwilkers_ no woops about it23:25
sbezverkkfox1111: ahh that was missing then23:25
kfox1111if there are other directories there.23:25
*** unicell has joined #openstack-kolla23:25
sdakeportdirect so i think your directions are good to go - i've tested em23:25
sbezverkso before running tool I need to add section into all_values.yaml23:25
sdakeportdirect lets get em in the docs in some way - they need a bit of tidying but we can iterate on em23:25
*** Pavo has quit IRC23:25
srwilkers_sdake, pardon the ignorance but what workflows?23:26
sdakesrwilkers_ the gerrit review work you did - is the openstaack workflow23:26
kfox1111sbezverk: yeah. do you want me to make that optional?23:26
sdakesrwilkers_ followed by two +2 reviews23:26
kfox1111probably fine I guess.23:26
sdakeor -1s with comments fixed23:26
sdakesome projects are harder then others23:27
sdakekolla is pretty loose with the reviews23:27
sdakegetting something into neutron for example - mission impossible ;)23:27
srwilkers_ah, i got you. wasnt sure what you meant by new ones :)23:27
srwilkers_no kidding23:27
sbezverkkfox1111: please because even if I added empty section it does not like it either23:27
sdakean hp manager once told me they bring donuts into the office every time a nova patch merges they produced ;)23:28
*** TxGirlGeek has quit IRC23:28
sdakei was like "are you serious?"23:28
sbezverkso it really want to see something inside. having copy just common part should be mandatory23:28
sdakehe was serious. ;)23:28
openstackgerritcaoyuan proposed openstack/kolla: Replaces uuid.uuid4 with uuidutils.generate_uuid()  https://review.openstack.org/40440623:28
srwilkers_must be depressing getting donuts 2-3 times a year23:28
sdakesrwilkers_ wow23:28
sdakesrwilkers_ :)23:28
srwilkers_implied sarcasm of course23:28
srwilkers_;)23:28
kfox1111sbezverk: k. will do in a few min.23:29
sdakefortunately there are no donut parties for kolla23:30
sdakestill laughing about that one srwilkers_ :)23:32
*** vhosakot has quit IRC23:32
srwilkers_;)23:32
sdakelaughed so much my daughter wanted me to explain it to her23:33
srwilkers_oh man23:33
kfox1111sdake: show her this: https://www.youtube.com/watch?v=4ht22ReBjno :)23:35
kfox1111"waaaa??"23:35
kfox1111:)23:35
*** Pavo has joined #openstack-kolla23:35
jascott1k8s for kids!23:36
srwilkers_yes!23:36
jascott1"do you wish you had your own HA Minecraft cluster?"23:36
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Initial Helm support  https://review.openstack.org/39629623:36
Pavoso if I deploy on say 3 nodes and a few weeks later I want to add another 3 nodes, do I have to do a destroy to add the new nodes?23:37
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Initial Helm support in the gate  https://review.openstack.org/40433223:38
kfox1111Pavo: shouldn't have to23:38
Pavoreconfigure?23:38
jascott1sdake all are we agreeing to use entrypoint for init container for microservice deployment yamls?23:38
kfox1111jascott1: optionally.23:38
jascott1pavo are you talking about adding k8s nodes?23:39
sdakejascott1 its in the spec23:39
Pavono no not yet, I am told kolla-ansible currently23:39
*** mgiles has quit IRC23:39
jascott1ah23:39
kfox1111jascott1: don't really need my pods having service accounts. just entrypoint maybe for blocking until unix sockets come up.23:39
jascott1yes!23:39
Pavoso only have to use kolla-ansible reconfigure after I updated my inventory file correct?23:40
sdakejascott1 in an older review that probably flew by you I asked kfox1111 where was init-container, and he suggested we tackle that in a followon review once we get the structure in place23:40
kfox1111+1.23:40
sdakerather init-container with entrypoint23:40
jascott1cool so I am working on glance charts based on sbezverk's patch23:40
kfox1111lets do jinja2 -> gotl/helm in one ps, then add entrypoint as a new feature ps.23:41
sdakei think portdirect is too :)23:41
jascott1wondering how to handle glances db dependency23:41
sdakeso the way we handle conflicts on the work is via launchpad23:41
sdakethat way we dont both do the same thing23:41
kfox1111jascott1: I think this is another case where we might want to use helm deps.23:41
portdirectnope - keystone/ceph23:41
sdakeportdirect ooops thought you mentioned you wer edoing glance23:41
portdirectnp :)23:42
sdakehard to keep it all straight- hence the launchpad :)23:42
kfox1111have the kolla-common kind of thing where we put skeleton jobs, like the keystone-endpoint creation job,23:42
jascott1why dont we just make (for instance) glance-db at same level as glance-api and glance-registry? then its optional and maybe use values file to control if it gets installed23:42
kfox1111and then make a glance-create-entrypoint job package that includes it and calls it with the right params.23:43
kfox1111jascott1: I think your up a level at service packages.23:44
jascott1in service there is micro1 micro2 which share the same db23:44
jascott1where to put db?23:44
jascott1(chart)23:45
*** inc0 has joined #openstack-kolla23:45
kfox1111jascott1: which review are you working off of?23:46
jascott1https://review.openstack.org/#/c/403959/23:46
*** lamt has quit IRC23:46
jascott1basically taking the glance k8s stuff from kolla-k8s and converting to gotpl following that lead23:47
kfox1111jascott1: yeah. there's kind of two parallel prototypes going right now...23:47
kfox1111https://review.openstack.org/#/c/396296/ is the other one.23:47
jascott1right23:47
jascott1we talked a lot yesterday about a more flat chart structure and not using requirements23:47
kfox1111the layout is different.23:47
kfox1111I think requirements might solve some issues.23:49
kfox1111for example, if we make a microservie rabbitmq, then the glance service package can include a rabbit of its own for rpc.23:49
kfox1111nova can too.23:49
jascott1yes but what is advantage of using helms requirements?23:50
sbezverkguys with this new approach, do NOT forget to re-run helm_prebuild whenever you change all_values23:50
jascott1i can install a named rabbit and tell my service about it23:50
sbezverk:-) I was scratching my head why I changed to ignore workaround but it still looking for workaround config map23:50
kfox1111jascott1: exactly that. being able to have a microservice instantiated in more then one service package as one.23:50
jascott1sorry i might be behind, you were proposing dynamically manipulating requirements file tho right?23:51
sbezverkkfox1111: do you think you can print out nicely the values you copy to microservice?23:51
kfox1111jascott1: thinking about it. if we keep versions in a single file, it would be pretty easy to fill in requirements with the right versions I think.23:51
kfox1111sbezverk: yeah. its just a yaml file.23:52
sbezverksince they are stored in a not very nice format in microservice directory23:52
kfox1111sbezverk: I was debating that a bit... we could generate it nicer, but then it would be more tempting for users to edit it directly then too.23:52
sbezverkkfox1111: I got it, I thought maybe if you print them out nicely it will give a way to visually inspect them one more time23:53
sbezverkbut it is up to you23:53
kfox1111oh... but... the way I'm writing it, I might be able to put a comment up at tthe top saying its generated....23:53
kfox1111then pretty print it.23:53
kfox1111let me try that...23:53
sbezverkkfox1111: so I was able install chart template using helm_prebuild tool and then helm install I am very very happy !!!!23:54
kfox1111sbezverk: awesome. :)23:54
*** goldyfruit has quit IRC23:55
sbezverkkfox1111: thank you!23:55
kfox1111np. :)23:57
*** Pavo has quit IRC23:57
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Initial Helm support  https://review.openstack.org/39629623:58
kfox1111sbezverk: try that one for values exported.23:59
kfox1111should be prettier.23:59
kfox1111and disclaimered. :)23:59
sbezverkkfox1111: one question though. do we really want oto check in this generated file into git? example now it has some my test bed specific settings23:59

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