I just tried to create a host with no puppetmaster (leaving the combo
box empty), and adding some conditional stuff to my provisioning
template so I could use foreman to deploy standalone servers as well
as puppet-managed ones. It turns out that foreman filled in a
puppetmaster for me anyway though, and I can't remove it in the edit
screen. The same seems to be true for Host Groups too.
Is there a way to have some hosts without a puppetmaster? Having spent
a while on the deployment scripts, it'd be nice to be able to leverage
them for consistently building non-managed hosts, too…
Thanks for any pointers,
Howie
> I just tried to create a host with no puppetmaster (leaving the combo
> box empty), and adding some conditional stuff to my provisioning
> template so I could use foreman to deploy standalone servers as well
> as puppet-managed ones. It turns out that foreman filled in a
> puppetmaster for me anyway though, and I can't remove it in the edit
> screen. The same seems to be true for Host Groups too.
>
> Is there a way to have some hosts without a puppetmaster? Having spent
> a while on the deployment scripts, it'd be nice to be able to leverage
> them for consistently building non-managed hosts, too…
>
> Thanks for any pointers,
>
Two comments:
- why do you care if the field is used? is that how you detect that
its not managed?
- you could use hostgroup based provisioning [1], this works more or
less the same (can even generate pxe menus) but does not create
dns/dhcp reservations.
Ohad
[1] - TemplateWriting - Foreman
···
On Wed, Sep 7, 2011 at 3:32 PM, Howard Jones wrote:
> Howie
>
> --
> 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.
>
>
> Two comments:
>
> 1. why do you care if the field is used? is that how you detect that
> its not managed?
Fair point 
I managed to bake one of my assumptions in there. I was
planning on using <% if @puppetmaster != "" -%> in my provisioning
template to skip the puppet-centric parts (extra repos, puppet
itself). It also makes it more obvious in the host list that it's not
really part of the puppet ecosystem.
> 2. you could use hostgroup based provisioning [1], this works more or
> less the same (can even generate pxe menus) but does not create
> dns/dhcp reservations.
I'll check that out instead. Thanks!
Howie
···
On 7 September 2011 13:48, Ohad Levy wrote:
>> Two comments:
>>
>> 1. why do you care if the field is used? is that how you detect that
>> its not managed?
>
> Fair point I managed to bake one of my assumptions in there. I was
> planning on using <% if @puppetmaster != "" -%> in my provisioning
> template to skip the puppet-centric parts (extra repos, puppet
> itself). It also makes it more obvious in the host list that it's not
> really part of the puppet ecosystem.
I guess we could try improving here, please feel in a feature
request… alternatively, you could use the parameters to pass what
ever attributes you like, and then access them via
@host.params["param_name"]
Ohad
···
On Wed, Sep 7, 2011 at 3:56 PM, Howard Jones wrote:
> On 7 September 2011 13:48, Ohad Levy wrote:
>
>> 2. you could use hostgroup based provisioning [1], this works more or
>> less the same (can even generate pxe menus) but does not create
>> dns/dhcp reservations.
>
> I'll check that out instead. Thanks!
>
> Howie
>
> --
> 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.
>
>
