oxidecomputer / oxidecomputer/omicron

Want silo-scoped endpoint for IP pool utilization

Open
#8,459 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

We have a fleet-level IP pool utilization endpoint ip_pool_utilization_view that we use to show utilization in the IP pool list page in the console. We should add a silo-scoped analog that lets non-operators look at utilization for a given IP pool linked to their silo (which they can already list with the misleadingly-named project_ip_pool_list).

Image

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 by reading the existing ip_pool_utilization_view API and the project_ip_pool_list endpoint, including their linked documentation. Trace how the fleet-level utilization request is scoped and determine the corresponding silo-scoped behavior for an IP pool linked to the caller's silo. Done means non-operators can retrieve utilization for an eligible pool through the new endpoint.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.