openstack/manila
Code Issues Proposed changes
4e25ce5a0c
manila/doc/source/devref/architecture.rst
Danny Al-Gaaf 84e953ca75 Unify usage of project name in doc to 'manila' 
Change project name in doc according to style rules in
http://docs.openstack.org/contributor-guide/writing-style/openstack-components.html

Closes-Bug: #1537808

Change-Id: I849b0ec34a1bfc01263f35a9ef0128100945867e
Signed-off-by: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
2016-02-15 20:25:28 +01:00

3.1 KiB
Raw Blame History

Manila System Architecture

The Shared File Systems service is intended to be ran on one or more nodes.

Manila uses a sql-based central database that is shared by all manila services in the system. The amount and depth of the data fits into a sql database quite well. For small deployments this seems like an optimal solution. For larger deployments, and especially if security is a concern, manila will be moving towards multiple data stores with some kind of aggregation system.

Components

Below you will a brief explanation of the different components.

/- ( LDAP )
[ Auth Manager ] ---
|            \- ( DB )
|
|

|
[ Web Dashboard ]- manilaclient -[ manila-api ] -- < AMQP > -- [ manila-scheduler ] -- [ manila-share ] -- ( shared filesystem )
|
|
|
|
|
< REST >
  • DB: sql database for data storage. Used by all components (LINKS NOT SHOWN)
  • Web Dashboard: external component that talks to the api. Beta extended Horizon available here: https://github.com/NetApp/horizon/tree/manila
  • manila-api
  • Auth Manager: component responsible for users/projects/and roles. Can backend to DB or LDAP. This is not a separate binary, but rather a python class that is used by most components in the system.
  • manila-scheduler
  • manila-share

Further Challenges

  • More efficient share/snapshot size calculation
  • Create a notion of "attached" shares with automation of mount operations
  • Support for Nova-network as an alternative to Neutron
  • Support for standalone operation (no dependency on Neutron/Nova-network)
  • Allow admin-created share-servers and share-networks to be used by multiple tenants
  • Support creation of new subnets for share servers (to connect VLANs with VXLAN/GRE/etc)
  • Gateway mediated networking model with NFS-Ganesha
  • Add support for more backends