<div dir="ltr">ok, My pleasure to help,<br><div>I created a bp for it:</div><div><a href="https://blueprints.launchpad.net/neutron/+spec/vpn-multiple-subnet">https://blueprints.launchpad.net/neutron/+spec/vpn-multiple-subnet</a><br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Dec 6, 2013 at 2:11 PM, Nachi Ueno <span dir="ltr"><<a href="mailto:nachi@ntti3.com" target="_blank">nachi@ntti3.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Yong<br>
<br>
Yes, to support multiple subnet is on the roadmap.<br>
I'll definitely welcome your help :P<br>
<br>
2013/12/5 Yongsheng Gong <<a href="mailto:gongysh@unitedstack.com">gongysh@unitedstack.com</a>>:<br>
<div><div class="h5">> I think we should allow more than subnet_id in one vpnservice object.<br>
> but the model below limits only one subnet_id is used.<br>
> <a href="https://github.com/openstack/neutron/blob/master/neutron/extensions/vpnaas.py" target="_blank">https://github.com/openstack/neutron/blob/master/neutron/extensions/vpnaas.py</a><br>
> RESOURCE_ATTRIBUTE_MAP = {<br>
><br>
>     'vpnservices': {<br>
>         'id': {'allow_post': False, 'allow_put': False,<br>
>                'validate': {'type:uuid': None},<br>
>                'is_visible': True,<br>
>                'primary_key': True},<br>
>         'tenant_id': {'allow_post': True, 'allow_put': False,<br>
>                       'validate': {'type:string': None},<br>
>                       'required_by_policy': True,<br>
>                       'is_visible': True},<br>
>         'name': {'allow_post': True, 'allow_put': True,<br>
>                  'validate': {'type:string': None},<br>
>                  'is_visible': True, 'default': ''},<br>
>         'description': {'allow_post': True, 'allow_put': True,<br>
>                         'validate': {'type:string': None},<br>
>                         'is_visible': True, 'default': ''},<br>
>         'subnet_id': {'allow_post': True, 'allow_put': False,<br>
>                       'validate': {'type:uuid': None},<br>
>                       'is_visible': True},<br>
>         'router_id': {'allow_post': True, 'allow_put': False,<br>
>                       'validate': {'type:uuid': None},<br>
>                       'is_visible': True},<br>
>         'admin_state_up': {'allow_post': True, 'allow_put': True,<br>
>                            'default': True,<br>
>                            'convert_to': attr.convert_to_boolean,<br>
>                            'is_visible': True},<br>
>         'status': {'allow_post': False, 'allow_put': False,<br>
>                    'is_visible': True}<br>
>     },<br>
><br>
> with such limit, I don't think there is a way to allow other subnets behind<br>
> the router be vpn exposed!<br>
><br>
> thoughts?<br>
><br>
> Thanks<br>
> Yong Sheng Gong<br>
><br>
</div></div>> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>