[01:14] <asomething> hi all, wondering if anyone around could help make some sense of some debug info from trying to deploy a Django project from bzr using the python-django charm
[01:14] <asomething> http://paste.ubuntu.com/5968323/
[01:15] <asomething> the relation-joined hook fails when running: 'juju add-relation python-django postgresql:db'
[01:17] <sarnold> asomething: just guessing, that -r in the relation-list command is given as the reason for the failing..
[01:17] <sarnold> asomething: .. can you find documentation on the relation-list command that describes what -r is and why it's there?
[01:18] <asomething> sarnold, let's see....
[01:20] <sarnold> hrm, finally found some docs, https://juju.ubuntu.com/docs/authors-charm-anatomy.html
[01:20] <sarnold> ... and its shorter than it could be and doesn't describe command line arguments at all. :/
[01:23] <asomething> hmm... 'juju debug-hooks'  doesn't exist for juju 1.10.0.1
[01:24] <asomething> guess I'll look at the  postgresql charm itself
[01:36] <asomething> so it's something about the id of a related unit...  line 200-206 here: https://github.com/charms/postgresql/blob/master/hooks/charmhelpers/core/hookenv.py
[01:38] <sarnold> nice
[01:39] <sarnold> but the downside is I'm not seing an easy way to remove it and leave the rest of the code alone. ;/ if it is supported in a newer version of juju, that'd be the easier thing to do, I think.
[01:45] <asomething> the same set of commands will get a hello world django project running, I guess I'll just work through the postgresql charm to I see exactly where my Django code is interacting
[01:45] <asomething> i was just hope that someone in here might have seen the same thing before
[01:45] <asomething> thanks for the try sarnold
[01:46] <sarnold> asomething: good luck :)
[01:46] <sarnold> asomething: oh!
[01:46] <sarnold> asomething: maybe you can roll back to a previous version of the postgresql charm?
[01:46] <sarnold> maybe there's an earlier version that would work with your version of juju?
[01:46] <asomething> worth trying
[01:46] <sarnold> maybe not _fun_... but worth trying.
[02:36] <MACscr> So do charms have to be deployed on their own instance or can you choose to install some of them on the same virtual machine or physical server?
[02:37] <mattrae_> MACscr: depends on which juju provider you use. there are juju providers for MAAS for bare metal installs, Openstack and ec2
[02:38] <mattrae_> MACscr: right now if you want to deploy multiple charms to a single machine or vm, you can use jitsu
[02:39] <MACscr> mattrae_: interesting, i wasnt really 100% aware of juju providers
[02:39] <mattrae_> MACscr: in newer juju releases there deploying mulitple charms to a single node will put those charms in lxc containers, so the charms dont' conflict
[02:39] <MACscr> ive only watched a few videos
[02:40] <MACscr> ah, thats cool
[02:40] <MACscr> so is there a management interface for managing these instances after they are deployed?
[02:41] <mattrae_> MACscr: there is juju-gui, which is a charm that you can deploy as well
[02:41] <MACscr> also, is there a limit to what is compatible with what? Aka, i see that juju can deploy openstack and it can also deploy ceph. Can it deploy ceph as the storage backend for openstack?
[02:42] <mattrae_> MACscr: the juju gui is similar to what you see when you go to jujucharms.com
[02:42] <mattrae_> MACscr: it depends on the charms but the openstack charms and ceph charms are reviewed or written by ccanonical to make sure they work together
[02:43] <mattrae_> MACscr: here's an example deployment that includes openstack and ceph https://wiki.ubuntu.com/ServerTeam/OpenStackHA
[02:44] <mattrae_> MACscr: that page is describing a HA deployment, which the charms support. but you don't have to deploy that way
[02:44] <MACscr> LOL, 28 servers for HA? rofl
[02:45] <mattrae_> MACscr: yeah, basically every component has at least 2 nodes
[02:45] <MACscr> right, but not every component needs its own node
[02:45] <mattrae_> MACscr: so right now, i'd suggest putting each charm on its own vm or node
[02:45] <MACscr> a lot of openstack components can go on the controller
[02:46] <MACscr> so should be able to do HA with actually just 6
[02:46] <mattrae_> MACscr: particularly for the openstack charms until there is container separataion. some of the charms can edit the same config files and they can conflict if you use jitsu to deploy to the same node
[02:47] <MACscr> hmm, so is the LXC container thing theoretical or is there a version that currently supports it?
[02:47] <mattrae_> MACscr: yeah you could do it that way, i'd watch out though for the scenario i'm mentioning where different charms may edit the same config file
[02:47] <mattrae_> MACscr: i think its real, let me see if i can find the branch to use
[02:48] <MACscr> I have 10 physical servers right now, plus a management server (low power for just doing deployments/vpn,etc), and then a single storage node, though im adding a second one shortly
[02:49] <mattrae_> MACscr: looks like in juju-core 1.13.0, there is a 'local' provider that does the container stuff
[02:49] <mattrae_> if you add the ppa:juju/devel
[02:49] <mattrae_> you should be able to install juju-core
[02:49] <MACscr> http://content.screencast.com/users/MACscr/folders/Snagit/media/539491bf-c5ed-49e8-88a5-d812f954176e/2013-08-02_04-54-29.png
[02:50] <MACscr> thats pretty much a quick mockup of the idea im having
[02:51] <MACscr> cool, thanks for the idea
[02:52] <mattrae_> MACscr: sure np :)
[02:53] <mattrae_> MACscr: looks like enough machines. you could potentially use a machine as a hypervisor and enlist the vms in maas.. if you need more machines in maas
[02:55] <mattrae_> MACscr: heres how maas can control vms http://askubuntu.com/questions/292061/how-to-configure-maas-to-be-able-to-boot-virtual-machines
[02:56] <MACscr> mattrae_: wow, you are just full of great info. Thanks so much!
[02:56] <mattrae_> MACscr: for sure, np :)
[02:58] <MACscr> i know there much be some huge gotcha thats going to rain on my parade that i havent seen yet =P
[20:24] <juju> hi
[20:42] <marcoceppi|away> jamespage: re simplestream data, you can spin your own imagemetadata to "overrule" whatever the actual data is. While I'm not 100% certain it'll work in all cases, I'm fairly confident you can have your own image-metadata which points to a different image than what simplestreams has