Reference Information › CA AppLogic Support Knowledge Base › Overview of Support Knowledge Base › How to Convert a Red Hat Based Managed app to VDS in 3.x

How to Convert a Red Hat Based Managed app to VDS in 3.x

This article is the instruction to convert a Redhat based managed app to VDS in 3.x. If appliance is not the manged app yet, please execute hvm2pv to install APK unpon app or manually install APK in according to Applogic online bookshelf.

Before the conversion, it's always recommended to save a copy of original app.

Procedure

1. Provision a VDS instance from CentOS VDS template carried by Applogic. If you would like convert a 64 bit app to VDS, please process provision using 64 bit VDS template.
2. Copy below files from VDS instance provisoned from CentOS tmplate to target app which you plan to convert to VDS.

   /etc/rc.d/init.d/applogic_appliance
   /etc/sysconfig/applogic_appliance
   /appliance/*
   

   if target app has files with same name and path, move orignal files to other folder. After template is created and tested, remove them.

   It's recommended to use Linux command "scp" or 3t shell command "vol manage" to accomplish it. Here are sample of copy /appliance/* using "scp" and "vol manage"

   Process to use scp to copy /appliance/* accross app

   • Start up both VDS instance and target app
   • Exectue "comp list <VDS instance name> to display its component name
   • Execute "interface list <VDS component name> --verbose" to display all the interface name and ip attached to VDS component. Afterward, write down "default" interface ip address
   • Run scp to copy /appliance/* from VDS component to controller via VDS component "default" interface ip address. for instance, run "scp root@<VDS component default interface ip>:/appliance/* <any directory on controller>".
   • Connect to target app, create /appliance folder and make sure its onwer/permission are same as VDS
   • Repeat the step b and c with target app, then copy files downloaded from VDS component to target app. This time, scp command may looks like "scp < directory on controller which has files downloaded from VDS> root@<target app default interface ip>:/appliance/".
   • Connect to target app, make sure the owner and permission of /appliance/* are same as ones on VDS.

   Process of use "vol manage" to copy /appliance/* accross app

   • On controller, make sure VDS instance and target app have been stopped
   • Execute "vol list <app name> -a" against VDS instance and target app respectively to get their boot volume name
   • Execute "vol manage <VDS boot volume name> <target app boot volume name>". It will automatically connect to filer , mount VDS boot volume and target app boot volume(in "vol manage", volume of first parameter is usually mounted to /mnt/vol, the second one is mounted to /mnt/vol2)
   • In filer, Execute "cp -a /mnt/vol/appliance/* /mnt/vol2/".Afterward, verify the owner and permission of target /appliance/* same as source one
   • Exit filer("vol manage" context)

     Remove /appliance/passwd.stamp if it exists, otherwise, the user name and password configured in “property values” tab of application “configure” window will not take effect.

     if /var/log/appliance/ directory does not eist on the target volume, create it.l the owner user namd group are root, read/write/execute permission mode is 755.

3. Stop app then define the requested properties
   1. Define properties in application boundary
   2. Define same properties in appliance boundary
   3. In the appliance “property values” window, redirect the appliance properties to counterparts defined in the application boundary
   4. Verify the “property values” tab in application “configure” window
4. Delete in/out/net/mon interfaces, then enable external interface check box
5. Check “template” check box which converts VDS to the template.
6. Process a provision from new template to verify its functionality