Bug 1626518

+++ This bug was initially created as a clone of Bug #1626513 +++

Description of problem:
------------------------
If the 'disktype' is chosen as 'jbod' gdeploy should execute without 'diskcount' & 'stripesize'

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
gdeploy-2.0.2-27.el7rhgs

How reproducible:
-------------------
Always

Steps to Reproduce:
--------------------
1. Create a config file with 'disktype' as 'jbod' without 'diskcount' & 'stripesize'
2. Execute the config file with gdeploy

Actual results:
----------------
gdeploy fails and requires 'diskcount'

Expected results:
------------------
gdeploy should execute without 'diskcount' mentioned

--- Additional comment from SATHEESARAN on 2018-09-07 10:11:20 EDT ---

The problem here is while creating the filesystem gdeploy tries to do this:
mkfs.xfs -d <su,sw> /dev/mapper/vg-lv

So 'su' is the stripe-size (unit) and 'sw' is the stripe-width.

RHGS Admin guide - 21.2 point 2, clearly states for JBOD su, sw should be ignored. Gdeploy should follow that

--- Additional comment from SATHEESARAN on 2018-09-07 10:12:03 EDT ---

#gdeploy configuration generated by cockpit-gluster plugin
[hosts]
host1

[disktype]
jbod

[pv1]
action=create
devices=vdb
ignore_pv_errors=no

[vg1]
action=create
vgname=gluster_vg_vdb
pvname=vdb
ignore_vg_errors=no

[lv4]
action=create
lvname=gluster_lv_vmstore
ignore_lv_errors=no
vgname=gluster_vg_vdb
mount=/gluster_bricks/vmstore
size=10GB
lvtype=thick