Port Chain Update Replaces the Existing Flow Classifiers

[Prithiv]

The port-chain-update PC --flow-classifier actually replaces the new flow classifier with the existing one unless specified both existing and the new flow classifier in the port chain update. There is no way to add another flow classifier by providing what classifier i have to insert in the existing chain. Should the port-chain-update just add the new flow classifier to the existing chain rather than the requirement to provide both classifiers in update

[RaoFei (milo-frao)]

If we check the other object update operation implementation in Neutron, we can find almost all the object's list update will use the new replace the old.
eg,
1. create object['attr'] = [a,b], then object['attr'] = [a,b]
2. update object['attr'] = [c], then object['attr'] = [c]
3. update object['attr'] = [a,b,c], then object['attr'] = [a,b,c]

There are many object implement as this behavior above.
eg,
port object's security_groups list,
subnet object's allocation_pools, dns_nameservers, and host_routes list.
router object's external_fixed_ips, routers list
...

So, it's acceptable to replaces the new flow classifier with the existing one unless specified both existing and the new flow classifier in the port chain update.

We can discuss more about this.

[xiaodongwang (xiaodongwang991481)]

Hi Raofei, How is the status of bug? If it is resolved, please close it.

[Bernard Cafarelli (bcafarel)]

The openstack CLI for SFC has this 'additive' behaviour, is it enough for this bug?