python-neutronclient

Fix help and validation for peer_address and peer_id

Bug #1225129 reported by Nachi Ueno
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Fix Released
Medium
Paul Michali

Bug Description

We have updated spec based on a spec bug regarding to peer-address and peer-id
https://bugs.launchpad.net/openstack-api-site/+bug/1225125

(1) peer-id is not mandatory parameter now.
(2) we can accept string in peer-address.
(3) update help message based on new doc

Tags: vpnaas
Nachi Ueno (nati-ueno)
Changed in python-neutronclient:
status: New → Confirmed
importance: Undecided → Critical
importance: Critical → Medium
milestone: none → 3.0.0
Revision history for this message
Paul Michali (pcm) wrote :

Further discussion led to leaving peer_id as mandatory, so skipping (1).

Changed in python-neutronclient:
assignee: nobody → Paul Michali (pcm)
status: Confirmed → In Progress
Paul Michali (pcm)
tags: added: vpnaas
Akihiro Motoki (amotoki)
Changed in python-neutronclient:
milestone: 3.0.0 → none
Revision history for this message
Akihiro Motoki (amotoki) wrote :

As of Dec 2015, the help message looks correct.

  --peer-address PEER_ADDRESS
                        Peer gateway public IPv4/IPv6 address or FQDN.
  --peer-id PEER_ID Peer router identity for authentication. Can be
                        IPv4/IPv6 address, e-mail address, key id, or FQDN.

Changed in python-neutronclient:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.