For more details on operating system please read the CentOS 5.5 x64 image note.

Elastix is an open source Unified Communications Server software that brings together IP PBX, email, IM, faxing and collaboration functionality. It has Web interface and includes capabilities such as a Call Center software with predictive dialing.

Asterisk is software that turns an ordinary computer into a voice communications server. Asterisk is the world’s most powerful and popular telephony development tool-kit. It is used by small businesses, large businesses, call centers, carriers and governments worldwide.

HylaFAX is an enterprise-class system for sending and receiving facsimiles as well as for sending alpha-numeric pages.

Openfire is a real time collaboration (RTC) server licensed under the Open Source GPL. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.

Postfix is Wietse Venema’s mailer that started life at IBM research as an alternative to the widely-used Sendmail program.

CentOS is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor. .

To access the Elastix web interface:

1. Type http://$IP in your preferred web browser.
* $IP is meant to stand for the IP address of your web server.
2. Use admin as the login name in the Name field.
3. Enter the admin password into the Password field. The password is palosanto
4. Click Submit.

Elastix version is: 2.0.0-32
Asterisk version is: 1.6.2.10-1
HylaFAX version is: 4.3.9-0
Openfire version is: 3.5.1-3
Postfix version is: 2.3.3-2.1
The distributive: CentOS release 5.5 (Final)

The system runs under Gentoo 10.1 (2010) with the latest set of software built for amd64 platform. The kernel is the default XEN DomU version 2.6.18-xen-r12 designed for Gentoo distributive.

Image Information & Recommendation:

Storage: The ‘/’ file-system usage is about 1.5Gb (”world” sources included).
This ’stage3′ installation provide you an ability to design the system to be much suitable for your needs.
The recommended total disk size is 10Gb. Note: the disk size depend from applications and services you plan to run on the system

Memory: The system use ~45Mb of memory to run mandatory services like init, disk management, logging and networking. We recommend use at least 376-512Mb of RAM.

CPU and processes: ~40 processes run by default on the system for a minimal CPU load. The recommended CPU is >= 500 MHz

The installation is based on:

• CentOS 5.5 with the latest set of updates installed
• hardware platform i386
• BlueOnyx 5106R

For more details on operating system please read the “CentOS 5.5 x86_64” image notes.

BlueOnyx is a Linux distribution (based on CentOS v5.5) which aims at delivering a turnkey server appliance for webhosting.

Please find more about BlueOnyx fetatures and services provided.

Complete the installation

Please point your browser to http://<IP>/login to complete the BlueOnyx installation.
where, <IP> - main interface IP address

You will be prompted with the following step by step configuration:
1. License Agreement

2. System Settings:
- Network Settings
- Administaratior Settings (Username, Password)
- Language settings
- Date and Time Settings

3. Closing notes.

Just after that you will be forwarded to BlueOnyx administrator interface.

To enable remote root ssh connection:

Open on the Server Management Tab: Network Services -> Shell
Check SSH Root Login option on Enable SSH Server section.
Press Save to apply changes.

Log into BlueOnyx

Now can log into the BlueOnyx.
Please use user ‘admin’ and password specified during Complete the installation stage:
http://<IP>:444/login.php

Please check Secure Connect if required. Or try:
https://<IP>:81/login.php

Installation directory

When you done with post-install/configuration please remove (if required, to save the disk space) the installation directory.
Log into the box via ssh, or console as root, and run:

# rm -rf /install

Please be very careful using the rm command!

For more details on operating system please read the ClearOS 5.1 x86 image notes.

The Web Server is based on Apache Hypertext Transfer Protocol Server.

The service version (shown in native reported format ) is:

# httpd -V
Server version: Apache/2.2.3
Server built:   Sep 21 2009 23:05:07
Server's Module Magic Number: 20051115:3
Server loaded:  APR 1.2.7, APR-Util 1.2.7
Compiled using: APR 1.2.7, APR-Util 1.2.7
Architecture:   32-bit
Server MPM:     Prefork
  threaded:     no
    forked:     yes (variable process count)

Web Server

