VPNaaS: leftid should be configurable

[Yi Jing Zhu]

Currently, both left & leftid are filled with external_ip automatically. But sometimes, user may want to specify the leftid as they desired, such as an email address.
It would be better if this can be supported.

Pre-conditions: None

Step-by-step reproduction steps:
1) create an ipsec connection from dashboard or CLI, there is no leftid option.

Version:
Stable Kilo/CentOS7/RDO

Thanks!

[Paul Michali (pcm)]

Are there requests from users for this capability? We have the ability to use email address for peer, but I've never seen it used.

[Yi Jing Zhu (nick-zhuyj)]

Hello Paul,
Our scenario is that, VPNaaS is behind a NAT, and then the leftid will be automatically filled as the local private IP of the neutron router gateway interface. But we don't want to expose this private IP for customers. So we want to fill the leftid as we desired.

Thanks!

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/310676
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=7cf4ef682f83fc08484011454f62c27882064dff
Submitter: Jenkins
Branch: master

commit 7cf4ef682f83fc08484011454f62c27882064dff
Author: nick.zhuyj <email address hidden>
Date: Wed Apr 27 03:36:02 2016 -0500

    Support local_id configuration

    In some case, we want to specify the local id instead of use the
    external ip. For example, the router is behind NAT, and we don't
    want to expose this IP to peer. This patch will make local_id
    configurable. Most often, local id would be domain name, email
    address etc. But if local id is not configured then external ip
    will still be used as the leftid.

    Note: this change is DocImpact & APIImpact

    Change-Id: I2433d72ba22ce410cbfafb7b8bfb16f51eefdfc1
    Closes-Bug: #1513353

[Armando Migliaccio (armando-migliaccio)]

The fix proposed here left much to be desired. A release note is missing, and the API extension was changed in place without taking into account that a user is unable to discover whether or not a system does support this capability. This should be reopened.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/neutron-vpnaas 9.0.0.0b1 development milestone.

[Ihar Hrachyshka (ihar-hrachyshka)]

Hm. Why do we track the bug for Neutron RC1? VPNaaS is not even in Stadium.

[Cao Xuan Hoang (hoangcx)]

I think this bug can be closed as it is covered by https://bugs.launchpad.net/neutron/+bug/1576888 and https://review.openstack.org/#/c/378068/ . Is that right?

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Bug closed due to lack of activity, please feel free to reopen if needed.