[openstack-dev] [nova][baremetal] Error when running nova boot for baremetal node

Mikyung Kang mkkang at isi.edu
Thu May 30 18:36:53 UTC 2013


Hello Ling,

1. Please check whether baremetal compute's hostname is correct:
"Host = node1"? Is this same to the hostname in the result of "nova service-list"?

2. Please check resource_track and capability information are being sent properly between compute and scheduler:

verbose = True
debug = True

/var/log/nova/compute.log
...
nova.compute.resource_tracker [-] Free ram (MB): xxx
nova.compute.resource_tracker [-] Free disk (GB): xxx
nova.compute.resource_tracker [-] Free VCPUS: xx

nova.compute.resource_tracker [-] Compute_service record updated for node1:xxx
...

/var/log/nova/scheduler.log
...
nova.scheduler.host_manager [req-xxx None None] Received compute service update from (u'node1', u'xxx'). update_service_capabilities /usr/lib/python2.6/site-packages/nova/scheduler/host_manager.py:359

nova.openstack.common.rpc.amqp [-] received {... u'host': u'node1', u'capabilities': [{... , u'host': u'node1', ...} _safe_log /usr/lib/python2.6/site-packages/nova/openstack/common/rpc/common.py:276
...

3. Please try cpu_arch="s== x86_64" when setting a baremetal flavor.

Thanks,
Mikyung




----- Original Message -----
From: "Ling Gao" <linggao at us.ibm.com>
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org>
Sent: Thursday, May 16, 2013 3:11:23 PM
Subject: [openstack-dev] [nova][baremetal] Error when running nova boot for	baremetal node


Hi, 
I have installed openstack Grizzly release and trying to set up to deploy baremetal nodes. I am following the instructions from https://wiki.openstack.org/wiki/Baremetal The controller and the compute hosts are two separate nodes. 

The last step failed. 
~#nova boot --flavor my-baremetal-flavor --image my-image my-baremetal-node 
~#nova show my-baremetal-node 
... 
| fault | {u'message': u'NoValidHost', u'code': 500, u'details': u'No valid host was found. | 



Here are some related date, I have substituted the ip/password and and mac with fake ones. 
~# nova baremetal-node-list 
+----+--------------+------+-----------+---------+-------------------+------------+-------------+-------------+---------------+ 
| ID | Host | CPUs | Memory_MB | Disk_GB | MAC Address | PM Address | PM Username | PM Password | Terminal Port | 
+----+--------------+------+-----------+---------+-------------------+------------+-------------+-------------+---------------+ 
| 5 | node1 | 2 | 4096 | 286 | 00:11:22:33:44:55:66 | 70.0.0.16 | USERID | | None | 
+----+--------------+------+-----------+---------+-------------------+------------+-------------+-------------+---------------+ 

~# nova baremetal-interface-list 5 
+----+-------------+---------+-------------------+ 
| ID | Datapath_ID | Port_No | Address | 
+----+-------------+---------+-------------------+ 
| 7 | 0 | 0 | 00:11:22:33:44:55:66 | 
| 8 | 0 | 0 | 00:11:22:33:44:55:67 | 
+----+-------------+---------+-------------------+ 

On compute host node1, the /etc/nova/nova.conf looks like this 
# cat /etc/nova/nova.conf 
[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 
flat_interface=eth1 
network_manager=nova.network.manager.FlatDHCPManager 
vncserver_proxyclient_address=127.0.0.1 
rabbit_hosts=10.1.0.166:5672 
flat_network_bridge=br100 
glance_api_servers=10.1.0.166:9292 
rabbit_userid=nova 
rabbit_ha_queues=false 
rabbit_password=passw0rd 
rabbit_host=10.1.0.166 
sql_connection=mysql://nova:passw0rd@10.0.1.166/nova 
vnc_enabled=true 
rabbit_virtual_host=/ 
image_service=nova.image.glance.GlanceImageService 
rabbit_port=5672 
novncproxy_base_url=http://10.1.0.166:6080/vnc_auto.html 
public_interface=eth0 
service_down_time=60 
vncserver_listen=127.0.0.1 
osapi_compute_listen=0.0.0.0 
ec2_listen=0.0.0.0 
volume_api_class=nova.volume.cinder.API 
osapi_volume_listen=0.0.0.0 
metadata_listen=0.0.0.0 
auth_strategy=keystone 
#compute_driver=libvirt.LibvirtDriver 
osapi_compute_workers=12 
rootwrap_config=/etc/nova/rootwrap.conf 
rpc_backend=nova.openstack.common.rpc.impl_kombu 
fixed_range=192.168.201.0/24 
dhcp_domain=novalocal 
send_arp_for_ha=True 
multi_host=True 
libvirt_type=kvm 
flat_injected=false 
scheduler_host_manager = nova.scheduler.baremetal_host_manager.BaremetalHostManager 
firewall_driver = nova.virt.firewall.NoopFirewallDriver 
compute_driver = nova.virt.baremetal.driver.BareMetalDriver 
ram_allocation_ratio = 1.0 
reserved_host_memory_mb = 0 

[baremetal] 
net_config_template = /opt/stack/nova/nova/virt/baremetal/net-static.ubuntu.template 
tftp_root = /tftpboot 
power_manager = nova.virt.baremetal.ipmi.IPMI 
driver = nova.virt.baremetal.pxe.PXE 
instance_type_extra_specs = cpu_arch:x86_64 
sql_connection = mysql://nova:passw0rd@10.1.0.166/nova_bm 

What else should I check? I do not see obvious errors from /var/log/nova/nova-api.log and /var/log/nova/nova-compute.log 

Thanks, 

Ling 

Ling Gao 
Poughkeepsie Unix Development Lab 
IBM Systems and Technology Group 


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list