The server configuration page is available in Server ->Web -> Web Server menu at https://IP_Address:81/admin/web-server.php.
Where, IP_Address - VPS main IP address

Please refer ClearOS Web Server User Guide for more details.

For more details on operating system please read the ClearOS 5.1 x86 image notes.

OpenVPN is a full-featured open source SSL VPN solution that accommodates a wide range of configurations, including remote access, site-to-site VPNs, Wi-Fi security, and enterprise-scale remote access solutions with load balancing, failover, and fine-grained access-controls. Starting with the fundamental premise that complexity is the enemy of security, OpenVPN offers a cost-effective, lightweight alternative to other VPN technologies that is well-targeted for the SME and enterprise markets.

The service version (shown in native reported format ) is:

# openvpn --version
OpenVPN 2.1_rc20 i386-redhat-linux-gnu [SSL] [LZO2] [EPOLL] built on Oct 24 2009
Developed by James Yonan
Copyright (C) 2002-2009 OpenVPN Technologies, Inc. 

OpenVPN

The server configuration page is available in Network ->VPN -> OpenVPN menu at https://IP_Address:81/admin/openvpn.php.
Where, IP_Address - VPS main IP address

Please refer ClearOS OpenVPN User Guide for more details.

For more details on operating system please read the ClearOS 5.1 x86 image notes.

The Web Proxy is based on the Squid - a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. Squid has extensive access controls and makes a great server accelerator.

The service version (shown in native reported format ) is:

# squid -v
Squid Cache: Version 2.6.STABLE21

Access Control

The server configuration page is available in Gateway ->Proxy and Filtering -> Access Control menu at https://IP_Address:81/admin/proxy-policy.php.
Where, IP_Address - VPS main IP address

Please refer ClearOS Access Control User Guide for more details.

Web Proxy

The server configuration page is available in Gateway ->Proxy and Filtering -> Web Proxy menu at https://IP_Address:81/admin/proxy.php.

Please refer ClearOS Web Proxy Control User Guide for more details.

For more details on operating system please read the ClearOS 5.1 x86 image notes.

MySQL is a relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases.
phpMyAdmin is a free software tool written in PHP intended to handle the administration of MySQL over the World Wide Web.

The service version (shown in native reported format ) is:

# mysql --version
mysql  Ver 14.12 Distrib 5.0.77, for redhat-linux-gnu (i686) using readline 5.1

phpMyAdmin-3.2.3-1.1.v5

Web Server

The server configuration page is available in Server ->Web -> Web Server menu at https://IP_Address:81/admin/web-server.php.
Where, IP_Address - VPS main IP address

Please refer ClearOS Web Server User Guide for more details.

MySQL Database

The server configuration page is available in Server ->Database -> MySQL menu at https://IP_Address:81/admin/mysql.php.

You can manage your MySQL database through phpMyAdmin web interface at https://IP_Address:81/mysql/.

Please refer ClearOS MySQL User Guide for more details.

For more details on operating system please read the ClearOS 5.1 x86 image notes.

Antimalware is based on Clam AntiVirus - an open source (GPL) anti-virus toolkit for UNIX, designed especially for e-mail scanning on mail gateways. It provides a number of utilities including a flexible and scalable multi-threaded daemon, a command line scanner and advanced tool for automatic database updates.

The service version (shown in native reported format ) is:

# clamd --version
ClamAV 0.95.3/9955/Wed Oct 28 11:18:03 2009

Antivirus

The service configuration page is available in Gateway ->Antimalware -> Antivirus Configuration menu at https://IP_Address:81/admin/antivirus.php.
Where, IP_Address - VPS main IP address

Please refer ClearOS Antivirus User Guide for more details.

Antiphishing

The service configuration page is available in Gateway ->Antimalware -> Antiphishing Configuration menu at https://IP_Address:81/admin/antiphishing.php.

Please refer ClearOS Antifishing User Guide for more details.

The system runs under ClearOS 5.1 with the latest set of packages installed on i386 platform. The XEN DomU kernel version is2.6.18-164.6.1.v5xen designed for RedHat Enterprise Linux distributive.

Image Information & Recommendation:

Storage: The ‘/’ file-system usage is about 850Mb, about 290 packages are installed.
This ‘basic’ installation provide you an ability to design the system to be much suitable for your needs.
The recommended total disk size is 10Gb. Note: the disk size depend from applications and services you plan to run on the system

Memory: The system use ~128Mb of memory to run mandatory services like init, disk management, logging, networking and ClearOS management console.

CPU and processes: ~60 processes run by default on the system for a minimal CPU load. The recommended CPU is >= 400 MHz

First Boot Configuration using WebConfig

When you first boot the system after the VPS installation has completed, you will be presented with some configuration options to complete the install. These settings are necessary for the configuration of certificates, changes to network settings, and options to register the system on ClearSDN.
WebConfig console is available at: https://IP_Address:81
Where:
IP_Address - VPS main IP address

Provide Language, Network, time Zone, Domain and Organization details to finish your ClearOS installation.

Your system security certificate may have changed and WebConfig interface will restart when this configuration is complete.

WebConfig interface

Please WebConfig interface documentation page on vendors site.

• running CentOS 5.5 with the latest set of updates installed
• hardware platform x86_64
• this is a basic image, with no firewall or add-ons

For more details on operating system please read the “CentOS 5.5 x86_64” image notes.

GlusterFS is a general purpose distributed file system for scalable storage. It aggregates various storage bricks over Infiniband RDMA or TCP/IP interconnect into one large parallel network file system..

The service version (shown in native reported format ) is:

# glusterfs --version
glusterfs 3.0.4 built on Apr 14 2010 08:20:28
Repository revision: v3.0.4

The following example let configure minimal cluster (based on two VPSes) with RAID 1 (the same files on each VPS) volumes.

1. Add a special hostname for each VPS to /etc/hosts on both VPSes. Let’s call them gluster1 and gluster2

# vim /etc/hosts
VPS1_IP gluster1
VPS2_IP gluster2

2. Make the directories for the GlusterFS volumes on each VPS:

mkdir -p /export/store1

3. We’re ready to make the configuration files for our storage volumes. This only needs to be run on the first VPS:

# glusterfs-volgen --name store1 --raid 1 gluster1:/export/store1 gluster2:/export/store1
Generating server volfiles.. for server 'gluster2'
Generating server volfiles.. for server 'gluster1'
Generating client volfiles.. for transport 'tcp'

4. Once that’s done, you’ll have four new files:
* booster.fstab - you won’t need this file
* gluster1-store1-export.vol - server-side configuration file for the first VPS
* gluster2-store1-export.vol - server-side configuration file for the second VPS
* store1-tcp.vol - client side configuration file for GlusterFS clients

5. Copy the gluster1-store1-export.vol file to /etc/glusterfs/glusterfsd.vol on your first VPS

# cp ./gluster1-store1-export.vol /etc/glusterfs/glusterfsd.vol

6. Copy gluster2-store1-export.vol to /etc/glusterfs/glusterfsd.vol on your second VPS

# scp ./gluster2-store1-export.vol root@gluster2:/etc/glusterfs/glusterfsd.vol

Be ready to give gluster2 (VPS2 box) root user password.

7. Copy the store1-tcp.vol should be copied to /etc/glusterfs/glusterfs.vol on both VPSes.

# cp ./store1-tcp.vol /etc/glusterfs/glusterfs.vol
# scp ./store1-tcp.vol root@gluster2:/etc/glusterfs/glusterfs.vol

8. Restart the GlusterFS servers on each VPS:

service glusterfsd restart

and configure it to start on VPS boot time

chkconfig glusterfsd on

9. You can now mount the GlusterFS volume on both VPSes:

# mkdir -p /mnt/glusterfs
# glusterfs /mnt/glusterfs/

10. Now you can save any data into /mnt/glusterfs on the first VPS, and it will be available on the second (and vice versa)

Obviously, this is a very simple and basic implementation of GlusterFS. You can increase performance by making dedicated VPSes just for serving data and you can adjust the default performance options when you mount a GlusterFS volume.

Please find more at GlusterFS Technical FAQ and the GlusterFS User Guide.