Traffic between buildings now crosses a trunk per pair and raises an incident when a link fills. Customers grow their traffic over their life, and your dashboards can read the whole site.
Added
Between buildings
- A full link between buildings raises an incident. Each direction of each trunk is its own alarm, with guidance and the customers crossing it, and it clears when the link has room again.
- The laptop and the router show the trunks. The Network page lists each pair of buildings with traffic out and in, a router's console shows the trunks it ends, and the wallboard shows the total.
- A rack cabled into another building's switch says so. Its hosts share that building's fault domain. The rack's info panel and the Network page's lamp name the building, and the API carries it.
- Inter-building traffic is in the API. Every pair of buildings reports its trunk both ways over REST and as per-lane Prometheus gauges, and the top bar carries the inter-building total.
- A 200 G carrier line is on the menu. Carrier Wavelength sits between the 100 G peering circuit and the 400 G wavelength, so a campus building climbs 25, 100, 200.
Customer traffic
- Customer traffic grows with the customer. Most tenants send bigger responses as they mature, each toward its own limit and never past it. Media, patch and dataset customers grow most. A blog barely grows.
- Your internet lines set the pace. A tenant only grows into a share of the line capacity your site has lit, so a garage on one line never grows a customer it cannot carry.
- A server with a full network port tells you. When its tenants send more than its links carry, an incident names the box and the fixes: bond ports, fit a faster module, move the tenant.
- Four heavy customers join the roster. A video origin, a backup vault, a dataset hub and a live-events broadcaster arrive near a gigabit and grow into servers with bonded 25 G ports.
Monitoring
- Your dashboards can read the whole site now. Prometheus gains the fabric traffic, the north-south and east-west split, host counts by state, memory and disk, the cable fleet and the internet ceiling.
- Prometheus names what caps your internet speed. A gauge reports whether your lines, your routers or an inline firewall is the limit, and carries all three figures beside it.
Learning the game
- Lessons walk you through the early game. The first takes an empty garage to a working network a step at a time. Ten more cover tenants, the laptop, services and outgrowing the room.
- Lessons about things going wrong arrive when they go wrong. The repair lesson waits for a part to fail, the security lesson for your first attack, the redundancy lesson for an outage.
- Highlights point at the next thing, then stop. The cue that teaches you to sign a tenant does not ring again for the next four, and comes back if you stall.
- Finished lessons stay in Knowledge, and Settings can turn them off. One switch hides the panel and the library, another stops the highlights. Both start on.
Changed
- Traffic between buildings crosses a trunk per pair. Servers in different buildings talk over the trunk between them, load its routers, take its latency and lose requests when it fills. Before, only replication crossed it.
- The campus handoff is 4 x 200 G. Each building now terminates 800 G of lines, up from 400 G. Existing lines and patches carry over at the speed of their router port.
- Traffic grows against the building's own lines. A tenant grew toward a share of every building's lines while its traffic could only leave through its own. Each building now bounds its own tenants.
- Everyone on a full server port shares it. Each tenant on a saturated server loses the same share of its traffic. Before, whichever tenant the game reached last lost all of it.
- Growth waits while a server port is full. A tenant whose server port clips its traffic stops growing until you fix the port, then carries on.
- The opening steps are lessons, not quests. Buying a rack, the gateway and your first server left the quest list, so you read each step once instead of in two places.
- Quests are goals you are working toward. Earning your first $5,000, racking three servers and moving to the basement stay. Anything that was teaching you the controls moved to a lesson.
- The Services page appears with your first tenant. It used to wait for somebody to ask for something that was not a VM, so you could not see or manage the service you already had.
- The quest panel shows five at a time. Finished quests roll off once a third is ticked, so the list stays short. The header still counts every quest you have.
- The Cart button turns orange when it holds something. An empty cart and a cart with three lines in it now read differently at a glance.
- Moving to a bigger site no longer needs a reputation score. Monthly revenue and customer count decide every move. Reputation still counts toward winning and toward which customers approach you.
- Growing customers pay for what they send. The meter counts every byte as before, so a tenant at three times its starting traffic bills three times the transfer.
Fixed
Network
- Console tables sort figures by value. Sorting the switch fabric by Load/Cap ranked a 9 Gbps switch above a 78 Gbps one, since it compared text. Every figure column now sorts by its number.
- The busiest-hosts load reads against the server's real port speed. It read the busiest server as 100% whatever its links, so a box on two bonded 25 G ports looked full at 950 Mbps.
- A tenant's failed requests name a full server port. Traffic that did not fit a server's network port used to vanish from every readout. It now shows as its own cause on the customer's card.
- Cables through a patch panel show their traffic. Hovering a lead on either side of a panel read nothing while the switch it fed showed the traffic. Every port along the run now reads it.
- Each building link on the network map reads its own traffic. Every link showed the site's whole inter-building total and one busy link lit them all. Each now shows its two directions.
- Bonds onto a switch pair work from any device. The console refused two uplinks onto a pair's two members as different devices. The pair now counts as one partner, as for servers.
Ops console
- The Networks page counts the customers your tier rules place. A network with a Gold rule read no customers and flagged every unpinned Gold tenant as a leak. Members and leaks now follow the rule.
- Accepting a prospect says where the default network puts them. The isolation choice read Shared network whatever your tier rules said. It now names the network the matching rule will use.
- A customer's page no longer shows empty before its details arrive. Opening a tenant could briefly show no services and no money while the console was still fetching them. It now waits.
- A server's shop row shows its power draw again. The rebuilt Shop dropped the rack height and power columns from servers alone, so a row ended on its network ports. Both are back.
- A quest reward names the quest. Finishing a quest printed its internal title key in the reward message. It now prints the quest's name.
Workloads
- Workload names are short again. A bucket, cluster, CDN or load-balancer row read its class and a seventeen-digit number. It now reads the class and a plain count, like obj-4207.
- Migrate moves the workload you clicked. On a bucket, cluster, CDN or load-balancer row the move could name a neighbour, so the engine refused it or moved a sibling. It now names the exact one.
- The move-workload picker scales memory and disk. It read a workload's needs as raw megabytes, so a big database showed a seven-digit figure. It now reads in GB or TB like the console.
Notes
- Your saves load. Saves from v0.1.65 and earlier load unchanged, and every customer starts growing from where it is.
- Load once to renumber. A save that lived through an August bug carries some workload ids in the wrong range. Loading once moves them back. Nothing moves, no downtime.
- Client and server must both be on v0.1.66. The network protocol moved, so a v0.1.66 server refuses a v0.1.65 client, and the other way round.
- The trunks endpoint is new. `/api/v1/network/trunks` lists each pair of buildings with a lane each way. Prometheus adds `uptime_trunk_lane_gbps`, `uptime_trunk_lane_drop_probability` and `uptime_trunk_up`.
- A server's real network speed is in the API. `hosts[].effective_nic_gbps` is its bonded ports' combined speed when teamed, otherwise its cable's negotiated speed. 0 until the first update after a load.
- Two fields name the buildings. `racks[].fabric_az_id` is the building whose switch the rack's hosts are wired to, and `inter_zone_gbps` on the top bar is the traffic between buildings.
- The region's backbone figures now total its trunks. `backbone_load_gbps` sums every lane of every pair, `backbone_saturated` is true when any lane is, `backbone_drop_p` is the worst lane, and `backbone_capacity_gbps` is one lane's capacity.
- API: `guidance`'s teaching fields changed shape. `enabled`, `lesson_id`, `title`, `blurb`, `step_index`, `step_count`, `nudge_tier` and `quest_id` are gone. It now reports open teaching arcs: `arcs_enabled`, `hints_enabled`, `arcs`, `focus`, `blocker_condition` and `tier`.
- `guidance.label` still carries a translation key, not English text, the same contract quest text already resolves through, and now names the blocker rather than the step.
- `guidance` says how many are left, and which console tab to open. `blocker_short_by` and `blocker_of` are how many the blocked step still needs and how many it asked for. `console_tab` names the tab to highlight.
- `guidance.console_page` names a laptop page to highlight. It is the nav rail's page id, and empty when the step's work is not on a page.
- `blocker_short_by` and `blocker_of` now report counts for tenants, workloads and repairs. They covered servers alone and reported zero for everything else.
- A new command records a laptop page opening. `NoteOpsPageOpened` carries the page id, matching `NoteConsoleOpened` for devices. It is how lessons about finding an answer complete.
- A new section lists finished teaching arcs. `arc_library` holds every closed arc grouped by concept, for the Knowledge page, and updates only when one closes.
- A new command toggles teaching arcs. `SetArcsEnabled` hides or shows the arc panel and the Knowledge library. It is what the Settings switch sends.
- Nineteen Prometheus gauges are new. They cover fabric traffic, the host fleet by state, memory and disk, the cable fleet, one-time revenue and the WAN ceiling. `/api/v1/metrics/catalog` lists every one.
- The nameplate is not the ceiling. `uptime_uplink_capacity_gbps` is the billed sum. The new `uptime_wan_effective_gbps` is what the site delivers, and it is the one to divide by for utilisation.
- Operating cost excludes hardware. `uptime_cost_total_dollars` now says so in its help text. Buying a server does not move it, because the spend reaches the accounts as depreciation. Revenue minus this figure is not profit.
- Reputation runs 0 to 1. Its help text called it a score, so a dashboard reading `uptime_reputation` as 0 to 100 shows 0.7 where it means 70%.