{"id":1414,"date":"2023-02-21T10:27:15","date_gmt":"2023-02-21T09:27:15","guid":{"rendered":"https:\/\/virtualguru.cz\/?p=1414"},"modified":"2024-11-27T17:08:09","modified_gmt":"2024-11-27T16:08:09","slug":"configstore-cli","status":"publish","type":"post","link":"https:\/\/virtualguru.cz\/en\/2023\/02\/21\/configstore-cli\/","title":{"rendered":"Configstore CLI"},"content":{"rendered":"

Tak jsem se musel pustit do hloubkov\u00e9 „kontroly“ ESX hosta verze 8. Jeliko\u017e jsem p\u0159ipravoval Lab na \u0161kolen\u00ed vSphere Whats New 8, tak jsem si pomohl vyklonov\u00e1n\u00edm nainstalovan\u00fdch nested host\u016f. Probl\u00e9m nastal s n\u011bkter\u00fdmi konfiguracemi, kter\u00e9 byly stejn\u00e9, resp. stejn\u011b \u0161patn\u00e9. V grafice to vid\u011bt nebylo, ale kdy\u017e jsem zkou\u0161el pou\u017e\u00edt novinku ve verzi 8, co\u017e je Cluster Desired State Configuration, projevilo se to. Je to d\u00e1no t\u00edm, \u017ee konfigurace ji\u017e nejsou ulo\u017eeny v pouh\u00fdch souborech (\/etc\/vmware\/esx.conf), ale od verze 7.0U2 jsou ulo\u017eeny v ConfigStore viz. vSphere Release notes<\/a>.<\/p>\n

Probl\u00e9m nast\u00e1v\u00e1, pokud chcete n\u011bco z toho zm\u011bnit. Nen\u00ed to nemo\u017en\u00e9, akor\u00e1t to chce trochu upravit syst\u00e9m my\u0161len\u00ed a p\u0159ej\u00edt z klasick\u00e9ho Linuxov\u00e9ho, kdy ve\u0161ker\u00e9 konfigurace jsou v souborech, do „program\u00e1torsk\u00e9ho“ kdy se upravuj\u00ed konfigurace p\u0159es API a JSON.<\/p>\n

Klasick\u00fd p\u0159\u00edstup p\u0159es esxcli tuto zm\u011bnu reflektuje, ale jsou n\u011bkter\u00e9 v\u011bci, kter\u00e9 i tak p\u0159es ESXCLI vid\u011bt nejsou. Konkr\u00e9tn\u00ed p\u0159\u00edklad, kter\u00fd mne potkal, se t\u00fdkal ulo\u017een\u00e9 konfigurace standardn\u00edch switch\u016f a jejich vazby na fyzick\u00e9 uplinky. Pokud ale ty uplinky v serveru u\u017e neexistovaly, tak ESXCLI je nezobrazovalo. Pokud jsem se ale pod\u00edval do ConfigStore, tak tam st\u00e1le je\u0161t\u011b byly zm\u00edn\u011bny a pak to d\u011blalo probl\u00e9my.<\/p>\n

Jak toto vy\u0159e\u0161it? William Lam u\u017e o tom napsal nejeden blogpost<\/a>. Stejn\u011b tak i Duncan Epping zde<\/a>. Poj\u010fme se ale pod\u00edvat na konkr\u00e9tn\u00ed p\u0159\u00edklad a proj\u00edt si, jak to po\u0159e\u0161it.<\/p>\n

Nejprve se mus\u00edme pod\u00edvat na strukturu ConfigStore. Ten je rozd\u011blen na sekce CurrentConfig, DesiredState, Default.<\/p>\n

Jedin\u00e1 \u010d\u00e1st, ve kter\u00e9 m\u016f\u017eete d\u011blat zm\u011bny je current.<\/p>\n

Pro p\u0159\u00edstup do configStore je p\u0159\u00edmo na ESXi hostu p\u0159\u00edkaz configstorecli<\/strong><\/p>\n

Nejprve je t\u0159eba pochopit jak se s p\u0159\u00edkazem configstorecli pracuje. Nejjednodu\u0161\u0161\u00ed je pou\u017e\u00edt n\u00e1pov\u011bdu za ka\u017edou \u010d\u00e1st\u00ed p\u0159\u00edkazu „-h“ nebo „–help“<\/p>\n

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

Jak je vid\u011bt ze screenshotu, tak pro konfiguraci m\u00e1me mo\u017enost pou\u017e\u00edt „get“,“set“,“update“,“delete“.<\/p>\n

Rozd\u00edl mezi Update a Set je zejm\u00e9na v nevyjmenovan\u00fdch \u010d\u00e1stech konfigurac\u00ed. Pokud pou\u017eiji Update, tak nevyjmenovan\u00e9 \u010d\u00e1sti se nezm\u011bn\u00ed, pokud Set, tak se sma\u017eou, resp p\u0159evedou do n\u011bjak\u00e9ho default nastaven\u00ed.<\/p>\n

Pro v\u0161echny ale pot\u0159ebujeme zn\u00e1t konkr\u00e9tn\u00ed \u010d\u00e1st (adresu) kterou budeme cht\u00edt upravovat, m\u011bnit, vytv\u00e1\u0159et apod. Toto n\u00e1m umo\u017en\u00ed adresace pomoc\u00ed -c (component) -g (group) a -k (key). Zjistit to nejjednodu\u0161eji m\u016f\u017eeme pomoc\u00ed v\u00fdpisu sch\u00e9matu. Op\u011bt pomoc\u00ed configstorecli.<\/p>\n

configstorecli schema list<\/pre>\n
Je\u0161t\u011b l\u00e9pe<\/p>\n
configstorecli schema list > \/vmfs\/volumes\/DatastoreName\/configstore-schema.json<\/pre>\n
Proto\u017ee pak si m\u016f\u017eete vygenerovan\u00fd JSON soubor st\u00e1hnout z datastore a zobrazit si jej v lok\u00e1ln\u00edm textov\u00e9m editoru, kter\u00fd um\u00ed i zv\u00fdraz\u0148ov\u00e1n\u00ed JSON syntaxe.<\/p>\n
\"\"<\/a><\/p>\n
Kdy\u017e u\u017e v\u00edme, jak m\u00e1me adresovat jednotliv\u00e9 konfigurace, tak si je m\u016f\u017eeme nechat vypsat.<\/p>\n
Nap\u0159\u00edklad:<\/p>\n
configstorecli config current get -c esx -g network_vss -k switches > \/vmfs\/volumes\/DatastoreName\/netconfig.json<\/pre>\n
\"\"<\/a><\/p>\n
Pokud bychom v tom cht\u011bli d\u011blat n\u011bjak\u00e9 zm\u011bny, tak samoz\u0159ejm\u011b op\u011bt p\u0159esm\u011brovat v\u00fdstup do souboru a ten upravovat.<\/p>\n
Jedna z v\u011bc\u00ed, na kter\u00e9 je t\u0159eba si d\u00e1t pozor, aby na konci \u0159\u00e1dku nebyly zbyte\u010dn\u00e9 \u010d\u00e1rky, pokud nen\u00e1sleduje dal\u0161\u00ed polo\u017eka, a aby soubor neza\u010d\u00ednal a nekon\u010dil symboly „[„, „]“ pokud na vstupu nen\u00ed konfigurace pole objekt\u016f.<\/p>\n
P\u0159\u00edklad souboru k \u00faprav\u011b:<\/p>\n
\"\"<\/a><\/p>\n
Jakmile m\u00e1me upraveno, tak pot\u0159ebujeme tuto konfiguraci nahr\u00e1t do ESXi hosta. K tomu n\u00e1m op\u011bt poslou\u017e\u00ed configstorecli, tentokr\u00e1t s p\u0159\u00edkazem „set“, nebo „update“. Rozd\u00edl viz v\u00fd\u0161e.<\/p>\n
P\u0159\u00edklad:<\/p>\n
configstorecli config current set -c esx -g network_vss -k switches -infile \/vmfs\/volumes\/DatastoreName\/netconfig.json<\/pre>\n
\"\"<\/a>Tak snad V\u00e1m to do budoucna pom\u016f\u017ee, pokud budete n\u011bkdy hledat probl\u00e9my v konfigurac\u00edch a n\u00e1sledn\u011b se je sna\u017eit opravit.<\/p>","protected":false},"excerpt":{"rendered":"
Tak jsem se musel pustit do hloubkov\u00e9 „kontroly“ ESX hosta verze 8. Jeliko\u017e jsem p\u0159ipravoval Lab na \u0161kolen\u00ed vSphere Whats New 8, tak jsem si<\/p>\n
Continue ReadingConfigstore CLI<\/span> <\/i><\/a><\/div>","protected":false},"author":4,"featured_media":1417,"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":14,"footnotes":""},"categories":[18,3],"tags":[47,58,32,6,11,9],"class_list":["post-1414","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-automatizace","category-vsphere","tag-api","tag-configstore","tag-esxcli","tag-esxi","tag-troubleshooting","tag-vsphere","entry"],"_links":{"self":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1414","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=1414"}],"version-history":[{"count":12,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1414\/revisions"}],"predecessor-version":[{"id":1658,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/posts\/1414\/revisions\/1658"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media\/1417"}],"wp:attachment":[{"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/media?parent=1414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/categories?post=1414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualguru.cz\/en\/wp-json\/wp\/v2\/tags?post=1414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}