Ensure that extended ethertypes still work by name
When the change to add support for extended ethertypes was introduced,
one scenario for backwards compatibility was not addressed in the
validator: using the canonical string names for ethertypes. This was
previously supported in the original implementation, using 'IPv4' or
'IPv6' for example.
Since the list of canonical ethertype names is available from os-ken we
consume it from there, which adds an additional dependency for
neutron-lib.
Reviewed: https:/ /review. opendev. org/673692 /git.openstack. org/cgit/ openstack/ neutron- lib/commit/ ?id=24aef1398b5 b69967696aa8cb6 598ab1be37c626
Committed: https:/
Submitter: Zuul
Branch: master
commit 24aef1398b5b699 67696aa8cb6598a b1be37c626
Author: Nate Johnston <email address hidden>
Date: Tue Jul 30 17:15:24 2019 -0400
Ensure that extended ethertypes still work by name
When the change to add support for extended ethertypes was introduced,
one scenario for backwards compatibility was not addressed in the
validator: using the canonical string names for ethertypes. This was
previously supported in the original implementation, using 'IPv4' or
'IPv6' for example.
Since the list of canonical ethertype names is available from os-ken we
consume it from there, which adds an additional dependency for
neutron-lib.
Related-Bug: #1838473 691d95c6c555f0c 56ae13d1a33
Change-Id: I53c6538dfbeea9