oxidecomputer / oxidecomputer/omicron

Operator API to configure session idle and absolute timeouts

Open
#5,477 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

customer security
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

Currently these values are hard-coded in the Nexus config to 1 hour and 8 hours, respectively. It would make a lot of sense to allow the operator to set these values dynamically.

https://github.com/oxidecomputer/omicron/blob/e800a0040c28c21aae1b723e7590534e25d3744a/smf/nexus/multi-sled/config-partial.toml#L8-L9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with smf/nexus/multi-sled/config-partial.toml at lines 8–9, where the one-hour and eight-hour values are hard-coded. Trace how Nexus configuration is exposed to operators and identify the relevant API entry point. Done means operators can configure both session idle and absolute timeouts instead of relying on fixed values.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, authentication
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.