...
- Requests for essential/recent data should be satisfied from the temporary DHS.
- Requests for historical data should fail with an explanatory message. We encourage users to wait until the system session has ended before re-run those requests after running their requests.
After the system session
...
is over, user work can resume as normal
Timetable of System Session on
| Time (UTC) | Event | Impact | User action |
|---|---|---|---|
| 8:00 | Change configuration of all services using MARS/ECFS to point to the temporary DHS in Bologna. | Check service status | |
| 8:00 - 8:30 | Drain all MARS/ECFS activity in DHS infrastructure in Reading | All active/queued MARS retrieve requests and ECFS get operations on the DHS in Reading will fail. | Please re-run to test behaviour expected during DHS Move. |
| 8:30 - 17:30 | DHS Move dry-run mode | Behaviour as expected during the DHS Move: only data copied to the temporary DHS essential/recent data will be available | If the data you request is not available, wait until the end of the System Session before re-running failed requests. |
| 18:00 | Revert to use DHS infrastructure in Reading: | Short interruption. | Please re-run all failed requests/scripts. |
| 18:00 - | Longer than usual turn-around time should be expected until back-log clears | Check service status |
Log output samples of execution at various stages
...