RFE: VIP support with allowed_address_pairs

Bug #1664805 reported by futangw
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Wishlist
futangw

Bug Description

Tacker data type tosca.nodes.nfv.CP.Tacker currently does not support allowed_address_pairs property, that is impossible to implement Virtual IP with Tacker for NE redundancy consideration.
allowed_address_pairs could be passed to HOT template transparently.

futangw (futangw)
Changed in tacker:
assignee: nobody → futangw (futangw)
Revision history for this message
yong sheng gong (gongysh) wrote :

anti_spoofing_protection: false is for this.

Revision history for this message
yong sheng gong (gongysh) wrote :

but allowed_address_pairs is also welcomed

Changed in tacker:
milestone: none → pike-1
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
futangw (futangw) wrote :

Hi, gongysh,

thanks for taking this.

yes, setting 'anti_spoofing_protection: false' allows VIP, but with disabled security. it's good to have both. :)

thanks,
futangw

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tacker (master)

Fix proposed to branch: master
Review: https://review.openstack.org/435187

Changed in tacker:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.openstack.org/435187
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=e1bc853b72546e1bbcce09382b67adc3334d18b3
Submitter: Jenkins
Branch: master

commit e1bc853b72546e1bbcce09382b67adc3334d18b3
Author: futangw <email address hidden>
Date: Wed Feb 15 15:45:07 2017 -0500

    Add allowed_address_pairs support in tacker CP

    Currently the tacker connection point (CP) support Virtural IP only if
    the security group is off (via anti_spoofing_protection off).
    But it's good to have both by supporting allowed_address_pairs.
    This RFE is for this purpose.

    Closes-Bug: #1664805
    Change-Id: I9fa1d4b69f8cbf51b047110cd6cfa61fb91a0bf0

Changed in tacker:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tacker 0.8.0

This issue was fixed in the openstack/tacker 0.8.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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