[07:23] <kjackal> Good morning Juju world!
[09:43] <dakj> Hello guys, any idea about this issue with Landscape-Dense MAAS? https://askubuntu.com/questions/906763/haproxy-reverseproxy-relation-changed-in-landscape-dense-maas-bundle thnaks
[12:17] <lazyPower> dakj: have you re-used that haproxy charm by relating it to something else, then removing a relation?
[12:18] <lazyPower> dakj: i'm not positive this is the case, but the error its complaining about is two vhosts with the same name.  So either the charm is coded in such a way this scenario happened, or some operation was issued against the charm that caused it to duplicate the  vhost. I'm not certain which is at fault here, but its most certainly a defect in the charm, unless you've manually edited that haproxy cfg :)
[12:42] <dakj> lazyPower: to your first Q: no I used the bundle dedicated to deploy that and nothing else, no re-used. Second one: no, I've run its default cfg without manual edit.
[12:43] <dakj> lazyPower: I've re-run more time that bundle and after the commit with Juju gui the error has been always the same.
[12:43] <lazyPower> dakj: i'm deploying now
[12:44] <lazyPower> give me a moment to let this deployment settle. If it errors i'll scrape the logs and file a bug and ping you with the bug id.
[12:44] <dakj> lazyPower: ok, I'm waiting your result
[12:52] <lazyPower> dakj: from a basic `juju deploy landscape-dense` i received no errors
[12:53] <lazyPower> dakj: https://104.197.250.70 - the haproxy unit is available at this ip, and things seem to have settled correctly
[12:54] <dakj> lazyPower: did you do that via command line or via gun?
[12:54] <lazyPower> dakj: cli
[12:55] <dakj> lazyPower: let me try that, but you used landscape-dense in my lab I used landscape-dense-maas
[12:56] <lazyPower> dakj: ok. give the dense bundle a go and lets see if it behaves as we expect it to
[12:56] <dakj> lazyPower: I think is the same
[12:56] <lazyPower> I'm going to tear down this model unless there's additional validation you'd like to perform?
[12:56] <dakj> lazyPower: https://jujucharms.com/landscape-dense-maas/
[12:57] <lazyPower> yeah it appears that teh dense-maas bundle relies on container networking to alow multi-host scalability
[12:57] <lazyPower> the -dense bundle doesn't offer that, and i did run this deployment against a public cloud as I dont readily have maas available to me
[13:17] <dakj> lazyPower: I'm doing the commit of landscape-dense, five minutes and see the result.
[13:20] <lazyPower> ack
[13:32] <dakj> lazyPower: same issue
[13:33] <lazyPower> dakj: i'm not certain what the issue is, but it would be a good first step to file an issue against the haproxy charm. https://bugs.launchpad.net/charm-haproxy/
[13:37] <dakj> lazyPower: already done...no answer
[13:42] <lazyPower> dakj: do you have that bug # handy?
[13:45] <dakj> lazyPower: I wrote here: https://bugs.launchpad.net/landscape-bundles/+bug/1685212 and https://bugs.launchpad.net/charms/+source/haproxy/+bug/1686629 and https://bugs.launchpad.net/landscape-charm/+bug/1692061 and added a comment here https://bugs.launchpad.net/charms/+source/haproxy/+bug/1520305
[13:45] <mup> Bug #1685212:  Landscape Dense MAAS: hook failed: "reverseproxy-relation-changed" for landscape-server:website <Landscape Bundles:New> <https://launchpad.net/bugs/1685212>
[13:45] <mup> Bug #1686629: hook failed: "reverseproxy-relation-changed" for landscape-server:website <haproxy (Juju Charms Collection):New> <https://launchpad.net/bugs/1686629>
[13:45] <mup> Bug #1692061: Landscape Dense MAAS: hook failed: "reverseproxy-relation-changed" for landscape-server:website <Landscape Charm:New> <https://launchpad.net/bugs/1692061>
[13:45] <mup> Bug #1520305: reverseproxy-relation-changed fails configuration check failed <haproxy (Juju Charms Collection):New> <https://launchpad.net/bugs/1520305>
[13:47] <lazyPower> dakj: thanks, i'll try to get some eyeballs on that today from the landscape team if they have any additional bandwidth
[13:54] <lazyPower> dakj:  and just to be clear, you're destroying the model and running a fresh deployment every time you attempt to deploy the landscape bundle?
[13:59] <dakj> lazyPower: yes I've destroyed that before to commit the bundle.
[14:10] <Zico> Hi, I need some help on JUJU metrics setup. To get started, how to make it work on top of the scalable-wiki for example that is PHP and MYSQL?
[14:12] <rick_h> Zico: so there's a hook you use in the charm. You'd need to add a metrics hook to one of those two charms. check out https://jujucharms.com/docs/stable/developer-metrics
[14:19] <rts-sander> can multiple hooks run at the same time in the same unit?
[14:22] <Zico> ~/charms/wiki-scalable/trusty/haproxy$ more layer.yaml  ---> includes: ['layer:metrics']
[14:23] <Zico> in metrics.yaml --> metrics:   juju-units:
[14:23] <Zico> juju metrics --all shall reflect the number of units after 5 minutes?
[14:23] <rts-sander> "No more than one hook will execute on a given system at a given time. A unit in a container is considered to be on a different system to any unit on the container's host machine."
[14:23] <rts-sander> so no
[14:23] <Zico> Thank you Rick_H
[14:25] <rick_h> Zico: np, have fun
[14:27] <rick_h> rts-sander: right, only one at a time
[14:27] <rick_h> rts-sander: so that the hook authors should be able to rely on things not going nuts during a hook execution
[14:34] <Zico> Q: I created the layer.yaml, and added --> includes: ['layer:metrics'] in the layer.yaml and in metrics.yaml --> juju-units: ---> this supposed to give the count of units.. juju metrics --all is still empty (after 5 minutes).
[14:38] <mattyw_> Zico, did you upgrade the charm when you added the layer:metrics layer?
[14:40] <Zico> Mattyw_, No, I didnt upgrade, if I should do, please assist how ? :)
[14:41] <mattyw_> Zico, so you added layer:metrics to an existing charm and then deployed it from scratch?
[14:44] <Zico> Mattyw_, Charm was already deployed, I just added the layer.yaml and metrics.yaml... I thought it's hot deployable?!
[14:45] <mattyw_> Zico, charms aren't I'm afraid. You'll have to do juju upgrade-charm
[14:45] <mattyw_> Zico, but in that situation you may encounter this: https://bugs.launchpad.net/juju/+bug/1675851
[14:45] <mup> Bug #1675851: juju collect-metrics reports failed to collect metrics: no collect application listening: does application support metric collection? when charm is metered <upgrade-charm> <juju:Triaged> <https://launchpad.net/bugs/1675851>
[14:46] <mattyw_> ^^ so the best approach would be to rebuilt the charm and then juju deploy it
[16:18] <cmars> anyone here tried using zetcd instead of zookeeper with big data charms yet? i'm interested in evaluating kafka and zetcd appeals to me...
[16:18] <cmars> also, anyone here using kafka with golang clients? :)
[16:23] <tvansteenburgh> cmars: well, i snapped zetcd Friday night after the announcement :)
[16:23] <dakj> lazyPower: I made other tests and the results has been: using cli with these commands juju deploy landscape-dense and juju deploy landscape-dense-maas, landscape is deployed correctly while using both bundle via gui I obtained the same issue
[16:23] <tvansteenburgh> cmars: snap install zetcd --edge
[16:23] <cmars> tvansteenburgh, awesome!
[16:24] <cmars> tvansteenburgh, is there a layer for snaps, like layer:apt?
[16:24] <lazyPower> cmars: layer:snap
[16:24] <lazyPower> https://github.com/stub42/layer-snap
[16:24] <cmars> shouldve guessed :)
[16:25] <lazyPower> well poo you left
[16:27] <lazyPower> dakj: so you're saying it deploys correctly via cli but not the gui?
[18:13] <ChrisHolcombe> does charm-tools support py3.5?
[18:13] <ChrisHolcombe> i mean charmhelpers*
[18:14] <ChrisHolcombe> lazyPower, you prob know this :)
[18:14] <lazyPower> charm helpers should, yeah
[18:14] <lazyPower> charm-tools shoudl as well
[18:14] <ChrisHolcombe> are you installing that with pip3 or what?
[18:14] <lazyPower> no it ships with layer-basic.
[18:14] <ChrisHolcombe> oh i see
[18:14] <lazyPower> charmhelpers is in the wheelhouse
[18:14] <ChrisHolcombe> alright
[18:14] <lazyPower> so i guess yes i'm indirectly doing that
[18:14] <lazyPower> but the tooling is doing it for me :)
[18:15] <ChrisHolcombe> :)
[18:15] <ChrisHolcombe> i'll run tox on the build bits then
[18:30] <Budgie^Smore> o/ juju world
[18:57] <Zic> lazyPower: hi, if I specify a specific revision of the canonical-kubernetes charm bundle, does it also deploy the old revision of charm inside the bundle? (for the same purpose of last time, build a "iso-prod" preproduction cluster and test its upgrade before do it in production)
[18:57] <Zic> (specify a specific, oh, well done...)
[18:57] <lazyPower> Zic: yes, if you deploy an older charm/bundle, it should use those older resources instead of the snaps and deploy the 1.5 tarball based cluster.
[18:58] <Zic> cool, will test that tomorrow :)
[18:59] <Zic> lazyPower: how can I retrieve the bundle version of a already installed cluster? don't know if I really can after an installation
[18:59] <lazyPower> Zic: juju status should giv eyou the charm revisions at the top
[19:00] <Zic> yep, but how to guess the charm *bundle* revision? :x
[19:00] <lazyPower> Zic: then just walk backwards in the bundle revisions in the store. i can lend a hand to get you the bundle rev if you get me the version of say, kubernetes-master.
[19:01] <Zic> oh, I think I can do that, I'm not at office currently but I will mount my VPN to launch a juju status at the cluster
[19:04] <Zic> http://paste.ubuntu.com/24625879/
[19:05] <Zic> lazyPower: ^
[19:26] <cmars> what's the method for ignoring files during charm build, in layer.yaml?
[19:26] <cmars> any examples of this?
[19:32] <tvansteenburgh> cmars: add key -> ignore: [list, of, file, or, dir, names]
[19:33] <cmars> tvansteenburgh, doesn't work :(
[19:33] <cmars> tvansteenburgh, the ignore: key goes at the top-level of layer.yaml?
[19:34] <tvansteenburgh> yeah
[19:34] <tvansteenburgh> cmars: hrm https://github.com/juju/charm-tools/issues/312
[19:35] <cmars> tvansteenburgh, ok. yeah, i can't ignore builds, deps or .*.swp
[19:37] <magicaltrout> lazyPower: is there persistent storage, cinder etc in CDK?
[19:52] <bdx> JUJU_UNIT_NAME
[19:53] <bdx> doesn't exist in the bash env anymore?
[19:58] <lazyPower> magicaltrout: ceph rbd
[19:58] <lazyPower> Zic: sorry i got sidetracked looking now
[19:59] <bdx> http://paste.ubuntu.com/24626263/
[20:02] <lazyPower> Zic: https://jujucharms.com/canonical-kubernetes/21/
[20:02] <lazyPower> Zic: that has your master revision :)   and you can deploy this with juju deploy canonical-kubernetes-21
[20:02] <tvansteenburgh> bdx: are you in a hook context when you run that?
[20:43] <dakj> lazyPower: have you tryed to deploy that via juju gui?
[20:44] <lazyPower> dakj: i have not
[20:44] <lazyPower> dakj: were you saying it deploys as expected via the CLI but not via the GUI?
[20:49] <dakj> yes I confirm that, using the cli with command juju deploy landscape-dense/landscape-dense-maas landscape is deployed right, while via gui or via cli using the command juju deploy cs:~landscape/bundle/landscape-dense-maas-25 in both task I've the same issue with HAproxy
[20:49] <dakj> lazyPower: yes I confirm that, using the cli with command juju deploy landscape-dense/landscape-dense-maas landscape is deployed right, while via gui or via cli using the command juju deploy cs:~landscape/bundle/landscape-dense-maas-25 in both task I've the same issue with HAproxy
[20:50] <lazyPower> dakj:  ok, so you state that landscape is deployed right, you're not experiencing any issues with the haproxy on that working deployment?
[20:57] <dakj> lazyPower: at moment any issue with HAproxy. I don't know if that is a my problem on my system or is an issue on that bundle. My juju status is pasted here https://paste.ubuntu.com/24626715/ and here after login on landscape https://pasteboard.co/9tyPhi0Xg.png
[20:59] <lazyPower> dakj: everything appears in order in that screenshot and your pasted status output
[20:59] <lazyPower> so i'm not certain what's causing the issue, you've filed some detailed reports. The only thing I can think of to help anyone following up would be to describe int he parent bug against the bundle, that it was deployed via the gui
[21:00] <lazyPower> that way its obvious when they attempt the deployment that it wont be `juju deploy`, its a drag and drop operation. there's some slight differences there in how juju processes the request but i dont know enough about the gui internals to know
[21:02] <dakj> lazyPower: I'll update all post about that, indicating that issue is due from gui and not via cli.
[21:02] <lazyPower> dakj: thank you for taking good care of the issues filed dakj. its certainly appreciated
[21:05] <dakj> lazyPower: I've to thanks you and the other guys who helped me to resolve the issue with Openstack base via juju and all support to learn more thinks about Juju. I hope to to reciprocate you with my support.
[21:06] <lazyPower> dakj: :) Welcome aboard o/
[21:06] <dakj> lazyPower: see you, have a nice day.
[23:15] <thumper> lazyPower: who knows about the namenode charm for k8s ?