ProHoster > blog > Utawala > Muhtasari mfupi na usanidi wa Kontena za Kata

Muhtasari mfupi na usanidi wa Kontena za Kata

Muhtasari mfupi na usanidi wa Kontena za Kata
Makala hii itajadili jinsi inavyofanya kazi Vyombo vya Kata, na pia kutakuwa na sehemu ya vitendo na unganisho lao kwa Docker.

Kuhusu shida za kawaida na Docker na suluhisho zao tayari iliandikwa, leo nitaelezea kwa ufupi utekelezaji kutoka kwa Makontena ya Kata. Kata Containers ni wakati salama wa kukimbia kwa kontena kulingana na mashine nyepesi nyepesi. Kufanya kazi nao ni sawa na vyombo vingine, lakini kwa kuongeza kuna kutengwa kwa kuaminika zaidi kwa kutumia teknolojia ya virtualization ya vifaa. Mradi ulianza mwaka wa 2017, wakati jumuiya ya jina moja ilikamilisha kuunganishwa kwa mawazo bora kutoka kwa Intel Clear Containers na Hyper.sh RunV, baada ya hapo kazi iliendelea juu ya usaidizi wa usanifu mbalimbali, ikiwa ni pamoja na AMD64, ARM, IBM p- na z. -mfululizo. Zaidi ya hayo, kazi inasaidiwa ndani ya hypervisors QEMU, Firecracker, na pia kuna ushirikiano na kontena. Msimbo unapatikana kwa GitHub chini ya leseni ya MIT.

Vipengele muhimu

  • Kufanya kazi na msingi tofauti, hivyo kutoa mtandao, kumbukumbu na kutengwa kwa I / O, inawezekana kulazimisha matumizi ya kutengwa kwa vifaa kulingana na upanuzi wa virtualization.
  • Usaidizi kwa viwango vya sekta ikijumuisha OCI (muundo wa kontena), Kubernetes CRI
  • Utendaji thabiti wa vyombo vya kawaida Linux, kuongeza kutengwa bila gharama za ziada ambazo huathiri utendaji wa mashine pepe za kawaida
  • Ondoa hitaji la kuendesha kontena ndani ya mashine kamili za mtandaoni, miingiliano ya jumla hurahisisha ujumuishaji na uzinduzi.

Ufungaji

Kuna nyingi chaguzi za usakinishaji, nitazingatia usakinishaji kutoka kwenye hazina, kulingana na mfumo endeshi Centos 7.
Ni muhimu: Kazi ya Vyombo vya Kata inasaidiwa tu kwenye vifaa, usambazaji wa uboreshaji haufanyi kazi kila wakati, pia wanahitaji msaada wa sse4.1 kutoka kwa processor.

Kufunga Vyombo vya Kata ni rahisi sana:

Sakinisha huduma za kufanya kazi na hazina:

# yum -y install yum-utils

Lemaza Selinux (ni sahihi zaidi kusanidi, lakini kwa unyenyekevu ninaizima):

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

Tunaunganisha hazina na kufanya ufungaji

# 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

marekebisho

Nitakuwa nikisanidi kufanya kazi na docker, usanikishaji wake ni wa kawaida, sitaielezea kwa undani zaidi:

# 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

Tunafanya mabadiliko kwa daemon.json:

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

Anzisha tena docker:

# service docker restart

Afya Angalia

Ukianzisha chombo kabla ya kuanza tena docker, unaweza kuona kwamba uname itatoa toleo la kernel inayoendesha kwenye mfumo mkuu:

# 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

Baada ya kuanza tena, toleo la kernel linaonekana kama hii:

# 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

Timu zaidi!

# 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

Mtihani wa upakiaji wa haraka

Ili kutathmini hasara kutoka kwa uvumbuzi - ninaendesha sysbench, kama mifano kuu chukua chaguo hili.

Inaendesha sysbench kwa kutumia Docker+containrd

Mtihani wa processor

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

Mtihani wa 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

Inaendesha sysbench kwa kutumia Docker+Kata Containers

Mtihani wa processor

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

Mtihani wa 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

Kimsingi, hali tayari iko wazi, lakini ni bora zaidi kuendesha vipimo mara kadhaa, kuondoa wauzaji na wastani wa matokeo, kwa hivyo sifanyi majaribio zaidi bado.

Matokeo

Licha ya ukweli kwamba vyombo kama hivyo huchukua takriban mara tano hadi kumi kuanza (wakati wa kawaida wa kukimbia kwa amri zinazofanana wakati wa kutumia kontena ni chini ya theluthi moja ya sekunde), bado hufanya kazi haraka sana ikiwa tutachukua wakati kamili wa kuanza (hapo). ni mifano hapo juu, amri zinazotekelezwa kwa wastani wa sekunde tatu). Kweli, matokeo ya mtihani wa haraka wa CPU na RAM yanaonyesha karibu matokeo sawa, ambayo hayawezi lakini kufurahiya, haswa kwa kuzingatia ukweli kwamba kutengwa kunatolewa kwa kutumia utaratibu unaoendeshwa vizuri kama kvm.

Tangazo

Makala ni mapitio, lakini inakupa fursa ya kujisikia wakati mbadala wa kukimbia. Maeneo mengi ya maombi hayajafunikwa, kwa mfano, tovuti inaelezea uwezo wa kuendesha Kubernetes juu ya Vyombo vya Kata. Zaidi ya hayo, unaweza pia kuendesha mfululizo wa majaribio yanayolenga kutafuta matatizo ya usalama, kuweka vikwazo na mambo mengine ya kuvutia.

Ninaomba wale wote ambao wamesoma na kurudia hapa kushiriki katika uchunguzi, ambao machapisho ya baadaye juu ya mada hii yatategemea.

Watumiaji waliojiandikisha pekee ndio wanaweza kushiriki katika utafiti. Weka sahihitafadhali.

Je, niendelee kuchapisha makala kuhusu Vyombo vya Kata?

  • 80,0%Ndiyo, andika zaidi!28

  • 20,0%Hapana, usifanye…7

Watumiaji 35 walipiga kura. Watumiaji 7 walijizuia.

Chanzo: mapenzi.com

Nunua upangishaji wa kuaminika wa tovuti zilizo na ulinzi wa DDoS, seva za VPS VDS 🔥 Nunua upangishaji wa tovuti unaoaminika kwa ulinzi wa DDoS, seva za VPS VDS | ProHoster