Re: [openstack-dev] [Openstack-operators] [nova][ironic] Concerns over rigid resource class-only ironic scheduling
On Thu, 14 Sep 2017 11:15:26 -0600, Ed Leafe wrote: On Sep 14, 2017, at 10:30 AM, melanie witt wrote: I was thinking, if it's possible to assign more than one resource class to an Ironic node, maybe you could get similar behavior to the old non-exact filters. So if you have an oddball config, you could tag it as multiple resource classes that it's "close enough" to for a match. But I'm not sure whether it's possible for an Ironic node to be tagged with more than one resource class. On the placement side, having an ironic node with two resource classes such as RC1 and RC2, would mean that the ResourceProvider (the ironic node) would have two inventory records: one for RC1, and another for RC2. When a request for a flavor specifying one of these classes is handled, only the one class’s inventory would be consumed. Placement would think that the node still had one of the other resource class available, and would include that if another request for that class is received, which would then fail as the node is already in use. Okay, so it's not possible to have one Ironic node with one inventory record be classified as two different resource classes. Never mind that idea then. Thanks for pointing that out. -melanie __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Openstack-operators] [nova][ironic] Concerns over rigid resource class-only ironic scheduling
On Sep 14, 2017, at 10:30 AM, melanie witt wrote: > > I was thinking, if it's possible to assign more than one resource class to an > Ironic node, maybe you could get similar behavior to the old non-exact > filters. So if you have an oddball config, you could tag it as multiple > resource classes that it's "close enough" to for a match. But I'm not sure > whether it's possible for an Ironic node to be tagged with more than one > resource class. On the placement side, having an ironic node with two resource classes such as RC1 and RC2, would mean that the ResourceProvider (the ironic node) would have two inventory records: one for RC1, and another for RC2. When a request for a flavor specifying one of these classes is handled, only the one class’s inventory would be consumed. Placement would think that the node still had one of the other resource class available, and would include that if another request for that class is received, which would then fail as the node is already in use. -- Ed Leafe __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
