CA AppLogic Forums

How-to create a managed Ubuntu 11.04 appliance (SIMPLIFIED)

PavelGeorgiev — Fri, 18 May 2012 19:10:47 GMT

These are the steps to create a managed ubuntu 11.04 appliance using iso2class/hvm2pv. This process is meant to be run on a AppLogic 3.0 grid or newer, if you want to execute it on an older version, you may have to manually install APK instead of using hvm2pv. This could be used for both 32-bit and 64-bit versions.

This is a simplified version of an older how-to. This one has more detailed instructions for the installation process and is easier to follow, providing a lot of commands that can simply be copy-pasted. The older how-to leaves a lot of options for the process (like choosing the partitioning setup), but also requires modifications to the instructions if you decide to make an install that is different than the once that is described.

Run iso2class

util iso2class app_name=ubuntu-11-04 iso_volume1=ubuntu-11.04-server-amd64.iso install_size=2G console_type=graphic os=linux-64 virt_mode=xen_hvm,vmware

Open the graphical console and complete the installation.

Few important things:
- if running on a xen grid, you need to pass xen_emul_unplug=never to the installer (press F6 on the install screen to get to that menu), otherwise the ubuntu install kernel will detect that it runs on xen and it will disable all devices
- no need to configure network during the install
- use a manual partitioning as follows:
/, primary, 500MB, ext3
/usr, primary, 1.6GB, ext3
- make sure you install openssh-server and libc6-i386 (needed only for 64-bit appliance, you will have to go to manual package selection for this) packages.
- install grub in the MBR (thats the default choice)

Once the installation is complete, go back to the iso2class console and proceed with the install. When prompted, say you want to run hvm2pv now.

While hvm2pv is running, it will prompt you with the following question:

Code:

Do you want to set up a new root password for text console login?

Say 'Y'. Before proceeding, login to the appliance that hvm2pv is running (it should be something like hvm2pv_pg-ubuntu-11-04_5133:main.LINUX64) and execute the following:

Code:



# root mount point of the boot partition, this needs to be change accordingly

ROOT_MOUNT=/mnt/vol/hdc1

 

# edit $ROOT_MOUNT/etc/default/grub and modify the GRUB_CMDLINE_LINUX line to include xen_emul_unplug=never

sed -i $ROOT_MOUNT/etc/default/grub -e 's/GRUB_CMDLINE_LINUX=.*$/GRUB_CMDLINE_LINUX="xen_emul_unplug=never"/'



#Update grub2 configuration:

mount -o bind /dev/ $ROOT_MOUNT/dev/

mount -o bind /sys/ $ROOT_MOUNT/sys/

mount -o bind /proc/ $ROOT_MOUNT/proc/

sed -e 's/timeout=-1/timeout=2/' -i $ROOT_MOUNT/etc/grub.d/00_header

chroot $ROOT_MOUNT/ update-grub



# Create PV grub configuration the root device and kernel/initrd paths may be different, check the grub2 config for details ($ROOT_MOUNT/boot/grub/grub.cfg):

cat > $ROOT_MOUNT/boot/grub/menu.lst  << EOF

default 0

timeout 1



title AppLogic Appliance

        root    (hd0,0)

        kernel  /boot/$(find $ROOT_MOUNT/boot/ -iname 'vmlinuz-2.6.38*' -printf '%f') root=UUID=$(blkid -o value -s UUID /dev/hdc1) ro console=hvc0

        initrd  /boot/$(find $ROOT_MOUNT/boot/ -iname 'initrd.img-2.6.38*' -printf '%f')

EOF



# Update dhcp configuration



ln -sf /etc/dhclient-enter-hooks $ROOT_MOUNT/etc/dhcp/dhclient-enter-hooks.d/apk



sed -i 's#\(/usr[[:blank:]]\+ext3[[:blank:]]\+defaults\)\([[:blank:]]\+\)[[:digit:]]\([[:blank:]]\+\)[[:digit:]]#\1,ro\20\30#g' $ROOT_MOUNT/etc/fstab

