feat: changed the way peertube role is handled

roles/fw-ferm/files/ferm.conf.r-vp1

@@ -35,23 +35,22 @@ table filter {
             proto (udp tcp) dport domain ACCEPT;
             proto udp dport bootps ACCEPT;
         }
-
         # interface réseau
-        interface $DEV_WORLD {
-
-        }
 
         # the rest is dropped by the above policy
     }#FIN INPUT
 
     # outgoing connections are not limited
-    chain OUTPUT {policy ACCEPT;
+    chain OUTPUT {
+        policy ACCEPT;
+#	interface $DEV_VPN proto ssh dport 22 ACCEPT;
+
     }#FIN OUTPUT
 
     chain FORWARD {
         policy ACCEPT;
+
         proto icmp icmp-type echo-request ACCEPT;
-        }
         # connection tracking
         mod state state INVALID DROP;
         mod state state (ESTABLISHED RELATED) ACCEPT;

roles/peertube-k3s/tasks/main.yml

@@ -0,0 +1,23 @@
+---
+  - name: mise a jour de resolv.conf...
+    copy:
+      src: /root/tools/ansible/gsb2023/roles/peertube/files/resolv.conf
+      dest: /etc/
+      mode: '0644'
+        
+  - name: installation de docker...
+    shell: curl https://releases.rancher.com/install-docker/20.10.sh | sh
+
+  - name: attente de l'installation...
+    wait_for:
+      timeout: 30
+      host: localhost
+
+  - name: installation de k3s...
+    shell: curl -sfL https://get.k3s.io | sh -s - --docker
+
+  - name: mise a jour de resolv.conf...
+    copy:
+      src: /root/tools/ansible/gsb2023/roles/peertube/files/resolv.conf
+      dest: /etc/
+      mode: '0644'

roles/peertube/files/resolv.conf

@@ -0,0 +1 @@
+nameserver 192.168.99.99

roles/peertube/files/values.yaml

@@ -71,7 +71,7 @@ mail:
   enbled: true
   config:
     general:
-      ALLOWED_SENDER_DOMAINS: # should be the same as your web domain
+      ALLOWED_SENDER_DOMAINS: "yes" 
       DKIM_AUTOGENERATE: "yes"
     opendkim:
       RequireSafeKeys: "no"

roles/peertube/tasks/main.yml

@@ -1,10 +1,4 @@
 ---
-  - name: installation de docker...
-    shell: curl https://releases.rancher.com/install-docker/20.10.sh | sh
-
-  - name: installation de k3s...
-    shell: curl -sfL https://get.k3s.io | sh -s - --docker
-
   - name: création du répertoire du dépot peertube...
     file:
       path: /root/tools/peertube
@@ -16,6 +10,7 @@
       repo: https://github.com/Elam-Monnot/Peertube-helm.git
       dest: /root/tools/peertube
       clone: yes
+      force: yes
 
   - name: copie de values.yaml...
     copy:
@@ -27,4 +22,10 @@
     shell: curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
 
   - name: installation de peertube...
-    shell: helm repo add https://charts.bitnami.com/bitnami && helm repo add https://bokysan.github.io/docker-postfix && helm dependency build /root/tools/peertube/helm/ && helm install --create-namesapce -n peertube peertube-gsb /root/tools/peertube/helm
+    shell: helm repo add postgresql https://charts.bitnami.com/bitnami && helm repo add redis https://charts.bitnami.com/bitnami && helm repo add mail https://bokysan.github.io/docker-postfix
+
+  - name: exposition du cluster...
+    shell: export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
+
+  - name: lancement du helm chart peertube...
+    shell: helm install --create-namespace -n peertube peertube-gsb /root/tools/peertube/helm

roles/post/files/interfaces.s-peertube

@@ -14,4 +14,4 @@ iface enp0s3 inet static
 allow-hotplug enp0s8
 iface enp0s8 inet static
         address 192.168.100.20/24
-	post-up systemctl start k3s
+	post-up systemctl start k3s && sleep 20 && export KUBECONFIG=/etc/rancher/k3s/k3s.yaml

s-peertube.yml

@@ -4,7 +4,8 @@
 
   roles:
     - base
-    - peertube
     - post
     - snmp-agent
     - ssh-cli
+    - peertube-k3s
+    - peertube

scripts/r-vp2-post.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 #recuperation du fichier de config
-wget http://r-vp1.gsb.adm:8800/wg0-b.conf
+wget http://r-vp1.gsb.adm:8000/wg0-b.conf
 #renomage fichier et mv
 mv ./wg0-b.conf /etc/wireguard/wg0.conf
 #activation interface wg0