yahoo-eng-team team mailing list archive

[Armando Migliaccio <1364221@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (INCUBATOR-JUNO, LIBERTY, MITAKA, NEWTON).
  Valid example: CONFIRMED FOR: INCUBATOR-JUNO


** Changed in: neutron
   Importance: Low => Undecided

** Changed in: neutron
       Status: Confirmed => Expired

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

Title:
  IPSec site connections in OpenStack Networking API v2.0 (neutron)
  Reference  - API v2.0 (neutron) and extensions

Status in neutron:
  Expired
Status in python-neutronclient:
  Won't Fix

Bug description:
   peer_id attribute  can be IPv4/IPv6 address as per design now ,but in notes mentioned as it can be IPv4/IPv6 address, e-mail address, key id, or FQDN.
  -----------------------------------
  Built: 2014-08-11T21:06:27 00:00
  git SHA: 3302e05316e88d42067e3c1555df34371043999d
  URL: http://docs.openstack.org/api/openstack-network/2.0/content/vpnaas_ext_ops_ipsec_site_connection.html
  source File: file:/home/jenkins/workspace/netconn-api-tox-doc-publishdocs/v2.0/section_neutron-ext-vpnaas.xml
  xml:id: vpnaas_ext_ops_ipsec_site_connection

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