Hide Forgot
On a client site doing an OSP, CF installation and have run into a likely documentation bug, an error or absent section. Possibly also missing parts to actual deployment tooling as well. The OSP consultant here suggested the deployment process / goal produces a locked down undercloud provisioning network. Cloudforms requires access to this network to attach to that as a infrastructure provider. POLA would suggest that a "done" openstack undercloud not immediately need to be reconfigured when CF is deployed and attempts to connect to it. A number of ways to resolve this, off the top of my head: * multi home CF instances, allow attaching to undercloud network (implemented here) * route the undercloud provisioning network * apache/ha proxy to provisioning network CF appliances do not ship with multiple nics (actually, just as a disk image). But shipping those (somehow) with multiple nics also could help. Failure here is in documentation (of OSP and/or CF), the OSP tooling, and/or single-homed CF appliances, and/or training updates to allow CF to directly access the undercloud API without extra OSP and CF appliance configuration.
notification drivers, and ceilometer configuration also a point of reconfiguration. https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/managing-providers/chapter-3-cloud-providers https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/paged/quickstart-guide-for-cloudforms-with-red-hat-openstack-platform/chapter-3-adding-an-openstack-cloud-provider Also (and a CF bug) the OPS documentation on how to use CF is much more detailed then the CF documentation. This seems redundant to have both.