x
/
fuel-plugin-scaleio-cinder
Code Issues Proposed changes

Fix rst format 

Change-Id: Ia04ac0dfc31b76e33d08f80af4c22b132d74a3f1
This commit is contained in:
msalem2 2015-10-27 14:03:06 +09:00
parent e5fa7fb70c
commit 1ffd80812d
3 changed files with 218 additions and 133 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

68
doc/content/installation.rst
View File

@ -3,7 +3,7 @@ ScaleIO Cinder plugin installation
===========================================================
The first step is to install the ScaleIO Cinder plugin in the Fuel Master:
1. Download the plugin from the [releases section](https://github.com/openstack/fuel-plugin-scaleio-cinder/releases "Releases Page") or from the [Fuel plugins catalog](https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/ "Fuel Plugins Catalog").
1. Download the plugin from the https://github.com/openstack/fuel-plugin-scaleio-cinder/releases "Releases Page" or from the https://www.mirantis.com/products/openstack-drivers-and-plugins/fuel-plugins/ "Fuel Plugins Catalog".
2. Copy the plugin to an already installed Fuel Master node. If you do not have the Fuel Master node yet, follow the instructions from the official Mirantis OpenStack documentation:
@ -17,7 +17,7 @@ The first step is to install the ScaleIO Cinder plugin in the Fuel Master:
4. Verify that the plugin has been installed successfully:
![Plugin Installation](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-1.png)
..image::https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-1.png
===========================================================
@ -26,51 +26,61 @@ ScaleIO Cinder plugin configuration
Once the plugin has been installed in the Master, we configure the nodes and set the parameters for the plugin:
1. Start by creating a new OpenStack environment following the [Mirantis instructions](https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#create-a-new-openstack-environment "Creating a new OpenStack environment")
1. Start by creating a new OpenStack environment following the https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#create-a-new-openstack-environment "Creating a new OpenStack environment")
2. Configure your environment following the [Mirantis OpenStack configuration documentation](https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#configure-your-environment)
2. Configure your environment following the https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#configure-your-environment
![OpenStack Node configuration](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-2.png)
..image::https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-2.png
3. Open the **Settings tab** of the Fuel web UI and scroll down the page. Select the Fuel plugin check-box to enable ScaleIO Cinder plugin for Fuel:
![ScaleIO Cluster Parameters](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-4.PNG)
..image::https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-4.PNG
**Plugin's parameters explanation:**
|Parameter Name |Parameter Description|
|---------------------|---------------------|
|ScaleIO Repo URL| The URL of the ScaleIO sources repository. This is the URL for the required scaleIO zip file that contains the ScaleIO product. **The URL can point to an external repository (requires external network access to that repository) or to an internal server in the local network (a local webserver)**. For our example we are using the URI for the [ScaleIO Linux download](http://downloads.emc.com/emc-com/usa/ScaleIO/ScaleIO_Linux_SW_Download.zip "ScaleIO Linux Download") located in the ScaleIO trial download at [EMC.com](http://www.emc.com/products-solutions/trial-software-download/scaleio.htm "ScaleIO Trial Download"). |
|userName|The ScaleIO User Name|
|Password|The SclaeIO password for the selected user name|
|ScaleIO GW IP|The IP address of the the ScaleIO Gateway service|
|ScaleIO Primary IP|The ScaleIO cluster's primary IP address|
|ScaleIO Secondary IP|The ScaleIO cluster's secondary IP address|
|ScaleIO protection domain|Name of the ScaleIO's protection domain|
|ScaleIO storage pool 1|Name of the first storage pool|
|Fault sets list|List of the fault sets (comma separated)|
+-------------------------+---------------------------------------------------------+
|Parameter Name |Parameter Description |
+=========================+=========================================================+
|userName |The ScaleIO User Name |
+-------------------------+---------------------------------------------------------+
|Password |The SclaeIO password for the selected user name |
+-------------------------+---------------------------------------------------------+
|ScaleIO GW IP |The IP address of the the ScaleIO Gateway service |
+-------------------------+---------------------------------------------------------+
|ScaleIO Primary IP |The ScaleIO cluster's primary IP address |
+-------------------------+---------------------------------------------------------+
|ScaleIO Secondary IP |The ScaleIO cluster's secondary IP address |
+-------------------------+---------------------------------------------------------+
|ScaleIO protection domain|Name of the ScaleIO's protection domain |
+-------------------------+---------------------------------------------------------+
|ScaleIO storage pool 1 |Name of the first storage pool |
+-------------------------+---------------------------------------------------------+
**Note:** Please refer to the ScaleIO documentation for more information on these parameters
This is an example of the ScaleIO configuration paremets populated:
![ScaleIO Cluster Parameters](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-5.PNG)
..image::https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-5.PNG
4. After the configuration is done, you can Add the nodes to the Openstack Deployment. There is a minimum of two nodes for this configuration:
+-------------------------+----------------------------------------------------------------------------------------------+
|Service/Role Name | Description |
+=========================+==============================================================================================+
|Controller Node |A node that runs network, volume, API, scheduler, and image services. Each service may be |
|+ Cinder Host |broken out into separate nodes for scalability or availability. |
| |In addition this node is a Cinder Host, that contains the Cinder Volume Manager |
+-------------------------+----------------------------------------------------------------------------------------------+
|Compute Node |A node that runs the nova-compute daemon that manages Virtual Machines (VMs) instances that |
| |provide a wide range of services, such as web applications and analytics. |
+-------------------------+----------------------------------------------------------------------------------------------+
..image::https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-3.PNG
Service/Role Name | Description |
|------------|-------------|
|Controller Node + Cinder Host |A node that runs network, volume, API, scheduler, and image services. Each service may be broken out into separate nodes for scalability or availability. In addition this node is a Cinder Host, that contains the Cinder Volume Manager|
|Compute Node |A node that runs the nova-compute daemon that manages Virtual Machines (VMs) instances that provide a wide range of services, such as web applications and analytics.|
![OpenStack Node Deployment](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-3.PNG)
**Note:** you can run the [network verification](https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#verify-networks) check and [deploy the environment](https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#deploy-changes).
**Note:** you can run the
..image::https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#verify-networks
check and https://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#deploy-changes.
After this is complete you should see a success message:
![OpenStack Deployment Successful](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-complete.jpg)
..image::https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-complete.jpg
**Note:** It make take an hour or more for the OpenStack deployment to complete, depending on your hardware configuration.

153
doc/content/introduction.rst
View File

@ -1,84 +1,123 @@
===========================================================
Introduction
===========================================================
Fuel plugin for ScaleIO for enabling OpenStack to work with an **External** ScaleIO deployment. This ScaleIO plugin for Fuel extends Mirantis OpenStack functionality by adding support for ScaleIO block storage.
=========================================================== Introduction
=========================================================== Fuel plugin
for ScaleIO for enabling OpenStack to work with an **External** ScaleIO
deployment. This ScaleIO plugin for Fuel extends Mirantis OpenStack
functionality by adding support for ScaleIO block storage.
ScaleIO is a software-only solution that uses existing servers' local disks and LAN to create a virtual SAN that has all the benefits of external storage—but at a fraction of cost and complexity. ScaleIO utilizes the existing local internal storage and turns it into internal shared block storage.
ScaleIO is a software-only solution that uses existing servers' local
disks and LAN to create a virtual SAN that has all the benefits of
external storage—but at a fraction of cost and complexity. ScaleIO
utilizes the existing local internal storage and turns it into internal
shared block storage.
The following diagram shows the plugin's high level architecture:
The following diagram shows the plugin's high level architecture:
![ScaleIO Fuel plugin high level architecture](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/fuel-plugin-scaleio-cinder-1.jpg)
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/fuel-plugin-scaleio-cinder-1.jpg
:alt: ScaleIO Fuel plugin high level architecture
ScaleIO Fuel plugin high level architecture
From the figure we can see that we need the following OpenStack roles and services:
From the figure we can see that we need the following OpenStack roles
and services:
+---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| Service/Role Name | Description | Installed in |
+=================================+=============================================================================================================================================================================================================================================+=====================+
| Controller Node + Cinder Host | A node that runs network, volume, API, scheduler, and image services. Each service may be broken out into separate nodes for scalability or availability. In addition this node is a Cinder Host, that contains the Cinder Volume Manager | OpenStack Cluster |
+---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| Compute Node | A node that runs the nova-compute daemon that manages Virtual Machine (VM) instances that provide a wide range of services, such as web applications and analytics. | OpenStack Cluster |
+---------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
Service/Role Name | Description | Installed in |
|------------|-------------|--------------|
|Controller Node + Cinder Host |A node that runs network, volume, API, scheduler, and image services. Each service may be broken out into separate nodes for scalability or availability. In addition this node is a Cinder Host, that contains the Cinder Volume Manager|OpenStack Cluster|
|Compute Node |A node that runs the nova-compute daemon that manages Virtual Machine (VM) instances that provide a wide range of services, such as web applications and analytics.|OpenStack Cluster|
In the **external ScaleIO cluster** we have installed the following roles and services:
Service Name | Description | Installed in |
|------------|-------------|--------------|
|SclaeIO Gateway (REST API)|The ScaleIO Gateway Service, includes the REST API to communicate storage commands to the SclaeIO Cluster, in addtion this service is used for authentication and certificate management.|ScaleIO Cluster|
|Meta-data Manager (MDM)|Configures and monitors the ScaleIO system. The MDM can be configured in redundant Cluster Mode, with three members on three servers, or in Single Mode on a single server.|ScaleIO Cluster|
|Tie Breaker (TB)|Tie Breaker service helps determining what service runs as a master vs. a slave |ScaleIO Cluster|
|Storage Data Server (SDS)|Manages the capacity of a single server and acts as a back-end for data access.The SDS is installed on all servers contributing storage devices to the ScaleIO system. These devices are accessed through the SDS.|ScaleIO Cluster|
|Storage Data Client (SDC)|A lightweight device driver that exposes ScaleIO volumes as block devices to the application that resides on the same server on which the SDC is installed.|Openstack Cluster|
**Note:** for more information in how to deploy a ScaleIO Cluster, please refer to the ScaleIO manuals located in the download packages for your platform: [http://www.emc.com/products-solutions/trial-software-download/scaleio.htm](http://www.emc.com/products-solutions/trial-software-download/scaleio.htm "Download ScaleIO") and/or [watch the demo](https://community.emc.com/docs/DOC-45019 "Watch our demo to learn how to download, install, and configure ScaleIO")
In the **external ScaleIO cluster** we have installed the following
roles and services:
+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| Service Name | Description | Installed in |
+==============================+======================================================================================================================================================================================================================+=====================+
| SclaeIO Gateway (REST API) | The ScaleIO Gateway Service, includes the REST API to communicate storage commands to the SclaeIO Cluster, in addtion this service is used for authentication and certificate management. | ScaleIO Cluster |
+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| Meta-data Manager (MDM) | Configures and monitors the ScaleIO system. The MDM can be configured in redundant Cluster Mode, with three members on three servers, or in Single Mode on a single server. | ScaleIO Cluster |
+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| Tie Breaker (TB) | Tie Breaker service helps determining what service runs as a master vs. a slave | ScaleIO Cluster |
+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| Storage Data Server (SDS) | Manages the capacity of a single server and acts as a back-end for data access.The SDS is installed on all servers contributing storage devices to the ScaleIO system. These devices are accessed through the SDS. | ScaleIO Cluster |
+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| Storage Data Client (SDC) | A lightweight device driver that exposes ScaleIO volumes as block devices to the application that resides on the same server on which the SDC is installed. | Openstack Cluster |
+------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
**Note:** for more information in how to deploy a ScaleIO Cluster,
please refer to the ScaleIO manuals located in the download packages for
your platform:
http://www.emc.com/products-solutions/trial-software-download/scaleio.htm
and/or `watch the demo <https://community.emc.com/docs/DOC-45019>`__
Requirements
===========================================================
These are the plugin requirements:
============
These are the plugin requirements:
| Requirement | Version/Comment |
|----------------------------------------------------------|-----------------|
| Mirantis OpenStack compatibility | >= 6.1 |
| ScaleIO Version | >= 1.32 |
| Controller and Compute Nodes' Operative System | CentOS/RHEL 6.5 |
| OpenStack Cluster (Controller/cinder-volume node) can access ScaleIO Cluster | via a TCP/IP Network |
| OpenStack Cluster (Compute nodes) can access ScaleIO Cluster| via a TCP/IP Network |
| Install ScaleIO Storage Data Client (SDC) in Controller and Compute Nodes| Plugin takes care of install|
+--------------------------------------------------------------------------------+--------------------------------+
| Requirement | Version/Comment |
+================================================================================+================================+
| Mirantis OpenStack compatibility | >= 6.1 |
+--------------------------------------------------------------------------------+--------------------------------+
| ScaleIO Version | >= 1.32 |
+--------------------------------------------------------------------------------+--------------------------------+
| Controller and Compute Nodes' Operative System | CentOS/RHEL 6.5 |
+--------------------------------------------------------------------------------+--------------------------------+
| OpenStack Cluster (Controller/cinder-volume node) can access ScaleIO Cluster | via a TCP/IP Network |
+--------------------------------------------------------------------------------+--------------------------------+
| OpenStack Cluster (Compute nodes) can access ScaleIO Cluster | via a TCP/IP Network |
+--------------------------------------------------------------------------------+--------------------------------+
| Install ScaleIO Storage Data Client (SDC) in Controller and Compute Nodes | Plugin takes care of install |
+--------------------------------------------------------------------------------+--------------------------------+
Limitations
===========================================================
===========
Currently Fuel doesn't support multi-backend storage.
Configuration
===========================================================
=============
Plugin files and directories:
|File/Directory|Description|
|--------------|-----------|
|Deployment_scripts| Folder that includes the bash/puppet manifests for deploying the services and roles required by the plugin|
|Deployment_scripts/puppet||
|environment_config.yaml|Contains the ScaleIO plugin parameters/fields for the Fuel web UI|
|metadata.yaml|Contains the name, version and compatibility information for the ScaleIO plugin|
|pre_build_hook|Mandatory file - blank for the ScaleIO plugin|
|repositories/centos|Empty Directory, the plugin scripts will download the required CentOS packages|
|repositories/Ubuntu|Empty Directory, not used|
|taks.yaml|Contains the information about what scripts to run and how to run them|
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| File/Directory | Description |
+==============================+==============================================================================================================+
| Deployment\_scripts | Folder that includes the bash/puppet manifests for deploying the services and roles required by the plugin |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| Deployment\_scripts/puppet | |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| environment\_config.yaml | Contains the ScaleIO plugin parameters/fields for the Fuel web UI |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| metadata.yaml | Contains the name, version and compatibility information for the ScaleIO plugin |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| pre\_build\_hook | Mandatory file - blank for the ScaleIO plugin |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| repositories/centos | Empty Directory, the plugin scripts will download the required CentOS packages |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| repositories/Ubuntu | Empty Directory, not used |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
| taks.yaml | Contains the information about what scripts to run and how to run them |
+------------------------------+--------------------------------------------------------------------------------------------------------------+
This Fuel plugin will install the ScaleIO Storage Data Client (SDC)
service on each Controller node and Compute node in the cluster. This is
necessary in order for the VMs in each compute node to utilize ScaleIO
Storage:
This Fuel plugin will install the ScaleIO Storage Data Client (SDC) service on each Controller node and Compute node in the cluster. This is necessary in order for the VMs in each compute node to utilize ScaleIO Storage:
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/fuel-plugin-scaleio-cinder-2.jpg
:alt: Plugin Architecture
![Plugin Architecture ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/fuel-plugin-scaleio-cinder-2.jpg)
Plugin Architecture
Before starting a deployment there are some things that you should
verify:
Before starting a deployment there are some things that you should verify:
1. Your ScaleIO Cluster can route 10G Storage Network to all Compute nodes
as well as the Cinder Control/Manager node.
2. Create an account on the ScaleIO cluster to use as the OpenStack Administrator
account (use the login/password for this account as san_login/password settings).
1. Your ScaleIO Cluster can route 10G Storage Network to all Compute
nodes as well as the Cinder Control/Manager node.
2. Create an account on the ScaleIO cluster to use as the OpenStack
Administrator account (use the login/password for this account as
san\_login/password settings).
3. Obtain the IP address from the ScaleIO cluster

130
doc/content/user-guide.rst
View File

@ -1,73 +1,109 @@
===========================================================
User Guide
===========================================================
1. Upload scaleio-cinder plugin code to the master node
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image001.png)
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image002.png) Build the code using fpb –build command
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image003.png)
=========================================================== User Guide
=========================================================== 1. Upload
scaleio-cinder plugin code to the master node |user guide1| |user
guide2| Build the code using fpb –build command |user guide3|
2. Install scaleio-cinder plugin using fuel plugins –install command
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image004.png)
2. Install scaleio-cinder plugin using fuel plugins –install command
|user guide4|
3. Ensure that plugin is installed successfully using cli
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image005.png)
4. Create environment with enabled plugin in fuel ui, lunch the fuel site and check setting section to make sure the Scaleio-Cinder section exists
3. Ensure that plugin is installed successfully using cli |user guide5|
4. Create environment with enabled plugin in fuel ui, lunch the fuel
site and check setting section to make sure the Scaleio-Cinder
section exists
5. Add 3 nodes with Controller role and 1 node with Compute and another role
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image006.png) Picture of the External ScaleIO Cluster Running
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image007.png) Retrive the external ScaleIO Cluster information. For our example these are the configuration settings:
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image008.png) Use the ScaleIO Cluster information to update the ScaleIO Plugin information
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image009.png)
5. Add 3 nodes with Controller role and 1 node with Compute and another
role |user guide6| Picture of the External ScaleIO Cluster Running
|user guide7| Retrive the external ScaleIO Cluster information. For
our example these are the configuration settings: |user guide8| Use
the ScaleIO Cluster information to update the ScaleIO Plugin
information |user guide9|
6. Apply network settings
6. Apply network settings
7. Use the networking settings that are appropriate for your environment. For our example we used the default settings provided by Fuel:
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image010.png)
7. Use the networking settings that are appropriate for your
environment. For our example we used the default settings provided
by Fuel: |user guide10|
8. Run network verification
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image011.png)
8. Run network verification |user guide11|
9. Deploy the cluster ![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image012.png)
10. Once the deployment finished successfully open Horizon Portal
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image013.png)
11. Check Storage tab under system information and make sure ScaleIO service is up and running
![user guide1 ](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image014.png)
9. Deploy the cluster |user guide12|
10. Once the deployment finished successfully open Horizon Portal |user
guide13|
11. Check Storage tab under system information and make sure ScaleIO
service is up and running |user guide14|
ScaleIO Cinder plugin OpenStack operations
==================================================================
==========================================
Once the OpenStack Cluster is setup, we can setup ScaleIO Volumes. This is an example in how to attach a Volume to a running VM:
Once the OpenStack Cluster is setup, we can setup ScaleIO Volumes. This
is an example in how to attach a Volume to a running VM:
1. Login into the OpenStack Cluster:
![OpenStack Login](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-6.PNG)
2. Review the Block storage services by navigating: Admin -> System -> System Information secction. You should see the ScaleIO Cinder Volume.
![Block Storage Services Verification](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-7.PNG)
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-6.PNG
:alt: OpenStack Login
3. Review the System Volumes by navigating to: Admin -> System -> Volumes. You should see the ScaleIO Volume Type:
OpenStack Login
![Volume Type Verification](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-8.PNG)
2. Review the Block storage services by navigating: Admin -> System ->
System Information secction. You should see the ScaleIO Cinder
Volume.
4. Create a new OpenStack Volume:
![Volume Creation](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-9.PNG)
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-7.PNG
:alt: Block Storage Services Verification
Block Storage Services Verification
3. Review the System Volumes by navigating to: Admin -> System ->
Volumes. You should see the ScaleIO Volume Type:
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-8.PNG
:alt: Volume Type Verification
Volume Type Verification
4. Create a new OpenStack Volume:
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-9.PNG
:alt: Volume Creation
Volume Creation
5. View the newly created Volume:
![Volume Listing](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-10.PNG)
6. In the ScaleIO Control Panel, you will see that no Volumes have been mapped yet:
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-10.PNG
:alt: Volume Listing
![ScaleIO UI No mapped Volumes](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-11.PNG)
Volume Listing
7. Once the Volume is attached to a VM, the ScaleIO UI will reflect the mapping:
6. In the ScaleIO Control Panel, you will see that no Volumes have been
mapped yet:
![ScaleIO UI Mapped Volume](https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-12.png)
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-11.PNG
:alt: ScaleIO UI No mapped Volumes
ScaleIO UI No mapped Volumes
7. Once the Volume is attached to a VM, the ScaleIO UI will reflect the
mapping:
.. figure:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/scaleio-cinder-install-12.png
:alt: ScaleIO UI Mapped Volume
ScaleIO UI Mapped Volume
.. |user guide1| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image001.png
.. |user guide2| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image002.png
.. |user guide3| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image003.png
.. |user guide4| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image004.png
.. |user guide5| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image005.png
.. |user guide6| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image006.png
.. |user guide7| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image007.png
.. |user guide8| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image008.png
.. |user guide9| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image009.png
.. |user guide10| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image010.png
.. |user guide11| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image011.png
.. |user guide12| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image012.png
.. |user guide13| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image013.png
.. |user guide14| image:: https://github.com/openstack/fuel-plugin-scaleio-cinder/blob/master/doc/images/installation/image014.png