OpenStack Staging-Ovirt Driver: global name \’sdk\’ is not defined

Getting Started The staging-ovirt driver allows OpenStack to easily use ovirt/RHV virtual machines as overcloud nodes.   For those of us running virtualized OpenStack labs, it's a huge step forward - as we either were previously having to hack our way around pxe_ssh or vmbc. Neither was a great solution. In order to use the staging-ovirt … Continue reading OpenStack Staging-Ovirt Driver: global name \’sdk\’ is not defined

OpenStack: Mapping Ironic Hostnames to Nova Hostnames

The Hostname Problem When deploying OpenStack via Red Hat OSP director you configure the hostname of your baremetal (ironic) nodes at time of import. This is done via json file, by default named instack-env.json (but often re-named, nodes.json). Below is an excerpt from that file. { "nodes" :  [ { "arch": "x86_64", "cpu": "4", "disk": … Continue reading OpenStack: Mapping Ironic Hostnames to Nova Hostnames

OpenStack: instackenv.json Format Example

Here is a quick and dirty example of the format of your instackenv.json. This is the file that Ironic uses to import nodes. Enter your IPMI user id under "pm_user" Enter your IPMI password under "pm_password"   [code language="css"] { "nodes":[ { "mac":[ "74:E6:E2:FB:71:B0" ], "cpu":"4", "memory":"6144", "disk":"40", "arch":"x86_64", "name":"control01", "pm_type":"pxe_ipmitool", "pm_user":"admin", "pm_password":"admin", "pm_addr":"10.75.99.120" }, … Continue reading OpenStack: instackenv.json Format Example

OpenStack Ironic: Manual Node Tagging and Mapping

Some of the OpenStack director guides that I have seen and read suggest using ACH Tools to perform role matching, which matches Ironic nodes to the most appropriate roles (flavors) bases on their CPU, Memory, and Disk configurations. However if you prefer to manually assign a role to a node follow the steps outlined below. Creating Flavors … Continue reading OpenStack Ironic: Manual Node Tagging and Mapping

OpenStack Ironic – CLI Cheat Sheet

Ironic is the baremetal provisioning component of OpenStack. Ironic interacts with hardware through a set of plug-ins. Technologies leveraged are PXE and IPMI as well as a few vendor specific plug-ins. Here are a few OpenStack Ironic commands that I have found useful when troubleshooting. List nodes registered with Ironic. $ ironic node-list   Show details … Continue reading OpenStack Ironic – CLI Cheat Sheet

OpenStack Ironic : JSON Validator

This handy tool, developed by an engineer at Red Hat, checks your Ironic JSON file for errors such as missing passwords, or non-unique MAC addresses. The script also tests connections to your bare metal (or virtual nodes in my test lab) to ensure that they are accessible.