AppLogic 2.3 Beta Documentation The latest production release is AppLogic 2.4.7 VPS_CentOS50, VPS64_CentOS50, VPS_CentOS51, VPS64_OSOL, VPS_SOL10: Virtual Private Server Applications
Functional overview
VPS_CentOS50, VPS64_CentOS50, VPS_CentOS51, VPS64_OSOL, and VPS_SOL10 are dedicated virtual private server applications. They are designed to be deployed as standalone applications with no catalog parts.
VPS applications can scale from approximately one twentieth of a physical server to a full physical server depending on the resouce needs of the end user.
VPS applications include a basic build environment with GCC.
With CentOS based VPS's, any of the other CentOS packages can be installed by the end user, simply by running
yum -y install <package> while running as
root user.
With Solaris based VPS's, additional packages can be installed using
pkgadd.
VPS applications are provided to allow hosting providers a quick and easy way to offer a dedicated server offering on the
AppLogic Grid.
VPS applications configure themselves through properties on first boot. The initial user is created and the root password is placed in a file (
/home/<user>/su.txt). VPS applications can be reset to their default properties by deleting
/appliance/passwd.stamp from the appliance and restarting the application.
| Application | Latest Version | OS | Notes |
|---|
| VPS_CentOS50 | 1.3.2-1 | CentOS 5 | |
| VPS64_CentOS50 | 1.1.2-1 | CentOS 5 (64 bit) | |
| VPS_CentOS51 | 1.1.2-1 | CentOS 5.1 | |
| VPS64_OSOL | 1.0.1 | OpenSolaris build 2008.05 | |
| VPS_SOL10 | 1.0.1 | Solaris 10 build GA | This application is currently not distributed with AppLogic. Please contact Technical Support for more information. |
Boundary
Resources
Linux based VPS's:
OpenSolaris VPS
Solaris 10 VPS
Terminals
The
external interface is enabled. It is used for incoming and outgoing traffic. Its network settings are configured through properties.
The
default interface is enabled. It is used for maintenance (incoming ssh connections from the controller).
User Volumes
None
Properties
| Property name | Type | Description |
|---|
hostname | String | Defines the hostname to assign. This property is mandatory. |
user | String | Defines the user to be created on provioning of the application. This property is mandatory. |
user_pw | String | Defines the password of the user account to be created. This property is mandatory. |
root_pw | String | Defines the password of the root account. it will be set on first boot and written to /home/<user>/su.txt This property is mandatory. |
primary_ip | IP Address | Defines the primary IP address of the external interface of the appliance. This property is mandatory. |
secondary_ip | IP Address | Defines the secondary IP address of the external interface of the appliance. |
netmask | IP address | Defines the network mask of the external interface. This property is mandatory. |
gateway | IP address | Defines the default IP network gateway (router) for the external interface. The gateway address can be outside the network specified by netmask. To use a gateway that does not expose an IP and serves as proxy arp, set this property to 0.0.0.0. This property is mandatory. |
dns1 | IP address | Defines the primary nameserver. This property is mandatory. |
dns2 | IP address | Defines the secondary server. |
dns3 | IP address | Defines the third server. |
Typical Usage
The folowing shows the typical useage of the VPS_CentOS51 application
VPS_CentOS51 is to be used by hosting providers in order to offer dedicated servers using
AppLogic without the need for any other 3rd party software or licenses.
VPS_CentOS51 is distirbuted only as an application containing a single instance of the appliance and does not reside in any catalogs.
Notes
By way of example, provisioning VPS_CentOS51 can be done by running a single command that can be automated from the providers portal.
app provision VPS_CentOS51 ExampleClient \
user=Exampleuser user_pw=abcd1234 root_pw=acbde12345 \
primary_ip=209.100.100.12 netmask=255.255.255.0 gateway=209.100.100.1 \
hostname=mydomain.com dns1=209.101.1.2 dns2=209.101.1.3 \
cpu.dflt=0.50 mem.dflt=1G VPS.boot.size=10G
The OpenSolaris and Solaris 10 VPS's have
zpool_import installed as a legacy service. On stop, this service executes
zpool export poolname on all ZFS pools which do not include a bootable dataset. On start, this service executes
zpool import -a.
The
zpool_import service leaves ZFS pools in an exported (portable) state when an appliance is stopped. This facilitates moving and copying pools from one application to another as well as modifying pools using the standard 3t shell
vol commands, e.g.,
vol resize,
vol copy, etc.
To manage ZFS pools manually, disable this service.
OpenSolaris? appliances use zpool version 10 and zfs version 2.
Solaris 10 appliances use zpool version 4 and zfs version 1. To use zfs pools with these appliances, create them from raw volumes rather than through the CLI
vol create command. The CLI
vol create operation creates the root zfs dataset using zfs version 2 which is not backwards compatible.
Limitations/Requirements
The
/appliance directory MUST be left intact. Any changes to any files in this directory can cause the appliance to stop working.
Preventing
vmad or
vme from the
/appliance directory from running on start will cause the appliance to stop working (on next restart).
Kernel updates and replacements should be based on AppLogic-provided kernel sources.
The
/root/.ssh/authorized_keys file should not be modified; it will be overwritten by the build system at runtime.
Related documents
- VPS64_CentOS50
- VPS_CentOS51
- VPS64_OSOL
- VPS_SOL10
Questions and Comments
To post questions and/or comments for this application, visit our
forum.
--
NetClime - 21 Mar 2008
AppLogic23 Web