Hi,

After reading the thread, to me it sounds like a problem foreman can solve.

Cheers,
Ohad

On 2/2/10, John Lyman <[email protected]> wrote:
> I'm trying to figure out the best way to achieve the following...
>
> Inside of each node definition, I have variables for ip address,
> default router, dns server, etc.  I have a jumpstart module that has
> several different file resources that use templates.  In each
> template, I would like to be able to use the values of the variables
> in all nodes.
>
> For example:
> node foo { ipaddress => 1.2.3.4 }
> node bar { ipaddress => 5.6.7.8 }
>
> class jumpstart {
>   jumpstart_client = [ "foo", "bar" ]
>   file { "sysidcfg":
>     content => template("sysidcfg.erb")
>   }
> }
>
> sysidcfg.erb:
> <% jumpstart_client.each do |client| -%>
> hostname=<%= client %> ip_address=<%= client::ipaddress %>
> <% end -%>
>
> I don't think the above is possible.  What is the best way to
> accomplish this (if any)?  I think this is where exported resources
> would come in to play, but in this case they will not work because I
> want the info on the jumpstart server before puppet is even installed/
> run on the node.  In other words, I want to define the node in puppet,
> do a catalog run on the jumpstart server to update it's config files
> based on the new node definition, and then jumpstart the node (which
> also installs puppet).
>
> Any ideas?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to