UC-22: Scheduled L2VPN Request with Future Start Time

[lmarinve]

Use Case 22: User Submits a Request with Scheduling and start_time in the Future

Domain: User Requests & Scheduling
Component(s): SDX Controller, Meican

---

Trigger

A user submits a new L2VPN provisioning request and specifies a start_time that is in the future (e.g., for a scheduled event or experiment).

---

Expected Behavior

SDX Controller:

• Validate that the start_time is in the future and follows scheduling format
• Decide between two approaches (to be finalized):
  1. Deferred Provisioning: Wait until the scheduled start_time, then submit breakdowns to OXPO
  2. Pre-reservation: Submit provisioning request immediately and tag it as reserved/idle until activation time
• Ensure provisioning happens as close as possible to the specified start_time
• Avoid scheduling collisions or bandwidth overcommitment during overlapping reservations
• Notify the user of the reservation confirmation and scheduled start

Meican:

• Allow start_time input in the L2VPN request UI
• Reflect status: "Scheduled", "Pending Activation", "Provisioned"
• Update user when service is activated
• Prevent edits once the service enters the "Scheduled" state, unless canceled or modified before provisioning

---

Discussion

• Should SDX Controller queue and manage future provisioning internally or use a scheduling agent/module?
• Need consistent time zone handling and clock synchronization (e.g., NTP)
• Coordination with PCE may be needed to ensure resources are available at start_time

---

Test Coverage

Planned test: test_22_scheduled_l2vpn_future_start.py
This test validates:

• Acceptance of a valid future start_time
• Deferred provisioning behavior and correct handoff to OXPO
• Service status changes in Meican

---

Project Reference

• Project 16 – AtlanticWave-SDX E2E Use Cases

---