ESD policy for tag or naming collisions #1136
Description
Title
Explicit handling of tag or naming collisions with multiple L7 policies
OpenStack Release
Newton+
Description
How to handle collisions within ESD
Agent Version
Newton +
Operating System
Any
OpenStack Release
Newton+
Description
Explicit handling requests for ESD
Deployment
Rule 1 - All ESDs, and ESD combinations should be tested by the provider before deployment. The f5-openstack-agent does not guarantee the validity of the profiles, iRules, or traffic policies contained in the ESDs on the BIG-IPs. ESD Tags for specific profile, traffic policies, and iRules will be checked for their presence in the /Common partition of the BIG-IP, but no check will be performed that the named ESD will not disrupt traffic to the pool members.That is an exercise for testing left to the provider which publishes the ESDs.
Rule 2 - ESD trumps standard LBaaSv2 L7 policy. If any L7 policy is applied which is mapped to a published ESD name, any rules associated with the policy will not be honored, but rather the ESD will be applied.
Rule 3 - ESD are exclusive such that if an ESD is applied, no further L7 policies which are not naming ESDs will be applied. You MUST not mix an ESDs with standard LBaaSv2 L7 policy rules.
Rule 4 - ESD should add a tag virtual_service_type which should initially be limited to fastL4 and standard. If no ESDs specify virtual_server_type, the default will be standard. The first match of an L7 policy (one with the lowest position number attribute) to an ESD with the virtual_server_type tag will be the ESD to dictate the virtual service type for all ESDs applied. If any further L7 policies naming ESDs contain conflicting virtual_server_type tags, the entire ESD should be ignored.
Rule 5 - ESD should be 'pre-processed' on the f5-openstack-agent such that the cumulative deployment of multiple ESDs result in a single virtual service deployment on the BIG-IP. If conflicting ESD tags are present in multiple ESDs, the tag in the ESD matching the L7 policy with the lowest position number attribute will be assume the correct one. This matches the 'first match' processing of LBaaSv2 L7 policy.