VM/VSA Install

From OSNEXUS Online Documentation Site
Jump to: navigation, search

QuantaStor may be installed on both bare-metal servers or as a guest VM using any of the major hypervisors including VMware ESXi, Microsoft Hyper-V, Citrix XenServer, and Linux KVM. VM installations are best for remote-site DR configurations, NAS Gateways, and small scale remote-office or cloud NAS use cases. When QuantaStor is installed as a guest VM this is known as a Virtual Storage Appliance (VSA).

Installing to VMware Workstation 9 (Virtual Storage Appliance)

There's really just one key step to successful installation on VMware Workstation 9 and that's to *not* use the Easy Installer. The Easy Installer will completely bypass the QuantaStor custom installation steps and will result in installing just plain Ubuntu Server. To ensure that the QuantaStor custom installation steps are run you must not use 'Easy Installer'. To bypass 'Easy Installer' simply choose 'I will install the operating system later.' and the virtual machine will be created with a blank hard disk. After you have created the VM instance you can then 'Edit Virtual Machine Settings' to point it to your QuantaStor CDROM or ISO image and begin the install. Here are a series of screenshots to illustrate the installation process:

Step 1.
Step 2.


Step 3. This is a key step. If you choose one of the first two it will try to use 'Easy Install' mode which will bypass the QuantaStor installation components. As such you must choose 'I will install the operating system later.'.
Step 4. Choose 64bit Ubuntu Linux from the list of available operating systems. (n.b. QuantaStor builds on top of the Ubuntu 64bit server Linux distribution.)


Step 5.
Step 6.


Step 7. 1GB of RAM is sufficient for doing basic things with a QuantaStor virtual storage appliance but for real production use you should allocate 2GB, 4GB or more.
Step 8. The installation will use DHCP to get an IP address and will connect to the net to determine your Time Zone. You'll also want to be able to connect to this VM via iSCSI from the host workstation so Bridged Networking is necessary.


Step 9. The boot device need only be 8GB in size but I just kept with the VMware default of 20GB. For production use, 20GB for the boot/system drive is best.
Step 10. SCSI is always best for the drive interface as it provides additional information and a unique ID by which QuantaStor can identify the device.


Step 11. You can use a single file or multiple files, I choose single file for simplicity.
Step 12.


Step 13.
Step 14.


Step 15.
Step 16.







Step 17.
Step 18.


Step 19. This disk drive is for creating a storage pool so we create a device here so later we can create 'pool0' within QuantaStor.
Step 20.


Step 21.
Step 22.


Step 23.
Step 24.



Note that the default console user is 'qadmin' and the default password is 'qadmin'. The console account is completely separate from the QuantaStor web management interface account which is 'admin' with the initial password of just 'password'.

Installing to VMware ESXi (Virtual Storage Appliance)

Using VMware with ESXi requires some specific settings to be chosen as part of the VM creation process. In this section we'll go step by step through each screen the VM creation wizard in the vSphere Client so the overall process is a snap.


Step 1. This first screen shows the available operating system selections, since QuantaStor is based on Ubuntu Server (64bit) we choose that from the drop down list of Linux OS types.
Step 2. Next we're asked to make a boot/system disk for the new virtual appliance. We suggest 6GB or more for your virtual machine, but more than 32GB is unnecessary unless you plan to install custom applications on your virtual storage appliance.



Step 3. Next you'll want to check that box that says 'Edit the virtual machine settings before completion.' as we have a number of things to edit before you can boot the system to start the installation. Once you check the box, press the 'Continue' button and you'll then be able to edit the virtual machine settings.
Step 4. At this point you'll be presented with the 'Virtual Machine Properties' dialog. In here there are a few things that you need to make sure of. First, make sure that you change the SCSI controller from LSI Parallel to LSI Logic SAS.










Step 5. Next, select the network adapter and make sure 'Connect at power on' is checked. This will allow the installer to access the Ubuntu package servers during the installation and will also configure your network via DHCP. You'll want to change this to a static address later but it is very convenient to have the system use DHCP for the initial installation phases.
Step 6. Next you'll need to select the ISO file for where you're keeping your osn_quantastor_vX.Y.Z.iso ISO file. This must also be 'Connected at power on' so that it can boot from the ISO to start the installation process.




