[heketi-devel] are there any examples of running heketi as a pod in kubernetes with non-containerized gluster?
Scott Creeley
screeley at redhat.com
Thu Mar 9 16:18:54 UTC 2017
Hi All,
Are there any examples of running heketi as a pod in kubernetes with non-containerized gluster?
I was able to start heketi as a pod in kubernetes and start writing the heketi.db to my external gluster cluster (non-containerized) but it fails on loading the topology most likely due to failed ssh connection to the gluster cluster from my heketi pod. Missing a network piece I'm sure, but not sure what other logs to look at to help?
[root at ocpdev heketi]# oc logs deploy-heketi-1-sx1fw
Heketi 3.1.0
[heketi] INFO 2017/03/08 23:23:50 Loaded ssh executor
[heketi] WARNING 2017/03/08 23:23:53 Unable to open database. Retrying using read only mode
[heketi] INFO 2017/03/08 23:23:53 Loaded simple allocator
[heketi] INFO 2017/03/08 23:23:53 GlusterFS Application Loaded
Listening on port 8080
[negroni] Started GET /clusters
[negroni] Completed 200 OK in 250.381µs
[negroni] Started GET /clusters/d2ff22f516c76f9c3e2e60af0cd97dd2
[negroni] Completed 200 OK in 466.435µs
[negroni] Started GET /nodes/01aeeab788f5975d4c5d38a2b4f2c217
[negroni] Completed 200 OK in 534.738µs
[negroni] Started GET /clusters/d2ff22f516c76f9c3e2e60af0cd97dd2
[negroni] Completed 200 OK in 228.541µs
[negroni] Started POST /devices
[negroni] Completed 0 in 2.166515ms
[negroni] Started POST /nodes
[negroni] Completed 0 in 110.326µs
[root at ocpdev ~]# oc exec -ti deploy-heketi-1-sx1fw /bin/sh
sh-4.2$ heketi-cli --server http://localhost:8080 topology info
Cluster Id: d2ff22f516c76f9c3e2e60af0cd97dd2
Volumes:
Nodes:
Node Id: 01aeeab788f5975d4c5d38a2b4f2c217
State: online
Cluster Id: d2ff22f516c76f9c3e2e60af0cd97dd2
Zone: 1
Management Hostname: gluster25.rhs
Storage Hostname: 192.168.1.205
Devices:
thanks,
Scott
More information about the heketi-devel
mailing list