Automation - write Ansible code to replace the installation script

fadeoutsoftware / WASDI

Web Advanced Space Developers Interface

http://www.wasdi.net

GNU General Public License v3.0

13 stars 5 forks source link

Automation - write Ansible code to replace the installation script #420

Closed ghost closed 2 years ago

ghost commented 2 years ago

Write Ansible code to replace the current installation script. Objective:

at least same features than the current script
to be able to reexecute the code safely
to version configurations files
to be able to manage different OS (Ubuntu, CentOS, etc)

ghost commented 2 years ago

Update:

I just saw I never write in this ticket.

I initialized the usage of Ansible with the major upgrade of MongoDB we have to do. And I continued to write a little code.

What I have at this moment:

for the major upgrade:
- a standalone playbook to upgrade MongoDB
for the long term:
- a role commonHandler to use to restart most common SystemD services (Apache, Nginx, RabbitMQ, etc)
- a role companyCopyFile which is a generic role to manage general / systme configuration file (example: /etc/nanorc because it make no sense to have a dedicated role just for the nano's configuration file)
- a role companyExploitationDirectory which is a role to install generic tools made by sysadmin (identity.sh, color.sh, etc)
- a role systemPackage which is the role to install all needed packages when we install a new server

ghost commented 2 years ago

Update

Now we have (in addition):

a role to manage logrotate configuration
a role to manage sudoers
a role to manage update-motd (specific for Ubuntu servers)

ghost commented 2 years ago

Update

Now we have (in addition):

a role to manage MongoDB
a role to manage Nginx
a role to manage Python PIP libraries

ghost commented 2 years ago

Update

Now we have (in addition):

a role to manage Keycloak (standalone instance for the moment)
a role to manage Ansible > state file > attribute 'i' (chattr +i)

ghost commented 2 years ago

Update

Now we have (in addition):

a role to manage docker
a role to manage keycloak in domain mode
a role to manage Sen2cor
a role to manage system users and groups (ssh keys are not managed yet)

The MongoDB's code is updated to be able to manage index

ghost commented 2 years ago

Update

Now we have (in addition):

a role to manage RabbitMQ (installation, configuration, user/right management, cluster management, plugins management)
a role to manage the hostname of machines

It remains:

tomcat
geoserver
wasdi (folders creation, configuration, installation, scheduler, ssh tunnel, etc)
backup management (everything I did manually to automatize: rsnapshot etc)

ghost commented 2 years ago

Update

Now we have (in addition):

a role to manage tomcat (+ cleanSnapDir)
a role to manage wasdi > jni
a role to manage wasdi > launcher
a role to manage wasdi > scheduler
a role to manage wasdi > ssh tunnel
a role to manage wasdi > trigger
a role to manage wasdi > utils
a role to manage SSH keys (public, private, authorized_key)

ghost commented 2 years ago

Update

This ticket was not updated for a long time but I progressed.

At this moment we are able to manage (full list):

several configurations files (/etc/updatedb.conf, etc)
docker
/etc/hosts entries
geoserver
GlusterFS (+ volumes)
hostname
Keycloak (domain and standalone)
logrotate
LVM
MongoDB server (standalone and ReplicaSet)
MongoDB indexes
MongoDB users
motd
Nginx
OpenSSH
PostgreSQL
Python > PIP packages
RabbitMQ
Sen2Cor
SSH keys (authorized_keys + private keys)
sudoers rules
systemd > resolved
system packages
system user and group
Tomcat
our toolbox
wasdi > backup
wasdi > client
wasdi > common
wasdi > JNI
wasdi > launcher
wasdi > scheduler
wasdi > ssh tunnels
wasdi > trigger
wasdi > utils

It remains (except if I forgot something):

to configure properly the cloud init component to be aligned everywhere
to continue to align all old servers (example : ssh configuration, etc)

ghost commented 2 years ago

Update

cloud init was aligned on all servers
sshd_config was aligned on all servers

Now I will analyze next things to align and open dedicated ticket if too risky and/or if we need a dedicated maintenance

ghost commented 2 years ago

Update

I analyzed and then here are my dedicated tickets: https://github.com/fadeoutsoftware/WASDI/issues/499 https://github.com/fadeoutsoftware/WASDI/issues/500 https://github.com/fadeoutsoftware/WASDI/issues/501

Now we can close this ticket.