[RFE] Allow using values from introspection for rule conditions

Bug #1579727 reported by Carmelo Ragusa on 2016-05-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic Inspector
In Progress
Wishlist
Zhenguo Niu

Bug Description

Currently it is possible to fetch values from the introspection data and assign it to a rule action, but it is not possible to fetch a value from introspection and use it as a rule condition.

For example as a condition:
If the bmc in the introspection data is equal to the ipmi address in the driver info of the node (for the condition), then set the ipmi username and password (as credentials).

Or:
Assign a different kernel and ramdisk based on the amount of RAM

Tags: rfe Edit Tag help
Dmitry Tantsur (divius) on 2016-05-09
summary: - Using values from introspection for rule conditions
+ [RFE] Allow using values from introspection for rule conditions
tags: added: rfe
Changed in ironic-inspector:
status: New → Triaged
importance: Undecided → Wishlist
Changed in ironic-inspector:
assignee: nobody → Zhenguo Niu (niu-zglinux)

Fix proposed to branch: master
Review: https://review.openstack.org/345535

Changed in ironic-inspector:
status: Triaged → In Progress
Chris Krelle (nobodycam) wrote :

I am not sure this is A true issue. I used Collected data in rule conditions since Mitaka version of inspector. I have used it to do what describe. I assign ipmi credentials based on manufacturer.
As an example:
{"op": "contains", "field": "data://inventory.system_vendor.manufacturer", "value": "Dell"}
or
{"op": "contains", "field": "data://inventory.system_vendor.manufacturer", "value": "HP"}

it is worth noting that I carry a patch internally to collect system_vendor information, but no code change to anything around the conditional usage support.

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

Other bug subscribers