2013-06-26 19:59:20 +02:00
|
|
|
## Standalone JBoss Deployment
|
|
|
|
|
|
|
|
|
|
- Requires Ansible 1.2 or newer
|
|
|
|
|
- Expects CentOS/RHEL 6.x hosts
|
|
|
|
|
|
|
|
|
|
These playbooks deploy a very basic implementation of JBoss Application Server,
|
|
|
|
|
version 7. To use them, first edit the "hosts" inventory file to contain the
|
|
|
|
|
hostnames of the machines on which you want JBoss deployed, and edit the
|
|
|
|
|
group_vars/jboss-servers file to set any JBoss configuration parameters you need.
|
|
|
|
|
|
|
|
|
|
Then run the playbook, like this:
|
|
|
|
|
|
2013-06-26 20:13:17 +02:00
|
|
|
ansible-playbook -i hosts site.yml
|
2013-06-26 19:59:20 +02:00
|
|
|
|
|
|
|
|
When the playbook run completes, you should be able to see the JBoss
|
|
|
|
|
Application Server running on the ports you chose, on the target machines.
|
|
|
|
|
|
|
|
|
|
This is a very simple playbook and could serve as a starting point for more
|
|
|
|
|
complex JBoss-based projects.
|
|
|
|
|
|
|
|
|
|
### Ideas for Improvement
|
|
|
|
|
|
|
|
|
|
Here are some ideas for ways that these playbooks could be extended:
|
|
|
|
|
|
|
|
|
|
- Write a playbook or an Ansible module to configure JBoss users.
|
|
|
|
|
- Write a playbook to deploy an actual application into the server.
|
|
|
|
|
- Extend this configuration to multiple application servers fronted by a load
|
|
|
|
|
balancer or other web server frontend.
|
|
|
|
|
|
|
|
|
|
We would love to see contributions and improvements, so please fork this
|
|
|
|
|
repository on GitHub and send us your changes via pull requests.
|
