<div><br><div class="gmail_quote"><div dir="auto">On Wed, 2 Aug 2017 at 18:41, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Aug 2, 2017 at 5:03 PM, Prashanth Pai <<a href="mailto:ppai@redhat.com" target="_blank">ppai@redhat.com</a>> wrote:<br>
> Hi all,<br>
><br>
> The ongoing work on glusterd2 necessitates following non-breaking and<br>
> non-exhaustive list of changes to glusterfs source code:<br>
><br>
> Port management<br>
> - Remove hard-coding of glusterd's port as 24007 in clients and elsewhere.<br>
> Glusterd2 can be configured to listen to clients on any port (still<br>
> defaults to<br>
> 24007 though)<br>
> - Let the bricks and daemons choose any available port and if needed report<br>
> the port used to glusterd during the "sign in" process. Prasanna has a<br>
> patch<br>
> to do this.<br>
> - Glusterd <--> brick (or any other local daemon) communication should<br>
> always happen over Unix Domain Socket. Currently glusterd and brick<br>
> process communicates over UDS and also port 24007. This will allow us<br>
> to set better authentication and rules for port 24007 as it shall only be<br>
> used<br>
> by clients.</blockquote><div dir="auto"><br></div><div dir="auto">We'll also need to account how brick multiplexing would work with this change.</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
><br>
> Changes to xlator options<br>
> - Xlator authors do not have to modify glusterd2 code to expose new xlator<br>
> options. IOW, glusterd2 will not contain the "glusterd_volopt_map" table.<br>
> Most of its fields will be moved to the xlator itself. Glusterd2 can load<br>
> xlator's shared object and read it's volume_options table. This also means<br>
> xlators have to adhere to some naming conventions for options.<br>
> - Add following additional fields (names are indicative) to volume_option_t:<br>
> - Tag: This is to enable users to list only options having a certain<br>
> tag.<br>
> IOW, it allows us to filter "volume set help" like output.<br>
> Example of tags: debug, perf, network etc.<br>
> - Opversion: The minimum (or a range) op-version required by the xlator.<br>
> - Configurable: A bool to indicate whether this option is<br>
> user-configurable.<br>
> This may also be clubbed with DOC/NO_DOC<br>
> functionality.<br>
> - Xlators like AFR, changelog require non-static information such as brick<br>
> path<br>
> to be present in it's options in the volfile. Currently, xlator authors<br>
> have<br>
> to modify glusterd code to get it.<br>
> This can rather be indicated by the xlator itself using<br>
> templates/placehoders.<br>
> For example, "changelog-dir" can be set in xlator's option as as<br>
> <<brick-path>>/.glusterfs/changelogs and then glusterd2 will ensure to<br>
> replace<br>
> <<brick-path>> with actual path during volfile generation.<br>
<br>
One more change in this regard would be that xlators would now need to<br>
ensure that all options have default values. There are cases where<br>
certain xlators options had default values only in the volopt_map and<br>
not in their own opt table. Also this will remove the possibilty of<br>
the defaults differing between volopt_map and xlator options table.</blockquote><div dir="auto"><br></div><div dir="auto">+1</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
><br>
> We'd like to hear your thoughts, suggestions and comments to these proposed<br>
> changes.<br>
><br>
> - Glusterd2 team<br>
><br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div></div><div dir="ltr">-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature">- Atin (atinm)</div>