Currently, you can't use Heketi directly with GlusterD2. Heketi's internal health checks probe for a running glusterd. In addition, Heketi issues all gluster commands through the "gluster" command line command rather than gd2's "glustercli" command. There's an effort underway to add support for the gd2 api to Heketi rather than use the command line tools but no PR has been posted as of yet. Since you're interested in this topic, you may want to monitor the heketi repo [1] on github for when that work is posted. [1]: https://github.com/heketi/heketi/pulls On Thursday, August 16, 2018 11:34:20 AM EDT Davide Obbi wrote: > Hi, > > how do i tell heketi to use glusterd2 instead of glusterd? > > When i perform the topology load i get the following error: > Creating node gluster01 ... Unable to create node: New Node doesn't have > glusterd running > > this suggest that is looking for glusterd in fact if i switch to glusterd > it finds it. > in heketi.json i could not find any option to specify this > > thanks > Davide > -- _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
