Appearance
systemslab context new
| Description | Create a new SystemsLab context. |
|---|---|
| Usage | systemslab context new [OPTIONS] |
Description
The systemslab context new command creates a new empty SystemsLab context.
The new context is created in the open state. It can be modified by attaching and detaching experiments from it. You can also attach newly submitted experiments by passing the context id via the --context flag to systemslab submit.
Once the experiment has completed, you will need to mark the context as complete so that SystemsLab can generate the appropriate reports.
Infrastructure policy
If this deployment runs the AWS infrastructure manager, --max-instances, --pin-hosts, and --no-autoscale set that context's per-context policy at creation time:
--max-instancesserializes a sweep onto a bounded fleet — the planner will not keep more than this many instances active for the context at once. Omit it for unlimited (the server's default).--pin-hostsprefers reusing the exact instances this context has already used, rather than spreading its requests across the fleet — useful for comparing configurations on identical hardware.--no-autoscalestops the planner from growing the context's fleet beyond what it has already acquired. Dead or interrupted instances may still be replaced.
There is currently no systemslab context command to change these on an existing context after creation.
TIP
Creating a new context does not re-run any of the experiments within. If you want to recreate an existing context with a few experiments replaced that can be done like so:
bash
ctx=$(systemslab context new --name 'my new context' --inherit <context-id>)
systemslab context replace $ctx <my bad experiment id> <my new experiment id>
# or, alternatively
systemslab detach $ctx <my bad experiment id>
systemslab submit my-experiment.jsonnet --context $ctxOptions
| Option | Default | Description |
|---|---|---|
--name | The name of the new context. | |
--inherit | An existing context ID to base the new context off of. This will copy the experiments and (optionally) the name from the provided context into the new one. | |
--description | Initial markdown description for the new context. The server sanitizes the submitted markdown before storing it. Conflicts with --description-file. | |
--description-file | Path to a file whose contents become the initial markdown description. Pass - to read from stdin. | |
--max-instances | Cap on the number of instances the infra planner will keep active for this context at once. Omit for unlimited (the server's default). Must be at least 1. | |
--pin-hosts | Prefer to reuse hosts this context has already used, rather than spreading its requests across the fleet. | |
--no-autoscale | Prevent the infra planner from growing the fleet backing this context beyond what it has already acquired. |
Common Options
| Option | Default | Description |
|---|---|---|
--systemslab-url | The URL at which to access the systemslab server. | |
--color | auto | Controls when color is used in the output. Possible values are auto, always, and never. |
--output-format | long | Output format to use when outputting messages. long will result output designed to be human-readable while short is short output meant to be used within scripts. |
Environment Variables
| Variable | Description |
|---|---|
SYSTEMSLAB_URL | Specify the URL used to contact the SystemsLab server. Equivalent to --systemslab-url. |