Revision history [back]

click to hide/show revision 1
initial version

asked 2014-03-13 07:37:33 -0600

affo gravatar image

[nova] Problems in creating network with FlatDHCPManager

Good Morning, I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 (http://docs.openstack.org/trunk/install-guide/install/apt/content/) and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

# The loopback network interface
auto lo
iface lo inet loopback
# Internal Network
auto eth0
iface eth0 inet static
address 192.168.0.10
netmask 255.255.255.0
# External Network
auto eth1
iface eth1 inet static
address 10.0.0.10
netmask 255.255.255.0
# NATted Network
auto eth2
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova vetwork-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.
Thank you

[nova] Problems in creating network with FlatDHCPManager

Good Morning, I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 (http://docs.openstack.org/trunk/install-guide/install/apt/content/) and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

# The loopback network interface
auto lo
iface lo inet loopback
# Internal Network
auto eth0
iface eth0 inet static
address 192.168.0.10
netmask 255.255.255.0
# External Network
auto eth1
iface eth1 inet static
address 10.0.0.10
netmask 255.255.255.0
# NATted Network
auto eth2
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova vetwork-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.
Thank you

[nova] Problems in creating network with FlatDHCPManager

Good Morning, I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 (http://docs.openstack.org/trunk/install-guide/install/apt/content/) 12.04 and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

#

\# The loopback network interface 
auto lo
iface lo inet loopback
#
\# Internal Network
auto eth0
iface eth0 inet static
address 192.168.0.10
netmask 255.255.255.0
#
\# External Network
auto eth1
iface eth1 inet static
address 10.0.0.10
netmask 255.255.255.0
#
\# NATted Network
auto eth2
iface eth2 inet dhcp

dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova vetwork-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.
Thank you

Problems in creating network with FlatDHCPManager

I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

\# The loopback network interface  
auto lo  
iface lo inet loopback  
\# Internal Network  
auto eth0  
iface eth0 inet static  
    address 192.168.0.10  
    netmask 255.255.255.0  
\# External Network  
auto eth1  
iface eth1 inet static  
    address 10.0.0.10  
    netmask 255.255.255.0  
\# NATted Network  
auto eth2  
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova vetwork-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance. advance.

Addings: I add here my nova.conf files (no problem in showing you my passwords :) ):

Control Node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.10  
vncserver_listen=192.168.0.10  
vncserver_proxyclient_address=192.168.0.10  
auth_strategy=keystone  
\#  
[database]  
connection=mysql://nova:nova@controller/nova  
\#  
[keystone_authtoken]  
auth_host=controller  
auth_port=35357  
auth_protocol=http  
admin_tenant_name=service  
admin_user=nova  
admin_password=nova

Compute Node:

[DEFAULT]  
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
auth_strategy=keystone  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.11  
vnc_enabled=True  
vncserver_listen=0.0.0.0  
vncserver_proxyclient_address=192.168.0.11  
novncproxy_base_url=http://controller:6080/vnc_auto.html  
glance_host=controller  
\#  
network_manager=nova.network.manager.FlatDHCPManager  
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver  
network_size=254  
allow_same_net_traffic=False  
multi_host=True  
send_arp_for_ha=True  
share_dhcp_address=True  
force_dhcp_release=True  
flat_network_bridge=br100  
flat_interface=eth1  
public_interface=eth1  
\#  
[database]  
connection=mysql://nova:nova@controller/nova

And I also add the /etc/network/interfaces file of the Compute Node (the one that "doesn't work"):

\# The loopback network interface
auto lo
iface lo inet loopback

\# Internal Network
auto eth0
iface eth0 inet static
    address 192.168.0.11
    netmask 255.255.255.0

\# NATted Network
auto eth2
iface eth2 inet dhcp

\# Network for VMs traffic, plugged into br100
allow-hotplug eth1
iface eth1 inet manual
    pre-up   ifconfig $IFACE up
    pre-down ifconfig $IFACE down

\# VMs bridge
auto br100
iface br100 inet static
    bridge_ports eth1
    address 10.0.0.1
    netmask 255.255.255.0

If you need something else tell me. Thank you

Problems in creating network with FlatDHCPManager

I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

\# The loopback network interface  
auto lo  
iface lo inet loopback  
\# Internal Network  
auto eth0  
iface eth0 inet static  
    address 192.168.0.10  
    netmask 255.255.255.0  
\# External Network  
auto eth1  
iface eth1 inet static  
    address 10.0.0.10  
    netmask 255.255.255.0  
\# NATted Network  
auto eth2  
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova vetwork-create network-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.

Addings: I add here my nova.conf files (no problem in showing you my passwords :) ):

Control Node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.10  
vncserver_listen=192.168.0.10  
vncserver_proxyclient_address=192.168.0.10  
auth_strategy=keystone  
\#  
[database]  
connection=mysql://nova:nova@controller/nova  
\#  
[keystone_authtoken]  
auth_host=controller  
auth_port=35357  
auth_protocol=http  
admin_tenant_name=service  
admin_user=nova  
admin_password=nova

Compute Node:

[DEFAULT]  
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
auth_strategy=keystone  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.11  
vnc_enabled=True  
vncserver_listen=0.0.0.0  
vncserver_proxyclient_address=192.168.0.11  
novncproxy_base_url=http://controller:6080/vnc_auto.html  
glance_host=controller  
\#  
network_manager=nova.network.manager.FlatDHCPManager  
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver  
network_size=254  
allow_same_net_traffic=False  
multi_host=True  
send_arp_for_ha=True  
share_dhcp_address=True  
force_dhcp_release=True  
flat_network_bridge=br100  
flat_interface=eth1  
public_interface=eth1  
\#  
[database]  
connection=mysql://nova:nova@controller/nova

And I also add the /etc/network/interfaces file of the Compute Node (the one that "doesn't work"):

\# The loopback network interface
auto lo
iface lo inet loopback

\# Internal Network
auto eth0
iface eth0 inet static
    address 192.168.0.11
    netmask 255.255.255.0

\# NATted Network
auto eth2
iface eth2 inet dhcp

\# Network for VMs traffic, plugged into br100
allow-hotplug eth1
iface eth1 inet manual
    pre-up   ifconfig $IFACE up
    pre-down ifconfig $IFACE down

\# VMs bridge
auto br100
iface br100 inet static
    bridge_ports eth1
    address 10.0.0.1
    netmask 255.255.255.0

If you need something else tell me. Thank you

Problems in creating network with FlatDHCPManager

I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

\# The loopback network interface  
auto lo  
iface lo inet loopback  
\# Internal Network  
auto eth0  
iface eth0 inet static  
    address 192.168.0.10  
    netmask 255.255.255.0  
\# External Network  
auto eth1  
iface eth1 inet static  
    address 10.0.0.10  
    netmask 255.255.255.0  
\# NATted Network  
auto eth2  
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova network-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.

Addings: I add here my nova.conf files (no problem in showing you my passwords :) ):

