Hello,
assuming that you are installing Ubuntu on your bare metal PC, the first thing to do is to configure the only one NIC you have as needed. Note that the NIC will be used for accessing the Operating System (ubuntu), the services (API endpoints), the dashboard (Horizon) and for "exposing" VMs when you associate a floating IP address to them.
Let's make some assumptions for proceeding with the explanation:
1) you want to install Havana with Neutron (not nova-network)
2) your installation is really a single node; i.e. you are not going to add compute nodes in the future
The first thing to do is to configure the network at Operating System level.
You need an OpenVSwitch bridge for several purposes so create that with command:
sudo ovs-vsctl add-br br-ex
Then you need to configure the network at OS level.
The following is an example of how you can configure the network using /etc/network/interfaces:
auto lo
iface lo inet loopback
auto eth1
iface eth1 inet manual
up ip address add 0/0 dev $IFACE
up ip link set $IFACE up
up ifconfig $IFACE promisc
up ifconfig $IFACE multicast
down ip link set $IFACE down
auto br-ex
iface br-ex inet static
address <static-ip-address>
netmask <mask>
network <network>
broadcast <broadcast>
gateway <gateway-ip-address>
up ifconfig $IFACE promisc
dns-nameservers <dns-ip-address> The first entry configures the loopback interface: no explanation is needed.
The second entry "starts" the interface whenever you switch on the PC. It's worth noticing that you do not assign any IP address to such an interface and this is needed because this interface will 'capture' all the traffic on the physical network it is connected to. The 'captured' traffic will be forwarded to all the virtual devices connected to the interfaces and one of such devices is br-ex.
The third entry configures br-ex, an OpenVSwitch bridge that will serve for the following purposes:
- give access to the services (API endpoints) and Horizon
- give access to the PC's Operating System (ubuntu)
- give access to VMs in the cloud when they are associated to a floating IP address
After preparing the file in this way, you reboot the PC.
It is fundamental to access the PC after the reboot from the console because if you try to access from ethernet you fail. The reason being that you have a single NIC but it is not assigned any IP address.
After accessing through the local console, you should see that you have three interfaces (ifconfig command):
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:65536 Metric:1
RX packets:91931 errors:0 dropped:0 overruns:0 frame:0
TX packets:91931 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19815734 (19.8 MB) TX bytes:19815734 (19.8 MB)
eth1 Link encap:Ethernet HWaddr 00:1a:4b:dd:44:5e
inet6 addr: fe80::21a ... (more)
