Skip to content
This repository has been archived by the owner on Feb 24, 2022. It is now read-only.

zOld ASO migration to Oracle

dciangot edited this page May 18, 2017 · 1 revision

ASO/Oracle migration plan

23 Nov

ASO v1.0.7.pre1 deployed on testbed. This is the hybrid version, still based on wmfactory/local couch for processes management, but with isOracle flag it is able run on Oracle. vocms0105 is the new vm that will host in production the aso/oracle instance. DONE

23 Nov - 5 Dec

Test ASO on testbed both with isOracle flag on and off (‘on’ version on vocms030, ‘off’ version on vocms0105) using real tasks. Publication special cases and similar have not been tested completely on previous functional tests DONE: tests ongoing

2 - 5 Dec

ASO v1.0.7 with all eventual fixes discovered during tests. Ready to be deployed on vocms0105 for the Dec release.

9 Dec until new year Gradually switch part of the incoming tasks in production to Oracle and monitor ASO behaviour.

Next year

A wmfactory/localcouch independent version has already been developed (full fts python binding, 3 components multithreaded Submitter, Monitor, Publisher). Functional tests will start soon, after that we can decide what to do with that. Let’s say on crab dev meeting on 5 Dec I will be able to present in detail pros, cons and new features.