Oopsee
Encyclopedia : O : OO : OOP : Oopsee
OOPSEE is an Acronym for "Online to Offline Provisioning Situation in the Enterprise Environment"
Technical Description
An OOPSEE is a situation caused by poorly managed provisioning imports that result in significant system degradation or system overload. These issues can be blamed for a number of support escalations in the large scale IT environments of the corporate world. Often this type of problem can be directly attributed to deploying the wrong DNS settings or Routing Tables during a scheduled daily update. Most often this is a case of user-input error. Due to the significant impact this type of error can cause on the system as a whole, most of these processes have become fully automated in the enterprise environments.Derived Acronym
- OOPSIE - Online to Offline Provisioning Situation in the Internet Environment
- *An OOPSIE is a specifically an issue that can be attributed to issues that can be attributed to issues stemming from Tier One or Tier Two internet providers. While an OOPSEE typically is limited to the corporate environment, an OOPSIE has potential to affect a more widespread userbase, including (but not limited to) single-homed servers/networks, home/end user internet connections, and Tier One Peering.
Example Usage
- "The customer continually made OOPSEEs that left them in escalations for three months."
- "The OOPSIE caused the Level3 and Verio networks to temporarily go offline."
- "Correctly identifying and managing provisioning through automation can help to prevent OOPSEEs in the future."
External links
- [NANOG] - NANOG mailing list entry in regards to a Level3 OOPSIE
- [http://Slashdot.org] - Slashdot Article Identifying an Example of an OOPSIE
From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.