Differences between revisions 1 and 2
Revision 1 as of 2008-10-29 05:46:36
Size: 2179
Editor: EldZierau
Comment:
Revision 2 as of 2008-11-25 13:42:53
Size: 2222
Editor: EldZierau
Comment: adding run no in name
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from AssignmentDeploy

Assignment - Rewrite deploy based on settings overwrite

Action(print,Printer friendly version) TableOfContents

References

Reference documents

  • ["Glossary"]

Dependencies

  • All the tasks below need to be done in the order they are specified.
  • all of the tasks is required to be done in the same iteration, although they can be implemented and tested in parallel with other developments.

Terminology

  • ...

Bugs

...

Feature Requests

Documentation

Deployment Manual with reference to existing sections in Installation Manual

  • Preparation
    • make it-config file
    • get netarchivesuite zip file
    • get and adjust configuration files
  • deploy
    • how to
    • what is happening
  • installation
    • how to (including modifications)
    • what is happening
  • start and kill

Settings documentation should only consist in references to xml files in repository.

Questions

  • Should we include creation of directories based om default settings?
  • ...

New definition of IT-config

explation of settings overwrite structure and special deploy configuration settings (levels, install dir etc.)

Rewrite deploy

Reuse deploy code from kb-doms (Royal Library Digital Object Managemnt System code):

  • machine definition class (for different os)
  • hirarchy modules at machine and application level

Use follwing design:

  • check input
  • read minimum default settings that are needed for deploy (e.g. baseDirs)
  • make physical location objects with from global level in it-config overwritten by specific physical location settings
  • for each physical location
    • make machine objects specified for the location correspong to the mashine OS
    • overwrite/add settings for maschine
    • for each machine
      • make application objects specified for the machine
      • overwrite/add settings for application
  • make consistency checks on known listed dependencies (e.g. bitarchives defined as common replicas)
  • use methods on objects in hierarchy to produce various scripts

AssignmentDeploy1 (last edited 2010-08-16 10:25:09 by localhost)