murmur pool up

Ensures the pool workflow is running for your tenant. If the pool is already running, this is a no-op. If it has stopped or has not been started, this starts it. Once running, the pool workflow continuously maintains warm VMs according to your pool-config limits and per-workspace min_idle settings.

Synopsis

murmur pool up [flags]

Pool commands run from your laptop only. They are not available on agent VMs.

Arguments

Name	Type	Required	Description
`--workspace`	string	no	Workspace name. Overrides the value from `murmur.yaml`.

Output

On success, prints a single confirmation line:

Pool workflow started

This message appears whether the workflow was already running or was newly started.

Examples

Start the pool

murmur pool up

Pool workflow started

Verify the pool is maintaining VMs

Run murmur pool status after starting the pool to confirm warm VMs are being provisioned:

murmur pool up && murmur pool status

Pool workflow started
warm: 2
  warm: murmur-a1b2c3d4 (murmur-a1b2c3d4)
  warm: murmur-e5f6g7h8 (murmur-e5f6g7h8)

Errors

Code	Meaning	What to do
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur auth` or check your `murmur.local.yaml` configuration.
`PERMISSION_DENIED`	Your role does not have `pool-config.edit` permission.	Ask a tenant admin to grant you the required permission.
(exit error)	`pool commands are not supported on VMs`	Run this command from your laptop, not from an agent VM.

Pools — concept overview
pool-config — catalog resource that controls pool capacity limits
murmur pool status — check the current pool state
murmur pool flush — destroy warm VMs so the pool replenishes

Getting Started

Core Concepts

Guides

murmur pool up

Synopsis

Arguments

Output

Examples

Start the pool

Verify the pool is maintaining VMs

Errors

​Synopsis

​Arguments

​Output

​Examples

​Start the pool

​Verify the pool is maintaining VMs

​Errors

​Related

Synopsis

Arguments

Output

Examples

Start the pool

Verify the pool is maintaining VMs

Errors

Related