Bug 1614484 - Red Hat OpenStack Platform Bare Metal Provisioning" document should be updated to include Introspection in Overcloud
Summary: Red Hat OpenStack Platform Bare Metal Provisioning" document should be update...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Alex McLeod
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1480137
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-09 17:48 UTC by mlammon
Modified: 2022-08-26 12:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-05 12:56:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-2506 0 None None None 2022-08-26 12:19:59 UTC

Description mlammon 2018-08-09 17:48:59 UTC
Red Hat OpenStack Platform 14 Bare Metal Provisioning document should be updated to include Introspection in Overcloud and its use case(s) examples.

1) configuration to allow ironic inspector services in overcloud  

 http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/environments/services/ironic-inspector.yaml
and include an inspection range (this is just example)
We will need to get details from development

parameter_default:
    IronicInspectorIpRange: 192.168.24.200,192.168.24.250 

2) introspection of baremetal node example(s) (i.e)

. overcloudrc
openstack baremetal introspection start node <uuid> or name

3) check logs, etc

Comment 1 Dan Sneddon 2018-08-15 21:58:28 UTC
Actually, the IronicInspectorIpRange is deprecated. See this releasenote:

[master]$ cat releasenotes/notes/ironic-inspector-use-dnsmasq_ip_subnets-abba77307e761b96.yaml
---
features:
  - Adds support to configure ironic-inspector with multiple ip ranges.
    This enables ironic-inspector's DHCP server to serve request that
    came in via dhcp-relay agent.
deprecations:
  - The parameter ``IronicInspectorIpRange`` is deprecated. Use the new
    ``IronicInspectorSubnets`` instead.


So really we need to document the IronicInspectorSubnets parameter. Requesting some documentation of its usage from hjensas.

Comment 2 Harald Jensås 2018-08-16 13:08:39 UTC
IronicInspectorSubnets is a list of IP ranges + additional dhcp options required for dhcp-relay. It maps to the dnsmasq_ip_subnets parameter of the ironic puppet module[1]

Previously we used:

parameter_default:
    IronicInspectorIpRange: 192.168.24.200,192.168.24.250 

With the new option we would do:

parameter_default:
    IronicInspectorSubnets:
        - ip_range: 192.168.24.200,192.168.24.250


For advanced config supporting multiple subnets via dhcp-relay with different dhcp options for netmask and gateway we would do:

parameter_default:
    IronicInspectorSubnets:
        - ip_range: 192.168.24.200,192.168.24.250
          tag: siteA
          netmask: 255.255.255.0
          gateway: 192.168.24.1
        - ip_range: 192.168.25.200,192.168.25.250
          tag: siteB
          netmask: 255.255.255.0
          gateway: 192.168.25.1


If we want two ranges in the same subnet we can do:

parameter_default:
    IronicInspectorSubnets:
        - ip_range: 192.168.24.100,192.168.24.150
        - ip_range: 192.168.24.200,192.168.24.250



[1] https://github.com/openstack/puppet-ironic/blob/master/manifests/inspector.pp#L144-L159


Note You need to log in before you can comment on or make changes to this bug.