Simplify Glusto-test setup and usage
Closed this issue · 2 comments
The setup and usage of Glusto-test are very not trivial - It's very hard to setup the framework on local machines and as a result a shared setup was created, however there are clear limitation for working with a shared setup.
As Gluster itself is extremely easy to deploy locally, there's no reason why the test framework deployment should be so complicated.
Ideally, The test framework should not perform validation of the configuration and instead pass the info to Gluster as-is and let Gluster try to operate in the provided environment. If it's successful, it means the config is valid, if it's unsuccessful, it means the configuration is wrong.
Efforts should be to modify the framework so setup and usage is no more complex than Gluster itself.
Thank you for your contributions.
Noticed that this issue is not having any activity in last 3 months! We are marking this issue as stale because it has not had any recent activity and we have decided not to fix it while triaging.
It will be closed in 14 days if no one responds with a comment here.
Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to reopen it.