The main objective of this Ansible project is to automate the configuration of the DCS-DV component to be deployed in 5G EVE from scratch, with differents steps to be executed, all gathered in main_playbook.yml.
Be sure of using this Ansible in a server which is able to reach the DCS-DV server through a SSH connection.
Installations steps are based on these references: 1 and 2
Note: be aware of having Internet connection and DNS resolution in the DCS-DV server to be updated. For that purpose, include nameserver 8.8.8.8 in /etc/resolv.conf in case it has not been included in that file or in /etc/network/interfaces file with the clause dns-nameservers 8.8.8.8. Moreover, it is desirable to exchange SSH keys between the DCS-DV server and the server in which Ansible will be executed.
$ sudo apt-get update -y
$ sudo apt-get install software-properties-common -y
$ sudo apt-add-repository --yes --update ppa:ansible/ansible
$ sudo apt-get install ansible -y
$ export ANSIBLE_HOST_KEY_CHECKING=False$ sudo apt-get update -y
$ sudo apt-get install git -yIt is contained in the 5geve-wp4-dcs-dv-deployment Ansible project:
$ cd /tmp
$ git clone git@github.com:5GEVE/5geve-wp4-dcs-dv-deployment.git
$ cd 5geve-wp4-dcs-dv-deployment
$ git checkout dev # if exists - if not, use master branch or whateverIn this Ansible project, there are some configuration files that must be completed with all the necessary information in order to reflect the infrastructure to be uploaded with all the steps included here. The configuration files with their description are the following:
- hosts: here, you have to include the DCS-DV server which will be configured within this Ansible project. The format of each line (PLEASE FOLLOW THIS FORMAT) should be the following: dcs_dv_hostname ansible_host=<DCS_DV_IP> ansible_user= ansible_ssh_pass=<SSH_PASS> ansible_become_pass=<SUDO_PASS>
- group_vars: includes useful variables for the servers defined in the hosts file.
- all: applies to all servers. Nothing to change here at the beginning. Only if you want to be stopped with each Ansible role execution, set prompt_when_finishes_tasks to true, or false otherwise. Other variables that may require a change are elasticsearch_password, which must be set to the password to be used for "elastic" user in Elasticsearch (if this playbook has already been executed in a server, you can check this parameter in the /usr/bin/dcs/create_logstash_pipeline.sh script - PASSWORD variable), dcm_ip_address, setting the DCM IP address, eve_db_password, setting the password to be used for the eve user in the DB, kibana_auth_enabled, enabling or not authentication in Kibana with Keycloak, update_module, which specifies if it is an update (true) or an installation from scratch (false), production_environment, to set some features related to the production environment in 5G EVE, keycloak_ip_address, setting the Keycloak IP address, keycloak_realm, setting the Keycloak Realm name, keycloak_client, setting the Keycloak client name, keycloak_clientsecret, setting the Keycloak password for the selected client, keycloak_cookie_password, setting the Keycloak cookie password, keycloak_username, setting the Keycloak username, keycloak_password, setting the Keycloak password, keycloak_nginx_user, setting the user to be used by nginx to interact with Keycloak, keycloak_nginx_password, setting the password related to the previous user, and keycloak_nginx_file, which is the file in which the nginx configuration will be saved.
$ cd /tmp
$ git clone git@github.com:5GEVE/5geve-wp4-dcs-signalling-topic-handler.git
$ cd dcs-python
$ git checkout dev # if exists - if not, use master branch6. Compress 5geve-wp4-dcs-signalling-topic-handler project and put it in this Ansible project as file
The easiest way to transfer the 5geve-wp4-dcs-signalling-topic-handler project to the DCS-DV server without having to exchange private keys or related (and confidential) information is to compress the 5geve-wp4-dcs-signalling-topic-handler project and send it to the DCS-DV server, where it would be decompressed and executed afterwards.
$ cd /tmp
$ mv 5geve-wp4-dcs-signalling-topic-handler dcs-python
$ tar czf dcs-python.tar.gz dcs-python
$ mv dcs-python.tar.gz 5geve-wp4-dcs-dv-deployment/roles/preparation/files$ cd /tmp
$ git clone git@github.com:5GEVE/5geve-wp4-dcs-kibana-dashboards-handler.git
$ cd 5geve-wp4-dcs-kibana-dashboards-handler
$ git checkout dev # if exists - if not, use master branch or whatever
$ git clone --recursive git@github.com:5GEVE/5geve-wp4-dcs-kibana-dashboards-generator.git # if not exist
$ cd 5geve-wp4-dcs-kibana-dashboards-generator
$ git checkout dev # if exists - if not, use master branch or whatever
$ cd ..
$ mv 5geve-wp4-dcs-kibana-dashboards-generator kibana-dashboards8. Compress 5geve-wp4-dcs-kibana-dashboards-handler project and put it in this Ansible project as file
The easiest way to transfer the 5geve-wp4-dcs-kibana-dashboards-handler project to the DCS-DV server without having to exchange private keys or related (and confidential) information is to compress the 5geve-wp4-dcs-kibana-dashboards-handler project and send it to the DCS-DV server, where it would be decompressed and used afterwards.
$ cd /tmp
$ mv 5geve-wp4-dcs-kibana-dashboards-handler dcs
$ tar czf dcs.tar.gz dcs
$ mv dcs.tar.gz 5geve-wp4-dcs-dv-deployment/roles/preparation/files$ cd /tmp/5geve-wp4-dcs-dv-deployment
$ ansible-playbook -i hosts main_playbook.yml- In case you want to monitor how much time is spent in each task, you have to modify the file /etc/ansible/ansible.cfg by uncommenting the callback_whitelist variable (line 83 of the file, "probably"), putting the following value: callback_whitelist = profile_tasks
This work has been done by Telcaria Ideas S.L. for the 5G EVE European project under the Apache 2.0 License.