Eli nqaku liza kuxubusha indlela elisebenza ngayo
Malunga neengxaki eziqhelekileyo kunye neDocker kunye nezisombululo zabo
Iimpawu eziphambili
- Ukusebenza ngondoqo owahlukileyo, ngaloo ndlela ukubonelela ngenethiwekhi, inkumbulo kunye ne-I / O yedwa, kunokwenzeka ukunyanzela ukusetyenziswa kwe-hardware yodwa esekelwe kwizandiso ze-virtualization.
- Inkxaso yemigangatho yoshishino kuquka i-OCI (ifomati yesiqulatho), i-Kubernetes CRI
- Ukusebenza okungaguquguqukiyo kwezikhongozeli zeLinux eziqhelekileyo, ukonyuka kwamalungelo odwa ngaphandle kokusebenza ngaphezulu kwee-VM eziqhelekileyo
- Qeda imfuno yokuqhuba izikhongozeli ngaphakathi koomatshini abapheleleyo, ujongano oluqhelekileyo lwenziwe lula ukudityaniswa kunye nokuqaliswa.
isicwangciso
kukho
ebalulekileyo: Umsebenzi we-Kata Containers ixhaswa kuphela kwi-hardware, ukuhanjiswa kwe-virtualization ayisoloko isebenza, nayo funa inkxaso ye-sse4.1 ukusuka kwiprosesa.
Ukufakela i-Kata Containers kulula kakhulu:
Faka izixhobo zokusebenza ngoovimba:
# yum -y install yum-utils
Khubaza iSelinux (ilungile ngakumbi ukuyiqwalasela, kodwa ukwenza lula ndiyayivala):
# setenforce 0
# sed -i 's/^SELINUX=enforcing$/SELINUX=permissive/' /etc/selinux/config
Sidibanisa indawo yokugcina kwaye senze ukufakela
# 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
Yenza ngokwezifiso
Ndiza kumisela ukusebenza kunye ne-docker, ukufakwa kwayo kuqhelekileyo, andizukuyichaza ngakumbi:
# 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
Senza utshintsho kwi-daemon.json:
# cat <<EOF > /etc/docker/daemon.json
{
"default-runtime": "kata-runtime",
"runtimes": {
"kata-runtime": {
"path": "/usr/bin/kata-runtime"
}
}
}
EOF
Qala kwakhona idocker:
# service docker restart
Umsebenzi osebenzayo
Ukuba uqala isikhongozeli ngaphambi kokuba uqalise kwakhona i-docker, unokubona ukuba uname uya kunika uguqulelo lwe-kernel esebenza kwinkqubo ephambili:
# 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
Emva kokuqalisa kwakhona, inguqulo ye-kernel ibonakala ngolu hlobo:
# 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
Amaqela amaninzi!
# 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
Uvavanyo lomthwalo okhawulezayo
Ukuvavanya ilahleko evela kwi-virtualization - ndiqhuba i-sysbench, njengemizekelo ephambili
Ukuqhuba i-sysbench usebenzisa i-Docker+container
Uvavanyo lweprosesa
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
Uvavanyo lwe-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
Ukuqhuba i-sysbench usebenzisa iDocker+Kata Containers
Uvavanyo lweprosesa
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
Uvavanyo lwe-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
Ngokomgaqo, imeko sele icacile, kodwa kungcono kakhulu ukuqhuba iimvavanyo amaxesha amaninzi, ukususa izinto ezingaphandle kunye nokulinganisa iziphumo, ngoko andizenzi ezinye iimvavanyo okwangoku.
ezifunyanisiweyo
Ngaphandle kwento yokuba izikhongozeli ezinjalo zithatha malunga namaxesha amahlanu ukuya kwishumi ubude ukuqalisa (ixesha lokuqhuba eliqhelekileyo lemiyalelo efanayo xa usebenzisa isikhongozeli lingaphantsi kwesithathu somzuzwana), zisasebenza ngokukhawuleza ukuba sithatha ixesha lokuqala ngokupheleleyo (apho yimizekelo engasentla, imiyalelo eyenziwa kumndilili wemizuzwana emithathu). Ewe, iziphumo zovavanyo olukhawulezayo lwe-CPU kunye ne-RAM zibonisa phantse iziphumo ezifanayo, ezingenakuvuya, ngakumbi ngenxa yokuba ukubekwa wedwa kunikezelwe kusetyenziswa indlela eqhutywa kakuhle njenge-kvm.
Isibhengezo
Inqaku liphononongo, kodwa likunika ithuba lokuziva elinye ixesha lokubaleka. Iindawo ezininzi zesicelo azifakwanga, umzekelo, isayithi ichaza ukukwazi ukuqhuba i-Kubernetes phezulu kwe-Kata Containers. Ukongeza, unokuphinda uqhube uthotho lweemvavanyo ezijolise ekufumaneni iingxaki zokhuseleko, izithintelo zokuseta, kunye nezinye izinto ezinomdla.
Ndiyabacela bonke abo baye bafunda baze baphinde babuyele apha ukuba bathathe inxaxheba kwisaveyi, apho iimpapasho ezizayo malunga nesi sihloko ziya kuxhomekeka.
Ngabasebenzisi ababhalisiweyo kuphela abanokuthatha inxaxheba kuphando.
Ngaba ndimele ndiqhubeke nokupapasha amanqaku malunga ne-Kata Containers?
-
80,0%Ewe, bhala ngakumbi!28
-
20,0%Hayi, musaβ¦7
Bali-35 abasebenzisi abavotileyo. Abasebenzisi abasi-7 abakhange.
umthombo: www.habr.com