1. Proposed title of this feature request Default gateway for foreman should be configurable 2. Who is the customer behind the request? Account: Openwave (acct #5235648) TAM customer: no SRM customer: yes Strategic: yes 3. What is the nature and description of the request? There should be a configurable parameter to decide if you want foreman to be the gateway and forward packets or if we want to use the network gateway as the defualt gateway 4. Why does the customer need this? (List the business requirements here) They don't want the foreman server to be a single point of failure for gateway traffic 5. How would the customer like to achieve this? (List the functional requirements here) There should be a configurable parameter to decide if you want foreman to be the gateway and forward packets or if we want to use the network gateway as the defualt gateway 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
This applies to only non-controller hosts. Controllers are set to the public_api subnet and *must* remain there. The other hosts will use public_api if it exists, but otherwise fall back to using the Provisioning/PXE. This is something that you can change on each host and puppet won't try to "fix it" later.
There are some really intricate requirements around the default gateway depending on the layout. For example, public_api must be the default gateway on controllers and certain layouts nova networking layouts need the external subnet. This is all done in the code today. Situations where we don't do the right thing should be filed and fixed.