[10:41] <mrskanko> hi
[10:41] <mrskanko> i need a help with juju
[11:50] <mainerror> Hello mrskanko.
[11:51] <mainerror> What is the problem?
[11:53] <mrskanko> i'm using Juju on openstack
[11:54] <mrskanko> i have configured the environment
[11:54] <mrskanko> but when i bootstrapping it
[11:54] <mrskanko> and i do juju status
[11:54] <mrskanko> i received a SSH ERROR
[11:54] <mrskanko> and i can't connect to the machine
[11:55] <mrskanko> but if i run in terminal ssh - i ubuntu@boostraped_machine
[11:55] <mrskanko> it run correctly
[11:58] <mrskanko> have you understood?
[11:58] <mainerror> Oh right, didn't see that yet. Sorry
[11:59] <mainerror> Phew. I have no idea, sorry. I'm sure someone will get back to you as soon as he reads this tough.
[11:59] <mrskanko> don't worry
[12:00] <mrskanko> thank you
[16:33] <mrskanko> What juju.control package contains?
[18:22] <rog> hey
[18:22] <rog> anyone around, by any chance?
[18:28] <rog> i can't quite work out how in the bootstrap process the zookeeper daemon actually gets run.
[18:28] <rog> i can see how the zookeeperd package gets installed, and how the initial zk hierarchy is created, but can't find the actual exec of zookeeperd
[18:29] <rog> it's something in juju/providers/common/cloudinit.py that i'm missing, i'm sure
[18:30] <rog> why i'm doing this on a sunday night, i'm not quite sure :-)
[18:35] <TheMue> rog: hehe, not a good time to get support
[18:35] <TheMue> rog: i'll start to dig deeper next week. right now first reedings in the wiki
[18:38] <rog> TheMue: first reedings?
[18:38] <rog> TheMue: have you started yet?
[18:39] <TheMue> rog: eh, reading
[18:39] <TheMue> rog: no, i'll start on thursday
[18:41] <rog> TheMue: cool! looking forward to working with you.
[18:43] <TheMue> rog: yep, me too. and listening to your music. *smile*
[18:44] <TheMue> rog: i think we'll meet in budapest
[19:06] <rog> TheMue: wonderful.
[19:55] <hazmat> rog, ping
[19:55] <hazmat> rog, the zk instance is started as a consequence of installing the pkg
[19:56] <hazmat> that's fairly common for daemon packages
[20:15] <rog> hazmat: thanks, that's useful
[20:15] <rog> hazmat: i thought the packages were just the equivalent of apt-get packages
[20:16] <rog> which don't run anything... i think. right?
[20:16] <rog> if the packages passed to cloud-init aren't apt-get packages, what are they?
[20:17] <hazmat> rog, they are apt-get packages
[20:17] <hazmat> rog, daemon packages will install upstart files that can start the relevant software
[20:17] <hazmat> rog, ie if you apt-get install nginx or apache, it will actually start the daemon
[20:18] <hazmat> a daemon package is just a semantic distinction i'm making on what software is being installed
[20:19] <rog> hazmat: i never realised that apt-get stuff could actually run the programs you're installing
[20:19] <rog> wow
[20:25] <TheMue> doesn't they just install the scripts in /etc/init.d and set the links in rc0.d to rcS.d?
[20:26] <TheMue> so everything is starting fine with the next boot and additionally the first time directly by apt?
[20:29] <hazmat> TheMue, indeed that's one way.. the newer way is to use upstart
[20:29] <hazmat> which does an inotify listen on the files in its dir and executes new ones
[20:29] <hazmat> it also monitors the the rcX.d dirs
[20:29] <hazmat> TheMue, http://upstart.ubuntu.com/
[20:30] <hazmat> SpamapS, looks like that sites need a new news item re the new releases
[20:31] <hazmat> SpamapS, actualy the downloads there don't correspond at all to the ones in the distro
[20:31] <hazmat> 1.3 vs 0.6.x
[21:03] <TheMue> hazmat: ah, will take a look at it
[21:31] <hazmat> TheMue, welcome aboard ;-)
[21:59] <TheMue> hazmat: thx, i really appreciate it
[23:47] <SpamapS> hazmat: upstream upstart is not like ubuntu upstart
[23:47] <SpamapS> hazmat: though I believe the delta is quite small as of 1.3