Arranging the description of vcpu thread policy according to current Cloud API.

Change-Id: I7ca500e85d1f8e3e480bebce2f8d6b997e8a0e38
Signed-off-by: Gulsum Atici <gulsum.atici@canonical.com>
(cherry picked from commit 72ef227544b795ad947b81e690f7149fbd184c6e)

diff --git a/models/augments/epa.yang b/models/augments/epa.yang
index d47d6a9..af8b7cd 100644 (file)
--- a/models/augments/epa.yang
+++ b/models/augments/epa.yang
@@ -90,19 +90,15 @@ module epa {
               "CPU thread pinning policy describes how to
                place the guest CPUs when the host supports
                hyper threads:
-               AVOID   : Avoids placing a guest on a host
-                         with threads.
-               SEPARATE: Places vCPUs on separate cores,
-                         and avoids placing two vCPUs on
-                         two threads of same core.
+               REQUIRE : Each vCPU is allocated on thread siblings
+                         of the same core.
                ISOLATE : Places each vCPU on a different core,
                          and places no vCPUs from a different
                          guest on the same core.
                PREFER  : Attempts to place vCPUs on threads
                          of the same core.";
             type enumeration {
-                enum AVOID;
-                enum SEPARATE;
+                enum REQUIRE;
                 enum ISOLATE;
                 enum PREFER;
             }