Bug 1444460

Summary:	cns-deploy should take label as input
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Raghavendra Talur <rtalur>
Component:	cns-deploy-tool	Assignee:	Mohamed Ashiq <mliyazud>
Status:	CLOSED ERRATA	QA Contact:	Prasanth <pprakash>
Severity:	high	Docs Contact:
Priority:	high
Version:	cns-3.5	CC:	bmohanra, hchiramm, jarrpa, mliyazud, pprakash, rcyriac, rhs-bugs, shberry, vinug
Target Milestone:	---	Keywords:	ZStream
Target Release:	CNS 3.5 Async
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cns-deploy-4.0.0-16.el7rhgs	Doc Type:	Bug Fix
Doc Text:	If this bug requires documentation, please select an appropriate Doc Type value.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-27 10:03:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raghavendra Talur 2017-04-21 11:31:05 UTC

Description of problem:
To select gluster nodes, cns-deploy has a hard coded label. It should take labels as input.

Comment 5 Raghavendra Talur 2017-04-25 15:03:33 UTC

changed doc text, please check.

Comment 6 Prasanth 2017-04-26 11:52:38 UTC

Verified as fixed in cns-deploy-4.0.0-16.el7rhgs

###################
  --daemonset-label DAEMONSET_LABEL
              Controls the value of the label set on nodes which will host pods
              from the GlusterFS daemonset. This allows for multiple GlusterFS
              daemonsets to run in the same cluster. Default is 'glusterfs'.


[root@dhcp46-41 ~]# cns-deploy -g --daemonset-label cnsds1 -y -l /var/log/8-cns-deploy.log --verbose
Using OpenShift CLI.
NAME               STATUS    AGE
storage-project2   Active    28m
Using namespace "storage-project2".
Checking that heketi pod is not running ... 
Checking status of pods matching 'glusterfs=heketi-pod':
No resources found.
Timed out waiting for pods matching 'glusterfs=heketi-pod'.
OK
template "deploy-heketi" created
serviceaccount "heketi-service-account" created
template "heketi" created
template "glusterfs" created
role "edit" added: "system:serviceaccount:storage-project2:heketi-service-account"
Marking 'dhcp47-41.lab.eng.blr.redhat.com' as a GlusterFS node.
node "dhcp47-41.lab.eng.blr.redhat.com" labeled
Marking 'dhcp47-42.lab.eng.blr.redhat.com' as a GlusterFS node.
node "dhcp47-42.lab.eng.blr.redhat.com" labeled
Marking 'dhcp47-43.lab.eng.blr.redhat.com' as a GlusterFS node.
node "dhcp47-43.lab.eng.blr.redhat.com" labeled
Deploying GlusterFS pods.
daemonset "glusterfs" created
Waiting for GlusterFS pods to start ... 
Checking status of pods matching 'glusterfs-node=pod':
glusterfs-fv9r1   1/1       Running   0         2m
glusterfs-jsw1z   1/1       Running   0         2m
glusterfs-mxk98   1/1       Running   0         2m
OK
service "deploy-heketi" created
route "deploy-heketi" created
deploymentconfig "deploy-heketi" created
Waiting for deploy-heketi pod to start ... 
Checking status of pods matching 'glusterfs=heketi-pod':
deploy-heketi-1-qkhn7   1/1       Running   0         40s
OK
Determining heketi service URL ... OK
Creating cluster ... ID: b5f8ba3bbc9ac26197518febfabdba3a
Creating node dhcp47-41.lab.eng.blr.redhat.com ... ID: bf9dc40cc8d18dabdb3d0e86dff9ca01
Adding device /dev/sdd ... OK
Adding device /dev/sde ... OK
Adding device /dev/sdf ... OK
Creating node dhcp47-42.lab.eng.blr.redhat.com ... ID: e913f49e883afc796185c7355fa1d812
Adding device /dev/sdd ... OK
Adding device /dev/sde ... OK
Adding device /dev/sdf ... OK
Creating node dhcp47-43.lab.eng.blr.redhat.com ... ID: 467cbdfed026a766903c96a7958aef1e
Adding device /dev/sdd ... OK
Adding device /dev/sde ... OK
Adding device /dev/sdf ... OK
heketi topology loaded.
Saving heketi-storage.json
secret "heketi-storage-secret" created
endpoints "heketi-storage-endpoints" created
service "heketi-storage-endpoints" created
job "heketi-storage-copy-job" created

Checking status of pods matching 'job-name=heketi-storage-copy-job':
heketi-storage-copy-job-r6124   0/1       Completed   0         31s
deploymentconfig "deploy-heketi" deleted
route "deploy-heketi" deleted
service "deploy-heketi" deleted
job "heketi-storage-copy-job" deleted
pod "deploy-heketi-1-qkhn7" deleted
secret "heketi-storage-secret" deleted
service "heketi" created
route "heketi" created
deploymentconfig "heketi" created
Waiting for heketi pod to start ... 
Checking status of pods matching 'glusterfs=heketi-pod':
deploy-heketi-1-qkhn7   1/1       Terminating   0         4m
OK
Determining heketi service URL ... OK
heketi is now running.
Ready to create and provide GlusterFS volumes.

