BOA

From Things and Stuff Wiki
Revision as of 19:12, 8 October 2012 by Milk (talk | contribs) (→‎Upgrade)
Jump to navigation Jump to search


Basics

Barracuda Octopus Aegir.

  • BOA New meta-installer for an easy Barracuda + Octopus + Aegir install and upgrade on the high performance LEMP stack.

Barracuda

Installs a tuned stack for Aegir PaaS use.

Octopus

  • Octopus installs alongside Barracuda, providing an Aegir satellite instance bundled with various distro install profiles and performance modules.
/data/disk/o1/distro/001/ - platforms be here

Setup

Use _FORCE_GIT_MIRROR=github because it is 10x faster than others.

Make sure that all sites have its associated Client, otherwise the site will be listed as available for all Clients/Users you have added.

Upgrade

Do not ever use apt to upgrade the stack. Upgrading got easier with BOA 2. See UPGRADE.txt for full details.

# Download and run BOA Meta Installer.
wget -q -U iCab http://files.aegir.cc/BOA.sh.txt
bash BOA.sh.txt
# To upgrade system and Aegir Master Instance to Stable
barracuda up-stable

# To upgrade system and Aegir Master Instance to HEAD
barracuda up-head
# To upgrade selected Aegir Satellite Instance to Stable
octopus up-stable o1

# To upgrade *all* Aegir Satellite Instances to Stable
octopus up-stable all
# To upgrade selected Aegir Satellite Instance to HEAD
octopus up-head o1

# To upgrade *all* Aegir Satellite Instances to HEAD
octopus up-head all

Will honour settings in;

/root/.barracuda.cnf
/root/.o1.octopus.cnf
/root/.o2.octopus.cnf

Will fuck up any changes to CSF config, i.e., port access.

Stack

Caching

  • Redis is an open source, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.

New system uses only Redis cache and the same configuration for all Drupal 6 and Drupal 7 platforms. This new system doesn't require any extra module to be enabled in any site. Complete integration is already enabled by default for every platform/site installed by default and for every custom platform as before - the next day after first site on the custom platform has been created. You can disable this caching layer using the same modules/cache/NO.txt control file as before. While there is just one cache engine (Redis) used, there is also an automatic, instant failover to standard database caching, just in case Redis is not available for some reason. You can also disable Redis cache on the fly for debugging by adding ?noredis=1 to any URL.

Development

Alias a dev.* site domain to bypass JS compression and CSS aggregation.