[openstack-dev] [Ironic]Nova resource tracker is not able to identify resources of BM instance when fake_pxe driver used
Senthilprabu Shanmugavel
senthilprabu.s at gmail.com
Tue Mar 29 13:59:09 UTC 2016
Hello,
I am using Ironic for deploying baremetal to my openstack environment.
Using Liberty version on Ubuntu 14.04. I followed Ironic documentation to
deploy x86 servers using pxe_ipmitool. Now I have a working Ironic setup
for PXE boot. I also want to add my test board running ARM 64 bit CPU to
ironic deployment. I would like to try using fake_pxe drivers because my
board don't support IPMI or anything else for out of band communication. So
idea was to do deployment without power management, eventually fake_pxe is
the obvious choice. But I have problem in updating the Ironic node which I
will explain below.
I created ironic node using fake_pxe driver. Added all necessary parameters
using node-update command. Node-show command output is given below for
reference
ironic node-show orange-box
+------------------------+-------------------------------------------------------------------------+
| Property | Value
|
+------------------------+-------------------------------------------------------------------------+
| chassis_uuid |
|
| clean_step | {}
|
| console_enabled | False
|
| created_at | 2016-03-29T12:42:53.500572+00:00
|
| driver | fake_pxe
|
| driver_info | {u'deploy_ramdisk':
u'd72d31de-8f9c-497c-8c51-87a0610f905b', |
| | u'deploy_kernel':
u'01f16454-ef4c-44d9-ae0e-03d4286aed0a'} |
| driver_internal_info | {}
|
| extra | {}
|
| inspection_finished_at | None
|
| inspection_started_at | None
|
| instance_info | {u'root_gb': 40, u'deploy_ramdisk':
u'cdd02e76-13aa-4f4e- |
| | ba32-362119c98fa6', u'deploy_kernel':
u'e1986cab- |
| | 9e55-4b9a-a094-2eda32361521', u'image_source':
u'cdd02e76-13aa-4f4e- |
| | ba32-362119c98fa6'}
|
| instance_uuid | None
|
| last_error | None
|
| maintenance | False
|
| maintenance_reason | None
|
| name | orange-box
|
| power_state | None
|
| properties | {u'memory_mb': 2048, u'cpu_arch': u'aarch64',
u'local_gb': 40, u'cpus': |
| | 2}
|
| provision_state | available
|
| provision_updated_at | None
|
| reservation | None
|
| target_power_state | None
|
| target_provision_state | None
|
| updated_at | 2016-03-29T13:45:07.439046+00:00
|
| uuid | 8146c660-b00f-4cec-9357-a4eab714e5fd
|
+------------------------+-------------------------------------------------------------------------+
>From nova-compute log (with debugging enabled)
2016-03-29 15:44:02.134 19124 DEBUG nova.virt.ironic.driver
[req-fbc8fc44-a3a4-43b0-bd82-cf077007320e - - - - -] Returning 1 available
node(s) get_available_nodes
/usr/lib/python2.7/dist-packages/nova/virt/ironic/driver.py:596
2016-03-29 15:44:02.135 19124 INFO nova.compute.resource_tracker
[req-fbc8fc44-a3a4-43b0-bd82-cf077007320e - - - - -] Auditing locally
available compute resources for node 8146c660-b00f-4cec-9357-a4eab714e5fd
2016-03-29 15:44:02.135 19124 DEBUG nova.virt.ironic.driver
[req-fbc8fc44-a3a4-43b0-bd82-cf077007320e - - - - -] Using cache for node
8146c660-b00f-4cec-9357-a4eab714e5fd, age: 0.00126004219055
get_available_resource
/usr/lib/python2.7/dist-packages/nova/virt/ironic/driver.py:621
2016-03-29 15:44:02.136 19124 DEBUG nova.compute.resource_tracker
[req-fbc8fc44-a3a4-43b0-bd82-cf077007320e - - - - -] *Hypervisor: VCPU
information unavailable* _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:591
2016-03-29 15:44:02.137 19124 DEBUG nova.compute.resource_tracker
[req-fbc8fc44-a3a4-43b0-bd82-cf077007320e - - - - -] Hypervisor/Node
resource view: name=8146c660-b00f-4cec-9357-a4eab714e5fd *free_ram=0MB
free_disk=0GB free_vcpus=unknown* pci_devices=None
_report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:610
Nova resource tracker is not able to find the available resource like CPU,
MEMORY and DISK and all are pointing to ZERO even though I ran "ironic
node-update orange-box add properties/memory_mb=2048 properties/local_gb=40
properties/cpu_arch=aarch64 properties/cpus=2".
ironic node-validate orange-box
+------------+--------+---------------+
| Interface | Result | Reason |
+------------+--------+---------------+
| boot | True | |
| console | None | not supported |
| deploy | True | |
| inspect | None | not supported |
| management | None | not supported |
| power | True | |
| raid | None | not supported |
+------------+--------+---------------+
Because of this during nova boot, scheduler failed to boot the BM instance.
Can anyone help me with what's wrong in my configuration?....
Thanks in advance,
Senthil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160329/7ad8837e/attachment.html>
More information about the OpenStack-dev
mailing list