openstack
/
neutron-specs
Code Issues Proposed changes

Missing caveat in NC DSCP spec 

added section explicitly calling out a lock on certain
variables in the classification resources to prevent
updating.
This avoids an issue with the classifications being
updated but the classifier having no way to inform its
consumers.

Change-Id: If937e343484387ecce4a3709bed3ca74cc52b9bc
This commit is contained in:
David Shaughnessy 2020-01-20 15:38:56 +00:00
parent 86e51045ab
commit acc57d57c4
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
specs/ussuri/qos_classifier.rst
View File

@ -208,6 +208,15 @@ classifications can be used, a few points need to be clarified:
not created or deleted. They need to have been previously
created using the User-facing Classifications API.
- As Neutron Classifier is unable to force an update action to it's
consumers and as users may be unaware of all the consumers of a
classification, the classification "definition" and "type" fields and the
classification group "classifications", "classification_groups" and
"operator" fields cannot be updated after creation.
ie.
A classification is consumed by both QoS and Security Groups with
a user only knowing about QoS consuming the classification.
The initial model of the CCF will include the following Classification Types:
Ethernet, IPv4, IPv6, TCP and UDP, which when combined are sufficient
to provide any 5-tuple classification.