The console over HTTP has its own counters, takes no instant, and prints a spanning tree computed at another instant #1336
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1336
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The console driven over HTTP is not the same console as the one in the browser, in three ways. All measured
against
POST /api/topologies/:id/config/:devId.1. One board, two sets of counters
The session is built on
new Simulator(topo)— a second accounting, with its own flow state:Traffic counted by
/flowsis invisible to the console, and traffic the console generates (ping) is invisible to thepayload — one board, two sets of counters, no way for an operator to tell which one they are reading.
2. Every answer is given at
Infinity:configtakes no instant, so the console always answers "once everything has settled". The cable endpoint takesatMsand reports a full convergence schedule, so the API can report a lab mid-convergence and cannot ask the consoleabout it.
3.
show spanning-treeprints whatever was computed lastdev.stpis written by whichever Simulator computed it last, and every HTTP request builds its own. After a cable iscut at 20000, a console asked at 25000 prints:
What must be true instead
publishes;
:configacceptsatMs, applies it on every request (a cached session must not pin a later caller to aninstant it did not ask for), and answers with
runAtMs(null= settled) andconvergence;show spanning-treerecomputes the tree at the attached simulator's instant before reading it.show ip routeprints a cache it never computes: a converged lab reads as empty and an early question reads as settled #1360