Changed EC backend from jerasure to liberasurecode in examples and docs

liberasurecode_rs_vand is build-in liberasurecode, so you don't need
another depedency libjerasure2.

liberasurecode_rs_vand is supported by pyeclib from 1.0.8
version, so bumping version up.

Closes-Bug: #1534325
Change-Id: If2d96875694df8fd48c5278395859aaa165cb566

doc/saio/swift/swift.conf

@@ -15,6 +15,6 @@ policy_type = replication
 [storage-policy:2]
 name = ec42
 policy_type = erasure_coding
-ec_type = jerasure_rs_vand
+ec_type = liberasurecode_rs_vand
 ec_num_data_fragments = 4
 ec_num_parity_fragments = 2

doc/source/overview_erasure_code.rst

@@ -204,7 +204,7 @@ an EC policy can be setup is shown below::
         [storage-policy:2]
         name = ec104
         policy_type = erasure_coding
-        ec_type = jerasure_rs_vand
+        ec_type = liberasurecode_rs_vand
         ec_num_data_fragments = 10
         ec_num_parity_fragments = 4
         ec_object_segment_size = 1048576

etc/swift.conf-sample

@@ -73,13 +73,14 @@ aliases = yellow, orange
 # The example 'deepfreeze10-4' policy defined below is a _sample_
 # configuration with an alias of 'df10-4' as well as 10 'data' and 4 'parity'
 # fragments. 'ec_type' defines the Erasure Coding scheme.
-# 'jerasure_rs_vand' (Reed-Solomon Vandermonde) is used as an example below.
+# 'liberasurecode_rs_vand' (Reed-Solomon Vandermonde) is used as an example
+# below.
 #
 #[storage-policy:2]
 #name = deepfreeze10-4
 #aliases = df10-4
 #policy_type = erasure_coding
-#ec_type = jerasure_rs_vand
+#ec_type = liberasurecode_rs_vand
 #ec_num_data_fragments = 10
 #ec_num_parity_fragments = 4
 #ec_object_segment_size = 1048576

requirements.txt

@@ -10,4 +10,4 @@ netifaces>=0.5,!=0.10.0,!=0.10.1
 pastedeploy>=1.3.3
 six>=1.9.0
 xattr>=0.4
-PyECLib>=1.0.7                          # BSD
+PyECLib>=1.0.8                          # BSD