ajout role kea + s-kea1-ps.yml

README.md

@@ -1,6 +1,6 @@
 # gsb2024
 
-2024-01-17 18h04 ps
+2024-01-19 11h45 ps
 
 Environnement et playbooks **ansible** pour le projet **GSB 2024**
 
@@ -23,8 +23,8 @@ Prérequis :
   * **r-ext** : routage, NAT
   * **s-proxy** : proxy **squid**
   * **s-itil** : serveur GLPI
-  * **s-backup** : DNS esclave + sauvegarde s-win (SMB)
+  * **s-backup** : DNS esclave + sauvegarde s-win (SMB), Stork et Gotify
-  * **s-mon** : supervision avec **Nagios4**, notifications et syslog
+  * **s-mon** : supervision avec **Nagios4/Zabbix**, notifications et journald
   * **s-fog** : deploiement postes de travail avec **FOG**
   * **s-win** : Windows Server 2019, AD, DNS, DHCP, partage fichiers
   * **s-nxc** : NextCloud avec **docker** via proxy inverse **traefik** et certificat auto-signé

goss/s-kea1.yaml

@@ -0,0 +1,90 @@
+file:
+  /etc/kea/kea-ctrl-agent.conf:
+    exists: true
+    mode: "0644"
+    size: 2470
+    owner: _kea
+    group: root
+    filetype: file
+    contains: []
+  /etc/kea/kea-dhcp4.conf:
+    exists: true
+    mode: "0644"
+    size: 11346
+    owner: _kea
+    group: root
+    filetype: file
+    contains: []
+  /tmp/kea4-ctrl-socket:
+    exists: true
+    mode: "0755"
+    size: 0
+    owner: _kea
+    group: _kea
+    filetype: socket
+    contains: []
+  /usr/local/lib/kea:
+    exists: true
+    mode: "0755"
+    size: 4096
+    owner: root
+    group: root
+    filetype: directory
+    contains: []
+package:
+  isc-kea-common:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  isc-kea-ctrl-agent:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  isc-kea-dhcp4:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  isc-kea-hooks:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  libmariadb3:
+    installed: true
+    versions:
+    - 1:10.11.4-1~deb12u1
+  mariadb-common:
+    installed: true
+    versions:
+    - 1:10.11.4-1~deb12u1
+  mysql-common:
+    installed: true
+    versions:
+    - 5.8+1.1.0
+port:
+  tcp:8000:
+    listening: true
+    ip:
+    - 172.16.64.20
+service:
+  isc-kea-ctrl-agent.service:
+    enabled: true
+    running: true
+  isc-kea-dhcp4-server.service:
+    enabled: true
+    running: true
+interface:
+  enp0s3:
+    exists: true
+    addrs:
+    - 192.168.99.20/24
+    mtu: 1500
+  enp0s8:
+    exists: true
+    addrs:
+    - 172.16.0.20/24
+    mtu: 1500
+  enp0s9:
+    exists: true
+    addrs:
+    - 172.16.64.20/24
+    mtu: 1500

goss/s-kea2.yaml

@@ -0,0 +1,90 @@
+file:
+  /etc/kea/kea-ctrl-agent.conf:
+    exists: true
+    mode: "0644"
+    size: 2470
+    owner: _kea
+    group: root
+    filetype: file
+    contains: []
+  /etc/kea/kea-dhcp4.conf:
+    exists: true
+    mode: "0644"
+    size: 11346
+    owner: _kea
+    group: root
+    filetype: file
+    contains: []
+  /tmp/kea4-ctrl-socket:
+    exists: true
+    mode: "0755"
+    size: 0
+    owner: _kea
+    group: _kea
+    filetype: socket
+    contains: []
+  /usr/local/lib/kea:
+    exists: true
+    mode: "0755"
+    size: 4096
+    owner: root
+    group: root
+    filetype: directory
+    contains: []
+package:
+  isc-kea-common:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  isc-kea-ctrl-agent:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  isc-kea-dhcp4:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  isc-kea-hooks:
+    installed: true
+    versions:
+    - 2.4.1-isc20231123184533
+  libmariadb3:
+    installed: true
+    versions:
+    - 1:10.11.4-1~deb12u1
+  mariadb-common:
+    installed: true
+    versions:
+    - 1:10.11.4-1~deb12u1
+  mysql-common:
+    installed: true
+    versions:
+    - 5.8+1.1.0
+port:
+  tcp:8000:
+    listening: true
+    ip:
+    - 172.16.64.21
+service:
+  isc-kea-ctrl-agent.service:
+    enabled: true
+    running: true
+  isc-kea-dhcp4-server.service:
+    enabled: true
+    running: true
+interface:
+  enp0s3:
+    exists: true
+    addrs:
+    - 192.168.99.21/24
+    mtu: 1500
+  enp0s8:
+    exists: true
+    addrs:
+    - 172.16.0.21/24
+    mtu: 1500
+  enp0s9:
+    exists: true
+    addrs:
+    - 172.16.64.21/24
+    mtu: 1500

goss/s-lb-bd.yaml