Control Node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.10  
vncserver_listen=192.168.0.10  
vncserver_proxyclient_address=192.168.0.10  
auth_strategy=keystone  
\#  
[database]  
connection=mysql://nova:nova@controller/nova  
\#  
[keystone_authtoken]  
auth_host=controller  
auth_port=35357  
auth_protocol=http  
admin_tenant_name=service  
admin_user=nova  
admin_password=nova

Compute Node:

[DEFAULT]  
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
auth_strategy=keystone  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.11  
vnc_enabled=True  
vncserver_listen=0.0.0.0  
vncserver_proxyclient_address=192.168.0.11  
novncproxy_base_url=http://controller:6080/vnc_auto.html  
glance_host=controller  
\#  
network_manager=nova.network.manager.FlatDHCPManager  
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver  
network_size=254  
allow_same_net_traffic=False  
multi_host=True  
send_arp_for_ha=True  
share_dhcp_address=True  
force_dhcp_release=True  
flat_network_bridge=br100  
flat_interface=eth1  
public_interface=eth1  
\#  
[database]  
connection=mysql://nova:nova@controller/nova

And I also add the /etc/network/interfaces file of the Compute Node (the one that "doesn't work"):

\# The loopback network interface
auto lo
iface lo inet loopback

\# Internal Network
auto eth0
iface eth0 inet static
    address 192.168.0.11
    netmask 255.255.255.0

\# NATted Network
auto eth2
iface eth2 inet dhcp

\# Network for VMs traffic, plugged into br100
allow-hotplug eth1
iface eth1 inet manual
    pre-up   ifconfig $IFACE up
    pre-down ifconfig $IFACE down

\# VMs bridge
auto br100
iface br100 inet static
    bridge_ports eth1
    address 10.0.0.1
    netmask 255.255.255.0

Last detail:
Installed on controller node:
nova-novncproxy
novnc
nova-api
nova-ajax-console-proxy
nova-cert
nova-conductor
nova-consoleauth
nova-doc
nova-scheduler
python-novaclient
Installed on compute node:
nova-compute-kvm
python-guestfs
nova-network
nova-api-metadata

If you need something else tell me. Thank you

Problems in creating network with FlatDHCPManager

I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

\# The loopback network interface  
auto lo  
iface lo inet loopback  
\# Internal Network  
auto eth0  
iface eth0 inet static  
    address 192.168.0.10  
    netmask 255.255.255.0  
\# External Network  
auto eth1  
iface eth1 inet static  
    address 10.0.0.10  
    netmask 255.255.255.0  
\# NATted Network  
auto eth2  
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova network-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.

Addings: I add here my nova.conf files (no problem in showing you my passwords :) ):

Control Node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.10  
vncserver_listen=192.168.0.10  
vncserver_proxyclient_address=192.168.0.10  
auth_strategy=keystone  
\#  
[database]  
connection=mysql://nova:nova@controller/nova  
\#  
[keystone_authtoken]  
auth_host=controller  
auth_port=35357  
auth_protocol=http  
admin_tenant_name=service  
admin_user=nova  
admin_password=nova

Compute Node:

[DEFAULT]  
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
auth_strategy=keystone  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.11  
vnc_enabled=True  
vncserver_listen=0.0.0.0  
vncserver_proxyclient_address=192.168.0.11  
novncproxy_base_url=http://controller:6080/vnc_auto.html  
glance_host=controller  
\#  
network_manager=nova.network.manager.FlatDHCPManager  
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver  
network_size=254  
allow_same_net_traffic=False  
multi_host=True  
send_arp_for_ha=True  
share_dhcp_address=True  
force_dhcp_release=True  
flat_network_bridge=br100  
flat_interface=eth1  
public_interface=eth1  
\#  
[database]  
connection=mysql://nova:nova@controller/nova

And I also add the /etc/network/interfaces file of the Compute Node (the one that "doesn't work"):

\# The loopback network interface
auto lo
iface lo inet loopback

\# Internal Network
auto eth0
iface eth0 inet static
    address 192.168.0.11
    netmask 255.255.255.0

\# NATted Network
auto eth2
iface eth2 inet dhcp

\# Network for VMs traffic, plugged into br100
allow-hotplug eth1
iface eth1 inet manual
    pre-up   ifconfig $IFACE up
    pre-down ifconfig $IFACE down

\# VMs bridge
auto br100
iface br100 inet static
    bridge_ports eth1
    address 10.0.0.1
10.0.0.11
    netmask 255.255.255.0
    network 10.0.0.0
    broadcast 10.0.0.255
    pre-up ifconfig eth0 192.168.0.11
    pre-up ifconfig eth0 up
    pre-up ifconfig eth1 down
    pre-up brctl addbr br100
    pre-up brctl addif br100 eth1
    pre-up ifconfig eth1 0.0.0.0
    pre-up dhclient eth2
    post-down ifconfig eth1 down
    post-down ifconfig eth0 down
    post-down ifconfig br100 down
    post-down brctl delif br100 eth1
    post-down brctl delbr br100

In this way, the network configuration doesn't fail at boot

Last detail:
Installed on controller node:
nova-novncproxy
novnc
nova-api
nova-ajax-console-proxy
nova-cert
nova-conductor
nova-consoleauth
nova-doc
nova-scheduler
python-novaclient

Installed on compute node:
nova-compute-kvm
python-guestfs
nova-network
nova-api-metadata

If you need something else tell me. Thank you

After some experiments, it turns out that there is a problem at the starting of nova-network.
Here are the error in the logs:

Controller:
nova-conductor.log

2014-03-18 18:04:46.616 3148 TRACE nova.openstack.common.rpc.amqp UnsupportedObjectError:  
Unsupported object type NetworkList  
2014-03-18 18:04:46.619 3148 ERROR nova.openstack.common.rpc.common   
[req-a11a07bd-2606-46d7-bcf7-  c7d0e5eae07d None None] Returning exception  
Unsupported object type NetworkList to caller

