The "<ESD name>" _can_ collide with a neutron l7_policy name

[zancas]

ESD names, as described here:

https://devcentral.f5.com/articles/customizing-openstack-lbaasv2-using-enhanced-services-definitions-25681

can conflict with l7_policy names.

A simple fix is to prepend a magic string to all ESD names, e.g.:

<ESD_NAME> = "f5_ESD_"<ESD_SPECIFIC_NAME>

[richbrowne]

If a user creates a L7 policy that has the same name as an ESD, then the ESD will be applied. We have no way of determining what the user's intent is.

Perhaps some naming guidelines included in the documentation would be helpful

[jgruber]

Agreed.. we simply document this.

Don't forget that we are 'hand waving' many profile, iRule, and traffic policy collisions on the BIG-IP as well with the proviso that the provider which constructs the ESD needs to test them. We can not turn the agent in a 'rules engine' for validity of all possible TMOS functionality.