Mef Eline behavior for scheduled EVCs

[italovalcy]

Hi,

Facing some challenges when using scheduled EVCs:

• Failover path tries to be set as soon as EVC is created instead of when the schedule is activated
• KytosTagsAreNotAvailable error is raised when trying to use an EVC with same VLAN id even when the schedule is no longer valid

I'm not sure if those behaviors are expected or not. Please advise.

[italovalcy]

For the first problem:

# curl -H 'Content-type: application/json' -X POST http://127.0.0.1:8181/api/kytos/mef_eline/v2/evc/ -d '{"name": "my evc1", "dynamic_backup_path": true, "uni_z": {"tag": {"value": 199, "tag_type": 1}, "interface_id": "00:00:00:00:00:00:00:03:1"}, "uni_a": {"tag": {"value": 199, "tag_type": 1}, "interface_id": "00:00:00:00:00:00:00:01:1"}, "metadata": {"xpto": [1,2,3,4]}, "circuit_scheduler": [{"date": "2024-08-06T23:24:00Z", "action": "create"}, {"date": "2024-08-06T23:26:00Z", "action": "remove"}]}'
{"circuit_id":"73d44dcd4fb34f"}

On the logs:

2024-08-06T23:22:53.320148+00:00 3618532328c4 uvicorn.access:INFO httptools_impl:489:  127.0.0.1:48958 - "POST /api/kytos/mef_eline/v2/evc/ HTTP/1.1" 201
2024-08-06T23:24:21.923656+00:00 3618532328c4 uvicorn.access:INFO httptools_impl:489:  127.0.0.1:48052 - "POST /api/kytos/pathfinder/v3/ HTTP/1.1" 200
2024-08-06T23:24:21.958571+00:00 3618532328c4 kytos.napps.kytos/mef_eline:WARNING evc:973:  Failover path for EVC(73d44dcd4fb34f, my evc1) was not deployed: No available path was found.
...
2024-08-06T23:24:00.478129+00:00 3618532328c4 kytos.napps.kytos/mef_eline:INFO evc:888:  EVC(73d44dcd4fb34f, my evc1) was deployed.
2024-08-06T23:24:00.478735+00:00 3618532328c4 apscheduler.executors.default:INFO base:144:  Job "EVCDeploy.deploy (trigger: date[2024-08-06 23:24:00 UTC], next run at: 2024-08-06 23:24:00 UTC)" executed successfully