From 492682c3239ec47ffe876c162ad2ae10a703c84e Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Thu, 16 Oct 2014 18:53:44 -0400 Subject: [PATCH] changes to vm_placement changed a compute service to the compute service added a , after the term host changed to the queue vs. just queue Change-Id: I8d022f26ace5a97f335dc3261b81c40780516adf --- doc/training-guides/common/section_vm-placement.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/training-guides/common/section_vm-placement.xml b/doc/training-guides/common/section_vm-placement.xml index e6d81611..6789e06e 100644 --- a/doc/training-guides/common/section_vm-placement.xml +++ b/doc/training-guides/common/section_vm-placement.xml @@ -8,8 +8,8 @@ Compute uses the nova-scheduler service to determine how to dispatch compute and volume requests. For example, the nova-scheduler service determines which host a VM should launch - on. The term host in the context of filters means a physical node - that has a nova-compute + on. The term host, in the context of filters, means a physical node + that has the nova-compute service running on it. You can configure the scheduler through a variety of options.
@@ -21,7 +21,7 @@
Just as shown by the above figure, nova-scheduler interacts with - other components through queue and central database repo. For + other components through the queue and central database repo. For scheduling, the queue is the essential communications hub. All compute nodes (also known as hosts in terms of OpenStack) periodically publish their status, resources available and