You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What does chi-in-a-box expect for an IPMI configuration?
Does the controller node provide DHCP for IPMI addresses?
Should you set IPMI addresses to match ironic_provisioning subnet in site-config/defaults.yml? (The answer here is no)
I originally asked this question in Slack. Opening a Github issue at Mark's request and pasting his original Slack response to the question for the issue record.
it doesn’t provide DHCP by default for the IPMI addresses. We’ve been habitually setting them to static IPs, but you could run a dhcp server instead
all we assume is routed access to whatever addresses they have, it actually shouldn’t be the ironic_provisioning subnet, which is instead used to boot the nodes onto while loading an image
simplest would likely be to put the IPMI interfaces on a separate switch/vlan/network, and give them a dedicated subnet, and then put some address in that subnet on the controller node
the goal being that we want those interfaces to work, even if the entire set of openstack services is down. Just a safeguard against circular dependencies
The text was updated successfully, but these errors were encountered:
What does chi-in-a-box expect for an IPMI configuration?
Does the controller node provide DHCP for IPMI addresses?
Should you set IPMI addresses to match
ironic_provisioning subnet
insite-config/defaults.yml
? (The answer here is no)I originally asked this question in Slack. Opening a Github issue at Mark's request and pasting his original Slack response to the question for the issue record.
The text was updated successfully, but these errors were encountered: