[00:00] <Budgie^Smore> hmm rookie mistake time? :-/
[00:01] <lazyPower> Budgie^Smore - i've lied to you
[00:01] <lazyPower> its non base64 encoded when looking at the secret via the webui
[00:02] <Budgie^Smore> OK *phew* don't scare me like that :P
[00:04] <Budgie^Smore> then it doesn't make sense why it is serving the wrong cert even after removing and readding the service :-/
[00:05] <Budgie^Smore> not to mention removing and readding the secret, simplifying the secret name, etc.
[00:06] <lazyPower> Budgie^Smore - when you're in a better position to debug, lets try to get you some TLC and get you unblocked.
[00:06] <lazyPower> i'm going be sticking around late tomorrow by about an hour or so, and i'm happy to help debug/reproduce then
[00:06] <lazyPower> think you'll have the time for that Budgie^Smore?
[00:07] <Budgie^Smore> that works, I am going to try and getting my virtualized environment up today
[00:07] <lazyPower> ok, that sounds great then
[00:07] <lazyPower> i'll see you tomorrow evening :)
[00:08] <Budgie^Smore> first step in solving a problem is figuring out if you have a problem at all, better to do that from a simplified cluster to rule out complexities
[00:09] <Budgie^Smore> I need to do it anyway since I want to be able to basically make a master node made up of VM (for now) that I can just spin up worker nodes... call me crazy but I want to containerize everything I can :P
[00:14] <Budgie^Smore> I would probably constainerize kubernetes masters if I could :P but that is totally just crazy talk
[00:15] <lazyPower> Budgie^Smore why do you think thats crazy talk? they are really gung-ho for self hosted at the developer watering holes
[00:15] <lazyPower> i'm not sold on the idea myself, but if its done well i can see why its attractive
[00:15] <Budgie^Smore> OK not sure crazy talk then
[00:15] <lazyPower> nah  just mostly crazy if you forget the triple-o work back in teh day and how big of a sideshow that was
[00:16] <lazyPower> not that it wasn't a feat of engineering, but that it was clunky and not really intuitive
[00:16] <lazyPower> ok i'm going to shut up now i feel like i'm dissing someone elses work...
[00:16]  * lazyPower checks out for the evening
[00:17] <Budgie^Smore> it is all about making sure that the services are all hardened correctly, I am not totally sold on the idea of the masters but everything else yes
[05:01] <Budgie^Smore> giving my laptop a real workout tonight, backing up a couple of VMs to USB and then I am going to do system reset and image it so I can wipe the hard drive and put Ubuntu on it!
[08:03] <kjackal> Good morning Juju world!
[09:13] <kjackal> Hi nobuto do you have a charm that uses the apache-php layer?
[09:19] <nobuto> kjackal: not really. but I demoed how to write a new charm in front of customers along with the official doc (https://jujucharms.com/docs/stable/developer-layer-example) it never worked with xenial.
[09:19] <nobuto> that's why I made a pull request to the layer.
[09:21] <kjackal> nobuto: I see. thank you for the PR. I am testing it right now with a dummy charm. Hopefully I am going to merge it. Lets see!
[09:21] <nobuto> kjackal: thanks
[09:34] <kjackal> nobuto: do you have a valid apache.yaml ?
[09:45] <kjackal> nobuto: I am getting this exception: http://pastebin.ubuntu.com/24000015/ Could be because the apache.yaml I found on the web is not valid
[09:47] <pranav__> Hey. Can we configure Juju 2.0 with maas server?
[09:51] <kjackal> pranav__: yes
[09:52] <kjackal> pranav__: https://jujucharms.com/docs/2.0/clouds-maas
[10:00] <nobuto> kjackal: let mee prepare apache.yaml for you to test.
[10:01] <pranav__> @kjackal many thanks!
[10:02] <chitteti> Hi juju World!!!
[10:04] <chitteti> charm release giving command giving error "ERROR cannot release charm or bundle: unauthorized: access denied for user"
[10:05] <chitteti> but able run the push command and its giving revision too
[10:05] <chitteti> url: cs:~ibmcharmers/xenial/ibm-db2-2 channel: unpublished
[10:09] <nobuto> kjackal: how about this? https://github.com/nobuto-m/layer-vanilla/blob/xenial/apache.yaml
[10:23] <kjackal> nobuto: I got another exception this time http://pastebin.ubuntu.com/24000102/
[10:23] <nobuto> kjackal: I used example vanilla layer. so checksum might be different. let me check.
[10:24] <kjackal> But this is past the patch your are proposing, so i will merge the PR. However, this layer seems rather old, and you might not want to use it for demos
[10:27] <nobuto> kjackal: right. vanilla layer needs to be updated to use new apache.yaml syntax: https://github.com/nobuto-m/layer-vanilla/blob/xenial/apache.yaml
[10:28] <nobuto> kjackal: anyway our new charm developing story in jujucharms.com might need a face lift.
[12:54] <Guest34515> channel wise charm revoke command is not working. how can we fix that?
[13:03] <kklimonda> how do I create services in bundle so more than one can be installed on a single machine?
[13:04] <kklimonda> right now, it seems to be ignoring "to" field, and spawn new machines for services
[13:05] <Guest34515> channel wise charm revoke command is not working. Please advice
[13:20] <marcoceppi> kklimonda: the to field should do it. could you share your bundle?
[13:20] <marcoceppi> Guest34515: are you getting an error message? Could you describe what's not working?
[13:31] <kklimonda> @marcoceppi: ah, I see - it seems if I add a new service to the bundle file, "to" is ignored
[13:39] <kklimonda> (add a new service and deploy again without cleaning the environment)
[13:40] <stokachu> kklimonda, is this with conjure-up?
[13:40] <kklimonda> no, pure juju 2.0
[13:40] <stokachu> ok
[13:42] <kklimonda> perhaps there is a different way to incrementally work on bundles?
[13:42] <kklimonda> so I can write them one application at a time
[14:20] <Guest26106> how to revoke specific revisions of a charm in charm store?
[14:41] <Guest26106> how to revoke specific revisions of a charm in charm store?
[14:41] <Guest26106> please help
[14:48] <marcoceppi> Guest26106:  are you getting an error message? Could you describe what's not working?
[15:23] <bildz> good morning
[15:23] <bildz> I am wanting to bootstrap juju to perform a canvas install of openstack, not through autopilot
[15:23] <bildz> the issue I am having is the internal network created by the lxd bridge on the bootstrapped juju machine
[15:23] <bildz> 10.0.0.0/24
[15:26] <marcoceppi> bildz: does that collide with your current network?
[15:27] <bildz> no its NAT'ed and preventing root based containers from getting a routable IP
[15:28] <bildz> I need the LXD bridge to use the correct DHCP, instead of the default bridge network
[15:34] <bildz> \o/
[15:37] <h00pz> ok guys how the heck do we reconfigure lxdbr0 to use my existing network (and dhcp) when deploying an app instead of going rogue and uising it own defined and useless 10.x.x.x network
[15:40] <bildz> marcoceppi: h00pz and I work next to each other
[15:43] <marcoceppi> bildz h00pz is this on maas?
[15:44] <h00pz> the hosts are deployed by maas but avoiding using autopilot as it sucks ass at placement
[15:44] <h00pz> we stood up a standalone juju controller and ‘juju add-machine ssh:<host>’ for all the computes
[15:45] <h00pz> then we added the openstack env and created the lxd containers for the various services but when it came to the lxd networking it went and used 10.x.x.x
[15:45] <h00pz> we would like to know how to change that lxd networking to use the same network and dhcp as the hosts they will be on
[15:50] <h00pz> marcoceppi: any idea how to hack the lxd bridges ?
[16:26] <kjackal> kwmonroe: cory_fu: and easy to merge update on the readme https://github.com/juju-solutions/layer-cwr/pull/86
[16:37] <bdx> I posted this in #netfilter and #lxdcontainers, possibly someone here has some insight ...
[16:37] <bdx> having some issues getting packets through to lxd containers via iptables nat, wondering if someone might shed some light on my attempt to nat from host to container
[16:38] <bdx> I'm applying a prerouting rule on my external interface in order to nat through the host to a lxd container on lxdbr0, the prerouting rule is "iptables -t nat -A PREROUTING -i ens3 -p tcp --dport 6379 -j DNAT --to 10.0.0.160:6379"
[16:38] <bdx> the packets don't seem to be making it through to the container though.... I'm wondering if there are any tricks of the trade I'm missing here?
[16:40] <bdx> trying to introspect the ufw rules docker creates in an attempt to recreate
[16:45] <kklimonda> bbcmicrocomputer: which contrail charms on jujucharms.com are most up to date?
[16:50] <kklimonda> https://api.jujucharms.com/charmstore/v5/cassandra-29/archive/config.yaml - why is install_sources type "string" when the default value is actually a list?
[16:54] <bbcmicrocomputer> kklimonda: https://jujucharms.com/u/sdn-charmers/
[16:54] <kklimonda> thanks
[16:54] <bbcmicrocomputer> kklimonda: bundles are here - http://bazaar.launchpad.net/~sdn-charmers/+junk/contrail-deployer/files/head:/bundles/
[16:55] <bbcmicrocomputer> kklimonda: works best with Contrail 3.2/3.1 commercial packages from Juniper
[16:55] <kklimonda> have you looked into dpdk vrouter?
[16:55] <bbcmicrocomputer> (require license)
[16:55] <bbcmicrocomputer> kklimonda: these charms don't support dpdk
[16:55] <bbcmicrocomputer> Contrail 4.x charms from Juniper should do (due April)
[16:56] <kklimonda> sigh, I need R3.1 with dpdk and juju - fortunately I'm familiar with contrail itself, so I just have to unknowns
[17:44] <cholcombe> anastasiamac: upgrading to juju 2.1-rc1 to fix the bug: https://bugs.launchpad.net/juju/+bug/1605241 causes juju to no longer be able to bootstrap a localhost environment.  It just says:cloud localhost not found
[17:44] <mup> Bug #1605241: lxd instances not starting <conjure> <juju:Fix Committed> <https://launchpad.net/bugs/1605241>
[17:49] <bdx> is there a method in charmhelpers that returns the primary network interface?
[17:51] <bdx> ahh, just found it - charmhelpers.contrib.network.ip.get_iface_addr()
[17:52] <bdx> even better - charmhelpers.contrib.network.ip.get_iface_from_addr(addr), nice
[18:21] <lazyPower> Zic - you around?
[18:46] <rick_h> Juju Show #6 in 14min
[18:47] <rick_h> get your popcorn
[18:47]  * jrwren fetches popcorn
[18:49] <rick_h> thedac: arosales marcoceppi lazyPower and anyone else I'm missing the HO url will be https://hangouts.google.com/hangouts/_/ytl/jtR7zxxKKNe2lyJ_QtFXBACCGGaZLppiaK6hWnMYUyI=?eid=103184405956510785630
[18:50] <rick_h> and the viewing url is: https://www.youtube.com/watch?v=K-cWDvM2zts
[18:50]  * thedac nods
[18:51] <arosales> rick_h: ack omw
[18:53] <thedac> rick_h: I am getting you do not have access to this page
[18:53] <rick_h> thedac: https://hangouts.google.com/hangouts/_/ytl/jtR7zxxKKNe2lyJ_QtFXBACCGGaZLppiaK6hWnMYUyI=?eid=103184405956510785630&hl=en_US&authuser=0 is my full url
[18:54] <rick_h> thedac: last time folks had to remove the hl and authuser keywords, maybe try setting up authuser to the right one for your account
[18:54] <thedac> ok
[18:54]  * rick_h also manually invites you in via email
[18:54] <thedac> thanks
[18:55] <magicaltrout> doesn't modern technology suck?! ;)
[18:56] <rick_h> 5 minute warning
[18:56] <rick_h> magicaltrout: at times...then it does magical things and tries to make up for it
[18:56] <thedac> just fyi, still not able to get in. No email received
[18:56] <thedac> Sure this is not restricted to a specific circle?
[18:56] <rick_h> thedac: try https://hangouts.google.com/call/kwu2kkxx5ve5rdlgkdcznmwoeae
[18:57] <thedac> That seems to be working
[18:57] <rick_h> arosales: marcoceppi lazyPower and anyone else ^
[19:04] <arosales> youtube play list
[19:04] <arosales> https://youtu.be/OBseJVHuVXI?list=PLW1vKndgh8gJS4upPNaXiYYHnCmFdWk03
[19:10] <magicaltrout> sat in a darpa webex and office hours, this is like multi tasking overload
[19:11] <mbruzek> Can I get a link to "watch" the juju sho?
[19:12] <magicaltrout> mbruzek: https://www.youtube.com/watch?v=K-cWDvM2zts
[19:12] <mbruzek> Thanks magicaltrout
[19:15] <mbruzek> marcoceppi: is it like brackets?
[19:16] <arosales> magicaltrout: lolz re darpa webex :-)
[19:17] <marcoceppi> mbruzek: hah, you wish
[19:27] <cholcombe> how do you remove a storage pool from juju lol?  I can't seem to find the cmd
[19:29] <arosales> cholcombe: looking here https://jujucharms.com/docs/stable/charms-storage
[19:29] <arosales> I think it is also dependent on when you want to remove the pool.
[19:30] <cholcombe> arosales: yeah i was looking there
[19:30] <cholcombe> everything there is about creating storage pools.  nothing about removing them
[19:30] <cholcombe> is it tied to the controller maybe?
[19:30] <arosales> ya I am also looking for remove
[19:31] <marcoceppi> https://insights.ubuntu.com/2017/02/10/webinar-getting-started-with-the-canonical-distribution-of-kubernetes/
[19:32] <arosales> cholcombe: may have to ping in #juju-dev
[19:32] <cholcombe> arosales: ok
[19:32] <arosales> cholcombe: I think wallyworld and axw were working on storage and there was some gaps
[19:32] <arosales> cholcombe: would be interested what you find out for 2.1 support
[19:32] <cholcombe> arosales: yeah i've talked with axw a few times.  I might ping him on this
[19:32] <arosales> cholcombe: +1
[19:33] <arosales> I think they come online here in a bit
[19:33] <arosales> ~3-4 hours
[19:33] <arosales> I think you can catch them more easily on west coast time
[19:33] <arosales> cholcombe: sorry I don't have a better answer
[19:33] <cholcombe> arosales: no worries
[19:35] <arosales> cholcombe: asked folks in the hangout too, but no command that we were able to find
[19:36] <cholcombe> arosales: yeah i don't think it exists.  that is really strange
[19:37] <rick_h> axw: the destroy is coming? ^
[19:37] <kklimonda> interesting, juju is hardcoded to connect to streams.canonical.com, even if local mirrors for tools and images are configured
[19:38] <kklimonda> that was a cause of a very long delay between juju deploy and MAAS starting to provisiong a machine
[19:42] <cholcombe> arosales: do you know the env variable i have to set to allow loopback devices in lxc with juju?
[19:49] <cholcombe> axw: ^^
[19:56] <arosales> cholcombe: is that ENV or LXD profile?
[20:00] <cholcombe> arosales: i thought i saw in a PR that you could set an env variable for juju and it would set the profile on creation
[20:00] <cholcombe> arosales: http://reviews.vapour.ws/r/1154/
[20:01] <cholcombe> looks like it says if StorageConfig.AllowMount is true than it sets it
[20:01] <arosales> cholcombe: ah ok :-)
[20:02] <arosales> good to know thanks cholcombe
[20:02] <cholcombe> arosales: https://github.com/juju/juju/pull/1826/files#diff-abd61728f26e92bea6ee732aa19f7808R17
[20:04] <arosales> cholcombe: good stuff
[20:05] <cholcombe> we need to document this.  this was entirely too hard to find
[20:13] <arosales> cholcombe: could you file a bug @ https://github.com/juju/docs/issues/
[20:13] <cholcombe> arosales: yup will do
[20:53] <rahworks> Hello all I followed the “kubernetes cluster Easy Way" Tutorial and decided to add deis workflow to it. The helm install failed at the deis install step with the following message. Error: forwarding ports: error upgrading connection: Upgrade request required.. Any suggestions on how to proceed?
[20:54] <lazyPower> rahworks - the "upgrade request" bits are due to the APILB charm. Its a layer7 router and it doesn't support SPDY, which kubernetes requires. There's a bug to replace this with an ELB as i know you are an AWS shop - https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/183
[20:54] <lazyPower> rahworks - additionally we are cycling towards replacing with HAProxy for the non cloud-koolaid version of that service
[20:56] <lazyPower> rahworks - there is a published work around for the helm installer failure because of the apilb - https://kubernetes.io/docs/getting-started-guides/ubuntu/troubleshooting/#common-problems
[20:56] <rahworks> lazypower thanks for the links, will take a look.
[21:02] <ravenpi> I love deploying to containers, because it "boots" so darn fast.  But it seems I always need a "base" charm installed on a physical system before I can install additional charms to containers on that physical system.  Is there a dummy juju charm I could install to set up a physical system, then install the charms I actually care about as containers?
[21:04] <lazyPower> ravenpi - juju deploy ubuntu
[21:04] <ravenpi> D'oh!  It is safe to say I would never have thought of that.  Too darn obvious.  :-)  Thanks!!
[21:04] <lazyPower> anytime :) we've hidden it in plain sight.
[21:05] <ravenpi> +1
[21:08] <lazyPower> rahworks - you're going to find another issue after that helm work-around though
[21:08] <lazyPower> rahworks - the deis chart is going to try to provision a service of type LoadBalancer, which will never be satisfied. bdx and i spoke to this lastnight
[21:08] <rahworks> ohh ok...
[21:09] <lazyPower> rahworks - we'll need to submit a patch for an alternative path (users on bare metal will love us for this) where it uses NodePort service type, or we'll have to manually configure an HAProxy alternative to forward the deis requests to the router
[21:09] <lazyPower> rahworks - additionally, if you have ingress=true on your workers, the deployment will never complete, as the ingress controller is occupying port 80, which the deis router wants.
[21:10] <rahworks> One extra step I did do was to allow all tcp traffic from my workstation...via sg
[21:10] <lazyPower> rahworks - are you trying this in lxd?
[21:12] <rahworks> just applying the dais install to the canonical-kube install... nothing lxd specific
[21:12] <rahworks> just applying the deis install to the canonical-kube install... nothing lxd specific
[21:12] <lazyPower> ok, that statement of "allow all traffic from my workstation" caught me off guard, not sure how that fits into the order of operations here.
[21:13] <rahworks> ohh... well after i updated the config to point to port 6443, the security groups setup for the master defaults to block that port.
[21:14] <lazyPower> rahworks - you should be able to juju expose kubernetes-master, and get that unblocked. its just defaulted to unexposed in HA formation to help isolate traffic away from it (read: slightly more secure by default)
[21:14] <rahworks> ohh ok..
[21:28] <bdx> lazyPower: container networking in 2.1 you say???
[21:28] <lazyPower> bdx - kick the tires and tell us what works for you and what doesnt :)
[21:29] <bdx> omg - on it
[21:33] <lazyPower> bdx https://lists.ubuntu.com/archives/juju/2017-February/008595.html
[22:18] <cholcombe> evilnick___: so yeah that setting doesn't seem to do it
[22:19] <cholcombe> is there a way to list the model config values currently set?
[22:19] <evilnick___> cholcombe, :(
[22:19] <evilnick___> yes, just juju model-config
[22:19] <cholcombe> evilnick___: cool.  do i need to create the model before this'll take?
[22:20] <evilnick___> cholcombe, you can set it as a default for models, then create a new model
[22:20] <evilnick___> i'm not sure if that will make a difference
[22:20] <cholcombe> ok then yeah it doesn't work :-/
[22:22] <evilnick___> ah. in that case maybe it didn't make it to LXD
[22:22] <cholcombe> evilnick___: yeah wallyworld just commented
[22:23] <cholcombe> that stinks.  i really want to test gluster on lxd so i can have it grab some floating ip's from my bridge and use them
[22:23] <cholcombe> allocating elastic ip's on ec2 is a pain
[22:23] <wallyworld> there are security issues with loop mounts
[22:23] <evilnick___> cholcombe, well, sorry about that, but at least I can now turn that issue into removing the reference from the storage page.
[22:23] <cholcombe> wallyworld: yeah i saw in the commit
[22:23] <wallyworld> it was enabled with lxc because those were prvileged
[22:23] <cholcombe> i see
[22:24] <cholcombe> wallyworld: can we at least give people the option to use said unsafe thing?
[22:24] <wallyworld> there are plans to come up with a solution, but there are things to consider so we don't do bad things
[22:24] <cholcombe> i'm totally onboard with this being bad in production but for dev it's difficult to work around
[22:24] <wallyworld> yeah understood
[22:25] <wallyworld> it's something that fell off the "most important thing to do next" list
[22:25] <cholcombe> yeah i understand
[22:25] <wallyworld> i'll prod the right folks to look into it
[22:25] <cholcombe> wallyworld: are there any block devices that'll work on my local lxd?
[22:26] <wallyworld> without loop devices, i don't think so
[22:26] <cholcombe> gah
[22:27] <wallyworld> leave it with me and i'll dig to get a proper answer
[22:27] <cholcombe> ok
[22:29] <cholcombe> wallyworld: maybe a zfs provider :)
[22:29] <cholcombe> that would be sweet for local
[22:29] <wallyworld> yeah, it would be
[22:30] <wallyworld> LXD is getting new storage APIs this cycle - juju was going to support those but we've had a team restructure and may need to drop that work
[22:30] <cholcombe> ah interesting.  i'll talk to rockstar about it and see what he knows
[22:31] <wallyworld> so it is recognised we have work to do, but not the people to do it as the next priority at the moment
[23:14] <axw> cholcombe: there's no command to remove pools, and the config attribute we use to have for loop devs no longer exists in juju 2
[23:14] <axw> cholcombe: you would have to make the necessary changes to the lxd profile by hand
[23:14] <cholcombe> axw: i see
[23:14] <cholcombe> can i set it globally for lxd?
[23:15] <axw> cholcombe: you can set it in the default profile
[23:15] <axw> cholcombe: juju also creates profiles for each model, so you can set it on a per-model basis
[23:15] <cholcombe> axw: cool.  if that was in the docs that'd be super helpful :D
[23:15] <cholcombe> i wouldn't have to bug ya
[23:16] <axw> cholcombe: I'll find out exactly what profile changes are required and update the docs issue
[23:16] <cholcombe> axw: awesome!  I'm looking forward to test driving this
[23:43] <axw> cholcombe: https://github.com/juju/docs/issues/1665
[23:43] <cholcombe> axw: :D
[23:43]  * cholcombe high fives axw
[23:43] <axw> cholcombe: btw, LXD is adding a storage API that we'll make use of when we're both ready
[23:43] <cholcombe> cool
[23:43] <axw> cholcombe: so you'll be able to add volumes into a container programmatically
[23:43] <cholcombe> sounds good to me !
[23:53] <andrew-ii> Is it recommended to deploy charms one at a time, or is it better to use bundles?
[23:54] <andrew-ii> I've been trying to get a modified openstack bundle to deploy properly, but I'm wondering if it's smarter to build it piece by piece