echo xen-blkfront >> $ROOT_MOUNT/etc/initramfs-tools/modules 



chroot $ROOT_MOUNT update-initramfs -u



# disable apparmor for dhclient

chroot $ROOT_MOUNT ln -s /etc/apparmor.d/sbin.dhclient /etc/apparmor.d/disable/



# move applogic_init service from runlevel S to 2345

chroot $ROOT_MOUNT update-rc.d -f applogic_init remove

chroot $ROOT_MOUNT update-rc.d -f applogic_init start 01 2 3 4 5 . stop 99 0 1 6 .

Proceed with the hvm2pv install. After it is done you should have a managed HVM appliance

Modify the boundary of the new class, to include 'Xen Paravirtualization' in its Virtualization modes and have a usr volume, common, read-only, shared:

class put_desc ubuntu-11-04:ISO2CLASS

Code:

component ISO2CLASS

   {

   .category         = Generic

   .description      = "iso2class singleton"

   .config_mode      = dhcp

   .console          = "ssh:22,text,graphic"



   volume boot       : class           , boot           , dev  = /dev/sda  , type = instantiable

   volume usr        : class           , shared         , ro          , dev  = /dev/sdb          , type = common



   resource cpu      : min      = 0.05 , max      = 16  , dflt = 0.5

   resource mem      : min      = 128M , max      = 16G , dflt = 512M

   resource bw       : min      = 1M   , max      = 1G  , dflt = 1M



   input in          : protocol = any

   output out        : protocol = any

   output net        : gateway         , protocol = any

   output mon        : protocol = cce



   interface default



   virtualization

      {

      options       = "esx_os_name=rhel6-64"

      device_schema = /dev/sdX

      modes         = "vmware,xen_pv"

      }



   visual

      {

      color      = violet

      style      = medium

      size       = 3

      east       = ooo

      west       = i



      output out : orient = east

      input in   : orient = west

      output mon : orient = east

      output net : orient = east

      }

   }

Split the boot volume into two volumes:

vol create ubuntu-11-04:boot par1.fs=raw par1.size=500MB
vol create ubuntu-11-04:usr par1.fs=raw par1.size=500MB
vol copy ubuntu-11-04:ISO2CLASS.boot%par1 ubuntu-11-04:boot%par1 --fscpy
vol copy ubuntu-11-04:ISO2CLASS.boot%par2 ubuntu-11-04:usr%par1 --fscpy

Copy the MBR
vol manage ubuntu-11-04:ISO2CLASS.boot ubuntu-11-04:boot

Code:

dd if=/dev/sdb of=/dev/sdc bs=1 count=446

dd if=/dev/sdb of=/dev/sdc bs=512 seek=1 skip=1 count=2047

Add the new volumes

vol copy ubuntu-11-04:boot ubuntu-11-04:ISO2CLASS.boot --overwrite --force
vol copy ubuntu-11-04:usr ubuntu-11-04:ISO2CLASS.usr --overwrite --force

-- Main.PavelGeorgiev - 08 May 2012

How-to create a managed Ubuntu 10.04 appliance

PavelGeorgiev — Fri, 18 May 2012 18:56:35 GMT

These are the steps to create a managed ubuntu 10.04.4 appliance using iso2class/hvm2pv. This process is meant to be run on a AppLogic 3.0 grid or newer, if you want to execute it on an older version, you may have to manually install APK instead of using hvm2pv. This could be used for both 32-bit and 64-bit versions.

Run iso2class

util iso2class app_name=ubuntu-10-04 iso_volume1=ubuntu-10.04.4-server-amd64.iso install_size=2G console_type=graphic os=linux-64 virt_mode=xen_hvm,vmware

Open the graphical console and complete the installation.