@@ -1,21 +1,38 @@
-package:
+addr:
-  mysql-server:
+    tcp://192.168.102.1:80:
-    installed: true
+        reachable: true
-    versions:
+        timeout: 500
-    - 5.5.54-0+deb8u1
+    tcp://192.168.102.2:80:
-command:
+        reachable: true
-  egrep "#bind-address" /etc/mysql/my.cnf:
+        timeout: 500
-    exit-status: 0
+service:
-    stdout:
+    mariadb:
-    - "#bind-address\t\t= 127.0.0.1"
+        enabled: true
-    stderr: []
+        running: true
-    timeout: 10000
+    mysql:
+        enabled: true
+        running: true
+user:
+    mysql:
+        exists: true
+        uid: 104
+        gid: 111
+        groups:
+            - mysql
+        home: /nonexistent
+        shell: /bin/false
+group:
+    mysql:
+        exists: true
+        gid: 111
 interface:
-  enp0s3:
+    enp0s3:
-    exists: true
+        exists: true
-    addrs:
+        addrs:
-    - 192.168.99.13/24
+            - 192.168.99.154/24
-  enp0s8:
+        mtu: 1500
-    exists: true
+    enp0s8:
-    addrs:
+        exists: true
-    - 192.168.102.50/24
+        addrs:
+            - 192.168.102.254/24
+        mtu: 1500

goss/s-lb-web1.yaml

@@ -1,63 +1,62 @@
 package:
-  apache2:
+    apache2:
-    installed: true
+        installed: true
-    versions:
+        versions:
-    - 2.4.10-10+deb8u7
+            - 2.4.57-2
-  php5:
+    nfs-common:
-    installed: true
+        installed: true
-    versions:
+        versions:
-    - 5.6.29+dfsg-0+deb8u1
+            - 1:2.6.2-4
 port:
-  tcp:22:
+    tcp6:80:
-    listening: true
+        listening: true
-    ip:
+        ip:
-    - 0.0.0.0
+            - '::'
-  tcp6:22:
-    listening: true
-    ip:
-    - '::'
-  tcp6:80:
-    listening: true
-    ip:
-    - '::'
 service:
-  apache2:
+    apache2:
-    enabled: true
+        enabled: true
-    running: true
+        running: true
-  sshd:
+    nfs-common:
-    enabled: true
+        enabled: false
-    running: true
+        running: false
-user:
-  sshd:
-    exists: true
-    uid: 105
-    gid: 65534
-    groups:
-    - nogroup
-    home: /var/run/sshd
-    shell: /usr/sbin/nologin
-command:
-  egrep 192.168.102.14:/export/www /etc/fstab:
-    exit-status: 0
-    stdout:
-    - 192.168.102.14:/export/www /var/www/html nfs _netdev rw 0 0
-    stderr: []
-    timeout: 10000
 process:
-  apache2:
+    apache2:
-    running: true
+        running: true
-  sshd:
+mount:
-    running: true
+    /var/www/html:
+        exists: true
+        opts:
+            - rw
+            - relatime
+        vfs-opts:
+            - rw
+            - vers=4.2
+            - rsize=131072
+            - wsize=131072
+            - namlen=255
+            - hard
+            - proto=tcp
+            - timeo=600
+            - retrans=2
+            - sec=sys
+            - clientaddr=192.168.102.1
+            - local_lock=none
+            - addr=192.168.102.253
+        source: 192.168.102.253:/home/wordpress
+        filesystem: nfs4
 interface:
-  enp0s3:
+    enp0s3:
-    exists: true
+        exists: true
-    addrs:
+        addrs:
-    - 192.168.99.11/24
+            - 192.168.99.101/24
-  enp0s8:
+        mtu: 1500
-    exists: true
+    enp0s8:
-    addrs:
+        exists: true
-    - 192.168.101.1/24
+        addrs:
-  enp0s9:
+            - 192.168.101.1/24
-    exists: true
+        mtu: 1500
-    addrs:
+    enp0s9:
-    - 192.168.102.1/24
+        exists: true
+        addrs:
+            - 192.168.102.1/24
+        mtu: 1500

goss/s-lb-web2.yaml

@@ -1,63 +1,62 @@
 package:
-  apache2:
+    apache2:
-    installed: true
+        installed: true
-    versions:
+        versions:
-    - 2.4.10-10+deb8u7
+            - 2.4.57-2
-  php5:
+    nfs-common:
-    installed: true
+        installed: true
-    versions:
+        versions:
-    - 5.6.29+dfsg-0+deb8u1
+            - 1:2.6.2-4
 port:
-  tcp:22:
+    tcp6:80:
-    listening: true
+        listening: true
-    ip:
+        ip:
-    - 0.0.0.0
+            - '::'
-  tcp6:22:
-    listening: true
-    ip:
-    - '::'
-  tcp6:80:
-    listening: true
-    ip:
-    - '::'
 service:
-  apache2:
+    apache2:
-    enabled: true
+        enabled: true
-    running: true
+        running: true
-  sshd:
+    nfs-common:
-    enabled: true
+        enabled: false
-    running: true
+        running: false
-user:
-  sshd:
-    exists: true
-    uid: 105
-    gid: 65534
-    groups:
-    - nogroup
-    home: /var/run/sshd
-    shell: /usr/sbin/nologin
-command:
-  egrep 192.168.102.14:/export/www /etc/fstab:
-    exit-status: 0
-    stdout:
-    - 192.168.102.14:/export/www /var/www/html nfs _netdev rw 0 0
-    stderr: []
-    timeout: 10000
 process:
-  apache2:
+    apache2:
-    running: true
+        running: true
-  sshd:
+mount:
-    running: true
+    /var/www/html:
+        exists: true
+        opts:
+            - rw
+            - relatime
+        vfs-opts:
+            - rw
+            - vers=4.2
+            - rsize=131072
+            - wsize=131072
+            - namlen=255
+            - hard
+            - proto=tcp
+            - timeo=600
+            - retrans=2
+            - sec=sys
+            - clientaddr=192.168.102.2
+            - local_lock=none
+            - addr=192.168.102.253
+        source: 192.168.102.253:/home/wordpress
+        filesystem: nfs4
 interface:
