VPNaaS admin up/down on service/connection broken

[Paul Michali]

With an active IPSec site-to-site connection, if the VPN service state is changed to admin down, the connection and service states still show as ACTIVE and traffic still flows over the connection.

If the IPsec site-to-site connection state is changed to admin down, the connection still shows as ACTIVE and traffic passes as well.

Does not look like the update_vpnservice API forwards to the device driver.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/81124

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/81124
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=23037823adbbf0bfc9c6398e8d460e84d49e4e6f
Submitter: Jenkins
Branch: master

commit 23037823adbbf0bfc9c6398e8d460e84d49e4e6f
Author: Paul Michali <email address hidden>
Date: Fri Mar 14 15:21:03 2014 +0000

    VPNaaS support for VPN service admin state change and reporting

    For VPN service admin state changes, hook up the API call to the service
    driver so that the configuration changes can be applied.

    Modify the status reporting, so that the VPN service and IPSec
    connection status' match the actual status when admin state down
    actions are performed (on both the service and connection).

    Change-Id: Ife7176675d20bb3ea529a4d79fa92a61f9550a6a
    Closes-Bug: 1291609