AppLogic 2.9 Documentation The latest production release is AppLogic 3.0.30 VDS_Win03S, VDS_Win0364S, VDS_Win03E, VDS_Win0364E
VDS_Win03DC, VDS_Win0364DC, VDS_Win03W
VDS_Win08S, VDS_Win0864S, VDS_Win08E, VDS_Win0864E
VDS_Win08DC, VDS_Win0864DC, VDS_Win08W, VDS_Win0864W
Virtual Dedicated Server Applications
Functional overview
VDS_Win03S, VDS_Win0364S, VDS_Win03E, VDS_Win0364E, VDS_Win03DC, VDS_Win0364DC, VDS_Win03W, VDS_Win08S, VDS_Win0864S, VDS_Win08E, VDS_Win0864E, VDS_Win08DC, VDS_Win0864DC, VDS_Win08W, and VDS_Win0864W are virtual dedicated server applications. They are designed to be deployed as standalone applications with no catalog parts.
VDS applications can scale from approximately one tenth of a physical server to a full physical server depending on the resource needs of the end user.
VDS applications are provided to allow hosting providers a quick and easy way to offer a dedicated server offering on the AppLogic Grid.
VDS 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). VDS applications can be reset to their default properties by deleting /appliance/passwd.stamp from the appliance and restarting the application.
Support for Windows Server 2008 based appliances and applications is available in versions of AppLogic later than 2.9.1.
| Application | Latest Version | OS | Notes |
| VDS_Win03S, VDS_Win03E, VDS_Win03DC, VDS_Win03W | 1.2.4-1 | Windows Server 2003 Standard/Enterprise/DataCenter/Web Edition R2 32-bit | These applications are not installed on the AppLogic grid by default. Please see the Windows Installation Reference for instructions on how to install these applications |
| VDS_Win0364S, VDS_Win0364E, VDS_Win0364DC | 1.2.4-1 | Windows Server 2003 Standard/Enterprise/DataCenter Edition R2 64-bit | These applications are not installed on the AppLogic grid by default. Please see the Windows Installation Reference for instructions on how to install these applications |
| VDS_Win08S, VDS_Win08E, VDS_Win08DC | 1.2.4-1 | Windows Server 2008 Standard/Enterprise/DataCenter Edition without Hyper-V SP2 32-bit | These applications are not installed on the AppLogic grid by default. Please see the Windows Installation Reference for instructions on how to install these applications |
| VDS_Win08W | 1.2.4-1 | Windows Server 2008 Web Edition SP2 32-bit | These applications are not installed on the AppLogic grid by default. Please see the Windows Installation Reference for instructions on how to install these applications |
| VDS_Win0864S, VDS_Win0864E, VDS_Win0864DC, VDS_Win0864W | 1.2.4-1 | Windows Server 2008 Standard/Enterprise/DataCenter/Web Edition R2 64-bit | These applications are not installed on the AppLogic grid by default. Please see the Windows Installation Reference for instructions on how to install these applications |
Boundary
Resources
32-bit Windows Server 2003 VDSs
64-bit Windows Server 2003 VDSs
32-bit Windows Server 2008 VDSs
64-bit Windows Server 2008 VDSs
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.
The appliance hostname cannot be longer than 15 characters. Setting the hostname property to more than 15 characters will result in a hostname truncated to the 15th character. 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. |
admin_pw | String | Defines the password of the Administrator (and Cygwin root) account. it will be set on first boot and written to /home/<user>/su.txt This property is mandatory. |
primary_ip | String | Defines the primary IP address (v4 or v6) of the external interface of the appliance. This property is mandatory. |
secondary_ip | String | Defines the secondary IP address (v4 or v6) of the external interface of the appliance. Default: (empty). |
netmask | IP address | Defines the network mask of the external interface. This property should be defined if IPv4 is used. Default: (empty). |
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 should be defined if IPv4 is used. Default: (empty). |
ipv6_gateway | String | Defines the default IPv6 network gateway (router) for the external interface. This property should be defined if IPv6 is used. Default: (empty). |
dns1 | String | Defines the primary nameserver (v4 or v6). This property is mandatory. |
dns2 | String | Defines the secondary server (v4 or v6). Default: (empty). |
dns3 | String | Defines the third server (v4 or v6). Default: (empty). |
Typical Usage
The following shows the typical usage of the VDS_WIN03S application
Windows VDS applications are 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.
Windows VDS applications are each distributed as an application containing a singleton instance - they do not use any catalog class appliances.
Notes
By way of example, provisioning VDS_WIN03S can be done by running a single command that can be automated from the providers portal.
app provision VDS_WIN03S_r14 ExampleClient \
user=Exampleuser user_pw=abcd1234 admin_pw=acbde12345 \
primary_ip=fe80::1/64 secondary_ip=209.100.100.12 netmask=255.255.255.0 gateway=209.100.100.1 \
ipv6_gateway=fe80::10 hostname=mydomain.com dns1=fe80::5 dns2=209.101.1.3 \
cpu.dflt=0.50 mem.dflt=1G VDS_WIN03S.boot.size=10G
3rd party open source software used inside of the appliance
Windows VDS applications use the following 3rd party/open source packages from Cygwin in addition to any 3rd party/open source packages which may be installed with Windows itself.
To see the full list of open source packages used in Windows VDS applications, please see its implementation design.
Windows
Please see the Windows Appliance Reference for significant details on the operation of Windows appliances under AppLogic.
Limitations/Requirements
The following directories MUST be left intact. Any changes to any files in these directories can cause the appliance to stop working.
- C:\appliance
- C:\cygwin
- C:\Program Files\Halsign TurboGate?
Preventing vmad or vme from running on start will cause the appliance to stop working (on next restart).
Related documents
Questions and Comments
To post questions and/or comments related to VDS_Win03x, visit our forum.
To post questions and/or comments related to VDS_Win08x, visit our forum.
-- OlegSmolov - 11 May 2010
Copyright © CA 2005-2012. All Rights Reserved.