OpenStack Shared Filesystems (manila) documentation

What is Manila?

Manila is the OpenStack Shared Filesystems service for providing Shared Filesystems as a service. Some of the goals of Manila are to be/have:

• Component based architecture: Quickly add new behaviors

• Highly available: Scale to very serious workloads

• Fault-Tolerant: Isolated processes avoid cascading failures

• Recoverable: Failures should be easy to diagnose, debug, and rectify

• Open Standards: Be a reference implementation for a community-driven api

For end users

As an end user of Manila, you’ll use Manila to create a remote file system with either tools or the API directly: python-manilaclient, or by directly using the REST API.

Tools for using Manila

Contents:

• User

Using the Manila API

All features of Manila are exposed via a REST API that can be used to build more complicated logic or automation with Manila. This can be consumed directly or via various SDKs. The following resources can help you get started consuming the API directly:

• Manila API

• Manila microversion history

For operators

This section has details for deploying and maintaining Manila services.

Installing Manila

Manila can be configured standalone using the configuration setting auth_strategy = noauth, but in most cases you will want to at least have the Keystone Identity service and other OpenStack services installed.

• Installation Tutorial

Administrating Manila

Contents:

• Admin Guide

Reference

Contents：

• Configuration
• Command Line Interface

Additional resources

• Manila release notes

For contributors

Contributions to Manila are welcome. There is a lot of background information that can help you get started. Please feel free to also ask any questions in the #openstack-manila IRC channel.

Getting started

• OpenStack Contributor Guide

Contributing to Manila

Contents:

• Contributor/Developer Guide
• API Microversions

Additional reference

Contents:

• Reference

Additional reference

Contents:

• Index