-  enp0s3:
+    enp0s3:
-    exists: true
+        exists: true
-    addrs:
+        addrs:
-    - 192.168.99.12/24
+            - 192.168.99.102/24
-  enp0s8:
+        mtu: 1500
-    exists: true
+    enp0s8:
-    addrs:
+        exists: true
-    - 192.168.101.2/24
+        addrs:
-  enp0s9:
+            - 192.168.101.2/24
-    exists: true
+        mtu: 1500
-    addrs:
+    enp0s9:
-    - 192.168.102.2/24
+        exists: true
+        addrs:
+            - 192.168.102.2/24
+        mtu: 1500

goss/s-lb.yaml

@@ -1,28 +1,55 @@
+package:
+    haproxy:
+        installed: true
+        versions:
+            - 2.6.12-1+deb12u1
+addr:
+    tcp://192.168.101.1:80:
+        reachable: true
+        timeout: 500
+    tcp://192.168.101.2:80:
+        reachable: true
+        timeout: 500
 port:
-  tcp:80:
+    tcp:80:
-    listening: true
+        listening: true
-    ip:
+        ip:
-    - 192.168.100.11
+            - 192.168.100.10
 service:
-  haproxy:
+    haproxy:
-    enabled: true
+        enabled: true
-    running: true
+        running: true
-  sshd:
+user:
-    enabled: true
+    haproxy:
-    running: true
+        exists: true
+        uid: 104
+        gid: 111
+        groups:
+            - haproxy
+        home: /var/lib/haproxy
+        shell: /usr/sbin/nologin
+group:
+    haproxy:
+        exists: true
+        gid: 111
+process:
+    haproxy:
+        running: true
 interface:
-  enp0s3:
+    enp0s3:
-    exists: true
+        exists: true
-    addrs:
+        addrs:
-    - 192.168.99.100/24
+            - 192.168.99.100/24
-    mtu: 1500
+        mtu: 1500
-  enp0s8:
+    enp0s8:
-    exists: true
+        exists: true
-    addrs:
+        addrs:
-    - 192.168.100.11/24
+            - 192.168.100.10/24
-    mtu: 1500
+        mtu: 1500
-  enp0s9:
+http:
-    exists: true
+    http://192.168.100.10/:
-    addrs:
+        status: 200
-    - 192.168.101.254/24
+        allow-insecure: false
-    mtu: 1500
+        no-follow-redirects: false
+        timeout: 5000
+        body: []

goss/s-mon.yaml

@@ -1,92 +1,62 @@
-package:
-  apache2:
-    installed: true
-  zabbix-server-mysql:
-    installed: true
-  zabbix-frontend-php:
-    installed: true
-  zabbix-apache-conf:
-    installed: true
-  zabbix-sql-scripts:
-    installed: true
-  zabbix-agent:
-    installed: true
-  mariadb-server:
-    installed: true
-  python3-pymysql:
-    installed: true
-  systemd-journal-remote:
-    installed: true
 file:
-  /etc/systemd/system/systemd-journal-remote.service:
+    /etc/systemd/system/systemd-journal-remote.service:
-    exist: true
+        exists: true
-    mode: "0777"
+        mode: "0644"
-    filetype: directory
+        owner: root
-  /var/log/journal/remote:
+        group: root
-    exist: true
+        filetype: file
-    mode: "0777"
+        contents: []
-    filetype: directory
+    /var/log/journal/remote:
-port:
+        exists: true
-  tcp:80:
+        mode: "0755"
-    listening: true
+        owner: systemd-journal-remote
-    ip:
+        group: systemd-journal-remote
-    - 0.0.0.0
+        filetype: directory
-  tcp:3306:
+        contents: []
-    listening: true
+package:
-    ip:
+    apache2:
-    - 127.0.0.1
+        installed: true
-  tcp:10050:
+        versions:
-    listening: true
+            - 2.4.57-2
-    ip:
+    mariadb-server:
-    - 0.0.0.0
+        installed: true
-  tcp:10051:
+        versions:
-    listening: true
+            - 1:10.11.4-1~deb12u1
-    ip:
+    systemd-journal-remote:
-    - 0.0.0.0
+        installed: true
-  tcp:19532:
+        versions:
-    listening: true
+            - 252.19-1~deb12u1
-    ip:
-      - '*'
 service:
-  apache2:
+    apache2:
-    enabled: true
+        enabled: true
-    running: true
+        running: true
-  zabbix-server:
+    mariadb.service:
-    enabled: true
+        enabled: true
-    running: true
+        running: true
-  zabbix-agent:
+    systemd-journal-remote.socket:
-    enabled: true
+        enabled: true
-    running: true
+        running: true
-  systemd-journal-remote.socket:
+    zabbix-agent:
-    enabled: true
+        enabled: true
-    running: true
+        running: true
-command:
+    zabbix-server:
-  sysctl net.ipv4.ip_forward:
+        enabled: true
-    exit-status: 0
+        running: true
-    stdout:
-    - net.ipv4.ip_forward = 0
-    stderr: []
-    timeout: 10000
-process:
-  apache2:
-    running: true
-  zabbix_server:
-    running: true
-  mariadb:
-    running: true
 interface:
