Versions Compared

Old Version 27

changes.mady.by.user Brian Van Klaveren

Saved on

compared with

New Version Current

changes.mady.by.user Warren Focke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DateChecklistsEvents
5/5, 11am Readiness meeting
5/5, 4pm
  •  Pipeline shutdown
  •  L1 shutdown
  •  FastCopy shut down
Shutdown of L1, pipeline. Disable pipeline job submission from FASTCopy. Some web applications may stay up.
5/5, 5pm
  •  Ian cleared to proceed
Remaining jobs drained out of batch farm. GLASTTREND in read-only.
5/5, 6pm
  •  GLASTTREND transfer started
GLASTTREND transfer (1a) should be be started by now
5/5, 10pm 

OPTIONAL:

Once at least 600GB has been transferred, we might be able to start conversion of some GLASTTREND files.

Not too likely to impact transfer performance, as it’s not likely to be hitting the same discs.

5/6, 6am
  •  Everything on glast-oracle machines in read-only
  •  GLASTTREND transfer done
  •  GLASTTREND conversion started
  •  GLASTGEN transfer started
  •  GLAST_DP_TEST transfer started

Transfer of GLASTTREND should be completed.

Notification that all applications will be down, including any that may have still been up after 6pm.

Transfer of remaining databases (step 2a) on glast-oracle machines should commence.

5/6, 10am
  •  GLASTTREND more than halfway converted

CONTINGENCY POINT:

Should the transfer (1a), but NOT conversion (1b), of GLASTTREND exceed this time limit, then we shall ABORT step 2 entirely, and proceed ONLY with step 1.

5/6, 2pm
  •  Transfer of any remaining databases started
  •  tnsnames.ora updated

The conversion of GLASTTREND (1b) must be more than half way finished, and the transfer of the remaining files (2a) must be more than halfway finished.

If not, we need to decide on which to proceed with based on how far along they are.

5/6, 3:30pm
  •  Transfer of all databases finished.
    Including: GLASTGEN, GLAST_DP_TEST, GLAST_ASP,
    GLAST_RSP, LAT, GLAST_CAL, etc...

The transfer of remaining files (2a) must be completed.

The conversion of the files (2b) should be started.

5/6, 5pm
  •  Conversion of GLASTTREND completed
  •  GLASTTREND is up
  •  Conversion of GLASTGEN completed
  •  Conversion of GLAST_DP_TEST completed
  •  Conversion of the rest of databases completed
  •  Pipeline Schema migrations started

The conversion GLASTTREND (1a) must be completed.

The conversion of the files (2b) must be completed. GLAST_DP_TEST database must be up, and the schema migrations for the pipeline will be started.

5/6, 7pm
  •  Pipeline Schema migrations finished
  •  Pipeline back up
  •  L1 back up
  •  FastCopy back up
  •  Web Applications restarted

The schema migrations should be finished.

GLASTTREND, GLASTGEN, and other databases should be up.

Applications should be started.

...