76 | | * '''OF-OPR-SLCR-OP-003''': The slicer MUST be able to support ''x'' with ''x''>1 concurrent slices of a substrate of ''y'' with ''y''>1 network devices which are passing traffic. |
77 | | * '''OF-OPR-SLCR-OP-004''': The slicer MUST allow for slices to be added and removed without disrupting other slices. |
78 | | * '''OF-OPR-SLCR-OP-005''': The slicer MUST have some logging mechanism for tracking important operational events. |
79 | | * '''OF-OPR-SLCR-OP-006''': The slicer MUST NOT cause operational issues with things like disk usage. |
80 | | * '''OF-OPR-SLCR-OP-006-a''': The slicer MUST NOT log excessive information which is not generally useful during default operations. |
81 | | * '''OF-OPR-SLCR-OP-006-b''': The slicer SHOULD support different log levels or enabling of additional debugging logs, and that SHOULD be possible to change while the software is running. |
82 | | * '''OF-OPR-SLCR-OP-006-c''': The slicer SHOULD continue to log properly in the event that its logs are rotated. |
83 | | * '''OF-OPR-SLCR-OP-007''': The slicer MUST ensure that substrate-generated traffic that doesn't belong to a slice (e.g. LLDP, CDP, etc) does not overwhelm the control plane. This can be satisfied by '''OF-OPR-SLCR-FN-002''' provided that the slicer doesn't install flows administratively that allow for this problem to occur. |
84 | | * '''OF-OPR-SLCR-OP-008''': The slicer SHOULD have a mechanism to prevent packet-ins coming from the switches from overwhelming the control plane when a controller is disconnected from the slicer. This could involve disabling a slice that sends too much control plane traffic, removing flows within a slice that have an output action to the controller port, or something else. The slicer SHOULD NOT indiscriminately disable a slice when the controller disconnects, as a disconnected controller could be part of an experimenter's test case. |
85 | | * '''OF-OPR-SLCR-OP-009''': When a slice is created or deleted the slicer MUST clear out flow tables of switches for the corresponding VLANs of that slice. |
| 76 | * '''OF-OPR-SLCR-OP-003''': The slicer SHOULD provide some information about its own data for GENI operational monitoring (e.g. number of slices, software version, etc). |
| 77 | * '''OF-OPR-SLCR-OP-004''': The slicer MUST be able to support ''x'' with ''x''>1 concurrent slices of a substrate of ''y'' with ''y''>1 network devices which are passing traffic. |
| 78 | * '''OF-OPR-SLCR-OP-005''': The slicer MUST allow for slices to be added and removed without disrupting other slices. |
| 79 | * '''OF-OPR-SLCR-OP-006''': The slicer MUST have some logging mechanism for tracking important operational events. |
| 80 | * '''OF-OPR-SLCR-OP-007''': The slicer MUST NOT cause operational issues with things like disk usage. |
| 81 | * '''OF-OPR-SLCR-OP-007-a''': The slicer MUST NOT log excessive information which is not generally useful during default operations. |
| 82 | * '''OF-OPR-SLCR-OP-007-b''': The slicer SHOULD support different log levels or enabling of additional debugging logs, and that SHOULD be possible to change while the software is running. |
| 83 | * '''OF-OPR-SLCR-OP-007-c''': The slicer SHOULD continue to log properly in the event that its logs are rotated. |
| 84 | * '''OF-OPR-SLCR-OP-008''': The slicer MUST ensure that substrate-generated traffic that doesn't belong to a slice (e.g. LLDP, CDP, etc) does not overwhelm the control plane. This can be satisfied by '''OF-OPR-SLCR-FN-002''' provided that the slicer doesn't install flows administratively that allow for this problem to occur. |
| 85 | * '''OF-OPR-SLCR-OP-009''': The slicer SHOULD have a mechanism to prevent packet-ins coming from the switches from overwhelming the control plane when a controller is disconnected from the slicer. This could involve disabling a slice that sends too much control plane traffic, removing flows within a slice that have an output action to the controller port, or something else. The slicer SHOULD NOT indiscriminately disable a slice when the controller disconnects, as a disconnected controller could be part of an experimenter's test case. |
| 86 | * '''OF-OPR-SLCR-OP-010''': When a slice is created or deleted the slicer MUST clear out flow tables of switches for the corresponding VLANs of that slice. |