{"id":1697,"date":"2025-06-19T11:38:37","date_gmt":"2025-06-19T09:38:37","guid":{"rendered":"https:\/\/virtualguru.cz\/?p=1697"},"modified":"2025-06-26T11:18:03","modified_gmt":"2025-06-26T09:18:03","slug":"vcf9-a-co-je-noveho","status":"publish","type":"post","link":"https:\/\/virtualguru.cz\/en\/2025\/06\/19\/vcf9-a-co-je-noveho\/","title":{"rendered":"VCF 9 and What's new"},"content":{"rendered":"

17th June Broadcom officially make available new version of VMware Cloud Foundation (VCF) with the version number 9. SO all of the components switched to version 9. All include vCenter, ESX hosts and also NSX and Aria Suite, which is now VCF Operations and VCF Automation. For this version all of us were waiting since its announcement in August 2024 on VMware Explore in Las Vegas.<\/p>\n

Let's have a look on the main things, which came with this version.<\/p>\n

Licensing<\/h1>\n

Asi t\u00edm nejz\u00e1sadn\u011bj\u0161\u00edm, co se zm\u011bnilo je licencov\u00e1n\u00ed. Dlouhou dobu jsme byli u VMware zvykl\u00ed, \u017ee se licence \u0159e\u0161ily formou licen\u010dn\u00edho kl\u00ed\u010de, kter\u00fd sest\u00e1val z 25 znak\u016f ve skupin\u00e1ch po 5. V tomto licen\u010dn\u00edm kl\u00ed\u010di se skr\u00fdvalo v\u0161e. Od produktu, edice, verze, po\u010dtu a\u017e po p\u0159\u00edpadn\u00e9 ukon\u010den\u00ed platnosti, pokud se jednalo o \u010dasov\u011b omezen\u00fd kl\u00ed\u010d. S p\u0159echodem k Broadcom se nejprve zm\u011bnil zp\u016fsob licencov\u00e1n\u00ed. Licence ji\u017e nebyly trval\u00e9, ale kupovaly se jako Subscripce. Licence m\u011bly omezenou platnost, kter\u00e1 korelovala s platnost\u00ed subscripce. Kdy\u017e vypr\u0161ela subscripce, musel se vym\u011bnit i licen\u010dn\u00ed kl\u00ed\u010d.<\/p>\n

S verz\u00ed 9 se ud\u00e1la dal\u0161\u00ed zm\u011bna. Od te\u010f ji\u017e nejsou licen\u010dn\u00ed kl\u00ed\u010de jak jsme je znali dlouhou dobu, ale p\u0159ech\u00e1z\u00ed se na licen\u010dn\u00ed soubory. Nejprve si ale mus\u00edte VCF Operations zaregistrovat na port\u00e1lu https:\/\/vcf.broadcom.com<\/a>. Bu\u010f m\u00e1te p\u0159\u00edmo p\u0159\u00edstup online a toto se provede „automaticky“, nebo si nech\u00e1te na VCF Operations vygenerovat registra\u010dn\u00ed soubor, kter\u00fd zaregistrujete na port\u00e1lu a vygeneruje se V\u00e1m „Activation Code“, kter\u00fd zase zp\u011bt nahrajete na VCF Operation. N\u00e1sledn\u011b si vyberete kter\u00e9 licence chcete pro sv\u00e9 prost\u0159ed\u00ed p\u0159idat a vygenerujete licen\u010dn\u00ed soubor a nahrajete do VCF Operations.\u00a0 V tomto licen\u010dn\u00edm souboru jsou pak v\u0161echny licence, kter\u00e9 m\u00e1te zakoupen\u00e9 a p\u0159i\u0159azen\u00e9 jednomu prost\u0159ed\u00ed. Tento licen\u010dn\u00ed soubor m\u00e1 v sob\u011b i otisk pro kter\u00e9 prost\u0159ed\u00ed byl vygenerov\u00e1n. Tak\u017ee nem\u016f\u017eete stejn\u00fd licen\u010dn\u00ed soubor pou\u017e\u00edt na v\u00edce prost\u0159ed\u00edch.<\/p>\n

Pozitivum je, \u017ee Eval perioda se zv\u00fd\u0161ila na 90 dn\u016f.<\/p>\n

Negativum je, \u017ee VCF Operations pos\u00edl\u00e1 \u00fadaje do Broadcom ohledn\u011b licence usage. Pokud nem\u00e1 p\u0159\u00edstup do internetu, mus\u00edte se manu\u00e1ln\u011b postarat o p\u0159esun Usage Reportu z Ops do VCF port\u00e1lu a to ka\u017ed\u00fdch max. 180 dn\u00ed.<\/p>\n

\"\"<\/a> \"\"<\/a> \"\"<\/a><\/center><\/p>\n

Instalace<\/h1>\n

Instalaci cel\u00e9ho prost\u0159ed\u00ed st\u00e1le je\u0161t\u011b m\u016f\u017eete d\u011blat tak jak jste byli zvykl\u00ed. Nainstalovat ESX hosty, nainstalovat vCenter Server, Operations, NSX …<\/p>\n

Ale nov\u011b je tu je\u0161t\u011b nov\u00e1 metoda a ta je doporu\u010dovan\u011bj\u0161\u00ed. Vyu\u017e\u00edt VCF Installer. K n\u011bmu se dostanete po deploymentu SDDC manager appliance. Nyn\u00ed u\u017e tato appliance slou\u017e\u00ed jen k instalaci. Pokud vyu\u017eijete VCF installer, m\u00e1te jistotu, \u017ee se v\u0161echny komponenty nainstaluj\u00ed ve spr\u00e1vn\u00fdch konfigurac\u00edch, budou spr\u00e1vn\u011b prov\u00e1z\u00e1ny a deployment prob\u00edh\u00e1 v souladu s Validated Designem.<\/p>\n

\"\"<\/a> \"\"<\/a><\/center><\/p>\n

Nejprve je t\u0159eba si st\u00e1hnout bal\u00ed\u010dky pro jednotliv\u00e9 komponenty. To m\u016f\u017eete ud\u011blat Online, pokud m\u00e1te p\u0159\u00edstup do internetu. Abyste si je v\u0161ak mohli st\u00e1hnout, mus\u00edte m\u00edt vygenerovan\u00fd download token. Ten pak zad\u00e1te v konfiguraci Online Depot. Pro prost\u0159ed\u00ed, kter\u00e1 nemaj\u00ed p\u0159\u00edm\u00fd p\u0159\u00edstup do internetu je k dispozici i mo\u017enost si st\u00e1hnout tyto bal\u00edky pomoc\u00ed Download Utility a nahr\u00e1t „ru\u010dn\u011b“.<\/p>\n

Posl\u00e9ze si vyberete, jestli budete instalovat VVF, nebo VCF. VVF obsahuje jen ESX, vCenter, vSAN a VCF Operations. VCF pak nav\u00edc i NSX a VCF Automation.<\/p>\n

Sou\u010d\u00e1st\u00ed installeru je i mo\u017enost vyu\u017eit\u00ed st\u00e1vaj\u00edc\u00edho vCenter, Operations, NSX pro upgrade a p\u0159echod na plnohodnotn\u00e9 VCF.<\/p>\n

\"\"<\/a> \"\"<\/a><\/center><\/p>\n

M\u016f\u017eete si vybrat instalaci s vysokou dostupnost\u00ed, kdy se provede deployment NSX manageru, VCF Automation a VCF Operations v clusterov\u00e9m proveden\u00ed. Nebo bez HA, kter\u00e9 je vhodn\u00e9 pro men\u0161\u00ed prost\u0159ed\u00ed, nebo jako testovac\u00ed, PoC apod.<\/p>\n

Z d\u016fvodu bezpe\u010dnosti si m\u016f\u017eete i nechat automaticky vygenerovat root\/admin hesla. Ta si pak na konci m\u016f\u017eete vyt\u00e1hnout a ulo\u017eit do V\u00e1mi preferovan\u00e9ho password manageru.<\/p>\n

\"\"<\/a><\/center><\/p>\n

https:\/\/techdocs.broadcom.com\/us\/en\/vmware-cis\/vcf\/vcf-9-0-and-later\/9-0\/release-notes\/vmware-cloud-foundation-90-release-notes\/platform-whats-new\/whats-new-installer.html<\/a><\/p>\n

vSphere<\/h1>\n

Memory Tiering – d\u00edky rychl\u00fdm NVMe za\u0159\u00edzen\u00edm m\u016f\u017eete nav\u00fd\u0161it pou\u017eitelnou pam\u011bt v serveru. V NVMe se ulo\u017e\u00ed m\u00e9n\u011b pou\u017e\u00edvan\u00e1 \u010d\u00e1st a DRAM pak slou\u017e\u00ed jako rychlej\u0161\u00ed cache. St\u00e1le je to ale rychlej\u0161\u00ed ne\u017e SWAP na remote datastore. NVMe za\u0159\u00edzen\u00ed jsou sice pomalej\u0161\u00ed ne\u017e DRAM, ale zase jsou p\u0159i stejn\u00e9 kapacit\u011b levn\u011bj\u0161\u00ed. D\u00edky tomu m\u016f\u017eete opravdu velk\u00e9 VM provozovat na levn\u011bj\u0161\u00edm HW. Aktu\u00e1ln\u011b je limit na pou\u017eit\u00ed Memory Tieringu na maxim\u00e1ln\u011b 400% DRAM. Limity jsou i na n\u011bkter\u00e9 funkcionality, kter\u00e9 nem\u016f\u017eete pou\u017e\u00edvat p\u0159i Memory Tieringu.<\/p>\n

Mixed HW v r\u00e1mci jednoho clusteru pro Desired Image update. S t\u00edm, jak n\u00e1m Update Manager odch\u00e1z\u00ed do hlubin zapomn\u011bn\u00ed, tak jsme m\u011bli jeden velk\u00fd limit nastupuj\u00edc\u00edho LIfeCycle Manageru. T\u00edm byl cluster ve kter\u00e9m jsme m\u011bli mix host\u016f od r\u016fzn\u00fdch vendor\u016f. V r\u00e1mci Desired Image jste mohli nakonfigurovat jen jedno vendor roz\u0161\u00ed\u0159en\u00ed, ovlada\u010de apod., v clusteru. Co ale kdy\u017e m\u00e1me Stretched Cluster a chceme jej ud\u011blat vendor agnostic? Do te\u010f to byl probl\u00e9m. Nyn\u00ed s verz\u00ed vSphere 9 ale ji\u017e m\u016f\u017eeme vyhov\u011bt i takov\u00e9muto po\u017eadavku a nastavit v\u00edce Vendor Add-On roz\u0161\u00ed\u0159en\u00ed na jednom clusteru.<\/p>\n

vHW 22<\/p>\n

960 vCPU
\nSecurity: AMD-SEV-SNP, Intel TDX
\n4Kn VMDK
\nvNVMe verze 1.4
\nhttps:\/\/techdocs.broadcom.com\/us\/en\/vmware-cis\/vsphere\/vsphere\/9-0\/vsphere-virtual-machine-administration\/configuring-virtual-machine-hardwarevsphere-vm-admin\/virtual-machine-compatibilityvsphere-vm-admin\/hardware-features-available-with-virtual-machine-compatibility-levelsvsphere-vm-admin.html<\/a><\/p>\n

Boot from NVMe\/FC<\/p>\n

https:\/\/techdocs.broadcom.com\/us\/en\/vmware-cis\/vcf\/vcf-9-0-and-later\/9-0\/release-notes\/vmware-cloud-foundation-90-release-notes\/platform-whats-new\/whats-new-vsphere.html<\/a><\/p>\n

vSAN<\/h1>\n

S vSAN se n\u00e1m to p\u0159evrac\u00ed do konfigurac\u00ed ESA, kter\u00e9 budou do budoucna hr\u00e1t prim. Roz\u0161i\u0159uj\u00ed se n\u00e1m funkce a OSA upad\u00e1. Nav\u00edc Hybridn\u00ed konfigurace bude do budoucna deprecated a bude se po\u010d\u00edtat jen s All-Flash konfiguracemi.<\/p>\n

vSAN p\u0159ich\u00e1z\u00ed s func\u00ed Glob\u00e1ln\u00ed deduplikace. Ta je ale zat\u00edm k dispozici pouze na vy\u017e\u00e1d\u00e1n\u00ed supportu.<\/p>\n

Nav\u00fd\u0161ily se ale po\u010dty FileShares a\u017e na 500. Plat\u00ed to jen pro ESA konfiguraci a pro NFS shares, nikoli pro SMB.<\/p>\n

Nov\u00e1 funkcionalita vSAN to vSAN replikace s RPO 1 min. P\u0159i vyu\u017eit\u00ed VMware Live Recovery<\/p>\n

https:\/\/techdocs.broadcom.com\/us\/en\/vmware-cis\/vcf\/vcf-9-0-and-later\/9-0\/release-notes\/vmware-cloud-foundation-90-release-notes\/platform-whats-new\/whats-new-vsan.html<\/a><\/p>\n

NSX<\/h1>\n

NSX roz\u0161i\u0159uje koncept VPC (Virtual Private Cloud).<\/p>\n

NSX p\u0159i konfiguraci transportn\u00edho nodu m\u00e1 nyn\u00ed jako v\u00fdchoz\u00ed volbu Enhanced Data Path – Standard. D\u00edky tomu se v\u00fdkon switchingu i routingu v\u00fdrazn\u011b zv\u00fd\u0161\u00ed. Pot\u0159ebujete k tomu, ale m\u00edt odpov\u00eddaj\u00edc\u00ed s\u00ed\u0165ov\u00e9 karty, kter\u00e9 maj\u00ed ovlada\u010de podporuj\u00edc\u00ed EDP – Interrupt<\/p>\n

https:\/\/compatibilityguide.broadcom.com\/search?program=io&persona=live&column=brandName&order=asc&ioDeviceType=%5BNetwork%5D&features=%5BEnhanced+Data+Path+-+Interrupt+mode%5D&activePage=1&activeDelta=20<\/a><\/p>\n

Konfigurace NSX m\u016f\u017ee ji\u017e b\u00fdt sou\u010d\u00e1st\u00ed vSphere profilu, co\u017e je n\u00e1stupce Host Profil\u016f. vSphere profily jsou JSON form\u00e1tovan\u00e9 konfigurace, kter\u00e9 obsahuj\u00ed rozd\u00edly oproti v\u00fdchoz\u00edmu nastaven\u00ed. V r\u00e1mci vSphere profilu nyn\u00ed m\u016f\u017ee b\u00fdt i odkaz na NSX Transport Node Profil, kter\u00fd se m\u00e1 pou\u017e\u00edt.<\/p>\n

NSX VIB bal\u00ed\u010dky jsou sou\u010d\u00e1st\u00ed ESX a podporuj\u00ed LivePatching, kter\u00fd p\u0159i\u0161el s verz\u00ed ESX 8.0U3.<\/p>\n

Pro zjednodu\u0161en\u00ed overlay s\u00edt\u00ed m\u016f\u017ee b\u00fdt vyu\u017eit st\u00e1vaj\u00edc\u00ed VMKernel port. P\u0159i importu do VCF se nap\u0159\u00edklad automaticky pou\u017eije vmk0 – management port – pro vyu\u017eit\u00ed jakoTunel Endpoint. D\u00edky tomu se m\u00e1 u\u0161et\u0159it mno\u017estv\u00ed IP, kter\u00e9 je pro vytvo\u0159en\u00ed cel\u00e9ho prost\u0159ed\u00ed pot\u0159eba, proto\u017ee se m\u016f\u017ee stejn\u00fd VMkernel port vyu\u017e\u00edt pro v\u00edce slu\u017eeb sou\u010dasn\u011b.<\/p>\n

https:\/\/techdocs.broadcom.com\/us\/en\/vmware-cis\/vcf\/vcf-9-0-and-later\/9-0\/release-notes\/vmware-cloud-foundation-90-release-notes\/platform-whats-new\/whats-new-nsx.html<\/a><\/p>\n

VCF Operations<\/h1>\n

VCF Operations je nyn\u00ed jako jedna z nutn\u00fdch komponent, jeliko\u017e se p\u0159es n\u011bj zad\u00e1vaj\u00ed i licence na v\u0161echny produkty. Ty u\u017e nejsou jako 25znakov\u00fd \u0159et\u011bzec, ale jako licen\u010dn\u00ed soubory a pravideln\u011b se kontroluj\u00ed proti VCF port\u00e1lu – mus\u00ed se nejpozd\u011bji ka\u017ed\u00fdch 180 dn\u00ed poslat usage report.<\/p>\n

Fleet Management<\/h1>\n

Valn\u00e1 \u010d\u00e1st funkc\u00ed, kter\u00e9 byly p\u0159edt\u00edm v SDDC manageru se p\u0159esunuly do VCF Operations, konkr\u00e9tn\u011b do \u010d\u00e1sti Fleet Management. Jedn\u00e1 se o Password Management, Certificate Managementu a dal\u0161\u00ed.<\/p>\n

\"\"<\/a> \"\"<\/a> \"\"<\/a><\/center><\/p>\n

Zm\u011bnil se i zp\u016fsob prov\u00e1z\u00e1n\u00ed mezi Management a Workload dom\u00e9nou. Ji\u017e se upou\u0161t\u00ed od vyu\u017eit\u00ed Enhanced Linked Mode (ELM) a vyu\u017e\u00edv\u00e1 se nov\u00fd zp\u016fsob pr\u00e1v\u011b p\u0159es Fleet Management. Pro autentizaci je mo\u017eno vyu\u017e\u00edt nov\u00fd Identity Broker, kter\u00fd pak umo\u017e\u0148uje ov\u011b\u0159ov\u00e1n\u00ed i do ostatn\u00edch komponent jako je vCenter, NSX. Tento identity broker m\u016f\u017ee b\u00fdt sou\u010d\u00e1st\u00ed vCenter serveru, nebo jako samostatn\u00e1 appliance.<\/p>\n

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

CO ji\u017e nen\u00ed<\/h1>\n

Jsou ale i v\u011bci, kter\u00e9 ji\u017e nejsou.<\/p>\n

    \n
  1. Update manager a Baseline update – nahrazeno Lifecycle Managerem a Desired Image<\/li>\n
  2. Cloud Builder Appliance – nahrazeno VCF Installer<\/li>\n
  3. Intergrated Windows Authentication<\/li>\n
  4. VMware Update Manager Download Service – integrov\u00e1no do VCF Download Tool<\/li>\n
  5. Intel Optane PMEM – pou\u017eijte Memory Tiering<\/li>\n
  6. vSphere Trust Authority<\/li>\n
  7. vShield Endpoint<\/li>\n
  8. Aria Operations for Logs<\/li>\n<\/ol>\n

    Deprecated – zat\u00edm jsou, ale u\u017e nebudou do budoucna<\/p>\n

      \n
    1. vSphere Auto Deploy<\/li>\n
    2. vSAN OSA hybrid configurations<\/li>\n
    3. vSAN over RDMA<\/li>\n
    4. Enhanced Linked Mode – nahrazov\u00e1no Fleet SSO<\/li>\n
    5. Host profiles – nahrazeno vSphere Profiles<\/li>\n
    6. vSphere Virtual Volumes<\/li>\n
    7. vCenter Profiles<\/li>\n
    8. VLANCE, VMXNET2 s\u00ed\u0165ovky – hodn\u011b star\u00e9<\/li>\n
    9. VMFSSparse delta format – od vSphere 9 se pou\u017e\u00edv\u00e1 ji\u017e jen SEsparse.<\/li>\n<\/ol>\n

      Kompletn\u00ed seznam si m\u016f\u017eete naj\u00edt v dokumentaci zde: https:\/\/techdocs.broadcom.com\/us\/en\/vmware-cis\/vcf\/vcf-9-0-and-later\/9-0\/release-notes\/vmware-cloud-foundation-90-release-notes\/platform-product-support-notes.html<\/a><\/p>","protected":false},"excerpt":{"rendered":"

      17. 6. 2025 Broadcom ofici\u00e1ln\u011b vydal novou verzi VMware Cloud Foundation (VCF) s ozna\u010den\u00edm 9. Na verzi 9 se tedy posunulo v\u0161e. Od vCenter serveru,<\/p>\n

      Continue ReadingVCF 9 and What's new<\/span> <\/i><\/a><\/div>","protected":false},"author":4,"featured_media":1701,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"iawp_total_views":598,"footnotes":""},"categories":[50,64,5,3],"tags":[6,59,81,65,44,13,9],"class_list":["post-1697","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nsx","category-vcf","category-vsan","category-vsphere","tag-esxi","tag-nsx","tag-nvme","tag-vcf","tag-vmware","tag-vsan","tag-vsphere","entry"],"_links":{"self":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/comments?post=1697"}],"version-history":[{"count":12,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1697\/revisions"}],"predecessor-version":[{"id":1739,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1697\/revisions\/1739"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media\/1701"}],"wp:attachment":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media?parent=1697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/categories?post=1697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/tags?post=1697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}