added documentation for adding new nodes to monitor
escape character handled for '_'
escape character handled for '_'
escape character handled for '_'
- the use of sudo in monitoring::install_escenic_munin_plugins made it
  fail on all systems not using sudo, such as RedHat/CentOS and
  Debian. Also, the sudo is redundant as ece-install insists on being
  run as root.

- replaced tee with standard redirect, otherwise, the munin stanzas
  are written in between the standard ece-install output
- spell checking
- uppercased some acronyms
- removed /binary as The Adactus access point as we're not using this
  at current projects (we've come up with a better approach to the
  VMEO integration).
- improved Varnish configuration with several features we've
  implemented at recent customer projects:

  -- serving stale content when the backend is down
  -- compressing content (gzip-ing it), this closes #108
  -- automatic robots handling on the beta version of any web
     site. This is to prevent indexing bots like Google Bot to index
     test/beta content
  -- handling re-directs from e.g. www.mysite.com to
     mysite.com. ece-install will set up re-directs TO the
     FQDN you'e got in your fai_publication_domain_mapping_list

- removed support for Varnish 2.x, ece-install now insists on using
  Varnish 3.

- improved feedback message
- added locks. The default behaviour right now will then be that all
  usrs of the program share the same locks. I.e. the 'escenic' users
  cannot call ece-import if cron or root is already using it.
- changed create_lock to NOT make the calling program fail.

- added create_lock_or_fail which does the same as create_lock with
  the difference that it will make your program fail if the lock
  already exists and it will print the error to standard out as well
  as in the log.
- removed the user specific logs as it feels weird.

- removed the debug loop
- moved the definitions of the pid_file and lock_file to the top of
  the script.

- made create_lock write output to standard out as well as the log
  file if the creation fails.
- fix to expand_all_variables_in_org_files to get unicode right.  We
  must read this from the sourced variable and not the declare
  registry to get unicode encoded characters right.
- removed the expand_all_variables_in_org_files_old (this shouldn't
  have been committed in the first place)

- in the new, copied expand_all_variables_in_org_files, the call to
  set_defaults_if_the_trails_are_not_set wasn't present, hence none of
  the defaults have kicked in for quite a while :-(
first attempts to descibe an upgrade process
test
test
more completeness
- added fai_monitoring_node_install which will only install a munin
  node, a nagios node and the escenic check_mk plugins. This closes
  #112

  Note that when you're running a regular ece-install profile, all of
  the above monitoring nodes are installed automatically, hence this
  profile is only for the times where you want to install the
  monitoring clients on servers that are not installed with
  ece-install.
- fixed regression bug:
  ece-install::monitoring::install_munin_gatherer would not include
  the host from which the user doing the installation from is
  connecting from. Hence, you would always get a 403 forbidden when
  accessing the /munin context in the web browser.

  However, normally, you would specify the
  fai_monitoring_privileged_hosts variable (previously called
  fai_privileged_hosts) with the IPs of hosts that should be able to
  access the /munin and /icigina contexts on the monitoring server so
  that *shouldn't be a problem.

  This should close #111

- simplified and hardened code in various monitoring methods.

- renamed fai_privileged_hosts => fai_monitoring_privileged_hosts as
  it's only used in the monitoring module

- moved get_privileged_hosts from ece-install to monitoring as it's
  only used in this module.