nird data

sigma2.no · Storage · 2 records · JSON

nird data lake / data peak as a free tier (sigma2, norway) Storagefails: quotaemail?card?Rdisagrees
NIRD Data Lake (Sigma2, Norway) — S3 object storage, 10 TB single-object support, 100M objects/bucket Storagefails: quotainstitutionno cardRper-object-capdisagrees

nird data lake / data peak as a free tier (sigma2, norway) Storage

fails: quotaemail?card?Rdisagrees

www.sigma2.no/user-contribution-model · rejected-provider · storage/nird-data-lake-data-peak-as-a-free-tier · JSON · compare

Sibling records disagree:

identity_kind: storage/nird-data-lake-data-peak-as-a-free-tier says email, storage/nird-data-lake-s3-object-storage-10-tb-single-object-sup says institution

Free tier	Not free — this is the single most important correction in this dossier. The User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD Data unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	Not free — this is the single most important correction in this dossier. The User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD Data
Notes	Not free — this is the single most important correction in this dossier. The User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD Data
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (1)

date	source	what it proved
2026-10-21	www.sigma2.no/user-contribution-model	Not free — this is the single most important correction in this dossier. The User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD Data

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "Not free — this is the single most important correction in this dossier. The User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD Data",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (15)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded

NIRD Data Lake (Sigma2, Norway) — S3 object storage, 10 TB single-object support, 100M objects/bucket Storage

fails: quotainstitutionno cardRper-object-capdisagrees

documentation.sigma2.no/files_storage/nird/s3.html · academic · storage/nird-data-lake-s3-object-storage-10-tb-single-object-sup · JSON · compare

Sibling records disagree:

identity_kind: storage/nird-data-lake-data-peak-as-a-free-tier says email, storage/nird-data-lake-s3-object-storage-10-tb-single-object-sup says institution

Free tier	No fixed per-project byte number published — quota is set per project by the Resource Allocation Committee (RFK) in TiB on NIRD Data Peak and/or Data Lake separately. What IS fixed and unusually generous: 'NIRD S3 supports 10TB single object sizes and up to 100 million objects per bucket', total NIRD capacity 75 PB (24 PB DP + 51 PB DL), and measured throughput '27GB/s'. unit TiB; metered on unstated
Price	none stated
Per-object cap	10 TB per single object (10000000000000 bytes)
Retention	not stated
Egress	Unmetered; S3 and HTTPS serve directly, and NIRD S3 is explicitly for 'data sharing with external collaborators' and 'data streaming'.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: 800 NOK per TB/year' for Category A, invoiced yearly to the institution. 20 TiB of Data Lake ≈ 9,400 NOK/yr. The bytes are unmetered but the TB-years are not — this fails the 'free' filter un
Limits	per-object-cap 10 TB per single object source per-object-cap: 10 TB per single object, 100M objects per bucket — the most permissive object caps in this niche. Retention: 'long-term storage of non-persistent data'; Data Lake has NO on-demand backup ('On-demand backup \| Yes \| No'), only erasure coding and snapshots. request-rate: not published (27 GB/s aggregate is the claim). Gate: Norwegian university/research affiliation plus RFK allocation.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	s3, nfs, rclone, cli s3
Tooling	rclone (provider = Other, endpoint https://s3.nird.sigma2.no), AWS CLI, s3cmd, MinIO client, Cyberduck. The same data is simultaneously available over POSIX, NFS and S3 — 'the same data can be accessed simultaneously through multiple protocols'.
Composes with	Quota is per project and RFK-allocated, so the multiplier is project count and the DP/DL split (two resources, 'The two resources have separate quota based on the project allocation'). NIRD Data Lake is pitched at 'structured or unstructured data of any volume larger than 1 TiB' — i.e. the intended workload IS tens of TB.
Reliability	CRITICAL COST CAVEAT most agents will miss: NIRD is NOT free. The User Contribution Model (v2.2, valid from 1 Oct 2025) prices it at 'NIRD Data Lake 470 NOK per TB/year' and 'NIRD Data Peak 800 NOK per TB/year' for Category A, invoiced yearly to the institution. 20 TiB of Data Lake ≈ 9,400 NOK/yr. The bytes are unmetered but the TB-years are not — this fails the 'free' filter unless an EU-programme exemption applies ('Projects participating in EU programmes are exempted from contribution').
Notes	No fixed per-project byte number published — quota is set per project by the Resource Allocation Committee (RFK) in TiB on NIRD Data Peak and/or Data Lake separately. What IS fixed and unusually generous: 'NIRD S3 supports 10TB single object sizes and up to 100 million objects per bucket', total NIRD capacity 75 PB (24 PB DP + 51 PB DL), and measured throughput '27GB/s'.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 10.0 TB

Evidence (6)

date	source	what it proved
2026-10-21	documentation.sigma2.no/files_storage/nird/s3.html	'NIRD S3 supports 10TB single object sizes and up to 100 million objects per bucket', rclone config with endpoint s3.nird.sigma2.no, 'measured throughput of 27GB/s'
2026-10-21	documentation.sigma2.no/files_storage/nird/dp_dl.html	DP vs DL table: DL protocols 'POSIX, GPFS and NFS', 'S3'; 'On-demand backup \| No'; 'storage for structured or unstructured data of any volume larger than 1 TiB'
2026-10-21	documentation.sigma2.no/files_storage/nird_lmd.html	'The total capacity of NIRD is 75 PB (24 PB on DP and 51 PB on DL)'
2026-10-21	www.sigma2.no/user-contribution-model	captured 2025-12-06: 'NIRD Data Lake \| 470 NOK per TB/year', 'NIRD Data Peak \| 800 NOK per TB/year', 'All prices below are valid from 1 October 2025. The current version of the User Contribution model is V2.2.'
2026-10-21	s3.nird.sigma2.no/	probe: curl -D - -> HTTP/1.1 200 OK, Server: NooBaa/5.21.4, ListAllMyBucketsResult Owner NooBaa. Live and answering; NooBaa (not Ceph), which means S3-over-object-store namespace rather than RGW.
2026-10-21	s3.nird.sigma2.no/probe-xyz/probe.txt	probe: curl -X PUT --data x -> 404 (write correctly closed)

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "No fixed per-project byte number published — quota is set per project by the Resource Allocation Committee (RFK) in TiB on NIRD Data Peak and/or Data Lake separately. What IS fixed and unusually generous: 'NIRD S3 supports 10TB single object sizes and up to 100 million objects per bucket', total NIRD capacity 75 PB (24 PB DP + 51 PB DL), and measured throughput '27GB/s'.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (5)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted