Quick start

This document describes how to install Manila from the OpenStack Kilo release. Note that the process differs from previous releases and is likely to change again in subsequent releases.

Manila consists of three main services, which are similar to those of the OpenStack Cinder project:

  • manila-api
  • manila-scheduler
  • manila-share

Installation of first two - manila-api and manila-scheduler is common for almost all deployments. But configuration of manila-share is backend-specific and can differ from deployment to deployment. Hence, this doc will cover just some specific case. Hence, this document will cover a single use case, configuring the “Generic” driver that uses the Cinder project as its backend.

Note that the manila-share service can run in two modes, with and without handling of share servers. In most cases share servers are virtual machines that export file shares via various network file systems. The example in this document describes a backend that manages share servers using network resources provided by Neutron.


Manila supports any network architecture. When a driver is managing its own share servers, it can use any of several network plug-ins that provide network resources. Manila includes plug-ins for Neutron and Nova-network, as well as a StandaloneNetworkPlugin for simple networks. When a driver is not managing share servers, it has no need for network plug-ins.


  • MySQL database
  • RabbitMQ message bus
  • OpenStack Keystone
  • Git

For Generic driver:

  • OpenStack Nova
  • OpenStack Neutron
  • OpenStack Cinder

Steps to perform

  • Installation of Manila binaries
  • Installation of Manila client
  • Registration in Keystone
  • Preparation of external files (configs, etc...)
  • Basic configuration of Manila
  • Database setup
  • Running Manila services
  • Creation of pilot share

Installation of Manila binaries

Manila binaries may be installed using various distribution packages or from source code. In our case we will use the latter, installation by cloning a git repository.

Clone repo:

$ git clone -b stable/kilo https://github.com/openstack/manila

Then run the installation script:

$ sudo python setup.py install

It will install the Manila binaries and their dependencies. These are the expected binaries:

  • manila-all
  • manila-api
  • manila-manage
  • manila-scheduler
  • manila-share

Installation of Manila client

To send requests to Manila we need to install the Manila client.

Install it using PIP:

$ sudo pip install python-manilaclient>=1.0.4


The starting version of the Manila client for Kilo release is 1.0.4

The above will install the Manila binary that will be used for issuing manila requests.

Registration in Keystone

Like all other OpenStack projects, Manila should be registered with Keystone. Here are the registration steps, similar to those of Cinder:

  1. Create Manila service user:

    $ keystone user-create --name manila --pass %PASSWORD%
  2. Add the admin role to the Manila user:

    $ keystone user-role-add --user manila --tenant service --role admin


Tenant/project may differ, but it should be the same as for all other service users such as ‘cinder’, ‘nova’, etc.

  1. Create the Manila service entities:

    $ keystone service-create \
        --name manila \
        --type share \
        --description "OpenStack Shared Filesystems"
    $ keystone service-create \
        --name manilav2 \
        --type sharev2 \
        --description "OpenStack Shared Filesystems V2"


|   Property  |              Value               |
| description |   OpenStack Shared Filesystems   |
|   enabled   |               True               |
|      id     | 4c13e9ff7ec04f4e95a26f72ecdf9919 |
|     name    |              manila              |
|     type    |              share               |

|   Property  |              Value               |
| description | OpenStack Shared Filesystems V2  |
|   enabled   |               True               |
|      id     | 2840d1e7b033437f8776a7bd5045b28d |
|     name    |             manilav2             |
|     type    |             sharev2              |
  1. Create the Share Filesystems service API endpoints:

    $ keystone endpoint-create \
        --service-id $(keystone service-list | awk '/ share / {print $2}') \
        --publicurl http://%controller%:8786/v1/%\(tenant_id\)s \
        --internalurl http://%controller%:8786/v1/%\(tenant_id\)s \
        --adminurl http://%controller%:8786/v1/%\(tenant_id\)s \
        --region regionOne
    $ keystone endpoint-create \
        --service-id $(keystone service-list | awk '/ sharev2 / {print $2}') \
        --publicurl http://%controller%:8786/v2/%\(tenant_id\)s \
        --internalurl http://%controller%:8786/v2/%\(tenant_id\)s \
        --adminurl http://%controller%:8786/v2/%\(tenant_id\)s \
        --region regionOne


|   Property  |                   Value                   |
|   adminurl  | http://%controller%:8786/v1/%(tenant_id)s |
|      id     |     c1984777db6941919657d15b25f05c94      |
| internalurl | http://%controller%:8786/v1/%(tenant_id)s |
|  publicurl  | http://%controller%:8786/v1/%(tenant_id)s |
|    region   |                 regionOne                 |
|  service_id |     4c13e9ff7ec04f4e95a26f72ecdf9919      |

