yahoo-eng-team team mailing list archive

[OpenStack Infra <1595515@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/333338
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=468b2f1b8bfc6091ba7384f4f9266fdd1b15a2b4
Submitter: Jenkins
Branch:    master

commit 468b2f1b8bfc6091ba7384f4f9266fdd1b15a2b4
Author: Chandan Dutta Chowdhury <chandanc@xxxxxxxxxxx>
Date:   Thu Jun 23 18:16:55 2016 +0530

    IP Conntrack Manager changes for FWaaS v2
    
    IpConntrackManager class should be a singleton
    to be used by both SG and FWaaS v2 API at the same time
    
    Change-Id: I4a9f3d9b3ac7afe989c0efb1fa4e7fd792cd9610
    Closes-Bug: 1595515


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  IpConntrackManager class in ip_conntrack.py should be a singleton to
  be used by both SG and FWaaS

Status in neutron:
  Fix Released

Bug description:
  The FWaaS V2 APIs is going to configure security rules at a port
  level. It will need to use connection tracking and zone configuration
  methods defined in the ip_conntrack.py and iptables_firewall.py in
  neutron project.

  Some methods in the IptablesFirewallDriver in iptables_firewall needs
  to be moved to IpConntrackManager class in ip_conntrack.py. As
  IpConntrackManager will be used by both SG and FWaaS V2 APIs and both
  of them can be used at the same time, the IpConntrackManager should be
  a singleton responsible for allocating and reclaiming zones assigned
  to ports.

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