<div dir="ltr">Sounds good. My comments are inline.<br><div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Aug 8, 2018 at 1:49 AM Nigel Babu <<a href="mailto:nigelb@redhat.com">nigelb@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I had a chat with Vijay and Akarsha yesterday. Here's a summary of what we decided.</div><div><br></div><div>* We want to have two versions of the glustolibs-gluster library.</div><div>* We will create a new repo called glusto-libs. Nigel will create this repo. To start off, we'll copy the content from glustolibs-gluster to this repo.</div></div></blockquote><div><br></div><div>Both the GCS and non-GCS namespace packages will be located in the new glusto-libs library, right?</div><div>Essentially going back to what we discussed way back about maintaining the two separate repos for tests and libs.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>* Akarsha will land changes to this library to support GD2. Vijay and Akarsha will take responsibility for keeping them in sync in terms of features that apply in both places.</div><div>* Given that moving the current version which supports 3.x to this repo will break a bunch of automation both upstream and downstream, we will defer it to the future. However, this is the end goal.<br></div></div></blockquote><div><br></div><div>I think this answers my above question, but wanted to be sure.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>* Akarsha will look at marking tests that are relevant for GD2 in the existing tests so we can have a glusterfs + GD2 sanity test (before going to the container layer).</div></div></blockquote><div><br></div><div>Will that be done via pytest markers and run via the py.test -m <marker_name>?</div><div><br></div><div>Cheers,</div><div>Jonathan<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 7, 2018 at 8:22 PM Jonathan Holloway <<a href="mailto:jholloway@redhat.com" target="_blank">jholloway@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Vijay,</div><div><br></div><div>Is there a specific way you had in mind to implement the GCS version of the glustolibs namespace package?<br></div><div>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?<br></div><div>What will that mixed architecture look like? Config setting to enable GCS or non-GCS and the logic in the libraries? Class-based?</div><div>Or are we maintaining both separately for the long-term?<br></div><div><br></div><div>Cheers,</div><div>Jonathan<br></div><br></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 7, 2018 at 1:51 AM Nigel Babu <<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello,</div><div><br></div><div>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.</div><div><br></div><div>[1]: <a href="https://github.com/loadtheaccumulator/glusto/issues/17" target="_blank">https://github.com/loadtheaccumulator/glusto/issues/17</a><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 26, 2018 at 7:38 PM Nigel Babu <<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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.<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 26, 2018 at 7:35 PM Nigel Babu <<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Do you have a PoC that we can play with some time next week?</div></blockquote></div><br></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="m_-6824012449009086886m_5290186627934501670m_1281298019344496525m_5030126779116539152gmail_signature"><div dir="ltr">nigelb<br></div></div></div></div>
</blockquote></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="m_-6824012449009086886m_5290186627934501670gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</blockquote></div></div></div></div>