NorskManager class
The entrypoint for all Norsk Manager applications
Signature:
export declare class NorskManager
Methods
| Method | Modifiers | Description |
|---|---|---|
Close down the Norsk connection |
||
Worker-facing call: the worker presents its registration token and tells Manager where to dial back. On success Manager raises Online on its provider bus and dials the worker; on Unauthenticated the token is unknown (or has been deregistered). Most consumers won’t call this directly — |
||
Stops a running job |
||
|
Connect to the Norsk Manager |
|
Spawn a new EC2 instance running the worker image, and make it available for picking up jobs |
||
Create a bundle (AutoManager v1). The bundle is passed in raw PB form — auto-manager (or any other consumer) is expected to convert its own typed Bundle to PB before calling. Returns the assigned bundleId so the caller can correlate later events. |
||
Create a new job |
||
Provision a node from the in-process mock provider’s URL pool (NORSK_MOCK_WORKER_URLS). Pops the next URL, raises Online with the supplied nodeId. Test-only — fails with ResourceExhausted if the pool is empty. |
||
Spawn a new OCI instance running the worker image, and make it available for picking up jobs |
||
Delete a bundle (AutoManager v1). |
||
Deletes a job |
||
Remove a cluster slot. If a worker is currently connected on this slot, its gRPC stream is closed and any running jobs are stopped. The token is invalidated. |
||
Provides a stream of the activity that is happening on the server-side. Reacting to these events is essential for the creation of client-side management logic. |
||
Search for jobs by id |
||
Search for jobs by tag/date/etc. See JobSearchSettings |
||
List all registered cluster slots (active + inactive). Includes the tokens — visible to operators so they can re-copy on demand. |
||
Return a list a all the nodes the manager knows about. |
||
Pre-register a cluster slot. Returns a |
||
Activate a dormant (start_mode = "manual") bundle job. Manager removes the dormant tag and re-emits jobUpdated; placement picks the job up via the normal flow. See §10.2 of the AutoManager design. |
||
Start a job on a node |
||
Deactivate a bundle job by re-stamping the dormant tag. v1 caveat: this is the tag-flip half only. Runtime termination of any currently-running workload and empty-node release with linger are tracked as Phase E.5 (pre-go-live). See §10.2.1. |
||
Stop a job running on a node |
||
Forcibly stop a node |
||
Update a bundle (AutoManager v1). Same convention as createBundle — caller passes raw PB. |
||
Update a job |