Configuration Management

The configuration of servers deployed on the cloud is a central aspect of cloud management with Tapp. The following elements are related:

  • Services. A service can be regarded as a package of modular codified system administration, which encompasses a set of system administration recipes and of attributes that allow fine-grained configuration. Services are mostly independent of the particular OS installation and cloud provider that you use. Tapp uses Opscode's Chef configuration manager software as a back-end for defining and applying services on cloud servers.

  • Scripts. Shell scripts can be defined and configured to be executed during boot, shutdown and in operational state. These, though OS-dependent as they generally are, allow further customization of cloud server configuration.

  • Templates. A template bundles the operative system to be run by a cloud server and the services and scripts to be applied to it, thus defining a blueprint for cloud server configuration management.

For example, we could create a template for our web server, using the service apache2, which installs and configures all aspects of Apache 2. We could further define a shell script for our template that is executed at boot and starts some supervision daemons on our web server.

Of course, not all system administration can be done by services and scripts, and often it is important to get direct access to the server. Tapp allows you to log into an ssh shell on the server from the web interface with a single click. In that way, you can perform your administrative tasks on the server comfortably through the browser.