Changes between Version 1 and Version 2 of GeniOmisUseUnplanned


Ignore:
Timestamp:
04/24/08 21:16:20 (16 years ago)
Author:
Mike Patton
Comment:

Overlooked one inter-page reference that still had old format.

Legend:

Unmodified
Added
Removed
Modified
  • GeniOmisUseUnplanned

    v1 v2  
    1010  * Not just those allocated now, but for the expected duration of the outage (and maybe a little beyond :-)?  Can that be done?
    1111 1. The NOC notifies the RP of each slice (if they have asked to be notified) of the outage, with the estimated duration.  The notification indicates the ticket number which is tracking the outage if the RP wishes to watch it or sign up for updates.
    12   * Not discussed in this example, but a possible response, is for a researcher to migrate their experiment (see Use-Case-Outage-Planned for a similar discussion) off the sliver that is out.  In some experiments, this migration may actually be part of the experiment.
     12  * Not discussed in this example, but a possible response, is for a researcher to migrate their experiment (see GeniOmisUsePlanned for a similar discussion) off the sliver that is out.  In some experiments, this migration may actually be part of the experiment.
    1313 1. The NOC monitors for restoral (and bugs the component owner or operator for new time estimates when the old one is exceeded).
    1414  * Notice that based on my operational experience, I said "when" not "if" there...but there's always that exceptional case where they do meet the original restoral estimate. :-)