checkpoint on splitting jetty from jetty instance so we can have multiples of the latter
seperated jetty and jetty-instance upstart configs
instance role named jetty9_instance now, put port spec back in
jetty_instances mostly done
remove items taken care of by jetty role, suffix the /etc/default/jetty file
remove vhost bindings to ports added in last attempt at hosting more than one component on a machine
fixup reference to base root in defaults files
seems the vars set by a role dependency do not persist when the role requiring runs, need to set jetty_instance_root in the role as well
conversion of everything to use jetty_instance
jetty launch no longer depends on ephemeral raid/mkdir if not in amazon cloud target
Fixes found in testing, variable scoping in role dependencies is crap, so we needed to stop using certain generics like webapp_root to get it all working, new family of variables for each role using jetty_instance, which the meta file maps to the params of the role dependency. Bit ugly, but it works.
convertying jvm_xmx to use new conventions
be smarter about starting C* on non-image setups
fixup some log4j files that had hardcoded paths into /opt/jetty_apps/logs
copy paste fail fixed
export jetty jmx port as configurable for jetty instantiations. initial switch of ports done
remove exhibitor_opts_port in favour of exhibitor_instance_port
remove priam_port in favour of exhibitor_instance_port
unroll priam port changes, cant be done yet
a couple of fixes found while testing all-in-one