Difference between revisions of "Deployment automation"

Revision as of 11:29, 14 January 2016

The problem

Biowikifarm uses a big stack of software: webserver, database, parsoid service, cronjobs, update scripts, custom scripts, plugins from various sources etc. Keeping track of all the pieces is becoming increasingly difficult. The problem manifests itself as:

• Difficulties to install a specific version of Mediawiki for a specific wiki.
• Incompatibilities between versions (e.g. Parsoid with Mediawiki versions).
• Configuration is difficult to maintain, as there is no overview of what is installed and where the corresponding files are.
• Seriously testing stuff before it's deployed is nearly impossible.
• Documenting changes is increasingly work-intensive.
• As configuration is done on the live server, downtime is necessary.

Inadequacy of the current practice

The current practice makes certain assumptions which amount to as many "anti-patterns" (Humble & Farley, 2010, chap. 1):

Manual deployment of wikis

• Extensive documentation is produced, which is supposed to document all the steps necessary for manual installation (this is impossible, as so much is tacit knowledge)
• Manual testing is required
• Upgrades often go wrong, are unpredictable and sometimes have to be reverted or patched
• Upgrades take several hours

No staging environment

• Whenever an upgrade wiki release has to be tested, it's released on the production environment, sometimes breaking the production build.

Manual configuration of the server

• Stepping back from an unsuccessful server configuration is very difficult
• Modifying the production system is dangerous, specially for files not under version control.

Potential solution approaches

Automated and repeatable deployment

Releasing wikis and Parsoid should be fully automated. Deploying a wiki should be as simple as choosing a name for it and running the deployment script.

• Errors would occur only once.
• Deployment should be repeatable.
• Maintaining extensive documentation is no longer necessary, everything should be documented in scripts.
• Scripts are better than documentation, as everything is explicit.
• Deployment should not depend on the expert, all admins should be able to deploy a wiki using the script.
• Manual deployment is boring and time-consuming.
• Testing is easy as the wiki can be deployed to the staging environment.
• Any version of the wiki should be deployable, particularly new ones.

Staging environment

Deploying a new wiki does not strictly speaking require a staging server. Yet upgrades of Mediawiki and Parsoid may require corresponding versions of libraries (e.g. PHP) that might break the production server. A staging server would be practical for detecting problems well in advance.

• As problems would be detected in advance, it should be possible to fix them without additional downtime.
• As we use open source stuff developed elsewhere, on other Linux versions etc., it would be better to test it before running in on our server.
• Integration problems with our network environment should be detectable on time.

Configuration under version control

References

Humble, J. and Farley, D., 2010. Continuous delivery: reliable software releases through build, test, and deployment automation. Pearson Education. http://proquestcombo.safaribooksonline.com.libezproxy.open.ac.uk/book/software-engineering-and-development/software-testing/9780321670250