Service chain related parameter updates are too disruptive
Bug #1446587 reported by
Magesh GV
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Fix Released
|
High
|
Magesh GV | ||
Bug Description
Today, any update to policy rule, classifier etc instead of invoking service chain update, deletes and recreates the service chain.
Even on Service chain side, any node or spec update results in recreating the whole chain. These update operations should be as non-disruptive as possible.
| Changed in group-based-policy: | |
| assignee: | nobody → Magesh GV (magesh-gv) |
| Changed in group-based-policy: | |
| status: | New → In Progress |
| Changed in group-based-policy: | |
| importance: | Undecided → High |
| milestone: | none → kilo-gbp-4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to group-based-policy (master) | #1 |
| Changed in group-based-policy: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to group-based-policy (stable/juno) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to group-based-policy (stable/juno) | #3 |
| tags: | added: in-stable-juno |
| Changed in group-based-policy: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 43a47143b817694
Author: Magesh GV <email address hidden>
Date: Tue Jun 30 09:27:02 2015 +0530
Gracefully handle parameter updates that affects Service Chain
Avoids deleting and creating the Chain instance for Rule/PRS/PTG
updates wherever the operation just requires just an Chain
instance update.
Closes-Bug: 1446587
Change-Id: Id2be94daa01d86