Compute:
nova-network.log

2014-03-18 18:04:46.505 4713 INFO oslo.messaging._drivers.impl_rabbit [-]  
Connected to AMQP server on controller:5672  
2014-03-18 18:04:46.524 4713 INFO oslo.messaging._drivers.impl_rabbit [-]  
Connected to AMQP server on controller:5672  
2014-03-18 18:04:46.554 4713 AUDIT nova.service [-] Starting network node (version 2014.1-b3)  
2014-03-18 18:05:46.623 4713 ERROR nova.openstack.common.threadgroup [-]  
Timed out waiting for a reply to message ID 018f73ff1f7149dfbd755aa945898e3e

nova-compute.log

2014-03-18 18:03:48.329 4510 AUDIT nova.service [-] Starting compute node (version 2014.1-b3)  
2014-03-18 18:03:48.443 4510 WARNING nova.virt.libvirt.driver [-]  
URI qemu:///system does not support events: internal error: could not initialize domain event timer  
2014-03-18 18:04:50.203 4510 ERROR nova.openstack.common.threadgroup [-]  
Timed out waiting for a reply to message ID f7bcd6b8074a440fa1e1a00b9da309de

Please help me!!! Thank you

Problems in creating network with FlatDHCPManager

I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

\# The loopback network interface  
auto lo  
iface lo inet loopback  
\# Internal Network  
auto eth0  
iface eth0 inet static  
    address 192.168.0.10  
    netmask 255.255.255.0  
\# External Network  
auto eth1  
iface eth1 inet static  
    address 10.0.0.10  
    netmask 255.255.255.0  
\# NATted Network  
auto eth2  
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova network-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.

Addings: I add here my nova.conf files (no problem in showing you my passwords :) ):

Control Node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.10  
vncserver_listen=192.168.0.10  
vncserver_proxyclient_address=192.168.0.10  
auth_strategy=keystone  
\#  
[database]  
connection=mysql://nova:nova@controller/nova  
\#  
[keystone_authtoken]  
auth_host=controller  
auth_port=35357  
auth_protocol=http  
admin_tenant_name=service  
admin_user=nova  
admin_password=nova

Compute Node:

[DEFAULT]  
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
auth_strategy=keystone  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.11  
vnc_enabled=True  
vncserver_listen=0.0.0.0  
vncserver_proxyclient_address=192.168.0.11  
novncproxy_base_url=http://controller:6080/vnc_auto.html  
glance_host=controller  
\#  
network_manager=nova.network.manager.FlatDHCPManager  
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver  
network_size=254  
allow_same_net_traffic=False  
multi_host=True  
send_arp_for_ha=True  
share_dhcp_address=True  
force_dhcp_release=True  
flat_network_bridge=br100  
flat_interface=eth1  
public_interface=eth1  
\#  
[database]  
connection=mysql://nova:nova@controller/nova

And I also add the /etc/network/interfaces file of the Compute Node (the one that "doesn't work"):Node:

\# The loopback network interface
auto lo
iface lo inet loopback

\# VMs bridge
auto br100
iface br100 inet static
    address 10.0.0.11
    netmask 255.255.255.0
    network 10.0.0.0
    broadcast 10.0.0.255
    pre-up ifconfig eth0 192.168.0.11
    pre-up ifconfig eth0 up
    pre-up ifconfig eth1 down
    pre-up brctl addbr br100
    pre-up brctl addif br100 eth1
    pre-up ifconfig eth1 0.0.0.0
    pre-up dhclient eth2
    post-down ifconfig eth1 down
    post-down ifconfig eth0 down
    post-down ifconfig br100 down
    post-down brctl delif br100 eth1
    post-down brctl delbr br100

In this way, the network configuration doesn't fail at boot

Last detail:
Installed on controller node:
nova-novncproxy
novnc
nova-api
nova-ajax-console-proxy
nova-cert
nova-conductor
nova-consoleauth
nova-doc
nova-scheduler
python-novaclient

Installed on compute node:
nova-compute-kvm
python-guestfs
nova-network
nova-api-metadata

If you need something else tell me. Thank you