|   Property  |                   Value                   |
|   adminurl  | http://%controller%:8786/v2/%(tenant_id)s |
|      id     |      63ddffd27e8c4c62b4ffb228083325e6     |
| internalurl | http://%controller%:8786/v2/%(tenant_id)s |
|  publicurl  | http://%controller%:8786/v2/%(tenant_id)s |
|    region   |                 regionOne                 |
|  service_id |      2840d1e7b033437f8776a7bd5045b28d     |


Port ‘8786’ is the default port for Manila. It may be changed to any other port, but this change should also be made in the Manila configuration file using opt ‘osapi_share_listen_port’ which defaults to ‘8786’.

Preparation of external files

Copy files from %git_dir%/etc/manila to dir ‘/etc/manila’:


Then generate a config sample file using tox:

$ tox -e genconfig

This will create a file with the latest config options and their descriptions:


Copy this file to the same directory as the above files, removing the suffix ‘.sample’ from its name:

$ cp %git_dir%/etc/manila/manila.conf.sample /etc/manila/manila.conf


Manila configuration file may be used from different places. /etc/manila/manila.conf is one of expected paths by default.

Basic configuration of Manila

In our case we will set up one backend with generic driver (using Cinder as its backend) configured to manage its own share servers. Open Manila configuration file /etc/manila/manila.conf:

signing_dir = /var/cache/manila
admin_password = %password_we_used_with_user_creation_operation%
admin_user = manila
admin_tenant_name = %service_project_name_we_used_with_user_creation_operation%
auth_protocol = http
auth_port = 35357
auth_host = %address_of_machine_with_keystone_endpoint%

# Set up MySQL connection. In following  ‘foo’ is username,
# ‘bar’ is password and ‘quuz’ is host name or address:
connection = mysql+pymysql://foo:bar@quuz/manila?charset=utf8

# Following opt defines directory to be used for lock files creation.
# Should be owned by user that runs manila-share processes.
# Defaults to env var ‘OSLO_LOCK_PATH’. It is used by manila-share services
# and is required to be set up. Make sure this dir is created and owned
# by user that run manila-share services.
lock_path = /etc/manila/custom_manila_lock_path

