lb policy should be able to work without scaling/deletion policy
Bug #1536481 reported by
Yanyan Hu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| senlin |
Fix Released
|
Undecided
|
Yanyan Hu | ||
Bug Description
Lb policy should be able to work without scaling/deletion policy. It should have the ability to choose deletion candidates when they are not provided in action.data by other policies.
| Changed in senlin: | |
| assignee: | nobody → Yanyan Hu (yanyanhu) |
| Changed in senlin: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to senlin (master) | #1 |
| Changed in senlin: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 92887f5312142d2
Author: yanyanhu <email address hidden>
Date: Thu Jan 21 03:39:36 2016 -0500
Further rework lb_policy
This patch further reworks lb_policy to make it support cases
where no scaling_policy and/or deletion_policy is attached to
cluster.
Change-Id: I529f74f59dec9e
Closes-Bug: #1535508
CLoses-Bug: #1536481