Changes between Version 1 and Version 2 of GeniOmisUseAssumptions
- Timestamp:
- 04/15/09 14:24:17 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniOmisUseAssumptions
v1 v2 1 1 = OMIS Use Case Assumptions = 2 2 3 These are (some of) the assumptions that were made about GENI operations for the [GeniOmisUseIntro OMIS Use cases]. As these assumptions evolve with the design they form a list of requirements for the facility.3 These are (some of) the assumptions that were made about GENI operations for the [GeniOmisUseIntro OMIS Use cases]. As these assumptions evolve with the design they form a list of requirements for the project. 4 4 5 5 * Aggregate Operations monitor their own components in whatever way they choose, so that they notice if the components they are providing go down or behave in some way that Agg Ops themselves have defined as not acceptable. Note that this behavior can be defined without any reference to slices or slivers whatsoever. In this example, the criteria might be that Agg Ops decides no CPU in a cluster should run at higher than 90% utilization, or they notice that some process is spewing packets at a rate that's overloading the isolation filtering.
