OpenStack - User contributions [en]

CinderSupportMatrix

2015-06-05T17:28:13Z

Bob Callaway:

'' Please be aware that the accuracy / completeness of the following (and given the basic characteristics of a wiki) is generally evolving and given its state of flux should be considered in draft state. Please refer to respective vendor's documentation for a more authoritative indication of support.''

== OpenStack Block Storage (aka Cinder) Drivers==

'''Note(s):'''

* OpenStack releases are commonly referred to by their [[ReleaseNaming|development codename]]. Each successive release increments alphabetically (B follows A... and so on).
* The below matrix indicates whether or not a particular feature is supported, and additionally the first release of OpenStack that it is supported in.
* Indication of a particular capability in Folsom or later connotes Cinder support. Essex or prior refers to support for Cinder's predecessor, nova-volume.
* Rows are ordered alphabetically and are not intended to specify precedence.
* Drivers listed in this support matrix are all merged upstream in the OpenStack github. If a driver is not available under https://github.com/openstack/cinder/tree/master/cinder/volume/drivers, please do NOT add to this matrix!



{| class="wikitable sortable" style="text-align: center;"
|-
! Driver !! Create Volume !! Delete Volume !! Attach Volume !! Detach Volume !! Extend Volume !! Create Snapshot !! Delete Snapshot !! List Snapshots !! Create Volume from Snapshot !! Create Volume from Image !! Create Volume from Volume (Clone) !! Create Image from Volume !! Volume Migration (host assisted)!! QoS !! Volume Replication!! Consistency Group!! Supported Protocols
|-
| CloudByte || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || || || iSCSI (Kilo)
|-
| Coraid || Grizzly || Grizzly || Grizzly || Grizzly || Havana || Grizzly || Grizzly || Grizzly || Grizzly || Havana || Havana || Havana || Havana || || || || AoE (Grizzly)
|-
| Datera || Juno || Juno || Juno || Juno || Juno|| Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || || iSCSI (Juno)
|-
| Dell EqualLogic || Havana || Havana || Havana || Havana || Icehouse || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || || || || iSCSI (Havana)
|-
| Dell Storage Center|| Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || || iSCSI (Kilo), FC (Kilo)
|-
| EMC VMAX || Grizzly || Grizzly || Grizzly || Grizzly || Juno || Grizzly || Grizzly || Grizzly || Grizzly || Grizzly || Grizzly || Grizzly || Havana || || || || iSCSI (Grizzly), FC (Icehouse)
|-
| EMC VNX Direct || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || || || Juno || iSCSI (Icehouse), FC (Juno)
|-
| EMC XtremIO || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || iSCSI (Juno), FC (Juno)
|-
| Fujitsu ETERNUS || Juno || Juno || Juno || Juno || Juno|| Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || iSCSI (Juno), FC (Juno)
|-
| GlusterFS || Grizzly || Grizzly || Grizzly || Grizzly || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || || || || GlusterFS (Grizzly)
|-
| Hitachi (HUS) || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || || || || iSCSI (Havana), FC (Juno)
|-
| Hitachi (HUS-VM) || Juno || Juno || Juno || Juno || Juno|| Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || FC (Juno)
|-
| Hitachi (VSP, VSP G1000) || Juno || Juno || Juno || Juno || Juno|| Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || FC (Juno), FCOE (Juno)
|-
| Hitachi (VSP G200-G600) || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || || FC (Kilo), iSCSI (Kilo)
|-
| Hitachi (HNAS) || Juno || Juno || Juno || Juno || Juno|| Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || iSCSI (Juno), NFS (Juno)
|-
| HP 3PAR (StoreServ) || Grizzly || Grizzly || Grizzly || Grizzly || Havana || Grizzly || Grizzly || Grizzly || Grizzly || Grizzly (iSCSI) Havana(FC) || Grizzly || Grizzly (iSCSI) Havana(FC) || Havana || || || || iSCSI (Grizzly), FC (Grizzly)
|-
| HP Lefthand (StoreVirtual) || Diablo || Diablo || Diablo || Diablo || Havana || Havana || Havana || Havana || Havana || Grizzly || Icehouse || Grizzly || Havana || || || || iSCSI (Diablo)
|-
| HP MSA || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || || || || || FC (Icehouse)
|-
| Huawei T Series V1 || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || || || || || iSCSI (Havana), FC (Havana)
|-
| Huawei T Series V2 || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || Kilo || || || iSCSI (Kilo), FC (Kilo)
|-
| Huawei V3 Series || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || Kilo || || || iSCSI (Kilo), FC (Kilo)
|-
| Huawei 18000 Series || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || Kilo || || || iSCSI (Kilo), FC (Kilo)
|-
| IBM DS8000 || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Folsom || Havana || Havana || Havana || Havana || || Juno || || FC (Havana)
|-
| IBM FlashSystem || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || || FC (Kilo)
|-
| IBM GPFS || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || || || || GPFS NSD
|-
| IBM Storwize family/SVC || Folsom || Folsom || Folsom || Folsom || Havana || Folsom || Folsom || Folsom || Folsom || Havana || Grizzly || Grizzly || Havana || Juno || Juno || Kilo || iSCSI (Folsom), FC (Grizzly)
|-
| IBM NAS || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || || || || || NFS
|-
| IBM XIV || Folsom || Folsom || Folsom || Folsom || Havana || Folsom || Folsom || Folsom || Folsom || Grizzly || Havana || Havana || Havana || || || || iSCSI (Folsom), FC (Grizzly)
|-

| LVM (Reference) || Folsom || Folsom || Folsom || Folsom || Havana || Folsom || Folsom || Folsom || Folsom || Grizzly || Grizzly || Grizzly || Havana || || || || iSCSI (Folsom)
|-
| NetApp Data ONTAP || Essex || Essex || Essex || Essex || Havana || Folsom || Folsom || Essex || Essex || Grizzly || Grizzly || Grizzly || Havana || || || || iSCSI (Folsom), NFS (Folsom), FC (Kilo)
|-
| NetApp E/EF-series || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || Icehouse || || || || iSCSI
|-
| Nexenta || Essex || Essex || Essex || Essex || Havana || Essex || Essex || Essex || Essex || Havana || Havana || Grizzly || Havana || || || || iSCSI (Essex), NFS (Havana)
|-
| NFS (Reference) || Folsom || Folsom || Folsom || Folsom || Havana || || || || || Grizzly || Grizzly || Havana || Havana || || || || NFS (Folsom)
|-
| Nimble Storage || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || iSCSI (Juno)
|-
| Pure Storage || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || Kilo || iSCSI (Juno)
|-
| Quobyte || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || || quobyte
|-
| RBD (Ceph) || Cactus || Cactus || Cactus || Cactus || Havana || Diablo || Diablo || Diablo || Folsom || Grizzly || Havana || Grizzly || || || || || RBD (Cactus)
|-
| Scality || Grizzly || Grizzly || Grizzly || Grizzly || Havana || Grizzly || Grizzly || Grizzly || Grizzly || Grizzly || Havana || Grizzly || || || || || Scality (Grizzly)
|-
| SMB || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || Juno || || || || || SMB (Juno)
|-
| SolidFire || Folsom || Folsom || Folsom || Folsom || Havana || Folsom || Folsom || Folsom || Folsom || Grizzly || Grizzly || Grizzly || Havana || || || || iSCSI (Folsom)
|-
| StorPool || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || || StorPool (Kilo)
|-
| Symantec || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || || NFS (Kilo)
|-
| Tintri || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || Liberty || || || || NFS (Liberty)
|-
| Violin Memory || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || n/a || n/a || n/a || iSCSI (Kilo), FC (Kilo)
|-
| VMware || Havana || Havana || Havana || Havana || Icehouse || Havana || Havana || Havana || Havana || Havana || Havana || Havana || || || || || VMware vmdk (Havana)
|-
| Windows Server 2012 || Grizzly || Grizzly || Grizzly || Grizzly || || Grizzly || Grizzly || Grizzly || Grizzly || Havana || || || Havana || || || || iSCSI (Grizzly)
|-
| X-IO technologies || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || Kilo || || || iSCSI (Kilo), FC (Kilo)
|-
| Zadara Storage || Folsom || Folsom || Folsom || Folsom || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || Havana || || || || iSCSI (Folsom), NFS (Havana)
|-
| Solaris (ZFS) || Diablo || Diablo || Diablo || Diablo || || || || || || || || || || || || || iSCSI (Diablo)
|-
| ProphetStor (Flexvisor) || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || Juno || || || || Kilo || iSCSI (Juno), FC (Juno)
|}


