With today's release of the 2009.Q3 update for 7000 Series Unified Storage Appliances there are a few enhancements to storage profiles that we can take advantage of and the trusty size calculator tool was in need of modification to use them, so I've spent some time putting them together. The resulting tool can be downloaded here, details about what has changed follow below.

The most obvious change from a size calculator perspective with the 2009.Q3 release is that the appliance has some new storage profiles (namely Triple Parity RAID with wide stripes, and Three-Way Mirroring). When run against an updated appliance or simulator, the tool will show these new profiles:

$ ./sizecalc.py 172.16.131.131 *** 12 Sun Storage 7000 Size Calculator Version 2009.Q3 type NSPF width spares data drives raw (TB) usable (TiB) mirror False 2 4 284 142.00 127.13 mirror True 2 4 284 142.00 127.13 mirror3 False 3 6 282 94.00 84.16 mirror3 True 3 6 282 94.00 84.16 raidz1 False 4 4 284 213.00 190.70 raidz1 True 4 4 284 213.00 190.70 raidz2 False 14 8 280 240.00 214.87 raidz2 True 14 8 280 240.00 214.87 raidz2 wide False 47 6 282 270.00 241.73 raidz2 wide True 20 8 280 252.00 225.61 raidz3 wide False 56 8 280 265.00 237.25 raidz3 wide True 35 8 280 256.00 229.19 stripe False 0 0 288 288.00 257.84 ** As of 2009.Q3, the raidz2 wide profile has been deprecated. ** New configurations should use the raidz3 wide profile. In addition to these supporting these new storage profiles, I wanted to enhance the calculator to better handle the existing variety of drives we support in the 7210 (the 2009.Q2 release could only model 1TB disks), and prepare to model configurations with drives larger than 1TB in the 7310 and 7410.

The revised help message explains how to declare different disk sizes in more detail (run sizecalc.py without any arguments to read it), but the examples below should help to highlight the new capability and how it ties in with the previous enhancements. Here is an example modelling a 7210 configuration using 500GB disks; you can see that the size keyword and argument are prepended to the JBOD layout:

$ ./sizecalc.py 172.16.131.131 *** size 500G 1 t1 Sun Storage 7000 Size Calculator Version 2009.Q3 type NSPF width spares data drives raw (TB) usable (TiB) mirror False 2 3 42 10.50 9.40 mirror3 False 3 3 42 7.00 6.27 raidz1 False 4 5 40 15.00 13.43 raidz2 False 14 3 42 18.00 16.12 raidz2 wide False 43 2 43 20.50 18.35 raidz3 wide False 43 2 43 20.00 17.91 stripe False 0 0 45 22.50 20.14 ** As of 2009.Q3, the raidz2 wide profile has been deprecated. ** New configurations should use the raidz3 wide profile. When combined with Eric Schrock's modeling feature we can specify a different size drive each time we 'add' a JBOD layout (we're not actually selling 2TB drives yet, but the tool will allow us to model that configuration anyway):

./sizecalc.py 172.16.131.131 *** 1 add size 2T 1 Sun Storage 7000 Size Calculator Version 2009.Q3 type NSPF width spares data drives raw (TB) usable (TiB) mirror False 2 4 44 33.00 29.54 mirror3 False 3 6 42 21.00 18.80 raidz1 False 4 8 40 45.00 40.29 raidz2 False 11 4 44 54.00 48.35 raidz2 wide False 23 2 46 63.00 56.40 raidz3 wide False 23 2 46 60.00 53.72 stripe False 0 0 48 72.00 64.46 ** As of 2009.Q3, the raidz2 wide profile has been deprecated. ** New configurations should use the raidz3 wide profile. In this example, have supplied the configuration "1 add size 2T 1" which tells the calculator to initially model a single JBOD with the default drive size, which is 1TB, and then add a new JBOD with 2T drives. You can see that the total number of disks is only 48, however the results are based on 72TB of raw capacity.

As always, you can find the latest 7000 information in the Fishworks wiki. Happy calculating!

EOF





More...