Main Page: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
For over twenty years the configuration of CSE's servers and lab computers has been managed by a home-grown product called <code>conform</code>. <code>conform</code> micromanaged the entire filesystem of each computer and handled the copying in of all configuration files, binaries, scripts, libraries, data files, etc, from a central repository called "the conformary". Very powerful, but also very labour intensive and very limiting. This is the ''Old World''. | For over twenty years the configuration of CSE's servers and lab computers has been managed by a home-grown product called <code>[[conform]]</code>. <code>conform</code> micromanaged the entire filesystem of each computer and handled the copying in of all configuration files, binaries, scripts, libraries, data files, etc, from a central repository called "the conformary". Very powerful, but also very labour intensive and very limiting. This is the ''Old World''. | ||
The ''New World'' grew out a HoS-supported project to move as much CSE infrastructure as possible out of CSE's K17 data centre and into "the cloud", specifically Amazon's AWS. Early on, a decision was made that <code>conform</code> would be left behind and that all new servers and hosts set up in AWS would be managed some other way. This other way ended up being -- after a review of configuration management tools -- a split between <code>cfengine</code> and Debian's <code>apt</code> family of package manager utilities (<code>apt</code>, <code>dpkg</code>, <code>apt-get</code>, <code>apt-file</code>, etc.) In this split, <code>apt</code> handles all Debian package management (mainly installs and updates) and <code>cfengine</code> handles the rest, mostly configuration files. | The ''New World'' grew out a HoS-supported project to move as much CSE infrastructure as possible out of CSE's K17 data centre and into "the cloud", specifically Amazon's AWS. Early on, a decision was made that <code>conform</code> would be left behind and that all new servers and hosts set up in AWS would be managed some other way. This other way ended up being -- after a review of configuration management tools -- a split between <code>[[cfengine]]</code> and Debian's <code>[[apt]]</code> family of package manager utilities (<code>apt</code>, <code>dpkg</code>, <code>apt-get</code>, <code>apt-file</code>, etc.) In this split, <code>apt</code> handles all Debian package management (mainly installs and updates) and <code>cfengine</code> handles the rest, mostly configuration files. | ||
Debian was chosen because CSE's existing teaching platform was heavily based on Debian and the principle of least surprise was applied. | Debian was chosen because CSE's existing teaching platform was heavily based on Debian and the principle of least surprise was applied. | ||
| Line 16: | Line 16: | ||
|Jointly managed by <code>apt</code> which mostly provides default versions of configuration files, and <code>cfengine</code> which installs CSE-specific versions of configuration files | |Jointly managed by <code>apt</code> which mostly provides default versions of configuration files, and <code>cfengine</code> which installs CSE-specific versions of configuration files | ||
|- | |- | ||
|style="white-space: nowrap;"|<code>/usr/local/extrafiles</code><br /><code>/usr/local/extrapackages</code><br /><code>/usr/local/debpkgs_lists</code> | |style="white-space: nowrap;"|<code>/usr/local/[[extrafiles]]</code><br /><code>/usr/local/[[extrapackages]]</code><br /><code>/usr/local/[[debpkgs_lists]]</code> | ||
|<code>cfengine</code> | |<code>cfengine</code> | ||
|- | |- | ||
| Line 28: | Line 28: | ||
|<code>apt</code> | |<code>apt</code> | ||
|} | |} | ||
== The light-touch approach == | |||
== Debian package management (<code>apt</code>) == | |||
== Configuration management (<code>cfengine</code>) == | |||
== Devolving teaching-related software and configuration to CSE's teaching staff == | |||
=== The split between CSG's and teaching's bailiwicks === | |||
---- | ---- | ||
Revision as of 14:48, 10 Haziran 2022
Introduction
For over twenty years the configuration of CSE's servers and lab computers has been managed by a home-grown product called conform. conform micromanaged the entire filesystem of each computer and handled the copying in of all configuration files, binaries, scripts, libraries, data files, etc, from a central repository called "the conformary". Very powerful, but also very labour intensive and very limiting. This is the Old World.
The New World grew out a HoS-supported project to move as much CSE infrastructure as possible out of CSE's K17 data centre and into "the cloud", specifically Amazon's AWS. Early on, a decision was made that conform would be left behind and that all new servers and hosts set up in AWS would be managed some other way. This other way ended up being -- after a review of configuration management tools -- a split between cfengine and Debian's apt family of package manager utilities (apt, dpkg, apt-get, apt-file, etc.) In this split, apt handles all Debian package management (mainly installs and updates) and cfengine handles the rest, mostly configuration files.
Debian was chosen because CSE's existing teaching platform was heavily based on Debian and the principle of least surprise was applied.
A bit more specifically, each New World host's filesystem is handled thusly:
| Path | Handled by |
|---|---|
/etc
|
Jointly managed by apt which mostly provides default versions of configuration files, and cfengine which installs CSE-specific versions of configuration files
|
/usr/local/extrafiles/usr/local/extrapackages/usr/local/debpkgs_lists
|
cfengine
|
/proc/sys/dev
|
The kernel |
/tmp/var
|
Whatever processes are running on the host |
| Everything else | apt
|
The light-touch approach
Debian package management (apt)
Configuration management (cfengine)
The split between CSG's and teaching's bailiwicks
MediaWiki installation leftovers
MediaWiki has been installed.
Consult the User's Guide for information on using the wiki software.