[[category: cinder]]

Manila/IcehouseDevstack

2014-05-28T23:13:53Z

Bob Callaway:

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

1. Clone devstack

$ git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git

2. Clone manila

$ git clone https://github.com/stackforge/manila.git

3. Copy over the devstack files from the manila repo into the devstack repo

$ cp manila/contrib/devstack/lib/manila devstack/lib/
$ cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/

4. Copy the sample local.conf into the root devstack directory

$ cd devstack; cp samples/local.conf .

5. Edit/append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
$ cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
#FLOATING_RANGE=192.168.33.128/28
#FLAT_INTERFACE=eth1
#PUBLIC_INTERFACE=eth1
#HOST_IP=192.168.33.10

EOF

6. Run stack.sh as normal; When it is complete, the manila processes should be started, and the horizon extensions for Manila should be present.

7. There is a current defect (https://bugs.launchpad.net/bugs/1314591) that may require you to set the security group rules for the service tenant; this can be achieved by running the following commands:
$ . openrc manila service
$ nova secgroup-add-rule default tcp 1 65535 0.0.0.0/0
$ nova secgroup-add-rule default udp 1 65535 0.0.0.0/0
$ nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0

===== Vagrant File =====

If you use Vagrant, here is a Vagrantfile that I have used successfully with the above process:

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "precise64"

config.vm.network :private_network, ip: "192.168.33.10"

config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", "2048"]
end

config.vm.provision :shell, :inline => "sudo apt-get upgrade -y && sudo apt-get install -y git vim libxslt1-dev libmysqlclient-dev"
end

Manila/JunoSummitPresentation

2014-05-16T19:24:43Z

Bob Callaway: /* Session Recording */

===== Presentation =====
[https://s3.amazonaws.com/netapp-openstack/manila_overview-atlanta-summit+v5.pdf Presentation]

===== Demo =====
[https://s3.amazonaws.com/netapp-openstack/manila_demo_v2.mp4 Demo]

===== Session Recording =====
[https://www.youtube.com/watch?v=fR-X7jbG5QM Session Recording]

Manila/IcehouseDevstack

2014-05-15T02:48:47Z

Bob Callaway:

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

1. Clone devstack

$ git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git

2. Clone manila

$ git clone https://github.com/openstack-dev/devstack.git

3. Copy over the devstack files from the manila repo into the devstack repo

$ cp manila/contrib/devstack/lib/manila devstack/lib/
$ cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/

4. Copy the sample local.conf into the root devstack directory

$ cd devstack; cp samples/local.conf .

5. Edit/append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
$ cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
#FLOATING_RANGE=192.168.33.128/28
#FLAT_INTERFACE=eth1
#PUBLIC_INTERFACE=eth1
#HOST_IP=192.168.33.10

EOF

6. Run stack.sh as normal; When it is complete, the manila processes should be started, and the horizon extensions for Manila should be present.

7. There is a current defect (https://bugs.launchpad.net/bugs/1314591) that may require you to set the security group rules for the service tenant; this can be achieved by running the following commands:
$ . openrc manila service
$ nova secgroup-add-rule default tcp 1 65535 0.0.0.0/0
$ nova secgroup-add-rule default udp 1 65535 0.0.0.0/0
$ nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0

===== Vagrant File =====

If you use Vagrant, here is a Vagrantfile that I have used successfully with the above process:

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "precise64"

config.vm.network :private_network, ip: "192.168.33.10"

config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", "2048"]
end

config.vm.provision :shell, :inline => "sudo apt-get upgrade -y && sudo apt-get install -y git vim libxslt1-dev libmysqlclient-dev"
end

Manila/IcehouseDevstack

2014-05-15T02:47:57Z

Bob Callaway: /* Vagrant File */

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

1. Clone devstack

$ git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git

2. Clone manila

$ git clone https://github.com/openstack-dev/devstack.git

3. Copy over the devstack files from the manila repo into the devstack repo

$ cp manila/contrib/devstack/lib/manila devstack/lib/
$ cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/

4. Copy the sample local.conf into the root devstack directory

$ cd devstack; cp samples/local.conf .

5. Edit/append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
$ cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
#FLOATING_RANGE=192.168.33.128/28
#FLAT_INTERFACE=eth1
#PUBLIC_INTERFACE=eth1
#HOST_IP=192.168.33.10

EOF

6. Run stack.sh as normal; When it is complete, the manila processes should be started, and the horizon extensions for Manila should be present.

7. There is a current defect (https://bugs.launchpad.net/bugs/1314591) that may require you to set the security group rules for the service tenant; this can be achieved by running the following commands:
$ . openrc manila service
nova secgroup-add-rule default tcp 1 65535 0.0.0.0/0
nova secgroup-add-rule default udp 1 65535 0.0.0.0/0
nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0

===== Vagrant File =====

If you use Vagrant, here is a Vagrantfile that I have used successfully with the above process:

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "precise64"

config.vm.network :private_network, ip: "192.168.33.10"

config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", "2048"]
end

config.vm.provision :shell, :inline => "sudo apt-get upgrade -y && sudo apt-get install -y git vim libxslt1-dev libmysqlclient-dev"
end

Manila/JunoSummitPresentation

2014-05-15T02:16:53Z

Bob Callaway:

Manila/JunoSummitPresentation

2014-05-15T02:14:16Z

Bob Callaway:

[https://s3.amazonaws.com/netapp-openstack/manila_overview-atlanta-summit+v5.pdf Presentation]

[https://s3.amazonaws.com/netapp-openstack/manila_demo_v2.mp4 Demo]

Session Recording (to come)

Manila/JunoSummitPresentation

2014-05-15T02:13:22Z

Bob Callaway: Created page with "[https://s3.amazonaws.com/netapp-openstack/manila_overview-atlanta-summit+v5.pptx Presentation] [https://s3.amazonaws.com/netapp-openstack/manila_demo_v2.mp4 Demo] Session R..."

[https://s3.amazonaws.com/netapp-openstack/manila_overview-atlanta-summit+v5.pptx Presentation]

[https://s3.amazonaws.com/netapp-openstack/manila_demo_v2.mp4 Demo]

Session Recording (to come)

Manila

2014-05-14T19:58:00Z

Bob Callaway: /* Meetings */

== Introduction ==
This page documents the concept and vision for establishing a shared file system service for OpenStack. The development name for this project is Manila. We propose and are in the process of implementing a new OpenStack service (originally based on Cinder). Cinder presently functions as the canonical storage provisioning control plane in [[OpenStack]] for block storage as well as delivering a persistence model for instance storage. The File Share Service prototype, in a similar manner, provides coordinated access to shared or distributed file systems. While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. The design and prototype implementation provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is intended to be sufficiently abstract to accommodate any of a variety of shared or distributed file system types. The team's intention is to introduce the capability as an OpenStack incubated project in the Juno timeframe, graduate it and submit for consideration as a core service as early as the as of yet unnamed "K" release.

[[File:Shares_Service.png]]

According to IDC in its “[http://www.idc.com/getdoc.jsp?containerId=235910 Worldwide File-Based Storage 2012-2016 Forecast]", file-based storage continues to be a thriving market, with spending on File-based storage solutions to reach north of $34.6 billion in 2016. Of the 27 Exabyte’s (EB) of total disk capacity estimated to have shipped in 2012, IDC projected that nearly 18 EB were file-based capacity, accounting for over 65% of all disk shipped by capacity. A diversity of applications, from server virtualization to relational or distributed databases to collaborative content creation, often depend on the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products. OpenStack, as the leading open IaaS capability, is increasingly contemplated as an option for deploying classic infrastructure in an "as a Service" model, but without specific accommodation for shared file systems represents an incomplete solution.

== Projects==

=== Manila ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/manila
|-
| Bug tracker
| https://bugs.launchpad.net/manila
|-
| Feature tracker
| https://blueprints.launchpad.net/manila
|}

=== Python Manila Client ===
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/python-manilaclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-manilaclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-manilaclient
|}

=== Meetings ===

[[Manila/Meetings|Project Agenda & Meetings]]

[[Manila/JunoSummitPresentation|Overview Presentation from Juno (Atlanta) Summit]]

=== Getting Started with Manila ===

Instructions for getting started with Manila using Devstack are available at: [[Manila/IcehouseDevstack|Manila on Devstack]]

Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]

=== Project Plan & Progress ===

[[Manila/ProjectPlan|Manila Project Plan]] 
Track progress towards [[Manila/Graduation|Manila Incubation & Graduation]].

== Design & Use Cases ==

[[Manila/design|Manila Component Design]] 
[[Manila/usecases|Manila Use Cases]]

== Subpages ==

{{Special:PrefixIndex/:Manila/}}

[[Category:Manila]]

Manila

2014-05-14T19:57:50Z

Bob Callaway: /* Meetings */

== Introduction ==
This page documents the concept and vision for establishing a shared file system service for OpenStack. The development name for this project is Manila. We propose and are in the process of implementing a new OpenStack service (originally based on Cinder). Cinder presently functions as the canonical storage provisioning control plane in [[OpenStack]] for block storage as well as delivering a persistence model for instance storage. The File Share Service prototype, in a similar manner, provides coordinated access to shared or distributed file systems. While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. The design and prototype implementation provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is intended to be sufficiently abstract to accommodate any of a variety of shared or distributed file system types. The team's intention is to introduce the capability as an OpenStack incubated project in the Juno timeframe, graduate it and submit for consideration as a core service as early as the as of yet unnamed "K" release.

[[File:Shares_Service.png]]

According to IDC in its “[http://www.idc.com/getdoc.jsp?containerId=235910 Worldwide File-Based Storage 2012-2016 Forecast]", file-based storage continues to be a thriving market, with spending on File-based storage solutions to reach north of $34.6 billion in 2016. Of the 27 Exabyte’s (EB) of total disk capacity estimated to have shipped in 2012, IDC projected that nearly 18 EB were file-based capacity, accounting for over 65% of all disk shipped by capacity. A diversity of applications, from server virtualization to relational or distributed databases to collaborative content creation, often depend on the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products. OpenStack, as the leading open IaaS capability, is increasingly contemplated as an option for deploying classic infrastructure in an "as a Service" model, but without specific accommodation for shared file systems represents an incomplete solution.

== Projects==

=== Manila ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/manila
|-
| Bug tracker
| https://bugs.launchpad.net/manila
|-
| Feature tracker
| https://blueprints.launchpad.net/manila
|}

=== Python Manila Client ===
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/python-manilaclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-manilaclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-manilaclient
|}

=== Meetings ===

[[Manila/Meetings|Project Agenda & Meetings]]
[[Manila/JunoSummitPresentation|Overview Presentation from Juno (Atlanta) Summit]]

=== Getting Started with Manila ===

Instructions for getting started with Manila using Devstack are available at: [[Manila/IcehouseDevstack|Manila on Devstack]]

Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]

=== Project Plan & Progress ===

[[Manila/ProjectPlan|Manila Project Plan]] 
Track progress towards [[Manila/Graduation|Manila Incubation & Graduation]].

== Design & Use Cases ==

[[Manila/design|Manila Component Design]] 
[[Manila/usecases|Manila Use Cases]]

== Subpages ==

{{Special:PrefixIndex/:Manila/}}

[[Category:Manila]]

Manila

2014-05-14T19:56:57Z

Bob Callaway: /* Getting Started with Manila */

== Introduction ==
This page documents the concept and vision for establishing a shared file system service for OpenStack. The development name for this project is Manila. We propose and are in the process of implementing a new OpenStack service (originally based on Cinder). Cinder presently functions as the canonical storage provisioning control plane in [[OpenStack]] for block storage as well as delivering a persistence model for instance storage. The File Share Service prototype, in a similar manner, provides coordinated access to shared or distributed file systems. While the primary consumption of file shares would be across OpenStack Compute instances, the service is also intended to be accessible as an independent capability in line with the modular design established by other OpenStack services. The design and prototype implementation provide extensibility for multiple backends (to support vendor or file system specific nuances / capabilities) but is intended to be sufficiently abstract to accommodate any of a variety of shared or distributed file system types. The team's intention is to introduce the capability as an OpenStack incubated project in the Juno timeframe, graduate it and submit for consideration as a core service as early as the as of yet unnamed "K" release.

[[File:Shares_Service.png]]

According to IDC in its “[http://www.idc.com/getdoc.jsp?containerId=235910 Worldwide File-Based Storage 2012-2016 Forecast]", file-based storage continues to be a thriving market, with spending on File-based storage solutions to reach north of $34.6 billion in 2016. Of the 27 Exabyte’s (EB) of total disk capacity estimated to have shipped in 2012, IDC projected that nearly 18 EB were file-based capacity, accounting for over 65% of all disk shipped by capacity. A diversity of applications, from server virtualization to relational or distributed databases to collaborative content creation, often depend on the performance, scalability and simplicity of management associated with file-based systems, and the large ecosystem of supporting software products. OpenStack, as the leading open IaaS capability, is increasingly contemplated as an option for deploying classic infrastructure in an "as a Service" model, but without specific accommodation for shared file systems represents an incomplete solution.

== Projects==

=== Manila ===

{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/manila
|-
| Bug tracker
| https://bugs.launchpad.net/manila
|-
| Feature tracker
| https://blueprints.launchpad.net/manila
|}

=== Python Manila Client ===
{| border="1" cellpadding="2"
| Source code
| https://github.com/stackforge/python-manilaclient
|-
| Bug tracker
| https://bugs.launchpad.net/python-manilaclient
|-
| Feature tracker
| https://blueprints.launchpad.net/python-manilaclient
|}

=== Meetings ===

[[Manila/Meetings|Project Agenda & Meetings]]

=== Getting Started with Manila ===

Instructions for getting started with Manila using Devstack are available at: [[Manila/IcehouseDevstack|Manila on Devstack]]

Developer documentation is still in progress, but is available in a draft state: [[Manila/docs|Manila Documentation]]

=== Project Plan & Progress ===

[[Manila/ProjectPlan|Manila Project Plan]] 
Track progress towards [[Manila/Graduation|Manila Incubation & Graduation]].

== Design & Use Cases ==

[[Manila/design|Manila Component Design]] 
[[Manila/usecases|Manila Use Cases]]

== Subpages ==

{{Special:PrefixIndex/:Manila/}}

[[Category:Manila]]

Manila/IcehouseDevstack

2014-05-14T19:55:55Z

Bob Callaway:

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

1. Clone devstack

$ git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git

2. Clone manila

$ git clone https://github.com/openstack-dev/devstack.git

3. Copy over the devstack files from the manila repo into the devstack repo

$ cp manila/contrib/devstack/lib/manila devstack/lib/
$ cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/

4. Copy the sample local.conf into the root devstack directory

$ cd devstack; cp samples/local.conf .

5. Edit/append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
$ cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
#FLOATING_RANGE=192.168.33.128/28
#FLAT_INTERFACE=eth1
#PUBLIC_INTERFACE=eth1
#HOST_IP=192.168.33.10

EOF

6. Run stack.sh as normal; When it is complete, the manila processes should be started, and the horizon extensions for Manila should be present.

7. There is a current defect (https://bugs.launchpad.net/bugs/1314591) that may require you to set the security group rules for the service tenant; this can be achieved by running the following commands:
$ . openrc manila service
nova secgroup-add-rule default tcp 1 65535 0.0.0.0/0
nova secgroup-add-rule default udp 1 65535 0.0.0.0/0
nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0

===== Vagrant File =====

If you use Vagrant, here is a Vagrantfile that I have used successfully with the above process:

$ VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "precise64"

config.vm.network :private_network, ip: "192.168.33.10"

config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", "2048"]
end

config.vm.provision :shell, :inline => "sudo apt-get upgrade -y && sudo apt-get install -y git vim libxslt1-dev libmysqlclient-dev"
end

Manila/IcehouseDevstack

2014-05-14T19:54:43Z

Bob Callaway:

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

1. Clone devstack

$ git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git

2. Clone manila

$ git clone https://github.com/openstack-dev/devstack.git

3. Copy over the devstack files from the manila repo into the devstack repo

$ cp manila/contrib/devstack/lib/manila devstack/lib/
$ cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/

4. Copy the sample local.conf into the root devstack directory

$ cd devstack; cp samples/local.conf .

5. Edit/append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
$ cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
#FLOATING_RANGE=192.168.33.128/28
#FLAT_INTERFACE=eth1
#PUBLIC_INTERFACE=eth1
#HOST_IP=192.168.33.10

EOF

6. Run stack.sh as normal; When it is complete, the manila processes should be started, and the horizon extensions for Manila should be present.

7. There is a current defect that may require you to set the security group rules for the service tenant; this can be achieved by running the following commands:
$ . openrc manila service
nova secgroup-add-rule default tcp 1 65535 0.0.0.0/0
nova secgroup-add-rule default udp 1 65535 0.0.0.0/0
nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0

===== Vagrant File =====

If you use Vagrant, here is a Vagrantfile that I have used successfully with the above process:

$ VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "precise64"

config.vm.network :private_network, ip: "192.168.33.10"

config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", "2048"]
end

config.vm.provision :shell, :inline => "sudo apt-get upgrade -y && sudo apt-get install -y git vim libxslt1-dev libmysqlclient-dev"
end

Manila/IcehouseDevstack

2014-05-14T13:01:42Z

Bob Callaway:

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

1. Clone devstack

$ git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git

2. Clone manila

$ git clone https://github.com/openstack-dev/devstack.git

3. Copy over the devstack files from the manila repo into the devstack repo

$ cp manila/contrib/devstack/lib/manila devstack/lib/
$ cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/

4. Copy the sample local.conf into the root devstack directory

$ cd devstack; cp samples/local.conf .

5. Edit/append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
$ cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
#FLOATING_RANGE=192.168.33.128/28
#FLAT_INTERFACE=eth1
#PUBLIC_INTERFACE=eth1
#HOST_IP=192.168.33.10

EOF

6. Run stack.sh as normal; When it is complete, the manila processes should be started, and the horizon extensions for Manila should be present.

===== Vagrant File =====

If you use Vagrant, here is a Vagrantfile that I have used successfully with the above process:

$ VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "precise64"

config.vm.network :private_network, ip: "192.168.33.10"

config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", "2048"]
end

config.vm.provision :shell, :inline => "sudo apt-get upgrade -y && sudo apt-get install -y git vim libxslt1-dev libmysqlclient-dev"
end

Manila/IcehouseDevstack

2014-05-14T12:57:33Z

Bob Callaway:

Manila/IcehouseDevstack

2014-05-13T21:40:59Z

Bob Callaway:

Manila/IcehouseDevstack

2014-05-13T21:39:06Z

Bob Callaway:

Manila/IcehouseDevstack

2014-05-13T21:37:06Z

Bob Callaway:

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

# Clone devstack
$ git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git
# Clone manila
$ git clone https://github.com/openstack-dev/devstack.git
# Copy over the devstack files
$ cp manila/contrib/devstack/lib/manila devstack/lib/
$ cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/
# Copy the sample local.conf into the root devstack directory
$ cd devstack; cp samples/local.conf .
# Append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
$ cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
\#FLOATING_RANGE=192.168.33.128/28
\#FLAT_INTERFACE=eth1
\#PUBLIC_INTERFACE=eth1
\#HOST_IP=192.168.33.20

EOF

#

Manila/IcehouseDevstack

2014-05-13T21:35:34Z

Bob Callaway: Created page with "Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila. # Clone devstack (git clone -b stable/icehouse https://github.com/opensta..."

Here are instructions on how to use Devstack with the latest code from Manila to begin using Manila.

# Clone devstack (git clone -b stable/icehouse https://github.com/openstack-dev/devstack.git)
# Clone manila (git clone https://github.com/openstack-dev/devstack.git)
# Copy over the devstack files
## cp manila/contrib/devstack/lib/manila devstack/lib/
## cp manila/contrib/devstack/extras.d/70-manila.sh devstack/extras.d/
# Copy the sample local.conf into the root devstack directory
## cd devstack; cp samples/local.conf .
# Append local.conf to enable manila, neutron, and change the horizon repository and branch to the Manila-specific fork; you may want to uncomment the last four lines depending on your networking configuration
cat <<EOF >> local.conf
enable_service manila,m-api,m-sch,m-shr

HORIZON_REPO=https://github.com/NetApp/horizon.git
HORIZON_BRANCH=manila

disable_service n-net
enable_service q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron
Q_PLUGIN=ml2
ENABLE_TENANT_VLANS=True
ML2_VLAN_RANGES=physnet1:100:200
PHYSICAL_NETWORK=physnet1
OVS_PHYSICAL_BRIDGE=br-eth1
Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch
Q_ML2_PLUGIN_TYPE_DRIVERS=vlan
SHARE_BACKING_FILE_SIZE=8G
\#FLOATING_RANGE=192.168.33.128/28
\#FLAT_INTERFACE=eth1
\#PUBLIC_INTERFACE=eth1
\#HOST_IP=192.168.33.20

EOF

#