compartir documentación con la comisión de cuidados y el coordinador pedagogico #51

Open
opened 2025-06-25 17:09:29 +00:00 by fauno · 7 comments
Owner
No description provided.
fauno added this to the Milestone 1 milestone 2025-06-25 17:09:29 +00:00
fauno added the
prioridad alta
hacer
labels 2025-06-25 17:09:29 +00:00
ChasquiLabo was assigned by fauno 2025-06-25 17:09:29 +00:00
cyborg_yogui was assigned by fauno 2025-06-25 17:09:29 +00:00
l4uZP was assigned by fauno 2025-06-25 17:09:29 +00:00
fauno added the due date 2025-06-26 2025-06-25 17:09:37 +00:00
Author
Owner
https://manuales.yanapak.abyaya.la/s/WuoMoVzaS# https://git.coopcloud.tech/escuela-comun/abyayala/src/branch/master/README.md
ChasquiLabo was unassigned by fauno 2025-07-02 15:13:03 +00:00
l4uZP was unassigned by fauno 2025-07-02 15:13:03 +00:00
Author
Owner
[Documentación del proxy](https://hedgedoc.sutty.abyaya.la/s/Fr_3Fr0W8)
fauno removed the due date 2025-06-26 2025-07-30 15:24:37 +00:00
fauno added
testear
and removed
hacer
labels 2025-07-30 15:24:57 +00:00
Author
Owner

esperando confirmación de las comisiones de cuidados y pedagogia

esperando confirmación de las comisiones de cuidados y pedagogia
Owner
  • Con respecto a la documentación. Aquí están las instrucciones para instalar el "Kit de Herramientas Abya Yala" actualizado a 2025 https://manuales.yanapak.abyaya.la/s/WuoMoVzaS#

  • Las recetas de despliegue se mantienen igual, no hay cambios a partir de integrar Abra a las huertas.

  • Con respecto a la pedagógico ya pueden encontrarlo en el documento oficial de la escuela, bajo la pestaña "huertas digitales"

- Con respecto a la documentación. Aquí están las instrucciones para instalar el "Kit de Herramientas Abya Yala" actualizado a 2025 https://manuales.yanapak.abyaya.la/s/WuoMoVzaS# - Las recetas de despliegue se mantienen igual, no hay cambios a partir de integrar Abra a las huertas. - Con respecto a la pedagógico ya pueden encontrarlo en el documento oficial de la escuela, bajo la pestaña "huertas digitales"
Owner

en seguimiento

en seguimiento
Owner

Dejo una documentacion AI-generada para comparación

Overview

Abyaya.la is an Ansible-based infrastructure automation system that deploys and manages a distributed network
with two main components:

  1. La RAP (Red Autónoma Pirata): A VPN network (10.13.12.1/24) that connects all nodes using Tinc
  2. El PROXY: A public-facing reverse proxy server that routes HTTPS traffic to nodes through the VPN

Common Commands

Main Deployment

# Deploy entire infrastructure to a host
ansible-playbook deploy.yml -e "alt=abyayala host=hetzner"

# Deploy specific service only
ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=vpn"

# Skip installation tasks
ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=nuevo" --skip-tags=installation

Node Management

1. Install RAP on a new node

ansible-playbook --become tasks/rap.yml -e "nodo=nuevo host=miservidora"
- host: target node in inventory
- nodo: node name (must match proxy configuration)

2. User Management

# Add SSH users to proxy
ansible-playbook tasks/users.yml -e "host=hetzner"
- Add public keys to tasks/files/ssh/WAYKI.pub
- Configure in group_vars/all/ssh_users.yml

Local Development

# Install locally for testing
ansible-playbook --become tasks/rap.yml -e "host=localhost nodo=nombrelo" -i hosts.local

# Enable SSH self-connection
cat ~/.ssh/id_ed25519.pub >> ~/.ssh/authorized_keys

Architecture

Infrastructure as Code Pattern

The entire network is defined declaratively in abyayala.yml as a matrix. The deploy.yml playbook reads this
matrix and orchestrates deployment through roles.

Key Files

- deploy.yml: Main orchestration playbook
- abyayala.yml: Declarative infrastructure matrix defining all services and nodes
- hosts.production: Ansible inventory with target hosts
- tasks/: Standalone task playbooks for specific operations
- roles/: Service configuration modules

Matrix Structure in abyayala.yml

Each entry defines either a role-based service or a proxy mapping:

VPN Node Authorization:
- service_name: vpn
  roles:
    - rap
  nodos:
    - marmite
    - ka

Proxy Mapping:
- service_name: nuevo
  domains:
    - nuevo.abyaya.la
  nodo: nuevo.comun
  force_https: yes
  ports:  # Optional
    - 222
  enable_compression: yes  # Optional

Roles Overview

- althost: Docker/Docker Swarm setup, manages docker-compose generation
- rap: Tinc VPN configuration (server and client)
- proxy: Nginx reverse proxy with SSL/TLS
- certbot: Let\'s Encrypt wildcard certificates
- dnsmasq: DNS resolution for VPN hostnames
- knsupdate: Knot DNS dynamic updates
- firewall: Firewall rules configuration
- users: Linux user and SSH key management

Deployment Flow

1. deploy.yml imports the matrix from abyayala.yml
2. althost role installs Docker and prepares compose environment
3. Role-specific tasks execute based on matrix definitions
4. proxy role generates virtual hosts and stream configurations for domains
5. Docker composition published and deployed

Two-Step Node Addition Process

Step 1: Configure node in VPN
1. Add node to nodos list under service_name: vpn in abyayala.yml
2. Run: ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=vpn"
3. Install RAP on node: ansible-playbook --become tasks/rap.yml -e "nodo=nuevo host=miservidora"

Step 2: Enable HTTPS access
1. Add proxy entry in abyayala.yml with domain and nodo mapping
2. Run: ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=nuevo"

Docker Composition Pattern

- Docker Compose files generated dynamically in /tmp/abyayala/
- Services defined through althost role\'s compose templates
- Deployed to /opt/abyayala/ on target hosts
- Full composition for complete deploys, mini composition for single services

Parameters

deploy.yml parameters:
- alt: Autonomous server name (always 'abyayala')
- host: Target server from inventory (required)
- service: Limit to specific service (optional)

Tags:
- installation: Skip with --skip-tags=installation to avoid reinstalling packages
- firewall, proxy, dns, certbot, knot, rap: Target specific components

Testing

- VPN nodes should connect to 10.13.12.1/24 network
- Proxy at 10.13.12.1 should ping nodes by hostname: ping ka.comun
- Services accessible via sub-sub-domains: https://sitio.nuevo.abyaya.la

Installation Prerequisites

# Install Ansible
pip install ansible
# OR
sudo apt-get install ansible

# Generate SSH key
ssh-keygen -t ed25519

# Copy to target
ssh-copy-id root@nuevo.comun
Dejo una documentacion AI-generada para comparación ## Overview Abyaya.la is an Ansible-based infrastructure automation system that deploys and manages a distributed network with two main components: 1. **La RAP (Red Autónoma Pirata)**: A VPN network (10.13.12.1/24) that connects all nodes using Tinc 2. **El PROXY**: A public-facing reverse proxy server that routes HTTPS traffic to nodes through the VPN ## Common Commands ### Main Deployment ```bash # Deploy entire infrastructure to a host ansible-playbook deploy.yml -e "alt=abyayala host=hetzner" # Deploy specific service only ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=vpn" # Skip installation tasks ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=nuevo" --skip-tags=installation Node Management 1. Install RAP on a new node ansible-playbook --become tasks/rap.yml -e "nodo=nuevo host=miservidora" - host: target node in inventory - nodo: node name (must match proxy configuration) 2. User Management # Add SSH users to proxy ansible-playbook tasks/users.yml -e "host=hetzner" - Add public keys to tasks/files/ssh/WAYKI.pub - Configure in group_vars/all/ssh_users.yml Local Development # Install locally for testing ansible-playbook --become tasks/rap.yml -e "host=localhost nodo=nombrelo" -i hosts.local # Enable SSH self-connection cat ~/.ssh/id_ed25519.pub >> ~/.ssh/authorized_keys Architecture Infrastructure as Code Pattern The entire network is defined declaratively in abyayala.yml as a matrix. The deploy.yml playbook reads this matrix and orchestrates deployment through roles. Key Files - deploy.yml: Main orchestration playbook - abyayala.yml: Declarative infrastructure matrix defining all services and nodes - hosts.production: Ansible inventory with target hosts - tasks/: Standalone task playbooks for specific operations - roles/: Service configuration modules Matrix Structure in abyayala.yml Each entry defines either a role-based service or a proxy mapping: VPN Node Authorization: - service_name: vpn roles: - rap nodos: - marmite - ka Proxy Mapping: - service_name: nuevo domains: - nuevo.abyaya.la nodo: nuevo.comun force_https: yes ports: # Optional - 222 enable_compression: yes # Optional Roles Overview - althost: Docker/Docker Swarm setup, manages docker-compose generation - rap: Tinc VPN configuration (server and client) - proxy: Nginx reverse proxy with SSL/TLS - certbot: Let\'s Encrypt wildcard certificates - dnsmasq: DNS resolution for VPN hostnames - knsupdate: Knot DNS dynamic updates - firewall: Firewall rules configuration - users: Linux user and SSH key management Deployment Flow 1. deploy.yml imports the matrix from abyayala.yml 2. althost role installs Docker and prepares compose environment 3. Role-specific tasks execute based on matrix definitions 4. proxy role generates virtual hosts and stream configurations for domains 5. Docker composition published and deployed Two-Step Node Addition Process Step 1: Configure node in VPN 1. Add node to nodos list under service_name: vpn in abyayala.yml 2. Run: ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=vpn" 3. Install RAP on node: ansible-playbook --become tasks/rap.yml -e "nodo=nuevo host=miservidora" Step 2: Enable HTTPS access 1. Add proxy entry in abyayala.yml with domain and nodo mapping 2. Run: ansible-playbook deploy.yml -e "alt=abyayala host=hetzner service=nuevo" Docker Composition Pattern - Docker Compose files generated dynamically in /tmp/abyayala/ - Services defined through althost role\'s compose templates - Deployed to /opt/abyayala/ on target hosts - Full composition for complete deploys, mini composition for single services Parameters deploy.yml parameters: - alt: Autonomous server name (always 'abyayala') - host: Target server from inventory (required) - service: Limit to specific service (optional) Tags: - installation: Skip with --skip-tags=installation to avoid reinstalling packages - firewall, proxy, dns, certbot, knot, rap: Target specific components Testing - VPN nodes should connect to 10.13.12.1/24 network - Proxy at 10.13.12.1 should ping nodes by hostname: ping ka.comun - Services accessible via sub-sub-domains: https://sitio.nuevo.abyaya.la Installation Prerequisites # Install Ansible pip install ansible # OR sudo apt-get install ansible # Generate SSH key ssh-keygen -t ed25519 # Copy to target ssh-copy-id root@nuevo.comun
Owner
  • Con respecto a la documentación. Aquí están las instrucciones para instalar el "Kit de Herramientas Abya Yala" actualizado a 2025 https://manuales.yanapak.abyaya.la/s/WuoMoVzaS#

  • Las recetas de despliegue se mantienen igual, no hay cambios a partir de integrar Abra a las huertas.

  • Con respecto a la pedagógico ya pueden encontrarlo en el documento oficial de la escuela, bajo la pestaña "huertas digitales"

Acá adjunto algunas propuestas a corregir en la documentación:

> - Con respecto a la documentación. Aquí están las instrucciones para instalar el "Kit de Herramientas Abya Yala" actualizado a 2025 https://manuales.yanapak.abyaya.la/s/WuoMoVzaS# > > - Las recetas de despliegue se mantienen igual, no hay cambios a partir de integrar Abra a las huertas. > > - Con respecto a la pedagógico ya pueden encontrarlo en el documento oficial de la escuela, bajo la pestaña "huertas digitales" Acá adjunto algunas propuestas a corregir en la documentación:
Sign in to join this conversation.
No description provided.