> That's because you are talking more about openflow should use no-zone, > because that's the right way to do for openflow, which i agree with. But > my question here is about the derive types, if ipv4-address-no-zone and > ipv4-address are two derive types and user are free to use any of these > derive type. Currently openflowplugin is using ipv4-address, so why they > have to change their yang model to use no-zone. > https://git.opendaylight.org/gerrit/#/c/71083/3/extension/openflowjava-extension-nicira/src/main/yang/nicira-action.yang > <https://git.opendaylight.org/gerrit/#/c/71083/3/extension/openflowjava-extension-nicira/src/main/yang/nicira-action.yang> > > [#]https://git.opendaylight.org/gerrit/#/c/71083/ > <https://git.opendaylight.org/gerrit/#/c/71083/>
This a proposed patch, a starting point -- and merging this will break OFP downstreams. It just happens to do all that is needed on the OFP side to completely verify. The end result is of that is two-fold: 1) user cannot specify a zone by mistake, because having a zone there is no longer valid -- any attempt to do that will fail-fast. 2) OFP can rely on that data to be validated to not contain a zone and being a plain IP addres -- and hence can remove code stripping it All of this results in better overall user experience, I think, but that is just my opinion. Regards, Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
