Use cases for configuring the Object Store server
You can configure the Object Store server depending on different use cases.
Use Case 1: Large number of objects per bucket are required.
The admin can configure a default pool without using the fs_sharing option.
The file system is not shared across buckets. A bucket can have large number of objects. The choice of file system sharing limits the number of buckets created.
Use Case 2: Admin needs large number of buckets but does not expect large number of objects per bucket.
The admin can create a group in its authentication server and configure this group in Object Store using the objectaccess> group set command.
The grouping provides options like choosing the disk pool to use, file system type, file system sharing, file system size, other file system options.
The admin can use the fs_sharing option to configure the Object Store server to share a file system across all buckets that are created by a user of that particular group.
The file system sharing allows the Object Store server to create a large number of buckets but limits the total number of objects present across the bucket.
Use Case 3: Admin wants to control the file system used for a bucket.
The admin has to pre-create the required file system using the storage> fs commands.
The admin can use the objectaccess> map command to map a directory of the existing file system as a bucket for a particular user.