aggregate filter leads vm in flavor with empty extrespecs cloud be booted on aggregate host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Description
===========
when i boot a vm with a flavor extra_specs is empty. vm will boot on aggregate host .
in my openstack environment, i have 3 nova-compute(
Add i create a host aggregate in nova zone with metadata "ssd=true". i put compute01 in this aggregate.
leave compute02 compute03 in nova zone with out any aggregate set.
when i boot vm with flavor aggregate_
but when i boot vm with flavor extra_specs is empty ,it also can boot on compute01.
when i see nova-scheduler log it debug info is aggregate intance extra filter return 3 available host .
but i expect vm can only boot on "compute02,
as we all know aggregate is used to tag host with some features like SSD and so on.
if other vm without aggregate metadata can boot on aggregate host ,i think this is a bug.
so i think we can change this scheduler filter code to "vm with flavor extra_specs is empty should not be booted on
aggregate host"
Expected result
===============
the vm will only be booted on compute02 or compute03
Actual result
=============
the vm be booted on compute01 .
Environment
===========
Mitaka openstack release code and 3 nova-compute host(compute01,
and set compute01 a aggregate SSD with metata (ssd=true)
Logs & Configs
==============
2016-10-14 17:17:03.143 14215 DEBUG nova.filters [req-e847975e-
summary: |
- vm will boot on aggregate host + aggregate filter leads vm in flavor with empty extrespecs cloud be + booted on aggregate host |
Changed in nova: | |
assignee: | nobody → jianfeng zhang (zhangjianfeng) |
status: | New → In Progress |
Fix proposed to branch: master /review. openstack. org/387855
Review: https:/