Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove a Switch in the network as part of a Maintenance (i.e. Switch decommission) #17

Open
italovalcy opened this issue Aug 14, 2020 · 0 comments

Comments

@italovalcy
Copy link
Contributor

Description: when the network operator needs to decommission a Switch, the orchestration tool should follow a sequence of steps to make sure no service will be affected

Expected deliverables:

  • Support the procedure described below:

The following procedure should be followed to decommission a link:
a) For each NNI or UNI on the switch, apply the same process as for Decommission a Link
and... ? What if it is an intra-switch service? if it is a intra-switch, you go to step C on the Link decommission (disable the service). The operator should have moved the intra-switch EVCs before (again: how is this integrated with Maintenance napp)

@hdiogenes hdiogenes changed the title (Feature Request) Remove a Switch in the network as part of a Maintenance (i.e. Switch decommission) Remove a Switch in the network as part of a Maintenance (i.e. Switch decommission) Aug 27, 2020
@hdiogenes hdiogenes transferred this issue from kytos/kytos Sep 1, 2020
ajoaoff pushed a commit to ajoaoff/maintenance that referenced this issue Jul 30, 2021
Update requirements to fix conflict error with wrapt and use kytos-ng repo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant