[01:09] <stub> vds: Last time I talked to my legal, I was told I can't bypass the clickthroughs in any way (including things like the Juju licence acceptance feature). However, if you look at the Oracle JRE distribution licence IIRC you can bundle it with software where it is required to make it work or make features work.
[01:10] <stub> vds: My interpretation being you would be able to embed the tarball in your charm or snap, but not in a charm layer. But I didn't put that interpretation to our legal.
[01:13] <stub> vds: If you want to use the Oracle JDK, the Cassandra charm requires the user to download (accepting the licence) and make the tarball available at a configurable URL. This was before Juju resources existed. It is a terrible user experience.
[03:01] <ericj> Ubuntu 16.04 Installed LXD and conjure-up snap packages.
 ran conjure-up kubernetes
 made it all the way to the end and received following error:
 "could not fetch IP addresses and link layer devices: cannot get all ip addreses
 Anyone know how to resolve this?
[07:37] <akshay__> https://www.irccloud.com/pastebin/3nNyg5ZI
[07:37] <akshay__> Need help
[07:45] <akshay__> Charm deployment fails as not able it add repository "cloud-archive:pike"
[07:45] <akshay__> Please see the pastebin for exact error
[08:14] <jryberg> Hi, I just started to play around with Juju and I'm impressed of the simplicity and how easy it is to bootstrap an entire Kubernetes cluster in the cloud. I do however have a question around the entire concept.  If you need to customize the entire kubernetes setup for example. Is this possible or should it only be used "as is". Will settings be ove
[08:14] <jryberg> rwritten during upgrades.  I know it's a hard question to answer but should charms be "fire and forget" or used as a base for further modifications?
[12:29] <elmaciej> Hello Everyone! I'm writing a charm which encapsultes a jar with some spark program. Does anyone knows how can I run action from hadoop-spark charm submit-spark during the deployment of my charm
[12:29] <elmaciej> I need your help charm masters!
[12:37] <kjackal> hi elmaciej, not sure about the masters but I can try to help
[12:37] <kjackal> how do you write your charm? python+reactive?
[12:38] <elmaciej> yes, that was my intention, I'm doing it based on vanilla charm
[12:38] <elmaciej> and to be honest it's first charm I have to write
[12:39] <kjackal> ok, no worries
[12:40] <kjackal> I would suggest you start by building the bigtop spark charm so you get familiar with the toolchain
[12:40] <kjackal> let me grab some links
[12:40] <kjackal> elmaciej: here is the bigtop project that has a number of charm layers. https://github.com/apache/bigtop
[12:41] <kjackal> the spark layers is here: https://github.com/apache/bigtop/tree/master/bigtop-packages/src/charm/spark/layer-spark
[12:42] <kjackal> so you should try building that one first. (git clone bigtop; charm build <pathtolayerspark>)
[12:42] <elmaciej> great, will do it now. Thank you very much.
[12:43] <kjackal> now you said you want to run a submit-spark during the deployment. I think you should first have to wait the deployment to finish and then submit a job.
[12:45] <kjackal> elmaciej: there is this action you ca take a look at to see how you can do a spark submit: https://github.com/apache/bigtop/blob/master/bigtop-packages/src/charm/spark/layer-spark/actions/spark-submit
[12:47] <kjackal> your jar can be inside your version of the charm or have it served from a remote location or make use of juju resources https://jujucharms.com/docs/2.1/developer-resources
[12:54] <elmaciej> kjackal : Thanks a lot!
[12:54] <kjackal> gl hf
[16:50] <bdx> kwmonroe: mind if I continue to hassle you about Greylog stuff?
[16:50] <kwmonroe> hassle away bdx!
[16:50] <bdx> I'll just start rattling off in that case
[16:50] <bdx> :)
[16:50] <bdx> 1) SSL
[16:51] <bdx> graylog has instructions for generating a key/cert and setting up ssl at the application/graylog level
[16:51] <bdx> http://docs.graylog.org/en/2.3/pages/configuration/https.html
[16:51] <bdx> its a bit cumbersome, and not really what I would want to go with anyway
[16:52] <bdx> I would rather just deploy an ssl terminating proxy infront of graylog
[16:52] <bdx> with the legit trusted key/cert from my CA
[16:55] <bdx> I'm thinking I should just be able to go ahead and setup the ssl terminating proxy in front of graylog, and forward to the web/api ports - bypassing the graylog ssl setup because terminating 1 hop in front of it
[16:55] <kwmonroe> bdx: agreed that an ssl proxy feels easiest.  GL needs the apache vhost proxy anyway, so just make the apache unit ssl-aware.
[16:55] <bdx> right
[16:56] <bdx> the other thing I was thinking about
[16:56] <bdx> I've used this https://gist.github.com/jamesbeedy/d587cbf048038fb274ef4cd55c4ee3dd
[16:56] <bdx> for quite some time
[16:57] <bdx> in front of apps that I want to terminate ssl infront of
[16:57] <bdx> I was thinking
[16:58] <bdx> it might be easier to just make the reverseproxy relation for haproxy do the right things to setup the extra frontend/backend for both 9000 on / and 9001 on /api
[16:59] <bdx> then we could kill the apache2 middle man
[16:59] <bdx> I gave the haproxy bits a try
[17:02] <bdx> kwmonroe: https://gist.github.com/jamesbeedy/b784bfd8779fca668b536332a10be5c1
[17:02] <bdx> my thinking behind ^
[17:02] <bdx> was such that it would just be easier to create the dict in python and just dump it to yaml
[17:03] <bdx> rather then trying to concat a bunch of templated strings inline
[17:03] <bdx> lol
[17:03] <bdx> but what I realized
[17:03] <kwmonroe> bdx: not to dissuade you from haproxy, but did you look at https://jujucharms.com/u/tengu-team/ssl-termination-proxy/?
[17:03] <kwmonroe> it's built with layer-nginx, so might handle the revproxy stuff ootb
[17:03] <kwmonroe> (plus letsencrypt support)
[17:04] <bdx> oh sick
[17:05] <bdx> sweet
[17:05] <bdx> ok, so lets use that as an example instead of haproxy
[17:06] <bdx> well
[17:06] <bdx> kwmonroe: the reason I went with haproxy, is because we have two ports that need forwarding based on the route right?
[17:06] <kwmonroe> i haven't actually used it myself, but i am encouraged that it calls the ngingx.congure_site bits, which i think will auto handle 9000 and 9001/api  bits: https://github.com/tengu-team/layer-ssl-termination-proxy/blob/master/reactive/ssl_termination_proxy.py#L121
[17:06] <bdx> kwmonroe: so this https://gist.github.com/jamesbeedy/b784bfd8779fca668b536332a10be5c1#file-haproxy_reverseproxy_test-py-L13
[17:06] <bdx> was my little bit of secret sauce
[17:07] <bdx> to accommodate the url route based routing
[17:07] <bdx> default / -> :9000, if /api, -> :9001
[17:09] <kwmonroe> yeah bdx, i *think* graylog is doing the right thing with the http interface: https://git.launchpad.net/graylog-charm/tree/reactive/graylog.py#n322
[17:09] <kwmonroe> that is setting a "services" string for both 9000 / and 9001 /api
[17:10] <kwmonroe> and i *think* the revproxy config_site bits of the nginx layer will do the right thing with those to make them vhost templates for nginx
[17:10] <bdx> https://jujucharms.com/haproxy/
[17:10] <bdx> it so contrived what type the relation data is lol
[17:10] <bdx> look at the last example for multiple backends
[17:10] <bdx> which is what I was trying to follow
[17:11] <bdx> but yeah
[17:11] <kwmonroe> oof, yeah, that example is hard to follow
[17:11] <bdx> the graylog charm is setting the correct type of data .... yaml strings
[17:11] <bdx> yeah
[17:12] <bdx> so you see how my example gist would work if we were just setting a yaml string, or even python types (just pass the dict to the relation)
[17:13] <bdx> it expresses the correct key:val in the data structure
[17:13] <bdx> it just has to get transformed into this crazy thing before it will make any sense to the haproxy / reverseproxy relation
[17:13] <bdx> lo
[17:13] <bdx> 9l
[17:14] <kwmonroe> lo9l fo real
[17:15] <bdx> I feel like building into this "crazy thing" any more then already has been done is just perpetuating the issue here
[17:16] <bdx> issue being the contrived data that the reverseproxy relation is accepting
[17:16] <bdx> it will never be something people will look at and be like "oh ok, I get it"
[17:17] <bdx> even after many hours now
[17:17] <bdx> :)
[17:17] <bdx> but I do get it, it just totally seems like the worst thing in the world
[17:18] <bdx> anyway
[17:18] <bdx> I don't even know where I was going with this
[17:19] <bdx> oh yeah, so I feel we are presented with a few not so great options here
[17:21] <bdx> given this isn't the most common use case, but its a pretty simple reverseproxy configuration that we should be able to support via charms w/o taking a round trip on the event horizon
[17:21] <kwmonroe> heh
[17:22] <bdx> possibly just "making it work" with the reverseproxy is the cheapest way to short term victory with Graylog
[17:23] <bdx> and looking at possibly doing something about the reverseproxy relation in the future
[17:23] <bdx> idk
[17:23] <bdx> possibly other people like it
[17:23] <bdx> I'm really forcing my view here
[17:23] <bdx> ha
[17:23] <bdx> sorry
[17:24] <bdx> but I feel my reasoning is justified
[17:24] <kwmonroe> i think one problem is the complex example in the haproxy charm.  i don't know what those options actually do, but the http interface example for rev proxy seems much simpler: https://github.com/juju-solutions/interface-http#requires
[17:25] <bdx> got it
[17:25] <bdx> ok
[17:26] <bdx> what they do
[17:26] <bdx> is allow you to configure more complex proxying
[17:26] <bdx> https://gist.github.com/jamesbeedy/b784bfd8779fca668b536332a10be5c1#file-haproxy_reverseproxy_test-py-L13
[17:26] <bdx> ^ takes care of proxying both of the routes
[17:27] <bdx>  / -> 9000 and /api -> 9001
[17:27] <bdx> by using the extra relation data context to configure extended routing/backend
[17:29] <bdx> its only complex because the data type/content isn't understandable
[17:29] <bdx> if was written out like this
[17:29] <bdx> http://paste.ubuntu.com/26090348/
[17:29] <bdx> and it said, "set the yaml string as relation data"
[17:30] <bdx> lol
[17:30] <bdx> but that (set the yaml string as relation data) isn't even whats going on
[17:30] <bdx> its not even a yaml string
[17:30] <bdx> I still don't know what it is
[21:07] <jose-phillips> hey
[21:07] <jose-phillips> exist a way to put a custom config
[21:07] <jose-phillips> on juju config file
[21:07] <jose-phillips> example i want to add something on the configuration of a charm
[21:07] <jose-phillips> cinder that is not supported on the yaml
[21:08] <bdx> jose-phillips: https://jujucharms.com/cinder/#charm-config-config-flags
[21:08] <jose-phillips> and if i want to add it on a different stanza
[21:10] <bdx> jose-phillips: make a bug report for the cinder charm about that
[21:11] <bdx> jose-phillips: https://bugs.launchpad.net/charm-cinder
[21:13] <jose-phillips> is exactly for this setting
[21:13] <jose-phillips> # A list of backend names to use. These backend names should be backed by a
[21:13] <jose-phillips> # unique [CONFIG] group with its options (list value)
[21:13] <jose-phillips> enable_backends
[21:19] <jose-phillips> also support enable_backends
[21:23] <bdx> jose-phillips: put that in a bug please
[21:24] <bdx> and post the bug back here after you have filed it
[21:47] <jose-phillips> ok bdx thanks
[21:47] <jose-phillips> another question did you know where juju store the containers configuration for openstack
[21:47] <jose-phillips> i need to create glance and cinder interface with 2 interfaces
[21:48] <bdx> jose-phillips: if you are deploying openstack to the lxd provider, you do that through lxd profile modification
[21:48] <jose-phillips> no is kvm
[21:48] <jose-phillips> novakvm
[21:48] <bdx> jose-phillips: so you have maas setup?
[21:48] <jose-phillips> yep
[21:48] <bdx> and you checked a bunch of kvm nodes into your maas?
[21:49] <jose-phillips> yep the deployment is completed on 3 nodes
[21:49] <jose-phillips> for example i dont need ceph
[21:49] <jose-phillips> because im using a netapp storage
[21:49] <jose-phillips> so i take 1 node for controller and 2 for compute
[21:50] <jose-phillips> on the controller node have 2 interfaces , data and storage
[21:50] <jose-phillips> when juju create the containters inside of controller node
[21:50] <jose-phillips> openstack controller node
[21:50] <bdx> jose-phillips: you need to create a feature request tp support netapp storge
[21:51] <jose-phillips> ok
[21:51] <jose-phillips> another question if i modify manually cinder.conf
[21:51] <jose-phillips> when will be overwritted?
[21:51] <jose-phillips> during upgrades only
[21:51] <jose-phillips> or restarting the container may overwrite the configuration
[22:50] <bdx> jose-phillips: modifying the config by hand is not supported in any way
[22:51] <bdx> jose-phillips: the openstack charms will keep persistence of the config files
[22:51] <bdx> modifying it by hand will only cause you grief