Please enable javascript, or click here to visit my ecommerce web site powered by Shopify.

Community Forum > Is it feasible? QuantaStor running on Amazon EC2 ubuntu instance

Hi,

I have been trying to build a Quanta Stor demo environment on Amazon EC2.
Would you advise me whether it is feasible to make demo environment into public Cloud?

Amazon EC2 ubuntu 10.10 amd64 image + EBS volumes ( to simulate internal disks).

When I followed the steps in 'Ubuntu Server 10.10 to QuantaStor Upgrade Guide', I found some errors but initially
connecting QuantaStor Manager looked fine. But eventually I couldn't log into the Manager and got

"Login attempt failed. [Error: Connection refused]".

The following are errors I noticed during installation.

$ sudo apt-get install qstormanager qstorservice qstortarget qstortomcat
...
...

Setting up qstortarget (2.0.1.2427-1) ...
Starting SCST target service: FATAL: Module iscsi_scst not found.
FATAL: Module qla2x00tgt not found.
FATAL: Module scst_vdisk not found.
FATAL: Module scst not found.
cannot find iscsictl in /proc/devices - make sure the module is loaded
failed.
ERROR: Module iscsi_scst does not exist in /proc/modules
ERROR: Module qla2x00tgt does not exist in /proc/modules
...
...

And these are logs in /var/log/qs_service.log

{Wed Apr 27 00:18:59 2011, INFO, 97593720:osn_service.cpp:118}
OS NEXUS QuantaStor Service 2.0.1.2430
Copyright (c) 2009-2011 OS NEXUS, Inc. All rights reserved.
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osn_service.cpp:123} Stopping services with open handles to key service ports.
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'smtpAuthType' operation for table 'AlertConfigSettings'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'smtpPassword' operation for table 'AlertConfigSettings'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'smtpUsername' operation for table 'AlertConfigSettings'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'initiatorType' operation for table 'InitiatorPort'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'wwpn' operation for table 'InitiatorPort'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'multipathEnabled' operation for table 'PhysicalDisk'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'scsiId' operation for table 'PhysicalDisk'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'unitId' operation for table 'PhysicalDisk'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'storageCloudId' operation for table 'SnapshotSchedule'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'assocType' operation for table 'SnapshotScheduleAssoc'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'markedDisabled' operation for table 'StoragePool'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'noBarriers' operation for table 'StoragePool'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'arpFilterMode' operation for table 'StorageSystem'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'arpFilterStatus' operation for table 'StorageSystem'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'domainSuffix' operation for table 'StorageSystem'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'isMaster' operation for table 'StorageSystem'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'isRemote' operation for table 'StorageSystem'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'searchSuffix' operation for table 'StorageSystem'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'storageSystemClusterId' operation for table 'StorageSystem'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'bandwidthLimit' operation for table 'StorageSystemLink'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'localIpAddress' operation for table 'StorageSystemLink'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'publicKey' operation for table 'StorageSystemLink'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'cloudContainerId' operation for table 'StorageVolume'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'isCloudBackup' operation for table 'StorageVolume'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'bytesRx' operation for table 'TargetPort'
{Wed Apr 27 00:18:59 2011, INFO, 97593720:osncmn_datarepository.h:234} Executing add column 'bytesTx' operation for table 'TargetPort'
{Wed Apr 27 00:19:01 2011, INFO, 97593720:osn_target_manager.h:40} Detected IET target mode driver, QuantaStor service activated with IET target plug-in.
{Wed Apr 27 00:19:01 2011, *CRITICAL*, 97593720:osn_target_manager.h:43} Required component '/usr/sbin/ietadm' is missing, service startup failed. [err=159]

Thanks in advance.

Rgds,
Heeyoung

April 26, 2011 | Unregistered CommenterHeeyoung

Hi Heeyoung,
It looks like it is not loading the SCST target driver. The 2.0 version has a custom kernel so you will need to install the kernel packages. Could you try running uname -a and posting the result here? That should show whether or not the -quantastor custom kernel is installed.
Thanks,
-Steve

April 29, 2011 | Registered CommenterSteve

Thanks Steve, please refer to the result (uname -a)

ubuntu@ip-10-146-102-129:~$ uname -a
Linux ip-10-146-102-129 2.6.35-28-virtual #49-Ubuntu SMP Tue Mar 1 15:12:28 UTC 2011 x86_64 GNU/Linux
ubuntu@ip-10-146-102-129:~$

BRgds,
Heeyoung

April 29, 2011 | Unregistered CommenterHeeyoung

Hi Heeyoung,
Is is possible to upgrade the kernel and reboot the machine image? What you want to see is this:

Linux quantastor-dev3 2.6.35-27-quantastor #48 SMP Wed Mar 9 10:02:36 PST 2011 x86_64 GNU/Linux

So next time you login, try these commands:

