Managing File Storage with Lustre File Systems
Manage Oracle Cloud Infrastructure File Storage with Lustre file systems.
Use the following tasks to manage a File Storage with Lustre file system:
- Listing File Systems
- Creating a File System
- Getting a File System's Details
- Editing a File System
- Updating File System Encryption
- Increasing File System Capacity
- Updating File System Root Squash Configuration
- Updating File System Network Security Groups
- Moving a File System to a Different Compartment
- Deleting a File System
Apply tags to resources to help organize them according to your business needs. You can apply tags when you create a resource, and you can update a resource later to add, revise, or remove tags. For general information about applying tags, see Resource Tags.
Lustre Quotas
Customers can use the Lustre file system storage quota feature (lfs setquota) to set user-based, group-based, and project-based quotas on the file system itself to limit end-user capacity utilization & optimize cost.
To limit File Storage with Lustre resources, see Limits on File Storage with Lustre Resources.
Required IAM Policy
To use Oracle Cloud Infrastructure, an administrator must be a member of a group granted security access in a policy by a tenancy administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don't have permission or are unauthorized, verify with the tenancy administrator what type of access you have and which compartment your access works in.
If you're new to policies, see Getting Started with Policies and Common Policies.
The following IAM policy statement allows a group of administrators to manage File Storage with Lustre resources:
Allow group <lustre-admin-group> to manage lustre-file-family in compartment <file_system_compartment>The following required policy allows the File Storage with Lustre service to attach Lustre servers hosts to subnets in your tenancy:
allow service lustrefs to use virtual-network-family in tenancyWithout the preceding policy, File Storage with Lustre can't use the network resources necessary to function.
If you're planning to encrypt file systems using your own keys, see the policies in Updating File System Encryption.
For more information, see File Storage with Lustre Policies.
Limitations and Considerations
- The minimum capacity for a file system is 31.2 TB. File system capacity can be increased in specific increments. File system capacity can't be decreased.
- The default maximum capacity for a file system is 200 TB. If you need more than 200 TB of capacity, contact support.
- The maximum aggregate throughput per tenancy is 200 GBps. This can be used across multiple file systems. For example, you can create a 72.8 TB file system at 125 MB/s/TB (for an aggregate of 91 GBps) and a 41.6 TB file system at 250 MB/s/TB (for an aggregate of 104 Gbps).
- Don't use /25 or smaller subnets for file system creation because they don't have enough available IP addresses.
- For file systems with capacity between 120 TB and 215 TB, use /24 or larger subnets
- For file systems with capacity between 200 TB and 400 TB, use /23 or larger subnets
- You can't attach a file system to a public subnet in a VCN. File systems must be attached to private subnets.