r4 - 30 Apr 2008 - 19:20:20 - EricTYou are here: Wiki >  AppLogic23 Web > RefAppsVPS64CentOS50Cid
ALERT! AppLogic 2.3 Beta Documentation The latest production release is AppLogic 3.0.30

Implementation Notes

Base Class

The base class for the VPS64_CentOS50 singleton is the LINUX64 appliance (64-bit CentOS 5.0).

Class Volume

The volume configuration for the VPS64_CentOS50 singleton is determined by the base class image from which it is created. The VPS64_CentOS50 appliance is not sensitive to the volume configuration and will work on most any setup. The setup chosen for the 1.0. release is as follows:

  • boot volume: 2 GB, mounted as "/", writeable, instantiable
The boot volume contains a basic Linux installation as the one present on the LINUX64 appliance.

Packages

VPS64_CentOS50 includes the same packages as LINUX64.

Contents of the release directory

Exported application image

  • VPS64_CentOS50_r1-1.1.1-1.tar.bz2

Application sources

  • VPS64_CentOS50_r1-1.1.1-1-src.tar.bz2: tar of all the scripts used to recreate the application

Tests

  • VPS64_CentOS50_r1-tst.tar.bz2: VPS64_CentOS50 test scripts

Re-install Procedure

Here are the steps to create a VPS64_CentOS50 application from a LINUX64 appliance on an AppLogic2.AppLogic grid (ALERT!This requires maintainer access to the grid):

  1. From the AppLogic2.AppLogic Editor, create an application named VPS64_CentOS50 with a LINUX64.
  2. Branch the LINUX64.
  3. Copy and uncompress VPS64_CentOS50_r1-1.1.1-1-src.tar.bz2 on the grid controller.
  4. Execute the mkgsc64.sh script: sh mkgsc64.sh, which performs the following:
    • renames the LINUX64 class in the VPS64_CentOS50 application to VPS_CentOS50
    • updates the VPS_CentOS50 class descriptor to setup the correct boundary
    • updates the main and package descriptors of the VPS64_CentOS50 application
    • mount the VPS_CentOS50 boot volume through 3tctl mount sv and mount the returned device with execute access with mount
    • copy VPS_CentOS50-specific scripts to the VPS_CentOS50 boot volume
    • unmount the VPS_CentOS50 boot volume (via umount and 3tctl umount sv)
    • export the VPS64_CentOS50 application
    • tar and zip the VPS_CentOS50 application export
    • NOTE: All operations are logged to mkgsc64.log. Check the log in case of any failures.
  5. Find the VPS64_CentOS50 release tar, VPS64_CentOS50_r1-1.1.1-1.tar.bz2, under /vol/_impex.

Theory of Operation

VPS64_CentOS50 is a dedicated grid server application that is designed to be deployed as a standalone application.

Configuration

External network setup

VPS64_CentOS50 has an external interface which allows the appliance to communicate with the outside world. VPS64_CentOS50 has an additional service, appliance_netsetup, which invokes the /appliance/appliance_netsetup.sh script to configure the external interface.

The /appliance/appliance_netsetup.sh script assigns the primary_ip and secondary_ip (if one is specified) to the external interface. This script also sets the netmask and gateway, as well as setting the DNS servers.

User and passwords

The root password and the user name and password are setup through the /appliance/change_pwd script on the initial boot of VPS64_CentOS50 and when the /appliance/passwd.stamp file is missing. This script is invoked by the /appliance/appliance.sh script.

In order to update the user, user_pw, or root_pw properties and have those changes take affect, the /appliance/passwd.stamp file must be deleted prior to restarting VPS64_CentOS50.

Log Files

VPS64_CentOS50 does not create any additional logs.

Important Notes

None

-- MinhQ - 26 Sep 2007

 
Copyright © CA 2005-2011. All Rights Reserved.
%