Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Required changes to Eldor are linked to moving off of CCMR's AFS. Hence the move from AFS will be being explained here, as a sub-project to the Eldor move project.

Steps and draft timeline

Ensure CIFS (replacement to AFS) is working for

...

Liang. Includes testing permissions, including writes.

Draft start date: Week of   May 27.24

Duration: About a weektwo days.

Make sure everyone has alternative ways to access AFS.

Turn off Eldor

Tentative date: June 3May 29.

Turn on Eldor, connected to CIFS

Tentative date: About a week after Eldor is turned off.

Ensure Eldor is working for Liang. Includes testing ssh, software.

Draft start date: June 6.

Duration: About two days.

Move Liang's data from AFS to CIFS. Ensure CIFS is working for Liang.

Draft start date: June 10.

Duration: About two days.

Move other users' data from AFS to CIFS one by one.

Draft start date: Week of June 10. As CIFS added for user and data moved to CIFS, turn off AFS for that user.

Duration: About one-two weeks. Do quickly to reduce overlap of some folks on AFS and some folks on CIFS.

Turn off AFS (waiting

...

this late allows us to roll-back, if Eldor must be reverted)

Tentative date: Soon after Eldor is functional.

Move all AFS data to CIFS

Tentative date: Same date AFS is turned off.

Duration: If just sync'ing data, maybe about a day.

If having to copy all data over, may take a day or twoDo soon after all accounts have been successfully moved to CIFS and have thus been turned off from AFS.

Status

Must identify all current users of Eldor

...