After some experiments, it turns out that there is a problem at the starting of nova-network.
Here are the error in the logs:

Controller:
nova-conductor.log

2014-03-18 18:04:46.616 3148 TRACE nova.openstack.common.rpc.amqp UnsupportedObjectError:  
Unsupported object type NetworkList  
2014-03-18 18:04:46.619 3148 ERROR nova.openstack.common.rpc.common   
[req-a11a07bd-2606-46d7-bcf7-  c7d0e5eae07d None None] Returning exception  
Unsupported object type NetworkList to caller

Compute:
nova-network.log

2014-03-18 18:04:46.505 4713 INFO oslo.messaging._drivers.impl_rabbit [-]  
Connected to AMQP server on controller:5672  
2014-03-18 18:04:46.524 4713 INFO oslo.messaging._drivers.impl_rabbit [-]  
Connected to AMQP server on controller:5672  
2014-03-18 18:04:46.554 4713 AUDIT nova.service [-] Starting network node (version 2014.1-b3)  
2014-03-18 18:05:46.623 4713 ERROR nova.openstack.common.threadgroup [-]  
Timed out waiting for a reply to message ID 018f73ff1f7149dfbd755aa945898e3e

nova-compute.log

2014-03-18 18:03:48.329 4510 AUDIT nova.service [-] Starting compute node (version 2014.1-b3)  
2014-03-18 18:03:48.443 4510 WARNING nova.virt.libvirt.driver [-]  
URI qemu:///system does not support events: internal error: could not initialize domain event timer  
2014-03-18 18:04:50.203 4510 ERROR nova.openstack.common.threadgroup [-]  
Timed out waiting for a reply to message ID f7bcd6b8074a440fa1e1a00b9da309de

Please help me!!! Thank you

Problems in creating network with FlatDHCPManager

I'm getting frustrated in trying to create a network with the command:

nova --debug network-create vmnet --fixed-range-v4=10.0.0.0/24 --bridge=br100 --multi-host=T

I'm following the official tutorial by OpenStack to install Icehouse on Ubuntu 12.04 and i'm getting stuck into the networking section.

I'm __not__ using neutron.

My setup is the following one:
- i'm using Oracle Virtual Box.
- I created 2 istances: the Control node and the Compute node.
- I created 2 host-only network cards one with 192.168.0.1 ip and the other 10.0.0.1.
As suggested the 192.168.0.0 net is used as internal net for openstack services and the other should be used at this point of the installation.
- I also use another NATted network card to access the internet from my Virtual Box VMs.

I paste here Controller node /etc/network/interfaces configuration:

\# The loopback network interface  
auto lo  
iface lo inet loopback  
\# Internal Network  
auto eth0  
iface eth0 inet static  
    address 192.168.0.10  
    netmask 255.255.255.0  
\# External Network  
auto eth1  
iface eth1 inet static  
    address 10.0.0.10  
    netmask 255.255.255.0  
\# NATted Network  
auto eth2  
iface eth2 inet dhcp

Everything went well until i installed and configured nova-network and nova-api-metadata. From that point on the interface virbr0 was created and, at boot, ubuntu fails to configure the network.
But I'm not worried about it (maybe I should, I don't know), because running sudo ifup -a makes everything good. tried to fix the problem as you will se in the /etc/network/interfaces file of the compute node.
At least anyone can ping everyone on any IP address.

Given this, once I run the command nova network-create ... on the __Controller node__, I wait several seconds and the output is (among others):

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500)

Up to now I tried many configurations and read as much as I could.
So, now, my questions are:
- What should I do?
- What should the /etc/network/interfaces file on the Compute Node should look like?

I apologize for my lack of linux-sysadmin skills in advance.

Addings: I add here my nova.conf files (no problem in showing you my passwords :) ):

Control Node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.10  
vncserver_listen=192.168.0.10  
vncserver_proxyclient_address=192.168.0.10  
auth_strategy=keystone  
\#  
[database]  
connection=mysql://nova:nova@controller/nova  
\#  
[keystone_authtoken]  
auth_host=controller  
auth_port=35357  
auth_protocol=http  
admin_tenant_name=service  
admin_user=nova  
admin_password=nova

Compute Node:

