[Users] ovirt-node trying to use NFS4
Hi, I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Thanks for any pointers, Ian
On 04/13/2012 07:20 PM, Ian Levesque wrote:
Hi,
I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16.
I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues
I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot.
So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain...
Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. You can also make the /etc/nfsmount.conf file persistent with "persist /etc/nfsmount.conf" (I haven't tested this myself).
Hi Juan, On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote:
On 04/13/2012 07:20 PM, Ian Levesque wrote:
Hi,
I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16.
I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues
I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot.
So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain...
Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use.
This worked perfectly - thanks for your help (and for pointing me at the persistent /config directory). Cheers, ~irl
On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote:
Hi Juan,
On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote:
On 04/13/2012 07:20 PM, Ian Levesque wrote:
Hi,
I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16.
I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues
I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot.
So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain...
Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use.
This worked perfectly - thanks for your help (and for pointing me at the persistent /config directory).
Cheers, ~irl
This issue should be filed as a bug against either engine or vdsm (or perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term. Mike
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------000009060703000002010307 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 04/16/2012 06:09 PM, Mike Burns wrote:
Hi Juan,
On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote:
Hi,
I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. This worked perfectly - thanks for your help (and for pointing me at
On 04/13/2012 07:20 PM, Ian Levesque wrote: the persistent /config directory).
Cheers, ~irl This issue should be filed as a bug against either engine or vdsm (or
On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term.
Mike
Isn't that what http://www.ovirt.org/wiki/Features/AdvancedNfsOptions all about ? Y.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------000009060703000002010307 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> On 04/16/2012 06:09 PM, Mike Burns wrote: <blockquote cite="mid:1334588994.3279.48.camel@beelzebub.mburnsfire.net" type="cite"> <pre wrap="">On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi Juan, On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote: </pre> <blockquote type="cite"> <pre wrap="">On 04/13/2012 07:20 PM, Ian Levesque wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi, I'm in the early stages of testing an ovirt install, using the </pre> </blockquote> </blockquote> <pre wrap="">official ovirt engine packages + F16. </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap=""> I configured a storage domain to connect to our gluster storage via </pre> </blockquote> </blockquote> <pre wrap="">NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: <a class="moz-txt-link-freetext" href="http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues">http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues</a> </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap=""> I then installed a host via ovirt-node (2.3.0-1) and successfully </pre> </blockquote> </blockquote> <pre wrap="">added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap=""> So what are my options here, other than not use ovirt-node? AFAIK, </pre> </blockquote> </blockquote> <pre wrap="">gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... </pre> <blockquote type="cite"> <pre wrap=""> Take a look at the /etc/vdsm/vdsm.conf configuration file in the </pre> </blockquote> <pre wrap="">host. </pre> <blockquote type="cite"> <pre wrap="">There is a nfs_mount_options parameter there that you can use. </pre> </blockquote> <pre wrap=""> This worked perfectly - thanks for your help (and for pointing me at the persistent /config directory). Cheers, ~irl </pre> </blockquote> <pre wrap=""> This issue should be filed as a bug against either engine or vdsm (or perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term. Mike</pre> </blockquote> <br> Isn't that what <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://www.ovirt.org/wiki/Features/AdvancedNfsOptions">http://www.ovirt.org/wiki/Features/AdvancedNfsOptions</a> all about ?<br> Y.<br> <br> <blockquote cite="mid:1334588994.3279.48.camel@beelzebub.mburnsfire.net" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <pre wrap=""> _______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> </body> </html> --------------000009060703000002010307--
On Mon, 2012-04-16 at 18:13 +0300, Yaniv Kaul wrote:
On 04/16/2012 06:09 PM, Mike Burns wrote:
Hi Juan,
On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote:
Hi,
I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. This worked perfectly - thanks for your help (and for pointing me at
On 04/13/2012 07:20 PM, Ian Levesque wrote: the persistent /config directory).
Cheers, ~irl This issue should be filed as a bug against either engine or vdsm (or
On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term.
Mike
Isn't that what http://www.ovirt.org/wiki/Features/AdvancedNfsOptions all about ? Y.
Reading that, looks like it's geared toward I/O timeouts, but could certainly be used for the other options. I wasn't aware of the feature previously. My point was simply that we shouldn't be use edit/persist long term for issues like this. There needs to be either a bug or feature filed so that we solve it long term. Mike
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 04/16/2012 06:20 PM, Mike Burns wrote:
On Mon, 2012-04-16 at 18:13 +0300, Yaniv Kaul wrote:
On 04/16/2012 06:09 PM, Mike Burns wrote:
Hi Juan,
On Apr 13, 2012, at 2:57 PM, Juan Hernandez wrote:
Hi,
I'm in the early stages of testing an ovirt install, using the official ovirt engine packages + F16. I configured a storage domain to connect to our gluster storage via NFS (pity we can't use gluster natively yet). On the engine server, I added Nfsvers=3 to /etc/nfsmount.conf as instructed here: http://www.ovirt.org/wiki/Troubleshooting_NFS_Storage_Issues I then installed a host via ovirt-node (2.3.0-1) and successfully added the host, but it refuses to connect to our storage domain because it's attempting to mount via NFS4. When I add Nfsvers=3 to /etc/nfsmount.conf on the host, it comes to life. Of course, that will be reset after a reboot. So what are my options here, other than not use ovirt-node? AFAIK, gluster doesn't export NFS4, let alone have options to disable it. And I don't see any way to add nfs mount options when defining a storage domain... Take a look at the /etc/vdsm/vdsm.conf configuration file in the host. There is a nfs_mount_options parameter there that you can use. This worked perfectly - thanks for your help (and for pointing me at
On 04/13/2012 07:20 PM, Ian Levesque wrote: the persistent /config directory).
Cheers, ~irl This issue should be filed as a bug against either engine or vdsm (or
On Fri, 2012-04-13 at 16:12 -0400, Ian Levesque wrote: perhaps both). An interface to set nfs options needs to be provided through either the engine admin UI or through vdsm in some other way. Manually editing and persisting files is ok as a workaround, but should not be recommended or used long term.
Mike
Isn't that what http://www.ovirt.org/wiki/Features/AdvancedNfsOptions all about ? Y.
Reading that, looks like it's geared toward I/O timeouts, but could certainly be used for the other options. I wasn't aware of the feature previously.
My point was simply that we shouldn't be use edit/persist long term for issues like this. There needs to be either a bug or feature filed so that we solve it long term.
well, for anything fancy, this can be used: http://www.ovirt.org/wiki/Features/PosixFSConnection but if we have an issue with NFS, i agree with need to solve it without using this.
participants (5)
-
Ian Levesque -
Itamar Heim -
Juan Hernandez -
Mike Burns -
Yaniv Kaul