[00:00] <thumper> hazmat: the juju deployer uses python-jujuclient, yes?
[00:00] <hazmat> ues
[00:00] <thumper> good, so I'm fixing the right thing at least :)
[00:00] <hazmat> thumper: yes
[00:01] <hazmat> thumper: yeah i saw this over email
[00:01] <hazmat> i thought the traceback into tox was wierd..
[00:01] <thumper> me too
[00:02] <hazmat> thumper: the env variable its looking for is used by the unit tests  its trying to parse the jenv file to connect a client to the named test env
[00:03] <hazmat> but its unclear if the test code needs to be updated to the newer location, or just an issue with the tox config on passing that env var
[00:04] <hazmat> thumper: what version of juju is this?
[00:04] <hazmat> with the format change, trunk?
[00:04] <thumper> hazmat: nah, a feature branch right now, but trunk soon
[00:05] <thumper> soon meaning by the end of next week
[00:06] <thumper> hazmat: what happens when tox reads this?  {env:JUJU_TEST_ENV:"test"}
[00:06] <hazmat> thumper: hopefully the above is enough to find next steps, else if you want to me look and the branch is otherwise solid, i can take a look
[00:06] <thumper> as you can see, I did set that env var
[00:06] <hazmat> thumper: i assume tox sets that env var for the test, but its barfing it appears there
[00:06] <thumper> but the error says: unkown environment variable 'JUJU_TEST_ENV:"test"'
[00:07] <thumper> it appears to think everything after env: is the name of the env variable
[00:07] <hazmat> thumper: ask on openstack, much more tox experience floating around there
[00:07]  * thumper grumbles
[00:07] <thumper> ETOOMUCHELSEON
[00:07] <hazmat> thumper: or the tox docs, its not a tool i use
[00:08] <thumper> me neither
[00:08]  * thumper blames tvansteenburgh
[00:08] <thumper> the tox docs don't have anything like this
[00:08] <thumper> they specify hard coded values in all the tox examples
[00:08]  * thumper has already looked
[00:09] <hazmat> thumper: what happens when you remove that config entirely?
[00:09] <hazmat> re the env var
[00:09]  * thumper shrugs, didn't try
[00:09]  * thumper removes the default
[00:10] <hazmat> if that runs, then export the env var, and try invoking tox
[00:10] <thumper> ERROR: tox version is 1.6, required is at least 1.8
[00:10] <hazmat> pip -U install tox
[00:10] <thumper> hence it not knowing about that expression format I bet
[00:10] <hazmat> probably
[00:12]  * thumper hacks stuff...
[00:12] <thumper> Ran 22 tests in 0.143s
[00:12] <thumper> FAILED (errors=13)
[00:12] <thumper> some things to fix I guess
[00:12] <thumper> cheers
[00:12]  * thumper adds to the list of shit to fix
[00:15] <thumper> hmm...
[00:15] <thumper> fixed that bit
[00:15] <thumper> now it is just failing tests...
[00:15] <thumper> for different reasons
[00:25] <hazmat> thumper: got a pastebin?
[00:25] <thumper> for?
[00:26] <hazmat> thumper: errors in the tests
[00:26] <hazmat> failing test stdout/err
[00:26] <thumper> I now have four failures and three errors
[00:26] <thumper> I need to go through them to work out why they are failing
[00:26] <hazmat> thumper: k
[00:26] <thumper> some are due to different bits in juju
[00:26] <thumper> some seems to be just weird
[00:27] <hazmat> thumper: good luck, ping me if you want a second pair of eyes
[00:27] <thumper> ack
[00:27] <thumper> thanks
[00:32] <hazmat> Destreyf_: you should have a look at the source to my version to see how to configure lxc for flannel, you basically drop a config into /etc/default/lxc-net and /etc/lxc/default.conf
[00:32] <hazmat>  after reading the values from flannel's on disk state file
[07:13] <lukasa> jamespage: You about?
[11:57] <Odd_Bloke> Anyone around to help me debug a Nagios servicegroups problem?
[13:15] <Dong> hello all? need some light to understand what is the bootstrapper
[13:15] <Dong> and when I do manual targeting cloudstack, do I need to have one VM up and running and config it to be the bootstrap
[13:42] <Syed_A> Hello folks, I was wondering how the lxc template "juju-trusty-lxc-template" is generated ?
[13:43] <Syed_A> I want to change the "juju-trusty-lxc-template" before it is transferred to the target host for the lxc container. Is it possible to do it ?
[13:45] <tvansteenburgh> Syed_A: you could manually modify that template
[13:46] <Syed_A> tvansteenburgh: Before it get transferred to the target host ?
[13:47] <tvansteenburgh> Syed_A: while not bootstrapped, start and attach to it, make your changes, exit, then bootstrap
[15:49] <hazmat> Syed_A: its not transferred its built on the individual hosts
[15:49] <hazmat> Syed_A: specifically its using the lxc ubuntu-cloud template
[15:50] <hazmat> which is a script to create the actual lxc instance which is used as a template for other containers
[15:52] <Syed_A> hazmat: oh!, intersting. Do you know how can i manually create it ?
[15:53] <hazmat> Syed_A: log into to the host.. lxc create -t ubuntu-cloud -n juju-trusty-lxc-template    and pass additional options to the ubuntu-cloud template per taste... perhaps a better question is starting with why?
[15:56] <Syed_A> hazmat: I want all the containers to have 3 nics which gets ip from 3 bridges. And /etc/hosts file of the containers to have the host entry for juju api node.
[15:57] <Syed_A> hazmat: And i don't want to manually edit on every machine which is hosting containers.
[15:59] <hazmat> Syed_A: hmm.. you could also use manual provider, most of that config for is going to be the conf for each container, you could set it up in the template container. another option is to modify the lxc ubuntu-cloud template, or modify the lxc default template on each host.... nutshell if that's what you want your going to need to modify something on each
[15:59] <hazmat> host, be it lxc conf or templates, or juju.
[16:00] <Syed_A> hazmat: Allow me to explain my setup.
[16:00] <Syed_A> hazmat: I have 4 VM's
[16:01] <Syed_A> hazmat: deploy, alice, bob and charlie
[16:01] <Syed_A> hazmat: On deploy i have the juju gui and juju charms
[16:01] <Syed_A> hazmat: I want to start containers on alice, bob and charlie
[16:02] <Syed_A> hazmat: So i will just use juju deploy sevice-x --to lxc:1(alice)
[16:03] <Syed_A> hazmat: and it will deploy sevice-x in a container on alice.
[16:04] <Syed_A> hazmat: But by default, the container will take the ip address from lxcbr0 bridge. Which i can change by changing the bridge configuration inside /var/lib/lxc/conatiner-x/config
[16:05] <Syed_A> hazmat: I don't want to manually change the configuration on alice. I want to automate it. Such that whenever i add a machine to deploy lxc containers on it; all the containers use 3 bridges specified in the template for the container.
[16:06] <Syed_A> hazmat: So a modified template on alice goes in to /var/lib/lxc and all the new containers use this modified template.
[16:07] <jrwren> Syed_A: can you set your 3 interface network defaults in /etc/lxc/default.conf ?
[16:10] <Syed_A> jrwren: Let me give it a try.
[16:20] <hazmat> jrwren: +1 thats the solution imo
[16:20] <hazmat> alternatively on the juju-trusty-lxc-template
[16:28] <Destreyf_> hazmat: your charm works fantastic, but i learned a harsh reality, setting up a OpenStack cluster HA on 3 nodes won't work because you need floating ip's for the services such as Keystone, Cinder and others.
[16:28] <Destreyf_> the flannel charm
[16:49] <pmatulis> does 'juju generate-config' only work on linux? or windows as well?
[17:06] <Destreyf_> pmatulis: juju is mostly (if not all) python based, so it should work on windows as well
[17:09] <pmatulis> Destreyf_: ok, i'm wondering about the generation of boilerplate file and directory
[17:10] <Destreyf_> I haven't used juju on windows (yet) so i'm not certain on where it places files
[17:25] <lazyPower> Destreyf_: actually juju-core (which includes the client application) is Go based.
[17:26] <lazyPower> pmatulis: the generate-config works on windows as well. its part of our CI tests
[17:39] <pmatulis> lazyPower: thank you
[17:39] <lazyPower> pmatulis: no problem. are you going to be working primarily on windows?
[17:40] <lazyPower> pmatulis: if so, there is a native windows client for juju, and if you find that you *need* that touch of a posix environment we have both vagrant boxes and docker containers with an isolated juju client environment for you to use.
[17:42] <Destreyf_> lazyPower: You guys rock btw.
[17:45] <lazyPower> Destreyf_: well thanks :)
[17:45] <Destreyf_> lazyPower: I used juju a while back and had nothing but trouble, granted i knew it was an emerging concept and its gotten much better since then.
[17:46] <lazyPower> Destreyf_: we've put a lot of focus over the last year on user experience, focus on the charms and making them really useful
[17:46] <lazyPower> now that actions has landed you'll start seeing even better core concepts with charms that are well written. You'll no longer need to ssh into a server - just juju action do :)
[17:46] <Destreyf_> lazyPower: i can tell, its been a great experience so far, sadly doing something as foolish as attemping 3 node HA OpenStack doesn't seem to want to work :P
[17:47] <lazyPower> well, thats a tough cookie to begin with Destreyf_
[17:47] <lazyPower> HA anything can be problematic to model, let alone cramming services on a single machine
[17:47] <Destreyf_> lazyPower: so you can setup charms that don't actually deploy to servers right? kinda like when you setup hacluster to manage say keystone, it just does the local stuff for each instance
[17:47] <lazyPower> and openstack is far from simple
[17:47] <pmatulis> lazyPower: no, i am helping with the juju documentation
[17:47] <lazyPower> pmatulis: oh excellent!
[17:47] <lazyPower> pmatulis: we appreciate you :)
[17:48] <Destreyf_> lazyPower: OpenStack is amazing, in all honesty, but i've never gotten to actually play with a deployment of it before.
[17:48] <pmatulis> lazyPower: right now the generate-config just says that the linux dir/file is created - nothing on windows
[17:49] <lazyPower> pmatulis: it might be worth poking your head in #juju-dev, or reaching out over the list to get the specifics. I know the cloudbase guys listen to the juju list, and they are the resident experts on juju+windows
[17:49] <pmatulis> lazyPower: thanks for the tip
[18:29] <hazmat> Destreyf_: bummer re ostack ha and float
[18:30] <hazmat> Destreyf_: if you need something that can do more manual ip mgmt, there are other options (weave, and maybe socketplane), but not sure if that's going to play nice with ostack unless its plumbed into nova
[18:31] <hazmat> Destreyf_: we've got some folks around here though that probably could point you to a dev setup... typically we run it virtualbox registered into maas, and then a maas env on juju with the ostack charms
[18:33] <hazmat> pmatulis: on windows it goes to the user's HOMEDRIVE + HOMEPATH env var then .juju
[18:34] <pmatulis> hazmat: roger
[18:38] <Destreyf_> hazmat: that might be worth doing, i'm just already using VM's for my tests
[18:42] <pmatulis> hazmat: so the online docs are wrong then. they currently show
[18:42] <pmatulis> %LOCALAPPDATA%/Juju
[18:57] <jrwren> docs folks: https://github.com/juju/docs/pull/475
[18:59] <pmatulis> jrwren: is that the only docs file where outfile.name was used?
[19:01] <Syed_A> Can anyone please tell me how can i generate "juju-trusty-lxc-template" manually ?
[19:01] <jrwren> pmatulis: good question.
[19:02] <jrwren> pmatulis: yes, that is the only docs file where outfile.name was used.
[19:02] <pmatulis> jrwren: ok
[19:03] <Syed_A> jrwren: I can see 3 interfaces inside the containers but  the containers /etc/network/interfaces has congiguration only for eth0. eth1 and eth2 are not configured.
[19:03] <Syed_A> jrwren: *configuration
[19:04] <jrwren> Syed_A: for that you will need to update the -template :(
[19:04] <Syed_A> jrwren: I can set the other two nics by using "lxc.network.ipv4".
[19:05] <Syed_A> jrwren: Yes, i figured that but that's the problem i am trying to solve precisely :(
[19:06] <Syed_A> jrwren: By any chance do you know how can i generate "juju-trusty-lxc-template" manually ?
[19:06] <jrwren> Syed_A: not offhand. hazmat gave you some background on that already. More than I ever knew.
[19:07] <hazmat> Syed_A: lxc-create -t ubuntu-cloud -n juju-trusty-lxc-template
[19:08] <hazmat> Syed_A: to get all the options lxc-create -h and /usr/share/lxc/template/lxc-ubuntu-cloud -h  (last is from memory) there's one more script for common config.. don't have an ubuntu box handy to spot check
[19:09] <jrwren> /usr/share/lxc/hooks/ubuntu-cloud-prep
[19:09] <jrwren> I wrote a blog post on using -t ubuntu-cloud http://jrwren.wrenfam.com/blog/2015/05/26/ubuntu-cloud-image-based-containers-with-lxc/
[19:11] <jrwren> Syed_A: you can steal the cloud-init script to pass with -u by copying it out of /var/lib/cloud/instance/user-data.txt
[19:12] <jrwren> i don't think that varies by juju provider, but I could be wrong.
[19:12] <Syed_A> hazmat: creating it ...
[19:13] <Syed_A> jrwren: Cool, Reading it
[22:16] <therealmarv> Hi. I have a question. I’ve submitted a charm to my personal namespace 5 hours ago on trunk and it is not updated yet on https://jujucharms.com (it still shows the old revision) Did I missed a step beside pushing it to my repo? How long does it take. this ingestion process?