Managing defined types from Foreman UI

Support
1

Hi,

Just curious: is there any plans to implement support for managing Puppet
defined types in Foreman UI?
I've already seen some approaches like module "foreman_resources" [1] and
plugin "foreman_resources" [2] but they were unsuitable for everyday needs.
Thanks!

[1] https://github.com/soumentrivedi/foreman_resources
[2] https://github.com/arnoudj/foreman_resources

··· -- Kind regards, Vladimir.
2

> Hi,
>
> Just curious: is there any plans to implement support for managing Puppet
> defined types in Foreman UI?
> I've already seen some approaches like module "foreman_resources" [1] and
> plugin "foreman_resources" [2] but they were unsuitable for everyday needs.
> Thanks!
>
> [1] https://github.com/soumentrivedi/foreman_resources
> [2] https://github.com/arnoudj/foreman_resources

Oh interesting, I hadn't seen those before. But you're basically limited
to writing some kinds of wrapper classes:
Instantiate Puppet resources - Foreman

The Smart Parameters allow merging of hashes now so you can add
resources to different layers - host group, host, etc, and have them
merged together at the end, so you might not need the plugin part.

https://github.com/stbenjam/puppet-hash_resources works without the
future parser enabled, if that was a problem.

··· On Tue, Sep 08, 2015 at 02:22:29PM +0300, Vladimir Stackov wrote:

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

3

Future parser is not a problem, the problem is that I can't maintain
hierarchy for multiple systems.

Say I need to add user to every system, then I'll use foreman_resources or
your hash_resources and use "user" defined type.
But when I need to exclude this user from single system I should use smart
selectors or maintain complete resource hierarchy for that system
separately.

What I want is to have some hierarchy-"merging" capabilities for defined
types and I can't achieve that with parametrized puppet modules.
Can you advice something? Thanks!

··· 2015-09-08 15:11 GMT+03:00 Stephen Benjamin :

On Tue, Sep 08, 2015 at 02:22:29PM +0300, Vladimir Stackov wrote:

Hi,

Just curious: is there any plans to implement support for managing Puppet
defined types in Foreman UI?
I’ve already seen some approaches like module “foreman_resources” [1] and
plugin “foreman_resources” [2] but they were unsuitable for everyday
needs.
Thanks!

[1] https://github.com/soumentrivedi/foreman_resources
[2] https://github.com/arnoudj/foreman_resources

Oh interesting, I hadn’t seen those before. But you’re basically limited
to writing some kinds of wrapper classes:

Instantiate Puppet resources - Foreman

The Smart Parameters allow merging of hashes now so you can add
resources to different layers - host group, host, etc, and have them
merged together at the end, so you might not need the plugin part.

https://github.com/stbenjam/puppet-hash_resources works without the
future parser enabled, if that was a problem.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Kind regards,
Vladimir.

4

> Future parser is not a problem, the problem is that I can't maintain
> hierarchy for multiple systems.
>
> Say I need to add user to every system, then I'll use foreman_resources or
> your hash_resources and use "user" defined type.
> But when I need to exclude this user from single system I should use smart
> selectors or maintain complete resource hierarchy for that system
> separately.
>
> What I want is to have some hierarchy-"merging" capabilities for defined
> types and I can't achieve that with parametrized puppet modules.
> Can you advice something? Thanks!

