yahoo-eng-team team mailing list archive

[varun kumar yadav <varun.yadav@xxxxxx>]

Public bug reported:


neutron net-create  ext-net1 --router:external=True
neutron subnet-create  --allocation-pool start=192.142.0.60,end=192.142.0.100 --gateway 192.142.0.1 ext-net1 192.142.0.0/16 --enable_dhcp=False


neutron net-create net1
neutron subnet-create net1 10.10.1.0/24 --name sub1
neutron router-create r1
neutron router-interface-add r1 sub1
neutron router-gateway-set r1 ext-net1

neutron net-create net2
neutron subnet-create net2 10.10.2.0/24 --name sub2
neutron router-create r2
neutron router-interface-add r2 sub2
neutron router-gateway-set r2 ext-net1


neutron vpn-ikepolicy-create ikepolicy1
neutron vpn-ipsecpolicy-create ipsecpolicy1
neutron vpn-service-create --name myvpn1 --description "My vpn service" r1 sub1


neutron vpn-ikepolicy-create ikepolicy2
neutron vpn-ipsecpolicy-create ipsecpolicy2
neutron vpn-service-create --name myvpn2 --description "My vpn service" r2 sub2

neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice-
id myvpn1 --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1
--peer-address 192.142.0.61 --peer-id 192.142.0.61 --peer-cidr
10.10.2.0/24 --psk secret


neutron ipsec-site-connection-create --name vpnconnection2 --vpnservice-id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 10.10.1.0/24 --psk secret


create a subnet  in the network net1 and net2 respectively.
neutron vpn-service-update  myvpn1  <new-subnet-id 1>
neutron vpn-service-update  myvpn2 <new-subnet-id 2>

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1318600

Title:
  VPNasS-> Vpn service object cannot be updated  with multiple subnets

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  
  neutron net-create  ext-net1 --router:external=True
  neutron subnet-create  --allocation-pool start=192.142.0.60,end=192.142.0.100 --gateway 192.142.0.1 ext-net1 192.142.0.0/16 --enable_dhcp=False

  
  neutron net-create net1
  neutron subnet-create net1 10.10.1.0/24 --name sub1
  neutron router-create r1
  neutron router-interface-add r1 sub1
  neutron router-gateway-set r1 ext-net1

  neutron net-create net2
  neutron subnet-create net2 10.10.2.0/24 --name sub2
  neutron router-create r2
  neutron router-interface-add r2 sub2
  neutron router-gateway-set r2 ext-net1

  
  neutron vpn-ikepolicy-create ikepolicy1
  neutron vpn-ipsecpolicy-create ipsecpolicy1
  neutron vpn-service-create --name myvpn1 --description "My vpn service" r1 sub1


  
  neutron vpn-ikepolicy-create ikepolicy2
  neutron vpn-ipsecpolicy-create ipsecpolicy2
  neutron vpn-service-create --name myvpn2 --description "My vpn service" r2 sub2

  neutron ipsec-site-connection-create --name vpnconnection1
  --vpnservice-id myvpn1 --ikepolicy-id ikepolicy1 --ipsecpolicy-id
  ipsecpolicy1 --peer-address 192.142.0.61 --peer-id 192.142.0.61
  --peer-cidr 10.10.2.0/24 --psk secret

  
  neutron ipsec-site-connection-create --name vpnconnection2 --vpnservice-id myvpn2 --ikepolicy-id ikepolicy2 --ipsecpolicy-id ipsecpolicy2 --peer-address 192.142.0.60 --peer-id 192.142.0.60 --peer-cidr 10.10.1.0/24 --psk secret

  
  create a subnet  in the network net1 and net2 respectively.
  neutron vpn-service-update  myvpn1  <new-subnet-id 1>
  neutron vpn-service-update  myvpn2 <new-subnet-id 2>

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1318600/+subscriptions