I apologize in advance for such an open-ended question. Also, I recognize that this subject is probably as much art as it is science. Nonetheless, I would appreciate any insight that can be offered.
I am looking for guidance on the subject of test lab requirements. Specifically, if an organization has multiple filer models in production, is it sufficient to maintain a single filer model in the lab for testing? More generally, can anyone point me to resources on the general subject of designing a data center test lab? A cursory search of the web was not helpful (probably because I am having some difficulty adequately refining my searches).
Jeff Browning's paper (TR3055 Creating a UNIX-based Database Software Testing Environment Using a NetApp Filer, http://www.netapp.com/tech_library/3055.html) is instructive from a software testing perspective. I'm interested not only in that, but also h/w and s/w compatibility/interoperability testing, as well as performance testing.
Thanks in advance. Again I apologize for the lack of detail in my request.
Joe
Joe Luchtenberg Dataline, Inc. 757-858-0600 757-285-1223 (mobile) 757-858-0606 (fax) joe.luchtenberg@data-line.com www.data-line.com
Joe,
We at TI have only a couple of models of NetApp filers, F760, F840c, and F880c. Our current lab environment consists of an F760c but is being upgraded to an F880c. We like to keep a model of the type we will be using. For the older models, well we pretty much know what we are doing with those. It is the new models that give us trouble and where we tend to need to experiment.
A test lab machine should be configured in a way that is representative of your production environment or where you wish your production environment to go. It is also good to have a router between the test network and the production network if possible. We like to perform bench marks with our systems and being able to isolate them from the production network allows us to create a baseline free from the network traffic. We can then configure the router to allow traffic from the production network and then check our filers as they would react in that prod. network.
We have also used our test filers as training aids to those interested in learning about filers. As the set up is so easy, we have no problems letting someone experiment with the system configuration learning the ins and outs of the filer and then just blowing it all away when they are done and installing a new boot image.
-gdg
Joe Luchtenberg wrote:
I apologize in advance for such an open-ended question. Also, I recognize that this subject is probably as much art as it is science. Nonetheless, I would appreciate any insight that can be offered.
I am looking for guidance on the subject of test lab requirements. Specifically, if an organization has multiple filer models in production, is it sufficient to maintain a single filer model in the lab for testing? More generally, can anyone point me to resources on the general subject of designing a data center test lab? A cursory search of the web was not helpful (probably because I am having some difficulty adequately refining my searches).
Jeff Browning's paper (TR3055 Creating a UNIX-based Database Software Testing Environment Using a NetApp Filer, http://www.netapp.com/tech_library/3055.html) is instructive from a software testing perspective. I'm interested not only in that, but also h/w and s/w compatibility/interoperability testing, as well as performance testing.
Thanks in advance. Again I apologize for the lack of detail in my request.
Joe
Joe Luchtenberg Dataline, Inc. 757-858-0600 757-285-1223 (mobile) 757-858-0606 (fax) joe.luchtenberg@data-line.com www.data-line.com
-
Joe Luchtenberg -
Mr. G. D. Geen