The OpenStack series of file Share Service (Manila) detailed

First, what is OpenStack?

OpenStack is an open-source cloud management platform project that combines several key components to do the job. OpenStack supports almost all types of cloud environments, and the project goal is to deliver a simple, massively scalable, rich, standard, unified cloud management platform. OpenStack provides an infrastructure as a service (IaaS) solution through a variety of complementary services, each providing an API for integration. Written in the Python language.

What is a NAS service?

As is well known, there are several types of storage stored, DAS (Direct attached Storage), NAS (Network attached Storage), and SAN (Storage area network) are mainly described today around NAS.

The NAS full name Network attached Storage is a web-based storage service, where the network is generally ethernet. When storage is delivered over the network, multiple applications within the LAN can mount storage services over the network, while mainstream NAS services support the CIFS protocol and the NFS protocol.

What is Manila?

The OpenStack project in Manila sounds like the capital of a country, yes, it is the capital of the Philippines. Haha, let's go to the following:)

The full name of the Manila project is File Share service, which is shared as a service. is one of the sub-projects in the OpenStack Big tent mode that provides file sharing on the cloud, supports CIFS protocols, and NFS protocols.

Community situation

Currently, the Manila project is dominated by major storage vendors, such as NETAPP, Mirantis, EMC, IBM, and so on, and the current version of the project is also being released with the release of OpenStack release.

The following is the GIT address, wiki address, and IRC address for the Manila project. Participate in community meeting discussions at 423 points per week

Https://github.com/openstack/manila

Https://wiki.openstack.org/wiki/Manila

#openstack-manila on IRC (freenode)

Introduction of Functionality

Share

User-specified size, Access protocol, share type

can be accessed concurrently by multiple instances

Share Access Rule ( ACL )

define which clients can access Share

according to IP address is defined

Share Network (shared network)

Define Client Access Share used by Neutron the network and subnets

a Share can only belong to one Share Network

Security Service (security services)

User security Services ( LDAP , Active Directory , Kerberos , etc.)

a Share can be associated with a maximum of one security service

Snapshots (snapshot)

Share a read-only copy of the file system

You can create a shared file system service from a snapshot

Backend

Share Providers of services

a Share must belong to a Backend

Driver (drive)

< Span style= "font-size:14px;font-family: ' Microsoft Jas Black '; > specific implementations of the backend file sharing service, such as gpfs glusterfs emc VNX generic cephfs

Generally use generic drive, CEPHFS driver has already been submitted. Being review.

https://review.openstack.org/#/c/270211/

Create Manila Share procedure description ( generic driver is used here)

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/7C/9E/wKiom1bTvmiju4ZlAAB2I43IlVg774.jpg "title=" Qq20160229114323.jpg "alt=" Wkiom1btvmiju4zlaab2i43ilvg774.jpg "/>

Create a Nova instance to provide Nfs/cifs shared services through Cinder's volume

Each share network creates a Nova instance

Connect to an existing neutron network and subnet

The Nova flavor, glance image, and SSH keypair that are used to create the Nova instance are Manila configured

Manila to configure a Nova instance via SSH

Manila API Overview

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/7C/9C/wKioL1bTwDig3ZpJAAE7xHrIHxk446.png "style=" float: none; "title=" 1.png "alt=" Wkiol1btwdig3zpjaae7xhrihxk446.png "/>

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/7C/9C/wKioL1bTwDmzUmMfAAL44BN7lMI170.png "style=" float: none; "title=" 2.png "alt=" Wkiol1btwdmzummfaal44bn7lmi170.png "/>

Manila Network explanation

Detailed instructions on the management and connection of the Manila network are detailed in King Absalom's blog post, which is not described here. http://mytrix.me/2015/01/network-part-of-manila/, as well as Chen Dihao blog articles about why private networks want to tie routers there are doubts: http://www.jianshu.com/p/ D04f829e3330 both articles are classic and worth a look.

Manila-ui Horizon

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/7C/9C/wKioL1bTwV2w3taQAACs2FKKMAc035.png "style=" float: none; "title=" 1.png "alt=" Wkiol1btwv2w3taqaacs2fkkmac035.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7C/9C/wKioL1bTwV2gxmC-AADFAwMl6sA328.png "style=" float: none; "title=" 2.png "alt=" Wkiol1btwv2gxmc-aadfawml6sa328.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7C/9E/wKiom1bTwOiiI4cAAACaLlMQXo4649.png "style=" float: none; "title=" 3.png "alt=" Wkiom1btwoiii4caaacallmqxo4649.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/7C/9C/wKioL1bTwV6g0yemAACkIB9c72s370.png "style=" float: none; "title=" 4.png "alt=" Wkiol1btwv6g0yemaackib9c72s370.png "/>

This article is from the "Attitude decides everything" blog, please make sure to keep this source http://sangh.blog.51cto.com/6892345/1745955

The OpenStack series of file Share Service (Manila) detailed