Soon I will publish my Puppet (http://reductivelabs.com/trac/puppet/wiki/AboutPuppet) code which automates deployment of the Aegir backend on web servers. (I plan to automate front end deployment in the future.)

My puppet code runs install.sh.txt with appropriate commandline arguments. In order to make it work, I needed to add a -y (yes) option to the install script. My patch is attached for your consideration.

CommentFileSizeAuthor
install.sh_.txt.yesmod.patch1.04 KBbwood

Comments

adrian’s picture

adrian commented

There's already some work in this area planned if you want to take a stab at it - #711760: separate backend and frontend install process

we want to replace (most) of install.sh with a drush command that uses drush_prompt and options to configure the back end, and strip the front end installer out of hostmaster entirely so that the backend can spawn it using a simple provision-install site.com.

bwood’s picture

bwood commented

Thanks for pointing me in the right direction. I'll study up on that other ticket. I've got puppet installing platforms, but have a bit of tidying up to do. A lot of what my puppet code does is take care of:

1. Install requirements
2. Configure system requirements, which include:
* create a Aegir user
* configure Apache, [postfix...]

as documented in http://git.aegirproject.org/?p=provision.git;a=blob_plain;f=INSTALL.txt;...

As install.sh.txt moves to a drush command I can easily update my puppet code.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

I'm marking this as fixed, because the install.sh in the dev-services branch now installs the hostmaster system from the commandline (no manual install profile tasks) and can be given all arguments required to complete without any prompts to the shell.

When dev-services merges to master, this will be the way to install Hostmaster going forward.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.