openstack/openstack-manuals
Code Issues Proposed changes
Files
c4a5766fae2d29129c24ac7a3754bf00053dd749
openstack-manuals/doc/admin-guide/source/shared_file_systems_intro.rst
Joseph Robinson 2ce5b11b1a [User Guides] Rename Admin-Guide-Cloud to Admin-Guide 
This patch changes the name of the Admin-Guide from the Cloud
Admin Guide to the Administrator guide. This affects the
filename in the repository, and references to cloud administrators
within the document texts.

1.) Changing instances of 'cloud administrator'
    to 'administrator'.

2.) Change links from '/admin-guide-cloud/' to
    '/admin-guide/' within the Admin Guide.

3.) Adjust .htaccess file.

Change-Id: I7f21a710e922981aa295afc0616de36fd819b523
Implements: blueprint user-guides-reorganised
2016-04-01 19:50:13 +09:00

1.0 KiB
Raw Blame History

Introduction

The OpenStack File Share service allows you to offer shared file systems service to OpenStack users in your installation. 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.