Changes between Version 11 and Version 12 of OpenFlow/Expedient
- Timestamp:
- 06/01/11 11:14:52 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenFlow/Expedient
v11 v12 25 25 || [wiki:GeniAggregate/WisconsinOpenFlow Wisconsin] || agember@cs.wisc.edu || 26 26 || || || 27 || [wiki:GeniAggregate/I nternet2OpenFlow Internet2]|| geni-openflow@internet2.edu ||27 || [wiki:GeniAggregate/I2OpenFlow Internet2] || geni-openflow@internet2.edu || 28 28 || [wiki:GeniAggregate/NLROpenFlow NLR] || openflow@nlr.net || 29 29 … … 53 53 == Slivers for expired slices == 54 54 55 If you forget to extend the expiration date on your slice, then your Expedient slivers will outlive your slice, and then you can't delete the Expedient slivers because you don't have a slice any more. (Expedient 4.x in theory adds expiration dates; we haven't checked yet whether the expiration date automatically gets set to your slice expiration date if you don't specify.)55 If an experimenter forgets to extend the expiration date on their GENI slice, then their Expedient slivers will outlive their slice, and they won't be able to delete the Expedient slivers, because they don't have a valid slice any more. (Expedient 4.x in theory adds expiration dates, although this seems to be set by hand in the rspec, so the sliver can still outlive the slice.) 56 56 57 An Expedient admin can delete them by hand; there's probably more than one way to do this, but an easy way is to browse to the Expedient AM web UI and delete the user's project from the Projects section of the main ("Dashboard") page. 57 An Expedient admin can delete them by hand; there's probably more than one way to do this, but an easy way is: 58 59 * Browse to the Expedient AM web UI. 60 * Look for the user's sliver (Expedient calls it "slice") in the Projects section of the main ("Dashboard") page, and click on it. 61 * On the ensuing slice detail page, in the "Management Actions" box, click on "Delete" to delete the slice.