Puppet users - Jul 2013 - Automating Change Ticket Creation following module deployment

Hi Everyone;

This is a way-out there question but, I wanted to see if anyone has any
advise to offer.


We have an API to our Change Management System.  Presently, I have a perl
script that creates a record in the change mgmt system but, the script is
somewhat manual (ie the use has to execute the script, passing information
in variables).

I am trying to come up with ways to automate the creation of a change
ticket following a puppet module being applied.

I know this is a very creative group of users and I was wondering if anyone
might be able/willing to toss some ideas my way?

Thank you
Bee

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Check out puppets reporting options. 

http://docs.puppetlabs.com/guides/reporting.html

You will probably need to rewrite your Perl script as a reporting module for the
best results.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

On Wednesday, July 10, 2013 4:53:25 PM UTC-5, Worker Bee
wrote:
>
> Hi Everyone;
>
> This is a way-out there question but, I wanted to see if anyone has any 
> advise to offer.
>
>
> We have an API to our Change Management System.  Presently, I have a perl 
> script that creates a record in the change mgmt system but, the script is 
> somewhat manual (ie the use has to execute the script, passing information 
> in variables).
>
> I am trying to come up with ways to automate the creation of a change 
> ticket following a puppet module being applied.
>
> I know this is a very creative group of users and I was wondering if 
> anyone might be able/willing to toss some ideas my way?
>

Possible alternatives include:

   - modifying each module to apply a refresh-only Exec that runs your 
   script if one of the module''s managed resources signals it.
   - enabling reporting, and parsing the run reports to submit entries to 
   CMS
   - monitoring the log entries emitted by the agent, and using those to 
   submit CMS entries
   - hacking the agent to hook in CMS notifications

There may be other alternatives.  Myself, I would probably go for the 
reporting or log-monitoring option.


John


If you want to avoid writing this into your modules, then you could hack 
the agent to hook your notifications in.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.