openstack/manila
Code Issues Proposed changes
8cb70952e3
manila/doc/source/contributor/architecture.rst
Luigi Toscano e02a625e9c Use the canonical URL for Manila repositories 
- When the URL refers to cloning or using git repositories, use the
  cloning URL (https://git.openstack.org/openstack/<project>)
- When the URL refers to the browsable version of the repository, use
  the cgit frontend (https://git.openstack.org/cgit/openstack/<project>)

Change-Id: I11a8e15c6d663786465c090b40db9e20b19194e6
2018-12-17 13:56:17 +01:00

3.0 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, implemented as a plugin to the OpenStack Dashboard (Horizon) project, source is here.
  • 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
  • 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