nova.git/nova/tests/scheduler, branch shared-key-msg

Merge "New select_destinations scheduler call"

2013-07-01T17:30:40+00:00

Merge "Add AggregateRamFilter"

2013-06-28T17:52:50+00:00

Merge "Add AggregateCoreFilter"

2013-06-28T17:41:39+00:00

New select_destinations scheduler call

2013-06-28T13:48:14+00:00

select_destinations returns a list of (host, node) tuples that satisfy
the request_spec and filter_properties passed to it.  This will allow
the conductor to get a list of destinations for workflows such as
creating or resizing an instance and then handle the orchestration
itself.

part of bp query-scheduler

Change-Id: I1a42cea64dbad67562d7efe8d759e6efb5ec8121

Merge "Clean up scheduler tests"

2013-06-25T20:35:41+00:00

Merge "Allow scheduler manager NoValidHost exception to pass over RPC"

2013-06-25T20:14:25+00:00

Extract live-migration scheduler logic from the scheduler driver

2013-06-24T09:49:07+00:00

Before moving the control of live-migration into the conductor,
extract the live-migration control logic into a separate class.

The callback to select_hosts will be replaced by a new
scheduler rpc method in a later changeset.

Part of blueprint live-migration-to-conductor
Change-Id: I6de33ada6dc377e20f8df07da92244f2c150b9fe

Add AggregateCoreFilter

2013-06-21T14:09:29+00:00

Implements blueprint per-aggregate-resource-ratio

* AggregateCoreFilter to support per-aggregate cpu_allocation_ratio
* Falls back to global setting if per-aggregate value not found

DocImpact

Change-Id: I9230f46e2490226f3c50d616aa173d4722095087

Add AggregateRamFilter

2013-06-21T13:58:21+00:00

Implements blueprint per-aggregate-resource-ratio

* AggregateRamFilter to support per-aggregate ram_allocation_ratio
* Falls back to global setting if per-aggregate value not found

DocImpact

Change-Id: I93e069f0ac3f595d9a2a17119274c7bfbe8fca31

Revert "Initial scheduler support for instance_groups"

2013-06-20T16:57:45+00:00

This reverts commit b2c17ae891b12118b9d11bf0ecc44e77956715c8.

While reviewing merged changes, I came across this one.  It's using the
conductor in a way that it shouldn't.  The scheduler has db access, so
there's no need to add the extra conductor overhead.  The best thing to
do here is to just revert for now, IMO.

Change-Id: Iaa0d67df7bb84913784d925cffebcd5f252249ea