>> Hello Ohad,
>> thanks for your answer, my problem is that a node has many roles - one
>> is rhel5base, the other is sapprod and so on.
>> I'm not sure I fully understand, but imho something like rhel5base should
> be auto included based on your OS facts rather then except foreman to do it
> for you.
> for example, lets say you have a hostgroup called base
> that base class could auto include other classes based on the machine
> the only limitation we had - which was about one group cant inherit from
> another group, is already resolved in the latest development version.
> if you like to assign multiple roles into a host, and each roles
> has parameters, which parameter wins?
I might jump in here, as it's something I used to do with Dashboard. Ideally
you should not have parameter conflicts - roles with similar attributes
should be subgroups, which we can already do in Foreman. However, I find
myself wanting to do something like:
So I have classes which are appropriate to a specific version of our
software, and classes appropriate to a given region. Trying to do that with
auto-includes is very messy. Subgroups work, but you end up with:
which means I duplicate a lot of information, and might make a mistake when
updating large numbers of groups.
I think multiple groups isn't necessarily wrong (as you say, it's use case
dependant). I can think of a couple of ways to solve the parameters problem.
The easiest way (although possibly confusing to the new user) is to do by
the order of the groups. So if I assign a group to Build18+Europe, then
Build18 wins, as it's earlier. Other options include adding a priority
weight to the parameters, or even showing conflicts on a host page and
allowing the user to specify.
I´m now running dashboard 1.1.1 and it seems to support this kind of
> Its good that everyone can chose whats best for them
Indeed. This is only piece of functionality I miss from Dashboard -
Foreman is way superior in all other respects
On 10 August 2011 20:47, Ohad Levy wrote:
> On Wed, Aug 10, 2011 at 5:55 PM, Stefan Wiederoder < > firstname.lastname@example.org> wrote: