After the last step, oracle VirtualBox should be up and running and you also should have downloaded the two virtual machine images. Now, you are ready to import the machines into VirtualBox.
Start with the ZFS Appliance, because that’s a bit more fun.

1.4. Install zfs appliance simulator virtual machine

1.4.1. Import the vm image into virtualbox

The zfs appliance simulator comes as a zip archive called something like SunZFSStorageVM-2011-04-24-5-0-1-1-33.zip. Just unpack that archive and you will end up with a bunch of virtual disks (*.vmdk) and, most importantly, an ovf – file.

root@jenklotz# unzip SunZFSStorageVM-2011-04-24-5-0-1-1-33.zip
Archive: SunZFSStorageVM-2011-04-24-5-0-1-1-33.zip
creating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000.ovf
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk5.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000.mf
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk10.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk1.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk6.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk9.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk4.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk11.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk7.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk2.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk12.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk8.vmdk
inflating: SunZFSStorageVM-2011.04.24.5.0,1-1.33/Sun_ZFS_Storage_7000-disk3.vmdk

In your virtualbox main window, select File -> import appliance
ZFSAttack_01_06_importApp1

Click open appliance.
ZFSAttack_01_07_importApp2
Browse to the ovf-file, you just extracted and press open
ZFSAttack_01_08_importApp3
Click next.
ZFSAttack_01_09_importApp4
Here you can change the virtual hardware settings of your virtual appliance. Because my notebook is a bit low on RAM, I gave the machine 1024MB, but you might want to stick with the default.
When you are sizing your RAM, please keep in mind, that in later labs you need the ZFS Appliance and the linux machine both running at the same time on your host system.
I was able to run the ZFS Appliance with 512MB RAM. Not the greatest performance anyone has ever seen, but working.
When you are done, press import.
ZFSAttack_01_10_importApp5
Wait.
Maybe have a cup of tea. Take the dog for a quick walk. Solve the problem of life, the universe and everything else. This really can take a while, depending on your host system.
ZFSAttack_01_11_importApp6
Finally, it’s done.

Notice the twelve virtual disks, the appliance has created. The upper two (50GB each) are the system disks, the other ten we will use later for the creation of the zpool.

1.4.2 Configure the virtual zfs appliance

If you are feeling adventurous, like I did, you now might want to hit the shiny green start-button. But if you do that, you most certainly will be greeted by this unfriendly error message.
ZFSAttack_01_12_VMsettings1
That’s because there is no network interface configured on the machine yet. But this can easily be done in just a few mouseclicks.
In the main window of virtual box, highlight your virtual machine and click on settings. A new windows pops up, that looks a lot like the one from step 1.3, where you created the virtual network. Select network.
ZFSAttack_01_13_VMsettings2
On the Adapter 1 tab, check enable network adapter. Attached to should be set to Host-only and the name should be set automatically to the network you created in step 1.3.

Click okay to return to the start screen of VirtualBox and start your machine by hitting… well, the shiny green start-button.
ZFSAttack_01_15_bootVM1
A quick note:
When you click inside the new window, your mouse cursor will get captured. If that happens to you, just hit the right “ctrl” key on your keyboard. That should bring your cursor back.

During boot, I received another error message, because my laptop does not work with VT-x hardware acceleration. This is needed for the Appliance in order to run under 64bit. I was able to ignore this message by pressing continue.
If you want to really fix this, you might have to reboot your host system. In BIOS, look for a setting called something like CPU-Virtualization and enable it. When done, you should be able to start the appliance without this message.

ZFSAttack_01_16_bootVM2
During the boot, you will receive a message saying the System detected 32 CPUs, but only 1 cpu(s) where enabled. Thats more or less a nice reminder, that a real ZFS Appliance normally has far more power, than your laptop and can safely be ignored for this lab.
ZFSAttack_01_17_bootVM3
After a while, you will be presented with the initial configuration screen. Enter the following values, that match the settings of the virtual network you created earlier.
ZFSAttack_01_18_bootVM4

Settings
hostame: zfsapp1
DNS domain: localdomain
IP Address: 192.168.56.100
IP Netmask: 255.255.255.0
Default Router: 192.168.56.1
DNS Server: 192.168.56.1
Passwort: (anything you like, but be sure to make a note of it - I used "oracle")

After you are done, keep the escape key on your keyboard pressed and at the same time press “1” to save the settings and continue the booting process.

After a while, the machine is done and gives you detailed instructions of what to do next.
ZFSAttack_01_19_bootVM5
And thats exactly, what we are going to do now.
Leave the virtual machine by hitting the right “ctrl” key, open your favourite webbrowser on your host system and browse to https://192.168.56.100:215/
ZFSAttack_01_20_bootVM6
Login using the username root and the password you specified a few steps before (and of course made a note of).
ZFSAttack_01_21_config1
You will be greeted by a welcome screen. Hit Start and begin the last part of the configuration process.
ZFSAttack_01_22_config2
On the first screen you can configure the network devices from your virtual machine.
The first device will be configured based on the settings you made a few steps back. Since we only need this one interface for our lab, you don’t have to make any adjustments here. But take some time and verify, that everything is configured the way, you would expect it to be.
When you are done, hit the commit button in the upper right.
ZFSAttack_01_23_config3
The second step is for configuring the dns settings. Also, those have already been made, so you don’t have to change anything. Just continue to the next screen.
ZFSAttack_01_24_config4
Here, you can configure ntp. For this lab, we don’t need it, so keep it off.
ZFSAttack_01_25_config5
Now, you can configure naming services. The ZFS Appliance is able use name services like LDAP or microsoft active directory for user authentication. For this lab, we don’t cover those, so just hit commit and go to the next screen.
ZFSAttack_01_26_config6
And now for the interesting part. here you can create a storage pool. As its name implies, the ZFS Appliances uses ZFS for its data shares, so we will create a zpool.
Hit the little “+” – Button next to available pools.
ZFSAttack_01_27_config7
Give the pool a name of your choice and click apply.
ZFSAttack_01_28_config8
The virtual machine comes with ten virtual data disks of 5GB size each, as you have seen earlier in the virtualBox homescreen.
Let’s add them all to the new zpool. Select 10 from the pulldown and click commit.
ZFSAttack_01_29_config9
Now you can select which profile you will configure the disks. A profile is nothing more than oracles fancy name for RAID-level. I selected Mirrored, which is essentially a RAID 10, but this is up to you.
Take a moment to see, what the Appliance has to offer here. When you have taken your pick, click on commit.
ZFSAttack_01_30_config10
And there is your zpool.

From the ten disks, two have been configured as spare disks. The other eight disks build the actual mirror, which leaves an effective size of 20GB.
ZFSAttack_01_31_config11
In the last step you can register your appliance with oracle support. When this feature is configured, the Appliance will be able to create service requests on its own, if it detects a hardware error like a broken disk. Of course, you need a working support contract to do this.
In this lab we obviously don’t have a working support contract for our virtual machine, so just hit later.
ZFSAttack_01_32_config12
If you see this page, it means, you are done and the appliance is up and ready to go.
Yeah!

On the next page, you will import the linux machine, which in the following labs will be used as client.

Leave a Reply

Your email address will not be published. Required fields are marked *