Takaitaccen bayani da saitin Kwantenan Kata

Takaitaccen bayani da saitin Kwantenan Kata
Wannan labarin zai tattauna yadda yake aiki Kata Kwantena, kuma za a sami wani bangare mai amfani tare da haɗin su zuwa Docker.

Game da matsalolin gama gari tare da Docker da mafitarsu tuni aka rubuta, A yau zan yi bayanin aiwatarwa a taƙaice daga kwantena na Kata. Kwantenan Kata amintaccen lokacin aikin kwantena ne dangane da injuna masu nauyi. Yin aiki tare da su iri ɗaya ne da sauran kwantena, amma ƙari da haka akwai warewar da ta fi dacewa ta amfani da fasahar sarrafa kayan masarufi. An fara aikin ne a cikin 2017, lokacin da al'ummar wannan sunan suka kammala haɗin gwiwar mafi kyawun ra'ayoyin daga Intel Clear Containers da Hyper.sh RunV, bayan haka aikin ya ci gaba da goyon bayan gine-gine daban-daban, ciki har da AMD64, ARM, IBM p- da z. -jeri. Bugu da ƙari, ana goyan bayan aiki a cikin hypervisors QEMU, Firecracker, kuma akwai kuma haɗin kai tare da kwantena. Ana samun lambar a GitHub karkashin lasisin MIT.

Abubuwan fasali

  • Yin aiki tare da keɓaɓɓen asali, don haka samar da hanyar sadarwa, ƙwaƙwalwar ajiya da keɓewar I / O, yana yiwuwa a tilasta amfani da keɓantawar kayan aiki dangane da haɓakar haɓakawa.
  • Taimako ga ka'idojin masana'antu ciki har da OCI (tsarin kwantena), Kubernetes CRI
  • Daidaitaccen aiki na kwantena Linux na yau da kullun, haɓaka keɓancewa ba tare da aikin sama da VM na yau da kullun ba
  • Kawar da buƙatar gudanar da kwantena a cikin cikakkun injunan kama-da-wane, abubuwan mu'amala na yau da kullun suna sauƙaƙe haɗin kai da ƙaddamarwa.

saitin

Akwai da yawa Zaɓuɓɓukan shigarwa, Zan yi la'akari da shigarwa daga ma'ajin, dangane da tsarin aiki na Centos 7.
Muhimmanci: Kata Kwantenan aiki ana tallafawa ne kawai akan kayan aiki, isar da ingantaccen aiki ba koyaushe yana aiki ba, kuma bukatar sse4.1 goyon baya daga processor.

Shigar da kwantena na Kata abu ne mai sauƙi:

Shigar da kayan aiki don aiki tare da ma'aji:

# yum -y install yum-utils

Kashe Selinux (ya fi dacewa don daidaitawa, amma don sauƙi na kashe shi):

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

Muna haɗa ma'ajiyar kuma mu yi shigarwa

# 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

gyara

Zan saita don yin aiki tare da docker, shigarwa na yau da kullun, ba zan kwatanta shi dalla-dalla ba:

# 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

Muna yin canje-canje zuwa daemon.json:

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

Sake kunna docker:

# service docker restart

Duba aiki

Idan kun fara akwati kafin sake kunna docker, zaku iya ganin cewa unname zai ba da sigar kernel da ke gudana akan babban tsarin:

# 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

Bayan sake farawa, sigar kernel yayi kama da haka:

# 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

Ƙarin ƙungiyoyi!

# 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

Gwajin lodi mai sauri

Don tantance asarar daga haɓakawa - Ina gudanar da sysbench, a matsayin manyan misalai dauki wannan zabin.

Gudun sysbench ta amfani da Docker+container

Gwajin sarrafawa

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

Gwajin 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

Gudun sysbench ta amfani da Docker+Kata Containers

Gwajin sarrafawa

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

Gwajin 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

A ka'ida, halin da ake ciki ya riga ya bayyana, amma ya fi dacewa don gudanar da gwaje-gwaje sau da yawa, cire masu fita da matsakaicin sakamako, don haka ban yi ƙarin gwaje-gwaje ba tukuna.

binciken

Duk da cewa irin waɗannan kwantena suna ɗaukar kusan sau biyar zuwa goma don farawa (lokacin gudu na yau da kullun don irin wannan umarni lokacin amfani da kwantena bai wuce kashi uku na daƙiƙa ba), har yanzu suna aiki da sauri idan muka ɗauki cikakken lokacin farawa (a can). misalai ne a sama, umarnin da aka yi a matsakaicin daƙiƙa uku). Da kyau, sakamakon gwajin sauri na CPU da RAM yana nuna kusan sakamako iri ɗaya, wanda ba zai iya yin farin ciki ba, musamman idan aka yi la'akari da cewa an ba da warewa ta hanyar amfani da tsarin aiki mai kyau kamar kvm.

Sanarwa

Labarin bita ne, amma yana ba ku dama don jin madadin lokacin aiki. Yawancin wuraren aikace-aikacen ba a rufe su ba, alal misali, rukunin yanar gizon yana bayyana ikon sarrafa Kubernetes a saman kwantena na Kata. Bugu da ƙari, kuna iya gudanar da jerin gwaje-gwaje da aka mayar da hankali kan gano matsalolin tsaro, saita ƙuntatawa, da sauran abubuwa masu ban sha'awa.

Ina roƙon duk waɗanda suka karanta kuma suka sake dawowa a nan don shiga cikin binciken, akan wanne wallafe-wallafen nan gaba kan wannan batu za su dogara.

Masu amfani da rajista kawai za su iya shiga cikin binciken. Shigadon Allah.

Shin zan ci gaba da buga labarai game da Kwantenan Kata?

  • 80,0%Ee, rubuta ƙari!28

  • 20,0%A'a, kar…7

Masu amfani 35 sun kada kuri'a. Masu amfani 7 sun kaurace.

source: www.habr.com

Add a comment