Main Page: Difference between revisions

From Essential
Jump to navigation Jump to search
No edit summary
No edit summary
 
(272 intermediate revisions by the same user not shown)
Line 1: Line 1:
My name is Antonio DA SILVA PACHECO ([[CV_PACHECO]] [https://fr.linkedin.com/in/antonio-d-49682273?trk=people-guest_people_search-card LINKEDIN]).
[[File:Infocepo-illustration.jpg|thumb|right]]
<br>
'''Discover cloud computing on infocepo.com''':
With this site, I want to share my projects.  
* Master cloud infrastructure
* Explore AI
* Compare Kubernetes and AWS
* Advance your IT skills with hands-on labs and open-source software.
 
Start your journey to expertise.
 
<br>
<br>
== AI Tools ==
* [https://chat.openai.com ChatGPT4] - Public assistant with learning abilities.
* [https://github.com/open-webui/open-webui open-webui] + [https://www.scaleway.com/en/h100-pcie-try-it-now/ GPU H100] + [https://ollama.com Ollama] - Private assistant and API.
* [https://github.com/ynotopec/summarize Private summary]
=== DEV ===
(28/08/2024)
* [https://ollama.com/library LLM Trending]
* [https://github.com/search?q=stars%3A%3E15000+forks%3A%3E1500+created%3A%3E2022-06-01&type=repositories&s=updated&o=desc Project Trending]
* [https://huggingface.co/spaces/HuggingFaceH4/open_llm_leaderboard LLM Ranking]
* [https://chat.lmsys.org ChatBot Evaluate]
* [https://www.perplexity.ai Perplexity AI] - R&D
* [https://huggingface.co/models Models Trending]
* [https://github.com/hiyouga/LLaMA-Factory LLM Fine Tuning]
* [https://huggingface.co/spaces/mteb/leaderboard Embeddings Ranking]
* [https://ann-benchmarks.com Vectors DB Ranking]
* [https://www.nvidia.com/en-us/data-center/h100/ NVIDIA H100] - KUBERNETES or HPC clusters for DATASCIENCE.
* [https://www.nvidia.com/fr-fr/geforce/graphics-cards/40-series/rtx-4080-family NVIDIA 4080] - GPU card for private assistance.
* [https://huggingface.co/models?pipeline_tag=image-text-to-text&sort=trending Img2txt Trending]
* [https://huggingface.co/spaces/TIGER-Lab/GenAI-Arena Txt2img Evaluate]
* [https://github.com/chatchat-space/Langchain-Chatchat Chatchat] - Private assistant with RAG capabilities in Chinese.
* [https://top500.org/lists/green500/ HPC Efficiency]
==== INTERESTING LLMs ====
(28/08/2024)
{| class="wikitable"
! Model
! Comment
|-
| '''RAG'''
| (gemma2-27b), $$
|-
| '''RAG-FR'''
| (glm4)
|-
| '''code'''
| (gemma2-27b), $$
|-
| '''math'''
| (gemma2-27b), $$
|-
| '''summary'''
| (llama3.1)
|-
| '''gemma2'''
| Fast
|-
| '''gemma2-27b'''
| Medium, best, $$
|-
| '''gemma2'''
| OllamaFunctions
|}


=NEWS=
=== NEWS ===
==CLOUD LAB==
(04/05/2024)
I want to share my [[LAB project]].<br>
* [https://www.youtube.com/@lev-selector/videos Very good AI News]
<br>
* For the [https://betterprogramming.pub/color-your-captions-streamlining-live-transcriptions-with-diart-and-openais-whisper-6203350234ef '''transcription'''] in real time with Diart, it is possible to follow the interlocutors.
[[file:Infocepo.drawio.png]]
* [https://github.com/openai-translator/openai-translator Translation] tools like Google Translate are becoming popular.
==Servers audit==
* [https://www.mouser.fr/ProductDetail/BittWare/RS-GQ-GC1-0109?qs=ST9lo4GX8V2eGrFMeVQmFw%3D%3D '''LLM 10x accelerator'''] and cheaper with GROQ.
I made [[ServerDiff.sh]] script to audit servers.
* [https://opensearch.org/docs/latest/search-plugins/conversational-search Opensearch with LLM]
You can track configuration drift.
You can check if your environments are the same.


==CLOUD migration example==
=== TRAINING ===
*1.5 days: infra audit (82 clustered services) ([https://infocepo.com/wiki/index.php/ServerDiff.sh audit own tool])
* [https://www.youtube.com/watch?v=4Bdc55j80l8 TRANSFORMERS ALGORITHM]


*1.5 days: physical and virtual target CLOUD architecture diagram
== CLOUD LAB ==
[[File:Infocepo.drawio.png]]
<br><br>
Presenting my [[LAB project]].


*1.5 days: physical compliance of 2 CLOUD (6 hypervisors, 6TB memory)
== CLOUD Audit ==
Created [[ServerDiff.sh]] for server audits. Enables configuration drift tracking and environment consistency checks.


*1 days: installation of the 2 CLOUD
== CLOUD Migration Example ==
[[File:Diagram-migration-ORACLE-KVM-v2.drawio.png]]
* 1.5d: Infrastructure audit of 82 services ([https://infocepo.com/wiki/index.php/ServerDiff.sh ServerDiff.sh])
* 1.5d: Create cloud architecture diagram.
* 1.5d: Compliance check of 2 clouds (6 hypervisors, 6TB memory).
* 1d: Cloud installations.
* 0.5d: Stability check.


*.5 day: stability check
{| style="border-spacing:0;width:18.12cm;"
{| style="border-spacing:0;width:18.12cm;"
|- style="background-color:#ffc000;border:0.05pt solid #000000;padding:0.049cm;"
|- style="background-color:#ffc000;border:0.05pt solid #000000;padding:0.049cm;"
| align=center style="color:#000000;" | '''ACTION'''
| align=center style="color:#000000;" | '''ACTION'''
| align=center style="color:#000000;" | '''RESULT'''
| align=center style="color:#000000;" | '''RESULT'''
| align=center style="color:#000000;" | '''OK/NOK'''
| align=center style="color:#000000;" | '''OK/KO'''
|-
|-
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | Disable all nodes minus one. (maintenance mode)
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | Activate maintenance for n/2-1 nodes or 1 node if 2 nodes.
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | All resources started whitout disruption.
| 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="background-color:#d8e4bc;border:0.05pt solid #000000;padding:0.049cm;color:#000000;" |  
|-
|-
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | Activate all nodes. Power off all nodes minus one, different from the previous test.
| 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.
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | All resources started.
| 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="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.
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | Power off all nodes simultaneously. Power on all nodes simultaneously.
| style="border:0.05pt solid #000000;padding:0.049cm;color:#000000;" | All resources started on all nodes.
| 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="background-color:#d8e4bc;border:0.05pt solid #000000;padding:0.049cm;color:#000000;" |  
|-
|-
|}
|}
*1.5 days: CLOUD automation study
* 1.5d: Cloud automation study.
* 1.5d: Develop 6 templates (2 clouds, 2 OS, 8 environments, 2 versions).
* 1d: Create migration diagram.
* 1.5d: Write 138 lines of migration code ([https://infocepo.com/wiki/index.php/MigrationApp.sh MigrationApp.sh]).
* 1.5d: Process stabilization.
* 1.5d: Cloud vs. old infrastructure benchmark.
* 0.5d: Unavailability time calibration per migration unit.
* 5 min: Load 82 VMs (env, OS, application code, 2 IPs).


*1.5 days: 6 templates (2 CLOUD, 2 OS, 8 environments, 2 versions)
Total = 15 man-days.


*1 day: migration diagram
== WEB Enhancement ==
[[File:Diagram-migration-ORACLE-KVM-v2.drawio.png]]
[[File:WebModelDiagram.drawio.png]]
 
*1.5 days: 138 lines of industrialization code for migration ([https://infocepo.com/wiki/index.php/MigrationApp.sh migration own code])
 
*1.5 days: process stabilization
 
*1.5 days: CLOUD benchmark vs old INFRA
 
*.5 days: calibration of unavailability time per unit migration
 
*5 minutes (effective load): 82 VM (env, os, application_code, 2 IP)


Total = 15 man-days
* Formalize infrastructure for flexibility and reduced complexity.
* Utilize customer-location tracking name server like GDNS.
* Use minimal instances with a network load balancer like LVS.
* 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 PROXY with TLS decoder like ENVOY for service compatibility.
* Consider serverless services 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.
* Use queues for long batches.
* Use buffers for stability of real streams.
* More information at [https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure CLOUD WIKIPEDIA] and [https://github.com/systemdesign42/system-design GITHUB].


==CLOUD improvement==
== CLOUD WIKIPEDIA ==
[[File:WebModelDiagram.drawio.png]]
* [https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure CLOUD WIKIPEDIA]
*Formalize your infrastructure as much as possible for more flexibility, low complexity and less technology lock-in.
*Use a name server able to handle the position of your customers like GDNS.
*Use a minimal instance and use a network load balancer like LVS. Monitor the global load of your instances and add/delete dynamically as needed.
*Or, many providers have dynamic computing services. Compare the prices. But take care about the technology lock-in.
*Use a very efficient TLS decoder like the ATS decoder without blocking.
*Use very fast http cache like VARNISH.
*Use a big cache for big files like ATS.
*...
*Use serverless service for standard runtimes like Java, Python and PHP. But beware of certain incompatibilities and a lack of consistency over time.
*...
*Each time you need dynamic computing power think about load balancing or native service from the providers (caution about providers services!)
*...
*Try to use open source STACKs as much as possible
*...
*Use cache for your databases like MEMCACHED


==CLOUD vs HW==
== CLOUD vs HW ==
{| class="wikitable"
{| class="wikitable"
|'''Function'''
|'''KUBERNETES'''
|'''OPENSTACK'''
|'''AWS'''
|'''Bare-metal'''
|'''HPC'''
|'''CRM'''
|'''OVIRT'''
|-
|-
|DEPLOY
! Function
|HELM/ANSIBLE/SH
! Kubernetes
|TERRAFORM/ANSIBLE/SH/JUJU
! OpenStack
|TERRAFORM/CLOUDFOUNDATION/ANSIBLE/JUJU
! AWS
|ANSIBLE/SH
! Bare-metal
|XCAT/CLUSH
! HPC
|ANSIBLE/SH
! CRM
|ANSIBLE/PYTHON/SH
! oVirt
|-
|-
|BOOTSTRAP
| '''Deployment Tools'''<br>''(Tools used for deployment)''
|API/CLI
| Helm, YAML, Operator, Ansible, Juju, ArgoCD
|PXE/API/CLI
| Ansible, Packer, Terraform, Juju
|API/CLI
| Ansible, Terraform, CloudFormation, Juju
|PXE/IPMI
| Ansible, Shell Scripts
|PXE/IPMI
| xCAT, Clush
|PXE/IPMI
| Ansible, Shell Scripts
|PXE/API
| Ansible, Python, Shell Scripts
|-
|-
|
| '''Bootstrap Method'''<br>''(Initial configuration and setup)''
|
| API
|
| API, PXE
|
| API
|
| PXE, IPMI
|
| PXE, IPMI
|
| PXE, IPMI
|
| PXE, API
|-
|-
|Router
| '''Router Control'''<br>''(Routing services)''
|API/CLI (kube-router)
| API (Kube-router)
|API/CLI (router/subnet)
| API (Router/Subnet)
|API/CLI (Route table/subnet)
| API (Route Table/Subnet)
|LINUX/OVS/external
| Linux, OVS, External Hardware
|XCAT/external
| xCAT, External Hardware
|LINUX/external
| Linux, External Hardware
|API
| API
|-
|-
|Firewall
| '''Firewall Control'''<br>''(Firewall rules and policies)''
|INGRESS/EGRESS/ISTIO
| Ingress, Egress, Istio, NetworkPolicy
|API/CLI (Security groups)
| API (Security Groups)
|API/CLI (Security group)
| API (Security Group)
|LINUX (NFT)
| Linux Firewall
|LINUX (NFT)
| Linux Firewall
|LINUX (NFT)
| Linux Firewall
|API
| API
|-
|-
|Vlan
| '''Network Virtualization'''<br>''(VLAN/VxLAN technologies)''
|DANM
| Multiple Options
|API/CLI (VPC)
| VPC
|API/CLI (VPC)
| VPC
|OVS/LINUX/external
| OVS, Linux, External Hardware
|XCAT/external
| xCAT, External Hardware
|LINUX/external
| Linux, External Hardware
|API
| API
|-
|-
|
| '''Name Server Control'''<br>''(DNS services)''
|
| CoreDNS
|
| DNS-Nameserver
|
| Amazon Route 53
|
| GDNS
|
| xCAT
|
| Linux, External Hardware
|
| API, External Hardware
|-
|-
|Name server
| '''Load Balancer'''<br>''(Load balancing options)''
|coredns
| Kube-proxy, LVS (IPVS)
|dns-nameserver
| LVS
|Amazon Route 53
| Network Load Balancer
|GDNS
| LVS
|XCAT
| SLURM
|LINUX/external
| Ldirectord
|API/external
| N/A
|-
|-
|Load balancer
| '''Storage Options'''<br>''(Available storage technologies)''
|kube-proxy/LVS(IPVS)
| Multiple Options
|LVS
| Swift, Cinder, Nova
|Network Load Balancer
| S3, EFS, FSx, EBS
|LVS
| Swift, XFS, EXT4, RAID10
|SLURM
| GPFS
|Ldirectord
| SAN
|
| NFS, SAN
|-
|Storage
|many
|SWIFT/CINDER/NOVA
|S3/EFS/FSX/EBS
|OPENSTACK SWIFT/XFS/EXT4/RAID10
|GPFS
|SAN
|NFS/SAN
|}
|}


==CLOUD REF==
== CLOUD providers ==
[https://landscape.cncf.io/?fullscreen=yes CLOUD REF]
* [https://cloud.google.com/free/docs/aws-azure-gcp-service-comparison CLOUD providers]
 
== CLOUD INTERNET NETWORK ==
* [https://global-internet-map-2021.telegeography.com/ CLOUD INTERNET NETWORK]
 
== CLOUD NATIVE ==
* [https://landscape.cncf.io/?fullscreen=yes OFFICIAL STACKS]
* DevSecOps :
[[File:DSO-POC-V3.drawio.png]]
 
== High Availability (HA) with Corosync+Pacemaker ==
[[File:HA-REF.drawio.png]]


==CLOUD providers==
=== Typical Architecture ===
*[https://cloud.google.com/free/docs/aws-azure-gcp-service-comparison aws-azure-gcp service comparison]


==Infrastructure example==
* Dual-room.
*[https://wikitech.wikimedia.org/wiki/Wikimedia_infrastructure Wikipedia]
* IPMI LAN (fencing).
==IT salaries==
* NTP, DNS+DHCP+PXE+TFTP+HTTP (auto-provisioning), PROXY (updates or internal REPOSITORY).
*[http://jobsearchtech.about.com/od/educationfortechcareers/tp/HighestCerts.htm Top technical certifications]
* Choose 2+ node clusters.
*[https://www.silkhom.com/barometre-2021-des-tjm-dans-informatique-digital/ IT]
* For 2-node, require COROSYNC 2-node config, 10-second staggered closing for stability. For better stability, choose 3+ nodes architecture.
*[http://www.journaldunet.com/solutions/emploi-rh/salaire-dans-l-informatique-hays/ IT]
* Allocate 4GB/base for DB resources. CPU resource requirements are generally low.
==REDHAT package browser==
[https://access.redhat.com/downloads/content/package-browser REDHAT package browser]
==HA COROSYNC+PACEMAKER==
Pour l'architecture je propose du classique :


2 salles
=== Typical Service Pattern ===
2FC / serveur (actif/actif) (SAN)
* Multipath
2*10Gbit/s ethernet / serveur (actif/passif, possible actif/actif si PXE sur VLAN natif 0)
* LUN
VLAN IPMI (pour le fence)
* LVM (LVM resource)
VLAN ADMIN qui doit être le VLAN natif si BOOTSTRAP par PXE (admin,provisionning,heartbeat)
* FS (FS resource)
VLAN USER (les services applicatifs)
* NFS (FS resource)
NTP
* User
DNS+DHCP+PXE+TFTP+HTTP pour du provisionning en automatique
* IP (IP resource)
PROXY (pour mise à jour ou sinon REPOSITORY interne)
* DNS name
* Process (Process resource)
* Listener (Listener resource)


Choisir entre des clusteurs à 2 noeuds ou plus.
== HPC ==
[[File:HPC.drawio.png]]


Pour une archi 2 noeuds il faut un paramètrage à 2 noeuds sur COROSYNC et veiller à configurer un fence décallé de 10 secondes pour l'un des noeuds (sinon clusteur instable).
== IT Wage ==
* [http://jobsearchtech.about.com/od/educationfortechcareers/tp/HighestCerts.htm Best IT certifications]
* [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]


Pour les services en écriture, ils seront de type actif/passif.
== SRE ==
Pour les autres services il est possible de faire de l'actif/actif.
* [https://openapm.io SRE]


Pour les ressources DB il faut prévoir 8Go par base en général et doubler pour un clusteur à 2 noeuds (perte d'un noeud).
== REDHAT Package Browser ==
Pour les ressources CPU, en règle général il n'y a pas de gros besoins. Astuce, pour des compressions dont les temps sont critiques utiliser PZSTD.
* [https://access.redhat.com/downloads/content/package-browser REDHAT Package Browser]

Latest revision as of 19:08, 17 September 2024

Infocepo-illustration.jpg

Discover cloud computing on infocepo.com:

  • Master cloud infrastructure
  • Explore AI
  • Compare Kubernetes and AWS
  • Advance your IT skills with hands-on labs and open-source software.

Start your journey to expertise.


AI Tools

DEV

(28/08/2024)

INTERESTING LLMs

(28/08/2024)

Model Comment
RAG (gemma2-27b), $$
RAG-FR (glm4)
code (gemma2-27b), $$
math (gemma2-27b), $$
summary (llama3.1)
gemma2 Fast
gemma2-27b Medium, best, $$
gemma2 OllamaFunctions

NEWS

(04/05/2024)

TRAINING

CLOUD LAB

Infocepo.drawio.png

Presenting my LAB project.

CLOUD Audit

Created ServerDiff.sh for server audits. Enables configuration drift tracking and environment consistency checks.

CLOUD Migration Example

Diagram-migration-ORACLE-KVM-v2.drawio.png

  • 1.5d: Infrastructure audit of 82 services (ServerDiff.sh)
  • 1.5d: Create cloud architecture diagram.
  • 1.5d: Compliance check of 2 clouds (6 hypervisors, 6TB memory).
  • 1d: Cloud installations.
  • 0.5d: Stability check.
ACTION RESULT OK/KO
Activate maintenance for n/2-1 nodes or 1 node if 2 nodes. All resources are started.
Un-maintenance all nodes. Power off n/2-1 nodes or 1 node if 2 nodes, different from the previous test. All resources are started.
Power off all nodes simultaneously. Power on all nodes simultaneously. All resources are started.
  • 1.5d: Cloud automation study.
  • 1.5d: Develop 6 templates (2 clouds, 2 OS, 8 environments, 2 versions).
  • 1d: Create migration diagram.
  • 1.5d: Write 138 lines of migration code (MigrationApp.sh).
  • 1.5d: Process stabilization.
  • 1.5d: Cloud vs. old infrastructure benchmark.
  • 0.5d: Unavailability time calibration per migration unit.
  • 5 min: Load 82 VMs (env, OS, application code, 2 IPs).

Total = 15 man-days.

WEB Enhancement

WebModelDiagram.drawio.png

  • Formalize infrastructure for flexibility and reduced complexity.
  • Utilize customer-location tracking name server like GDNS.
  • Use minimal instances with a network load balancer like LVS.
  • 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 PROXY with TLS decoder like ENVOY for service compatibility.
  • Consider serverless services 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.
  • Use queues for long batches.
  • Use buffers for stability of real streams.
  • More information at CLOUD WIKIPEDIA and GITHUB.

CLOUD WIKIPEDIA

CLOUD vs HW

Function Kubernetes OpenStack AWS Bare-metal HPC CRM oVirt
Deployment Tools
(Tools used for deployment) 		Helm, YAML, Operator, Ansible, Juju, ArgoCD Ansible, Packer, Terraform, Juju Ansible, Terraform, CloudFormation, Juju Ansible, Shell Scripts xCAT, Clush Ansible, Shell Scripts Ansible, Python, Shell Scripts
Bootstrap Method
(Initial configuration and setup) 		API API, PXE API PXE, IPMI PXE, IPMI PXE, IPMI PXE, API
Router Control
(Routing services) 		API (Kube-router) API (Router/Subnet) API (Route Table/Subnet) Linux, OVS, External Hardware xCAT, External Hardware Linux, External Hardware API
Firewall Control
(Firewall rules and policies) 		Ingress, Egress, Istio, NetworkPolicy API (Security Groups) API (Security Group) Linux Firewall Linux Firewall Linux Firewall API
Network Virtualization
(VLAN/VxLAN technologies) 		Multiple Options VPC VPC OVS, Linux, External Hardware xCAT, External Hardware Linux, External Hardware API
Name Server Control
(DNS services) 		CoreDNS DNS-Nameserver Amazon Route 53 GDNS xCAT Linux, External Hardware API, External Hardware
Load Balancer
(Load balancing options) 		Kube-proxy, LVS (IPVS) LVS Network Load Balancer LVS SLURM Ldirectord N/A
Storage Options
(Available storage technologies) 		Multiple Options Swift, Cinder, Nova S3, EFS, FSx, EBS Swift, XFS, EXT4, RAID10 GPFS SAN NFS, SAN

CLOUD providers

CLOUD INTERNET NETWORK

CLOUD NATIVE

DSO-POC-V3.drawio.png

High Availability (HA) with Corosync+Pacemaker

HA-REF.drawio.png

Typical Architecture

  • Dual-room.
  • 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. For better stability, choose 3+ nodes architecture.
  • Allocate 4GB/base for DB resources. CPU resource requirements are generally low.

Typical Service Pattern

  • Multipath
  • LUN
  • LVM (LVM resource)
  • FS (FS resource)
  • NFS (FS resource)
  • User
  • IP (IP resource)
  • DNS name
  • Process (Process resource)
  • Listener (Listener resource)

HPC

HPC.drawio.png

IT Wage

SRE

REDHAT Package Browser

Retrieved from "https://infocepo.com/wiki/index.php?title=Main_Page&oldid=1864"