ProHoster > Blog > Administrasyon an > Brèf apèsi ak konfigirasyon Kata Containers

Brèf apèsi ak konfigirasyon Kata Containers

Brèf apèsi ak konfigirasyon Kata Containers
Atik sa a pral diskite sou kijan li fonksyone Kata Containers, epi pral gen tou yon pati pratik ak koneksyon yo nan Docker.

Konsènan pwoblèm komen ak Docker ak solisyon yo deja te ekri, jodi a mwen pral yon ti tan dekri aplikasyon an soti nan Kata Containers. Kata Containers se yon tan an sekirite veso ki baze sou machin vityèl ki lejè. Travay ak yo se menm jan ak lòt resipyan, men anplis gen yon izolasyon ki pi serye lè l sèvi avèk teknoloji Virtualization pyès ki nan konpitè. Pwojè a te kòmanse nan 2017, lè kominote a ki gen menm non te konplete fizyon pi bon lide ki soti nan Intel Clear Containers ak Hyper.sh RunV, apre sa travay kontinye sou sipò pou divès achitekti, ki gen ladan AMD64, ARM, IBM p- ak z. -seri. Anplis de sa, travay yo sipòte andedan hypervisors yo QEMU, Firecracker, epi gen tou entegrasyon ak containerd. Kòd la disponib nan GitHub anba lisans MIT.

Karakteristik prensipal la

  • Travay ak yon nwayo separe, konsa bay rezo, memwa ak I / O izolasyon, li posib fòse itilizasyon izolasyon pyès ki nan konpitè ki baze sou ekstansyon Virtualization.
  • Sipò pou estanda endistri ki gen ladan OCI (fòma veso), Kubernetes CRI
  • Pèfòmans konsistan nan resipyan Linux regilye yo, ogmante izolasyon san pèfòmans VM regilye yo
  • Elimine nesesite pou kouri kontenè andedan machin vityèl plen véritable, entèfas jenerik senplifye entegrasyon ak lansman.

Enstalasyon

Gen anpil opsyon enstalasyon, mwen pral konsidere enstale soti nan depo yo, ki baze sou sistèm nan operasyon Centos 7.
Li enpòtan: Kata Containers travay sipòte sèlman sou pyès ki nan konpitè, Virtualization transfert pa toujou travay, tou bezwen sipò sse4.1 soti nan processeur a.

Enstale Kata Containers se byen senp:

Enstale sèvis piblik pou travay ak depo:

# yum -y install yum-utils

Enfim Selinux (li pi kòrèk pou konfigirasyon, men pou senplisite mwen enfim li):

# setenforce 0
# sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config

Nou konekte repozitwa a epi fè enstalasyon an

# source /etc/os-release
# ARCH=$(arch)
# BRANCH="${BRANCH:-stable-1.10}"
# yum-config-manager --add-repo "http://download.opensuse.org/repositories/home:/katacontainers:/releases:/${ARCH}:/${BRANCH}/CentOS_${VERSION_ID}/home:katacontainers:releases:${ARCH}:${BRANCH}.repo"
# yum -y install kata-runtime kata-proxy kata-shim

ajisteman

Mwen pral mete kanpe pou travay ak Docker, enstalasyon li se tipik, mwen pa pral dekri li an plis detay:

# rpm -qa | grep docker
docker-ce-cli-19.03.6-3.el7.x86_64
docker-ce-19.03.6-3.el7.x86_64
# docker -v
Docker version 19.03.6, build 369ce74a3c

Nou fè chanjman nan daemon.json:

# cat <<EOF > /etc/docker/daemon.json
{
  "default-runtime": "kata-runtime",
  "runtimes": {
    "kata-runtime": {
      "path": "/usr/bin/kata-runtime"
    }
  }
}
EOF

Rekòmanse docker:

# service docker restart

Fonksyonèl chèk la

Si ou kòmanse veso a anvan rekòmanse Docker, ou ka wè ke uname pral bay vèsyon an nan nwayo a ap kouri sou sistèm prensipal la:

# docker run busybox uname -a
Linux 19efd7188d06 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64 GNU/Linux

Apre yon rekòmanse, vèsyon nwayo a sanble sa a:

# docker run busybox uname -a
Linux 9dd1f30fe9d4 4.19.86-5.container #1 SMP Sat Feb 22 01:53:14 UTC 2020 x86_64 GNU/Linux

Plis ekip!