# Set pretty logging output. Not required, but may be useful.
logging_exception_prefix = %(color)s%(asctime)s.%(msecs)d TRACE %(name)s ^[[01;35m%(instance)s^[[00m
logging_debug_format_suffix = ^[[00;33mfrom (pid=%(process)d) %(funcName)s %(pathname)s:%(lineno)d^[[00m
logging_default_format_string = %(asctime)s.%(msecs)d %(color)s%(levelname)s %(name)s [^[[00;36m-%(color)s] ^[[01;35m%(instance)s%(color)s%(message)s^[[00m
logging_context_format_string = %(asctime)s.%(msecs)d %(color)s%(levelname)s %(name)s [^[[01;36m%(request_id)s ^[[00;36m%(user_id)s %(project_id)s%(color)s] ^[[01;35m%(instance)s%(color)s%(message)s^[[00m

# Set auth strategy for usage of Keystone
auth_strategy = keystone

# Set message bus creds
rabbit_userid = %rabbit_username%
rabbit_password = %rabbit_user_password%
rabbit_hosts = %address_of_machine_with_rabbit%
rpc_backend = rabbit

# Following opt is used for definition of share backends that should be enabled.
# Values are conf groupnames that contain per manila-share service opts.
enabled_share_backends = london

# Enable protocols ‘NFS’ and ‘CIFS’ as those are the only supported
# by Generic driver that we are configuring in this set up.
# All available values are (‘NFS’, ‘CIFS’, ‘GlusterFS’, ‘HDFS’)
enabled_share_protocols = NFS,CIFS

# Following is password for user ‘neutron’ for interaction with Neutron.
# It is required only when Neutron is set up in lab, and handling of
# share servers is used within configured share drivers.
neutron_admin_password = %password%

# Following is password for user ‘cinder’ for interaction with Cinder service.
# Used only by Generic driver.
cinder_admin_password = %password%

# Following is password for user ‘nova’ for interaction with Nova service.
# Used only by Generic driver for the moment.
nova_admin_password = %password%

# Set the project/tenant name of the ‘service’ tenant. These should all be the
# same value, but may be different than the default.
neutron_admin_project_name = service
cinder_admin_tenant_name = service
nova_admin_tenant_name = service

# Manila requires ‘share-type’ for share creation.
# So, set here name of some share-type that will be used by default.
default_share_type = default_share_type

state_path = /opt/stack/data/manila
osapi_share_extension = manila.api.contrib.standard_extensions
rootwrap_config = /etc/manila/rootwrap.conf
api_paste_config = /etc/manila/api-paste.ini
share_name_template = share-%s

# Set scheduler driver with usage of filters. Recommended.
scheduler_driver = manila.scheduler.drivers.filter.FilterScheduler

# Set following opt to ‘True’ to get more info in logging.
debug = True

# This is custom opt group that is used for storing opts of share-service.
# This one is used only when enabled using opt `enabled_share_backends`
# from DEFAULT group.

# Set usage of Generic driver which uses Cinder as backend.
share_driver = manila.share.drivers.generic.GenericShareDriver

# Generic driver supports both driver modes - with and without handling
# of share servers. So, we need to define explicitly which one we are
# enabling using this driver.
driver_handles_share_servers = True

# Generic driver is the only driver that uses image from Glance for building
# service VMs in Nova. And following are data for some specific image.
# We used one defined in [1]
# [1] https://github.com/openstack/manila/blob/6785cad9/devstack/plugin.sh#L86
service_instance_password = ubuntu
service_instance_user = ubuntu
service_image_name = ubuntu_1204_nfs_cifs

# These will be used for keypair creation and inserted into service VMs.
path_to_private_key = /home/stack/.ssh/id_rsa
path_to_public_key = /home/stack/.ssh/id_rsa.pub

# Custom name for share backend.
share_backend_name = LONDON


The Generic driver does not use network plugins, so none is part of the above configuration. Other drivers that manage their own share servers may require one of Manila’s network plug-ins.

Database setup

Manila supports different SQL dialects in theory, but it is only tested with MySQL, so this step assumes that MySQL has been installed.

Create the database for Manila:


Then create Manila’s tables and apply all migrations:

$ manila-manage db sync

Here is the list of tables for the Kilo release of Manila:

| Tables_in_manila                           |
| alembic_version                            |
| network_allocations                        |
| project_user_quotas                        |
| quota_classes                              |
| quota_usages                               |
| quotas                                     |
| reservations                               |
| security_services                          |
| services                                   |
| share_access_map                           |
| share_export_locations                     |
| share_metadata                             |
| share_network_security_service_association |
| share_networks                             |
| share_server_backend_details               |
| share_servers                              |
| share_snapshots                            |
| share_type_extra_specs                     |
| share_type_projects                        |
| share_types                                |
| shares                                     |

Running Manila services

Run manila-api first:

$ manila-api \
    --config-file /etc/manila/manila.conf & \
    echo $! >/opt/stack/status/stack/m-api.pid; \
    fg || echo "m-api failed to start" | \
    tee "/opt/stack/status/stack/m-api.failure"

Create a default share type before running manila-share service:

$ manila type-create default_share_type True

Where default_share_type is custom name of share-type and True is value for required extra-spec driver_handles_share_servers. These are required params for creation of share-type.


| ID        | Name               | Visibility | is_default | required_extra_specs                |
| %some_id% | default_share_type | public     | -          | driver_handles_share_servers : True |

Service manila-api may be restarted to get updated information about default share type. So, get list of share types after restart of service manila-api:

$ manila type-list


| ID        | Name                       | Visibility | is_default | required_extra_specs                 |
| %some_id% | default_share_type         | public     | YES        | driver_handles_share_servers : True  |

Add any additional extra specs to share-type if needed using following command:

$ manila type-key default_share_type set key=value

This may be viewed as follows:

$ manila extra-specs-list

Run manila-scheduler:

$ manila-scheduler \
    --config-file /etc/manila/manila.conf & \
    echo $! >/opt/stack/status/stack/m-sch.pid; \
    fg || echo "m-sch failed to start" | \
    tee "/opt/stack/status/stack/m-sch.failure"

Run manila-share:

$ manila-share \
    --config-file /etc/manila/manila.conf & \
    echo $! >/opt/stack/status/stack/m-shr.pid; \
    fg || echo "m-shr failed to start" | \
    tee "/opt/stack/status/stack/m-shr.failure"

Creation of pilot share

In this step we assume that the following services are running:

  • Keystone
  • Nova (used by Generic driver, not strict dependency of Manila)
  • Neutron (default network backend for Generic driver, used when driver handles share servers)
  • Cinder (used by Generic driver)

To operate a driver that handles share servers, we must create a share network, which is a set of network information that will be used during share server creation. In our example, to use Neutron, we will do the following:

$ neutron net-list

Here we note the ID of a Neutron network and one of its subnets.


Some configurations of the Generic driver may require this network be attached to a public router. It is so by default. So, if you use the default configuration of Generic driver, make sure the network is attached to a public router.

Then define a share network using the Neutron network and subnet IDs:

$ manila share-network-create \
    --name test_share_network \
    --neutron-net-id %id_of_neutron_network% \
    --neutron-subnet-id %id_of_network_subnet%

Now we can create a share using the following command:

$ manila create NFS 1 --name testshare --share-network test_share_network

The above command will instruct Manila to schedule a share for creation. Once created, configure user access to the new share before attempting to mount it via the network:

$ manila access-allow testshare ip --access-level rw

We added read-write access to all IP addresses. Now, you can try mounting this NFS share onto any host.