What Yuiko has described makes a lot of sense, and from that perspective perhaps instead of us defining what driver a node should and shouldn't be using a config file, we should just provide a guide to using the inspector rules for this and maybe some prewritten rules that can set the driver and driver info etc fields for different cases?
Then the work flow would be, default to Fake driver because we don't need any special info for that, however if a rule detects that its IPMIable by making sure that the IPMI address is valid or something, then it can set the driver to an ipmitool one and then set the password and username based on either a retrieved field or values defined in the rule itself. WDYT? Sam
__________________________________________________________________________ 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
