File storage is often the last big IT cost that nobody attributes to its consumers. Here is how to move, methodically, from a NAS “paid by everyone” to PowerScale chargeback that finance accepts and departments understand.
Why charge back file storage?
Without cost attribution, storage demand is infinite: every project asks for “a bit more space”, nobody cleans up, and growth is paid for through cluster expansions that IT alone must justify to management. Chargeback changes the dynamic. As soon as a terabyte has an owner and a price, three things happen: requests become rational, stale data gets archived, and the budget conversation shifts from “IT is expensive” to “department X consumes Y to deliver Z”.
You do not need to actually invoice to get this effect — showback (presenting costs without billing them) is often enough. Either way, you must measure correctly.
What OneFS measures — and what it does not
OneFS, the operating system of PowerScale clusters, keeps detailed accounts: capacity consumed per directory, quotas per user or group, protection overhead, snapshot space. What is missing is the entire rest of the billing chain: no rate engine, no notion of customer or department, no monthly report a manager could read, no consolidated history.
That is precisely the gap a chargeback tool fills: turning OneFS raw metrics into charges — amounts, in a currency, attached to organizational entities, over accounting periods.
Choosing the billing unit: the access zone
The access zone is the natural chargeback unit on PowerScale. Each zone has its own directory service, its own shares and its own tree: it almost always maps to a real organizational entity — a department, a faculty, a hosted client. Wiring each zone to a billing “tenant” yields complete coverage: 100% of consumption attributed, zero orphaned terabytes.
A complete PowerScale rate model distinguishes three components:
- Data capacity — the files themselves, in $/GiB per month;
- Protection overhead — space consumed by redundancy (erasure coding, mirroring), which can be priced separately or folded into the base rate;
- Snapshots — snapshot space, often priced lower to encourage protection, but never free: it is what silently explodes when a retention policy is misconfigured.
Rate tiers (the first 10 TiB at one price, the rest cheaper) let you reflect your real economies of scale.
Implementation, step by step
- Inventory the access zones across all clusters and identify each one’s organizational owner. Zones with no obvious owner are your first cleanup opportunity.
- Create the tenants — the billing entity, with its currency, contact and report address.
- Define rate profiles and attach them to zones. Start simple: one realistic default profile beats twelve theoretical ones.
- Run a blank month. Produce the reports without distributing them, validate the amounts with two or three friendly managers, adjust the rates.
- Publish — automatic monthly delivery of reports to each tenant, with history starting to accumulate.
The classic pitfalls
- Disabled zones are not billed — verify every zone you intend to charge is active in the metering tool.
- Currency must be consistent between the tenant and every profile applied to its components; improvised exchange rates ruin report credibility.
- The first report will surprise people. Plan an explanatory note: protection overhead and snapshots are invisible to users, who only know “the size of their files”.
- Do not bill retroactively. Announce, run two months of showback, then switch on real billing if that is the goal.