cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chris snow <chsnow...@gmail.com>
Subject devcloud 2 to 3 - network configuration
Date Sun, 16 Feb 2014 11:36:53 GMT
For the vagrant version of devcloud that I am working on (which may
become devcloud 3?), I have had to switch the network cards in
Virtualbox.

Devcloud2 has

eth0 - host only network
eth1 - nat network

However, Vagrant requires the first network card to be the NAT one, i.e.

eth0 - nat network
eth1 - host only network

Question 1: Am I correct in thinking that I just need to make the
following changes to the devcloud2 network setup:

auto xenbr0
iface xenbr0 inet static
        bridge_ports eth0         # <-- devcloud3 changes this to eth1
        address 192.168.56.10
        netmask 255.255.255.0
        network 192.168.56.0
        broadcast 192.168.56.255
        gateway 192.168.56.1
        dns_nameservers 8.8.8.8 8.8.4.4
        post-up route del default gw 192.168.56.1; route add default
gw 192.168.56.1 metric 100;

auto xenbr1
iface xenbr1 inet dhcp
        bridge_ports eth1           # <-- devcloud3 changes this to eth0
        dns_nameservers 8.8.8.8 8.8.4.4
        post-up route add default gw 10.0.3.2  # <-- devcloud3 changes
this to 10.0.2.2

Question 2: What is the purpose of xenbr0 and xenbr1?  I.e. how are
there bridges used by cloudstack / xen?

Many thanks,

Chris

Mime
View raw message