On 2014-07-14 20:41, Andrii Kalytiuk wrote:
> Hi,
>
> I look into ways to use MCollective to *run test automation* on lab
> machines.
>
> After couple of days of research I still have a question /is MCollective
> is right tool/ to perform all required routines.
>
> *So my question is:*
> /Will it be proper/ to use MCollective for following operations on
> Windows nodes - using own custom agents:
>
> 1. Wait for server node (virtual machine) to become responsive after revert
> 2. Copy file with (test automation data) from network location
> 3. Unzip test automation files
> 4. Update content of config files on machine
> 5. Run command line utility to execute test automation.
> * Takes from couple of minutes to hour or more
> * Console output to be returned to MCollective client
> * Output returns to client gradually (more or less shortly after
> it is produced on server)
> * /Is it possible to send responses to prompts of interactive
> command line application?/
> 6. Archive certain files on server
> 7. Copy zip file with output files to network location
>
> As I get from documentations all points except 5th can be implemented as
> a single or several command line calls.
>
> *So main questions are:*
> Is it possible to use MCollective to execute long-running command line
> utility on server and gradually return to client output of the utility
> as it is produced?
> Is it possible to implement interaction with a command line application
> which prompts for additional user inputs on server (e. g. non-silent
> installation)?
Use a product that is appropriate for such tasks instead of trying to
retrofit something that wasn't built for it.
Jenkins comes to mind, as a great tool to run CI, CD and automated
tests. See
http://jenkins-ci.org/
Regards, David