/!\ '''Deprecated''' See [[Tasks/2]] -------------------- ##Task ## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting ## as they may become relevant later on. = Maintenance Agreement = ## Valid states: "Not started", "In progress" and "Finished" '''State:''' Not started ## The time used is measured in man days and does not include the time spent on any sub-tasks. '''Time used:''' 0 md. == Description == ## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions. ## Any available (technical) details goes into the below documentation pages. The task consists of making agreements with the IT maintenance department, and developing required supporting scripts etc. for the agreement. See the analysis documents for details. == Sub tasks == === 2.1 Agreements with maintenance === * 2.1.1 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? * 2.1.2 Re-iterate bitstorage agreements. * Preparation of the two tasks above is estimated to ½ md. * 2.1.3 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? * 2.1.4 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? * Preparation of the two tasks above is estimated to 3 md. * 2.1.5 Agreement about which aspects should be under surveillance (!BigSister). * Preparation of the above task is estimated to 1½ md. * 2.1.6 Agreement of which ports are allocated for our use. * Preparation of the above task is estimated to 0 md. * 2.1.7 Agreements about hardware, that supports our needs. (Fast harddrive for Fedora, RAM, bandwidth, ...) * Preparation of the above task is estimated to 1 md. * 2.1.8 Meetings and minutes with IT maintenance dept. * Preparation of the above task is estimated to 3 md. * '''Total estimate: 9 md.''' === 2.2 Supporting development === * 2.2.1 Install scripts, (ant) scripts for bundling installers in a package, potentially including install/upgrade documentation (also important for open sourcing). * The task above is estimated to 8md. * 2.2.2 Supporting development to expose relevant details for use by BigSister. (Consider open sourcing!) * The task above is estimated to 4md. This task is liable to grow if not kept in check, so please try to keep inside the estimate. * 2.2.3 Make sure port-definitions are easily configurable in all sources. The same for machine names, directories, databases, and others (also important for open sourcing). * The task above is estimated to 2 md. * 2.2.4 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. * The task above is estimated to 8 md. * '''Total estimate: 22 md.''' * '''Total for this task: 31 md.''' ## . [:TaskX.Y.Z:Add sub task link 1 here] ## . [:TaskX.Y.Z:Add sub task link 2 here] ## . ... ## . [:TaskX.Y.Z:Add sub task link N here] == Documentation == ## The documentation section links to the documentation relevant to this task and its sub-tasks (if any). ## ## The below links will automatically be expanded to page names like "MyTaskPageNameAnalysisDocument" in your created page. ## This should be a proper default. ## ## DO NOT comment out these links. * [[2009Tasks/MaintenanceAgreementAnalysisDocument|Analysis Document]] * [[2009Tasks/MaintenanceAgreementDesignDocument|Design Document]] * [[2009Tasks/MaintenanceAgreementSystemMaintenanceDocument|System Set-up and Maintenance Document]] ## == Parent task == ## * ["TaskX"] == Progress history == <> ## Add information about about the current state of the task here. That is, information about what has been completed so far and ## what outstanding issues are left. Example: ## ##=== 2007-09-13 === ##Finished the design documentation. A review is needed before this task is completed. ## ##=== 2007-08-25 === ##Completed requirement specification. We are now ready for writing the design document.