Foreman hierarchy

Support
1

Is it easy and possible to add additional Foreman hierarchy to handle
exception cases? In the doc, it seems there are currently 4 tiers for
Foreman hierarchy, which might not be enough for my case. If not, all
exceptions would have to be handled at the node level, which might not
be ideal in many cases.

2

> Is it easy and possible to add additional Foreman hierarchy to handle
> exception cases? In the doc, it seems there are currently 4 tiers for
> Foreman hierarchy, which might not be enough for my case. If not, all
> exceptions would have to be handled at the node level, which might not
> be ideal in many cases.
>

Which other tiers did you have in mind?

there are currently 5 tiers (including OS which seems to be undocumented).

in the past, we tried define dynamically parameters (with a priority), but
we never got a good structure around how to set it up, so eventually it was
removed from the menus.

The easy solution for now is to apply for a feature request if you want to
have more hierarchal parameters (such as subnet etc).

I'm looking for ideas of how to assoicate parameters for something which is
not a property of a host.

Ohad

··· On Fri, May 13, 2011 at 12:37 PM, hyde wrote:

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

3

Like global default tier, dns domains, data center region, hardware type
tier, data center site, a facts combination of roles (host
group)/environment/data center sites … It would be very nice if foreman
hierarchy could be setup as flexible as extlookup…

··· On Fri, May 13, 2011 at 6:26 AM, Ohad Levy wrote:

On Fri, May 13, 2011 at 12:37 PM, hyde haiwu.us@gmail.com wrote:

Is it easy and possible to add additional Foreman hierarchy to handle
exception cases? In the doc, it seems there are currently 4 tiers for
Foreman hierarchy, which might not be enough for my case. If not, all
exceptions would have to be handled at the node level, which might not
be ideal in many cases.

Which other tiers did you have in mind?

there are currently 5 tiers (including OS which seems to be undocumented).

in the past, we tried define dynamically parameters (with a priority), but
we never got a good structure around how to set it up, so eventually it was
removed from the menus.

The easy solution for now is to apply for a feature request if you want to
have more hierarchal parameters (such as subnet etc).

I’m looking for ideas of how to assoicate parameters for something which is
not a property of a host.

Ohad

–

You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

4

> Like global default tier, dns domains, data center region, hardware type
> tier, data center site, a facts combination of roles (host
> group)/environment/data center sites … It would be very nice if foreman
> hierarchy could be setup as flexible as extlookup…
>
You would be surprised to know that we already have such support[1] in
Foreman… the issue we were facing is that we never found a good way to
represent the data and priority mix.
additionally, it was an issue in terms of ACL… so i think the question
here is more about how to model the solution rather the technical
implementation.

Ohad

[1] - Feature #141: add support to extlookup kind of queries through foreman - Foreman - add support to extlookup kind of
queries through foreman

··· On Fri, May 13, 2011 at 7:17 PM, hai wu wrote:

On Fri, May 13, 2011 at 6:26 AM, Ohad Levy ohadlevy@gmail.com wrote:

On Fri, May 13, 2011 at 12:37 PM, hyde haiwu.us@gmail.com wrote:

Is it easy and possible to add additional Foreman hierarchy to handle
exception cases? In the doc, it seems there are currently 4 tiers for
Foreman hierarchy, which might not be enough for my case. If not, all
exceptions would have to be handled at the node level, which might not
be ideal in many cases.

Which other tiers did you have in mind?

there are currently 5 tiers (including OS which seems to be undocumented).

in the past, we tried define dynamically parameters (with a priority),
but we never got a good structure around how to set it up, so eventually it
was removed from the menus.

The easy solution for now is to apply for a feature request if you want
to have more hierarchal parameters (such as subnet etc).

I’m looking for ideas of how to assoicate parameters for something which
is not a property of a host.

Ohad

–

You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

5

Being very new to foreman (just installed and configured it initially this
week), I am not sure how to use the 5 existing ENC tiers (including OS) in
foreman. And you mentioned below that similar support for multiple tiers is
already built-in in Foreman, does this mean we could put more overriding
tiers than the existing 5? Are there any documentations on this? Multiple
overriding ENC hierarchies is a common requirement for large environment, on
the PDF file page 37, you could see their ENC includes more tiers:

··· On Fri, May 13, 2011 at 12:45 PM, Ohad Levy wrote:

On Fri, May 13, 2011 at 7:17 PM, hai wu haiwu.us@gmail.com wrote:

Like global default tier, dns domains, data center region, hardware type
tier, data center site, a facts combination of roles (host
group)/environment/data center sites … It would be very nice if foreman
hierarchy could be setup as flexible as extlookup…

You would be surprised to know that we already have such support[1] in
Foreman… the issue we were facing is that we never found a good way to
represent the data and priority mix.
additionally, it was an issue in terms of ACL… so i think the question
here is more about how to model the solution rather the technical
implementation.

Ohad

[1] - Feature #141: add support to extlookup kind of queries through foreman - Foreman - add support to extlookup kind of
queries through foreman

On Fri, May 13, 2011 at 6:26 AM, Ohad Levy ohadlevy@gmail.com wrote:

On Fri, May 13, 2011 at 12:37 PM, hyde haiwu.us@gmail.com wrote:

Is it easy and possible to add additional Foreman hierarchy to handle
exception cases? In the doc, it seems there are currently 4 tiers for
Foreman hierarchy, which might not be enough for my case. If not, all
exceptions would have to be handled at the node level, which might not
be ideal in many cases.

Which other tiers did you have in mind?

there are currently 5 tiers (including OS which seems to be
undocumented).

in the past, we tried define dynamically parameters (with a priority),
but we never got a good structure around how to set it up, so eventually it
was removed from the menus.

The easy solution for now is to apply for a feature request if you want
to have more hierarchal parameters (such as subnet etc).

I’m looking for ideas of how to assoicate parameters for something which
is not a property of a host.

Ohad

–

You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.