Can Foreman User data be available to Puppet Modules?

Support
1

Greetings,

I am curious if Foreman's Authentication data can be made available to
systems through puppet modules.

Consider this concept -

  1. Foreman User logs into foreman and builds a new node.
  2. The node is monitored by Nagios automatically.
  3. The nagios module either adds a new contact for the Foreman user or
    associates the contact which already exists for the Foreman User as the
    notification contact for the new node.
  4. The Foreman User's user information and sudoers access is added to
    the node.

I could think of more, but I think that's enough to get the idea across. I
have a hard time believing I'm the first to think of this since I'm a
novice with puppet, foreman and nagios, but I have yet to develop a search
query that produces any discussion on a topic like this.
Thanks for your thoughts!

··· -- Sean M. Alderman Senior Engineer, UDit Systems Integration and Engineering University of Dayton
2

You can access to owner name and email in your puppet manifest as it's
exposed by Foreman's ENC script :
you can use $::owner_name and $::owner_email.
We use it in dev environment to route root's mail to owner's personal mail.

Hope it will help.

Regards,

Romain Vrignaud

··· 2013/7/18 Sean Alderman

Greetings,

I am curious if Foreman’s Authentication data can be made available to
systems through puppet modules.

Consider this concept -

  1. Foreman User logs into foreman and builds a new node.
  2. The node is monitored by Nagios automatically.
  3. The nagios module either adds a new contact for the Foreman user or
    associates the contact which already exists for the Foreman User as the
    notification contact for the new node.
  4. The Foreman User’s user information and sudoers access is added to
    the node.

I could think of more, but I think that’s enough to get the idea across.
I have a hard time believing I’m the first to think of this since I’m a
novice with puppet, foreman and nagios, but I have yet to develop a search
query that produces any discussion on a topic like this.
Thanks for your thoughts!

Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton

–
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/groups/opt_out.

3

Romain,
Excellent, I will give this a shot! Thank you!

··· -- Sean M. Alderman Senior Engineer, UDit Systems Integration and Engineering University of Dayton

On Fri, Jul 19, 2013 at 9:34 AM, Romain Vrignaud rvrignaud@gmail.comwrote:

You can access to owner name and email in your puppet manifest as it’s
exposed by Foreman’s ENC script :
you can use $::owner_name and $::owner_email.
We use it in dev environment to route root’s mail to owner’s personal mail.

Hope it will help.

Regards,

Romain Vrignaud

2013/7/18 Sean Alderman salderman1@udayton.edu

Greetings,

I am curious if Foreman’s Authentication data can be made available to
systems through puppet modules.

Consider this concept -

  1. Foreman User logs into foreman and builds a new node.
  2. The node is monitored by Nagios automatically.
  3. The nagios module either adds a new contact for the Foreman user
    or associates the contact which already exists for the Foreman User as the
    notification contact for the new node.
  4. The Foreman User’s user information and sudoers access is added to
    the node.

I could think of more, but I think that’s enough to get the idea across.
I have a hard time believing I’m the first to think of this since I’m a
novice with puppet, foreman and nagios, but I have yet to develop a search
query that produces any discussion on a topic like this.
Thanks for your thoughts!

Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton

–
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/groups/opt_out.

–
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/groups/opt_out.