fshy

Home / Storage

nird data

sigma2.no · 2 records in Storage · JSON

Records 2

documentation.sigma2.no/files_storage/nird/s3.htmlAcademicstorage/nird-data-lake-s3-object-storage-10-tb-single-object-supJSONcomparereport an error

Sibling records disagree:

Free allowance
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.
Verdict
paidno free allowance; listed for its price
Cost
no price stated
Identity
institutionno card, no phone
Binding limit
per-object-cap10 TB per single object
Evidence
documented13 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
Free tierNo 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
Pricenone stated
Limits
  • per-object-cap (binding) 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.
Identityinstitution Applicants belong to a listed Norwegian organisation (universities and university colleges, governmental research centres, hospitals, industrial parties); the project leader holds a permanent, postdoctoral or temporary position; master and PhD students and guest researchers apply through a colleague.
EgressUnmetered; S3 and HTTPS serve directly, and NIRD S3 is explicitly for 'data sharing with external collaborators' and 'data streaming'.
Per-object cap10 TB per single object (10000000000000 bytes)
Retentionnot stated
Interfaces3, nfs, rclone, cli part of the text of Free tier, above
Toolingrclone (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 withQuota 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.
ReliabilityCRITICAL 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').
NotesPriced per TB per year for an allocated project: Category A NIRD Data Lake 470 NOK per TB/year and NIRD Data Peak 800 NOK per TB/year (valid from 1 October 2025); projects participating in EU programmes are exempted from contribution.
Evidence notedocumented documented: the 10 TB single-object size was read on 2026-11-03 at https://documentation.sigma2.no/files_storage/nird/s3.html, the Data Lake yearly price per TB at https://www.sigma2.no/user-contribution-model, the backup difference at https://documentation.sigma2.no/files_storage/nird/dp_dl.html and the applicant eligibility at https://www.sigma2.no/apply-e-infrastructure-resources.
Parsed numbers
  • has-free-tier 0
  • per-object-cap 10 TB
Evidence 13
datesourcewhat it proved
2026-10-21documentation.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-21documentation.sigma2.no/files_storage/nird/dp_dl.htmlDP 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-21documentation.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-21www.sigma2.no/user-contribution-modelcaptured 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-21s3.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-21s3.nird.sigma2.no/probe-xyz/probe.txtprobe: curl -X PUT --data x -> 404 (write correctly closed)
2026-11-03www.sigma2.no/user-contribution-modelCategory A NIRD Data Lake costs 470 NOK per TB per year
2026-11-03www.sigma2.no/apply-e-infrastructure-resourcesstudents and guest researchers cannot apply directly; an eligible organisation and project leader are required
2026-11-03www.sigma2.no/user-contribution-modelEU-programme projects are exempt from the contribution
2026-11-03www.sigma2.no/user-contribution-modelCategory A NIRD Data Peak costs 800 NOK per TB per year
2026-11-03documentation.sigma2.no/files_storage/nird/dp_dl.htmlData Peak has on-demand backup, Data Lake has none
2026-11-03documentation.sigma2.no/files_storage/nird/s3.htmlthe single-object size is 10TB
2026-11-04documentation.sigma2.no/files_storage/nird/s3.htmlNIRD S3 supports 10 TB single objects
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 values 3
  • per object cap notes: the field may be stated in a source that was not read
  • retention notes: the field may be stated in a source that was not read
  • retention stated: the field may be stated in a source that was not read

www.sigma2.no/user-contribution-modelstorage/nird-data-lake-data-peak-as-a-free-tierJSONcomparereport an error

Sibling records disagree:

Free allowance
The User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD…
Verdict
fails: quotathe free allowance is too small to matter
Cost
not stated
Identity
email?placeholder, not evidence; card unknown, phone unknown
Binding limit
noneno named constraint binds
Evidence
reported1 source; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierThe User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD…
unit none; metered on none
Pricenone stated
Identityemail (placeholder) not published
Egressnot recorded
Interfaceunknown
Toolingnot recorded
Evidence 1
datesourcewhat it proved
2026-10-21www.sigma2.no/user-contribution-modelThe 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": "The User Contribution Model v2.2 charges 470 NOK per TB/year for NIRD Data Lake and 800 NOK per TB/year for NIRD…","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 7
  • chaining: no value was recorded for this field
  • egress terms: no value was recorded for this field
  • interface: the access interface was not established
  • per object cap notes: no value was recorded for this field
  • per object cap stated: no value was recorded for this field
  • retention stated: no value was recorded for this field
  • tooling: no value was recorded for this field