Heat: add availability_zone 89/48889/1
authorRoss Brattain <ross.b.brattain@intel.com>
Thu, 24 Aug 2017 22:06:50 +0000 (15:06 -0700)
committerRoss Brattain <ross.b.brattain@intel.com>
Thu, 14 Dec 2017 03:46:30 +0000 (03:46 +0000)
commit6c191845688b5c6d1fdf71524d820dc67f15b888
treebe251ea41d03bbf5b82e0b8a8d6510eed1fa6c3b
parent4f0b2293ce25d8311d352bc4f10708d6a1e00c79
Heat: add availability_zone

Users would like to ensure placement of VMs on specific compute nodes so
that the measurements are meaningful. Examples: Measure network
performance in different scenarios (VMs in same host, in different
hosts, across fabric, across tenants)

Example:

context:
  name: yardstick
  placement_groups:
    pgrp1:
      policy: "availability"
  servers:
    tg_0:
      floating_ip: true
      placement: "pgrp1"
      availability_zone: "zone2"
    vnf_0:
      floating_ip: true
      placement: "pgrp1"
      availability_zone: "zone1"

Change-Id: I28a757c25ae3f5b3571ab3edd82d51ceba32c302
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
(cherry picked from commit 81b9d338268f47f3d8863f10ef3940f0ea79d618)
tests/unit/benchmark/contexts/test_model.py
yardstick/benchmark/contexts/model.py
yardstick/orchestrator/heat.py