Ruby Tech BlueOnyx OpenVZ VPS template

apmuthu

Renowned Member
Feb 26, 2009
871
12
83
Chennai - India & Singapore
github.com
Has anyone tried out the OpenVZ Template for BlueOnyx from Ruby tech at:
http://mirrors.rubyringtech.com/openvz/

Renamed the template from:
Code:
[/URL][URL="http://mirrors.rubyringtech.com/openvz/blueonyx-5106R-i386-RRT10132010.tar.gz"]blueonyx-5106R-i386-RRT10132010.tar.gz[/URL]
to
Code:
centos-5.0-blueonyx_5106R.RRT10132010-1_i386.tar.gz
for ProxMox VE to recognise it.

Installed, turned on Quotas and started it.
Cannot access on Browser.

Tried with Venet and Bridged mode in vain. With an dwithout Quotas.
Log states /proc/misc is missing.
Even manually edited the /etc/sysconfig/network - no use.
Only /etc/sysconfig/network-scripts/ifcfg-lo is available.
The route-venet0 file points to 192.0.2.1 - non-existant.

Tried a vzrestore and it was missing the vps.conf file:

# vzrestore centos-5.0-blueonyx_5106R.RRT10132010-1_i386.tar.gz 120
Code:
INFO: restore openvz backup 'centos-5.0-blueonyx_5106R.RRT10132010-1_i386.tar.gz' using ID 120
INFO: extracting archive 'centos-5.0-blueonyx_5106R.RRT10132010-1_i386.tar.gz'
INFO: Total bytes read: 1089249280 (1.1GiB, 100MiB/s)
INFO: extracting configuration to '/etc/vz/conf/120.conf'
INFO: sh: /var/lib/vz/private/120/etc/vzdump/vps.conf: No such file or directory
ERROR: restore openvz backup 'centos-5.0-blueonyx_5106R.RRT10132010-1_i386.tar.gz' failed - command 'sed -r -e 's/VE_ROOT=.*/VE_ROOT=\"\/var\/lib\/vz\/root\/$VEID\"/' -e 's/VE_PRIVATE=.*/VE_PRIVATE=\"\/var\/lib\/vz\/private\/$VEID\"/' -e 's/host_ifname=veth[0-9]+./host_ifname=veth120./' <'/var/lib/vz/private/120/etc/vzdump/vps.conf' >'/etc/vz/conf/120.conf'' failed with exit code 1
 
Yes, Dietmar, I realise that without the conf file bundled into the tar.gz, the file cannot be used for a vzrestore. I wanted to check out if it were present.

www.blueonyx.it and www.blueonyx.nl seem to have begun blocking IP addresses from India ever since OpenBQBO OpenSource packages were being released in competition with commercial interests. During the install a licensing RPM was being trickled into the system, viz.,
Code:
solarspeed-ioncube-3.1.32-2008AV06.i386.rpm   | 2.4 MB

I finally managed to get it running after using Lucas Peyatt's advice an earlier post here. This is also a workaround for the issue of GATEWAYDEV listed in an earlier post.
This specific template has a lot of IPTABLES rules in it that interferes with the crons on the host cutting off internet connectivity to the guest every 1 minute needing a service iptables restart in the guest from time to time.

The only changes were:

1. The template file:
Code:
blueonyx-5106R-i386-RRT10132010.tar.gz

was renamed to be:
Code:
blueonyx-5.0-bo_5106R.RRT10132010-1_i386.tar.gz
2. A new file was created as: /etc/vz/dists/blueonyx.conf having:
Code:
ADD_IP=blueonyx-add_ip.sh
DEL_IP=redhat-del_ip.sh
SET_HOSTNAME=redhat-set_hostname.sh
SET_DNS=set_dns.sh
SET_USERPASS=set_userpass.sh
SET_UGID_QUOTA=set_ugid_quota.sh
POST_CREATE=postcreate.sh
The current version (ProxMox VE 1.7) of the redhat-del_ip.sh file is identical to the sauce-del_ip.sh provided by Lucas Peyatt. His sauce-add_ip.sh has been uploaded as /etc/vz/dists/scripts/blueonyx-add_ip.sh with some cosmetic mods to reflect the current version of redhat-add_ip.sh so that a patch file if made will be small. His functionsnew.txt has been appended to the file /etc/vz/dists/scripts/functions , the appended contents being:
Code:
function remove_fake_old_route()
{
    local file="$1"

    [ -f "${file}" ] || return 0
    if ! grep -qE '191.255.255.[0-1]' $file; then
        return 0
    fi
    sed '/191.255.255.[0-1]/d' < ${file} > ${file}.$$ &&
        mv -f ${file}.$$ ${file}
    rm -f ${file}.$$ 2>/dev/null
}
The file blueonyx-add_ip.sh is zipped and attached herewith.
View attachment blueonyx-add_ip.zip

yum install screen was done and the yum update was done from within it while another SSH screen was used to keep restarting the IPTABLES.
 
Last edited:
The parameter values were double quoted in /etc/sysconfig/network and it's contents in working state are:
Code:
FORWARD_IPV4=true   # changed on Fri Mar 11 01:04:41 2011
GATEWAY="192.0.2.1"
HOSTNAME="blueonyxvps001.mydomain.com"
NETWORKING="yes"