Comment 9 for bug 1645979

> Option 2: Introduce a conditional behavior of env.d in master, other branches are informed with docs.
>
> This would require work on the inventory, to check user_variables* and see if ovs/lxb was used, and then change the env.d accordingly.
>
> Pros:
> + Deployers of ovs/lxb would automatically get what they need without changes
> - It's a lot of wiring for something that could be reduced as a doc change, and maintaining an env.d file.

While this is certainly something we could explore, I'm hesitant to do so because of the uncertain future of the env.d mechanisms, specifically as discussed in https://bugs.launchpad.net/openstack-ansible/+bug/1643955. While env.d won't be going away in the near term, my preference would be to avoid adding too many behaviors to it that might introduce barriers to migrating away.

I'd also agree that forcing deployers to carry separate environment files for OVS would be annoying, but not necessarily out of line with how we generally do things. LXB is still our default. The downside is that to flex the OVS functionality in the gates some (more) env.d manipulation would have to be put in place.