Hi,
I'm trying to incorporate some modules from foreman-installer into our
set of puppet modules, that would install and configure Foreman with our
services. Basically I want to deploy it with thin instead of passenger,
so I would provide different configuration for apache. But still I want
to reuse the foreman module (if possible using git submodules). So what
I need is to customize the parameters in foreman/manifests/params.pp
(e.g. disable $passenger etc.).
I haven't find a way how to do it without modifying the original foreman
module. Anyone with a solution that would do it? So simply said: I would
like to define my own module, that would alter the params in foreman
module. From what I found so far is not possible with the current state.
But perhaps someone will enlighten me.
Thanks,
– Ivan
Greg,
Parameterizing the modules, would mean that we limit people to Puppet
2.6.5+. Since currently supported OSes ship lower versions of Puppet,
I'm not sure how we want to handle? (We also claim to support really
old versions of Puppet as well.)
Thanks,
Brian
···
On Fri, Jun 8, 2012 at 10:44 AM, Greg Sutcliffe wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08/06/12 15:16, Ivan Nečas wrote:
>> Hi,
>>
>> I'm trying to incorporate some modules from foreman-installer into
>> our set of puppet modules, that would install and configure Foreman
>> with our services. Basically I want to deploy it with thin instead
>> of passenger, so I would provide different configuration for
>> apache. But still I want to reuse the foreman module (if possible
>> using git submodules). So what I need is to customize the
>> parameters in foreman/manifests/params.pp (e.g. disable $passenger
>> etc.).
>>
>> I haven't find a way how to do it without modifying the original
>> foreman module. Anyone with a solution that would do it? So simply
>> said: I would like to define my own module, that would alter the
>> params in foreman module. From what I found so far is not possible
>> with the current state. But perhaps someone will enlighten me.
>
> Parameterizing the foreman and foreman_proxy modules are defintely on
> my todo list, but I've not had time yet. If you wnt to have a go, the
> puppet module is already parameterized, and may serve as a useful
> reference guide. You can compare the 'master' and 'oldstable' branches
> of theforeman/puppet-puppet.git to see what the changes look like.
>
> I also have use cases for customizing the modules (different DHCP
> subnets in foreman-proxy for example) so I hope to get to it in the
> next week or two.
>
> Greg
> - --
> OpenPGP -> KeyID: CA0AEB93
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk/SD9IACgkQ8O7RN8oK65MsQACfXowdFaU/piW1MGg4bi+pVsDd
> +s0An3PRi9YumIX4mptWIOR1PSFifhqn
> =o/2F
> -----END PGP SIGNATURE-----
Parameterizing the foreman and foreman_proxy modules are defintely on
my todo list, but I've not had time yet. If you wnt to have a go, the
puppet module is already parameterized, and may serve as a useful
reference guide. You can compare the 'master' and 'oldstable' branches
of theforeman/puppet-puppet.git to see what the changes look like.
I also have use cases for customizing the modules (different DHCP
subnets in foreman-proxy for example) so I hope to get to it in the
next week or two.
Greg
OpenPGP -> KeyID: CA0AEB93
···
On 08/06/12 15:16, Ivan Nečas wrote:
> Hi,
>
> I'm trying to incorporate some modules from foreman-installer into
> our set of puppet modules, that would install and configure Foreman
> with our services. Basically I want to deploy it with thin instead
> of passenger, so I would provide different configuration for
> apache. But still I want to reuse the foreman module (if possible
> using git submodules). So what I need is to customize the
> parameters in foreman/manifests/params.pp (e.g. disable $passenger
> etc.).
>
> I haven't find a way how to do it without modifying the original
> foreman module. Anyone with a solution that would do it? So simply
> said: I would like to define my own module, that would alter the
> params in foreman module. From what I found so far is not possible
> with the current state. But perhaps someone will enlighten me.
we had this discussion when I parameterized the puppet module - I'm
maintaining an 'oldstable' branch of the foreman installer which is
not parameterized for older puppet clients. The wiki also reflects
that option and states which modules have been converted.
Greg
···
On 08/06/12 17:06, Brian Gupta wrote:
> Greg,
>
> Parameterizing the modules, would mean that we limit people to
> Puppet 2.6.5+. Since currently supported OSes ship lower versions
> of Puppet, I'm not sure how we want to handle? (We also claim to
> support really old versions of Puppet as well.)
>
> Thanks, Brian
> Greg,
>
> Parameterizing the modules, would mean that we limit people to Puppet
> 2.6.5+. Since currently supported OSes ship lower versions of Puppet,
> I'm not sure how we want to handle? (We also claim to support really
> old versions of Puppet as well.)
What about making branch katello-installer-2.0 that would state to be
working only on newer Puppet versions and keep the previous more
compatible version in 1.0 or something like that). The re-usability is
quite important for the installer (we can't assume the users to keep the
defaults) and therefore the parametrized approach is a natural
evolution. Avoiding it just for the compatibility reasons is not worth
– Ivan
···
On 06/08/2012 06:06 PM, Brian Gupta wrote:
from my point of view.
Thanks,
Brian
On Fri, Jun 8, 2012 at 10:44 AM, Greg Sutcliffegsutcliffe@ibahn.com wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/06/12 15:16, Ivan Nečas wrote:
Hi,
I’m trying to incorporate some modules from foreman-installer into
our set of puppet modules, that would install and configure Foreman
with our services. Basically I want to deploy it with thin instead
of passenger, so I would provide different configuration for
apache. But still I want to reuse the foreman module (if possible
using git submodules). So what I need is to customize the
parameters in foreman/manifests/params.pp (e.g. disable $passenger
etc.).
I haven’t find a way how to do it without modifying the original
foreman module. Anyone with a solution that would do it? So simply
said: I would like to define my own module, that would alter the
params in foreman module. From what I found so far is not possible
with the current state. But perhaps someone will enlighten me.
Parameterizing the foreman and foreman_proxy modules are defintely on
my todo list, but I’ve not had time yet. If you wnt to have a go, the
puppet module is already parameterized, and may serve as a useful
reference guide. You can compare the ‘master’ and ‘oldstable’ branches
of theforeman/puppet-puppet.git to see what the changes look like.
I also have use cases for customizing the modules (different DHCP
subnets in foreman-proxy for example) so I hope to get to it in the
next week or two.
Greg
OpenPGP -> KeyID: CA0AEB93
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/SD9IACgkQ8O7RN8oK65MsQACfXowdFaU/piW1MGg4bi+pVsDd
+s0An3PRi9YumIX4mptWIOR1PSFifhqn
=o/2F
-----END PGP SIGNATURE-----
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> Hi,
>>
>> I'm trying to incorporate some modules from foreman-installer into
>> our set of puppet modules, that would install and configure Foreman
>> with our services. Basically I want to deploy it with thin instead
>> of passenger, so I would provide different configuration for
>> apache. But still I want to reuse the foreman module (if possible
>> using git submodules). So what I need is to customize the
>> parameters in foreman/manifests/params.pp (e.g. disable $passenger
>> etc.).
>>
>> I haven't find a way how to do it without modifying the original
>> foreman module. Anyone with a solution that would do it? So simply
>> said: I would like to define my own module, that would alter the
>> params in foreman module. From what I found so far is not possible
>> with the current state. But perhaps someone will enlighten me.
> Parameterizing the foreman and foreman_proxy modules are defintely on
> my todo list, but I've not had time yet. If you wnt to have a go, the
> puppet module is already parameterized, and may serve as a useful
> reference guide. You can compare the 'master' and 'oldstable' branches
> of theforeman/puppet-puppet.git to see what the changes look like.
Thank you! That was what I was searching for. Perhaps I will send some
pull requests for that (since need it for my current project anyway).
– Ivan
···
On 06/08/2012 04:44 PM, Greg Sutcliffe wrote:
> On 08/06/12 15:16, Ivan Nečas wrote:
I also have use cases for customizing the modules (different DHCP
subnets in foreman-proxy for example) so I hope to get to it in the
next week or two.
Greg
OpenPGP -> KeyID: CA0AEB93
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/SD9IACgkQ8O7RN8oK65MsQACfXowdFaU/piW1MGg4bi+pVsDd
+s0An3PRi9YumIX4mptWIOR1PSFifhqn
=o/2F
-----END PGP SIGNATURE-----
Glad to help. Patches would be awesome - as I say, I will do it
eventually, but I need to focus on cleaning up our Debian packages
first 
Greg
···
On 11/06/12 13:28, Ivan Nečas wrote:
> Thank you! That was what I was searching for. Perhaps I will send
> some pull requests for that (since need it for my current project
> anyway).
