[07:57] <erik_lonroth_> Hello!
[08:00] <erik_lonroth_> I'm encountering some problem with installing juju on ubuntu via "snap".  It fails to download and this is what I encounter. https://pastebin.com/LM6JGkDy - Is this something you have experienced too
[08:00] <erik_lonroth_> I commented on this: https://bugs.launchpad.net/click-package-index/+bug/1688529?comments=all
[08:00] <mup> Bug #1688529: X-Ubuntu-Series is required but not accepted <Click Package Index:New> <https://launchpad.net/bugs/1688529>
[08:39] <gvseghbr> Hi, I've some problems with bootstrapping a controller on my VMware cluster. Everything seems to be okay, up to the point the bootstrapping process tries to contact the controller API (via WebSocket). I get this error “09:56:03 DEBUG juju.api apiclient.go:842 error dialing websocket: Forbidden”, something to do with the X509 certificate.
[08:43] <gvseghbr> Here some more output: https://askubuntu.com/questions/953079/error-while-bootstrapping-on-vmware
[10:02] <magicaltrout> erik_lonroth_:
[10:03] <magicaltrout> i don't have an answer for you
[10:03] <magicaltrout> but
[10:03] <magicaltrout> if you provide X-Ubuntu-Series: 16
[10:03] <magicaltrout> you do get a direct link to the download url
[10:05] <magicaltrout> curl -H X-Ubuntu-Series:16 https://api.snapcraft.io/api/v1/snaps/details/juju
[10:54] <rick_h> erik_lonroth_: interesting. seems like that might be a snap bug that will have to get looked into
[10:55] <rick_h> oh, you filed it heh
[10:55] <rick_h> or found one
[15:46] <stormmore> o/
[19:24] <bdx> hey, what is the supported graphite charm I should be using?
[19:50] <rick_h> bdx: not sure, the community ones seem to be older from folks that aren't maintaining them.
[20:03] <bdx> rick_h: you use the grafana + prometheus + collectd charms in your monitoring stack?
[20:03] <bdx> rick_h: do you know what interface the collectd and prometheus charms relate on?
[20:03] <rick_h> bdx: yea, telegraf, grafana, prometheus. https://jujucharms.com/u/prometheus-charmers/ is the IS folks that do most of that setup
[20:04] <bdx> rick_h: how does collectd fit into the picture?
[20:05] <rick_h> bdx: looking, looks like it's a subordinate like telegraf. Just uses juju-info to communicate like telegraf.
[20:05] <bdx> ha
[20:05] <bdx> so you would think
[20:05] <rick_h> Most of those folks are offline (UK) or not yet on (AU/etc)
[20:05] <bdx> rick_h: its cool man
[20:05] <rick_h> bdx: but also might be worth an email to the juju list, I'm honestly not sure as I've not set it up :(
[20:06] <bdx> ahh
[20:26] <rick_h> bdx: ooh, did you know about charm set extra-info? https://github.com/juju/charmstore/issues/774#issuecomment-327590988
[20:27] <bdx> rick_h: that is great
[20:27] <bdx> man
[20:27] <bdx> so many great things happening
[20:28] <rick_h> bdx: can put any key/value in there for some fun stuff
[20:29] <bdx> rick_h: thats great ... don't we have a similar thing for models now too?
[20:29] <rick_h> bdx: for models? I mean there's annotations over the API but not sure what's on the CLI for it.
[20:30] <rick_h> what's nice here is how it's right in the charm command. I know there was an extra-info api and could be hit up with a python client/etc, but awesome it's baked into the charm command cli for quick hacky foo like that
[20:31] <bdx> yeah totally
[20:31] <bdx> really cool
[20:37] <bdx> I think I have a bunch of places where triggers will take over in my charms
[20:37] <bdx> triggers use case: https://gist.github.com/jamesbeedy/e36b4bd4cf35d1f48682acc1605c373a
[20:38] <bdx> rick_h: I've got this manual vs relations battle similar to ^
[20:38] <bdx> going on in almost every charm
[20:38] <bdx> I think triggers will really help clear a lot of that out
[20:41] <bdx> https://gist.github.com/jamesbeedy/e36b4bd4cf35d1f48682acc1605c373a#file-data_api-py-L42
[20:46] <bdx> rick_h: I found it!
[20:46] <bdx> look
[20:46] <bdx> lol
[20:46] <bdx> from the collectd charm http://imgur.com/a/n9b6p
[20:48] <bdx> ^ what I call a "hunt and slap"
[20:48] <rick_h> bdx: lol
[20:49] <rick_h> bdx: very sneaky
[20:49] <bdx>  deadly
[20:53] <bdx> rick_h: will you aid me in finding the elusive "aluria's PPA" ?
[20:53] <bdx> the single PPA needed to make prometheus exporting work with the collectd charm
[20:54] <rick_h> bdx: https://launchpad.net/~aluria/+archive/ubuntu/bootstack
[20:54] <rick_h> bdx: that's the PPA referenced
[20:54] <bdx> rick_h: awesome!
[20:57] <bdx> rick_h: nice find
[20:58] <bdx> rick_h: ok, bunch of cruft here
[20:58] <bdx> rick_h: I am impressed with your ppa finding ability
[20:58] <bdx> rick_h: still no excuse for the state of this collectd charm though
[20:58] <rick_h> bdx: https://launchpad.net/ubuntu/+ppas
[20:58] <bdx> so
[20:58] <bdx> ahh
[20:58] <bdx> nice
[20:59] <bdx> lol
[20:59] <bdx> so yeah
[20:59]  * rick_h is a good typer in a search box :)
[20:59] <bdx> collectd charm supports xenial and trusty, but the prometheus export functionality is only supported from aluria's ppa for trusty
[20:59] <bdx> graphite_export functionality is currently broken
[21:00] <bdx> soooo
[21:00] <bdx> you can use the collectd charm with aluria's repo on trusty I'm assuming
[21:00] <bdx> this totally suck
[21:00] <bdx> s
[21:01] <rick_h> bdx: so you can try to build it on a later series if it still works
[21:01] <bdx> rick_h: the charm deploys on xenial fine
[21:01] <rick_h> bdx: so you can head to https://launchpad.net/~aluria/+archive/ubuntu/bootstack/+packages and click "copy packages into your own PPA, and then you change the series when you copy them
[21:02] <rick_h> bdx: I mean the package, if it works on the series or not
[21:02] <bdx> oh really
[21:02] <rick_h> yea
[21:02] <rick_h> that's if the software package works as is across series, many will but not sure here.
[21:04] <bdx> got it
[21:04] <bdx> I'll give it a try
[21:05] <bdx> rick_h: thx
[21:05] <rick_h> then obviously change the PPA setting in the charm config to your own PPA and such
[21:05] <rick_h> bdx: cool, let me know how it goes. Hopefully it'll work out.
[21:13] <bdx> rick_h: so, making progress http://paste.ubuntu.com/25480346/
[21:13] <bdx> I was able to copy over the packages to my own ppa, and build them for xenial
[21:14] <bdx> they all built fine, and are in my "peopledatalabs" ppas
[21:14] <bdx> ppa
[21:14] <bdx> but I'm thinking I may need to do something to get a releases file
[21:14] <bdx> I was getting the same error when using the bootstack ppa too
[21:14] <bdx> hmm
[21:15] <rick_h> bdx: yea, so looking at that error...it's because the ppa doesn't have anything for your series
[21:16] <rick_h> bdx: so have to make sure the charm series matches your PPA and that in that PPA is a RELEASES file with content
[21:16] <rick_h> bdx: could be caching/etc for something newly built
[21:16] <rick_h> bdx: is the PPA private? I don't see it in the account
[21:17] <rick_h> oh wait, I do see it my bad
[21:17] <bdx> ahh, "in that PPA is a RELEASES file with content" can you give an example?
[21:17] <bdx> here https://launchpad.net/~peopledatalabs/+archive/ubuntu/ppa
[21:18] <rick_h> bdx: https://launchpad.net/~peopledatalabs/+archive/ubuntu/ppa/+packages so that shows pending
[21:18] <rick_h> with a failure?
[21:19] <bdx> where?
[21:19] <bdx> ooh
[21:19] <bdx> I see
[21:19] <rick_h> bdx: and still shows no packages "Number of packages:
[21:19] <rick_h> 0 source packages (471.0 MiB)
[21:19] <rick_h> 0 binary packages (4.7 MiB)"
[21:19] <rick_h> bdx: yea, have to poke around the PPA/package details bits there
[21:19] <rick_h> bdx: once they run there should be PPA build logs if you had them rebuilt vs just copied binaries
[21:20] <rick_h> bdx: so maybe they're in the build queue, might take a little bit depending on how busy they are
[21:21] <bdx> I see
[21:21] <bdx> totally
[21:21] <bdx> yeah ... I had them rebuilt when I copied them over, thinking it would be good thing to do
[21:21] <bdx> possibly I can also try with just copying for the heck of it
[21:21] <rick_h> yea
[21:22] <rick_h> so have to just be patient and wait for a PPA builder to come along and try to build it
[21:23] <rick_h> bdx: ok hover over the green gear icon for the first package
[21:23] <rick_h> bdx: "all builds were built successfully but not yet published"
[21:23] <rick_h> bdx: so it's not even the builders to wait on, but just the publish process which will build that releases file and you'll be off to the races
[21:24] <bdx> I see, I see
[21:24]  * rick_h has to run but will check in later if I can. Good luck!
[21:25] <bdx> kk, thx
[21:26] <gvseghbr> Hi, is there somebody who can help with bootstrapping a VMware controller?
[21:26] <gvseghbr> On my system it fails when the bootstrap process wants to connect to the API
[21:49] <bdx> rick_h: yeah man ... my fears were realized ... it was packaged for upstart
[21:49] <bdx> :(
[21:54] <bdx> rick_h: where I ended up athttp://paste.ubuntu.com/25480507/
[21:54] <bdx> http://paste.ubuntu.com/25480507/
[21:55] <bdx> looks like the collectd-exporter-prometheus.conf made it to /etc/init
[21:55] <bdx> but thats about it