Matt Phelps wrote:
By making automatic export changes, we remove some of the administrative burden. The cost for doing so is that the default actions may not be what the power users exactly want to do. (And an expectation is that a power admin will check the exports file 99% of the time. It is that other 1% of the time, especially with vol renames and a reboot, that cause them to submit RFEs for automatic editing.)
what a wonderfull world... well, your arguments are persuasive
but
* ABOUT UPGRADES here, i speak for running Filers that are experiencing an Ontap Upgrade the more the black box change, indeed because of * " ' ` improvement ` ' " * the harder it becomes to administer, you always have to track down every change that could occur and pass lots of time to learn new way of doing the same thing - i could speak about options ip.sack.enable passed to on by default which cause enormous damages - i could speak about "vol snapmirror" commands that turn into new "snapmirror" set of command which make lost time and disapointed admins
i don't agree with your 99% for me, perhaps 99% of newbie netapp would appreciate the new feature but 99% of proven netapp admins won't appreciate it
each Ontapp upgrade had became a real challenge nowday (this was a formality before - 537 and some 6)
* ABOUT DOCUMENT NEW FEATURES you could tell me that i am saying something like : " i want no enhancement " " i want only bug correction " for sure i would be wrong because there is a right balance to aim
for me the balance is not respected when improvements occurs w/ out notification or too hard to track (or not enought clear when the improvment has important impact) i think netapp in general - you also i guess - did a good work in documenting new commands in manual and displaying messages at the filer boot, in /etc/messages explaining what had changed I think it is good but not enought
I would appreciate that every options which are new in the new release is displayed at the boot and can be understand with a little explanation message, and also a link to a manpage or any documentation and remember that the worst in a new command implementation is to "silently" change its behavior w/out noticing the user i understand it can be in a way, heavy to manage for you, but it is crucial for some admins (exports not exported after a reboot, snapmirror not running/resyncing after an upgrade w/out a warning, ...)
* ABOUT AUTOMATIZATION - admin does love the way the Filer automatically manage lots of thing (like disks, raid groups, vol add vol0 N, hot-plug/automatic jukebox detection, /etc/passwd automatic creation with notification of it) netapp add an abstract level on top of the uggly dirty hardware/repetitive stuff - i am sure numerous admin won't like at all automatic access to their data w/ out notification like permit nobody access to the root of a volume. access to data is not an abstract layer but is directly part of its security policy
* DON'T READ BELLOW i don't like windoz when windoz crash, you have to wait for the next service pack i thaught I was good at word 6. when i touch to word 2003, i was unable to work with, too much automatic stuff, i was unable to disable it the car i like to drive has a manual gear box
htc