openstack manila - home - netapp...

OpenStack Manila  Shared File Services for the Cloud  Bob Callaway, PhD  Chief Architect & Senior Manager, Technical Marketing – OpenStack Cloud Solutions Group, NetApp  OpenStack Summit – Paris – November 3rd, 2014

© 2014 NetApp, Inc. All rights reserved. NetApp Proprietary – Limited Use Only 1

Agenda

1) Project Overview

2) Use Cases

3) Demo

4) Architectural Overview

5) Drivers: Vendor Integrations

6) Automation

7) What’s new in Juno and Kilo Focus

8) How to get started with Manila


NetApp is a leading innovator in the OpenStack community Manila: The OpenStack Shared File Service Program

Manila

Clustered Data ONTAP

Finance R&D

Share “R&D” with Instances 1 & 3

Create a “Marketing” share for 2 & 4

Nova

Hypervisor

VM VM VM VM VM VM Marketing

Manila is now a

formally incubated

OpenStack program!

 Applicable for a variety of use cases (DBaaS, generic file share, VDI, etc)

of all storage sold is for file-based use cases per IDC, 2012


65 %

Use Cases Manila – The OpenStack Shared File Service Program


Adding File Services along side Block & Object in OpenStack clouds Manila: Shared File Services within an OpenStack Deployment


An Open, Standard API for File System Provisioning and Management Manila: Standalone Shared File Services Management

§  Replace homegrown or legacy systems

§  Improve IT responsiveness by providing self-service share management

§  Integrate Manila with existing automation frameworks through REST API or CLI


Manila

Shared FileServices

REST API

Demo Manila – The OpenStack Shared File Service Program


Key Concepts & Architecture Manila – The OpenStack Shared File Service Program


Manila: Key Concepts

§ Share (an instance of a shared file system) § User specifies size, access protocol, “share type” § Can be accessed concurrently by multiple instances

§ Share access rules (ACL) § Defines which clients can access the share § Specified by IP in CIDR notation

§ Share network § Defines the Neutron network & subnet through which instances

access the share § A share can be associated with only one share network


Manila: Key Concepts (continued)

§ Security service § Finer-grained client access rules for Authn/z (e.g. LDAP, Active

Directory, Kerberos) § Share can be associated to multiple security services

§ Snapshots § Read-only copy of share contents § New share can be created from a snapshot

§ Backend §  Provider of shares; a share resides on a single backend

§ Driver §  Vendor or technology-specific implementation of backend API


Designed for highly available and scalable shared file services Manila: Architectural Overview

§  Manila is not in the data path!

§  manila-api§  Exposes REST API through WSGI

application

§  manila-scheduler§  Makes provisioning decisions for

share requests

§  manila-share§  Manager process + one process per

backend §  Responsible for communicating with

storage subsystems


REST

Manila Processes

Horizon

manila-api manila-scheduler

manila-share Driver

manila-share Driver

manila-share Driver

Control Path

Supports a variety of strategies for diverse deployments Manila: Network and Storage Multitenancy

Network Segmentation Storage Segmentation

Manila Enablement Example Use Case

Layer 3 (IP)

Layer 3 (IP)

Direct Replace custom service Customer PoC on existing equipment

Layer 3 (IP)

Layer 2 (VLAN, VXLAN, GRE, STT, etc)

Single segment (e.g. VLAN) for all tenants

Replace custom service


Layer 3 (IP)

Manila provides gateway Private cloud deployment



Manila configures storage to join appropriate tenant layer 2 network

Public cloud deployment


Drivers Manila – The OpenStack Shared File Service Program


A pluggable model for vendors and the community Manila Drivers

§  Reference Implementation §  Nova VM (from Glance image) hosts NFS, CIFS servers §  Cinder volume (of requested size) per share provides storage capacity

§  NetApp clustered Data ONTAP

§  EMC VNX

§  Red Hat GlusterFS

§  IBM GPFS (in review)

§  HP (in development)

§  More to come…


The worlds #1 storage OS is integrated with OpenStack Manila NetApp’s clustered Data ONTAP Manila Driver

§  Driver points at an existing Clustered Data ONTAP deployment

§  A new storage virtual machine (SVM) is created for each share network

§  Create a new Data Logical Interface (LIF) with the VLAN tag set to same VLAN tag of the Neutron network associated with the share network

§  Access permissions are set at the controller for guests


manila create

Control Path

Data Path

Manila

mount –t nfs

Neutron

nova-compute

NFS

nova-compute

Automation Manila – The OpenStack Shared File Service Program


puppet-manila Puppet Module contributed by NetApp now on Stackforge Automation for installation & configuration of Manila


How does a customer use puppet-manila?


Declare basic service parameters

(DB connection, AMQP, etc)

Declare other config key/value pairs

Installs the API service, configured to use Keystone

Installs Scheduler, Share packages from distro

How does puppet-manila configure/manage Manila?


User or Tool creates or updates manifest

Puppet parses and validates

manifest according to

module

Install distribution-

specific packages (e.g.

RPMs, deb files)

Creates/updates Manila

configuration files per manifest

declaration

Start declared Manila

processes

Monitor process state, configuration files for state

change; enforce

declared state

Juno & Kilo Status Manila – The OpenStack Shared File Service Program


What’s new in Juno

§  Officially an incubated OpenStack program (August 26th, 2014)! §  Note: Manila repos are now under “openstack” Github organization

§  puppet-manila now on stackforge

§  Increased developer & admin documentation

§  Removal of obsolete/unmaintained drivers (NetApp 7mode, LVM)

§  Added concept of "share servers" with admin only APIs

§  Added tempest integration and gate tests

§  Remove a lot of utility code and replace it with Olso (significantly better Oslo integration)

§  Improvements to existing APIs (better filtering, more details, etc)


Kilo Roadmap – Manila Community


10/15 4/15 4/16 10/14

Manila Graduation & Customer PoC Manila Incubation

Features

Theme Proliferate Manila

-  Manila currency and new features -  Generic driver maintenance -  TBD

-  Manila:core maintenance and features -  Triple-O

-  Manila support at the undercloud

-  Generic driver maintenance -  Service implemented QoS

-  investigation

-  Manila Core -  SDN compatibilities

-  OVS bridge for non-SDN native backends

-  Replication -  manage / unmanage -  Backup -  automated mounts

-  Generic driver maintenance -  IPv6 Support -  Consistency Groups -  Enable Trove for Manila awareness -  Deduplicate code via Oslo -  Python 3

-  Manila Core -  SSC -  Pools -  Modular independence

-  Deployment Automation -  Shift devstack -  Puppet & Chef

-  Horizon shift -  Deployer & Tenant facing

documentation -  “Generic” driver maintenance -  Require CI Slave -  Extend Tempest Coverage -  Support all TC graduation

requirements

Kilo L M Juno

Getting Started Manila – The OpenStack Shared File Service Program


Get involved with Manila! How to get started with Manila

§ Devstack § See our blog: http://netapp.github.io/openstack/2014/08/15/manila-devstack/

§ Distributions § RDO §  RPMs are available now; Packstack integration coming soon

§ OpenSUSE §  RPMs are available now; installer integration coming soon

§ More to come…

§ IRC on Freenode § #openstack-manila any time § #openstack-meeting-alt at 15:00 UTC on Thursdays


Questions? Manila – The OpenStack Shared File Service Program


openstack manila - home - netapp...

Documents