<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Tue, Nov 28, 2017 at 12:25 AM Ben Bradley <<a href="mailto:listsbb@virtx.net">listsbb@virtx.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 23/11/17 06:46, Maton, Brett wrote:<br>
> Might not be quite what you're after but adding<br>
><br>
> # RHEV PRIVATE<br>
><br>
> To /etc/multipath.conf will stop vdsm from changing the file.<br>
> |||<br>
<br>
Hi there. Thanks for the reply.<br>
Yes I am aware of that and it seems that's what I will have to do.<br>
I have no problem with VDSM managing the file, I just wish it didn't<br>
automatically load local storage devices into multipathd.<br></blockquote><div><br></div><div>We don't load anything, this is multipathd default behavior.</div><div><br></div><div>We cannot blacklist local devices since we don't know which devices</div><div>are local, this is something the administrator of the machine should handle.</div><div><br></div><div>In RHEL/CentOS 7.5 we will have a good way to blacklist most local devices,</div><div>see <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1456955#c0">https://bugzilla.redhat.com/show_bug.cgi?id=1456955#c0</a></div><div><br></div><div>Once this is available, your multipath.conf will be upgrade to use the</div><div>new feature when you upgrade vdsm.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I'm still not clear on the purpose of this automatic management though.<br>
From what I can tell there is no difference to hosts/clusters made<br>
through this automatic management - i.e. you still have to add storage<br>
domains manually in oVirt.<br></blockquote><div><br></div><div>The purpose of this configuration is to allow Vdsm to manage shared</div><div>storage - we require certain configuration.</div><div><br></div><div>In 4.2 we documented every setting in multipath.conf, please see</div><div><a href="https://github.com/oVirt/vdsm/blob/913c2e202de718ec828b240642e37e059a86dac9/lib/vdsm/tool/configurators/multipath.py#L66">https://github.com/oVirt/vdsm/blob/913c2e202de718ec828b240642e37e059a86dac9/lib/vdsm/tool/configurators/multipath.py#L66</a><br></div><div>to understand why we require each value.</div><div><br></div><div>If the default multiapth.conf does not work for you, you can make the file</div><div>private, and then you are responsible for using new features provided</div><div>by multipath, we will never touch the file.</div><div><br></div><div>You can also file a bug if you think the default configuration can be</div><div>improved to support some use case.</div><div><br></div><div>Nir</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Could anyone give any info on the purpose of this auto-management of<br>
local storage devices into multipathd in VDSM?<br>
Then I will be able to make an informed decision as to the benefit of<br>
letting it continue.<br>
<br>
Thanks, Ben<br>
<br>
><br>
> On 22 November 2017 at 22:42, Ben Bradley <<a href="mailto:listsbb@virtx.net" target="_blank">listsbb@virtx.net</a><br>
> <mailto:<a href="mailto:listsbb@virtx.net" target="_blank">listsbb@virtx.net</a>>> wrote:<br>
><br>
> Hi All<br>
><br>
> I have been running ovirt in a lab environment on CentOS 7 for<br>
> several months but have only just got around to really testing things.<br>
> I understand that VDSM manages multipath.conf and I understand that<br>
> I can make changes to that file and set it to private to prevent<br>
> VDSM making further changes.<br>
><br>
> I don't mind VDSM managing the file but is it possible to set to<br>
> prevent local devices being automatically added to multipathd?<br>
><br>
> Many times I have had to flush local devices from multipath when<br>
> they are added/removed or re-partitioned or the system is rebooted.<br>
> It doesn't even look like oVirt does anything with these devices<br>
> once they are setup in multipathd.<br>
><br>
> I'm assuming it's the VDSM additions to multipath that are causing<br>
> this. Can anyone else confirm this?<br>
><br>
> Is there a way to prevent new or local devices being added<br>
> automatically?<br>
><br>
> Regards<br>
> Ben<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a> <mailto:<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> <<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a>><br>
><br>
><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div></div>