Differences between revisions 2 and 3

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. Possibly also backup of system configuration from this task?
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

What other tasks does this task rely on? Which other tasks have parts that we need before performing this task?

Backup depends on Fedora 3.2 setup
Bitstorage agreement depends to some degree on Bitstorage integration task (if agreements need to be updated)
Install/upgrade packages depend to some degree on all tasks generating code.
Install upgrade documentation depends on the documentation tasks
Surveillance requires input from tasks that generate stuff that needs to be under surveillance, at least Fedora 3.2 setup, probably API
Port-definitions et al requires all code to conform.
Benchmarking requires Fedora 3.2 setup, and if other code needs to be benchmarked, that code as well, e.g. bitstorage.

-  ⇤ ← Revision 2 as of 2009-06-03 09:37:28 → 
  Size: 2719
  Editor: jrg
  Comment:
+   ← Revision 3 as of 2009-06-03 10:42:31 → ⇥
  Size: 3524
  Editor: jrg
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 14:
- * 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.
+ * 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. Possibly also backup of system configuration from this task?
 Line 39:
+What other tasks does this task rely on? Which other tasks have parts that we need before performing this task?

 * Backup depends on Fedora 3.2 setup
 * Bitstorage agreement depends to some degree on Bitstorage integration task (if agreements need to be updated)
 * Install/upgrade packages depend to some degree on all tasks generating code.
 * Install upgrade documentation depends on the documentation tasks
 * Surveillance requires input from tasks that generate stuff that needs to be under surveillance, at least Fedora 3.2 setup, probably API
 * Port-definitions et al requires all code to conform. :-)
 * Benchmarking requires Fedora 3.2 setup, and if other code needs to be benchmarked, that code as well, e.g. bitstorage.