The default amount of memory given to the VM is only 512MB which is insufficient. QuantaStor has an internal web server which uses a fair bit of memory and additional memory is used as a buffer cache to accelerate read performance. If you have it, set this to 2GB or more, else set it to at least 1GB of RAM.


This is what it should look like when you're all done. Go ahead and click finish and you can start your VM to start the installation process.



Installing to Oracle VirtualBox (Virtual Storage Appliance)

Getting a QuantaStor storage system setup as a virtual appliance is one of the easiest ways to get started with QuantaStor to test out the features and get a feel for the product. To install QuantaStor as a VirtualBox virtual appliance you'll first need to download the virtual appliance from our downloads page, and you'll need to install the latest version of VirtualBox from their website http://www.virtualbox.org.

Once you have the quantastor_vsa_ovf.zip file downloaded you'll need to unzip the file. In there you will find a file with a .ovf extension and some associated files, that's what you'll be importing as a virtual appliance. Now you'll need to startup VirtualBox and select 'Import Appliance..' from the 'File' menu. Next you'll select the .ovf file that you unzipped from the quantastor_vsa_ovf.zip in the previous step. That's all there is to it. Note that by default QuantaStor is setup to use Bridged Networking so that your hosts can access the exported iSCSI targets exposed by the VM.

Adding disks to your QuantaStor Virtual Storage Appliance

Step 1. Before starting your QuantaStor VSA VM you'll want to first add some storage to it so that you have some storage with which to create storage pools. Bring up the settings panel for your VM so that you can add more storage.


Step 2. Our testing has found that virtual storage disks hosted on a virtual SAS Controller is much more reliable than the default SATA controller. The first step will be to add this SAS controller as shown in this screen capture.


Step 3. Once the SAS controller is available, a new disk can be added to it using the button highlighted below. We recommend that you attach at least a 40GB disk to the virtual appliance so that you have enough disk space to create a storage pool that's large enough to provision storage volumes that are 8GB in size to install Windows, Linux, and/or applications onto.



Configuring your QuantaStor VSA VirtualBox appliance

Now that you have one or more disks attached to your imported appliance, all you need to do now is to start it up and configure it as per the general Getting Started Guide.

Installing to Citrix XenServer v7.x (Virtual Storage Appliance)

Running QuantaStor as a virtual storage appliance (VSA) can be installed from our ISO. There are just a few steps to get started.

After clicking the 'New VM' option, you will need to select the 'Ubuntu Trusty Tahr 14.04' option and click 'Next'.

NewVM.png

Next you'll need to name the virtual machine and click 'Next'.

NameVM.png

Next select the ISO image that you intend to install from, whether this is from an ISO library or DVD drive. Select the latest QuantaStor ISO and click 'Next'.

SelectISO.png

Next select the home server and click 'Next'.

SelectHomeServer.png

Next allocate processor and memory resources. For a test environment 1 vCPU and 1GB of RAM is fine, but you will need 2GB of RAM if you're using scale-out NAS. Click 'Next'.

AllocateResources.png

You might be given an option to assign a virtual GPU. In this example we don't have a GPU and for QuantaStor you won't need one so just click 'Next'.

AssignGPU.png

Next configure the storage. We recommend 6GB or more for your virtual machine, but more than 32GB is unnecessary unless you plan to install custom applications on your virtual storage appliance. Click 'Next'.

ConfigureStorage.png

Next configure networking. We would recommend at least 1 virtual network interface. Click 'Next'.

ConfigureNetworking.png

Now you're ready to create the virtual machine. Take a moment to go over the selected configuration. When you are happy to proceed click 'Create Now'.

CreateVM.png

Installing to Microsoft Hyper-V (Virtual Storage Appliance)

Running QuantaStor as a virtual storage appliance (VSA) can be done by installed from ISO, but there's a few configuration changes that you'll need to make after you create the virtual machine.

One change is to add a Legacy Network Adapter as the installation process will not be able to access the network using the standard adapter. To do this navigate to the VM's settings. In the 'Add Hardware' section, add a 'Legacy Network Adapter'. Now configure this to your choosing. Then select the network adapter created from the create VM wizard, and remove it.

LegacyAdapterSetting.png

