Skip to content

design-proposal(ip-address-claims): a platform that bills addresses bills claims - #126

Merged
Timofei Larkin (lllamnyp) merged 1 commit into
mainfrom
design/ip-metering-bills-claims
Nov 11, 2026
Merged

Timofei Larkin (lllamnyp) merged 1 commit into
mainfrom
design/ip-metering-bills-claims

Conversation

@lllamnyp

Copy link
Copy Markdown
Member

Restores a clause to Metering follows the claim in the ip-address-claims proposal. When the paragraph was added in e04d0eb it ended: "a platform that bills addresses bills claims". The prose rewrite in 82cd418 dropped that clause. What remained, "The IPAddress ledger is the unit of accounting", reads as if IPAddress objects were the billable unit, and review of cozystack/address-controller#12 read it that way.

The paragraph now says that a platform bills claims, as storage bills PersistentVolumeClaims, and that the IPAddress ledger is the record behind the bill: claimRef says whose, the conditions say since when.

Before review

  • If this revises a merged design proposal: it adds a decision record under that proposal's decisions/ directory, or says below why none is needed.

No record is needed. This is a wording fix that restores what the paragraph said before the prose rewrite; no decision changed.

DCO

  • Commits are signed off (git commit --signoff).

…ills claims

The prose rewrite in 82cd418 dropped this clause from "Metering follows
the claim", which left the ledger sentence reading as if IPAddress
objects were the billable unit. The clause is restored, and the ledger
is described as the record behind the bill.

Assisted-by: LLM
Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>
@coderabbitai

coderabbitai Bot commented Nov 10, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: a9541083-5755-467f-b392-852262f21037
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@IvanHunters IvanHunters left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This resolves the metering concern I raised on the metrics PR (address-controller#12) at the design level, and it resolves it the right way. Reframing the unit of accounting from the address to the claim, "a platform that bills addresses bills claims, as storage bills PersistentVolumeClaims," matches how the implementation actually accounts: the per-namespace claim gauge is the billable unit, and the address ledger is the record behind it. The PersistentVolumeClaim analogy is apt, and a dual-stack claim is then one billable unit rather than an undercount of two addresses, which was the other half of my concern. The paragraph stays internally consistent (claimRef says whose, the conditions say since when).

@lllamnyp
Timofei Larkin (lllamnyp) merged commit b71ae2f into main Nov 11, 2026
2 checks passed
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.

2 participants