Actions:
- Install org-glast-runquality-web (version 1.2) library to PROD.
- Install org-glast-datahandling-common (version 1.4) library to PROD.
- Install org-glast-datacat-client (version 2.3) library to PROD.
- Install org-glast-datacat-sp (version 2.2) library to PROD.
-
- Upload org-glast-datacat-sp (version 2.2) stored procedures to PROD.
- Install org-glast-pipeline-server (version 1.3) library to PROD.
- Upload org-glast-pipeline-server (version 1.3) stored procedures to PROD.
- Modify PROD pipeline startup script to use version 1.3
- Apply patches to Database tables, adding new columns with default values to support new features.
- this is non-destructive and does not have to be reverted in the event of a version back-out
- Restart PROD
Approximately 20 minutes total based on length of time it took to add the new table-columns in DEV.
Motivation:
- Support for L1 Data reprocessing
- Support in Pipeline Jython scripts for newest dataset-find routine (with significant improvements in meta-data search capabilities and bugfixes to same)
- Ability to auto-retry failed processes
- New ability to adjust zombie-process reaping delay
- New command line feature enables users to deal with 'zombie' processes when reaper is unable to. (previously this required a developer's direct intervention.)
Rollback Procedure:
Because of the new stored procedures that will be installed the back-out procedure is slightly more involved than usual:
- Shut-down pipeline server
- Return server start-up script to version 1.2.5
- Re-upload Pipeline stored procedures v1.2.5
- Re-upload Data Catalog stored procedures v2.1
- Restart pipeline server
Note that the additional steps are quite simple to perform and only extend the outage for a back-out from ~5 minutes to ~10.
Updates that would not require backing out (with justification):
- Columns added to Process and ProcessInstance tables for auto-retry support need not be removed as it is not used by previous pipeline version and will be ignored.
- PFE (Pipeline Front End) need not be reverted from 2.7 back to 2.6 because additional features supporting process auto-retry will work if columns are not removed, and schema additions are optional and backward-compatible.
Associated Jira:
SSC-135@JIRA
Details
Pipeline 1.3
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
DataCat Client 2.3
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Pipeline Front End 2.7
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|