[02:36] <shazzner> hey everyone
[02:36] <shazzner> I've been reading up on juju/ensemble
[02:36] <shazzner> and I'm eager to try it out
[02:37] <shazzner> what's a good way to set something up and practice with?
[02:37] <shazzner> I was thinking Amazon's EC2 free account
[02:38] <shazzner> also is juju only really good for web-facing servers?
[02:38] <shazzner> or can I use it to deploy something like OpenERP?
[03:56] <dosdawg> you could use it for internal servers if you ran openstack or some other ec2 api compatable
[04:15] <shazzner> dosdawg: do you have a tutorial or something about setting up openstack? Thanks!
[05:02] <SpamapS> shazzner: its non-trivial :)
[05:02] <shazzner> then I'll need the most un-trivial tutorial/guide there is! :)
[05:02] <SpamapS> shazzner: you can use the orchestra provider to install machines for specific workloads using juju
[05:05] <SpamapS> shazzner: For OpenStack you need several components.. mysql, rabbitmq, nova (for virtualization and the API), glance (for hosting machine images)..
[05:07] <SpamapS> shazzner: here's a good starting point http://cloud.ubuntu.com/2011/10/ubuntu-cloud-deployment-with-orchestra-and-juju/
[05:08] <shazzner> thanks! sorry I'm a bit distracted watching the #OWS stuff
[05:08] <SpamapS> #OWS ?
[05:10] <shazzner> Occupy Wall Street, twitter hashtag
[05:10] <SpamapS> ah
[05:10] <SpamapS> shazzner: if you just want to "play" with juju you can use the "local" provider which will start LXC containers (like a VM but more lightweight) to stand in for EC2 VMs or real servers.
[05:11] <shazzner> ah ok, thanks
[05:12] <SpamapS> shazzner: as far as OpenERP, yes, you could deploy it with juju
[05:12] <shazzner> is there a charm built for it?
[05:13] <SpamapS> no, but they're pretty easy to write. :)
[05:13] <SpamapS> and I believe at least some of its backend services have charms
[05:14] <SpamapS> looks like it has a web component and a server component, and it uses postgresql..
[05:23] <SpamapS> shazzner: anyway, local provder should be documented at http://j.mp/juju-docs .. heading to sleep, but good luck, and let us know if you have any success w/ an OpenERP charm. :)
[05:24] <shazzner> Ok, thanks again!
[05:24] <shazzner> Get some sleep :)
[05:26] <shang> quick question, I install orchestra, but did not see the management class comes up, did I missing something?
[06:35] <fwereade> shang: you mean you install ubuntu-orchestra-server, and cobbler runs, but the juju-orchestra-* mgmt classes are not created?
[06:37] <fwereade> shang: if so, I don't think I can help, I use orchestra but I'm not familiar with how it's all set up
[06:37] <fwereade> shang: but ping me if you think it's something juju-related
[07:32] <shang> fwereade: ok, thanks!
[10:46] <doitdistributed> hi
[10:46] <doitdistributed> I have a problem installing juju on lucid
[10:47] <doitdistributed> any hints?
[10:47] <doitdistributed>  sudo apt-get install juju
[10:47] <doitdistributed> Reading package lists... Done
[10:47] <doitdistributed> Building dependency tree
[10:47] <doitdistributed> Reading state information... Done
[10:47] <doitdistributed> The following NEW packages will be installed:
[10:47] <doitdistributed>   juju
[10:47] <doitdistributed> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
[10:47] <doitdistributed> Need to get 0B/383kB of archives.
[10:47] <doitdistributed> After this operation, 2,879kB of additional disk space will be used.
[10:47] <doitdistributed> (Reading database ... 170192 files and directories currently installed.)
[10:47] <doitdistributed> Unpacking juju (from .../juju_0.5+bzr409-1juju1~lucid1_all.deb) ...
[10:47] <doitdistributed> dpkg: error processing /var/cache/apt/archives/juju_0.5+bzr409-1juju1~lucid1_all.deb (--unpack):
[10:47] <doitdistributed>  trying to overwrite '/usr/bin/relation-list', which is also in package ensemble 0:0.5+bzr292-0ensemble1~lucid1
[10:47] <doitdistributed> dpkg-deb: subprocess paste killed by signal (Broken pipe)
[10:47] <doitdistributed> Errors were encountered while processing:
[10:47] <doitdistributed>  /var/cache/apt/archives/juju_0.5+bzr409-1juju1~lucid1_all.deb
[10:47] <doitdistributed> E: Sub-process /usr/bin/dpkg returned an error code (1)
[10:50] <drt24> doitdistributed: perhaps this is due to already having ensemble installed?
[10:50] <doitdistributed> hmpf
[10:50] <doitdistributed> :-)
[10:51] <doitdistributed> that was it - stupid me! Thanks a lot!
[12:48] <_mup_> Bug #881991 was filed: Devops page does not exist on juju.ubuntu.com <marketing> <website> <juju:New> < https://launchpad.net/bugs/881991 >
[13:08] <_mup_> txzookeeper/session-and-conn-fail r59 committed by kapil.foss@gmail.com
[13:08] <_mup_> try to make the retry wrapper functions generic, privatize some of the helpers, address some doc string comments
[13:11] <hazmat> g'morning juju folks
[13:17] <rog> niemeyer: hiya
[13:17] <niemeyer> rog: Yo
[13:17] <niemeyer> Greetings from almost-UDS
[13:17] <rog> niemeyer: having fun?
[13:17] <niemeyer> Not yet :)
[13:18] <niemeyer> Just got in the room
[15:55] <dosdawg> whats juju do that chef or puppet won't ??
[16:00] <hazmat> dosdawg, orchestration
[16:00] <hazmat> and reuse
[16:22] <SpamapS> http://askubuntu.com/questions/52840/differentiator-between-juju-and-front-runners-puppet-and-chef/66287#66287
[16:22] <_mup_> Bug #66287: fglrx freeze machine <linux-restricted-modules-2.6.17 (Ubuntu):New> < https://launchpad.net/bugs/66287 >
[16:23] <hazmat> dosdawg, ^ answer from a puppet founder at the askubuntu link
[16:26] <rog> some config files have a "juju: environments" line at the start. does this have any significance?
[16:26] <rog> s/config/environments.yaml/
[16:27] <rog> i've noticed that in at least one place in the testing code it still says "ensemble: environments" so i'm guessing it doesn't signify too much :-)
[16:28] <rog> any particular reason it's there at all?
[16:35] <dosdawg> interesting about puppet vs juju
[16:35] <dosdawg> thanks
[16:36] <SpamapS> rog: not required, I think originally it was meant to just signify how to interpret the file, but the filename does that already
[16:37] <rog> SpamapS: ok, thanks. i thought that, but i just thought i'd check before ignoring it entirely. i wonder if parsing it should fail if it's there, in fact. (obviously it would need deprecating first)
[16:40] <SpamapS> deprecation warnings for cruft is a great idea
[16:43] <hazmat> rog, its basically a tag header to ensure its not some random yaml file
[16:44] <rog> hazmat: ok. well, it would be if it was actually required :-)
[16:44] <rog> as it is, it's noise AFAICS
[16:45] <rog> i think it may as well just be a comment.
[16:45] <rog> alternatively we could enforce it.
[16:45] <hazmat> rog, it should be the python impl
[16:45] <hazmat> enforced that is
[16:45] <rog> hazmat: not as far as i can see.
[16:46] <rog> hazmat: as in: many of the tests omit it, or have it wrong (e.g. ensemble: environments). and the parsing code doesn't seem to look for it.
[16:46] <rog> but i may easily have misinterpreted
[16:46] <rog> that's why i'm asking...
[16:47] <hazmat> rog, indeed it is superflous on environments.yaml
[16:47] <hazmat> the charm metadata does have a required header
[16:48] <rog> ah, ok. maybe it should be required in environments too, for consistency
[16:48] <hazmat> hmm.. that doesn't seem to be the case either
[16:48] <hazmat> weird.. i  know there was a header check at some point
[16:49] <rog> hazmat: personally, i think that the structural check is sufficient.
[16:49] <rog> hazmat: but i'm fine with doing a header check too.
[16:50] <hazmat> rog, yeah.. the structural check is more relevant
[18:12] <evan__> Does anyone have experience with installing Hbase using juju charms hadoop-master / slave + Hbase
[19:40] <hazmat> evan_, i don't believe there is an hbase charm yet