[one-users] OpenNebula 2.2 not respecting network range?
Lars Kellogg-Stedman
lars at seas.harvard.edu
Wed Apr 27 08:08:11 PDT 2011
Hello all,
I have a network defined like this:
NAME="Cloud Private"
TYPE=RANGED
BRIDGE=br619
GATEWAY=10.243.19.1
NETWORK_ADDRESS=10.243.19.20
NETWORK_SIZE=200
I would expect this to allocate addresses in the range 10.243.19.20 -
10.243.19.220. However, if I create a VM from this description:
CPU = 1
MEMORY = 1024
DISK = [ image = "Basic Server" ]
NIC = [ NETWORK = "Cloud Private" ]
GRAPHICS = [
type = "vnc",
listen = "0.0.0.0"
]
It gets a lease for 10.243.19.1:
$ onevnet show 'Cloud Private'
VIRTUAL NETWORK 1 INFORMATION
ID: : 1
UID: : 0
PUBLIC : N
VIRTUAL NETWORK TEMPLATE
BRIDGE=br619
GATEWAY=10.243.19.1
NAME=Cloud Private
NETWORK_ADDRESS=10.243.19.20
NETWORK_SIZE=200
TYPE=RANGED
LEASES INFORMATION
LEASE=[ IP=10.243.19.1, MAC=5e:a5:0a:f3:13:01, USED=1, VID=13 ]
How do I fix this? Do I simply not understand how ranged networks
work? Thanks for your help,
--
Lars Kellogg-Stedman <lars at seas.harvard.edu>
Senior Technologist
Harvard University SEAS
Academic and Research Computing (ARC)
More information about the Users
mailing list