Ask Your Question
0

Baremteal: How to check BM_Hardware enrollment

asked 2013-07-16 00:06:32 -0500

shanthakumar K gravatar image

updated 2013-07-16 08:01:12 -0500

Jobin gravatar image

Hi,

How to ensure the baremetal hardware enrollment is success or not,

As per the wiki “Once the hardware is enrolled in the baremetal driver, the Nova compute process will broadcast the availability of a new compute resource to the Nova scheduler during the next periodic update, which by default occurs once a minute.”

But I’m not getting any updates on scheduler log other than

2013-07-15 11:04:28.684 8541 AUDIT nova.service [-] Starting scheduler node (version 2013.1)
2013-07-15 11:04:30.433 INFO nova.openstack.common.rpc.common [req-105763e7-ee4c-4606-9a0b-9981953a50bf None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 11:04:30.453 INFO nova.openstack.common.rpc.common [req-105763e7-ee4c-4606-9a0b-9981953a50bf None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 13:29:48.110 8541 INFO nova.service [-] Caught SIGTERM, exiting
2013-07-15 13:30:03.074 13854 AUDIT nova.service [-] Starting scheduler node (version 2013.1)
2013-07-15 13:30:04.890 INFO nova.openstack.common.rpc.common [req-3718a701-9951-4909-aee2-3119c642ece8 None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 13:30:04.915 INFO nova.openstack.common.rpc.common [req-3718a701-9951-4909-aee2-3119c642ece8 None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 13:33:51.087 WARNING nova.scheduler.driver [req-f3340166-463f-4304-910a-a75a500f8ed1 e29d4b006311421896a3469d7efb3621 33a71acc451e4bfc8105a1b7d01bfe8c] [instance: b1b1c5de-2df1-4e14-802e-19a14ecba50f] Setting instance to ERROR state.
2013-07-15 13:35:53.056 13854 INFO nova.service [-] Caught SIGTERM, exiting
2013-07-15 13:35:56.351 14644 AUDIT nova.service [-] Starting scheduler node (version 2013.1)
2013-07-15 13:35:57.745 INFO nova.openstack.common.rpc.common [req-1876911d-5952-4fa3-bf1f-aab826a62b62 None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 13:35:57.755 INFO nova.openstack.common.rpc.common [req-1876911d-5952-4fa3-bf1f-aab826a62b62 None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 13:39:14.250 14644 INFO nova.service [-] Caught SIGTERM, exiting
2013-07-15 13:39:16.509 16823 AUDIT nova.service [-] Starting scheduler node (version 2013.1)
2013-07-15 13:39:17.850 INFO nova.openstack.common.rpc.common [req-87863536-99f2-417d-aeea-f7459fe420b3 None None] Connected to AMQP server on 192.168.124.81:5672
2013-07-15 13:39:17.867 INFO nova.openstack.common.rpc.common [req-87863536-99f2-417d-aeea-f7459fe420b3 None None] Connected to AMQP server on 192.168.124.81:5672

Kindly let me know what went wrong on my configuration.

All the openstack stack services are up & running with baremetal changes on the nova.conf effective.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2013-07-16 01:41:17 -0500

shanthakumar K gravatar image

updated 2013-07-16 08:00:34 -0500

Jobin gravatar image

You can ensure the hardware enrolled by below methods.

Before hardware enrollment, you could see only nova-compute host in the hypervisor list

nova hypervisor-list
+----+--------------------------------+
| ID | Hypervisor hostname            |
+----+--------------------------------+
| 1  | d00-50-56-8b-0c-5f |
+----+--------------------------------+

After hardware enrollment, you could see nova-compute & enrolled hardware in hypervisor list of nova

nova hypervisor-list
+----+--------------------------------------+
| ID | Hypervisor hostname                  |
+----+--------------------------------------+
| 1  | d00-50-56-8b-0c-5f    |
| 2  | b18b1324-10df-4b1e-be81-777d5057a1c6 |
+----+--------------------------------------+



nova hypervisor-stats
+----------------------+-------+
| Property             | Value |
+----------------------+-------+
| count                | 2     |
| vcpus_used           | 1     |
| local_gb_used        | 10    |
| memory_mb            | 6003  |
| current_workload     | 1     |
| vcpus                | 2     |
| running_vms          | 1     |
| free_disk_gb         | 35    |
| disk_available_least | 32    |
| local_gb             | 45    |
| free_ram_mb          | 2931  |
| memory_mb_used       | 3072  |
+----------------------+-------+
edit flag offensive delete link more

Comments

Issue has been resolved

shanthakumar K gravatar imageshanthakumar K ( 2013-07-16 01:41:43 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2013-07-16 00:06:32 -0500

Seen: 70 times

Last updated: Jul 16 '13