NSX|v service insertion handle upgrade

Bug #1604567 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vmware-nsx
Fix Released
Undecided
Unassigned

Bug Description

https://review.openstack.org/336920
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/vmware-nsx" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 8451309333f56a83dec5dd73c9e93ea5b0c1bad1
Author: Adit Sarfaty <email address hidden>
Date: Sun Jul 3 15:40:02 2016 +0300

    NSX|v service insertion handle upgrade

    When the service insertion is first enabled, and a security group is created,
    the plugin should do 2 things to allow the user to start working with service
    insertion immediately:
    1. Add all the current compute ports (VMs) to service insertion security group.
    2. Depending on the configuration, the driver will create any->any flow classifier entry,
       and any->any redirect rule at the backend so all the traffic will be redirected
       to the security partner.

    DocImpact: new nsxv configuration: service_insertion_redirect_all
    In True the plugin will create a rule to redirect all the traffic to the security partner.

    Change-Id: I2d45f4db821e205ccb09f02e2579d05c938c2658

Tags: doc vmware-nsx
Adit Sarfaty (asarfaty)
Changed in vmware-nsx:
status: New → Fix Committed
status: Fix Committed → Fix Released
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.