root@dhcp46-41 ~]# export HEKETI_CLI_SERVER=http://heketi-storage-project2.cloudapps.mystorage.com

[root@dhcp46-41 ~]# curl http://heketi-storage-project2.cloudapps.mystorage.com/hello
Hello from Heketi[root@dhcp46-41 ~]# 

[root@dhcp46-41 ~]# heketi-cli cluster list
Clusters:
b5f8ba3bbc9ac26197518febfabdba3a

[root@dhcp46-41 ~]# heketi-cli cluster info b5f8ba3bbc9ac26197518febfabdba3a
Cluster id: b5f8ba3bbc9ac26197518febfabdba3a
Nodes:
467cbdfed026a766903c96a7958aef1e
bf9dc40cc8d18dabdb3d0e86dff9ca01
e913f49e883afc796185c7355fa1d812
Volumes:
399f72e3c3f837c11e5f963c1d91de46

[root@dhcp46-41 ~]# heketi-cli volume list
Id:399f72e3c3f837c11e5f963c1d91de46    Cluster:b5f8ba3bbc9ac26197518febfabdba3a    Name:heketidbstorage


[root@dhcp46-41 ~]# heketi-cli volume info 399f72e3c3f837c11e5f963c1d91de46
Name: heketidbstorage
Size: 2
Volume Id: 399f72e3c3f837c11e5f963c1d91de46
Cluster Id: b5f8ba3bbc9ac26197518febfabdba3a
Mount: 10.70.47.41:heketidbstorage
Mount Options: backup-volfile-servers=10.70.47.42,10.70.47.43
Durability Type: replicate
Distributed+Replica: 3


[root@dhcp46-41 ~]# oc get pods
NAME              READY     STATUS    RESTARTS   AGE
glusterfs-fv9r1   1/1       Running   0          12m
glusterfs-jsw1z   1/1       Running   0          12m
glusterfs-mxk98   1/1       Running   0          12m
heketi-1-ltg6g    1/1       Running   0          4m


[root@dhcp46-41 ~]# oc get all
NAME        REVISION   DESIRED   CURRENT   TRIGGERED BY
dc/heketi   1          1         1         config

NAME          DESIRED   CURRENT   READY     AGE
rc/heketi-1   1         1         1         4m

NAME            HOST/PORT                                         PATH      SERVICES   PORT      TERMINATION   WILDCARD
routes/heketi   heketi-storage-project2.cloudapps.mystorage.com             heketi     <all>                   None

NAME                           CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
svc/heketi                     172.30.104.255   <none>        8080/TCP   4m
svc/heketi-storage-endpoints   172.30.109.22    <none>        1/TCP      5m

NAME                 READY     STATUS    RESTARTS   AGE
po/glusterfs-fv9r1   1/1       Running   0          12m
po/glusterfs-jsw1z   1/1       Running   0          12m
po/glusterfs-mxk98   1/1       Running   0          12m
po/heketi-1-ltg6g    1/1       Running   0          4m


[root@dhcp46-41 ~]# oc get ds
NAME        DESIRED   CURRENT   READY     NODE-SELECTOR        AGE
glusterfs   3         3         3         storagenode=cnsds1   12m


[root@dhcp46-41 ~]# oc get nodes --show-labels
NAME                               STATUS                     AGE       LABELS
dhcp46-35.lab.eng.blr.redhat.com   Ready                      2d        beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=dhcp46-35.lab.eng.blr.redhat.com,storagenode=glusterds2
dhcp46-36.lab.eng.blr.redhat.com   Ready                      2d        beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=dhcp46-36.lab.eng.blr.redhat.com,region=infra,storagenode=glusterds2
dhcp46-39.lab.eng.blr.redhat.com   Ready                      2d        beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=dhcp46-39.lab.eng.blr.redhat.com,region=infra,storagenode=glusterds2
dhcp46-41.lab.eng.blr.redhat.com   Ready,SchedulingDisabled   2d        beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=dhcp46-41.lab.eng.blr.redhat.com
dhcp47-41.lab.eng.blr.redhat.com   Ready                      45m       beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=dhcp47-41.lab.eng.blr.redhat.com,storagenode=cnsds1
dhcp47-42.lab.eng.blr.redhat.com   Ready                      45m       beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=dhcp47-42.lab.eng.blr.redhat.com,storagenode=cnsds1
dhcp47-43.lab.eng.blr.redhat.com   Ready                      45m       beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=dhcp47-43.lab.eng.blr.redhat.com,storagenode=cnsds1
###################

Comment 8 Humble Chirammal 2017-04-27 09:59:37 UTC

*** Bug 1428316 has been marked as a duplicate of this bug. ***

Comment 9 errata-xmlrpc 2017-04-27 10:03:37 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1172

Comment 10 vinutha 2018-12-06 19:46:31 UTC

Marking qe-test-coverage as - since the preferred mode of deployment is using ansible