[automated-testing] Supporting GD2 & GD1 in glusto-tests

Jonathan Holloway jholloway at redhat.com
Tue Aug 7 14:52:16 UTC 2018


Is there a specific way you had in mind to implement the GCS version of the
glustolibs namespace package?
Do we maintain a separate branch for now and then when we have everything
in the branch working for both GCS and non-GCS swap it to master?
What will that mixed architecture look like? Config setting to enable GCS
or non-GCS and the logic in the libraries? Class-based?
Or are we maintaining both separately for the long-term?


On Tue, Aug 7, 2018 at 1:51 AM Nigel Babu <nigelb at redhat.com> wrote:

> Hello,
> Is there a POC that you can show yet? This is the second blocker to test
> GCS. The other one is a glusto[1] bug.
> [1]: https://github.com/loadtheaccumulator/glusto/issues/17
> On Thu, Jul 26, 2018 at 7:38 PM Nigel Babu <nigelb at redhat.com> wrote:
>> My primary concern here is that this may not work like you think it will.
>> We may want to test this idea for it's limitations and problems before we
>> decide.
>> On Thu, Jul 26, 2018 at 7:35 PM Nigel Babu <nigelb at redhat.com> wrote:
>>> Do you have a PoC that we can play with some time next week?
> --
> nigelb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20180807/cb80c2f2/attachment.html>

More information about the automated-testing mailing list