Funs Kessen 3 years ago
parent
commit
662ad31b55
1 changed files with 26 additions and 23 deletions
  1. 26
    23
      README.md

+ 26
- 23
README.md View File

@@ -1,8 +1,6 @@
1
-fuel-plugin-datera-cinder
2
-=========================
1
+# fuel-plugin-datera-cinder
3 2
 
4
-Plugin description
5
--------------------
3
+## Plugin description
6 4
 
7 5
 Datera plugin for Fuel extends Mirantis OpenStack functionality by
8 6
 adding support for Datera Elastic Data Fabric.
@@ -10,47 +8,52 @@ adding support for Datera Elastic Data Fabric.
10 8
 The Datera EDF is an fast, policy based, management lights out, 
11 9
 iSCSI block storage device that can be used as a Cinder backend.
12 10
 
13
-Requirements
14
-------------
11
+## Requirements
15 12
 
16
-| Requirement                                          | Version/Comment |
17
-|------------------------------------------------------|-----------------|
18
-| Mirantis OpenStack compatibility                     | >= 7.0          |
19
-| Access to Datera via ccinder-volume node             |                 |
20
-| iSCSI initiator on all compute/cinder-volume nodes   |                 |
13
+```
14
+Requirement                                          | Version/Comment
15
+---------------------------------------------------- | ---------------
16
+Mirantis OpenStack compatibility                     | >= 7.0         
17
+Access to Datera via ccinder-volume node             |                
18
+iSCSI initiator on all compute/cinder-volume nodes   |                
19
+```
21 20
 
22
-Limitations
23
------------
21
+## Limitations
24 22
 
25 23
 Mirantis Openstack 7.0 does not support multiple backends.
26 24
 
27
-Datera configuration
28
----------------------
25
+## Datera configuration
29 26
 
30 27
 Before deployment the following needs to be verified:
31 28
 1. Your Datera Cluster is reachable by all compute nodes, as well as the Cinder Control/Manager node.  
32 29
 2. Create an Openstack account on the Datera cluster that can create volumes. (san_login/password).
33 30
 3. Use the Management VIP address for the Datera cluster. (as the san_ip)`
34 31
 
35
-Datera Cinder plugin installation
36
----------------------------------
32
+## Datera Cinder plugin installation
37 33
 
38 34
 Grab the RPM, upload it to the Fuel master server and run:
39
-```fuel plugins --install <rpm> ```
35
+```
36
+fuel plugins --install <rpm>
37
+```
40 38
 
41 39
 Building the plugin from scratch:
42
-```yum install python-pip createrepo dpkg-devel dpkg-dev rpm rpm-build ```
40
+```
41
+yum install python-pip createrepo dpkg-devel dpkg-dev rpm rpm-build
42
+```
43 43
 or
44
-```pip install fuel-plugin-builder ```
44
+```
45
+pip install fuel-plugin-builder
46
+```
45 47
 
46
-```git clone https://github.com/snuf/fuel-plugin-datera-cinder
48
+```
49
+git clone https://github.com/snuf/fuel-plugin-datera-cinder
47 50
 fpb --build fuel-plugin-datera-cinder
48 51
 scp <rpm> <fuel master node>
49 52
 fuel plugins --install <rpm>
50 53
 ```
51 54
 
52
-Datera plugin configuration
53
-----------------------------
55
+## Datera plugin configuration
56
+
54 57
 For Fuel 7.0 the plugin is under the settings tab. In Fuel 8.0 this has however moved to the Settings->Storage tab.
55 58
 
56 59
 Enabling the driver is done by ticking the box at the top of the configuration fields for the driver. The previously mentioned san_login, san_password and san_ip are used in their respective fields. Take not of the replica count field, which dictates the amount of copies that will be held in the EDF for all Mirantis Fuel Openstack created volumes

Loading…
Cancel
Save