Using private IPs for Hardware Nodes - Revision history

Kir: use template:legacy

2016-09-12T21:39:27Z

use template:legacy

2016-08-20T08:38:44Z

Mark as applicable for OpenVZ 6 only.

2016-01-21T16:21:24Z

‎Hardware Node configuration

2012-05-08T22:47:27Z

stop -> stopped

2012-01-04T15:18:54Z

fix link. - Sergey Ivanov

2012-01-04T15:17:38Z

I have moved it to another blog. - Sergey Ivanov

2011-10-21T12:22:25Z

Reverted edits by 59.36.98.57 (talk) to last revision by Kir

2011-10-21T09:24:01Z

‎Container configuration

2011-06-14T10:31:45Z

‎Edit the container's configuration: remove CONFIG_CUSTOMIZED

2009-08-14T10:23:54Z

‎Edit the container's configuration

@@ Line 1: / Line 1: @@
-'''This page is applicable for OpenVZ 6''' (for Virtuozzo 7 documentation see [http://docs.openvz.org '''here''']).
+{{Legacy}}
-<br><br>This article describes how to assign public IPs to containers running on OVZ Hardware Nodes in case you have a following network topology:
 [[Image:PrivateIPs_fig1.gif|An initial network topology]]

← Older revision		Revision as of 08:38, 20 August 2016
Line 1:		Line 1:
−	This article describes how to assign public IPs to containers running on OVZ Hardware Nodes in case you have a following network topology:	+	'''This page is applicable for OpenVZ 6''' (for Virtuozzo 7 documentation see [http://docs.openvz.org '''here''']).
		+	<br><br>This article describes how to assign public IPs to containers running on OVZ Hardware Nodes in case you have a following network topology:

	[[Image:PrivateIPs_fig1.gif\|An initial network topology]]		[[Image:PrivateIPs_fig1.gif\|An initial network topology]]

@@ Line 24: / Line 24: @@
 === Hardware Node configuration ===
 ==== Create a bridge device ====
@@ Line 41: / Line 43: @@
   [HN]# ip route add default via 10.0.0.1 dev br0
-{{Warning|if you are '''configuring''' the node '''remotely''' you '''must''' prepare a '''script''' with the above commands and run it in background with the redirected output or you'll '''lose the access''' to the Node.}}
 ==== A script example ====

@@ Line 237: / Line 237: @@
 ==== Create On-umount script for remove HW → CT route(s) ====
-which should be called each time a container with VEID (<code>/etc/vz/conf/$VEID.umount</code>), or any container (<code>/etc/vz/conf/vps.umount</code>) is stop.
+which should be called each time a container with VEID (<code>/etc/vz/conf/$VEID.umount</code>), or any container (<code>/etc/vz/conf/vps.umount</code>) is stopped.
 <pre>

@@ Line 224: / Line 224: @@
 exit 0
 </pre>
-<p><small>Note: this script can be easily extended to work for multiple triples &lt;bridge, ip address, veth device&gt;, see http://sysadmin-ivanov.blogspot.com/2009/11/autofonix.html </small></p>
+<p><small>Note: this script can be easily extended to work for multiple triples &lt;bridge, ip address, veth device&gt;, see http://sysadmin-ivanov.blogspot.com/2008/02/2-veth-with-2-bridges-on-openvz-at.html </small></p>
 ==== Make the script to be run on a container start ====

@@ Line 57: / Line 57: @@
   [HN]# /tmp/br_add >/dev/null 2>&1 &
-Way to use the internet to help ppeloe solve problems!
+=== Container configuration ===
 === Resulting OpenVZ Node configuration ===

@@ Line 129: / Line 129: @@
 ==== Edit the container's configuration ====
 Add these parameters to the <code>/etc/vz/conf/$CTID.conf</code> file which will be used during the network configuration:
 * Add <code>VETH_IP_ADDRESS="IP/MASK"</code> (a container can have multiple IPs separated by spaces)
 * Add <code>VE_DEFAULT_GATEWAY="CT DEFAULT GATEWAY"</code>
@@ Line 137: / Line 136: @@
 <pre>
 # Network customization section
 VETH_IP_ADDRESS="85.86.87.195/26"
 VE_DEFAULT_GATEWAY="85.86.87.193"

@@ Line 129: / Line 129: @@
 ==== Edit the container's configuration ====
 Add these parameters to the <code>/etc/vz/conf/$CTID.conf</code> file which will be used during the network configuration:
-* Add/change <code>CONFIG_CUSTOMIZED="yes"</code> (indicates that a custom
+* Add/change <code>CONFIG_CUSTOMIZED="yes"</code> (indicates that a custom script should be run on a container start)
-  script should be run on a container start)
+* Add <code>VETH_IP_ADDRESS="IP/MASK"</code> (a container can have multiple IPs separated by spaces)
 * Add <code>VE_DEFAULT_GATEWAY="CT DEFAULT GATEWAY"</code>
-* Add <code>BRIDGEDEV="BRIDGE NAME"</code> (a bridge name to which the
+* Add <code>BRIDGEDEV="BRIDGE NAME"</code> (a bridge name to which the container veth interface should be added)
 An example: