Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey guys,

i'm trying to install and configure Ironic manually. In this context
i'll try to write a doc for others because the existing one is really
incomplete. In this case i've some problems and questions


OpenStack ENV:
Icehouse + Ubuntu 14.04

1 controller node (Ironic-conductor, Ironic-api, tftp, ipmitool,
nova-api, nova-scheduler,....)
1 network node (neutron related agents)
1 comp node (nova-compute, ovs-agent)
5 bare metal nodes (all have IPMI module)


1) Correct driver
Atm i'm trying to use pxe_ipmitool instead of the default one by
devstack pxe_ssh. Is the ipmi driver workable ?
I'm asking because i don't see any doc about this driver and if i try to
boot a node the node do nothing. A switch on => off and off => on is
working but thats it nothing more.


2) Networking
Network is a big topic and I've some questions about the initial
configuration of the bm nodes.

Devstack creates a pool within volumes for each bare metal node but for
which purpose ?

Devstack creates a new ovs bridge with a new created port and with this
mac you will creade a "node-port" in ironic. Will this mac be injected
on the bm host ? Is there any way to prevent manual configurations on
the network stack ? Normally should do this the ovs-agent ?!

How is the interaction between Neutron and Ironic port ? Is there any
special configuration steps needed ?


3) Nova interaction
I've created all needed images with the image-builder, i've created a
new bare metal flavor and i'm trying to boot my bm hosts via
nova boot --flavor baremetal --image
2e2c9e54-115b-4049-896f-c7db11995b89 --key-name test --nic
net-id=62729e73-ce7a-49ca-9ad4-9c5a4ca42fc9 testing
How is in this case the relationship between the created port of neutron
and the configured port of ironic ?




Some additional informations:
root at apitest:~# ironic node-list
+--------------------------------------+---------------+-------------+--------------------+
| UUID                                 | Instance UUID | Power State |
Provisioning State |
+--------------------------------------+---------------+-------------+--------------------+
| 4b9ae9b7-233e-4b98-81e7-510111fe24f7 | None          | power on    |
None               |
+--------------------------------------+---------------+-------------+--------------------+
root at apitest:~# ironic node-port-list 4b9ae9b7-233e-4b98-81e7-510111fe24f7
+--------------------------------------+-------------------+
| UUID                                 | Address           |
+--------------------------------------+-------------------+
| 4462d77c-19eb-4adb-a63e-4f035cc331cd | 52:54:00:37:e2:73 |
+--------------------------------------+-------------------+


root at apitest:~# ironic node-show 4b9ae9b7-233e-4b98-81e7-510111fe24f7
+------------------------+---------------------------------------------------------------------+
| Property               |
Value                                                               |
+------------------------+---------------------------------------------------------------------+
| chassis_uuid           |
b4a10b63-ed09-49a7-892c-ee5fbbf41737                                |
| created_at             |
2014-06-23T12:21:14.513492+00:00                                    |
| driver                 |
pxe_ipmitool                                                        |
| driver_info            | {u'pxe_deploy_ramdisk':
u'4b7c2ac1-c458-4383-ba19-4142bf372c08',    |
|                        | u'pxe_image_source':
u'2e2c9e54-115b-4049-896f-c7db11995b89',       |
|                        | u'pxe_root_gb': u'10', u'ipmi_username':
u'xxxx', u'ipmi_address': |
|                        | u'xxxx', u'ipmi_password': u'xxxx',
u'pxe_deploy_kernel': |
|                        |
u'409e7ab5-d54a-4553-9ee5-7b41da483902'}                            |
| extra                  |
{}                                                                  |
| instance_uuid          |
None                                                                |
| last_error             |
None                                                                |
| maintenance            |
False                                                               |
| power_state            | power
on                                                            |
| properties             |
{}                                                                  |
| provision_state        |
None                                                                |
| reservation            |
None                                                                |
| target_power_state     |
None                                                                |
| target_provision_state |
None                                                                |
| updated_at             |
2014-06-25T11:50:50.775798+00:00                                    |
| uuid                   |
4b9ae9b7-233e-4b98-81e7-510111fe24f7                                |
+------------------------+---------------------------------------------------------------------+

All configurations of Ironic and Nova i've checked with help of
http://docs.openstack.org/developer/ironic/deploy/install-guide.html
and the devstack configuration templates/steps.

Compute:
# Compute IRONIC#
compute_driver=ironic.nova.virt.ironic.IronicDriver
scheduler_host_manager=ironic.nova.scheduler.ironic_host_manager.IronicHostManager
ram_allocation_ratio=1.0
reserved_host_memory_mb=0
compute_manager=ironic.nova.compute.manager.ClusteredComputeManager

[ironic]
# Ironic keystone admin name
admin_username=ironic
#Ironic keystone admin password.
admin_password=xxx
# keystone API endpoint
admin_url=https://xxxx.local:35357/v2.0
# Ironic keystone tenant name.
admin_tenant_name=service
# URL for Ironic API endpoint.
api_endpoint=http://xxxx.local:6385/v1







I know it's a complex topic and this problems can occurs by thousand
miss configurations but I'm happy about every hint.
I hope you have all needed informations otherwise please ask me.


Cheers and thanks
Heiko


- -- 
anynines.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTqrpqAAoJELxFogM4ixOFFNkIALs9HkzE7bM42G7BYXsSfJSC
kn+AWv28Y6KBV5uikY+LmOcN0hVSnapetOFMxzlwE5TGquxP4fWgKCUrpeJlAHmH
4N9pul0kEovsMxhORZfyYOJdXVkeVhpXLrtrMxQukvr337I0PDjWBWeXpiCCQupQ
eavckknqxXWCnXqj3iuqmPrV1EqxWXJ2xkNnDIBnQ01ex/B/1NLG9FbuLRD+Mn64
lzs0qJhw2L7gYYEbmBufAFkR3wLe3KlAXRMYcjOJ7mSyRPwBayF8b+adH+6HWX/9
vtau0uWBQ7mOos7rwbeS7aAnlwcZkIztZdoLfjCaZRYy1Co2Jwax1Z7jlu/bpbU=
=0os1
-----END PGP SIGNATURE-----