That's what I mentioned is the deep merging of smart class parameters.
I don't know if it will fulfill your needs, but its a relatively recent
feature (Feature #3309: Support deep merging of hash structures in smart class parameters - Foreman).

··· On Tue, Sep 08, 2015 at 03:49:22PM +0300, Vladimir Stackov wrote:

2015-09-08 15:11 GMT+03:00 Stephen Benjamin stephen@redhat.com:

On Tue, Sep 08, 2015 at 02:22:29PM +0300, Vladimir Stackov wrote:

Hi,

Just curious: is there any plans to implement support for managing Puppet
defined types in Foreman UI?
I’ve already seen some approaches like module “foreman_resources” [1] and
plugin “foreman_resources” [2] but they were unsuitable for everyday
needs.
Thanks!

[1] https://github.com/soumentrivedi/foreman_resources
[2] https://github.com/arnoudj/foreman_resources

Oh interesting, I hadn’t seen those before. But you’re basically limited
to writing some kinds of wrapper classes:

Instantiate Puppet resources - Foreman

The Smart Parameters allow merging of hashes now so you can add
resources to different layers - host group, host, etc, and have them
merged together at the end, so you might not need the plugin part.

https://github.com/stbenjam/puppet-hash_resources works without the
future parser enabled, if that was a problem.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

5

Ah, I misunderstood you, sorry.
This feature is exactly what I want!
Can you point me to document on how to use this feature? YAML values is
always getting to be simply overriden.

··· 2015-09-08 16:06 GMT+03:00 Stephen Benjamin :

On Tue, Sep 08, 2015 at 03:49:22PM +0300, Vladimir Stackov wrote:

Future parser is not a problem, the problem is that I can’t maintain
hierarchy for multiple systems.

Say I need to add user to every system, then I’ll use foreman_resources
or
your hash_resources and use “user” defined type.
But when I need to exclude this user from single system I should use
smart
selectors or maintain complete resource hierarchy for that system
separately.

What I want is to have some hierarchy-“merging” capabilities for defined
types and I can’t achieve that with parametrized puppet modules.
Can you advice something? Thanks!

That’s what I mentioned is the deep merging of smart class parameters.
I don’t know if it will fulfill your needs, but its a relatively recent
feature (Feature #3309: Support deep merging of hash structures in smart class parameters - Foreman).

2015-09-08 15:11 GMT+03:00 Stephen Benjamin stephen@redhat.com:

On Tue, Sep 08, 2015 at 02:22:29PM +0300, Vladimir Stackov wrote:

Hi,

Just curious: is there any plans to implement support for managing
Puppet

defined types in Foreman UI?
I’ve already seen some approaches like module “foreman_resources”
[1] and

plugin “foreman_resources” [2] but they were unsuitable for everyday
needs.
Thanks!

[1] https://github.com/soumentrivedi/foreman_resources
[2] https://github.com/arnoudj/foreman_resources

Oh interesting, I hadn’t seen those before. But you’re basically
limited

to writing some kinds of wrapper classes:

Instantiate Puppet resources - Foreman

The Smart Parameters allow merging of hashes now so you can add
resources to different layers - host group, host, etc, and have them
merged together at the end, so you might not need the plugin part.

https://github.com/stbenjam/puppet-hash_resources works without the
future parser enabled, if that was a problem.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send

an email to foreman-users+unsubscribe@googlegroups.com.

To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google
Groups

“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an

email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Kind regards,
Vladimir.

6

> Ah, I misunderstood you, sorry.
> This feature is exactly what I want!
> Can you point me to document on how to use this feature? YAML values is
> always getting to be simply overriden.

··· On Tue, Sep 08, 2015 at 04:18:51PM +0300, Vladimir Stackov wrote:

2015-09-08 16:06 GMT+03:00 Stephen Benjamin stephen@redhat.com:

On Tue, Sep 08, 2015 at 03:49:22PM +0300, Vladimir Stackov wrote:

Future parser is not a problem, the problem is that I can’t maintain
hierarchy for multiple systems.

Say I need to add user to every system, then I’ll use foreman_resources
or
your hash_resources and use “user” defined type.
But when I need to exclude this user from single system I should use
smart
selectors or maintain complete resource hierarchy for that system
separately.

What I want is to have some hierarchy-“merging” capabilities for defined
types and I can’t achieve that with parametrized puppet modules.
Can you advice something? Thanks!

That’s what I mentioned is the deep merging of smart class parameters.
I don’t know if it will fulfill your needs, but its a relatively recent
feature (Feature #3309: Support deep merging of hash structures in smart class parameters - Foreman).

2015-09-08 15:11 GMT+03:00 Stephen Benjamin stephen@redhat.com:

On Tue, Sep 08, 2015 at 02:22:29PM +0300, Vladimir Stackov wrote:

Hi,

Just curious: is there any plans to implement support for managing
Puppet

defined types in Foreman UI?
I’ve already seen some approaches like module “foreman_resources”
[1] and

plugin “foreman_resources” [2] but they were unsuitable for everyday
needs.
Thanks!

[1] https://github.com/soumentrivedi/foreman_resources
[2] https://github.com/arnoudj/foreman_resources

Oh interesting, I hadn’t seen those before. But you’re basically
limited

to writing some kinds of wrapper classes:

Instantiate Puppet resources - Foreman

The Smart Parameters allow merging of hashes now so you can add
resources to different layers - host group, host, etc, and have them
merged together at the end, so you might not need the plugin part.

https://github.com/stbenjam/puppet-hash_resources works without the
future parser enabled, if that was a problem.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send

an email to foreman-users+unsubscribe@googlegroups.com.

To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google
Groups

“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an

email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Kind regards,
Vladimir.

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Best Regards,

Stephen Benjamin
Red Hat Engineering

7

Also our manual mentions it under "Merging overrides":
http://theforeman.org/manuals/1.9/index.html#4.2.6SmartMatchers

··· On 08/09/15 15:04, Stephen Benjamin wrote: > On Tue, Sep 08, 2015 at 04:18:51PM +0300, Vladimir Stackov wrote: >> > Ah, I misunderstood you, sorry. >> > This feature is exactly what I want! >> > Can you point me to document on how to use this feature? YAML values is >> > always getting to be simply overriden. > https://www.youtube.com/watch?v=Z75Z670WqZs

–
Dominic Cleal
dominic@cleal.org

8

Shame on me.

Thank you, Dominic!

··· 2015-09-08 17:05 GMT+03:00 Dominic Cleal :

On 08/09/15 15:04, Stephen Benjamin wrote:

On Tue, Sep 08, 2015 at 04:18:51PM +0300, Vladimir Stackov wrote:

Ah, I misunderstood you, sorry.
This feature is exactly what I want!
Can you point me to document on how to use this feature? YAML values
is

always getting to be simply overriden.
https://www.youtube.com/watch?v=Z75Z670WqZs

Also our manual mentions it under “Merging overrides”:
Foreman :: Manual

–
Dominic Cleal
dominic@cleal.org

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Kind regards,
Vladimir.