Feature #8523
opendefault BMC interface username/password for hostgroup
Description
It gets pretty tedious rekeying the BMC credentials over and over again when they are very often identical for a group of hosts. It would very convient if it was possible to set a default globally and/or on a hostgroups as is currently possible for the root password.
Updated by Dominic Cleal about 10 years ago
- Project changed from Smart Proxy to Foreman
- Category set to BMC
Updated by Alex Balk over 9 years ago
Would really like to see this happen, specifically per hardware-type. In our case, that's what differentiates user/pass combos.
Adding a user/pass manually is simply not possible at scale. A parameter would be a brilliant solution!
Updated by Stefan Lasiewski about 8 years ago
This still isn't available with Foreman 1.11.
BMC & IPMI are generally used in larger environments, and adding the BMC password to every node is quite tedious and error prone. It would be great to have a way to automate this.
Updated by Marek Hulán about 8 years ago
With hostgroup it's quite tricky, the thing is that hostgroup does not have interfaces since it does not make sense to share info like IP, MAC for more hosts. Maybe we could achieve that through global settings so if there's no password set it would inherit it from settings. Or if you need to have different password per hostgroup, then maybe smart variable or hostgroup parameter?
Updated by Aaron Krzywicki about 8 years ago
Marek Hulán wrote:
With hostgroup it's quite tricky, the thing is that hostgroup does not have interfaces since it does not make sense to share info like IP, MAC for more hosts. Maybe we could achieve that through global settings so if there's no password set it would inherit it from settings. Or if you need to have different password per hostgroup, then maybe smart variable or hostgroup parameter?
Would locations be easier to implement? Assigning default credentials per site would be useful for our use case.
Updated by Marek Hulán about 8 years ago
smart variable and/or parameter would work even with locations, probably the best option then