[04:28] <hallyn> arosales: hey - question.  https://jujucharms.com/docs/2.1/help-vmware  says vmware hardware version 8 or high is required for juju+vsphere.  But juju uses a hardcoded ubuntu.ovf using 'vmx-10', which is a lot newer (and newer than most of my boxes)
[04:29] <hallyn> arosales: who would know whether the v10 is actually required, or whether that's a bug in the code, and maybe just maybe how to specify a different version (differnt ovf) without re-compiling juju :)
[04:30] <thumper> hallyn: axw probably knows
[04:30] <thumper> hallyn: btw, don't use 2.1, use 2.2
[04:50] <hallyn> thumper: hm actually i'm using 2.0.2
[04:50] <thumper> hallyn: oh for the love of god please upgrade
[04:50] <hallyn> guess i'm on xenial.
[04:50] <hallyn> why isn't the archive uptodate :)
[04:51] <thumper> reasons...
[04:51] <hallyn> ppa:juju/ppa ?
[04:51] <thumper> I think it is ppa:juju/stable
[04:51] <thumper> but let me check
[04:52] <thumper> yeah, the stable one
[04:52] <hallyn> ok thanks, will do that now.  But having looked at github I assume it won't help with my problem :)
[04:52] <thumper> wallyworld: do you know about the vsphere reqs?
[04:58] <arosales> ah, thumper thanks for the reply
[05:21] <wallyworld> arosales: hallyn: IIANM we do only support vmx-10; i think it's to do with API compatibility but not sure
[05:23] <hallyn> :(
[05:23] <hallyn> that makes me very sad
[05:24] <hallyn> wallyworld: in that case, https://jujucharms.com/docs/2.1/help-vmware is a bug iiuc :)
[05:24] <hallyn> but so, this lab i have can't be used this way.  that kinda sucks.
[05:25] <hallyn> wallyworld: who would know for sure ?  (i.e. what features are missing etc)
[05:25] <wallyworld> hallyn: that would be andrew but he's away for another day or so; i'll be asking him when he gets back
[05:26] <wallyworld> i must admit, i thought we did support v8
[05:26] <wallyworld> but it could be recent sdk changes forced us to 10
[05:26] <wallyworld> but i'll need to check
[05:27] <wallyworld> it's certainly in the code that 10 it must be
[05:27] <wallyworld> but the reason i do not know
[05:35] <hallyn> wallyworld: ok, thanks.  Hm, I guess I emailed andrew earlier today, as he was the one who pushed that ovf file
[05:36] <wallyworld> ok, i'll follow up with him when he's back in the office
[05:36] <hallyn> thanks- \o
[05:36] <wallyworld> we do now make user of datastore apis to manage image caching so it may be related to that
[05:37] <wallyworld> i'd hope though we could still support v8
[06:01] <hallyn> Hm, created a 'datacente'r with just the single machine that's new enough.  Error chagned - http://paste.ubuntu.com/25671564/
[06:01] <hallyn> heading to sleep - thanks for the confirmation so far :)
[11:47] <narinder> Hi Leann
[13:45] <ed___> hi there juju people! I'm looking at running canonical kubernetes. Can you recommend how I'd make a clean setup we can store the juju bundle [or whatever the right terms would be] in git, and, we'd like to add a docker image repository to the setup. We're experimentally trying this in MAAS at the moment.
[13:49] <tvansteenburgh> ed___: the bundle is just yaml, so you can store it anywhere
[13:49] <rick_h> ed___: howdy, so the k8s page walks through install steps: https://jujucharms.com/canonical-kubernetes/ and it'll work with maas. As far as storing a bundle in git or the like I don't think you'll need to. Check out http://mitechie.com/blog/2017/9/28/learning-to-speak-juju for 'terminology' introduction.
[14:42] <ed___> thank you tvansteenburgh & rick
[16:28] <tvansteenburgh> ed___: regarding docker registry in your k8s: https://medium.com/@tvansteenburgh/private-docker-registries-and-the-canonical-distribution-of-kubernetes-31cb05a9b61c
[16:57] <skay> the resources doc mentions using a resource per dependency, but I have ~90 python packages I use. should I bundle that many or have 90 resources?
[17:00] <tvansteenburgh> skay: bundle them. i assume this is so you can install offline?
[17:01] <skay> tvansteenburgh: yes
[17:01] <tvansteenburgh> i certainly wouldn't have 90 resources, lol
[17:01] <skay> haha me either. I hadn't noticed that bit in the docs until today
[17:09] <skay> are nested dictionaries okay for yaml configs?
[17:09] <skay> py yaml is okay with them