[09:47] <glenn___> spamaps: well this was just in testing phase, but im wondering if the structure is good, with 3 init scripts
[09:50] <glenn___> spamaps: 1 script would be to start a server, wether its mongrel or webrick, the other 2 scripts are there for spawning multiple mongrels
[11:41] <glenn___> spamaps: i made them simpler now: http://paste.ubuntu.com/892038/ http://paste.ubuntu.com/892039/ http://paste.ubuntu.com/892040/
[15:37] <zyga> what is the correct way to start a script once networking is up
[15:38] <zyga> start on startup and started networking ?
[15:39] <SpamapS> zyga: depends on the OS
[15:39] <zyga> SpamapS, oneiric+
[15:40] <SpamapS> zyga: you never need to 'start on startup and xxxx' .. startup is just if you have something that can be started without regard to the current system state (since startup happens *first* before disks are mounted or anything else is running)
[15:40] <zyga> SpamapS, right
[15:40] <SpamapS> zyga: for Ubuntu 11.10 (oneiric) or later, runlevel 2 is always "after the network is up"
[15:40] <zyga> SpamapS, actually I have a different requirement
[15:40] <zyga> SpamapS, I just explained it incorrectly
[15:40] <zyga> SpamapS, I need "first boot script"
[15:40] <zyga> SpamapS, I start with a pre-made image
[15:41] <zyga> SpamapS, then I need to run a shell script on the first boot
[15:41] <SpamapS> zyga: perhaps look into cloud-init
[15:41] <zyga> SpamapS, I'm starting with a barebone oneiric image
[15:41] <SpamapS> zyga: it has a "nocloud" mode where you just drop a config yaml file on the disk and it reads it.
[15:41] <glenn___> is there anyone else who could review my upstart scripts for puppet, before i will add them to the issue for the ubuntu package?
[15:41] <zyga> SpamapS, does it have any upstart files I could reference?
[15:42] <SpamapS> glenn___: I'm taking a look now. :)
[15:42] <SpamapS> zyga: it has several that it uses to run before and after networking has come up
[15:42] <glenn___> spamaps: awesome :)
[15:42] <SpamapS> zyga: it just keeps track of whether or not it has already run, and exits gracefully if it has
[15:42] <zyga> SpamapS, ok, let me try to find that 
[15:42] <glenn___> zyga: im using upstart scripts on runlevel 2345
[15:43] <glenn___> so when the server is in its right init it would start
[15:44] <SpamapS> glenn___: so, are you hoping to get this into 12.04? And if so, why?
[15:44] <glenn___> spamaps: everyone is telling me it probably wont work
[15:45] <zyga> SpamapS, http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/upstart/cloud-init-nonet.conf this looks like it
[15:45] <glenn___> spamaps: why upstart? :)
[15:45] <glenn___> spamaps: but perhaps we could insert it before beta2
[15:45] <SpamapS> glenn___: right now the package is in sync w/ Debian, and works fine. Why change it?
[15:45] <glenn___> spamaps: why use upstart...
[15:46] <SpamapS> for this particular service, why use upstart.. yes thats what I'm saying.
[15:46] <glenn___> spamaps: since that is the new way of starting daemons in precise
[15:46] <glenn___> spamaps: almost all services we use is in upstart
[15:46] <glenn___> except for apache, varnish, haproxy and such
[15:47] <glenn___> spamaps: all services work without upstart, this is the same as asking why use upstart at all
[15:47] <zyga> glenn___, what new  way if I may ask?
[15:47] <glenn___> zyga: upstart
[15:48] <zyga> glenn___, well that's true for a number of releases, just that most services were not converted
[15:48] <glenn___> hence my point to get all services upstart compatible
[15:48] <SpamapS> glenn___: so.. "because other stuff uses upstart" is not a valid reason, IMO. The main reason I encourage usage of upstart is because it allows the scripts to be simpler, since upstart handles most of the boiler plate stuff.
[15:49] <zyga> SpamapS, I hate the inconsistency between service XXX start and start XXX 
[15:49] <SpamapS> glenn___: the other big reason is because you want other upstart jobs to be able to start before or after it.
[15:49] <SpamapS> zyga: so use service all the time. It works with upstart jobs.
[15:49] <glenn___> spamaps: what exactly is ur point
[15:49] <glenn___> ive been spending a lot of hours so we can implement upstart for the puppet package
[15:49] <SpamapS> glenn___: I do want your upstart job to land in Ubuntu. But we're *way* way way way too late for precise without a compelling reason.
[15:49] <glenn___> spamaps: i gave up on the precise release
[15:49] <glenn___> :)
[15:50] <glenn___> spamaps: but, if, it would be in there, that would be nice though
[15:50] <SpamapS> glenn___: Ok, so I expect mongrel to be gone for 12.10 .. so we can drop to just the one upstart job. :)
[15:50] <glenn___> spamaps: when do we know if mongrel is gone in 12.10?
[15:51] <glenn___> spamaps: also, i think we should default to puppetmaster-passenger as a master
[15:52] <SpamapS> http://bugs.debian.org/663921
[15:52] <SpamapS> glenn___: ^^ .. removal has begun already from Debian. When we sync, it will be gone.
[15:54] <glenn___> spamaps: that would be a nice point to use upstart as well then
[15:54] <glenn___> spamaps: since the init.d scripts have to be changed anyway, including the defaultfiles
[15:55] <SpamapS> glenn___: indeed.
[15:55] <glenn___> spamaps: puppet client upstart script, im using that one already
[15:55] <glenn___> spamaps: the passenger is relying on apache 
[16:03] <glenn___> spamaps: so if we sync this from debian into 12.10 the puppetmaster package needs to be changed right? to remove the mongrel support..
[16:04] <glenn___> but still there would be an upstart script for the puppetmaster, just not with mongrel support, thus only 1 script instead of 3
[16:14] <SpamapS> glenn___: right
[16:38] <glenn___> spamaps: that makes things a lot easyer. i suppose i should focus on that then :)
[16:39] <SpamapS> glenn___: right, and I think at this point.. we're a couple of days from beta2 freeze.. its bugfixes only... what you've done is a fantastic feature. :)
[16:57] <glenn___> spamaps: hopefully the first of many to come :)