[DEFAULT]  
dhcpbridge_flagfile=/etc/nova/nova.conf  
dhcpbridge=/usr/bin/nova-dhcpbridge  
logdir=/var/log/nova  
state_path=/var/lib/nova  
lock_path=/var/lock/nova  
force_dhcp_release=True  
iscsi_helper=tgtadm  
libvirt_use_virtio_for_bridges=True  
connection_type=libvirt  
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf  
verbose=True  
ec2_private_dns_show_ip=True  
api_paste_config=/etc/nova/api-paste.ini  
volumes_path=/var/lib/nova/volumes  
enabled_apis=ec2,osapi_compute,metadata  
auth_strategy=keystone  
rpc_backend=nova.rpc.impl_kombu  
rabbit_host=controller  
rabbit_password=rabbit  
my_ip=192.168.0.11  
vnc_enabled=True  
vncserver_listen=0.0.0.0  
vncserver_proxyclient_address=192.168.0.11  
novncproxy_base_url=http://controller:6080/vnc_auto.html  
glance_host=controller  
\#  
network_manager=nova.network.manager.FlatDHCPManager  
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver  
network_size=254  
allow_same_net_traffic=False  
multi_host=True  
send_arp_for_ha=True  
share_dhcp_address=True  
force_dhcp_release=True  
flat_network_bridge=br100  
flat_interface=eth1  
public_interface=eth1  
\#  
[database]  
connection=mysql://nova:nova@controller/nova

And I also add the /etc/network/interfaces file of the Compute Node:

\# The loopback network interface
auto lo
iface lo inet loopback

\# VMs bridge
auto br100
iface br100 inet static
    address 10.0.0.11
    netmask 255.255.255.0
    network 10.0.0.0
    broadcast 10.0.0.255
    pre-up ifconfig eth0 192.168.0.11
    pre-up ifconfig eth0 up
    pre-up ifconfig eth1 down
    pre-up brctl addbr br100
    pre-up brctl addif br100 eth1
    pre-up ifconfig eth1 0.0.0.0
    pre-up dhclient eth2
    post-down ifconfig eth1 down
    post-down ifconfig eth0 down
    post-down ifconfig br100 down
    post-down brctl delif br100 eth1
    post-down brctl delbr br100

In this way, the network configuration doesn't fail at boot

Last detail:
Installed on controller node:
nova-novncproxy
novnc
nova-api
nova-ajax-console-proxy
nova-cert
nova-conductor
nova-consoleauth
nova-doc
nova-scheduler
python-novaclient

Installed on compute node:
nova-compute-kvm
python-guestfs
nova-network
nova-api-metadata

If you need something else tell me. Thank you

After some experiments, it turns out that there is a problem at the starting of nova-network.
Here are the error in the logs:

Controller:
nova-conductor.log

2014-03-18 18:04:46.616 3148 TRACE nova.openstack.common.rpc.amqp UnsupportedObjectError:  
Unsupported object type NetworkList  
2014-03-18 18:04:46.619 3148 ERROR nova.openstack.common.rpc.common   
[req-a11a07bd-2606-46d7-bcf7-  c7d0e5eae07d None None] Returning exception  
Unsupported object type NetworkList to caller

Compute:
nova-network.log

2014-03-18 18:04:46.505 4713 INFO oslo.messaging._drivers.impl_rabbit [-]  
Connected to AMQP server on controller:5672  
2014-03-18 18:04:46.524 4713 INFO oslo.messaging._drivers.impl_rabbit [-]  
Connected to AMQP server on controller:5672  
2014-03-18 18:04:46.554 4713 AUDIT nova.service [-] Starting network node (version 2014.1-b3)  
2014-03-18 18:05:46.623 4713 ERROR nova.openstack.common.threadgroup [-]  
Timed out waiting for a reply to message ID 018f73ff1f7149dfbd755aa945898e3e

nova-compute.log

2014-03-18 18:03:48.329 4510 AUDIT nova.service [-] Starting compute node (version 2014.1-b3)  
2014-03-18 18:03:48.443 4510 WARNING nova.virt.libvirt.driver [-]  
URI qemu:///system does not support events: internal error: could not initialize domain event timer  
2014-03-18 18:04:50.203 4510 ERROR nova.openstack.common.threadgroup [-]  
Timed out waiting for a reply to message ID f7bcd6b8074a440fa1e1a00b9da309de

Please help me!!! Thank you