Changes between Version 10 and Version 11 of CMDI 1.2/Rollout


Ignore:
Timestamp:
06/09/16 07:19:26 (8 years ago)
Author:
Twan Goosen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CMDI 1.2/Rollout

    v10 v11  
    1010=== Preparation ===
    1111Preparation steps can take place a couple of days before the deployment
    12 * [] Prepare [#Componentconversion component conversion], i.e. fix/remove problematic components and profiles
     12* [] ```Twan```: Prepare [#Componentconversion component conversion], i.e. fix/remove problematic components and profiles
     13* [] ```Twan```: Make a deployment package for the VLO
     14* [] ```Twan```: Make a deployment package for the Component Registry
     15* [] ```Twan```: Make a runnable package with ready to use configuration file for the conversion tool
     16* [] ```Menzo```: Make a deployment package for the harvester
    1317
    1418=== VLO and harvester ===
    1519In theory, these steps take place some days before the deployment if the schedule allows for it (it depends on an admin being available)
    16 * [] Validate existing harvest result (with CMDI 1.1) as a reference. Store validation results.
    17 * [] Deploy the OAI harvester with support for CMDI 1.2, configure harvest result to CMDI 1.2
    18 * [] Deploy the VLO version with support for CMDI 1.2
     20* [] ```Menzo```: Validate existing harvest result (with CMDI 1.1) as a reference. Store validation results.
     21* [] ```Willem```: Deploy the OAI harvester with support for CMDI 1.2, configure harvest result to CMDI 1.2
     22* [] ```Willem```: Deploy the VLO version with support for CMDI 1.2
    1923
    2024=== Toolkit ===
    21 * [] Change the default Component Registry location from the alpha server to the production server
    22 * [] Tag/release toolkit on !GitHub, make development branch (master should be stable)
    23 * [] Check if the toolkit is available and up-to-date at [https://infra.clarin.eu/CMDI/1.x]
     25* [] ```Menzo```: Change the default Component Registry location from the alpha server to the production server
     26* [] ```Menzo```: Tag/release toolkit on !GitHub, make development branch (master should be stable)
     27* [] ```Menzo```: Check if the toolkit is available and up-to-date at [https://infra.clarin.eu/CMDI/1.x]
    2428
    2529=== Component Registry ===
    26 * [] Run a 'dry' [#Componentconversion component conversion] on a dump of the Component Registry database to see if there are no new problematic cases
    27 * [] Stop the Component Registry
     30* [] ```Twan```: Run a 'dry' [#Componentconversion component conversion] on a dump of the Component Registry database to see if there are no new problematic cases
     31* [] ```Willem```: Stop the Component Registry
    2832* [#Componentconversion Convert] of all component and profile definitions within the Component Registry with the component upgrade tool:
    29  * [] Backup the Component Registry database
    30  * [] Run the upgrade tool (see below for details) and make sure that it terminates without any errors
     33 * [] ```Willem```: Backup the Component Registry database
     34 * [] ```Willem```: Run the upgrade tool (see below for details) and make sure that it terminates without any errors
    3135  * in case of errors, most likely one or more components need to be fixed
    32  * [] Make a backup of the freshly converted database
    33 * [] Deploy and start the Component Registry version with support for CMDI 1.2
     36 * [] ```Willem```: Make a backup of the freshly converted database
     37* [] ```Willem```: Deploy and start the Component Registry version with support for CMDI 1.2
    3438
    3539=== Testing ===
    36 * [] Validate existing harvest result (with CMDI 1.1) to see that CMDI 1.1 records still validate (the same way). Compare to pre-deployment validation results.
    37 * [] Run a harvest with conversion to CMDI 1.2
    38 * [] Validate harvest results (CMDI 1.1 and CMDI 1.2)
    39 
     40* [] ```Menzo```: Validate existing harvest result (with CMDI 1.1) to see that CMDI 1.1 records still validate (the same way). Compare to pre-deployment validation results.
     41* [] ```Willem```: Run a harvest with conversion to CMDI 1.2
     42* [] ```Menzo```: Validate harvest results (CMDI 1.1 and CMDI 1.2)
    4043
    4144== Component conversion ==