VIOS Shared Storage Pools (was called NextGen) = Simple
nagger 100000MRSJ Visits (13262)
Finally, I found the time to try this new exciting feature and it was really simple to create and operate. I captured movie footage of my first attempt and it all worked (once I removed my spelling mistakes in commands). It only took two commands. So the technology has advanced concepts but it really easy to use, COOL! Some of the commands come with long option names like "-custername". A quick misquote from Star-Trek, never goes wrong: "It is UNIX Jim, but not as we know it!"
One command to create my cluster, repository and initial shared storage pool for Virtual I/O Server called diamondvios1:
cluster -create -clustername galaxy -repopvs hdisk2 \
-spname atlanic -sppvs hdisk3 hdisk5 \
Note: This is the padmin user command cluster and NOT mkcluster as previously reported.
Note: hdisk2 is the cluster repository and hdisks 3 and 5 are the pool.
Then one other command to allocate disk space (16 GB) from the pool and to a client Logical Partition (LPAR) connected to vhost2 virtual adapter:
mkbdsp -clustername galaxy -sp atlantic 16G \
-bd vdisk_diamond6a \
This second command we have already seen this "make backing-device from storage pool" command when using file-backed storage pools first available about 4+ years ago. It is not rocket science but it does give you Thin Provisioning and disk space spread across the pool. Then you start up the client LPAR and install any POWER supported operating system like AIX, Red Hat or Linux. I will have to ask about IBM i. There are a few management and monitoring commands but these two basic provide all the function.
Watch the 22 minute Hands-On movie at Shared Storage Pool Movie
and see the commands used in my Hints and Tip page.
I am happily running a few copies of AIX 7, RHEL 6 and SLES 11 in the client partitions. For the AIX LPARs, I assigned 16 GB "thin" disk space. AIX thinks is has allocated about 5 GB (including, so far, un-touched paging space) but only 3 GB has actually been written too and actually allocated from the Shared Storage Pool. The clients LPAR operating system just see a regular virtual SCSI disk (vSCSI) that we have had for years and operated without knowing anything about the new Shared Storage Pool type. This makes it very easy to adopt.