how to prove installation?

asked 2013-07-10 15:04:45 -0500

gpinkham
21 ●4

where I work I need to provide "installation qualification" for the applications. this is my first go round with this but I was told it typically includes lots of screen shots as evidence.. for instance they take screen shots of sql manager showing that tables were indeed created etc.. is this something that can be accomplished with puppet? install, configure and provide evidence. I was told "saying the script ran is not enough"..

thanks!

edit retag flag offensive close merge delete

Comments

One could always provide secondary proof, by using something like ScriptRock or serverspec to validate your builds.

ken ( 2013-07-11 08:13:59 -0500 )edit

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2013-07-11 07:51:03 -0500

banjer
264 ●7 ●13 ●22

updated 2013-07-11 07:54:40 -0500

Puppet reports will provide you with a detailed report of every puppet run that is performed on every agent, and what was changed/installed (if any changes were actually made).

That's as good, if not better than screenshots of manually completing a task in a GUI. If you can trust a GUI displaying that some task was completed, then you can trust a detailed log or report of what was changed.

I also like Foreman for an ENC because of its built-in auditing.

edit flag offensive delete link

add a comment

answered 2013-07-11 08:15:22 -0500

gpinkham
21 ●4

ok thanks.. so just to be clear.. if the execution involves say a database migration script that outputs "table xyz created" etc puppet will log that info as well as the rest of the info from the run (like "user abc created", "user assigned role def" etc???

I have limited time between now and go live with this app (< 2 months).. so I need to finish coding it and create my test and prod servers.. and create reams of QMS documents.. I know learning to use puppet is a good thing in general.. just trying to make sure I have ... (more)

edit flag offensive delete link

Comments

Yes, if you use the "logoutput => true" attribute on your exec resources, all output from the executed command will be reported and can be saved to a file, passed to ...(more)