Few important things:
- no need to configure network during the install
- use a manual partitioning as follows:
/, primary, 500MB, ext3
/usr, primary, 1.6GB, ext3
- make sure you install openssh-server and libc6-i386 (needed only for 64-bit appliance, you will have to go to manual package selection for this) packages.
- install grub in the MBR (thats the default choice)

Once the installation is complete, go back to the iso2class console and proceed with the install. When prompted, say you want to run hvm2pv now.

While hvm2pv is running, it will prompt you with the following question:

Code:

Do you want to set up a new root password for text console login?

Say 'Y'. Before proceeding, login to the appliance that hvm2pv is running (it should be something like hvm2pv_pg-ubuntu-10-04_5133:main.LINUX64) and execute the following:

Code:

# root mount point of the boot partition, this needs to be change accordingly

ROOT_MOUNT=/mnt/vol/hdc1

 

#Update grub2 configuration:

mount -o bind /dev/ $ROOT_MOUNT/dev/

mount -o bind /sys/ $ROOT_MOUNT/sys/

mount -o bind /proc/ $ROOT_MOUNT/proc/

sed -e 's/timeout=-1/timeout=2/' -i $ROOT_MOUNT/etc/grub.d/00_header

chroot $ROOT_MOUNT/ update-grub



# Create PV grub configuration the root device and kernel/initrd paths may be different, check the grub2 config for details ($ROOT_MOUNT/boot/grub/grub.cfg):

cat > $ROOT_MOUNT/boot/grub/menu.lst  << EOF

default 0

timeout 1



title AppLogic Appliance

        root    (hd0,0)

        kernel  /boot/$(find $ROOT_MOUNT/boot/ -iname 'vmlinuz-2.6.32*' -printf '%f') root=UUID=$(blkid -o value -s UUID /dev/hdc1) ro console=hvc0

        initrd  /boot/$(find $ROOT_MOUNT/boot/ -iname 'initrd.img-2.6.32*' -printf '%f')

EOF



sed -i 's#\(/usr[[:blank:]]\+ext3[[:blank:]]\+defaults\)\([[:blank:]]\+\)[[:digit:]]\([[:blank:]]\+\)[[:digit:]]#\1,ro\20\30#g' $ROOT_MOUNT/etc/fstab



# move applogic_init service from runlevel S to 2345

chroot $ROOT_MOUNT update-rc.d -f applogic_init remove

chroot $ROOT_MOUNT update-rc.d -f applogic_init start 01 2 3 4 5 . stop 99 0 1 6 .

Code:

component ISO2CLASS

   {

   .category         = Generic

   .description      = "iso2class singleton"

   .config_mode      = dhcp

   .console          = "ssh:22,text,graphic"



   volume boot       : class           , boot           , dev  = /dev/sda  , type = instantiable

   volume usr        : class           , shared         , ro          , dev  = /dev/sdb          , type = common



   resource cpu      : min      = 0.05 , max      = 16  , dflt = 0.5

   resource mem      : min      = 128M , max      = 16G , dflt = 512M

   resource bw       : min      = 1M   , max      = 1G  , dflt = 1M



   input in          : protocol = any

   output out        : protocol = any

   output net        : gateway         , protocol = any

   output mon        : protocol = cce



   interface default



   virtualization

      {

      options       = "esx_os_name=rhel6-64"

      device_schema = /dev/sdX

      modes         = "vmware,xen_pv"

      }



   visual

      {

      color      = violet

      style      = medium

      size       = 3

      east       = ooo

      west       = i



      output out : orient = east

      input in   : orient = west

      output mon : orient = east

      output net : orient = east

      }

   }

Split the boot volume into two volumes:

vol create ubuntu-10-04:boot par1.fs=raw par1.size=500MB
vol create ubuntu-10-04:usr par1.fs=raw par1.size=500MB
vol copy ubuntu-10-04:ISO2CLASS.boot%par1 ubuntu-10-04:boot%par1 --fscpy
vol copy ubuntu-10-04:ISO2CLASS.boot%par2 ubuntu-10-04:usr%par1 --fscpy

