VDS_Win03S, VDS_Win0364S, VDS_Win03E, VDS_Win0364E

VDS_Win03DC, VDS_Win0364DC, VDS_Win03W

Virtual Dedicated Server Applications

Functional overview

VDS_Win03S, VDS_Win0364S, VDS_Win03E, VDS_Win0364E, VDS_Win03DC, VDS_Win0364DC, and VDS_Win03W 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.

Boundary

Resources

32-bit Windows Server 2003 VDSs

64-bit Windows Server 2003 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

Windows Server 2003 based VDSs

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	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

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

app provision VDS_WIN03S_r1 ExampleClient \
    user=Exampleuser user_pw=abcd1234 admin_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 VDS_WIN03S.boot.size=10G

3rd party open source software used inside of the appliance

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

• Test Plan
• Implementation Design

Questions and Comments

To post questions and/or comments, visit our forum.

-- BeckyH - 17 Jun 2009