Hi all,
I have posed a question a few weeks ago about debugging the nova-network issue,
that I can not run the nova-network on the "controller" node (single
flatdhcpmanger), I was able to run that properly on the compute nodes, however.
During the process of debugging, I understand the process of network much
better, iptables, ebtable, dhcp, meta-data services all could cause problem.
I tracked it down in the /usr/lib/python2.6/site-packages/nova/network/l3.py
fixed_range = kwargs.get('fixed_range', False)
networks = kwargs.get('networks', None)
if not fixed_range and networks is not None:
LOG.debug("I am here")
for network in networks:
LOG.debug("But not here")
self.initialize_network(network['cidr'])
Therefore, nova-network skipped bridge configuration and dnsmasq, thus it is
quite useless even though the main nova-network is running! The "networks"
must be different on the "controller node" and on "compute nodes".
How do I print the variables fixed_range and network using the openstack
logging facilities? I would like to get to the bottom of this issue.
Thank you very much for your help!
Zhi-Wei Lu
IET-CR-Network Operations Center
University of California, Davis
(530) 752-0155
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
