Editing Using private IPs for Hardware Nodes
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
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 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]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Prerequisites == | == Prerequisites == | ||
Line 26: | Line 18: | ||
=== Hardware Node configuration === | === Hardware Node configuration === | ||
− | |||
− | |||
==== Create a bridge device ==== | ==== Create a bridge device ==== | ||
Line 45: | Line 35: | ||
[HN]# ip route add default via 10.0.0.1 dev br0 | [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 ==== | ==== A script example ==== | ||
Line 133: | Line 123: | ||
==== Edit the container's configuration ==== | ==== 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 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/change <code>CONFIG_CUSTOMIZED="yes"</code> (indicates that a custom |
+ | 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>VE_DEFAULT_GATEWAY="CT DEFAULT GATEWAY"</code> | ||
− | * Add <code>BRIDGEDEV="BRIDGE NAME"</code> (a bridge name to which the container veth interface should be added) | + | * Add <code>BRIDGEDEV="BRIDGE NAME"</code> (a bridge name to which the |
+ | container veth interface should be added) | ||
An example: | An example: | ||
<pre> | <pre> | ||
# Network customization section | # Network customization section | ||
+ | CONFIG_CUSTOMIZED="yes" | ||
VETH_IP_ADDRESS="85.86.87.195/26" | VETH_IP_ADDRESS="85.86.87.195/26" | ||
VE_DEFAULT_GATEWAY="85.86.87.193" | VE_DEFAULT_GATEWAY="85.86.87.193" | ||
Line 164: | Line 159: | ||
for str in $NETIF_OPTIONS; do \ | for str in $NETIF_OPTIONS; do \ | ||
# getting 'ifname' parameter value | # getting 'ifname' parameter value | ||
− | if | + | if [[ "$str" =~ "^ifname=" ]]; then |
# remove the parameter name from the string (along with '=') | # remove the parameter name from the string (along with '=') | ||
CTIFNAME=${str#*=}; | CTIFNAME=${str#*=}; | ||
fi | fi | ||
# getting 'host_ifname' parameter value | # getting 'host_ifname' parameter value | ||
− | if | + | if [[ "$str" =~ "^host_ifname=" ]]; then |
# remove the parameter name from the string (along with '=') | # remove the parameter name from the string (along with '=') | ||
VZHOSTIF=${str#*=}; | VZHOSTIF=${str#*=}; | ||
Line 228: | Line 223: | ||
exit 0 | exit 0 | ||
</pre> | </pre> | ||
− | <p><small>Note: this script can be easily extended to work for multiple triples <bridge, ip address, veth device>, see http:// | + | <p><small>Note: this script can be easily extended to work for multiple triples <bridge, ip address, veth device>, see http://vireso.blogspot.com/2008/02/2-veth-with-2-brindges-on-openvz-at.html </small></p> |
==== Make the script to be run on a container start ==== | ==== Make the script to be run on a container start ==== | ||
Line 241: | Line 236: | ||
==== Create On-umount script for remove HW → CT route(s) ==== | ==== Create On-umount script for remove HW → CT route(s) ==== | ||
− | which should be called each time a container with VEID (<code>/etc/vz | + | which should be called each time a container with VEID (<code>/etc/sysconfig/vz/$VEID.umount</code>), or any container (<code>/etc/sysconfig/vz/vps.umount</code>) is stoped: |
− | |||
<pre> | <pre> | ||
#!/bin/bash | #!/bin/bash | ||
− | # /etc/vz | + | # /etc/sysconfig/vz/$VEID.umount or /etc/sysconfig/vz/vps.umount |
# a script to remove routes to container with veth-bridge from bridge | # a script to remove routes to container with veth-bridge from bridge | ||
Line 271: | Line 265: | ||
</pre> | </pre> | ||
− | {{Note|The script should be executable (chmod +x /etc/vz | + | {{Note|The script should be executable (chmod +x /etc/sysconfig/vz/vps.umount)}} |
==== Setting the route CT → HN ==== | ==== Setting the route CT → HN ==== |