Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Initial Version and Version 1 of Ticket #6372


Ignore:
Timestamp:
08/02/11 13:38:37 (13 years ago)
Author:
szwells
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6372 – Description

    initial v1  
    1 Currently the VM scripts are a single folder of scripts which require a certain amount of setup before they are run, e.g. creating a .VirtualBox/HardDisks/ folder, copy VDI to it, &c. 
     1Currently the VM scripts are a single folder of scripts which require a certain amount of setup before they are run, e.g.  
     2  * creating a .VirtualBox/HardDisks/ folder,  
     3  * copy VDI to it,  
     4  * &c. 
    25 
    3 The scripts should be refactored into a app having the following structure: 
    4  
    5       /bin 
    6       /cache 
    7       /config 
    8       /docs 
    9       /keys 
    10       /logs 
    11       /scripts 
    12       /vdi 
    13       /virtual.appliances 
    14       INSTALL 
    15       README 
     6The scripts should be refactored into a shell application having the following structure: 
     7{{{ 
     8    /bin 
     9    /cache 
     10    /config 
     11    /docs 
     12    /keys 
     13    /logs 
     14    /scripts 
     15    /vdi 
     16    /virtual.appliances 
     17    INSTALL 
     18    README 
     19}}} 
    1620 
    1721INSTALL will: 
     
    2933    * /logs will store logfiles from the VM creation process to allow easy bug-fixing & tracking 
    3034 
    31 The user should be able to specify config files for individual VMs so that a number of deployment scenarios can be targeted, e.g. load balancing OMERO components across individual VMs or to support scripted cluster deployment & management. 
     35The user should be able to specify config files for individual VMs so that a number of deployment scenarios can be targeted, e.g.  
     36  * load balancing OMERO components across individual VMs  
     37  * Provisioning automatically a range of VMs using different codebases, e.g. specify 3 new VMs installed with OMERO 4.3.1, 4.2.2, & trunk respectively. 
     38  * support scripted cluster deployment & management. 

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.12962 sec.)

We're Hiring!