Hello,
You mention you believe it was GA at one point, and I don't believe that is correct. It used to be the case, but at some point, they determined that if the base release was GD, then subsiqent released are auto-majically placed into GD status.
This has caused us problems and I hope others chime in to see if NetApp will go back to the old release cycle of every version being GA before going to GD.
Stephen Darragh BAE Systems IT Merrimack NH
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Kevin Sheen Sent: Thursday, October 30, 2008 9:04 PM To: Jack Lyons; toasters@mathworks.com Subject: Re: Data OnTap 7.2.6 We upgraded a pair of clustered 3070's and a 3020 last Saturday. We do a small amount of CIFS, more NFS and lots of LUNs. We haven't had any issues. All of the hosts connected to the clustered 3070's are multipathed except for one. good luck with the issues, Kevin At 07:17 PM 10/30/2008, Jack Lyons wrote:
Does NetApp still publish the number of appliances running different version of Data OnTap? We just upgraded to 7.2.6 on Sunday and we have had two (and possibly a third) panics causing failover on 1 of the 4 filers. Failover went smoothly for the most part (I bet the app team that didn't want to spend the money multipathing software / hba's will be singing another tune tomorrow) but both panics didn't create complete core dumps. We are working on the case with NetApp support but want to see what other people were seeing about 7.2.6. 7.2.6 went GD recently and I assume it was GA for awhile before that, but I can't figure release dates or the number of appliances running the different versions of Data OnTap. Thanks Jack p.s. why did we upgrade? http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=281669 is the bug we are hitting...in addition to: http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=253517 http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=256975 http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=271864
Since they change that, we tend to not place too much value on "GD" either anymore.
Right now to me it means "The latest release of a well-tested base", whereas it used to mean "This release has been running for a while and has been found stable, we corrected the stuff we found when it was GA"
Personally, I prefer the latter approach, since I can then more easily assume a GD release will have the most serious bugs fixed and always recommend customers to run GD releases, whereas now, installing a new ONTAP for the first time is a bit more of a surprise, and I cannot as easily make the assumption that a GD release is generally a good one as I could before.
Greets,
Nils
On Mon, Nov 3, 2008 at 5:27 PM, Darragh, Stephen J (US SSA) stephen.j.darragh@baesystems.com wrote:
Hello,
You mention you believe it was GA at one point, and I don't believe that is correct. It used to be the case, but at some point, they determined that if the base release was GD, then subsiqent released are auto-majically placed into GD status.
This has caused us problems and I hope others chime in to see if NetApp will go back to the old release cycle of every version being GA before going to GD.
Stephen Darragh BAE Systems IT Merrimack NH
They used to have it easily seen how long people were running a certain release. I agree the GA before GD was a good measure of the release.
Jack
Nils Vogels wrote:
Since they change that, we tend to not place too much value on "GD" either anymore.
Right now to me it means "The latest release of a well-tested base", whereas it used to mean "This release has been running for a while and has been found stable, we corrected the stuff we found when it was GA"
Personally, I prefer the latter approach, since I can then more easily assume a GD release will have the most serious bugs fixed and always recommend customers to run GD releases, whereas now, installing a new ONTAP for the first time is a bit more of a surprise, and I cannot as easily make the assumption that a GD release is generally a good one as I could before.
Greets,
Nils
On Mon, Nov 3, 2008 at 5:27 PM, Darragh, Stephen J (US SSA) stephen.j.darragh@baesystems.com wrote:
Hello,
You mention you believe it was GA at one point, and I don't believe that is correct. It used to be the case, but at some point, they determined that if the base release was GD, then subsiqent released are auto-majically placed into GD status.
This has caused us problems and I hope others chime in to see if NetApp will go back to the old release cycle of every version being GA before going to GD.
Stephen Darragh BAE Systems IT Merrimack NH
-
Darragh, Stephen J (US SSA) -
Jack Lyons -
Nils Vogels