For now - it might be an idea to simply remove those options and document it better.
This will result in the following:
* New OVS-DVR deploys will need to know (and read the documentation we add) to create a custom env.d file.
* Existing OVS-DVR deploys will continue as normal, EXCEPT when adding a new compute host (assuming they first updated their OSA deploy and then tried to deploy to the new host) - a release note will be added.
This is because the dynamic_inventory doesn't actively remove the hosts, since they haven't changed, as such the groupings remain the same.
For now - it might be an idea to simply remove those options and document it better.
This will result in the following:
* New OVS-DVR deploys will need to know (and read the documentation we add) to create a custom env.d file.
* Existing OVS-DVR deploys will continue as normal, EXCEPT when adding a new compute host (assuming they first updated their OSA deploy and then tried to deploy to the new host) - a release note will be added.
This is because the dynamic_inventory doesn't actively remove the hosts, since they haven't changed, as such the groupings remain the same.