Changes between Version 38 and Version 39 of OpenFlow/FOAM


Ignore:
Timestamp:
01/29/13 14:39:26 (7 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/FOAM

    v38 v39  
    179179If a sliver is automatically approved, FOAM will also send mail when that happens. If the automatic approval fails (e.g. because FlowVisor is down, because the new sliver uses the same controller as an existing sliver, etc), the admin *won't* get mail; https://openflow.stanford.edu/bugs/browse/FOAM-288 is tracking that bug in FOAM.
    180180
    181 If a sliver isn't automatically approved, it'll show up in the pending queue, and have pend_reason set to some text explaining why the sliver wasn't automatically approved.
     181If a sliver isn't automatically approved, it'll show up in the pending queue, and have pend_reason set to some text explaining why the sliver wasn't automatically approved. There's also a nightly cron job that sends a reminder message to the FOAM admin address about the slivers in the pending queue; you should generally either approve them, reject them, or contact the experimenter if you need more information before making a decision.
    182182
    183183Some reasons to reject a sliver that wasn't automatically approved:
     
    185185 * It includes multiple cross-connects.
    186186 * It includes an I2-connected MyPLC plnode (ganel, gardil, sardis) and an NLR cross-connect, or an NLR plnode (bain, navis) and an I2 cross-connect.
    187  * It overlaps with something, and the existing sliver is more legitimate than the new one (e.g. someone's trying to use someone else's subnet).
     187 * It overlaps with something, and the existing sliver is more legitimate than the new one (e.g. the new sliver is trying to use someone else's subnet).
    188188
    189189We generally follow up to the rejection e-mail message from FOAM, copying the experimenter, to explain why we rejected the sliver.