The next change is during the installation of QuantaStor. When the iso is first being loaded hit the 'f6' key when on the language selection screen (you may have to hit it before you see the screen as Hyper-V sometimes doesnt load the screen in time before the language is selected). This will bring up an options screen. Hit 'f6' again to bring up 'Other Options', and then hit escape to close it. This step is to bring up the boot options string that we will now modify. In the boot options string that is listed remove 'nodmraid' and 'acpi=off'. You will also want to add the field 'vga=788' to fix some graphical issues that occur sometimes. Now hit enter to start the installation.

The options on the left should be changed to look like the options on the right.

OldOptions.png NewOptions.png

You can now install QuantaStor onto your virtual machine just as you would any other operating system. Note that you should allocate at least 1GB of RAM to your QuantaStor VM and you should allocate at least a 30GB + the number of GB in RAM virtual hard drive for use as your boot/system disk. Example: A system with 32GB in ram should have atleast 62GB in hard drive space.


Here are some of the problems you may encounter if you do not make these changes. As you can see the graphics might not be displayed properly, and the disks may not be discovered.

BadVideo.png NoDisk.png

Installing QuantaStor VSA to an Amazon EC2 Instance

The following steps summarize the process for installing QuantaStor in the Amazon AWS cloud by starting with an Ubuntu Server 14.04 image and then upgrading it to a QuantaStor Virtual Storage Appliance.

Selecting an Amazon Machine Image

We currently do not have an Amazon Machine Image for QuantaStor so the installation procedure requires upgrading a stock Ubuntu Server 14.04 image to use as a starting point. You'll find these in the AMI image marketplace here: https://aws.amazon.com/marketplace/pp/B00JV9JBDS

EC2 Firewall Configuration

Be sure to open up the TCP port 3260 to your QuantaStor system so you can access your iSCSI devices from other machines in the cloud. Next you'll need to open up the TCP port 22 on your QuantaStor system so you can login to the SSH to the console. You'll also need access to port 22 for remote replication. Finally, open up port 80 and/or 443 so that you can access the QuantaStor web management interface, and if you're going to be replicating between a local QuantaStor instance and your Amazon Cloud instance you'll need to open TCP port 5151. In summary, open the TCP ports 80, 443, 5151, & 3260.

EC2 PEM Files / SSH Login

When you create and download your .pem key file, remember to use PuttyGen to convert the .pem key into a .ppk private key that you can load into Pageant, after that you'll be able to login to the system as 'ubuntu'. If you're not familiar with PuTTY, it is a free SSH client for Windows that allows you to login to the QuantaStor console remotely over a secure connection. You'll need to login to your Ubuntu Server Amazon Machine Image using SSH in order to upgrade/convert it to a QuantaStor system. PuTTY is available here [1]:

Upgrading the Amazon Machine Image

To install QuantaStor onto your Amazon machine image after you have it created you'll need to login to the VM via SSH and run these commands:

echo "deb http://packages.osnexus.com/packages trusty main" > /etc/apt/sources.list.d/osnexus.list
wget http://packages.osnexus.com/packages/osnexus.gpg
apt-key add ./osnexus.gpg
apt-get update
apt-get install qstorservice qstormanager

Installing the QuantaStor Kernel

QuantaStor requires a number drivers which are not included with the standard AWS Ubuntu 3.13 kernel. As such a kernel upgrade is required to upgrade the system to a QuantaStor kernel build. This is done by running the following script as root:

sudo qs-kernelupgrade

Note that the qs-kernelupgrade stage will pause and report some grub errors and dkms errors as it goes along and these should be ignored. Please give the upgrade process at least 20 minutes to run. After the kernel upgrade is complete and you're presented with the command prompt again, it'll be time to reboot the VM.

reboot now

After the reboot verify that the system started with the new kernel. You'll want to see 4.4.0-112-generic in the output from running uname like so:

root@ip-10-XXX-XX-XXX:~# uname -a
Linux ip-10-XXX-XX-XXX 4.4.0-112-generic #135~14.04.1-Ubuntu SMP Tue Jan 23 20:41:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Install Remaining Packages

Now to finish we need to install winbind and update the kerberos default config file:

apt-get update
apt-get install winbind ceph radosgw
cp /etc/krb5.default /etc/krb5.conf

Now verify that the AD config script is working:

/opt/osnexus/quantastor/bin/qs_cifs_dc_setup.py --get_service_config

You should see some output that looks like this:

security =  user
workgroup =  WORKGROUP
realm =
kdc =  QS-KDC
trusteddomain =