Skip to content

Configurable stacks - #58

Draft
zmc wants to merge 2 commits into
stacks-1-block-poolfrom
stacks-2-config
Draft

zmc wants to merge 2 commits into
stacks-1-block-poolfrom
stacks-2-config

Conversation

@zmc

@zmc zmc commented Oct 23, 2026

Copy link
Copy Markdown
Member

Named stacks of services, defined in config.toml, each with its own data directory and [containers] overrides. The existing services become the default teuthology stack, so nothing changes for current users except that state moves to data_dir/teuthology (existing files are not moved). --stack selects a stack, and depends runs other stacks first.

zmc added 2 commits October 23, 2026 13:55
Add a StackResource protocol describing what CephDevStack needs from a
service, and let PodmanResource and Container take data_dir and
containers_config, so a stack can give each service its own on-disk
state and its own view of the [containers] config.

Signed-off-by: Zack Cerza <zack@cerza.org>
Stacks are named sets of services defined in config.toml. The existing
services become the "teuthology" stack, which stays the default.

- Each stack keeps its state in data_dir/<stack> and can override
  [containers] settings for its own services. Existing archives and
  disk images directly under data_dir are not moved.
- --stack picks a stack, and a stack's depends run before it on start.
- Loop allocation accounts for every stack's backing files.
- Loop and block-pool requirements are only checked for stacks that
  deploy testnodes.

Signed-off-by: Zack Cerza <zack@cerza.org>
@zmc
zmc added this pull request to stack #57 October 23, 2026 19:58

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant