it is no longer possible to use http:/ as curl now expect a hostname to be
given, see curl issue https://github.com/curl/curl/issues/936

Like for af0c5b11

    $ git diff 8-7-stable 8-8-stable --
            files/gitlab-cookbooks/gitlab/templates/default/sv-sidekiq-run.erb

is empty.

Like for 61177775.

I've manually reviewed

    git diff 8-7-stable 8-8-stable -- files/gitlab-config-template/gitlab.rb.template \
                                      files/gitlab-cookbooks/gitlab/attributes/default.rb

on omnibus-gitlab repository.

There are only changes on postgresql and registry options, which are not relevant for us.

Do not use container_registry and registry_* options

This does almost(*) only pure merge. We will slaposify / adjust config
and corresponding md5sum in the following patches.

(*) condition on smtp_authentication was applied by hand on smtp_settings.rb.in

In the case of hellorina SR, the following section generated invalid command:

[proxy]
command-line = {{ python_location }}/bin/python2.7 {{ rina_proxy }} ${server:instance-guid} ${:ipv6} ${:port}
...

This value can be used as a unique identifier within the cloud.
It was already available for the requesting partition ('request' recipe).

/reviewed-on nexedi/slapos!101

/reviewed-by: TrustMe

Add a class SlapConfigParser which overrite ConfigParser.write method to fix parse problem when
configuration like:
[section]
foo += bar

is included in buildout file. softwaretype recipe will generate
buildout file with foo + = bar because ConfigParser doesn't reconize +=
delimiter and read key as "foo +", value as "bar".
Then ConfigParser.write method generate

[section]
foo + = bar
...

This is invalid with buildout version 2

/reviewed-on nexedi/slapos!100

@Tyagov, please review.

Now the test runners use the LD_PRELOAD environment variable to load
the correct libstdc++ built by slapos and restart themselves.

The restart is necessary because LD_PRELOAD is only taken into account
at the time the process is started. Changing this environment variable
in runtime has no effects.

Tests results are available at Nexedi's ERP5 and are 100% ok: https://nexedi.erp5.net/test_result_module/20160927-3FA05624.

/reviewed-on nexedi/slapos!99

Document how to setup replication.
Add support for no-zope ERP5 instance, so it is possible to setup a
replicating, full-featured ERP5 Cluster instance tree without providing
service until it needs to take over its upstream, or to become
otherwise independent.