The previous usage lead to impossilibity of overriding variables defined
in role, because they were included forcibly in the tasks for
standalone-shared.

By using default Ansible apporach to role vars, they can be overriden on
playbook basis.

/reviewed-on nexedi/slapos.package!48

It is ansible standard and allows to set file mode.

As explained in http://docs.ansible.com/ansible/latest/template_module.html
"Leaving off the leading zero will likely have unexpected results.", so fix it.

  This change was suggested by @luke

  The current tag is broken, so we use master to validate the deployment, until we can release a new version

As frontend can be already available, but still not serving correct content
check that it returns ZMI (Zope Management Interface) before providing it
as working for the user.

As standalone-shared is for ERP5-related mainly, and those do require
old gcc version, install (in hackich way) gcc-4.9 on Debian 9.

Also gcc and g++ (and others) are set to be default as 4.9.

The hackish way is based on https://unix.stackexchange.com/questions/334888/how-install-g-4-9-on-debian-stretch

/reviewed-on nexedi/slapos.package!44

By allowing unittest.longMessage and adding result.content to the
test output on failure it is easier to debug issue with assertion.

As more then one type of ERP5ish software release can be build
with the playbook, make finding ipv4 more reliable.

Also, as there can be only one public IPv4 drop the playbook_name
namespace from the detected value.

As only two software releases shall be present on a box, assume that one
which is NOT apache frontend is the ERP5 one.

We have no control over how the ERP5 SR will be named, so this change
support this case.

As currently Debian 9 key on OBS is not valid, we need to update apt
information with allowing insecure repositories.

Even if repository role uses debian9-aptconf as dependency, it does not
update repository information *after* adding the repository. So just
update it.

/reviewed-on !42

As vars_files has higher precedence than vars_prompt, remove
re6st_registry_url and re6st_fingerprint from settings/vifib.yml.

/reviewed-on !40

Defaults are kept, as in settings/vifib.yml

It is required in order to being able to use vars_prompt in slapos
playbook, while keeping compatiblity with other playbooks.

During upgrade process it is requried to stop for some time requesting
of exsiting software releases and remove them from slapproxy.

The ansible, which will run later, will take care of readding new
software release and crontabs.

As remote repositories are unsure about it quality, rely on shacache and
use it to download and install slapos.node.

This improves quality of playbook and somehow escapes chicken and egg
problem of shacache access and required tools.

This release fixes problem with filling monitor log files with
"AH03490: scoreboard is full, not at MaxRequestWorkers.Increase
ServerLimit."

/reviewed-on nexedi/slapos.package!37

/reviewed-on nexedi/slapos.package!36

Use vifib-kernel to upgrade debian kernel and distro to a recent version

Combining when and register made it impossible to have "portable" way to
find default (public) IPv4 with shell script. This is expected behaviour
of ansible, see https://github.com/ansible/ansible/issues/12779

As Ansbile provides information about a host, use it
(ansible_default_ipv4.address) to fetch this kind of address.

As the process of installing from ERP5 can be controlled with a script,
create such script instead of many steps.

This script is safe to be run many times.

By setting default slapos_ansible_offline to false and using it as
conditional for repository role it is possible to drive, from example
from host variable, if playbook shall restrain itself from running
oneline required roles.

/reviewed-on nexedi/slapos.package!33

This is ERP5 Standalone installation (as erp5-standalone script
provides) offline installation.

/reviewed-on nexedi/slapos.package!34

As package provided does not ensure creation of /opt/slapgrid and
/srv/slapgrid add them if not present.