Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1339886

Summary: [Docs] [Instances] Document soft affinity rules
Product: Red Hat OpenStack Reporter: Andrew Dahms <adahms>
Component: documentationAssignee: Radek Bíba <rbiba>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Lopes <mlopes>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0 (Mitaka)CC: mlopes, srevivo
Target Milestone: gaKeywords: Documentation
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-22 23:33:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1093244    
Bug Blocks:    

Description Andrew Dahms 2016-05-26 05:26:04 UTC
In Red Hat OpenStack Platform 9, it is possible to apply soft affinity that allows users to specify a preference for two instances to start on the same Compute node where possible.

Details of the new rules should be added to the documentation. Perhaps a good candidate for "Table 3.4. Scheduling Filters" in the Instances and Images guide?

From the engineering bug: 

"As a tenant I would like to schedule instances on the same host if possible,
so that I can achieve colocation. However if it is not possible to schedule
some instance to the same host then I still want that the subsequent
instances are scheduled together on another host. In this way I can express
a good-to-have relationship between a group of instances.


End User might want to have a less strict affinity rule than what is today
available in server-group API extension. With the proposed good-to-have
affinity rule the End User can request nova to schedule the instance to the
same host if possible. However if it is not possible (e.g. due to resource
limitations) then End User still wants to keep the instances on a small
amount of different host.


This change would extend the existing server-group API extension with a new
policy soft-affinity. When a instance is booted into a group with
soft-affintiy policy the scheduler will use a new weight AffinityWeight to
sort the available hosts according to the number of instances running on them
from the same server-group.

This new soft-affinity policy is mutually exclusive with the other existing
server-group policies."

Comment 1 Andrew Dahms 2016-07-04 11:37:39 UTC
Assigning to Radek for review.

Comment 2 Radek Bíba 2016-07-04 13:23:36 UTC
Having read the spec and the upstream commit, I'd say this should go to the section on weights, not filters.

Comment 6 Andrew Dahms 2016-08-22 23:33:00 UTC
This content is now live on the Customer Portal.

Closing.