Hi there,
My problem is that I want to achieve a maximum use of our public IP
range for VM's. We only have a /27 at this stage and there are some
other servers in use already.
After using the CentOS set up guide a few times we could get things
going but that basically used up our range or caused other problems [1].
Ideally I would like to generate private ranges for the VM guests and
attach them to public IP's as required (something I am under the
impression that Cloudstack can do ).
Please bear in mind I have done the initial set up many, many times but
with slight differences in selections trying to achieve this but run
into road blocks. This time I have ignored the auto set up and created a
zone manually. This has given me a set up with:
cloud0 Link encap:Ethernet HWaddr
inet addr:169.254.0.1 Bcast:169.254.255.255 Mask:255.255.0.0
cloudbr0 Link encap:Ethernet HWaddr 00:30:48:FC:6B:B4
inet addr: X.X.X.X Bcast:X.X.X.0 Mask:255.255.255.224
eth0 (is the bridged physical interface)
Does my cloudbr0 having a public IP mean that I have to do something
different to the install process?
Is cloud0 a remnant of previous set ups or can/should the local guest
network hang in this range?
I'm not looking for someone to spoon feed me the answers (because I need
to maintain this set up myself) but I feel like I have misunderstood
something crucial.
The install or set up pointers I am after is to achieve:
X.X.X.X is a public IP with a NFS server on it (single machine set up).
I want the management & storage networks to be virtual and private.
I want to be able to allocate X.X.X.17 -> VM (169.254.0.26).
[1] The CentOS how to points at every VM being on the same {public}
range as the host. When set up this way the SSVM's were reported to
contribute in a DNS DDoS.
Sorry for all the typing but I am keen to learn more.
Thanks
Piers
