Baremetal filters and default filters cannot be used simultaneously in the same nova

Bug #1787509 reported by Jiang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Undecided
Unassigned

Bug Description

Hello, my openstack version is pike.
There is only one nova-scheduler service in environment, but I have ironic nodes and kvm nodes.If I set use_baremetal_filters to True, I can only use baremetal_enabled_filters. If set use_baremetal_filters to False, I can only use enabled_filters.
Is there a way to use both filters at the same time? If I create ironic instance, use baremetal_enabled_filters. If I create vm instance, use enabled_filters.

Revision history for this message
Matt Riedemann (mriedem) wrote :

No that's not supported. I'm not entirely sure how various deployments handle this issue, if it's separate compute API endpoints for VMs and BMs or how they handle a single nova installation doing both VMs and BMs besides using baremetal filters for specific host aggregates that use ironic. What is the intersection of filters that you need and which filters are mutually exclusive in your setup?

It probably helps to know that the baremetal filter stuff is deprecated starting in Pike (and removed in Rocky) since we have custom resource classes now and scheduling based on the Placement service.

https://docs.openstack.org/ironic/latest/install/configure-nova-flavors.html

Revision history for this message
Matt Riedemann (mriedem) wrote :
Changed in nova:
status: New → Won't Fix
tags: added: ironic scheduler
Revision history for this message
Matt Riedemann (mriedem) wrote :

Correction in comment #1, I meant "using specific baremetal flavors", not filters.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.