add stickiness=1 to neutron agents PM resources

Bug #1312177 reported by Sergey Vasilenko on 2014-04-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Dmitry Ilyin
4.1.x
High
Fuel Library (Deprecated)

Bug Description

add stickiness=1 to neutron agents Pacemaker resources

Changed in fuel:
status: New → Confirmed
Andrew Woodward (xarses) wrote :

This is an issue for HA because it can cause L3 agent to move when not necessary which causes an outage. Increasing to high and retargeting to 5.0

Changed in fuel:
importance: Wishlist → High
milestone: 5.1 → 5.0
assignee: Sergey Vasilenko (xenolog) → Andrew Woodward (xarses)
Changed in fuel:
assignee: Andrew Woodward (xarses) → Sergey Vasilenko (xenolog)

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

Changed in fuel:
status: Confirmed → In Progress
Bogdan Dobrelya (bogdando) wrote :

there is an option to restrict some movements for the business time , see http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-rules-cluster-options.html#id1941641

Mike Scherbakov (mihgen) on 2014-05-14
Changed in fuel:
assignee: Sergey Vasilenko (xenolog) → Dmitry Ilyin (idv1985)
Dmitry Ilyin (idv1985) wrote :

Resource stickiness is the measure of how much a resource wants to stay where it is. Or you can think about it as a cost of resource movement to another server. If there is no stickness defined pacemaker will move any resource at will to achive what it thinks optimal placement is and it's usually pretty much random. Usually pacemaker doesn't move resources during the normal operation doing so only when cluster state changes.

If stickiness is defined resource will be moved only if there is a rule with more score then the stickness value that wants to move the resource. For example, colocation can have infinity score and it will be more important then any finite stickiness and resource will be moved. Or there could be colocation with negative infinity meaning that resources will never be together.

It's very common to set stickiness for every resource using resource-defaults because no one wants the resources to move around. Usually people set score to 100 like in CLuster From Scratch manual.

Setting stickiness to 1 for some resources? Why? Let's just set stickness using resource-defaults for all resources.

Reviewed: https://review.openstack.org/93297
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=ffb90ef1653c94b85625168fb04d3c6228ab0053
Submitter: Jenkins
Branch: master

commit ffb90ef1653c94b85625168fb04d3c6228ab0053
Author: Sergey Vasilenko <email address hidden>
Date: Mon May 12 16:51:45 2014 +0400

    add stickiness=1 to some singletone PM resources

    Change-Id: I208435a4b03007604d25e907b916018b99e2a903
    Closes-bug: #1312177

Changed in fuel:
status: In Progress → Fix Committed
Bogdan Dobrelya (bogdando) wrote :

backports-4.1.1?

Reviewed: https://review.openstack.org/96854
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=c83a8d6291624ac7769f286fb06515013cb11834
Submitter: Jenkins
Branch: stable/4.1

commit c83a8d6291624ac7769f286fb06515013cb11834
Author: Sergey Vasilenko <email address hidden>
Date: Mon May 12 16:51:45 2014 +0400

    add stickiness=1 to some singletone PM resources

    Change-Id: I208435a4b03007604d25e907b916018b99e2a903
    Closes-bug: #1312177

Meg McRoberts (dreidellhasa) wrote :

Documented as fixed in 4.1.1 Release Notes.

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

Other bug subscribers