Analysis of Maintenance Agreement

Agreements with maintenance

• Back-up: Which Fedora directories we would like to be backed up, and how often. We provide maintenance with information on the characteristics of the directories.
• Re-iterate bitstorage agreements.
• Agreement about what should be given to maintenance for them to be able to install. Needed are: An install-package, instructions. Who sets up configuration for production environment?
• Agreement about what should be given to maintenance for them to be able to upgrade. Needed are: An install-package, instructions. Who sets up configuration for production environment?

• Agreement about which aspects should be under surveillance (BigSister).

• Agreement of which ports are allocated for our use.
• Agreements about hardware, that supports our needs. (Fast harddrive for Fedora, RAM, bandwidth, ...)

Supporting development

• Install scripts, (ant) scripts for bundling installers in a package, potentially including install/upgrade documentation (also important for open sourcing).

• Supporting development to expose relevant details for use by BigSister. (Consider open sourcing!)

• Make sure port-definitions are easily configurable in all sources. The same for machine names, directories, databases, and others (also important for open sourcing).
• Potential development of benchmarking code to base our demands for production hardware on (code from Toke). If system is difficult to move onto other hardware, importance of benchmarking rises.

Prerequisites and Assumptions

Resources