5.4 KiB
Fuel Manila plugin
https://blueprints.launchpad.net/fuel-plugin-manila/+spec/initial-9.0
There is the Fuel plugin that installs and configures the Manila1.
Problem description
There is the Manila project that provides a shared file system service for OpenStack. It's the new OpenStack project that provides coordinated access to shared or distributed file systems. The Manila has multiple storage backends (to support vendor or file system specific nuances/capabilities) that could work simultaneously on one environment.
The Fuel Manila plugin adds utilization the corresponding OpenStack service in an Fuel environment.
Proposed changes
Install the Manila inside an MOS environment. The python-manilaclient, manila-api and manila scheduler should works on controller. Manila-share and manila-data processes should works on nodes with new roles --- manila-share and manila-date accordingly. Upload the service image into glance (if generic driver is enabled in that environment).
| Public | ManagementPublic
| | Private
| | Storage
| |
+---------------------+ | | +------------+
|Controller | | +----| An NetApp |
|+------------------+ | +--------------o----+ storage |
||haproxy | | | | +------------+
|| manila-api | +--------+ |
|| | | | |
|+------------------+ +--------o--------------+
| manila-scheduler | | | +------------+
+---------------------+ | | | Cinder |
| +----+ node |
+---------------------+ | | +------------+
|Manila-share | | |
| manila-share +--------+ |
+---------------------+ | | +------------+
| | | Compute |
+---------------------+ | +----+ node |
|Manila-data | | | +------------+
| manila-data +--------+ |
+---------------------+ | |
| |Web UI
A user will have possibilities to chose a storage backend and its parameters.
Nailgun
None
Data model
New database, tables and account to database access.
REST API
None
Orchestration
None
RPC Protocol
None
Fuel Client
None
Plugins
The Fuel Manila plugin doesn't interact with others.
Fuel Library
None
Alternatives
Deploy an environment with Cinder and Compute nodes, install and configure the Manila manually.
Upgrade impact
None
Security impact
None
Notifications impact
None
End user impact
Manila has CLI2 and Web3 UI. Both of them will be deployed by the plugin.
Performance impact
None
Deployment impact
There is service image4 that would be built on each deployment with enabled generic driver.
Developer impact
None
Infrastructure impact
None
Documentation impact
- Deployment Guide (how to prepare an environment for installation, how to install the plugin, how to deploy OpenStack an environment with the plugin).
- User Guide (which features the plugin provides, how to use them in the deployed OS environment).
- Test Plan.
- Test Report.
Implementation
Assignee(s)
- Primary assignee:
-
Igor Gajsin <igajsin>
- QA:
-
Oleksandr Kosse <okosse>, Volodymyr Rozhanskyy <vrozhanskyy>
- Mandatory design review:
-
Igor Gajsin <igajsin>
Work Items
- Build infrastructure for the project.
- Install certain packages and programs.
- Do keystone stuff (users, endpoints end so on).
- Create DB user, database and populate it.
- Configure the manila with generic driver.
- Add haproxy and iptables rules.
- Add init scripts.
- Install service image, create storage network
- Add Horizon parts.
- Configure the manila with netapp driver.
Dependencies
The Fuel Manila plugin depends on the whole Manila project. See links in the section "References".
Testing, QA
Will be improved by QA.
Acceptance criteria
Will be improved by QA.