yahoo-eng-team team mailing list archive

[sean mooney <1842061@xxxxxxxxxxxxxxxxxx>]

we can discuss deprecating the unscoped support or the filter in general
as we now have better alternatives  such as
https://docs.openstack.org/nova/latest/reference/isolate-aggregates.html

but given the upgrade impact this would need a deprecation cycle at a
minium to notify operators that they will need to resize all there
instances to update the flavor which is not cheap or we will need to
provide tooling such as nova-manage commands or similar to help with
that.

that falls out of the scope of a simple bug fix in my view as we would
have to come to a consensus on how to change the behavior which likely
should be done via a spec or (specless blueprint and mailing list/ptg
discussion)

given the above setting this to wont fix for now.

** Changed in: nova
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1842061

Title:
  Compute schedulers in nova - AggregateInstanceExtraSpecsFilter docs
  are not clear

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  - [x] This is a doc addition request.

  The description for the AggregateInstanceExtraSpecsFilter filter is
  not clear:

  https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#aggregateinstanceextraspecsfilter

  (note it's also described here:
  https://docs.openstack.org/nova/latest/user/filter-scheduler.html)

  It's not clear what aggregate_instance_extra_specs is used for.

  Note that further down in the document there are some examples:

  https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html#example-specify-compute-
  hosts-with-ssds

  So I guess based on that, it means you would just add metadata to a
  host aggregate like foo=bar and then tie a flavor to that by setting
  an extra spec of aggregate_instance_extra_specs:foo=bar on the flavor.
  But what about other standard extra specs like hide_hypervisor_id, you
  can't put the aggregate_instance_extra_specs prefix on that in the
  flavor since it would break the extra spec for the actual code that
  checks for that standard extra spec. Does that mean the flavor has to
  have both the scoped and unscoped spec? Or that the filter will handle
  the unscoped spec? It would be nice to have the documentation on the
  filter itself explain this and give examples of how to use it, for
  both a standard and custom flavor extra spec (note the latter has an
  example linked above for the ssd example).

  This originally came up while triaging bug 1841932 and trying to make
  sense of the filter (it's not very clear even by looking at the code).

  -----------------------------------
  Release:  on 2019-08-22 20:13:47
  SHA: 0882ea69ea0c46cf97ecd5a1ec49a3007f293c28
  Source: https://opendev.org/openstack/nova/src/doc/source/admin/configuration/schedulers.rst
  URL: https://docs.openstack.org/nova/latest/admin/configuration/schedulers.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1842061/+subscriptions