-  enp0s3:
+    enp0s3:
-    exists: true
+        exists: true
-    addrs:
+        addrs:
-    - 192.168.99.8/24
+            - 192.168.99.8/24
-  enp0s8:
+        mtu: 1500
-    exists: true
+    enp0s8:
-    addrs:
+        exists: true
-    - 172.16.0.8/24
+        addrs:
+            - 172.16.0.8/24
+        mtu: 1500
 http:
-  http://localhost/zabbix:
+    http://s-mon.gsb.lan/zabbix:
-    status: 401
+        status: 200
-    allow-insecure: false
+        allow-insecure: false
-    no-follow-redirects: false
+        no-follow-redirects: false
-    timeout: 5000
+        timeout: 5000
-    body: []
+        body: []

goss/s-nas.yaml

@@ -0,0 +1,55 @@
+file:
+    /home/wordpress:
+        exists: true
+        mode: "0755"
+        owner: www-data
+        group: www-data
+        filetype: directory
+        contents: []
+package:
+    file:
+        installed: true
+        versions:
+            - 1:5.44-3
+    nfs-common:
+        installed: true
+        versions:
+            - 1:2.6.2-4
+    nfs-kernel-server:
+        installed: true
+        versions:
+            - 1:2.6.2-4
+addr:
+    tcp://192.168.102.1:80:
+        reachable: true
+        timeout: 500
+    tcp://192.168.102.2:80:
+        reachable: true
+        timeout: 500
+service:
+    nfs-common:
+        enabled: false
+        running: false
+    nfs-kernel-server:
+        enabled: true
+        running: true
+    nfs-mountd:
+        enabled: true
+        running: true
+    nfs-server:
+        enabled: true
+        running: true
+    nfs-utils:
+        enabled: true
+        running: false
+interface:
+    enp0s3:
+        exists: true
+        addrs:
+            - 192.168.99.153/24
+        mtu: 1500
+    enp0s8:
+        exists: true
+        addrs:
+            - 192.168.102.253/24
+        mtu: 1500

goss/s-nxc.yaml

@@ -0,0 +1,145 @@
+file:
+  /root/nxc:
+    exists: true
+    mode: "0755"
+      #size: 4096
+      #owner: root
+      #group: root
+    filetype: directory
+    contains: []
+
+  /root/nxc/certs:
+    exists: true
+    mode: "0755"
+      #size: 4096
+      #owner: root
+      #group: root
+    filetype: directory
+    contains: []
+
+  /root/nxc/config:
+    exists: true
+    mode: "0755"
+      #size: 4096
+      #owner: root
+      #group: root
+    filetype: directory
+    contains: []
+
+  /root/nxc/config/dynamic.yml:
+    exists: true
+    mode: "0644"
+      #size: 415
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+  /root/nxc/config/static.yml:
+    exists: true
+    mode: "0644"
+      #size: 452
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+  /root/nxc/docker-compose.yml:
+    exists: true
+    mode: "0644"
+      #size: 2135
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+  /root/nxc/nxc-debug.sh:
+    exists: true
+    mode: "0755"
+      #size: 64
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+  /root/nxc/nxc-prune.sh:
+    exists: true
+    mode: "0755"
+      #size: 110
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+  /root/nxc/nxc-start.sh:
+    exists: true
+    mode: "0755"
+      #size: 34
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+  /root/nxc/nxc-stop.sh:
+    exists: true
+    mode: "0755"
+      #size: 32
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+  /usr/local/bin/mkcert:
+    exists: true
+    mode: "0755"
+      #size: 4788866
+      #owner: root
+      #group: root
+    filetype: file
+    contains: []
+
+addr:
+  tcp://s-nxc.gsb.lan:443:
+    reachable: true
+    timeout: 500
+
+port:
+  tcp:22:
+    listening: true
+    ip:
+    - 0.0.0.0
+
+  tcp:80:
+    listening: true
+    ip: []
+
+  tcp:443:
+    listening: true
+    ip: []
+
+      #tcp:8081:
+      #listening: true
+      #ip:
+      #- 0.0.0.0
+
+interface:
+  enp0s3:
+    exists: true
+    addrs:
+    - 192.168.99.7/24
+    mtu: 1500
+
+  enp0s8:
+    exists: true
+    addrs:
+    - 172.16.0.7/24
+    mtu: 1500
+
+http:
+  https://s-nxc.gsb.lan:
+    status: 200
+    allow-insecure: true
+    no-follow-redirects: false
+    timeout: 5000
+    body:
+      - Nextcloud

roles/dns-master/files/db.gsb.lan

