What would the cli command look like for integrating custom xlator?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The cli has been great for adding the necessary management tools,but if you want to use custom translators, you're back to writing vol files and losing your ability to do online volume changes. This ability needs to be added in order for custom translators to become viable. 

What would the cli command look like for integrating custom xlator? 

I can picture a couple ways, one of which would be that xlators would list requirements and providers so the volgen would be able to intuit a valid graph if that xlator is enabled for the volume. The cli would provide command hooks for any new features that xlator would need to add to the cli.

The gluster command should have a switch option listing the supported mount options in case a xlator provides new ones (would be parsed by mount.glusterfs). 

Anybody else have a view?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130122/6f01c663/attachment-0001.html>


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux