Corporate Home Open Source Home
Syndicate content
Eucalyptus
4 replies [Last post]
pnunn
Offline
Joined: 06/07/2010

Hi Guys,

I'm struggling to get some IP addresses working on my nodes that are public using UEC.

I've managed, from a clean install of both CC and NC's to get machines running with IP addresses that are part of our internal network. I need to change these to be on the public network now.

I have been all over the documentation and it seems that I shouldn't have been editing the eucalyptus.local.conf file but rather the eucalyptus.conf file. I have now done that, but the changes are never reflected in the configuration.

I have now gone back to editing the local.conf file, changed the IP's to the range I want and issued a sudo stop eucalyptus-cc CLEAN=1 and sudo start eucalyptus-cc CLEAN=1

Now when I do uca-describe-addresses I get

ADDRESS 111.127.169.120 nobody
ADDRESS 111.127.169.121 nobody
ADDRESS 111.127.169.122 nobody
ADDRESS 111.127.169.123 nobody
ADDRESS 111.127.169.124 nobody
ADDRESS 111.127.169.125 nobody
ADDRESS 111.127.169.126 nobody
ADDRESS 192.168.123.75 nobody
ADDRESS 192.168.123.76 nobody
ADDRESS 192.168.123.77 nobody
ADDRESS 192.168.123.78 nobody
ADDRESS 192.168.123.79 nobody

so both the old and new IP's are listed.

Can someone please tell me where I should be making these changes and how to get them correctly reflected in the installation? Is there ANY up to date documentation anywhere?

My configurations are as follows..


eucalyptus.conf

# /etc/eucalyptus/eucalyptus.conf
#
# These are the Ubuntu Enterprise Cloud's default Eucalyptus parameters.

# Affects: All
# See: **NOTE** below
EUCALYPTUS="/"
EUCA_USER="eucalyptus"

# Affects: CLC, Walrus, SC
DISABLE_DNS="Y"
DISABLE_ISCSI="Y"
JVM_MEM="1024m"

# Affects: CC, NC
# See: **NOTE** below
ENABLE_WS_SECURITY="Y"
LOGLEVEL="DEBUG"
VNET_PUBINTERFACE="eth0"
VNET_PRIVINTERFACE="eth0"
#VNET_MODE="MANAGED-NOVLAN"

# Affects: CC
# See: **NOTE** below
CC_PORT="8774"
SCHEDPOLICY="ROUNDROBIN"
POWER_IDLETHRESH="300"
POWER_WAKETHRESH="300"
NC_SERVICE="axis2/services/EucalyptusNC"
VNET_DHCPDAEMON="/usr/sbin/dhcpd3"
VNET_DHCPUSER="dhcpd"
NODES=""
VNET_ADDRSPERNET="32"
#VNET_SUBNET=""
#VNET_NETMASK=""
#VNET_DNS=""
#VNET_PUBLICIPS=""

# Affects: NC
NC_PORT="8775"
HYPERVISOR="kvm"
MANUAL_INSTANCES_CLEANUP=0
VNET_BRIDGE="br0"
INSTANCE_PATH="/var/lib/eucalyptus/instances/"

##########################################################################
#
# Administrative overrides and customizations may go below, in accordance
# with the manpage for eucalyptus.conf(5).
#
# However, to modify Eucalyptus parameters, you are advised to use
# euca_conf(8), which will update eucalyptus.local.conf(5) and ensure
# smooth package upgrades.
#
# **NOTE**: To activate changes of these parameters on a CC, you must:
# sudo restart eucalyptus-cc CLEAN=1
# HOWEVER, if you do this, all currently running virtual#
##########################################################################

These settings are totally ignored
VNET_MODE="MANAGED"
VNET_SUBNET="172.19.0.0"
VNET_NETMASK="255.255.0.0"
VNET_DNS="208.67.222.222"
VNET_ADDRSPERNET="10"
VNET_PUBLICIPS="111.125.169.120-111.125.169.126"

and


# /etc/eucalyptus/eucalyptus.local.conf

# This file is read and written by euca_conf(8)
# WARNING: You should *never* edit this file directly.

# To modify Eucalyptus parameters, either use euca_conf(8), or
# edit /etc/eucalyptus/eucalyptus.conf according to eucalyptus.conf(5).

# network configuration from the input configuration file
VNET_MODE="MANAGED-NOVLAN"
VNET_SUBNET="172.19.0.0"
VNET_NETMASK="255.255.0.0"
VNET_DNS="208.67.222.222"
VNET_ADDRSPERNET="10"
VNET_PUBLICIPS="111.126.169.120-111.126.169.126"

Any help would be greatly appreciated.. I need to get this rolled out very soon.

Thank you.

Peter.

pnunn
Offline
Joined: 06/07/2010
More information...

I now have a machine running an 111.126.169.120 but cannot get to it with either ping or ssh, even from the cloud controller itself.

IP Tables -L gives

sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere ctstate ESTABLISHED
ACCEPT all -- anywhere !172.19.0.0/16
admin-default all -- anywhere anywhere
ACCEPT all -- 172.19.0.80/28 172.19.0.80/28

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain admin-default (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- 168.197-26-211.dynamic.dsl.mel.iprimus.net.au 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- 123-243-142-155.static.tpgi.com.au 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- 0.0.0.0/24 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- 114.111.128.0/19 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- mel.intervolve.com.au 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- 000.008.dsl.brs.iprimus.net.au/15 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- 203-219-248-249.static.tpgi.com.au 172.19.0.80/29 tcp dpt:ssh
ACCEPT tcp -- 254.197-26-211.dynamic.dsl.mel.iprimus.net.au 172.19.0.80/29 tcp dpt:ssh

ifconfig on the CC


ifconfig
eth0 Link encap:Ethernet HWaddr 6c:f0:49:4c:2a:e8
inet addr:192.168.123.69 Bcast:192.168.123.127 Mask:255.255.255.128
inet6 addr: fe80::6ef0:49ff:fe4c:2ae8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:603673 errors:0 dropped:0 overruns:0 frame:0
TX packets:535766 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:264693679 (264.6 MB) TX bytes:196166167 (196.1 MB)
Interrupt:26 Base address:0x4000

eth0:metadata Link encap:Ethernet HWaddr 6c:f0:49:4c:2a:e8
inet addr:169.254.169.254 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:26 Base address:0x4000

eth0:priv Link encap:Ethernet HWaddr 6c:f0:49:4c:2a:e8
inet addr:172.19.0.81 Bcast:172.19.0.89 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:26 Base address:0x4000

eth0:pub Link encap:Ethernet HWaddr 6c:f0:49:4c:2a:e8
inet addr:111.126.169.120 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:26 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1486974 errors:0 dropped:0 overruns:0 frame:0
TX packets:1486974 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:640794839 (640.7 MB) TX bytes:640794839 (640.7 MB)

ip addr show

sudo ip addr show
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 6c:f0:49:4c:2a:e8 brd ff:ff:ff:ff:ff:ff
inet 169.254.169.254/32 scope link eth0:metadata
inet 192.168.123.69/25 brd 192.168.123.127 scope global eth0
inet 111.125.169.126/28 scope global eth0
inet 172.19.0.81/28 brd 172.19.0.89 scope global eth0:priv
inet 111.126.169.120/32 scope global eth0:pub
inet6 fe80::6ef0:49ff:fe4c:2ae8/64 scope link
valid_lft forever preferred_lft forever
4: eucabr10: mtu 1500 qdisc noqueue state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

Not sure what else to give you that might help.. I'm lost.. sorry.

santhony
Offline
Joined: 06/25/2010
same issue

I have the same issue.. Not sure where to globally change the VNET_MODE type. I also have to manually update the eucalyptus.local.conf file.

Within that file though, it says

"# To modify Eucalyptus parameters, either use euca_conf(8), or
# edit /etc/eucalyptus/eucalyptus.conf according to eucalyptus.conf(5)."

But writing directly into eucalyptus.conf never seems to update any other conf files..

pnunn
Offline
Joined: 06/07/2010
It is odd.. that's for sure.

It is odd.. that's for sure. We managed to get our system working finally by assigning a second IP to the nic in the cloud controller on our external network (to get the gateway in place) and then we had to turn off some of the firewall to get it working.

But.. so far so good, but nervous about what happens when we upgrade/change anything.. but for now its working.

Peter.

graziano
Offline
Joined: 01/14/2010
Hello, glad you got it

Hello,

glad you got it working. If I'm not mistaken, it seems to be an unfortunate wording within the UEC configuration file: the local version is the one that should be modified, not eucalyptus.conf. I think the reason is to facilitate upgrading.

cheers
graziano