Description of problem:

Documentation implies that Ironic is supported in the OSP director Overcloud:

- https://access.redhat.com/documentation/en/red-hat-enterprise-linux-openstack-platform/7/bare-metal-provisioning/chapter-1-install-and-configure-openstack-bare-metal-provisioning-ironic

"OpenStack Bare Metal Provisioning (ironic) provides the components required to provision and manage physical machines for end users. Bare Metal Provisioning in the Overcloud interacts with the following OpenStack services:"

"If you used the director to deploy your OpenStack environment, the database and messaging services are installed on a Controller node in the Overcloud."

"Alternatively, install and configure Bare Metal Provisioning components on a dedicated openstack-nova-compute node; see Compute Node Requirements in the Director Installation and Usage guide for hardware requirements."

"A RHEL OpenStack Platform environment with Bare Metal Provisioning services configured on an Overcloud node. You must have completed all steps in this guide up to and including Section 2.4, “Configure PXE for Bare Metal Provisioning”."

"# openstack baremetal introspection start NODE_UUID --discoverd-url http://overcloud IP:5050"

"Replace overcloud IP with the service_url value that was previously set in ironic.conf."

- https://access.redhat.com/documentation/en/red-hat-enterprise-linux-openstack-platform/version-7/release-notes/#idm140310893120672

The release notes list Ironic as fully supported:

"OpenStack Bare Metal Provisioning (ironic)
    The Bare Metal Provisioning service is now supported in Compute (using Compute and OpenStack Networking service configuration). The service integrates with the Compute service (in the same way that virtual machines are provisioned), and provides a solution for the 'bare-metal-to-trusted-tenant' use case. For example, within the OpenStack cloud:

        Hadoop clusters can be deployed on bare metal.
        Hyperscale and high-performance computing (HPC) clusters can be deployed.
        Database hosting for applications sensitive to virtual machines can be used. 

    The service consists of the Bare Metal Provisioning API, a Conductor, database- and hardware-specific drivers, and leverages common technologies like PXE, IPMI, and DHCP. With this release, the Bare Metal Provisioning service can also now be passed capabilities defined in a flavor's extra-spec key."

Although Ironic is supported as a service it has not been integrated into OSP director.
- any scale/update/upgrade/deploy operation will overwrite the manual changes suggested in this document
- the service is not integrated with HAproxy and pacemaker, which means that it will not be reachable after a VIP failover

If Ironic is supported in the overcloud, the document needs to be updated so the deployment steps fully integrate Ironic into the overcloud including update operations, deployments, and clustering.

If Ironic is not fully supported in the overcloud than the document should be updated to reflect this:
- notes should be added about limitations for installing it in this way

I would like to see the document updated to explain that Ironic is tested and supported by Red Hat but has not been integrated in director, and then list the many caveats for deploying per the steps in this document.