=== CyberJacob is now known as CyberJacob|Away === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [01:50] Has anyone asked for a config field in which there are a select few options which users could choose from? Which could be represented in the GUI as a select/dropdown? [01:52] hatch: yea, enums basically [01:52] hatch: it's part of the discussion around using jsonschema to represent config options === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [01:52] ok - atm I am just going to give them the possible options in the description but that just feels ripe for issues [01:52] typos and whatnot [01:55] hatch: yea [01:55] it would be even better if those enum options could enable/disable subsequent config options :) [02:33] when running debug-hooks on a unit the tmux session that opens is in the home directory of the unit not the charm as shown in the docs - where can I find the actual hooks? [02:34] $CHARM_DIR is blank [02:37] ahah I need to actually trigger the hook externally [02:37] looks like we need to update these docs :) === _thumper_ is now known as thumper === scuttlemonkey is now known as scuttle|afk [04:04] hatch: Yeah - it could be clearer that none of the juju env is available until you're in a hook context (ie. config-get and other juju binaries) === erkules_ is now known as erkules [04:17] yeah just a small wording change will help with that - I'll try and remember to submit a PR for that this week === kadams54 is now known as kadams54-away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === psivaa-holiday is now known as psivaa [13:38] Am I missing something or is charmhelpers now broken on trusty since the py3 support mp? [13:41] * gnuoy goes to investigate further [14:14] gnuoy: there's a bug already [14:14] gnuoy: https://bugs.launchpad.net/charm-helpers/+bug/1395378 [14:14] marcoceppi, ah, ok. thanks [14:14] Bug #1395378: latest python3 additions seem to break with trusty python-six [14:15] gnuoy: If you want, check out if lp:~stub/charmhelpers/py3-2 sorts things for you [14:16] stub, thanks [14:18] I can't get the venvs built in a precise VM :-( [14:22] marcoceppi: does juju work against Canonistack? I was told it did, I can bootstrap on it but `juju status` never returns [14:22] mhall119: it does [14:23] lazyPower may have some insight on this [14:23] mhall119: you have do to like proxies and shuttle and stuff [14:23] mhall119: do you have your VPN setup? [14:23] you wont get anything back from juju status util you've activated your VPN or canonistack-sshuttle - i highly recommend the VPN route [14:25] lazyPower: no, I don't [14:32] gnuoy: did that work btw? I'd like to know what series you deployed too. [14:33] stub, I haven't tried as yet tbh [15:09] jamespage, got a sec for https://code.launchpad.net/~gnuoy/charm-helpers/haproxy-singlenode-mode/+merge/242790 ? [15:11] gnuoy, looks reasonable [15:11] is this for the 'run haproxy always' stuff? [15:12] jamespage, it is [15:17] tvansteenburgh: yes, apt-get as an import side effect is disgusting. There are some others hiding in charm-helpers too... [15:20] gnuoy, +1 [15:35] jamespage, thanks [15:36] gnuoy, https://code.launchpad.net/~james-page/charms/trusty/quantum-gateway/stable-vlan-flat-support [15:36] I'd like to get that landed asap [15:37] jamespage, err, I thought I already had. sorry about that [15:37] gnuoy, you acked and I landed next [15:37] thats for stable [15:37] jamespage, +1 [15:38] gnuoy, thanks === scuttle|afk is now known as scuttlemonkey === scuttlemonkey is now known as scuttle|afk === scuttle|afk is now known as scuttlemonkey === kadams54 is now known as kadams54-away [16:42] hey there, i am wondering if i can upgrade from juju 0.7 to the newer juju-core, without having to re-bootstrap the whole environment again? [16:45] sayon: that's a great question [16:47] sayon: as you may be aware a lot has changed in the latest releases of juju, let me find out if there is a migration path [16:47] marcoceppi: i know, right :) [16:47] oh wow 0.7 to 1.20.x? woo thats a huge update. [16:48] lazyPower: yea, i tried to upgrade once juju-gui was introduced but i could not figure out how to do it without rebootstrapping [16:49] sayon: so we've since introduced a "juju upgrade-juju" command but I don't think that will work on an environment that's as old as 0.7 [16:49] sayon, there's isn't anything supported from pyjuju/zookeeper to juju-core/mongodb [16:50] marcoceppi: it won't i already tried, there is no upgrade-juju command :( [16:50] hazmat: i thought so [16:51] sayon, capturing the topology from juju status > and capturing the data in env and then rebootstrapping and restoring by hand .. its a pretty manual process.. juju-core does support in place upgrades. === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away [16:51] i am running in alot of trouble since i upgraded my maas installation on ubuntu 12.04 [16:52] sayon, doh.. [16:52] sayon, was that recently? [16:53] hazmat: it has been some month i guess, everything worked just fine till i wanted to add another machine [16:53] sayon, there was a security fix that got pushed for maas in the last few weeks that broke pyjuju .. pyjuju has been eol'd for a few years. [16:53] hazmat i guess thats what i am facing right now [16:53] sayon, if you want to keep the env, i'd recommending apt-pinning maas to the older version [16:54] the security fix was around the object storage capabilities of maas, and is only relevant if maas was exposed directly to untrusted users which is not common. [16:54] hazmat, tried that already but i am running into problem since the database structure seems to have changed alot [16:55] ugh [16:55] when downgrading it fails to convert from the newer to the older database version [16:56] * hazmat tries to dig up details [17:00] sayon, do you have the error when adding a new machine to the environment? [17:00] ie from log [17:00] it looks like the change was specifically around how charm urls are handed to units [17:01] sayon, also what version of maas is the newer one? [17:01] well when i add a new machine it gets commisioned in maas and is the ready [17:01] but "juju status" won't list the new machine and may not acuire it for charm installations [17:02] hazmat: its maas 1.2+bzr1373+dfsg-0ubuntu1~12.04.5 [17:06] sayon, interesting.. thats a different issue.. the commit i was referencing hasn't landed in 1.2 series yet... do you know what the other version of maas was.. apt-cache policy maas should have it [17:07] hazmat: wow, seems like it was 0.1+bzr482+dfsg-0ubuntu1 [17:11] sayon, hmmm.. so nutshell i'd recommend a bootstrapping that env again using the juju stable ppa on precise https://launchpad.net/~juju/+archive/ubuntu/stable?field.series_filter=precise [17:11] juju-core can self-update itself.. [17:12] i'm asking on #maas re best version/ppa for precise [17:12] hazmat: that means reinstallation of all machines used with juju charms, right? [17:13] sayon, sadly yes [17:14] that version of maas was ancient, and pyjuju has been eol'd for a while [17:15] hazmat: ok, i think i will then do a complete reinstallation with the new LTS version of ubuntu [17:15] and not stick with precise for any longer [17:16] but thanks alot for your help and support hazmat and marcoceppi! [17:18] np === scuttlemonkey is now known as scuttle|afk === scuttle|afk is now known as scuttlemonkey === scuttlemonkey is now known as scuttle|afk === scuttle|afk is now known as scuttlemonkey [19:03] avoine: I'd like to be able to run collectstatic, any objection to the idea of having it happen during install and upgrade? [19:04] avoine: also, there is the ansible branch you have, and I'm wondering if most all of hte python code in hooks.py is going away and it will turn in to a lightweight shim around ansible calls? [19:05] skay: The idea was to use a subordinate for that: http://bazaar.launchpad.net/~patrick-hetu/+junk/django-contrib-staticfiles/files [19:07] skay: also Simon proposed to use dj-static: https://code.launchpad.net/~bloodearnest/charms/precise/python-django/trunk/+merge/235430 [19:07] skay: yes, migrating to Ansible is the long term plan [19:09] for that dj-static branch -- I would leave whether or not someone uses dj-static up to the project [19:09] but the dollectstatic command still needs to be called, and if it should be handled as a subordinate, maybe document it in the readme? [19:10] I happen to be using dj-static right now, and I handle the dependencies in my project's requirements file [19:10] so python-django installs it for me accordingly [19:11] on another note, when find_django_admin_cmd fails to find the admin, would you want sys.exit(1) there? [19:12] I'm not clear on when things should fail silently or not, but that one seems like maybe it shouldn't fail silently [19:14] skay: can you give me the line number? [19:15] skay: Simon's patch would be better since it is not recommended to use django.contrib.staticfiles in production [19:18] avoine: http://bazaar.launchpad.net/~patrick-hetu/charms/precise/python-django/pure-python/view/head:/hooks/hooks.py#L206 === rcj is now known as Guest93149 [19:22] I think I did that to catch the cases where django is not installed [19:22] skay: do you have a case where this should not append? [19:23] avoine: I'll try to dig up what was happening to me. somehow the method was returning None and then the charm was attemping to call None syncdb etc. [19:24] ouch [19:24] avoine: I'm not sure how much you want to dig in to it. I was working on a branch of this to allow for pip extra args and was doing --no-index --file-files and had hte wrong version of something, if memory serves [19:24] avoine: so it didn't install django properly? I thought perhaps that should put the unit in to an error state earlier than it did [19:24] it ended up looking like an error with the pgsql relation rather than earlier [19:25] so, the method allows for the django-admin command not to be found, and doesn't fail. perhaps it should [19:25] skay: no because you could have installed django from a debian package so I'm not checking if it exist earlier [19:26] avoine: oh that makes sense. [19:26] I figured there was a reason [19:26] skay: yeah the pgsql will also fail if django is not installed [19:26] *relation === roadmr is now known as roadmr_afk === rcj is now known as Guest31019 === roadmr_afk is now known as roadmr === scuttlemonkey is now known as scuttle|afk === fuzzy_ is now known as Fuzai === Guest31019 is now known as rcj === rcj is now known as Guest68049