Reactor wrote:
Josh26 wrote:
There is nothing worse than doing all your testing with firmware x and then putting it into production, before being told a month later firmware y has been in "monitored release" for the whole time, and is now the recommended deployment.
If new to the 3PAR platform, it's actually a good exercise to do an upgrade prior to going into production, assuming there's a reasonably-equivalent-to-production test environment around the array. It could theoretically uncover peculiar implementation issues, such as missing paths or host settings discrepancies—all things you don't want to discover while performing a software upgrade in production.
Ditto for this, firmware updates are probably the most risk prone operation you'll do in the lifetime of the array, having a selection of your typical host configurations attached but with non production data should help iron out host config issues to make them smoother in future. You could do some random node restarts to emulate it but it's not exactly the same.
Also I suspect 3.3.1 is unlikely to become a trustable default this year, 3.2.2 was in the wild too early because new hardware came out that only supported 3.2.2. I don't expect new hardware before Aug, except maybe xscale cards.
Hopefully they get it stable quicker then 3.2.2 but I'd still wait for MU2 on a prime production box.