Migrating to enc and parametrized classes

Hi,
I've been running puppet now for a few weeks now using a nodes.pp
file and plan to migrate to foreman backed with an enc shortly.

After following the documentation and testing generally everything
looks like it is going to work but I have a couple of questions:

After running the
rake puppet:import:puppet_classes RAILS_ENV=production

most of the classes (see below) and environments are imported into the enc.

I'm currently running with out the external_node option in puppet.conf
while I set up still relying on the nodes.pp file for now.

The nodes appear in foreman as they connect but not the
node class relationship.
To check there is no way to automate this? I just do it via the web
interface? This is fine, I don't have many hosts yet.

Second question my nodes.pp currently contains some parametrized classes,

e.g.
class { ocsagent: ocsserver => $::ocsserver }

everything I have this way was not imported at all into the enc.

My suspicion is I should move this out to separate module and
get the value from a global setting, this way it should pass the import?

Essentially the foreman schema supports attributes in a global, host
or hostgroup, not a per class setting on a particular host. Am I correct?

Steve.

··· -- Steve Traylen

> Hi,
> I've been running puppet now for a few weeks now using a nodes.pp
> file and plan to migrate to foreman backed with an enc shortly.
>
> After following the documentation and testing generally everything
> looks like it is going to work but I have a couple of questions:
>
> After running the
> rake puppet:import:puppet_classes RAILS_ENV=production
>
> most of the classes (see below) and environments are imported into the enc.
>
> I'm currently running with out the external_node option in puppet.conf
> while I set up still relying on the nodes.pp file for now.
>
> The nodes appear in foreman as they connect but not the
> node class relationship.
> To check there is no way to automate this? I just do it via the web
> interface? This is fine, I don't have many hosts yet.
>
Yes, sadly no importer exists at the moment.

> Second question my nodes.pp currently contains some parametrized classes,
>
> e.g.
> class { ocsagent: ocsserver => $::ocsserver }
>
> everything I have this way was not imported at all into the enc.
>
> My suspicion is I should move this out to separate module and
> get the value from a global setting, this way it should pass the import?
>
> Essentially the foreman schema supports attributes in a global, host
> or hostgroup, not a per class setting on a particular host. Am I correct?
>
We also support a more complex data structure (and ordering) see
http://theforeman.org/wiki/foreman/Smart_Variables

Ohad

··· On Mon, Oct 17, 2011 at 9:35 PM, Steve Traylen wrote: > Steve. > > > -- > Steve Traylen > > -- > 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. > >