Skip to content
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.

Talend/ansible-talend-platform

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

63 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Ansible framework for Talend Platform (deprecated)

Deprecation: Installing Talend products using RPM is deprecated from the R2023-03 release. Use Talend Installer instead. For more information, see Installing your Talend products using Talend Installers.

This repository contains Ansible roles and playbooks to deploy, manage, and configure the Talend Platform services.

Note: These playbooks are provided without support and are intended to be a guideline. Any issue encountered can be reported via Talend Support and will be addressed on a best effort basis. Pull requests are also encouraged.

Specifically, this repository, through its playblooks:

  • Installs Talend 7.2, 7.3 or 8.0 RPM packages.
  • Starts services using systemd scripts.
  • Provides configuration options for Talend packages.

You can find detailed documentation about each RPM package delivered by Talend and their related services in Talend Help Center.

Prerequisites

To be able to install applications using Ansible, you need to setup your environment as follows:

  1. Install Extra Packages for Enterprise Linux:
    sudo yum install epel-release
  2. Install Ansible on the master host used for the deployment:
    sudo yum install ansible
  3. All hosts need to be reachable via SSH from the master node. Hosts must be defined in /etc/ansible/hosts on the master node. Note that provided default playbook talend.yml uses host group tac-group
  4. Install git: sudo yum install git
  5. Make sure you have at least 2GB free disk space in /var.
  6. Ansible typically requires a password-less SSH access from master to a target host and a password-less "sudo" on a target host.

Installing Talend applications using RPM/Ansible require RHEL/CentOS 7.X or 8.X or Rocky 8.X as operating system.

Installing applications using Ansible

  1. Perform a Git checkout the tagged release release/X.Y.Z of the Talend version you are installing.

  2. Specify your credentials and the version of Talend applications to install in the ansible/group_vars/all file. These parameters are used to access the RPM repository. To change the RPM version to install, edit the following parameters:

    • 7.2 applications:
    rpm_base_version: 7.2
    rpm_patch_version: 1
    rpm_build_number: 201906201446
    • 7.3 applications:
    rpm_base_version: 7.3
    rpm_patch_version: 1
    rpm_build_number: 202002191130
    • 8.0 applications:
    rpm_base_version: 8.0
    rpm_patch_version: 1
    rpm_build_number: 202211231200
  3. Configure the playbook you want to install by specifying:

    1. the hosts to install the roles on. Hosts must be defined in /etc/ansible/hosts on the master node.
    2. the remote_user name. Make sure that the user has the required permissions to install applications on all hosts.
    3. the roles to install, by installation order.
    4. the vars to overwrite with a new value for that specific playbook. Adding variables to the playbook is optional.

    For example:

      hosts: tac-group
      remote_user: root
      roles:
        - java
        - talend-repo
        - runtime
      vars:
        rt_http_port: 8041
        rt_https_port: 9002
        rt_ssh_port: 8102
        rt_rmi_registry_port: 1100
        rt_rmi_server_port: 44445
        rt_js_command_server_port: 8010
        rt_js_file_server_port: 8011
        rt_js_monitoring_port: 8898
        rt_js_process_message_port: 8556
        rt_master_password: 'password'

    Sample playbooks are available here or here.

  4. Configure the installation parameters as well as the configuration of each role using their respective defaults/main.yml file.
    Variables can be overwritten if they are set differently directly in the playbook.

  5. Run the playbook:
    ansible-playbook <playbook>.yml

Important: Always include java and then talend-repo roles in as first roles in playbooks. If Tomcat is needed for the set of roles that are installed, also include the tomcat role between talend-repo and the following roles.

Uninstalling applications

You can remove installed applications using sudo yum remove <list_of_packages> manually on every host.

The list of packages can be received by executing the command rpm -qa | grep talend.

List of applications

The following applications can be installed from this repository using their dedicated Ansible role:

Role Application
tac Talend Administration Center (TAC)
iam Talend Identity and Access Management (IAM) service
mdm Talend Master Data Management (MDM)
logserver Talend Log Server
jobserver Talend Job Server
runtime Talend Runtime server
tdp Talend Data Preparation (requires tcomp)
tcomp Talend Component Server
tds Talend Data Stewardship (TDS)
tsd Talend Dictionary Service (TSD)
sap-rfc-server Talend SAP RFC Server
filebeat Talend Filebeat service

The following roles install third-party components:

Role Application
tomcat Apache Tomcat server (required by tac, iam, tds, tsd and mdm)
mongodb MongoDB server (required by tds, tdp and tsd)
kafka Apache Kafka server (required by tds and tdp)
minio MinIO server (required by tsd)

List of applications compatible with Talend Cloud Hybrid setup

Talend Cloud lets you install and host Talend Data Preparation (tdp), Talend Data Stewardship (tds) and Talend Dictionary Service (tsd) on premises. This setup allows you to store sensitive data behind your firewall, while still managing your users and the rest of your platform from Talend Cloud.

Ansible roles corresponding to these applications are compatible with the Hybrid setup for Talend Cloud. See dedicated hybrid parameters in the details of each role.

To learn more about it, refer to Talend Help Center.

List of ports to open

Each application requires some TCP/IP ports to be open by default:

  • tac: 8080 (parameter app_tomcat_port in tac defaults )
  • iam: 9080 (parameter app_tomcat_port in iam defaults )
  • mdm: 8180 (parameter app_tomcat_port in mdm defaults )
  • runtime: 1099, 8000, 8001, 8040, 8101, 8555, 8888, 9001, 44444 (look for parameters in runtime defaults )
  • jobserver: 8000, 8001, 8555, 8888 (look for parameters in jobserver defaults )
  • tdp: 9999 (parameter tdp_server_port in tdp defaults )
  • tcomp: 8989 (parameter tcomp_server_port in tcomp defaults )
  • tds: 19999 (parameter app_tomcat_port in tds defaults )
  • tdq: 8187 (parameter app_tomcat_port in tsd defaults )
  • logserver: 9200 and 9300 for Elastic Search; 5601 for Kibana; 5044, 8057 and 9600 for LogStash (some ports can be configured in logserver defaults, others are hard-coded)

In addition, service components (Kafka, MongoDB and Minio) require open ports when accessed from other hosts:

To open a port, you can use one of the methods described below:

  • By directly opening ports. For example:

    sudo firewall-cmd --add-port=8080/tcp --permanent
    sudo firewall-cmd --add-port=9080/tcp --permanent
    sudo firewall-cmd --reload
  • By creating Talend network service files in /etc/firewalld/services. For example:

    Create the following xml file in the folder /etc/firewalld/services with file name Talend-TAC.xml:

    <?xml version="1.0" encoding="utf-8"?>
    <service>
      <short>Talend Administration Center</short>
      <description>Talend Administration Center is a web-based application allowing data integration project managers to administrate users and projects. It also controls and monitors the execution of Jobs.</description>
      <port protocol="tcp" port="8080"/>
    </service>

    After that you can activate Talend-TAC service with commands:

    sudo firewall-cmd --add-service=Talend-TAC --permanent
    sudo firewall-cmd --reload

Issues

Issues are tracked through Talend Support.

Licence

Apache license