@@ -5,7 +5,7 @@
 ;
 $TTL    604800
 @       IN      SOA     s-infra.gsb.lan. root.s-infra.gsb.lan. (
-                        2024011800      ; Serial
+                        2024011900      ; Serial
                         7200	        ; Refresh
                         86400           ; Retry
                         8419200         ; Expire
@@ -16,9 +16,11 @@ $TTL    604800
 @      	        IN      A       127.0.0.1
 @       	IN      AAAA    ::1
 s-infra  	IN      A       172.16.0.1
-s-backup        IN      A	172.16.0.4
 s-proxy         IN      A       172.16.0.2
 s-appli    	IN      A       172.16.0.3
+s-backup        IN      A	172.16.0.4
+s-stork         IN      A	172.16.0.4
+s-gotify        IN      A	172.16.0.4
 s-win    	IN      A       172.16.0.6
 s-mess   	IN      A       172.16.0.7
 s-nxc		IN	A	172.16.0.7

roles/docker/tasks/main.yml

@@ -7,7 +7,7 @@
 - name: on verifie si docker est installe
   stat:
     path: /usr/bin/docker
-# command: which docker
+  #command: which docker
   register: docker_present
 
 - name: Execution du script getdocker si docker n'est pas deja installe

roles/gotify/tasks/main.yml

@@ -0,0 +1,50 @@
+---
+    - name: Mise a jour apt cache
+      apt:
+        update_cache: yes
+
+    - name: Creation /etc/gotify
+      ansible.builtin.file:
+        path: /etc/gotify
+        state: directory
+        mode: '0755'
+
+    - name: Creation /opt/gotify
+      ansible.builtin.file:
+        path: /opt/gotify
+        state: directory
+        mode: '0755'
+
+    - name: installation de gotify
+      get_url:
+        url: "https://github.com/gotify/server/releases/latest/download/gotify-linux-amd64.zip"
+        dest: "/tmp/gotify.zip"
+
+    - name: Extraction de Gotify
+      ansible.builtin.unarchive:
+        src: "/tmp/gotify.zip"
+        dest: "/opt/gotify"
+      become: yes
+
+    - name: Creation du fichier systemd
+      template:
+        src: "gotify.service.j2"
+        dest: "/etc/systemd/system/gotify.service"
+      become: yes
+
+    - name: Reload systemd
+      systemd:
+        daemon_reload: yes
+
+    - name: Creation du fichier conf gotify
+      template:
+        src: "config.yml.j2"
+        dest: "/etc/gotify/config.yml"
+      become: yes
+
+    - name: Demarage du gotify
+      systemd:
+        name: gotify
+        state: started
+        enabled: yes
+

roles/gotify/templates/config.yml.j2

@@ -0,0 +1,4 @@
+server:
+  keepaliveperiodseconds: 0
+  listenaddr: "" # the address to bind on, leave empty to bind on all addresses
+  port: 8008

roles/gotify/templates/gotify.service.j2

@@ -0,0 +1,13 @@
+[Unit]
+Description=Gotify Server
+After=network.target
+
+[Service]
+Type=simple
+User=root
+ExecStart=/opt/gotify/gotify-linux-amd64
+Restart=on-failure
+
+[Install]
+WantedBy=multi-user.target
+

roles/kea/README.md

@@ -0,0 +1,14 @@
+# Rôle Kea
+***
+Rôle du Kea pour la haute disponibilité dhcp
+
+## Tables des matières
+    1. [Que fait le rôle Kea ?]
+
+
+## Que fait le rôle Kea ?
+Il permet de configurer les serveur kea en mode haute disponibilité.
+
+### Installation et configuration de kea
+
+Le rôle kea va installer les packets kea dhcp4, hook, admin une fois les packets installer. Nous allons configurer les 2 serveurs kea pour qu'il distribut les ip de n-user et soit en haute disponibilité.

roles/kea/default/main.yml

@@ -0,0 +1,8 @@
+#variable kea
+ kea_ver: "2.4.1"
+  kea_dbname: ""
+  kaa_dbuser: ""
+  kea_dbpasswd: ""
+  kea_dhcp4_dir: "/etc/kea/kea-dhcp4.conf"
+  kea_ctrl_dir: "/etc/kea/kea-ctrl-agent.conf"
+

roles/kea/files/kea-ctrl-agent.conf

@@ -6,7 +6,7 @@
     {
         // We need to specify where the agent should listen to incoming HTTP
         // queries.
-        "http-host": "172.16.64.1",
+        "http-host": "172.16.0.20",
 
         // This specifies the port CA will listen on.
         "http-port": 8000,
@@ -18,7 +18,7 @@
             {
                 "comment": "socket to DHCPv4 server",
                 "socket-type": "unix",
-                "socket-name": "/tm/kea4-ctrl-socket"
+                "socket-name": "/tmp/kea4-ctrl-socket"
             },
 
             // Location of the DHCPv6 command channel socket.

roles/kea/files/kea-dhcp4.conf

@@ -22,7 +22,7 @@
         // The DHCPv4 server listens on this interface. When changing this to
         // the actual name of your interface, make sure to also update the
         // interface parameter in the subnet definition below.
-        "interfaces": [ "enp0s8" ]
+        "interfaces": [ "enp0s9" ]
     },
 
     // Control socket is required for communication between the Control
@@ -88,7 +88,7 @@
                 "high-availability": [ {
                     // This parameter points to this server instance. The respective
                     // HA peers must have this parameter set to their own names.
-                    "this-server-name": "kea1",
+                    "this-server-name": "s-kea1.gsb.lan",
                     // The HA mode is set to hot-standby. In this mode, the active server handles
                     // all the traffic. The standby takes over if the primary becomes unavailable.
                     "mode": "hot-standby",
@@ -116,24 +116,24 @@
                     "peers": [
                         // This is the configuration of this server instance.
                         {
-                            "name": "kea1",
+                            "name": "s-kea1.gsb.lan",
                             // This specifies the URL of this server instance. The
                             // Control Agent must run along with this DHCPv4 server
                             // instance and the "http-host" and "http-port" must be
                             // set to the corresponding values.
-                            "url": "http://172.16.64.1:8000/",
+                            "url": "http://172.16.64.20:8000/",
                             // This server is primary. The other one must be
                             // secondary.
                             "role": "primary"
                         },
                         // This is the configuration of the secondary server.
                         {
-                            "name": "kea2",
+                            "name": "s-kea2.gsb.lan",
                             // Specifies the URL on which the partner's control
                             // channel can be reached. The Control Agent is required
                             // to run on the partner's machine with "http-host" and
                             // "http-port" values set to the corresponding values.
-                            "url": "http://172.16.64.2:8000/",
+                            "url": "http://172.16.64.21:8000/",
                             // The other server is secondary. This one must be
                             // primary.
                             "role": "standby"
@@ -152,7 +152,7 @@
 
             // There are no relays in this network, so we need to tell Kea that this subnet
             // is reachable directly via the specified interface.
-            "interface": "enp0s8",
+            "interface": "enp0s9",
 
             // Specify a dynamic address pool.
             "pools": [
@@ -171,7 +171,7 @@
                 {
                     // For each IPv4 subnet you typically need to specify at least one router.
                     "name": "routers",
-                    "data": "172.16.64.1"
+                    "data": "172.16.64.254"
                 },
                 {
                     // Using cloudflare or Quad9 is a reasonable option. Change this
@@ -179,7 +179,7 @@
                     // choice is 8.8.8.8, owned by Google. Using third party DNS
                     // service raises some privacy concerns.
                     "name": "domain-name-servers",
-                    "data": "172.16.64.1"
+                    "data": "172.16.0.1"
                 }
             ],
 

roles/kea/handlers/main.yml

@@ -0,0 +1,12 @@
+---  
+- name: Restart isc-kea-dhcp4-server
+  ansible.builtin.service:
+    name: isc-kea-dhcp4-server.service
+    state: restarted
+    enabled: yes
+
+- name: Restart isc-kea-ctrl-agent
+  ansible.builtin.service:
+    name: isc-kea-ctrl-agent.service
+    state: restarted
+    enabled: yes

roles/kea/tasks/main.yml

@@ -0,0 +1,43 @@
+---  
+
+- name: Preparation  
+  shell: curl -1sLf 'https://dl.cloudsmith.io/public/isc/kea-2-4/setup.deb.sh' | sudo -E bash
+
+- name: Update apt
+  ansible.builtin.apt:
+    update_cache: yes
+
+- name: Installation paquet isc-kea-common
+  ansible.builtin.apt:
+    deb: isc-kea-common
+    state: present
+
+- name: Installation isc-kea-dhcp4
+  ansible.builtin.apt:
+    name: isc-kea-dhcp4-server
+    state: present
+
+- name: Installation isc-kea-ctrl-agent
+  ansible.builtin.apt:
+    name: isc-kea-ctrl-agent
+    state: present
+
+- name: Installation isc-kea-hooks
+  ansible.builtin.apt:
+    name: isc-kea-hooks
+    state: present
+
+- name: Generation du fichier de configuration kea-ctrl-agent
+  ansible.builtin.copy:
+    src: kea-ctrl-agent.conf.j2
+    dest: /etc/kea/kea-ctrl-agent.conf
+  notify:
+    - Restart isc-kea-ctrl-agent
+
+- name: Generation du fichier de configuration kea-dhcp4.conf
+  ansible.builtin.template:
+    src: kea-dhcp4.conf.j2
+    dest: /etc/kea/kea-dhcp4.conf
+  notify:
+    - Restart isc-kea-dhcp4-server
+

roles/kea/templates/kea-ctrl-agent.conf.j2

@@ -6,7 +6,7 @@
     {
         // We need to specify where the agent should listen to incoming HTTP
         // queries.
-        "http-host": "172.16.64.1",
+        "http-host": "{{ kea_ctrl_address }}",
 
         // This specifies the port CA will listen on.
         "http-port": 8000,
@@ -18,7 +18,7 @@
             {
                 "comment": "socket to DHCPv4 server",
                 "socket-type": "unix",
-                "socket-name": "/tm/kea4-ctrl-socket"
+                "socket-name": "/tmp/kea4-ctrl-socket"
             },
 
             // Location of the DHCPv6 command channel socket.

roles/kea/templates/kea-dhcp4.conf.j2

@@ -22,7 +22,7 @@
         // The DHCPv4 server listens on this interface. When changing this to
         // the actual name of your interface, make sure to also update the
         // interface parameter in the subnet definition below.
-        "interfaces": [ "enp0s8" ]
+        "interfaces": {{ kea_dhcp_interfaces }}
     },
 
     // Control socket is required for communication between the Control
@@ -88,7 +88,7 @@
                 "high-availability": [ {
                     // This parameter points to this server instance. The respective
                     // HA peers must have this parameter set to their own names.
-                    "this-server-name": "kea1",
+                    "this-server-name": "{{ kea_this_server }}",
                     // The HA mode is set to hot-standby. In this mode, the active server handles
                     // all the traffic. The standby takes over if the primary becomes unavailable.
                     "mode": "hot-standby",
@@ -116,24 +116,24 @@
                     "peers": [
                         // This is the configuration of this server instance.
                         {
-                            "name": "kea1",
+                            "name": "{{ kea_srv1 }}",
                             // This specifies the URL of this server instance. The
                             // Control Agent must run along with this DHCPv4 server
                             // instance and the "http-host" and "http-port" must be
                             // set to the corresponding values.
-                            "url": "http://172.16.64.1:8000/",
+                            "url": "http://{{ kea_ctrl_address1 }}:8000/",
                             // This server is primary. The other one must be
                             // secondary.
                             "role": "primary"
                         },
                         // This is the configuration of the secondary server.
                         {
-                            "name": "kea2",
+                            "name": "{{ kea_srv2 }}",
                             // Specifies the URL on which the partner's control
                             // channel can be reached. The Control Agent is required
                             // to run on the partner's machine with "http-host" and
                             // "http-port" values set to the corresponding values.
-                            "url": "http://172.16.64.2:8000/",
+                            "url": "http://{{ kea_ctrl_address2 }}:8000/",
                             // The other server is secondary. This one must be
                             // primary.
                             "role": "standby"
@@ -152,7 +152,7 @@
 
             // There are no relays in this network, so we need to tell Kea that this subnet
             // is reachable directly via the specified interface.
-            "interface": "enp0s8",
+            "interface": "enp0s9",
 
             // Specify a dynamic address pool.
             "pools": [
@@ -171,7 +171,7 @@
                 {
                     // For each IPv4 subnet you typically need to specify at least one router.
                     "name": "routers",
-                    "data": "172.16.64.1"
+                    "data": "172.16.64.254"
                 },
                 {
                     // Using cloudflare or Quad9 is a reasonable option. Change this
@@ -179,7 +179,7 @@
                     // choice is 8.8.8.8, owned by Google. Using third party DNS
                     // service raises some privacy concerns.
                     "name": "domain-name-servers",
-                    "data": "172.16.64.1"
+                    "data": "172.16.0.1"
                 }
             ],
 

roles/nxc-traefik/files/docker-compose.yml

@@ -53,8 +53,8 @@ services:
     image: nextcloud
     container_name: app
     restart: always
-    ports:
+      #ports:
-      - 8081:80
+      #- 8081:80
     #links:
     depends_on:
       - db

roles/wireguard-r/README.md

@@ -24,7 +24,10 @@ bash r-vp1-post.sh
 ```
 ## Sur **r-vp2**:
 
-Lancer le script r-vp2-post.sh pour récuperer le fichier de configuration et activer l'interface wg0.
+Lancer le playbook : *ansible-playbook -i localhost, -c local* r-vp2.yml sur **r-vp2**
+
+Puis lancer le script r-vp2-post.sh pour récuperer le fichier de configuration et activer l'interface wg0.
+
 ### 🛠️ Lancer le script
 ```bash
 cd /tools/ansible/gsb2023/Scripts
@@ -34,7 +37,11 @@ bash r-vp2-post.sh
 ```
 ## Fin
 
-redemarer les machines
+Pour finir redemarer les machines.
 ```bash
 reboot
 ```
+Veuillez maintenant vous rendre dans le dossier du role ferm : 
+*gsb2024/roles/fw-ferm*
+
+*Modification : jm*

roles/zabbix-cli/defaults/main.yml

@@ -1,2 +1,3 @@
 SERVER: "127.0.0.1"
-SERVERACTIVE: "172.16.0.8"
+SERVERACTIVE: "192.168.99.8"
+TOKENAPI: "f72473b7e5402a5247773e456f3709dcdd5e41792360108fc3451bbfeed8eafe"

roles/zabbix-cli/tasks/main.yml

@@ -28,3 +28,11 @@
         state: restarted
         enabled: yes
 
+    - name: mise ne place script hostcreate
+      template:
+        src: hostcreate.sh.j2
+        dest: /tmp/hostcreate.sh
+
+    - name: lancement script hostcreate
+      command: bash /tmp/hostcreate.sh
+

roles/zabbix-cli/templates/hostcreate.sh.j2

@@ -0,0 +1 @@
+curl -X POST -H "Content-Type: application/json" -d '{ "jsonrpc":"2.0","method":"host.create","params": {"host": "{{ ansible_hostname }}","groups": [{"groupid": "6"}],"templates": [{"templateid": "10343"}],"inventory_mode": 0,"inventory": {"type": 0}},"auth": "{{ TOKENAPI }}","id": 1}' http://{{ SERVERACTIVE }}/zabbix/api_jsonrpc.php

s-backup.yml

@@ -7,6 +7,7 @@
     - goss
 #   - proxy3
     - zabbix-cli
+    - gotify
 #   - ssh-cli
     # - syslog-cli
     - smb-backup

s-kea1-ps.yml

@@ -0,0 +1,21 @@
+---
+- hosts: localhost
+  connection: local
+  vars:
+    kea_this_server: "s-kea1"
+    kea_srv1: "s-kea1"
+    kea_srv2: "s-kea2"
+    kea_ctrl_address_this: "172.16.0.20"
+    kea_ctrl_address1: "172.16.0.20"
+    kea_ctrl_address2: "172.16.0.21"
+    kea_dhcp_int: ["enp0s9"]
+
+  roles:
+        - base
+       - goss
+      # - ssh-cli
+    - kea
+      # - zabbix-cli
+      # - journald-snd
+      # - snmp-agent
+          - post

s-lb-web1.yml

@@ -4,6 +4,7 @@
 
   roles:
     - base
+    - goss
     - post-lb
     - lb-web
       # - zabbix-cli

s-lb-web2.yml

@@ -4,6 +4,7 @@
 
   roles:
     - base
+    - goss
     - post-lb
     - lb-web
       # - zabbix-cli

s-nas.yml

@@ -9,6 +9,7 @@
     
   roles:
     - base
+    - goss
       #- zabbix-cli
     - lb-nfs-server
     - ssh-cli

s-nxc.yaml

@@ -0,0 +1,55 @@
+command:
+  ls -l .:
+    exit-status: 0
+    stdout:
+    - total 200
+    - -rwxr-xr-x  1 root root  232 15 janv. 17:38 agoss
+    - -rw-r--r--  1 root root  212 15 janv. 17:38 changelog
+    - drwxr-xr-x  3 root root 4096 15 janv. 17:38 doc
+    - drwxr-xr-x  2 root root 4096 19 janv. 10:50 goss
+    - -rwxr-xr-x  1 root root  209 15 janv. 17:38 gsbchk
+    - -rwxr-xr-x  1 root root 7174 15 janv. 17:38 gsbstart
+    - -rwxr-xr-x  1 root root  728 15 janv. 17:38 gsbstartl
+    - -rw-r--r--  1 root root  289 15 janv. 17:38 lisezmoi.txt
+    - drwxr-xr-x  2 root root 4096 15 janv. 17:38 old
+    - drwxr-xr-x  2 root root 4096 19 janv. 09:16 pre
+    - -rw-r--r--  1 root root  477 19 janv. 09:16 pull-config
+    - -rw-r--r--  1 root root 5070 19 janv. 09:16 README.md
+    - -rw-r--r--  1 root root  141 15 janv. 17:38 r-ext.yml
+    - -rw-r--r--  1 root root  151 15 janv. 17:38 r-int.yml
+    - drwxr-xr-x 55 root root 4096 19 janv. 09:16 roles
+    - -rw-r--r--  1 root root  177 15 janv. 17:38 r-vp1-fw.yml
+    - -rw-r--r--  1 root root  259 15 janv. 17:38 r-vp1.yml
+    - -rw-r--r--  1 root root  173 15 janv. 17:38 r-vp2-fw.yml
+    - -rw-r--r--  1 root root  305 15 janv. 17:38 r-vp2.yml
+    - -rw-r--r--  1 root root  181 19 janv. 09:16 s-adm.yml
+    - -rw-r--r--  1 root root  119 15 janv. 17:38 s-agence.yml
+    - -rw-r--r--  1 root root  166 19 janv. 09:16 s-appli.yml
+    - -rw-r--r--  1 root root  182 19 janv. 09:16 s-backup.yml
+    - drwxr-xr-x  3 root root 4096 19 janv. 09:16 scripts
+    - -rw-r--r--  1 root root  213 15 janv. 17:38 s-docker.yml
+    - -rw-r--r--  1 root root  144 15 janv. 17:38 s-elk.yml
+    - -rw-r--r--  1 root root  178 19 janv. 09:16 s-fog-post.yml
+    - -rw-r--r--  1 root root  162 19 janv. 09:16 s-fog.yml
+    - -rw-r--r--  1 root root  199 19 janv. 09:16 s-infra.yml
+    - -rw-r--r--  1 root root  351 15 janv. 17:38 s-itil.yml
+    - -rw-r--r--  1 root root  185 19 janv. 09:16 s-kea1.yml
+    - -rw-r--r--  1 root root  174 19 janv. 09:16 s-kea2.yml
+    - -rw-r--r--  1 root root  131 19 janv. 09:16 s-lb-bd.yml
+    - -rw-r--r--  1 root root  127 19 janv. 09:16 s-lb-web1.yml
+    - -rw-r--r--  1 root root  127 19 janv. 09:16 s-lb-web2.yml
+    - -rw-r--r--  1 root root  145 19 janv. 09:16 s-lb.yml
+    - -rw-r--r--  1 root root  148 19 janv. 09:16 s-mess.yml
+    - -rw-r--r--  1 root root  241 19 janv. 09:16 s-mon.yml
+    - -rw-r--r--  1 root root  290 19 janv. 09:16 s-nas.yml
+    - -rw-r--r--  1 root root  156 15 janv. 17:38 s-nxc.yml
+    - -rw-r--r--  1 root root  140 15 janv. 17:38 s-peertube.yml
+    - -rw-r--r--  1 root root  148 19 janv. 09:16 s-proxy.yml
+    - -rw-r--r--  1 root root  161 15 janv. 17:38 s-test.yml
+    - drwxr-xr-x  3 root root 4096 15 janv. 17:38 sv
+    - drwxr-xr-x  2 root root 4096 15 janv. 17:38 tests
+    - drwxr-xr-x  2 root root 4096 15 janv. 17:38 vagrant
+    - drwxr-xr-x  2 root root 4096 15 janv. 17:38 windows
+    - drwxr-xr-x  7 root root 4096 19 janv. 09:16 wireguard
+    stderr: []
+    timeout: 10000

wireguard/README.md

@@ -0,0 +1,18 @@
+# **Explication :** 
+
+Le dossier Wireguard comprend tous les tests de ping à effectuer une fois l'installation complète complète de wireguard. 
+
+Les dossiers présent dans ce dossier contiennent les routes qui doivent être présent sur nos différentes machines. Vous pouvez comparer les interface avec un "ip a" en cas de disfonctionnement. 
+
+# **Etapes pour lancer les tests:**
+
+Pour tester le bon fonctionnement du VPN et faire la phase de test, rendez vous sur la machine ou vous voulez faire les tests de ping (nous allons prendre ping-sinfra.sh comme exemple)
+
+* Mettez vous dans le dossier tools/ansible/gsb2024/wireguard
+
+* Lancer le script de s-infra : bash ping-sinfra.sh 
+
+Une fois lancer une série de ping vont se lancer automatiquement, si tout est bon le scipt devrait arrivé à sa fin. 
+Si toutefois un ping ne passe pas, le scipt vaa bloquer sur le ping qui est en cours d'éxécution ! 
+
+*Modification : jm*