apt-get update
apt-get install linux-headers-2.6.35-27-quantastor linux-headers-2.6.35-27 linux-image-2.6.35-27-quantastor

Our customized version of the SCST driver is installed into /lib/modules/2.6.35-27-quantastor and right now you're not loading that kernel so it's not finding the SCST iSCSI driver at boot time. When it doesn't see the SCST driver it tries to load the IET driver hence that error message in the log. We'll probably change that logic so that there's a explicit driver selection setting in /etc/quantastor.conf for SCST or IET rather than having it show this error as it's somewhat misleading. Please let us know how it goes, I'm very interested to hear if QuantaStor runs as an AMI.

Best,
-Steve

April 29, 2011 | Registered CommenterSteve

Hi Steve,

Now I succeeded. Thank you for the support!

I chose an AMI(Amazon Machine Image) which supports PV-GRUB(kernel loader) and followed the step in 'Ubuntu Server 10.10 to QuantaStor Upgrade Guide'.

And modified the file /boot/grub/menu.lst

TO
...
#
title Ubuntu 2.6.35-27.48-quantastor 2.6.35.11
root (hd0)
kernel /boot/vmlinuz-2.6.35-27-quantastor root=LABEL=uec-rootfs ro console=hvc0
initrd /boot/initrd.img-2.6.35-27-quantastor
#

FROM
...
#
title Ubuntu 10.10, kernel 2.6.35-28-virtual
root (hd0)
kernel /boot/vmlinuz-2.6.35-28-virtual root=LABEL=uec-rootfs ro console=hvc0
initrd /boot/initrd.img-2.6.35-28-virtual
#
...

Then I did reboot. With new kernel, the Instance brought up successfully and I was able to confirm the kernel had loaded.

# uname -a
Linux ip-10-146-90-143 2.6.35-27-quantastor #48 SMP Wed Mar 9 21:46:32 PST 2011 x86_64 GNU/Linux


Now everything looks fine and I can see the Amazon EBS volumes in QuantStor Manager like this.

Name Type State Storage Pool Size Vendor Product ID Serial Number
sdf SCSI Normal 1024MiB Hypervisor VDISK 28d154ef-ceb0-8cf6-dbbf-0de5a80b02df
sdg SCSI Normal 1024MiB Hypervisor VDISK fd0f5c66-eedf-df28-39ea-b13285fb7ff9
sdh SCSI Normal 1024MiB Hypervisor VDISK 57ae34fe-915f-610f-4791-ef96afac4acd
sdi SCSI Normal 1024MiB Hypervisor VDISK 7689a90c-af7e-334e-a473-27a7a72fc24e

Thank you again!

Rgds,
Heeyoung

May 3, 2011 | Unregistered CommenterHeeyoung

I forgot to mention this.
Before modified /boot/grub/menu.lst, I did

# apt-get update
# apt-get install linux-headers-2.6.35-27-quantastor linux-headers-2.6.35-27 linux-image-2.6.35-27-quantastor

as you tought me.

Thanks.
Heeyoung

May 3, 2011 | Unregistered CommenterHeeyoung

Great going Heeyoung! After getting the system running, were you able to assign some physical disks to it and create a pool?

May 5, 2011 | Registered CommenterSteve

Hi Steve,

The disks you can see in the last post (sdf, sdg, sdh, sdi) are actually physical disks in the field of Amazon Cloud. They are EBS (Elastic Block Storage) volumes which works as same as any physical disks do on in-premise environmnent. I am going to add posts if there is any problem using QuantaStor from now. As far as I guess, there will be no problem in creating a pool and doing additional tasks from here.

Thanks,
Heeyoung

May 5, 2011 | Unregistered CommenterHeeyoung

Yes, I overlooked that part of the post. That's great, yes you should be able to create storage pools with those just fine. Thanks Heeyoung.

May 7, 2011 | Registered CommenterSteve

We just gave this a try today and wanted to summarize the steps for those looking to use QuantaStor in the cloud.

1) Locate an Ubuntu Server 10.10 image to use as a starting point. You'll find these in the Community AMI images, the one we used was
AMI: ebs/ubuntu-images/ubuntu-maverick-10.10-amd64-server-20101225 (ami-cef405a7)
2) Be sure to open up the TCP port 3260 on your QuantaStor system so you can access your iSCSI devices from other machines in the cloud
3) Be sure to open up the TCP port 22 on your QuantaStor system so you can login via SSH to the console.
4) 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'
5) Install QuantaStor using our Upgrade Guide here: http://wiki.osnexus.com/mediawiki/index.php/Ubuntu_Server_10.10_to_QuantaStor_Upgrade_Guide
6) After all the packages are installed you'll need to switch the kernel over to our custom kernel by modifying the /boot/grub/menu.lst file as Heeyoung notes above.
7) We noticed a long delay when creating the Storage Pool.. it succeeded but for whatever reason it took longer than normal.
8) Enjoy!

June 30, 2011 | Registered CommenterSteve