trove/locality-support-for-clusters-78bb74145d867df2.yaml at master - trove - OpenDev: Free Software Needs Free Tools

openstack/trove

Peter Stachowski 51f2655770 Locality support for clusters

In order to allow clusters to be all on the same hypervisor
(affinity) or all on different hypervisors (anti-affinity) a new
argument (locality) needed to be added to the Trove cluster-create API.

This changeset addresses the Trove server part of this feature.
'locality' can now be added to the ReST payload for a cluster-create
command and it is passed along as a scheduler hint to Nova.

The cluster scenario tests were enhanced to test that 'affinity'
works. Testing that 'anti-affinity' fails proved to be too
time consuming, since at present the only way for a cluster to
'fail' is to timeout (and that takes 10 hours).

The server-group is checked to make sure it is created properly,
and that it has been deleted after all the related instances are gone.

DocImpact: New functionality

Partially implements: blueprint replication-cluster-locality
Depends-On: Ie46cfa69ffe6a64760aca38c495563f5724bd0d0

Change-Id: I657bf5c023d0257e462cc39f57c16eb6ee83807a

2016-07-07 21:30:10 +00:00

8 lines

238 B

YAML

Raw Permalink Blame History

 ---
 features:
     - A locality flag was added to the trove ReST API to
       allow a user to specify whether the instances of a
       cluster should be on the same hypervisor (affinity)
       or on different hypervisors (anti-affinity).