UC-17: OXPO Deletes an Existing L2VPN

[lmarinve]

Use Case 17: OXPO Deletes a Previously Provisioned L2VPN

Domain: Error Handling / Resilience
Component(s): SDX Controller, Meican, OXPO

---

Trigger

OXPO sends a topology or service update where an existing, active L2VPN (previously provisioned via SDX) is no longer present — indicating it was deleted either manually or due to failure.

---

Expected Behavior

SDX Controller:

• TODO: Define policy for reconciling unexpected L2VPN deletion
• Detect that the L2VPN is no longer installed at the OXPO (via periodic sync or event message)
• Log the removal event with full context: L2VPN ID, timestamp, domain
• Update the L2VPN status = error and set status_reason = "deleted by OXPO"
• Do not attempt auto-reprovision unless explicitly allowed by policy
• Notify the user/operator via the Notification system that the service was removed externally
• Optionally mark the service as “Needs review” in Meican or queue for administrative decision

Meican:

• Display the L2VPN as error or deleted with a reason if provided
• Disable user actions that would rely on the deleted service
• Optionally allow an operator to restore or re-request the service manually

---

Test Coverage

Planned test: test_23_l2vpn_deleted_by_oxpo.py
This test will simulate an external L2VPN removal at the OXPO level and verify:

• SDX Controller logs and detects the deletion
• L2VPN is flagged as error
• No automatic reprovisioning occurs
• Meican reflects the deletion and disables relevant actions

---

Project Reference

• Project 16 – AtlanticWave-SDX E2E Use Cases

---