<div dir="ltr"><div dir="ltr">Thanks for posting here Amye! Will try to answer these questions inline, and for missing ones, will get back soon.<div><br></div><div>Sorry about missing this meeting, the evenings in these months are bit blocked :-/</div><div><br></div><div>-</div><div><br></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Dec 5, 2018 at 8:51 PM Amye Scavarda <<a href="mailto:amye@redhat.com">amye@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"><div dir="ltr">So the agenda for today's meeting has some questions, but unfortunately, we don't have the maintainers group online to be able to assist.</div><div dir="ltr">Here's what's come up: </div><div dir="ltr"><br><div><div>- gluster-prometheus-exporter: the git tag still refer to 0.3dev, when a final first release would be available? what are the targeted components metrics of such release and next?</div><div>- gluster-block: benchmark reporting: couldn't find anything online, what expectations should we have?</div></div></div></div></blockquote><div><br></div><div>Depends on work-load. We recommend it for more of transaction workload, like DB, or jenkins etc. </div><div> </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"><div dir="ltr"><div><div>- glusterd2: any timeline of when would be production ready?</div></div></div></div></blockquote><div><br></div><div>We are focusing on getting it used as a default project in container workload. So, it wouldn't be a replacement for GD1 yet. Once it works smoothly in that work load, we will get it into default gluster stack. Please refer to <a href="https://github.com/gluster/gcs">https://github.com/gluster/gcs</a> for the progress on this effort.</div><div><br></div><div>We are seeing how to provide 'thin-arbiter' feature we got into filesystem side in the releases. Will keep the users list informed about it. We should have something for users by glusterfs-6.0 timeframe (which is next release).</div><div><br></div><div> </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"><div dir="ltr"><div><div>- glusterfs: running glusterfs on high spec HW is it a waste of resources or there are plans for optimizations? NVDIM support? NVME drives etc</div></div></div></div></blockquote><div><br></div><div>Currently, we are trying to stabilize the current codebase. The optimizations would follow later. We are happy to get help here. Both in terms of code, and guidance (through github issues).</div><div> </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"><div dir="ltr"><div><div>- georeplication: implementation and monitoring seems to be challenging what is the vision?</div></div></div></div></blockquote><div><br></div><div>gluster-ansible project already has supports for automated geo-replication management. Can that be tried? We are planning to integrate more of monitoring with gluster-prometheus later.</div><div><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"><div dir="ltr"><div><div>- heketi coming up features?</div></div><div><br></div></div></div></blockquote><div> </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"><div dir="ltr"><div></div><div>Putting this on the mailing list for larger visibility. </div><div>- amye </div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 4, 2018 at 10:39 AM Amye Scavarda <<a href="mailto:amye@redhat.com" target="_blank">amye@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"><div dir="ltr"><a href="https://bit.ly/gluster-community-meetings" target="_blank">https://bit.ly/gluster-community-meetings</a> has an agenda, but should we postpone these to January? </div><div dir="ltr"><br></div><div dir="ltr">If we were to replace the Community Meetings with a video call to present current work, would that be more effective? Would you rather just do office hours for a particular feature? </div><div dir="ltr"><br></div><div dir="ltr">Drop a note on list for what you'd like to see happen with the community meetings, overall Gluster community. :D </div><div dir="ltr"><br></div><div dir="ltr">- amye </div><div dir="ltr"><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-2129041046630965732m_-198699492443460236gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-2129041046630965732gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div></div></div>