Reference Information › Marketplace Catalog Reference Guide › Virtual Dedicated Server Application Templates › Fedora

Fedora

Functional Overview

VDS_Fedora16_r2, VDS64_Fedora16_r2 , VDS_Fedora17_r2, VDS64_Fedora17_r2, VDS_Fedora18_r2, and VDS64_Fedora18_r2 are dedicated virtual server applications. They are designed to be deployed as standalone applications with no catalog parts.

The VDS applications provide hosting providers a quick and easy way to offer a dedicated server offering on the CA AppLogic grid. Depending on your resource needs, the applications can scale from approximately one twentieth of a physical server to a full physical server.

VDS applications include a basic build environment with GCC, if available. With these VDSs, you can install any Fedora package simply by using yum or installed directly with rpm while running as root user.

The 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. You can reset the VDS applications to their default properties by deleting /appliance/passwd.stamp from the appliance and restarting the application.

When configuring the application, you can specify multiple IP addresses for a single interface. For example, you can run two identical applications on the same grid, but on separate servers as well as on different grids, if the IP address is accessible from both grids. In addition, you can specify the DNS settings instead of allowing the application to inherit the DNS settings from the grid. For additional information on configuring the application, refer to the Application Configuration section of the User Interface Reference.

Boundary

Resources

Terminals

There are no terminals.

The raw interface is enabled. You must configure the raw interface in the GUI before starting the application. These applications use the multiple external interfaces feature.

The default interface is enabled. It is used for maintenance, such as incoming ssh connections from the controller.

User Volumes

None

Properties

Typical Usage

The VDS is used by hosting providers to offer dedicated servers using AppLogic without the need for any other third party software or licenses.

The VDS is distributed only as an application containing a single instance of the appliance and does not reside in any catalogs.

Notes

By way of example, provisioning the VDS can be done by running a single command that can be automated from the provider's portal.

app provision VDS_Fedora18_r2 ExampleClient \ 

user=Exampleuser user_pw=abcd1234 root_pw=acbde12345 \ 
hostname=mydomain.com iface.ext=191.202.144.52 \
cpu.dflt=0.50 mem.dflt=1G VDS_Fedora18.boot.size=10G 

Limitations and Requirements

The /appliance directory must remain intact. Any changes to any files in this directory can cause the appliance to stop working.

The /root/.ssh/authorized_keys file should not be modified. It will be overwritten by the build system at runtime.

Error Messages

In case of application startup failure, the following errors may be logged to the system log:

Open Source and Third Party Software used Inside the Application

The VDS_Fedora applications do not use any open source packages in addition to those of their base Fedora releases.