indigo-dc/ansible-role-kepler

Ansible role to deploy the Kepler scientific workflow engine and Indigo workflows

Role and Dockerfile for Kepler Workflow engine

Roles and Dockerfiles to install the Kepler Workflow engine:

Introduction

The repository contains ansible-roles that are published in ansible galaxy:

• https://galaxy.ansible.com/indigo-dc/kepler/

The directory docker-kepler is linked to dockerhub with automatic build. This image can run the Kepler Workflow engine

Requirements

No aditional requirements

Role Variables

The variables that can be passed to this role and a brief description about them are as follows.

• indigo_kepler_version: a version of indigo-dc/indigokepler module to be used
• password_vnc: password to connect to VNC

Dependencies

None for now

Install the Playbook

To install the role:

$ ansible-galaxy install indigo-dc.kepler

Run the playbook

An example of playbook for the kepler:

---
- hosts: localhost
  become: true
  roles:
    - indigo-dc.kepler

Or execute:

$ ansible-playbook /etc/ansible/roles/indigo-dc.kepler/tests/kepler.yml

Run the kepler workflow application

License

Apache v2

Author Information

Mario David: [email protected] LIP and Indigo-DataCloud project

Acknowledgments

• Kepler and Kepler WF for Indigo

ansible-role-kepler's Issues

Including init.sh in the execution of the role

The file docker-kepler/Dockerfile includes the following last line:
CMD /etc/init.d/vmcontext start; /home/ubuntu/init.sh
Therefore, the script init.sh, which starts up the VNC server, is only executed when a Docker container is started.

If this role is executed on a Virtual Machine, then the script is never executed and the VNC server is not started.

Is it possible to introduce the actions of the init.sh script inside the Ansible Role so that feature parity is matched between Docker containers and VMs?

Also, the execution of the init.sh inside a vanilla Ubuntu 14.04 Virtual Machine Image results in the following error
:...
/root/.vnc/xstartup: 25: /root/.vnc/xstartup: twm: not found
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 113 requests (113 known processed) with 0 events remaining.
Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s
root@vnode-0:/home/ubuntu#