Re: [Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup
-------- Original Message -------- Subject: [Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup Date: Mon, 21 May 2012 06:34:32 -0400 (EDT) From: Einav Cohen <ecohen@redhat.com> To: Ayal Baron <abaron@redhat.com>, Eldan Hildesheim <ehildesh@redhat.com>, Eldan Hildesheim <info@eldanet.com>, Miki Kenneth <mkenneth@redhat.com>, Andrew Cathrow <acathrow@redhat.com>, Simon Grinberg <sgrinber@redhat.com>, Alexey Chub <achub@redhat.com> CC: engine-devel@ovirt.org
Please review the mock-up on the feature page: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience
Sorry, I just saw this. The advanced features should be in an advanced tab (not easily accessible) in general I'd like to discourage users from changing these params. not sure what mount options is as it is not supported for NFS.
Comments are welcome.
---- Thanks, Einav _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On 06/05/2012 08:03 AM, Ayal Baron wrote:
-------- Original Message -------- Subject: [Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup Date: Mon, 21 May 2012 06:34:32 -0400 (EDT) From: Einav Cohen<ecohen@redhat.com> To: Ayal Baron<abaron@redhat.com>, Eldan Hildesheim <ehildesh@redhat.com>, Eldan Hildesheim<info@eldanet.com>, Miki Kenneth<mkenneth@redhat.com>, Andrew Cathrow <acathrow@redhat.com>, Simon Grinberg<sgrinber@redhat.com>, Alexey Chub<achub@redhat.com> CC: engine-devel@ovirt.org
Please review the mock-up on the feature page: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience Sorry, I just saw this. The advanced features should be in an advanced tab (not easily accessible) in general I'd like to discourage users from changing these params. I agree with this. Have an "Advanced Options" button or something that will display these options. Default state should be hidden. It could get really ugly if the user starts mucking around with options like (r, hard, and sync).
The reason I say this is that the default settings for NFS should be sufficient in the majority of cases. Further, you would think that the NFS maintainers carefully selected and tested the default option set for a variety of scenarios, I'd be hesitant to make it easy to override them unless there is a ground swell of NFS problems. Most of the NFS problems that I've seen are related to server-side permissions and cannot be resolved by the client.
not sure what mount options is as it is not supported for NFS.
Comments are welcome.
---- Thanks, Einav _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
----- Original Message ----- From: "Keith Robertson" <kroberts@redhat.com> Sent: Tuesday, June 5, 2012 4:06:45 PM
-------- Original Message -------- Subject: [Engine-devel] Advanced Nfs Options + NFSv4 GUI mockup Date: Mon, 21 May 2012 06:34:32 -0400 (EDT) From: Einav Cohen<ecohen@redhat.com> To: Ayal Baron<abaron@redhat.com>, Eldan Hildesheim <ehildesh@redhat.com>, Eldan Hildesheim<info@eldanet.com>, Miki Kenneth<mkenneth@redhat.com>, Andrew Cathrow <acathrow@redhat.com>, Simon Grinberg<sgrinber@redhat.com>, Alexey Chub<achub@redhat.com> CC: engine-devel@ovirt.org
Please review the mock-up on the feature page: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience Sorry, I just saw this. The advanced features should be in an advanced tab (not easily accessible) in general I'd like to discourage users from changing these params. I agree with this. Have an "Advanced Options" button or something
On 06/05/2012 08:03 AM, Ayal Baron wrote: that will display these options. Default state should be hidden. It could get really ugly if the user starts mucking around with options like (r, hard, and sync).
The reason I say this is that the default settings for NFS should be sufficient in the majority of cases. Further, you would think that the NFS maintainers carefully selected and tested the default option set for a variety of scenarios, I'd be hesitant to make it easy to override them unless there is a ground swell of NFS problems.
Mock-ups updated - you can review them at: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience [You are welcome to suggest a better phrasing for the default-advanced-nfs-options-values-change warning. Current one is: "It is recommended to keep the default values in the fields below unchanged"]
Most of the NFS problems that I've seen are related to server-side permissions and cannot be resolved by the client.
not sure what mount options is as it is not supported for NFS.
Comments are welcome.
---- Thanks, Einav _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On 06/12/2012 08:09 AM, Einav Cohen wrote:
Mock-ups updated - you can review them at: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience
[You are welcome to suggest a better phrasing for the default-advanced-nfs-options-values-change warning. Current one is: "It is recommended to keep the default values in the fields below unchanged"]
I thought time out was discussed on the relevant patch to be in same units (tenth of seconds) as what users would copy from their mount options: timeo=n The time (in tenths of a second) the NFS client waits for a response before it retries an NFS request. If this option is not specified, requests are retried every 60 seconds for NFS over TCP. The NFS client does not perform any kind of timeout backoff for NFS over TCP.
----- Original Message ----- From: "Itamar Heim" <iheim@redhat.com> Sent: Tuesday, June 12, 2012 9:56:30 AM
On 06/12/2012 08:09 AM, Einav Cohen wrote:
Mock-ups updated - you can review them at: http://www.ovirt.org/wiki/Features/AdvancedNfsOptions#User_Experience
[You are welcome to suggest a better phrasing for the default-advanced-nfs-options-values-change warning. Current one is: "It is recommended to keep the default values in the fields below unchanged"]
I thought time out was discussed on the relevant patch to be in same units (tenth of seconds) as what users would copy from their mount options:
correct. mock-up updated.
timeo=n The time (in tenths of a second) the NFS client waits for a response before it retries an NFS request. If this option is not specified, requests are retried every 60 seconds for NFS over TCP. The NFS client does not perform any kind of timeout backoff for NFS over TCP. _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (4)
-
Ayal Baron -
Einav Cohen -
Itamar Heim -
Keith Robertson