Simplify collection launch review
This commit is contained in:
+39
-18
@@ -14,7 +14,9 @@ when provisioning begins.
|
||||
|
||||
For example, a collection targeting four Kino and two Der Riese lobbies, with
|
||||
two Kino already registered, creates two Kino and two Der Riese lobbies.
|
||||
The preview shows **Target / Existing or queued / To create** for each map.
|
||||
The preview groups maps by game and shows **Target / Existing or queued /
|
||||
Create** for each map, with **Remove** in exact mode. Existing totals in exact
|
||||
mode include the listed removals, including those already awaiting cleanup.
|
||||
Matching is by game and exact map variant; T6 Town and Farm are distinct even
|
||||
though they share an engine map. Provisioning identities are counted once when
|
||||
they appear in both the server registry and active creation queue.
|
||||
@@ -30,15 +32,24 @@ It fills deficits without changing existing servers' files.
|
||||
1. Choose **Create collection** on **Fleet → Collections** and name the lineup.
|
||||
2. Add maps from Black Ops I or II and set the desired total lobbies for each.
|
||||
3. Choose **Save & preview** (or **Preview fleet changes** on a saved collection).
|
||||
Choose **Fill missing servers** or **Match collection exactly**, then review
|
||||
the server IDs and estimated capacity. Native host ports are assigned later.
|
||||
4. Launches covered by unused keys show **Game key available**. Each game’s
|
||||
available keys are counted once across the full lineup. If more keys are
|
||||
needed, add them under **Administration → Keys**, then refresh the preview.
|
||||
Launch is enabled when every new server has an available game key.
|
||||
5. Choose **Queue N servers** (or confirm removals and choose **Apply** in exact
|
||||
mode) and follow the collection progress page.
|
||||
If every target is already met, choose **Done**; no operation is created.
|
||||
The dialog prepares its preview automatically. Both **Fill missing**
|
||||
and **Match exactly** are visible; selecting a mode rechecks the
|
||||
plan. Review the change summary and the map table grouped by game.
|
||||
4. Check the required key coverage for each game. Available keys count once
|
||||
across the full lineup, and every new server needs a key. If a game is short,
|
||||
open **Administration → Keys** to add keys or wait for assigned keys to be
|
||||
released. Returning to the dialog rechecks the pools and fleet.
|
||||
5. Review the capacity summary. Expand its details for CPU, memory, ports, and
|
||||
startup slots. Capacity estimates are advisory: queued launches can wait for
|
||||
hosts or resources. Native host ports are assigned during provisioning.
|
||||
6. Expand **Server details** to inspect server IDs, launch order, retained servers,
|
||||
and existing-server health. **Advanced settings** holds the runtime override;
|
||||
**Setup details** shows configuration, managed files, and game-file upload
|
||||
information.
|
||||
7. Use **Queue N servers** in the persistent footer, or review and confirm
|
||||
the removal list before choosing **Create N · Remove M** when removals are
|
||||
needed. Follow the collection progress page after submission. If no changes are needed,
|
||||
choose **Done**; no operation is created.
|
||||
|
||||
### Match collection exactly
|
||||
|
||||
@@ -49,9 +60,10 @@ variant. It removes excess lobbies and maps outside the collection. Retained
|
||||
servers keep their containers, files, ports, and configuration without a restart.
|
||||
The option is chosen per launch; opening another preview defaults to fill mode.
|
||||
|
||||
Review the removal list and check its confirmation before applying. Removed
|
||||
servers lose their containers, files, and registrations; their keys return to the
|
||||
game pool only after confirmed removal.
|
||||
The removal list stays visible in exact mode. Review it and check its confirmation
|
||||
before applying. Every refreshed preview clears that confirmation so it must be
|
||||
reviewed again. Removed servers lose their containers, files, and registrations;
|
||||
their keys return to the game pool only after confirmed removal.
|
||||
Unstarted creations are cancelled without booting a container. Running servers
|
||||
use the normal removal queue and require a fresh zero-player RCON response.
|
||||
Occupied or unreachable servers wait. Already pending removals are reused.
|
||||
@@ -94,6 +106,11 @@ when preparing new launches.
|
||||
|
||||
### Preview and submission
|
||||
|
||||
A preview runs automatically when the dialog opens, the mode or launch settings
|
||||
change, the user returns from managing keys, or the current preview expires.
|
||||
Refreshing also resets removal confirmation. The preview lasts 30 minutes;
|
||||
checks and displayed counts describe the fleet when it was prepared.
|
||||
|
||||
A native collection preview reads a shared capacity snapshot, maintained from host
|
||||
heartbeats and fleet changes. It estimates available ports, CPU, memory, and startup
|
||||
slots without running placement for each server. Missing or insufficient capacity
|
||||
@@ -107,11 +124,15 @@ no jobs or key reservations from that submission are committed. Legacy submissio
|
||||
also revalidate their reviewed ports. Refreshing the preview rechecks pool
|
||||
availability and resets removal confirmation.
|
||||
|
||||
Submitting the same preview again returns the same collection, including after
|
||||
a lost response or an application restart. Reusing the collection with a new
|
||||
preview recomputes the shortfall, including servers queued by earlier launches.
|
||||
It does not add another full copy of the lineup. If the shortfall or reviewed
|
||||
identities change before submission, the request is rejected without changes and
|
||||
If a submission response is lost or cannot be confirmed, retry that same
|
||||
submission. The dialog keeps the reviewed preview while the outcome is uncertain
|
||||
instead of automatically replacing it. If the original request committed,
|
||||
submitting the same preview again returns the same collection, including after
|
||||
its original expiry or an application restart, without repeating operations.
|
||||
|
||||
Reusing the collection with a new preview recomputes the shortfall, including
|
||||
servers queued by earlier launches. It does not add another full copy of the
|
||||
lineup. If the shortfall or reviewed identities change before submission, the request is rejected without changes and
|
||||
requires a fresh preview. Previously saved additive previews are checked against
|
||||
the current shortfall too.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user