Copy the MBR
vol manage ubuntu-10-04:ISO2CLASS.boot ubuntu-10-04:boot

Code:

dd if=/dev/sdb of=/dev/sdc bs=1 count=446

dd if=/dev/sdb of=/dev/sdc bs=512 seek=1 skip=1 count=2047

Add the new volumes

vol copy ubuntu-10-04:boot ubuntu-10-04:ISO2CLASS.boot --overwrite --force
vol copy ubuntu-10-04:usr ubuntu-10-04:ISO2CLASS.usr --overwrite --force

How-to create a managed RHEL 6.1 appliance

PavelGeorgiev — Fri, 18 May 2012 18:46:22 GMT

These are the steps to create a managed Centos 6.1 appliance using iso2class/hvm2pv. This process is meant to be run on a AppLogic 3.0 grid or newer, if you want to execute it on an older version, you may have to manually install APK instead of using hvm2pv. This could be used for both 32-bit and 64-bit versions.

Run iso2class

util iso2class app_name=rhel-61 iso_volume1=rhel-server-6.1-x86_64-dvd.iso mem=1G install_size=1G console_type=graphic os=linux-64 virt_mode=xen_hvm,vmware

Open the graphical console and complete the installation.
Few important things:
- if you are running that on an esx grid, the mouse will not work during the install, you will need to use the keyboard to complete the installation.
- use a manual partitioning as follows (create custom layout):
/, primary, 400MB, ext3
/usr, primary, 600MB, ext3
- package sleection - you will need the 'minimum' install (additional packages may be selected if desired, more disk space may be needed if you decide to include additional software)
- install grub in the MBR (thats the default choice)

Once the installation is complete, go back to the iso2class console and proceed with the install.

When iso2class gives you the following prompt:

Code:

Before continuing with the final modification of the singleton class

descriptor, please specify how CA AppLogic should manage the resulting

appliance:

   1.  Windows msi/APK is installed:  the appliance is fully managed

   2.  Windows msi/APK is NOT installed:  the appliance is unmanaged



Please specify a number 1-2 and then press [Enter]:

Before you answer that, open a new shell and execute:

vol manage rhel-61:iso_volume1 rhel-61:ISO2CLASS.boot

and execute the following in the filer:

Code:

cp -va /mnt/vol/Packages/wget*.rpm /mnt/vol2/par1/root/



# Execute the following only if you are installing a 64-bit OS

cp -va /mnt/vol/Packages/{nss-softokn-freebl-3,glibc-2}*i686.rpm /mnt/vol2/par1/root/

Exit the filer (wait for the vol manage opration to complete) and proceed with the iso2class install. When prompted, say you want to run hvm2pv now.

While hvm2pv is running, it will prompt you with the following question:

Code:

Do you want to set up a new root password for text console login?

Say 'Y'. Before proceeding, login to the appliance that hvm2pv is running (it should be something like hvm2pv_rhel-6.1_5133:main.LINUX64) and execute the following:

Code:

ROOT_MOUNT=/mnt/vol/hdc1

