Admin Guide¶
Shared File Systems service provides a set of services for management of shared file systems in a multi-project cloud environment. The service resembles OpenStack block-based storage management from the OpenStack Block Storage service project. With the Shared File Systems service, you can create a remote file system, mount the file system on your instances, and then read and write data from your instances to and from your file system.
The Shared File Systems service serves same purpose as the Amazon Elastic File System (EFS) does.
The Shared File Systems service can run in a single-node or multiple node configuration. The Shared File Systems service can be configured to provision shares from one or more back ends, so it is required to declare at least one back end. Shared File System service contains several configurable components.
It is important to understand these components:
Share networks
Shares
Multi-tenancy
Back ends
The Shared File Systems service consists of four types of services, most of which are similar to those of the Block Storage service:
manila-api
manila-data
manila-scheduler
manila-share
Installation of first three - manila-api
, manila-data
, and
manila-scheduler
is common for almost all deployments. But configuration
of manila-share
is backend-specific and can differ from deployment to
deployment.
- Key concepts
- Share management
- Share types
- Quotas and limits
- Share group types
- Share groups
- Share snapshots
- Share servers
- Share server management
- Share server limits (Since Wallaby release)
- Security services
- Share migration
- Share replication
- Multi-storage configuration
- Networking
- Troubleshoot Shared File Systems service
- Profiling the Shared File Systems service
- Upgrading the Shared File System service
- Share revert to snapshot
- Share server migration
- Manila share features support mapping
- Capabilities and Extra-Specs
- Group Capabilities and group-specs
- Export Location Metadata