# time docker run busybox mount
kataShared on / type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,size=65536k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
sysfs on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,relatime,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (ro,nosuid,nodev,noexec,relatime,xattr,name=systemd)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (ro,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (ro,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (ro,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (ro,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup (ro,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (ro,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/freezer type cgroup (ro,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (ro,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (ro,nosuid,nodev,noexec,relatime,cpuset)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
kataShared on /etc/resolv.conf type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
kataShared on /etc/hostname type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
kataShared on /etc/hosts type 9p (rw,dirsync,nodev,relatime,mmap,access=client,trans=virtio)
proc on /proc/bus type proc (ro,relatime)
proc on /proc/fs type proc (ro,relatime)
proc on /proc/irq type proc (ro,relatime)
proc on /proc/sys type proc (ro,relatime)
tmpfs on /proc/acpi type tmpfs (ro,relatime)
tmpfs on /proc/timer_list type tmpfs (rw,nosuid,size=65536k,mode=755)
tmpfs on /sys/firmware type tmpfs (ro,relatime)

real    0m2.381s
user    0m0.066s
sys 0m0.039s

# time docker run busybox free -m
              total        used        free      shared  buff/cache   available
Mem:           1993          30        1962           0           1        1946
Swap:             0           0           0

real    0m3.297s
user    0m0.086s
sys 0m0.050s

Tès chaj rapid

Pou evalye pèt yo soti nan Virtualization - mwen kouri sysbench, kòm egzanp prensipal yo pran opsyon sa a.

Kouri sysbench lè l sèvi avèk Docker + containerd

Tès processeur

sysbench 1.0:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1
Initializing random number generator from current time

Prime numbers limit: 20000

Initializing worker threads...

Threads started!

General statistics:
    total time:                          36.7335s
    total number of events:              10000
    total time taken by event execution: 36.7173s
    response time:
         min:                                  3.43ms
         avg:                                  3.67ms
         max:                                  8.34ms
         approx.  95 percentile:               3.79ms

Threads fairness:
    events (avg/stddev):           10000.0000/0.00
    execution time (avg/stddev):   36.7173/0.00

Tès RAM

sysbench 1.0:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1
Initializing random number generator from current time

Initializing worker threads...

Threads started!

Operations performed: 104857600 (2172673.64 ops/sec)

102400.00 MiB transferred (2121.75 MiB/sec)

General statistics:
    total time:                          48.2620s
    total number of events:              104857600
    total time taken by event execution: 17.4161s
    response time:
         min:                                  0.00ms
         avg:                                  0.00ms
         max:                                  0.17ms
         approx.  95 percentile:               0.00ms

Threads fairness:
    events (avg/stddev):           104857600.0000/0.00
    execution time (avg/stddev):   17.4161/0.00

Kouri sysbench lè l sèvi avèk Docker + Kata Containers

Tès processeur

sysbench 1.0:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1
Initializing random number generator from current time

Prime numbers limit: 20000

Initializing worker threads...

Threads started!

General statistics:
    total time:                          36.5747s
    total number of events:              10000
    total time taken by event execution: 36.5594s
    response time:
         min:                                  3.43ms
         avg:                                  3.66ms
         max:                                  4.93ms
         approx.  95 percentile:               3.77ms

Threads fairness:
    events (avg/stddev):           10000.0000/0.00
    execution time (avg/stddev):   36.5594/0.00

Tès RAM

sysbench 1.0:  multi-threaded system evaluation benchmark

Running the test with following options:
Number of threads: 1
Initializing random number generator from current time

Initializing worker threads...

Threads started!

Operations performed: 104857600 (2450366.94 ops/sec)

102400.00 MiB transferred (2392.94 MiB/sec)

General statistics:
    total time:                          42.7926s
    total number of events:              104857600
    total time taken by event execution: 16.1512s
    response time:
         min:                                  0.00ms
         avg:                                  0.00ms
         max:                                  0.43ms
         approx.  95 percentile:               0.00ms

Threads fairness:
    events (avg/stddev):           104857600.0000/0.00
    execution time (avg/stddev):   16.1512/0.00

Nan prensip, sitiyasyon an deja klè, men li pi pi bon pou fè tès yo plizyè fwa, retire outliers ak mwayèn rezilta yo, kidonk mwen pa fè plis tès ankò.

Jwenn

Malgre lefèt ke veso sa yo pran apeprè senk a dis fwa pi long pou kòmanse (tan nòmal kouri pou kòmandman menm jan an lè w ap itilize containerd se mwens pase yon tyè nan yon segonn), yo toujou travay byen vit si nou pran tan an kòmanse absoli (gen se egzanp pi wo a, kòmandman fèt an mwayèn twa segonn). Oke, rezilta yo nan yon tès rapid nan CPU ak RAM montre prèske menm rezilta yo, ki pa ka men kontan, espesyalman nan limyè de lefèt ke izolasyon yo bay lè l sèvi avèk yon mekanis ki byen kouri tankou kvm.

Anons

Atik la se yon revizyon, men li ba ou opòtinite pou santi ègzekutabl altènatif la. Anpil domèn aplikasyon yo pa kouvri, pou egzanp, sit la dekri kapasite nan kouri Kubernetes sou tèt Kata Containers. Anplis de sa, ou ka kouri tou yon seri tès ki konsantre sou jwenn pwoblèm sekirite, mete restriksyon, ak lòt bagay enteresan.

Mwen mande tout moun ki te li ak remonte isit la pou yo patisipe nan sondaj la, sou ki piblikasyon pwochen sou sijè sa a pral depann.

Se sèlman itilizatè ki anrejistre ki ka patisipe nan sondaj la. Enskri, tanpri.

Èske mwen ta dwe kontinye pibliye atik sou Kata Containers?

  • 80,0%Wi, ekri plis!28

  • 20,0%Non, pa...7

35 itilizatè yo te vote. 7 itilizatè te absteni.

Sous: www.habr.com

Add nouvo kòmantè