chroot $ROOT_MOUNT rpm -Uv /root/*rpm

rm -fv $ROOT_MOUNT/root/*rpm

ln -sf /etc/dhclient-enter-hooks $ROOT_MOUNT/etc/dhcp/dhclient-enter-hooks

sed -i 's#\(/usr[[:blank:]]\+ext3[[:blank:]]\+defaults\)\([[:blank:]]\+\)[[:digit:]]\([[:blank:]]\+\)[[:digit:]]#\1,ro\20\30#g' $ROOT_MOUNT/etc/fstab

sed -i $ROOT_MOUNT/boot/grub/menu.lst -e 's/ quiet/ quiet xen_emul_unplug=never/'

sed -i $ROOT_MOUNT/etc/sysconfig/selinux -e 's/^SELINUX=.*$/SELINUX=disabled/'



mount -o bind /dev/ $ROOT_MOUNT/dev/

mount -o bind /sys/ $ROOT_MOUNT/sys/

mount -o bind /proc/ $ROOT_MOUNT/proc/



# Install grub

chroot $ROOT_MOUNT grub --batch --no-floppy << EOF

device (hd0) /dev/hdc

root (hd0,0)

setup (hd0)

quit

EOF

Code:

component ISO2CLASS

   {

   .category         = Generic

   .description      = "iso2class singleton"

   .config_mode      = dhcp

   .console          = "ssh:22,text,graphic"



   volume boot       : class           , boot           , dev  = /dev/sda  , type = instantiable

   volume usr        : class           , shared         , ro          , dev  = /dev/sdb          , type = common



   resource cpu      : min      = 0.05 , max      = 16  , dflt = 0.5

   resource mem      : min      = 128M , max      = 16G , dflt = 512M

   resource bw       : min      = 1M   , max      = 1G  , dflt = 1M



   input in          : protocol = any

   output out        : protocol = any

   output net        : gateway         , protocol = any

   output mon        : protocol = cce



   interface default



   virtualization

      {

      options       = "esx_os_name=rhel6-64"

      device_schema = /dev/sdX

      modes         = "vmware,xen_pv"

      }



   visual

      {

      color      = violet

      style      = medium

      size       = 3

      east       = ooo

      west       = i



      output out : orient = east

      input in   : orient = west

      output mon : orient = east

      output net : orient = east

      }

   }

Split the boot volume into two volumes:

vol create rhel-61:boot par1.fs=raw par1.size=300MB
vol create rhel-61:usr par1.fs=raw par1.size=500MB
vol copy rhel-61:ISO2CLASS.boot%par1 rhel-61:boot%par1 --fscpy
vol copy rhel-61:ISO2CLASS.boot%par2 rhel-61:usr%par1 --fscpy

Copy the MBR
vol manage rhel-61:ISO2CLASS.boot rhel-61:boot

Code:

dd if=/dev/sdb of=/dev/sdc bs=1 count=446

dd if=/dev/sdb of=/dev/sdc bs=512 seek=1 skip=1 count=2047

Add the new volumes

vol copy rhel-61:boot rhel-61:ISO2CLASS.boot --overwrite --force
vol copy rhel-61:usr rhel-61:ISO2CLASS.usr --overwrite --force

How-to create a managed Centos 6.1 appliance

PavelGeorgiev — Thu, 17 May 2012 23:32:48 GMT

These are the steps to create a managed Centos 6.1 appliance using iso2class/hvm2pv. This process is meant to be run on a AppLogic? 3.0 grid or newer, if you want to execute it on an older version, you may have to manually install APK instead of using hvm2pv. This could be used for both 32-bit and 64-bit versions.

Run iso2class

util iso2class app_name=Centos-61 iso_volume1=CentOS-6.1-x86_64-bin-DVD1.iso mem=1G install_size=1G console_type=graphic os=linux-64 virt_mode=xen_hvm,vmware

Open the graphical console and complete the installation.

Few important things:
- if you are running that on an esx grid, the mouse will not work during the install, you will need to use the keyboard to complete the installation.
- use a manual partitioning as follows (create custom layout):
/, primary, 400MB, ext3
/usr, primary, 600MB, ext3
- package sleection - you will need the 'minimum' install (additional packages may be selected if desired, more disk space may be needed if you decide to include additional software)
- install grub in the MBR (thats the default choice)

Once the installation is complete, go back to the iso2class console and proceed with the install.

When iso2class gives you the following prompt:

Code:

Before continuing with the final modification of the singleton class

descriptor, please specify how CA AppLogic should manage the resulting

appliance:

   1.  Windows msi/APK is installed:  the appliance is fully managed

   2.  Windows msi/APK is NOT installed:  the appliance is unmanaged



Please specify a number 1-2 and then press [Enter]:

Before you answer that, open a new shell and execute:
vol manage Centos-61:iso_volume1 Centos-61:ISO2CLASS.boot
and execute the following in the filer:

Code:

cp -va /mnt/vol/Packages/wget*.rpm /mnt/vol2/par1/root/



# Execute the following only if you are installing a 64-bit OS

cp -va /mnt/vol/Packages/{nss-softokn-freebl-3,glibc-2}*i686.rpm /mnt/vol2/par1/root/

Code:

Do you want to set up a new root password for text console login?

Say 'Y'. Before proceeding, login to the appliance that hvm2pv is running (it should be something like hvm2pv_CentOS-6.1_5133:main.LINUX64) and execute the following:

Code:

ROOT_MOUNT=/mnt/vol/hdc1

chroot $ROOT_MOUNT rpm -Uv /root/*rpm

rm -fv $ROOT_MOUNT/root/*rpm

ln -sf /etc/dhclient-enter-hooks $ROOT_MOUNT/etc/dhcp/dhclient-enter-hooks

sed -i 's#\(/usr[[:blank:]]\+ext3[[:blank:]]\+defaults\)\([[:blank:]]\+\)[[:digit:]]\([[:blank:]]\+\)[[:digit:]]#\1,ro\20\30#g' $ROOT_MOUNT/etc/fstab

sed -i $ROOT_MOUNT/boot/grub/menu.lst -e 's/ quiet/ quiet xen_emul_unplug=never/'

sed -i $ROOT_MOUNT/etc/sysconfig/selinux -e 's/^SELINUX=.*$/SELINUX=disabled/'



mount -o bind /dev/ $ROOT_MOUNT/dev/

mount -o bind /sys/ $ROOT_MOUNT/sys/

mount -o bind /proc/ $ROOT_MOUNT/proc/



# Install grub

chroot $ROOT_MOUNT grub --batch --no-floppy << EOF

device (hd0) /dev/hdc

root (hd0,0)

setup (hd0)

quit

EOF

Code:

component ISO2CLASS

   {

   .category         = Generic

   .description      = "iso2class singleton"

   .config_mode      = dhcp

   .console          = "ssh:22,text,graphic"



   volume boot       : class           , boot           , dev  = /dev/sda  , type = instantiable

   volume usr        : class           , shared         , ro          , dev  = /dev/sdb          , type = common



   resource cpu      : min      = 0.05 , max      = 16  , dflt = 0.5

   resource mem      : min      = 128M , max      = 16G , dflt = 512M

   resource bw       : min      = 1M   , max      = 1G  , dflt = 1M



   input in          : protocol = any

   output out        : protocol = any

   output net        : gateway         , protocol = any

   output mon        : protocol = cce



   interface default



   virtualization

      {

      options       = "esx_os_name=rhel6-64"

      device_schema = /dev/sdX

      modes         = "vmware,xen_pv"

      }



   visual

      {

      color      = violet

      style      = medium

      size       = 3

      east       = ooo

      west       = i



      output out : orient = east

      input in   : orient = west

      output mon : orient = east

      output net : orient = east

      }

   }

Split the boot volume into two volumes:

vol create Centos-61:boot par1.fs=raw par1.size=300MB
vol create Centos-61:usr par1.fs=raw par1.size=500MB
vol copy Centos-61:ISO2CLASS.boot%par1 Centos-61:boot%par1 --fscpy
vol copy Centos-61:ISO2CLASS.boot%par2 Centos-61:usr%par1 --fscpy

Copy the MBR
vol manage Centos-61:ISO2CLASS.boot Centos-61:boot

Code:

dd if=/dev/sdb of=/dev/sdc bs=1 count=446

dd if=/dev/sdb of=/dev/sdc bs=512 seek=1 skip=1 count=2047

Add the new volumes

vol copy Centos-61:boot Centos-61:ISO2CLASS.boot --overwrite --force
vol copy Centos-61:usr Centos-61:ISO2CLASS.usr --overwrite --force

Windows folder sharing between servers

luisr — Thu, 17 May 2012 20:25:54 GMT

Hi,
I have an application with 3 windows servers. There's a service that requires that a particular folder at each server should be shared between all.
What are your suggestions to implement this scenario?

Windows folder share

luisr — Thu, 17 May 2012 18:49:26 GMT

move to http://forum.3tera.com/showthread.php?t=5061

Applogic and NAS need to be friends

Jcraft — Wed, 16 May 2012 18:00:17 GMT

I am currently trying to set up windows 2008 server that connects to 4 external NAS devices via NFS (Ip only).The customer does not want any internet access to the NAS...I guess im confused because I really dont see how this is done via the NAS appliances on the grid. Has anybody done this? if so can you share an example, or anything

THANKS!

Common causes of grid instability

PeterNic — Wed, 16 May 2012 17:47:37 GMT

Hi, I thought I would share some common reasons we have seen when troubleshooting grids that appear unstable. In all of items below, the issue has been either configuration error or missing mandatory hotfix. In all cases, CA's support can help diagnose the issues.

Here are the top possible reasons for the failure/instability (in more that 50-60% of the cases it has been the first one below):

spanning tree (STP) is not properly/fully disabled on the backbone switch. AppLogic 2.9 as well as 3.5 beta have built-in STP detection; 3.0 and 3.1 do not. That said, we have seen some switches on which STP cannot be disabled and/or cannot be detected programmatically (very rare but exist � IIRC, low end, older premium brand switches; support knows them)
missing one or more mandatory hotfixes (please check the release notes of the AppLogic release you use)
having pre-3.1 AppLogic grids on the same backbone that don�t have the mandatory hotfix hf3240 installed � this is very insidious, since this rare condition on one unpatched grid can cause failure on other, perfectly patched grids. You should know if there are other grids on the backbone and whether they have hf3240 applied (if 2.9 grid, then hf3240 has to be re-applied if new servers are added to the grid after the hotfix is installed; not needed in 3.0); the condition can also be easily detected by running network capture or reviewing the statistics on the switches.
some combinations of disk controllers and hard drives (popular brand) have firmware problems under load; typically disabling NCQ fixes the problem. Support knows the procedure for detecting the problem and turning NCQ off.
server BIOS is not up to date � while this is a rare issue, we have seen it several times, especially on higher end servers that were purchased early in the production run. Similarly, bad memory and/or bad hard drives can cause instability.
backbone/switch configuration is unusual/incorrect. For example, if the backbone switch is uplinked or shared between multiple backbones (via VLANs), it is important to use the backbone ID and grid ID correctly to prevent MAC address conflicts (which will wreak havoc on multiple grids). In one case, we even found an inadvertent connection between the external and the backbone networks (by some clever but incorrect VLAN setup). AppLogic 3.5 provides some additional network topology diagnostic checks/heuristics to help avoid these but if you are doing something unusual (i.e., anything other than plain configuration), it is worth taking a look at.
certain switches have vendor-specific STP/broadcast storm control features that has been identified as problematic. Check out discussions on this forum and the AppLogic user group.

I hope this is helpful. Please feel free to comment/augment expand.

Best regards,
- Peter

Failed to allocate resources

luisr — Tue, 15 May 2012 12:36:13 GMT

When stopping an application we notices the message Log "...failed to destroy VNA group"
Now when trying to start the same application it reports:
"...failed to allocate resources for component"
"...failed to create VNA"

It's related to the server where the error occurored. I have to assign the appliance affinity to another server to be able to boot.

adding additional ips to a vds

sparkjohn — Mon, 14 May 2012 19:42:31 GMT

Hello,

In my cpanel VDS application, I would like to add a few additional ips other than primary and secondary ips. Unfortunately applogic doc does not have a straight forward method to do this. I tried to modify the application boundary and added a third ip property value. But I think that is not enough for it to work. So I wrote a script and added it to /etc/init.d/applogic_init. But that did not work.

============
#!/bin/bash
### script to autromatically add the additional public ips to the server ###
new_ips=`cat /etc/applogic.sh |sed -e '/primary_ip/d' -e '/secondary_ip/d'|grep "_ip="|sed -e 's/=/ /g' -e "/''/d" |awk '{print $2}'`
ip_nums=`echo $new_ips|tr ' ' ' '|wc -l`
#echo $ip_nums
for i in $new_ips
do
if [ $ip_nums -gt 0 ]
then
ifconfig eth0:$ip_nums $i netmask 255.255.255.192 up
fi
let ip_nums=$ip_nums-1
done
=============

Can anybody please explain a better way to do this?

Regards
John

What is the right way to expend a boot volume of VDS

LPG — Fri, 11 May 2012 10:07:18 GMT

Hi,

I have provisioned a CentOS VDS before but now I need to expend the disk size of VDS. I use the vol resize to resized the volume and get success message in grid shell. When I log into the VDS and run fdisk command, fdisk show the new size but with following messages:

Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 2) logical=(0, 1, 9)
Partition 1 has different physical/logical endings:
phys=(391, 127, 56) logical=(877, 55, 56)

Does my steps are wrong and how can I fix the problem?

Many thanks.

Security Hotfix hf6868 released for CA AppLogic 3.0.30 GA, 3.1.14 GA, 3.5.7 Beta

EricT — Wed, 09 May 2012 22:35:09 GMT

This hotfix resolves SCR 6868 where a regular user with valid login access to a CA AppLogic grid can escalate his/her permissions. This hotfix should be applied to all CA AppLogic 3.0.30 GA/3.1.14 GA/3.5.7 Beta grids.

This vulnerability cannot be exploited without a valid login to the grid. CA AppLogic 2.9 and all prior versions are not vulnerable to this issue.

hf6868 is a mandatory hotfix for CA AppLogic 3.0.30 GA/3.1.14 GA/3.5.7 Beta.

Note: A grid reboot is not required after applying this hotfix; the hotfix takes effect immediately after it is applied to a grid.

3.1 Supermicro IPMI incompatible?

samware — Tue, 08 May 2012 17:23:36 GMT

Howdy.

I am attempting to setup a tiny AppLogic environment with some Supermicro systems, and I am having a bear of a time. Apparently my BMC/IPMI is not compatible with AppLogic's scripts. :(

Server boots to PXE linux, runs scripts, and waits instead of powering off. Checking the BFC control panel I can see that the server has been quarantined and marked as not having power control. "Compute host has no power controller and will never be shut down..."

First thing I did was statically assign IPs to the IPMI controllers--all within the ranges I specified on the BFC's power network. I also ensured the BFC was plugged into the power network.

My BFC's "Administration->BFC->Backup IPMI Authentication" properties are set to my IPMI admin credentials.

Sometimes AppLogic's PXE linux will create a "PowerAdmin__BFC" on my IPMI controllers, which I will then give admin privileges and reboot the system but to no avail.

Changing the BFC's "Administration->BFC->IP Authority" from "User" to "System" makes no difference. I would prefer not to have to enter an IP in BIOS for IPMI thus "System" setting would be nice.

Nothing I do solves the issue.

Hardware:
IPMI controller seems to be "Winbond WPCM450"
Firmware version is 2.36
http://www.nuvoton.com/NuvotonMOSS/C...d-faea27fbf1e2

Motherboard is "H8DG6-F"
http://www.supermicro.com/Aplus/moth...x0/H8DG6-F.cfm

Any pointers are greatly appreciated.
-bo

cannot start application - Volume in use

luisr — Mon, 07 May 2012 12:43:04 GMT

Hello,
Somehow after stopping an application the volumes of an appliance remained 'in use' and we cannot start the applications because of that.
Is there a way to unlock this?

How to access guest VM console by API?

tonyjun — Wed, 02 May 2012 03:41:39 GMT

Or other method, not grid gui contoller.