Skip to content

Commit

Permalink
Address comments
Browse files Browse the repository at this point in the history
Signed-off-by: Ben <[email protected]>
  • Loading branch information
Neon-White committed Nov 18, 2024
1 parent 8b9ba92 commit 5ff6e44
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion doc/bucket-types.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,10 @@ Data buckets are the 'classic' type of bucket in NooBaa. NooBaa deployments usua
The only way to access the objects on data buckets is through NooBaa - the chunks cannot be used or deciphered without the system.

## Namespace Buckets
Namespace buckets work differently than data buckets, since they try¹ to not apply any processing on the objects that are uploaded to them, and act as more of a 'passthrough'. In cases where a non-S3 storage provider API is used, NooBaa takes care of bridging potential gaps between S3 and the provider's API - no user action is required.
Namespace buckets work differently than data buckets, since they try¹ to not apply any processing on the objects that are uploaded to them, and act as more of a 'passthrough'. In cases where a non-S3 storage provider API is used, NooBaa takes care of bridging potential gaps between S3 and the provider's API - no user action is required. This also means that as long as NooBaa supports a certain provider's API, users can 'translate' it to S3 with NooBaa, regardless of what API the cloud provider supplies.
The objects can be accessed both from within NooBaa, as well as from whatever storage providers hosts them.
Namespace buckets also support having multiple 'read' sources - for example, a single namespace bucket can show the objects from several Azure Blob containers, AWS S3 buckets, Google Cloud Platform buckets, all at the same time.
Another feature of namespace buckets is cache, which can be configured to keep frequently-accessed objects in the system's memory, effectively reducing access time as well as egress and access costs.

<sup><sub>1. In some cases, object metadata (such as tags) might have to be modified in order to comply with a cloud provider's limits</sub></sup>

Expand All @@ -24,6 +26,8 @@ The objects can be accessed both from within NooBaa, as well as from whatever st
| Filesystem (NSFS) | ❌ | ✅
| Persistent Volume Pool | ✅ | ❌

For specific API calls, you can check [AWS API Compatibility](https://github.com/noobaa/noobaa-core/blob/master/docs/design/AWS_API_Compatibility.md)

<sub>Please note that the table above might be out of date, or have additional support that is not present in older versions - the best way to check if a storage provider is supported is to run the NooBaa CLI tool (that fits the NooBaa version installed on the cluster) with a command such as `noobaa namespacestore create` or `noobaa backingstore create` and see which providers are listed in the help message.</sub>

## Buckets in Relation to Bucketclasses and Stores
Expand Down

0 comments on commit 5ff6e44

Please sign in to comment.