[#12] Add __FROSTFS__ system prefix

Signed-off-by: Denis Kirillov <d.kirillov@yadro.com>
This commit is contained in:
Denis Kirillov 2023-03-06 14:56:09 +03:00
parent eafcbff11f
commit 3adb55c38a
15 changed files with 56 additions and 56 deletions

View file

@ -587,16 +587,16 @@ values will be considered invalid.
There are some "well-known" attributes affecting system behaviour:
* __NEOFS__SUBNET \
* [ __NEOFS__SUBNET | __FROSTFS__SUBNET ] \
String ID of a container's storage subnet. Any container can be attached to
one subnet only.
* __NEOFS__NAME \
* [ __NEOFS__NAME | __FROSTFS__NAME ] \
String of a human-friendly container name registered as a domain in
NNS contract.
* __NEOFS__ZONE \
String of a zone for `__NEOFS__NAME`. Used as a TLD of a domain name in NNS
* [ __NEOFS__ZONE | __FROSTFS__ZONE ] \
String of a zone for `__NEOFS__NAME`/`__FROSTFS__NAME`. Used as a TLD of a domain name in NNS
contract. If no zone is specified, use default zone: `container`.
* __NEOFS__DISABLE_HOMOMORPHIC_HASHING \
* [ __NEOFS__DISABLE_HOMOMORPHIC_HASHING | __FROSTFS__DISABLE_HOMOMORPHIC_HASHING ] \
Disables homomorphic hashing for the container if the value equals "true" string.
Any other values are interpreted as missing attribute. Container could be
accepted in a NeoFS network only if the global network hashing configuration