gluster-one
gluster-one copied to clipboard
gluster
Gluster One -- An Opinionated Node Executor
- https://bugzilla.redhat.com/show_bug.cgi?id=1633090 - Input accepts invalid IP addresses, Needs to throwout errors
Currently we are not checking for duplicate hostnames when deploying through colonizer. we check if the host IPs are duplicates but not the hostnames. Hence the deployment proceeds with duplicate...
- RFE - Separate the runtime logging of the tool and the application logging of colonizer - Ability to run the colonizer in debug mode. - request vaguely originating from...
- RFE - Explore the possibility of integrating with the VDO project with glusterfs deployments for the NAS and media repository use cases.
In the case of standardized repeatable deployments, even the fields currently left to user input could be templated, allowing for an unattended installation. Modify the design of the OEMID files...
Current UI design forces the user to abort and start over if any input was made inaccurately. Change the design to allow re-entry of values for any field.
I think it would be beneficial to have the min/max number of nodes in a separate file, something like a recommendation with the best settings. I've put the new file...
When I tried to install the gluster nodes using gluster-colonizer, I got some issues with the discovery of the nodes. It was reporting that 2 nodes were found, then 1...
I thought that listing which volume type the flavour is using may be good during install.