puppet: Move top-level zulip deployments into "profile" directory.

This moves the puppet configuration closer to the "roles and profiles
method"[1] which is suggested for organizing puppet classes.  Notably,
here it makes clear which classes are meant to be able to stand alone
as deployments.

Shims are left behind at the previous names, for compatibility with
existing `zulip.conf` files when upgrading.

[1] https://puppet.com/docs/pe/2019.8/the_roles_and_profiles_method
This commit is contained in:
Alex Vandiver
2020-10-19 17:49:54 -07:00
committed by Tim Abbott
parent 27cfb14d92
commit c2185a81d6
37 changed files with 638 additions and 602 deletions

View File

@@ -10,8 +10,8 @@ if [ -z "$SERVER" ] || [ -z "$ROLES" ]; then
echo "Installs an empty Ubuntu server in AWS with a Zulip server role."
echo
echo " * server is the local part of the hostname (e.g. postgres0)"
echo " * roles is a list of Puppet rules to be passed to scripts/lib/install"
echo " E.g. 'zulip::base,zulip::postgres_common'"
echo " * roles is a comma-separated list of Puppet rules to be passed to scripts/lib/install"
echo " E.g. 'zulip::profile::postgres_appdb_tuned'"
echo " * branch is used to override the default branch to install from."
echo
echo "Reads configuration from $HOME/.zulip-install-server.conf, which should look like:"