Main Page: Difference between revisions

From Essential
Jump to navigation Jump to search
 
(214 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[File:Ynotopec elementary particles motion interaction science 4f947bd8-3a57-49f5-a5b5-df3128737f22.png|thumb|right]]
[[File:Infocepo-picture.png|thumb|right|Discover cloud and AI on infocepo.com]]
Welcome to my WIKI.


It explores cloud computing, focusing on migration, infrastructure, and high availability. It discusses tools like Kubernetes, OpenStack, AWS, emphasizes open-source software, and outlines key factors for cloud infrastructure implementation.
= infocepo.com – Cloud, AI & Labs =


<br>
Welcome to the '''infocepo.com''' portal.
== AI Solutions ==
*[https://chrome.google.com/webstore/detail/webchatgpt-chatgpt-with-i/lpfemeioodjbpieminkklglpmhlngfc Science Research Tool] - AI for science.
*[https://www.midjourney.comDesign Platform] - AI-powered design.


=== Next Steps ===
This wiki is intended for system administrators, cloud engineers, developers, students, and enthusiasts who want to:


*[https://python.langchain.com LANGCHAIN] - Upcoming semantic tool.
* Understand modern architectures (Kubernetes, OpenStack, bare-metal, HPC…)
*[https://chat.lmsys.org/ VICUNA (LLAMA)] - Open-source AI chat.
* Deploy private AI assistants and productivity tools
* Build hands-on labs to learn by doing
* Prepare large-scale audits, migrations, and automations


=== POCs ===
The goal: turn theory into '''reusable scripts, diagrams, and architectures'''.


*AUDIO - Real-time translation.
__TOC__
*[https://github.com/Significant-Gravitas/Auto-GPT Auto-GPT] - AI for coding.
*[https://openai.com OpenAI's AI Tools] - Industry-transforming AI.
*[https://lmsys.org/blog/2023-05-03-arena Benchmark] - AI performance standard.
*PICTURE - NVIDIA NeuralCompressionTechnic compression.
*[https://huggingface.co/models HuggingFace] - AI models.


== CLOUD LAB ==
----
[[file:Infocepo.drawio.png]]
<br><br>
Presenting my [[LAB project]].


== Infrastructure Audit ==
= Getting started quickly =
Created [[ServerDiff.sh]] for server audits. Enables configuration drift tracking and environment consistency checks.


== Cloud Migration Example ==
== Recommended paths ==
[[File:Diagram-migration-ORACLE-KVM-v2.drawio.png|thumb|right]]
*1.5d: Infrastructure audit of 82 services ([https://infocepo.com/wiki/index.php/ServerDiff.sh ServerDiff.sh])


*1.5d: Create cloud architecture diagram
; 1. Build a private AI assistant
* Deploy a typical stack: '''Open WebUI + Ollama + GPU''' (H100 or consumer-grade GPU)
* Add a chat model and a summarization model
* Integrate internal data (RAG, embeddings)


*1.5d: Compliance check of 2 clouds (6 hypervisors, 6TB memory)
; 2. Launch a Cloud lab
* Create a small cluster (Kubernetes, OpenStack, or bare-metal)
* Set up a deployment pipeline (Helm, Ansible, Terraform…)
* Add an AI service (transcription, summarization, chatbot…)


*1d: Cloud installations
; 3. Prepare an audit / migration
* Inventory servers with '''ServerDiff.sh'''
* Design the target architecture (cloud diagrams)
* Automate the migration with reproducible scripts


*.5d: Stability check
== Content overview ==


*1.5d: Cloud automation study
* '''AI guides & tools''' : assistants, models, evaluations, GPUs
* '''Cloud & infrastructure''' : HA, HPC, web-scale, DevSecOps
* '''Labs & scripts''' : audit, migration, automation
* '''Comparison tables''' : Kubernetes vs OpenStack vs AWS vs bare-metal, etc.


*1.5d: Develop 6 templates (2 clouds, 2 OS, 8 environments, 2 versions)
----


*1d: Create migration diagram
= future =
[[File:Automation-full-vs-humans.png|thumb|right|The world after automation]]


*1.5d: Write 138 lines of migration code ([https://infocepo.com/wiki/index.php/MigrationApp.sh MigrationApp.sh])
= AI Assistants & Cloud Tools =


*1.5d: Process stabilization
== AI Assistants ==


*1.5d: Cloud vs old infrastructure benchmark
; '''ChatGPT'''
* https://chatgpt.com ChatGPT – Public conversational assistant, suited for exploration, writing, and rapid experimentation.


*.5d: Unavailability time calibration per migration unit
; '''Self-hosted AI assistants'''
* https://github.com/open-webui/open-webui Open WebUI + https://www.scaleway.com/en/h100-pcie-try-it-now/ H100 GPU + https://ollama.com Ollama 
: Typical stack for private assistants, self-hosted LLMs, and OpenAI-compatible APIs.
* https://github.com/ynotopec/summarize Private summary – Local, fast, offline summarizer for your own data.


*5min: Load 82 VMs (env, os, application_code, 2 IP)
== Development, models & tracking ==


Total = 15 man-days
; '''Discovering and tracking models'''
* https://ollama.com/library LLM Trending – Model library (chat, code, RAG…) for local deployment.
* https://huggingface.co/models Models Trending – Model marketplace, filterable by task, size, and license.
* https://huggingface.co/models?pipeline_tag=image-text-to-text&sort=trending Img2txt Trending – Vision-language models (image → text).
* https://huggingface.co/spaces/TIGER-Lab/GenAI-Arena Txt2img Evaluation – Image generation model comparisons.


{| style="border-spacing:0;width:18.12cm;"
; '''Evaluation & benchmarks'''
|- style="background-color:#ffc000;border:0.05pt solid #000000;padding:0.049cm;"
* https://lmarena.ai/leaderboard ChatBot Evaluation – Chatbot rankings (open-source and proprietary models).
| align=center style="color:#000000;" | '''ACTION'''
* https://huggingface.co/spaces/mteb/leaderboard Embedding Leaderboard – Benchmark of embedding models for RAG and semantic search.
| align=center style="color:#000000;" | '''RESULT'''
* https://ann-benchmarks.com Vectors DB Ranking – Vector database comparison (latency, memory, features).
| align=center style="color:#000000;" | '''OK/KO'''
* https://top500.org/lists/green500/ HPC Efficiency – Ranking of the most energy-efficient supercomputers.
 
; '''Development & fine-tuning tools'''
* https://github.com/search?q=stars%3A%3E15000+forks%3A%3E1500+created%3A%3E2022-06-01&type=repositories&s=updated&o=desc Project Trending – Major recent open-source projects, sorted by popularity and activity.
* https://github.com/hiyouga/LLaMA-Factory LLM Fine Tuning – Advanced framework for LLM fine-tuning (instruction tuning, LoRA, etc.).
* https://www.perplexity.ai Perplexity AI – Advanced research and synthesis oriented as a “research copilot”.
 
== AI Hardware & GPUs ==
 
; '''GPUs & accelerators'''
* https://www.nvidia.com/en-us/data-center/h100/ NVIDIA H100 – Datacenter GPU for Kubernetes clusters and intensive AI workloads.
* NVIDIA 5080 – Consumer GPU for lower-cost private LLM deployments.
* https://www.mouser.fr/ProductDetail/BittWare/RS-GQ-GC1-0109?qs=ST9lo4GX8V2eGrFMeVQmFw%3D%3D GROQ LLM accelerator – Hardware accelerator dedicated to LLM inference.
 
----
 
= Open models & internal endpoints =
 
''(Last update: 2026-02-13)''
 
The models below correspond to '''logical endpoints''' (for example via a proxy or gateway), selected for specific use cases.
 
{| class="wikitable"
! Endpoint !! Description / Primary use case
|-
|-
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | Activate maintenance for n/2-1 nodes or 1 node if 2 nodes.
| '''ai-chat''' || Based on '''gpt-oss-20b''' – General-purpose chat, good cost / quality balance.
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | All resources are started.
| style="background-color:#d8e4bc;border:0.05pt solid #000000;padding:0.049cm;color:#000000;" |
|-
|-
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | Un-maintenance all nodes. Power off n/2-1 nodes or 1 node if 2 nodes, different from the previous test.
| '''ai-translate''' || gpt-oss-20b, temperature = 0 – Deterministic, reproducible translation (FR, EN, other languages).
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | All resources are started.
| style="background-color:#d8e4bc;border:0.05pt solid #000000;padding:0.049cm;color:#000000;" |
|-
|-
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | Power off simultaneous all nodes. Power on simultaneous all nodes.
| '''ai-summary''' || qwen3 – Model optimized for summarizing long texts (reports, documents, transcriptions).
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | All resources are started.
| style="background-color:#d8e4bc;border:0.05pt solid #000000;padding:0.049cm;color:#000000;" |
|-
|-
| '''ai-code''' || gpt-oss-20b – Code reasoning, explanation, and refactoring.
|-
| '''ai-code-completion''' || gpt-oss-20b – Fast code completion, designed for IDE auto-completion.
|-
| '''ai-parse''' || qwen3 – Structured extraction, log / JSON / table parsing.
|-
| '''ai-RAG-FR''' || qwen3 – RAG usage in French (business knowledge, internal FAQs).
|-
| '''gpt-oss-20b''' || Agentic tasks.
|}
|}


== Cloud Enhancement ==
Usage idea: each endpoint is associated with one or more labs (chat, summary, parsing, RAG, etc.) in the Cloud Lab section.
[[File:WebModelDiagram.drawio.png|thumb|right]]
 
----
 
= News & Trends =
 
* https://www.youtube.com/@lev-selector/videos Top AI News – Curated AI news videos.
* https://betterprogramming.pub/color-your-captions-streamlining-live-transcriptions-with-diart-and-openais-whisper-6203350234ef Real-time transcription with Diart + Whisper – Example of real-time transcription with speaker detection.
* https://github.com/openai-translator/openai-translator OpenAI Translator – Modern extension / client for LLM-assisted translation.
* https://opensearch.org/docs/latest/search-plugins/conversational-search Opensearch with LLM – Conversational search based on LLMs and OpenSearch.
 
----
 
= Training & Learning =
 
* https://www.youtube.com/watch?v=4Bdc55j80l8 Transformers Explained – Introduction to Transformers, the core architecture of LLMs.
* Hands-on labs, scripts, and real-world feedback in the [[LAB project|CLOUD LAB]] project below.
 
----
 
= Cloud Lab & Audit Projects =
 
[[File:Infocepo.drawio.png|400px|Cloud Lab reference diagram]]
 
The '''Cloud Lab''' provides reproducible scenarios: infrastructure audits, cloud migration, automation, high availability.
 
== Audit project – Cloud Audit ==
 
; '''[[ServerDiff.sh]]'''
Bash audit script to:


* Formalize infrastructure for flexibility and reduced complexity.
* detect configuration drift,
* Utilize customer-location tracking name server like GDNS.
* compare multiple environments,
* Use minimal instances with a network load balancer like LVS.
* prepare a migration or remediation plan.
* Compare prices of dynamic computing services, beware of tech lock-in.
* Employ efficient frontend TLS decoder like HAPROXY.
* Opt for fast HTTP cache like VARNISH and Apache Traffic Server for large files.
* Use REVERSE PROXY with TLS decoder like ENVOY for service compatibility.
* Consider serverless service for standard runtimes, mindful of potential incompatibilities.
* Employ load balancing or native services for dynamic computing power.
* Use open source STACKs where possible.
* Employ database caches like MEMCACHED.
* More information at [https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure CLOUD WIKIPEDIA].


== CLOUD WIKIPEDIA ==
== Example of Cloud migration ==
* [https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure CLOUD WIKIPEDIA]
 
[[File:Diagram-migration-ORACLE-KVM-v2.drawio.png|400px|Cloud migration diagram]]
 
Example: migration of virtual environments to a modernized cloud, including audit, architecture design, and automation.


== CLOUD vs HW ==
{| class="wikitable"
{| class="wikitable"
! Task !! Description !! Duration (days)
|-
|-
!Function
| Infrastructure audit || 82 services, automated audit via '''ServerDiff.sh''' || 1.5
!KUBERNETES
!OPENSTACK
!AWS
!Bare-metal
!HPC
!CRM
!OVIRT
|-
|-
|DEPLOY
| Cloud architecture diagram || Visual design and documentation || 1.5
|HELM/YAML/OPERATOR/ANSIBLE/JUJU
|ANSIBLE+PACKER+TERRAFORM/JUJU
|ANSIBLE/TERRAFORM/CLOUDFORMATION/JUJU
|ANSIBLE/SH
|XCAT/CLUSH
|ANSIBLE/SH
|ANSIBLE/PYTHON/SH
|-
|-
|BOOTSTRAP
| Compliance checks || 2 clouds, 6 hypervisors, 6 TB of RAM || 1.5
|API
|API/PXE
|API
|PXE/IPMI
|PXE/IPMI
|PXE/IPMI
|PXE/API
|-
|-
|Router (control)
| Cloud platform installation || Deployment of main target environments || 1.0
|API (Kube-router)
|API (Router/Subnet)
|API (Route table/Subnet)
|LINUX/OVS/external
|XCAT/external
|LINUX/external
|API
|-
|-
|Firewall (control)
| Stability verification || Early functional tests || 0.5
|INGRESS/EGRESS/ISTIO/NETWORKPOLICY
|API (Security groups)
|API (Security group)
|LINUX
|LINUX
|LINUX
|API
|-
|-
|Vlan/Vxlan
| Automation study || Identification and automation of repetitive tasks || 1.5
|many
|VPC
|VPC
|OVS/LINUX/external
|XCAT/external
|LINUX/external
|API
|-
|-
|Name server (control)
| Template development || 6 templates, 8 environments, 2 clouds / OS || 1.5
|coredns
|dns-nameserver
|Amazon Route 53
|GDNS
|XCAT
|LINUX/external
|API/external
|-
|-
|Load balancer
| Migration diagram || Illustration of the migration process || 1.0
|kube-proxy/LVS(IPVS)
|LVS
|Network Load Balancer
|LVS
|SLURM
|Ldirectord
|
|-
|-
|Storage
| Migration code writing || 138 lines (see '''MigrationApp.sh''') || 1.5
|many
|-
|SWIFT/CINDER/NOVA
| Process stabilization || Validation that migration is reproducible || 1.5
|S3/EFS/FSX/EBS
|-
|SWIFT/XFS/EXT4/RAID10
| Cloud benchmarking || Performance comparison vs legacy infrastructure || 1.5
|GPFS
|-
|SAN
| Downtime tuning || Calculation of outage time per migration || 0.5
|NFS/SAN
|-
| VM loading || 82 VMs: OS, code, 2 IPs per VM || 0.1
|-
! colspan=2 align="right"| '''Total''' !! 15 person-days
|}
|}


== CLOUD providers ==
=== Stability checks (minimal HA) ===
* [https://cloud.google.com/free/docs/aws-azure-gcp-service-comparison CLOUD providers]
 
== CLOUD INTERNET NETWORK ==
{| class="wikitable"
* [https://global-internet-map-2021.telegeography.com/ CLOUD INTERNET NETWORK]
! Action !! Expected result
== CLOUD NATIVE ==
|-
* [https://landscape.cncf.io/?fullscreen=yes CLOUD NATIVE]
| Shutdown of one node || All services must automatically restart on remaining nodes.
== High Availability (HA) with Corosync+Pacemaker ==
|-
[[File:HA-REF.drawio.png|thumb|right]]
| Simultaneous shutdown / restart of all nodes || All services must recover correctly after reboot.
|}
 
----
 
= Web Architecture & Best Practices =
 
[[File:WebModelDiagram.drawio.png|400px|Reference web architecture]]
 
Principles for designing scalable and portable web architectures:
 
* Favor '''simple, modular, and flexible''' infrastructure.
* Follow client location (GDNS or equivalent) to bring content closer.
* Use network load balancers (LVS, IPVS) for scalability.
* Systematically compare costs and beware of '''vendor lock-in'''.
* TLS:
** HAProxy for fast frontends,
** Envoy for compatibility and advanced use cases (mTLS, HTTP/2/3).
* Caching:
** Varnish, Apache Traffic Server for large content volumes.
* Favor open-source stacks and database caches (e.g., Memcached).
* Use message queues, buffers, and quotas to smooth traffic spikes.
* For complete architectures:
** https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure Wikimedia Cloud Architecture
** https://github.com/systemdesign42/system-design System Design GitHub
 
----
 
= Comparison of major Cloud platforms =
 
{| class="wikitable"
! Feature !! Kubernetes !! OpenStack !! AWS !! Bare-metal !! HPC !! CRM !! oVirt
|-
| '''Deployment tools''' || Helm, YAML, ArgoCD, Juju || Ansible, Terraform, Juju || CloudFormation, Terraform, Juju || Ansible, Shell || xCAT, Clush || Ansible, Shell || Ansible, Python
|-
| '''Bootstrap method''' || API || API, PXE || API || PXE, IPMI || PXE, IPMI || PXE, IPMI || PXE, API
|-
| '''Router control''' || Kube-router || Router/Subnet API || Route Table / Subnet API || Linux, OVS || xCAT || Linux || API
|-
| '''Firewall control''' || Istio, NetworkPolicy || Security Groups API || Security Group API || Linux firewall || Linux firewall || Linux firewall || API
|-
| '''Network virtualization''' || VLAN, VxLAN, others || VPC || VPC || OVS, Linux || xCAT || Linux || API
|-
| '''DNS''' || CoreDNS || DNS-Nameserver || Route 53 || GDNS || xCAT || Linux || API
|-
| '''Load Balancer''' || Kube-proxy, LVS || LVS || Network Load Balancer || LVS || SLURM || Ldirectord || N/A
|-
| '''Storage options''' || Local, Cloud, PVC || Swift, Cinder, Nova || S3, EFS, EBS, FSx || Swift, XFS, EXT4, RAID10 || GPFS || SAN || NFS, SAN
|}
 
This table serves as a starting point for choosing the right stack based on:
 
* Desired level of control (API vs bare-metal),
* Context (on-prem, public cloud, HPC, CRM…),
* Existing automation tooling.
 
----
 
= Useful Cloud & IT links =
 
* https://cloud.google.com/free/docs/aws-azure-gcp-service-comparison Cloud Providers Compared – AWS / Azure / GCP service mapping.
* https://global-internet-map-2021.telegeography.com/ Global Internet Topology Map – Global Internet mapping.
* https://landscape.cncf.io/?fullscreen=yes CNCF Official Landscape – Overview of cloud-native projects (CNCF).
* https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure Wikimedia Cloud Wiki – Wikimedia infrastructure, real large-scale example.
* https://openapm.io OpenAPM – SRE Tools – APM / observability tooling.
* https://access.redhat.com/downloads/content/package-browser RedHat Package Browser – Package and version search at Red Hat.
* https://www.silkhom.com/barometre-2021-des-tjm-dans-informatique-digital Barometer of IT freelance daily rates.
* https://www.glassdoor.fr/salaire/Hays-Salaires-E10166.htm IT Salaries (Glassdoor) – Salary indicators.
 
----
 
= Advanced: High Availability, HPC & DevSecOps =
 
== High Availability with Corosync & Pacemaker ==
 
[[File:HA-REF.drawio.png|400px|HA cluster architecture]]
 
Basic principles:
 
* Multi-node or multi-site clusters for redundancy.
* Use of IPMI for fencing, provisioning via PXE/NTP/DNS/TFTP.
* For a 2-node cluster:
  – carefully sequence fencing to avoid split-brain,
  – 3 or more nodes remain recommended for production.
 
=== Common resource patterns ===
 
* Multipath storage, LUNs, LVM, NFS.
* User resources and application processes.
* Virtual IPs, DNS records, network listeners.
 
== HPC ==
 
[[File:HPC.drawio.png|400px|Overview of an HPC cluster]]
 
* Job orchestration (SLURM or equivalent).
* High-performance shared storage (GPFS, Lustre…).
* Possible integration with AI workloads (large-scale training, GPU inference).
 
== DevSecOps ==
 
[[File:DSO-POC-V3.drawio.png|400px|DevSecOps reference design]]
 
* CI/CD pipelines with built-in security checks (linting, SAST, DAST, SBOM).
* Observability (logs, metrics, traces) integrated from design time.
* Automated vulnerability scanning, secret management, policy-as-code.
 
----


=== Typical Architecture ===
= About & Contributions =


*Dual-room.
For more examples, scripts, diagrams, and feedback, see:
*IPMI LAN (fencing).
*NTP, DNS+DHCP+PXE+TFTP+HTTP (auto-provisioning), PROXY (updates or internal REPOSITORY).
*Choose 2+ node clusters.
*For 2-node, require COROSYNC 2-node config, 10-second staggered closing for stability.
*Stateless resources. Allocate 4GB/base for DB resources. CPU resource requirements generally low.


=== Typical Service Pattern ===
* https://infocepo.com infocepo.com
*Multipath
*LUN
*LVM (LVM resource)
*FS (FS resource)
*NFS (FS resource)
*User
*IP (IP resource)
*DNS name
*Process (Process resource)
*Listener (Listener resource)


== IT salaries ==
Suggestions for corrections, diagram improvements, or new labs are welcome.
*[http://jobsearchtech.about.com/od/educationfortechcareers/tp/HighestCerts.htm Best IT certifications]
This wiki aims to remain a '''living laboratory''' for AI, cloud, and automation.
*[https://www.silkhom.com/barometre-2021-des-tjm-dans-informatique-digital/ FREELANCE]
*[http://www.journaldunet.com/solutions/emploi-rh/salaire-dans-l-informatique-hays/ IT]
== SRE ==
* [https://openapm.io SRE]
== REDHAT package browser ==
* [https://access.redhat.com/downloads/content/package-browser REDHAT package browser]

Latest revision as of 01:24, 13 February 2026

Discover cloud and AI on infocepo.com

infocepo.com – Cloud, AI & Labs

Welcome to the infocepo.com portal.

This wiki is intended for system administrators, cloud engineers, developers, students, and enthusiasts who want to:

  • Understand modern architectures (Kubernetes, OpenStack, bare-metal, HPC…)
  • Deploy private AI assistants and productivity tools
  • Build hands-on labs to learn by doing
  • Prepare large-scale audits, migrations, and automations

The goal: turn theory into reusable scripts, diagrams, and architectures.


Getting started quickly

Recommended paths

1. Build a private AI assistant
  • Deploy a typical stack: Open WebUI + Ollama + GPU (H100 or consumer-grade GPU)
  • Add a chat model and a summarization model
  • Integrate internal data (RAG, embeddings)
2. Launch a Cloud lab
  • Create a small cluster (Kubernetes, OpenStack, or bare-metal)
  • Set up a deployment pipeline (Helm, Ansible, Terraform…)
  • Add an AI service (transcription, summarization, chatbot…)
3. Prepare an audit / migration
  • Inventory servers with ServerDiff.sh
  • Design the target architecture (cloud diagrams)
  • Automate the migration with reproducible scripts

Content overview

  • AI guides & tools : assistants, models, evaluations, GPUs
  • Cloud & infrastructure : HA, HPC, web-scale, DevSecOps
  • Labs & scripts : audit, migration, automation
  • Comparison tables : Kubernetes vs OpenStack vs AWS vs bare-metal, etc.

future

The world after automation

AI Assistants & Cloud Tools

AI Assistants

ChatGPT
  • https://chatgpt.com ChatGPT – Public conversational assistant, suited for exploration, writing, and rapid experimentation.
Self-hosted AI assistants
Typical stack for private assistants, self-hosted LLMs, and OpenAI-compatible APIs.

Development, models & tracking

Discovering and tracking models
Evaluation & benchmarks
Development & fine-tuning tools

AI Hardware & GPUs

GPUs & accelerators

Open models & internal endpoints

(Last update: 2026-02-13)

The models below correspond to logical endpoints (for example via a proxy or gateway), selected for specific use cases.

Endpoint Description / Primary use case
ai-chat Based on gpt-oss-20b – General-purpose chat, good cost / quality balance.
ai-translate gpt-oss-20b, temperature = 0 – Deterministic, reproducible translation (FR, EN, other languages).
ai-summary qwen3 – Model optimized for summarizing long texts (reports, documents, transcriptions).
ai-code gpt-oss-20b – Code reasoning, explanation, and refactoring.
ai-code-completion gpt-oss-20b – Fast code completion, designed for IDE auto-completion.
ai-parse qwen3 – Structured extraction, log / JSON / table parsing.
ai-RAG-FR qwen3 – RAG usage in French (business knowledge, internal FAQs).
gpt-oss-20b Agentic tasks.

Usage idea: each endpoint is associated with one or more labs (chat, summary, parsing, RAG, etc.) in the Cloud Lab section.


News & Trends


Training & Learning


Cloud Lab & Audit Projects

Cloud Lab reference diagram

The Cloud Lab provides reproducible scenarios: infrastructure audits, cloud migration, automation, high availability.

Audit project – Cloud Audit

ServerDiff.sh

Bash audit script to:

  • detect configuration drift,
  • compare multiple environments,
  • prepare a migration or remediation plan.

Example of Cloud migration

Cloud migration diagram

Example: migration of virtual environments to a modernized cloud, including audit, architecture design, and automation.

Task Description Duration (days)
Infrastructure audit 82 services, automated audit via ServerDiff.sh 1.5
Cloud architecture diagram Visual design and documentation 1.5
Compliance checks 2 clouds, 6 hypervisors, 6 TB of RAM 1.5
Cloud platform installation Deployment of main target environments 1.0
Stability verification Early functional tests 0.5
Automation study Identification and automation of repetitive tasks 1.5
Template development 6 templates, 8 environments, 2 clouds / OS 1.5
Migration diagram Illustration of the migration process 1.0
Migration code writing 138 lines (see MigrationApp.sh) 1.5
Process stabilization Validation that migration is reproducible 1.5
Cloud benchmarking Performance comparison vs legacy infrastructure 1.5
Downtime tuning Calculation of outage time per migration 0.5
VM loading 82 VMs: OS, code, 2 IPs per VM 0.1
Total 15 person-days

Stability checks (minimal HA)

Action Expected result
Shutdown of one node All services must automatically restart on remaining nodes.
Simultaneous shutdown / restart of all nodes All services must recover correctly after reboot.

Web Architecture & Best Practices

Reference web architecture

Principles for designing scalable and portable web architectures:

  • Favor simple, modular, and flexible infrastructure.
  • Follow client location (GDNS or equivalent) to bring content closer.
  • Use network load balancers (LVS, IPVS) for scalability.
  • Systematically compare costs and beware of vendor lock-in.
  • TLS:
    • HAProxy for fast frontends,
    • Envoy for compatibility and advanced use cases (mTLS, HTTP/2/3).
  • Caching:
    • Varnish, Apache Traffic Server for large content volumes.
  • Favor open-source stacks and database caches (e.g., Memcached).
  • Use message queues, buffers, and quotas to smooth traffic spikes.
  • For complete architectures:

Comparison of major Cloud platforms

Feature Kubernetes OpenStack AWS Bare-metal HPC CRM oVirt
Deployment tools Helm, YAML, ArgoCD, Juju Ansible, Terraform, Juju CloudFormation, Terraform, Juju Ansible, Shell xCAT, Clush Ansible, Shell Ansible, Python
Bootstrap method API API, PXE API PXE, IPMI PXE, IPMI PXE, IPMI PXE, API
Router control Kube-router Router/Subnet API Route Table / Subnet API Linux, OVS xCAT Linux API
Firewall control Istio, NetworkPolicy Security Groups API Security Group API Linux firewall Linux firewall Linux firewall API
Network virtualization VLAN, VxLAN, others VPC VPC OVS, Linux xCAT Linux API
DNS CoreDNS DNS-Nameserver Route 53 GDNS xCAT Linux API
Load Balancer Kube-proxy, LVS LVS Network Load Balancer LVS SLURM Ldirectord N/A
Storage options Local, Cloud, PVC Swift, Cinder, Nova S3, EFS, EBS, FSx Swift, XFS, EXT4, RAID10 GPFS SAN NFS, SAN

This table serves as a starting point for choosing the right stack based on:

  • Desired level of control (API vs bare-metal),
  • Context (on-prem, public cloud, HPC, CRM…),
  • Existing automation tooling.

Useful Cloud & IT links


Advanced: High Availability, HPC & DevSecOps

High Availability with Corosync & Pacemaker

HA cluster architecture

Basic principles:

  • Multi-node or multi-site clusters for redundancy.
  • Use of IPMI for fencing, provisioning via PXE/NTP/DNS/TFTP.
  • For a 2-node cluster:
 – carefully sequence fencing to avoid split-brain,
 – 3 or more nodes remain recommended for production.

Common resource patterns

  • Multipath storage, LUNs, LVM, NFS.
  • User resources and application processes.
  • Virtual IPs, DNS records, network listeners.

HPC

Overview of an HPC cluster

  • Job orchestration (SLURM or equivalent).
  • High-performance shared storage (GPFS, Lustre…).
  • Possible integration with AI workloads (large-scale training, GPU inference).

DevSecOps

DevSecOps reference design

  • CI/CD pipelines with built-in security checks (linting, SAST, DAST, SBOM).
  • Observability (logs, metrics, traces) integrated from design time.
  • Automated vulnerability scanning, secret management, policy-as-code.

About & Contributions

For more examples, scripts, diagrams, and feedback, see:

Suggestions for corrections, diagram improvements, or new labs are welcome. This wiki aims to remain a living laboratory for AI, cloud, and automation.