This version:
 - do not depends on pyscopg2 ( and postgresql )
 - do not have version spec in dependencies ( to prevent version conflicts )
 - serve a sample cube without any setup

grep '----- something' fails because of the '-' character
used for passing options:
grep: unrecognized option '----- something'
so only grep for the string 'something'

on the SlapOS's host, as required to chroot in the build
environment cros_sdk

configuration files

Automate ebuild revision numbers.
Reactivate testing.

The caucase parameter 'auto-sign-csr' used to say if the first csr should be signed
was changed to 'auto-sign-csr-amount' to let specify how many csr can be signed without
human intervention.
This parameter will be set to 2 in erp5 software release, so that caucase http server and
apache server cas request thier certificate automatically.

/reviewed-on nexedi/slapos!203

whenever the zope instances have the same title (example all zope have 'Zope monitor' as title) the request to frontends consider it as the same request and gives same frontend to each of them.

/reviewed-on nexedi/slapos!202

http://mailman.nginx.org/pipermail/nginx-announce/2017/000200.html

See the comments at [this MR](nexedi/slapos!193).

/reviewed-on nexedi/slapos!200

 The principle of deployment on slapos is once the instance is read to use the
 all the promises must work and buildout would stop to run for a while. This
 Promise is been disable because it assumes the user must use the instance first
 them the promise will be green, which can cause endless failure.

 This fail until user do something makes tests and resilience fail, as there is
 no automation to emulate a user take some action.

 This problem MUST be reimplemented on the current way, and not assume user will
 do any action. Others promises can be added into monitor (but not this one like this).

  extra-eggs conflicts with monitor setup.

Added a buildout.hash.cfg for generating automatic md5sums.

/reviewed-on nexedi/slapos!197