Paul Michali b30f876885 VPNaaS: Separate validation for Cisco impl ... Moving validation logic from Cisco service driver, into a validation subclass, so that it'll be applied during the persistence phase (so validation failures can block the persistence, instead of setting to error state). This is part of the effort to separate out L3 validation and builds upon the reference implementation changes being reviewed in 102351. Note: One unit test is commented out, due to a bug in oslo.messaging 1.3.0. It will be uncommented later, once 1.4.0.0.a3 or newer is available for use. Change-Id: I6040e6d8ab32b707bcf67a0882507b7ee2d4bebe Partial-Implementation: blueprint l3-svcs-vendor-validation		2014-07-16 15:05:01 -04:00
..
__init__.py	VPNaaS: separate out validation logic for ref impl	2014-07-16 15:05:01 -04:00
cisco_csr_db.py	Switch to using of oslo.db	2014-06-30 14:07:59 +03:00
cisco_ipsec.py	VPNaaS: Separate validation for Cisco impl	2014-07-16 15:05:01 -04:00
cisco_validator.py	VPNaaS: Separate validation for Cisco impl	2014-07-16 15:05:01 -04:00
ipsec.py	Moved rpc_compat.py code back into rpc.py	2014-06-24 10:35:39 +02:00