Best practices (is there any?)

Good day.

Thank you for great product. I've been using it for 3 month now… But I
still have some questions. Is there any 'best practice' guide that
describes how to utilize forge modules?
For now I've selected path of creating wrapper classes that uses these
modules. In case if I use raw modules such as apache it's very hard to
configure host for desired task. Configuration becomes too distributed
across multiple parameters.
Or maybe It's better to create foreman orientated modules from scratch?
What are your suggestions?

Thanks,
Mikhail.

I don't think there is a best practice with forge modules yet, but from
what I've seen of Puppet 4.0 (or whatever they will call it) it appears
that the Enterprise version is moving MUCH closer to the style of
management we get from theforeman. I agree, right now, not many forge
modules have full configuration from smart parameters/values and i would
love to see more community discussion about what this means for the future.
Some extend the module with a wrapper to include values, others edit them
and some people may just fork them locally and hack them up.

··· On Friday, October 17, 2014 1:03:29 AM UTC-5, Mikhail Shevtsov wrote: > > Good day. > > Thank you for great product. I've been using it for 3 month now.. But I > still have some questions. Is there any 'best practice' guide that > describes how to utilize forge modules? > For now I've selected path of creating wrapper classes that uses these > modules. In case if I use raw modules such as apache it's very hard to > configure host for desired task. Configuration becomes too distributed > across multiple parameters. > Or maybe It's better to create foreman orientated modules from scratch? > What are your suggestions? > > Thanks, > Mikhail. >

Just curious, what is needed other than configuring parameters to set up a
host? Are there just too many that it gets tedious to configure - in that
case what's the proposed solution? Would a plugin serving preconfigured
hostgroups for some modules help?

··· On Fri, Oct 17, 2014 at 3:42 PM, Byron Miller wrote:

I don’t think there is a best practice with forge modules yet, but from
what I’ve seen of Puppet 4.0 (or whatever they will call it) it appears
that the Enterprise version is moving MUCH closer to the style of
management we get from theforeman. I agree, right now, not many forge
modules have full configuration from smart parameters/values and i would
love to see more community discussion about what this means for the
future. Some extend the module with a wrapper to include values, others
edit them and some people may just fork them locally and hack them up.

On Friday, October 17, 2014 1:03:29 AM UTC-5, Mikhail Shevtsov wrote:

Good day.

Thank you for great product. I’ve been using it for 3 month now… But I
still have some questions. Is there any ‘best practice’ guide that
describes how to utilize forge modules?
For now I’ve selected path of creating wrapper classes that uses these
modules. In case if I use raw modules such as apache it’s very hard to
configure host for desired task. Configuration becomes too distributed
across multiple parameters.
Or maybe It’s better to create foreman orientated modules from scratch?
What are your suggestions?

Thanks,
Mikhail.


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.


Daniel Lobato

@elobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30