davgordo / fuse-spring-boot-playbooks

Ansible playbooks for operation automation of Fuse on Spring Boot

Fuse on Spring Boot Ansible playbooks

Provision and deploy Fuse integration packaged as Spring Boot applications.

Run the playbook

ansible-playbook playbook.yml -i {inventory} -e app_name=example-app -e app_version=1.0.0 -e app_artifact_path=files/hello-1.0.0.jar

Alternatively, an app_artifact_url can be specified to download the Spring Boot jar from an HTTP endpoint.

Test with Vagrant

• place sample jar in files directory or provide a default artifact URL
• vagrant up

If you're looking for a sample service that works with this playbook, checkout this simple RESTlet example

fuse-spring-boot-playbooks's Issues

Suggested improvements to role

The following are a list of suggested improvements that may be made to the repository:

1. Investigate the use of tags
2. An role already exists for setting up many of the prerequisites including Java at this repository. May want to omit many of the steps from the environment.yml task
3. The health check should make use of inventory_hostname and not ansible_host
   1. Should also have the endpoint be parameterized instead of a static /health
4. Cleanup should not use shell module but a combination of find to locate files in question and the file to remove the file
5. Considerations in the role for opening firewall ports (iptables or firewalld). A good example can be found here

deployments of the same app version more than once does not start up app

This may be a design we want to revisit. Should the user be allowed to deploy the same app version more than once?

Currently, if the user deploys the same app version twice, then the existing deployment is overwritten (which means that rollback would not be possible). Even worse, the handler that starts the newly deployed app is skipped, because the notify doesn't fire.

One idea could be to uniquely name each deployment (even if it's the same artifact version) by using either a timestamp or a build number. This way every deployment creates a unique directory.

See roles/deployment/tasks/main.yml