{"id":353,"date":"2023-09-14T13:34:08","date_gmt":"2023-09-14T13:34:08","guid":{"rendered":"https:\/\/d-mashina.net\/?p=353"},"modified":"2023-09-14T13:34:13","modified_gmt":"2023-09-14T13:34:13","slug":"migracija-hp-microserver-gen8-iz-rhel7-na-debian12","status":"publish","type":"post","link":"https:\/\/d-mashina.net\/index.php\/2023\/09\/14\/migracija-hp-microserver-gen8-iz-rhel7-na-debian12\/","title":{"rendered":"Migracija HP Microserver Gen8 iz RHEL7 na Debian12"},"content":{"rendered":"

Kar nekaj \u010dasa sem s tem okleval, sej sem na tem doma dodelanem stre\u017eniku, v katerega sem vgradil 32GB RAM in SSD disk, ki ga uporabljam kot OS disk, imel kar precej Docker kontejnerjev in virtualk, ki jih uporabljam pri vsakdanjem delu.<\/p>\n

\"\"\"\"<\/p>\n

Virtualke in kontejnerje imam shranjene na diskovnem polju RAID5, ki je v stre\u017eniku, tako da sem na OS disk brez te\u017eav namestil najnovej\u0161i Debian 12. Zakaj Debian? Na omenjenem stre\u017eniku, je v RHEL svetu uradno z gonilniki HP podprt samo RHEL7, tak oda razli\u010dice 8 in 9 tudi pri RockyLinux ali AlmaLinux nista podprte. Medtem je za Debian 12 na voljo repozitorij, v katerem so HP orodja za delo z RAID krmilnikom in vse ostale HP pritekline.<\/p>\n

Med sources.list je potrebno dodat:<\/p>\n

deb http:\/\/downloads.linux.hpe.com\/SDR\/repo\/mcp bookworm\/current non-free<\/strong><\/p>\n

oz. ustrezno verzijo:<\/p>\n

deb http:\/\/downloads.linux.hpe.com\/SDR\/repo\/mcp bookworm\/12.80 non-free<\/strong><\/p>\n

Namestitev je potekala brez te\u017eav. \u0160e najve\u010d dela sem imel s konfiguracijo mre\u017ee, pri kateri sem dve mre\u017eni kartici dal v “bond” in na bondu za potrebe virtualizacije naredil \u0161e “bridge”.<\/p>\n

auto bond0
\n<\/em>iface bond0 inet static<\/em>
\naddress 10.1.1.5<\/em>
\nnetmask 255.255.255.0<\/em>
\nnetwork 10.1.1.0<\/em>
\ngateway 10.1.1.1<\/em>
\nbond-slaves eno1 eno2<\/em>
\nbond-mode 1<\/em>
\nbond-miimon 100<\/em>
\nbond-downdelay 200<\/em>
\nbond-updelay 200<\/em><\/p>\n

pred tem pa se ne sme pozabiti na namestitev paketa ifenslave<\/p>\n

apt-get install ifenslave<\/strong><\/p>\n

in potem \u0161e bridge sprememba:<\/p>\n

auto eno1<\/em>
\niface eno1 inet manual<\/em>
\nauto eno2<\/em>
\niface eno2 inet manual<\/em>
\nauto bond0<\/em>
\niface bond0 inet manual<\/em>
\nbond-slaves eno1 eno2<\/em>
\nbond-mode 1<\/em>
\nauto br0<\/em>
\niface br0 inet static<\/em>
\naddress 10.1.1.5<\/em>
\nnetmask 255.255.255.0<\/em>
\nnetwork 10.1.1.0<\/em>
\ngateway 10.1.1.1<\/em>
\nbridge_ports bond0<\/em>
\nbridge_stp off<\/em>
\nbridge_fd 0<\/em>
\nbridge_maxwait 0<\/em><\/p>\n

seveda mi je najve\u010d \u010dasa vzelo raziskava, zakaj kljub uporabi bonda, omre\u017ena vmesnika eno1 in eno2 \u0161e vedno dobita DHCP naslov. Te\u017eave je bila v tam, da je bil name\u0161\u010den in skonfiguriran dhcpcd server, po odstranitvi servisa je bond pri\u010del delovat brez te\u017eav.<\/p>\n

Naslednja te\u017eava je bila, da je stre\u017enik ob pove\u010danem prometu ob\u010dasno zamrznil. Seveda je to znana HP te\u017eava, pri kateri je potrebno v BIOS-u stre\u017enika onemogo\u010dit Intel VTd. Virtualizacija bo kljub temu delovala.<\/p>\n

Za potrebe Dockerja sem dodal Docker repozitorije in ga namestil. Spremenil sem konfiguracijsko datoteko \/etc\/docker\/daemon.json, da ka\u017ee na moje diskovno polje.<\/p>\n

Vsebina datoteke:<\/p>\n

{<\/em>
\n“data-root”: “\/virtu01\/dockerlib”,<\/em>
\n“insecure-registries” : [“registry.gitlab.macqo.d-mashina.net”],<\/em>
\n“experimental”: true<\/em>
\n}<\/em><\/p>\n

in dodajanje Dokcer repozitorijev in GPG klju\u010da:<\/p>\n

# Add Docker’s official GPG key:<\/strong>
\nsudo apt-get update<\/strong>
\nsudo apt-get install ca-certificates curl gnupg<\/strong>
\nsudo install -m 0755 -d \/etc\/apt\/keyrings<\/strong>
\ncurl -fsSL https:\/\/download.docker.com\/linux\/debian\/gpg | sudo gpg –dearmor -o \/etc\/apt\/keyrings\/docker.gpg<\/strong>
\nsudo chmod a+r \/etc\/apt\/keyrings\/docker.gpg<\/strong><\/p>\n

# Add the repository to Apt sources:<\/strong>
\necho \\”deb [arch=”$(dpkg –print-architecture)” signed-by=\/etc\/apt\/keyrings\/docker.gpg] https:\/\/download.docker.com\/linux\/debian \\”$(. \/etc\/os-release && echo”$VERSION_CODENAME”)” stable” | \\<\/strong>
\nsudo tee \/etc\/apt\/sources.list.d\/docker.list > \/dev\/null<\/strong>
\nsudo apt-get update<\/strong><\/p>\n

in namestitev Docker programske opreme:<\/p>\n

apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin<\/strong><\/p>\n

Sledila je \u0161e namestitev KVM virtualizacije, po\u017earne pregrade UFW in Cockpita:<\/p>\n

apt install -y qemu-kvm libvirt-daemon libvirt-clients bridge-utils virt-manager<\/strong><\/p>\n

apt install cockpit ufw<\/strong> (za upravljanje z virtualkami v Cockpitu)<\/p>\n

\"\"<\/p>\n

in Cockpit plugin za Docker (ker ne maram Podmana): https:\/\/github.com\/Xantios\/cockpit-docker (enostavna navodila)<\/p>\n

Prenos KVM VM-ov iz RHEL v Debian ni trivialen, da bi samo skopiral VM-e, zato sem preko Cockpita izbral opcijo Import VM, pri \u010demer sem izbral disk na diskovnem polju in uvozil VM. Vse je potekalo brez te\u017eav. Verjetno bi se dalo te\u017eavo re\u0161it \u0161e na enostavnje\u0161i na\u010din, toda tega nisem raziskoval.<\/p>\n

\"\"<\/p>\n

V Cokpit LOG-ih so se ob\u010dasno pojavljale napake, ki so znane pri HP stre\u017enikih in jih re\u0161imo tako, da v \/etc\/default\/grub dodamo vrstico:<\/p>\n

GRUB_CMDLINE_LINUX_DEFAULT=”quiet intel_iommu=igfx_off intremap=off”<\/strong><\/p>\n

Ko namestimo \u0161e vse HP programe in agente, imamo v ILO administraciji prikaz vseh delujo\u010dih komponent.<\/p>\n

\"\"<\/p>\n

Torej na kratko povedano, sem v 4 urah iz RHEL7 stre\u017enika pre\u0161el na Debian 12 stre\u017enik, z najnovej\u0161o KVM (QEMU) in Docker programsko opremo.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Kar nekaj \u010dasa sem s tem okleval, sej sem na tem doma dodelanem stre\u017eniku, v katerega sem vgradil 32GB RAM in SSD disk, ki ga uporabljam kot OS […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[112,10],"tags":[],"class_list":["post-353","post","type-post","status-publish","format-standard","hentry","category-debian","category-linux"],"_links":{"self":[{"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/posts\/353","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/comments?post=353"}],"version-history":[{"count":1,"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/posts\/353\/revisions"}],"predecessor-version":[{"id":361,"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/posts\/353\/revisions\/361"}],"wp:attachment":[{"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/media?parent=353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/categories?post=353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/d-mashina.net\/index.php\/wp-json\/wp\/v2\/tags?post=353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}