Merge "DocImpact: Add MapR-FS native driver"

api-ref/source/parameters.yaml

@@ -1986,8 +1986,8 @@ project_id_messages_body:
 protocol:
   description: |
     The Shared File Systems protocol of the share to
-    manage. A valid value is ``NFS``, ``CIFS``, ``GlusterFS``, or
-    ``HDFS``.
+    manage. A valid value is ``NFS``, ``CIFS``, ``GlusterFS``,
+    ``CEPHFS``, ``HDFS`` or ``MAPRFS``.
   in: body
   required: true
   type: string
@@ -2810,15 +2810,16 @@ share_new_size:
 share_proto:
   description: |
     The Shared File Systems protocol. A valid value
-    is ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, or ``CephFS``.
-    ``CephFS`` supported is starting with API v2.13.
+    is ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, ``CephFS``,
+    ``MAPRFS``, ``CephFS`` supported is starting with API v2.13.
   in: body
   required: true
   type: string
 share_protocol:
   description: |
     The file system protocol of the member, which is
-    ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS`` or ``CEPHFS``.
+    ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, ``CEPHFS`` or
+    ``MAPRFS``.
   in: body
   required: true
   type: string
@@ -3211,16 +3212,18 @@ snapshot_share_id_request:
 snapshot_share_protocol:
   description: |
     The file system protocol of a share snapshot. A
-    valid value is ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, or
-    ``CephFS``.  ``CephFS`` is supported starting with API v2.13.
+    valid value is ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``,
+    ``CephFS`` or ``MAPRFS``. ``CephFS`` is supported starting
+    with API v2.13.
   in: body
   required: true
   type: string
 snapshot_share_protocol_request:
   description: |
     The file system protocol of a share snapshot. A
-    valid value is ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, or
-    ``CephFS``.  ``CephFS`` is supported starting with API v2.13.
+    valid value is ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``,
+    ``CephFS`` or ``MAPRFS``, ``CephFS`` is supported starting
+    with API v2.13.
   in: body
   required: true
   type: string

doc/source/admin/shared-file-systems-crud-share.rst

@@ -12,8 +12,8 @@ are prerequisite knowledge:
 
 #. To create a share, use :command:`manila create` command and
    specify the required arguments: the size of the share and the shared file
-   system protocol. ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, or
-   ``CephFS`` share file system protocols are supported.
+   system protocol. ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, ``CephFS`` or
+   ``MAPRFS`` share file system protocols are supported.
 
 #. You can also optionally specify the share network and the share type.
 
@@ -88,8 +88,8 @@ To create a file share in no share servers mode, you need to:
 
 #. To create a share, use :command:`manila create` command and
    specify the required arguments: the size of the share and the shared file
-   system protocol. ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, or
-   ``CephFS`` share file system protocols are supported.
+   system protocol. ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, ``CephFS`` or
+   ``MAPRFS`` share file system protocols are supported.
 
 #. You should specify the :ref:`share type <shared_file_systems_share_types>`
    with ``driver_handles_share_servers = False`` extra specification.
@@ -213,8 +213,8 @@ To create a file share in share servers mode, you need to:
 
 #. To create a share, use :command:`manila create` command and
    specify the required arguments: the size of the share and the shared file
-   system protocol. ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, or
-   ``CephFS`` share file system protocols are supported.
+   system protocol. ``NFS``, ``CIFS``, ``GlusterFS``, ``HDFS``, ``CephFS`` or
+   ``MAPRFS`` share file system protocols are supported.
 
 #. You should specify the :ref:`share type <shared_file_systems_share_types>`
    with ``driver_handles_share_servers = True`` extra specification.

doc/source/admin/shared-file-systems-manage-and-unmanage-share.rst

@@ -59,7 +59,7 @@ The positional arguments are:
   back end.
 
 - protocol. The Shared File Systems protocol of the share to manage. Valid
-  values are NFS, CIFS, GlusterFS, or HDFS.
+  values are NFS, CIFS, GlusterFS, HDFS or MAPRFS.
 
 - export_path. The share export path in the format appropriate for the
   protocol:
@@ -72,6 +72,8 @@ The positional arguments are:
 
   - GlusterFS. 10.0.0.1:/foo_volume.
 
+  - MAPRFS. maprfs:///share-0 -C  -Z  -N foo.
+
 The ``driver_options`` is an optional set of one or more key and value pairs
 that describe driver options. Note that the share type must have the
 ``driver_handles_share_servers = False`` option. As a result, a special share

doc/source/admin/shared-file-systems-share-management.rst

@@ -19,6 +19,7 @@ The shares are based on of the supported Shared File Systems protocols:
 * *GLUSTERFS*. Gluster file system (GlusterFS).
 * *HDFS*. Hadoop Distributed File System (HDFS).
 * *CEPHFS*. Ceph File System (CephFS).
+* *MAPRFS*. MapR File System (MAPRFS).
 
 The Shared File Systems service provides set of drivers that enable you to use
 various network file storage devices, instead of the base implementation. That

doc/source/install/index.rst

@@ -17,8 +17,8 @@ The OpenStack Shared File Systems service (manila) provides coordinated
 access to shared or distributed file systems. The method in which the share is
 provisioned and consumed is determined by the Shared File Systems driver, or
 drivers in the case of a multi-backend configuration. There are a variety of
-drivers that support NFS, CIFS, HDFS, GlusterFS, CEPHFS and other protocols
-as well.
+drivers that support NFS, CIFS, HDFS, GlusterFS, CEPHFS, MAPRFS and other
+protocols as well.
 
 The Shared File Systems API and scheduler services typically run on the
 controller nodes. Depending upon the drivers used, the share service can run