<div dir="ltr"><div>So Ansible is supposed to be already installed and available on the machine / (docker container) running Hawkular Services, right ?</div><div><br></div><div>Thomas</div><div> </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 15, 2016 at 3:57 AM, John Mazzitelli <span dir="ltr"><<a href="mailto:mazz@redhat.com" target="_blank">mazz@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Slight change - I found out there is a feature in feature-pack stuff that let you ship with direct file content that gets copied into the server. So I put the Ansible scripts in the feature pack. This is the correct way to do it. Now anyone building the server with the feature pack (integration tests, for example) will get the Ansible integration as well.<br>
<br>
So link [3] changes from my original email. It is now:<br>
<br>
[3] <a href="https://github.com/jmazzitelli/hawkular-services/tree/HAWKULAR-1096-ansible-commands/feature-pack/src/main/content/standalone/configuration/ansible" rel="noreferrer" target="_blank">https://github.com/jmazzitelli/hawkular-services/tree/HAWKULAR-1096-ansible-commands/feature-pack/src/main/content/standalone/configuration/ansible</a><br>
<div class="HOEnZb"><div class="h5"><br>
----- Original Message -----<br>
> I have a very simple PoC working that shows Ansible integrated with Hawkular<br>
> such that it can start a WildFly server remotely.<br>
><br>
> I'll begin with a brief summary.<br>
><br>
> SUMMARY<br>
><br>
> A client connects to the Hawkular Server via its websocket and passes in a<br>
> JSON request (like it does the other kinds of requests). The JSON request<br>
> looks something like:<br>
><br>
> AnsibleRequest={"playbook":"start-wildfly.yml", "extraVars": {<br>
> "wildfly_home_dir":"/opt/wildfly10" } }<br>
><br>
> The command-gateway server takes the request, runs the Ansible playbook, and<br>
> returns the response back over the websocket to the client with an<br>
> AnsibleResponse (which includes the Ansible output to show what it did).<br>
><br>
> DETAILS<br>
><br>
> The code is in two branches in my repos. See [1] and [2]. You need both for<br>
> this to work.<br>
><br>
> Hawkular-Services packages up Ansible playbooks and its associated files in<br>
> standalone/configuration/ansible. See [3].<br>
><br>
> Hawkular-Commons adds to command gateway a new JSON request/response for<br>
> Ansible requests. See [4] and [5].<br>
><br>
> The Ansible command is invoked in the server when the AnsibleRequest JSON is<br>
> received over the websocket. This command implementation runs the Ansible<br>
> playbook and returns the results back in a AnsibleResponse. See [6].<br>
><br>
> If you build commons and then services to pull the new commons in, you can<br>
> run a test to see it work. I use the test command CLI utility in the agent<br>
> to do this [7]. First, build the new dist and run it so you have a Hawkular<br>
> Service running (for example, "mvn clean install -Pdev,embeddedc"). Next,<br>
> create a test JSON request file (say, "/tmp/hawkular.json") with this<br>
> content:<br>
><br>
> { "playbook":"start-wildfly.yml",<br>
> "extraVars": {<br>
> "wildfly_home_dir":"/directory/where/you/installed/wildfly"<br>
> }<br>
> }<br>
><br>
> Now build the hawkular-agent from source (just so you get the test command<br>
> CLI utility) and run the test command CLI, telling it to use the JSON in<br>
> your file and send it to your Hawkular Service server:<br>
><br>
> $ cd<br>
> <hawkular-agent-source-dir>/hawkular-wildfly-agent-itest-parent/hawkular-wildfly-agent-command-cli/target<br>
><br>
> $ java -jar hawkular-wildfly-agent-command-cli-*.jar --username jdoe<br>
> --password password \<br>
> --command AnsibleRequest --request-file=/tmp/hawkular.json<br>
><br>
> This sends the request to your local Hawkular Service server over the<br>
> websocket, the Ansible playbook "start-wildfly.yml" is run, which starts the<br>
> WildFly in that home dir you specified in your JSON request, and the<br>
> response is sent back. The Command CLI tool will write the responses it<br>
> receives to disk - look at the cli output for the names of the files it<br>
> writes - you can look in there to see what the Ansible command response was<br>
> (its just the full Ansible output).<br>
><br>
> There is still LOTS to do here (for one, you'll notice it assumes your<br>
> wildfly install is on "localhost" :)). This is merely a PoC that we can use<br>
> as a starting point - it shows that this can be done and how we can do it.<br>
><br>
> -- John Mazz<br>
><br>
> [1]<br>
> <a href="https://github.com/jmazzitelli/hawkular-commons/tree/HAWKULAR-1096-ansible-commands" rel="noreferrer" target="_blank">https://github.com/jmazzitelli/hawkular-commons/tree/HAWKULAR-1096-ansible-commands</a><br>
> [2]<br>
> <a href="https://github.com/jmazzitelli/hawkular-services/tree/HAWKULAR-1096-ansible-commands" rel="noreferrer" target="_blank">https://github.com/jmazzitelli/hawkular-services/tree/HAWKULAR-1096-ansible-commands</a><br>
> [3]<br>
> <a href="https://github.com/jmazzitelli/hawkular-services/tree/HAWKULAR-1096-ansible-commands/dist/src/main/resources/standalone/configuration/ansible" rel="noreferrer" target="_blank">https://github.com/jmazzitelli/hawkular-services/tree/HAWKULAR-1096-ansible-commands/dist/src/main/resources/standalone/configuration/ansible</a><br>
> [4]<br>
> <a href="https://github.com/jmazzitelli/hawkular-commons/blob/HAWKULAR-1096-ansible-commands/hawkular-command-gateway/hawkular-command-gateway-api/src/main/resources/schema/AnsibleRequest.schema.json" rel="noreferrer" target="_blank">https://github.com/jmazzitelli/hawkular-commons/blob/HAWKULAR-1096-ansible-commands/hawkular-command-gateway/hawkular-command-gateway-api/src/main/resources/schema/AnsibleRequest.schema.json</a><br>
> [5]<br>
> <a href="https://github.com/jmazzitelli/hawkular-commons/blob/HAWKULAR-1096-ansible-commands/hawkular-command-gateway/hawkular-command-gateway-api/src/main/resources/schema/AnsibleResponse.schema.json" rel="noreferrer" target="_blank">https://github.com/jmazzitelli/hawkular-commons/blob/HAWKULAR-1096-ansible-commands/hawkular-command-gateway/hawkular-command-gateway-api/src/main/resources/schema/AnsibleResponse.schema.json</a><br>
> [6]<br>
> <a href="https://github.com/jmazzitelli/hawkular-commons/blob/HAWKULAR-1096-ansible-commands/hawkular-command-gateway/hawkular-command-gateway-war/src/main/java/org/hawkular/cmdgw/command/ws/AnsibleCommand.java" rel="noreferrer" target="_blank">https://github.com/jmazzitelli/hawkular-commons/blob/HAWKULAR-1096-ansible-commands/hawkular-command-gateway/hawkular-command-gateway-war/src/main/java/org/hawkular/cmdgw/command/ws/AnsibleCommand.java</a><br>
> [7]<br>
> <a href="https://github.com/hawkular/hawkular-agent/tree/master/hawkular-wildfly-agent-itest-parent/hawkular-wildfly-agent-command-cli" rel="noreferrer" target="_blank">https://github.com/hawkular/hawkular-agent/tree/master/hawkular-wildfly-agent-itest-parent/hawkular-wildfly-agent-command-cli</a><br>
> _______________________________________________<br>
> hawkular-dev mailing list<br>
> <a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
><br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>