{"id":95643,"date":"2020-10-01T13:42:18","date_gmt":"2020-10-01T11:42:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs"},"modified":"2020-10-01T13:42:18","modified_gmt":"2020-10-01T11:42:18","slug":"network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","title":{"rendered":"Network-as-a-Service pre ve\u013ek\u00e9 podniky: netradi\u010dn\u00fd pr\u00edpad","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Network-as-a-Service
\nAko aktualizova\u0165 sie\u0165ov\u00e9 zariadenia na ve\u013ekom podniku bez zastavenia v\u00fdroby<\/i>? <\/i>O rozsiahlej akcii v re\u017eime \u201eoper\u00e1cie na otvorenom srdci\u201c hovor\u00ed <\/i>projektov\u00fd mana\u017e\u00e9r Linxdatacenter Oleg Fedorov.\u00a0<\/strong><\/i>
\n<\/a><\/noindex>
\nV posledn\u00fdch rokoch zaznamen\u00e1vame zv\u00fd\u0161en\u00fd dopyt od z\u00e1kazn\u00edkov po slu\u017eb\u00e1ch s\u00favisiacich so sie\u0165ov\u00fdmi komponentmi IT infra\u0161trukt\u00fary. Potreba konektivity IT syst\u00e9mov, slu\u017eieb, aplik\u00e1ci\u00ed, \u00faloh monitorovania a operat\u00edvneho riadenia biznisu takmer v ka\u017edej oblasti n\u00fati dnes firmy venova\u0165 sie\u0165am vy\u0161\u0161iu pozornos\u0165.\u00a0\u00a0<\/p>\n

Rozsah dopytu \u2013 od zabezpe\u010denia odolnosti siete po vytvorenie a spr\u00e1vu z\u00e1kazn\u00edckych auton\u00f3mnych syst\u00e9mov s obstaran\u00edm blokov IP adresy<\/a>, nastaven\u00edm protokolov smerovania a riaden\u00edm dopravy v s\u00falade s politikami organiz\u00e1ci\u00ed.<\/p>\n

Rastie aj dopyt po komplexn\u00fdch rie\u0161eniach na budovanie a \u00fadr\u017ebu sie\u0165ovej infra\u0161trukt\u00fary, predov\u0161etk\u00fdm zo strany z\u00e1kazn\u00edkov, ktor\u00fdch sie\u0165ov\u00e1 infra\u0161trukt\u00fara sa buduje od z\u00e1kladov alebo je mora\u00e1lne zastaran\u00e1, vy\u017eaduj\u00faca v\u00e1\u017ene modifik\u00e1cie.\u00a0<\/p>\n

Tento trend \u010dasovo zcoincidoval s obdob\u00edm rozvoja a zlo\u017eitosti vlastnej sie\u0165ovej infra\u0161trukt\u00fary Linxdatacenter. Roz\u0161\u00edrili sme geografiu na\u0161ej pr\u00edtomnosti v Eur\u00f3pe prostredn\u00edctvom pripojenia k vzdialen\u00fdm lokalit\u00e1m, \u010do si zase vy\u017eiadalo aj zlep\u0161enie infra\u0161trukt\u00fary siete.\u00a0<\/p>\n

Spolo\u010dnos\u0165 spustila nov\u00fa slu\u017ebu pre klientov, Network-as-a-Service: rie\u0161ime v\u0161etky sie\u0165ov\u00e9 \u00falohy klientov, \u010do im umo\u017e\u0148uje s\u00fastredi\u0165 sa na hlavn\u00fd biznis.<\/p>\n

V lete 2020 sa dokon\u010dil prv\u00fd ve\u013ek\u00fd projekt v tomto smere, o ktorom by sme chceli hovori\u0165.\u00a0<\/p>\n

Na za\u010diatku\u00a0<\/h2>\n

\nVe\u013ek\u00fd priemyseln\u00fd komplex n\u00e1s oslovil s po\u017eiadavkou na moderniz\u00e1ciu sie\u0165ovej \u010dasti infra\u0161trukt\u00fary v jednom z jeho podnikov. Bolo potrebn\u00e9 vymeni\u0165 star\u00e9 zariadenia za nov\u00e9, vr\u00e1tane jadra siete.<\/p>\n

Posledn\u00e1 moderniz\u00e1cia zariaden\u00ed na podniku prebehla pred pribli\u017ene 10 rokmi. Nov\u00e9 vedenie podniku sa rozhodlo zlep\u0161i\u0165 konektivitu, za\u010d\u00ednaj\u00fac aktualiz\u00e1ciou infra\u0161trukt\u00fary na najz\u00e1kladnej\u0161ej, fyzickej \u00farovni.\u00a0<\/p>\n

Projekt bol rozdelen\u00fd na dve \u010dasti: upgrade serverov\u00e9ho parku a sie\u0165ov\u00fdch zariaden\u00ed. My sme sa zodpovedali za druh\u00fa \u010das\u0165.\u00a0<\/p>\n

Z\u00e1kladn\u00e9 po\u017eiadavky na pr\u00e1ce zah\u0155\u0148ali minimaliz\u00e1ciu prestojov v\u00fdrobn\u00fdch liniek podniku po\u010das vykon\u00e1vania pr\u00e1c (a na niektor\u00fdch \u00fasekoch aj \u00fapln\u00e9 vyl\u00fa\u010denie prestojov). Ak\u00e9ko\u013evek zastavenie znamen\u00e1 priamu finan\u010dn\u00fa stratu pre klienta, \u010do sa za \u017eiadnych okolnost\u00ed nesmelo sta\u0165. V s\u00favislosti s prev\u00e1dzkov\u00fdm re\u017eimom objektu 24x7x365, ako aj s \u00fapln\u00fdm nedostatkom pl\u00e1novan\u00fdch prestojov v praxi podniku, pred nami bola dan\u00e1 \u00faloha, v podstate vykona\u0165 oper\u00e1ciu na otvorenom srdci. To sa stalo hlavn\u00fdm rozli\u0161ovac\u00edm znakom projektu.<\/p>\n

Ideme<\/h2>\n

\nPr\u00e1ce boli napl\u00e1novan\u00e9 na princ\u00edpe pohybu od uzlov siete vzdialen\u00fdch od jadra k t\u00fdm bli\u017e\u0161\u00edm, ako aj od menej ovplyv\u0148uj\u00facich v\u00fdrobn\u00e9 l\u00ednie k t\u00fdm, ktor\u00e9 ovplyv\u0148uj\u00fa t\u00fato pr\u00e1cu priamo.\u00a0<\/p>\n

Napr\u00edklad, ak vezmeme uzol siete v oddelen\u00ed predaja, tak v\u00fdpadok spojenia v d\u00f4sledku pr\u00e1c v tomto oddelen\u00ed nijako neovplyvn\u00ed v\u00fdrobu. Tento incident n\u00e1m ako dod\u00e1vate\u013eovi pom\u00f4\u017ee overi\u0165 spr\u00e1vnos\u0165 zvolen\u00e9ho pr\u00edstupu k pr\u00e1ci s tak\u00fdmito uzlami a po jeho korekcii pokra\u010dova\u0165 v \u010fal\u0161\u00edch f\u00e1zach projektu.\u00a0<\/p>\n

Je potrebn\u00e9 nielen vymeni\u0165 uzly a k\u00e1ble v sieti, ale aj spr\u00e1vne nakonfigurova\u0165 v\u0161etky komponenty pre spr\u00e1vnu funkciu rie\u0161enia ako celku. Presne konfigur\u00e1cie sa takto overovali: za\u010d\u00ednaj\u00fac s pr\u00e1cami v odstupe od jadra, sme si akoby d\u00e1vali \u201epr\u00e1vo na chybu\u201c, \u010d\u00edm sme neohrozovali kriticky d\u00f4le\u017eit\u00e9 oblasti pr\u00e1ce podniku.\u00a0<\/p>\n

Ur\u010dili sme z\u00f3ny, ktor\u00e9 neovplyv\u0148uj\u00fa v\u00fdrobn\u00fd proces, ako aj kritick\u00e9 \u00faseky \u2013 dielne, blok nakladania a vykladania, sklady at\u010f. Na k\u013e\u00fa\u010dov\u00fdch \u00fasekoch bolo s klientom dohodnut\u00e9 pr\u00edpustn\u00e9 prestoje pre ka\u017ed\u00fd uzol siete osobitne: od 1 do 15 min\u00fat. \u00daplne sa vyhn\u00fa\u0165 odpojeniu jednotliv\u00fdch uzlov siete nebolo mo\u017en\u00e9, preto\u017ee k\u00e1bel mus\u00ed by\u0165 fyzicky prepnut\u00fd z p\u00f4vodn\u00e9ho zariadenia na nov\u00e9, a po\u010das prep\u00ednania je tie\u017e potrebn\u00e9 rozuzli\u0165 \"bradu\" k\u00e1blov, ktor\u00e1 sa vytvorila po\u010das nieko\u013ek\u00fdch rokov prev\u00e1dzky bez riadneho \u00fasilia (jedna z n\u00e1sledkov outsourcovania pr\u00e1c na mont\u00e1\u017e k\u00e1blov\u00fdch liniek).<\/p>\n

Pr\u00e1ce boli rozdelen\u00e9 do nieko\u013ek\u00fdch f\u00e1z.<\/p>\n

F\u00e1za 1<\/b> \u2013 Audit. Pr\u00edprava a schv\u00e1lenie pr\u00edstupu k pl\u00e1novaniu pr\u00e1c a pos\u00fadenie pripravenosti t\u00edmov: klienta, dod\u00e1vate\u013ea, ktor\u00fd vykon\u00e1va mont\u00e1\u017e, a n\u00e1\u0161ho t\u00edmu.<\/p>\n

F\u00e1za 2<\/b> \u2013 Vypracovanie form\u00e1tu pre vykon\u00e1vanie pr\u00e1c s podrobnou anal\u00fdzou a pl\u00e1novan\u00edm. Zvolili sme form\u00e1t kontroln\u00e9ho zoznamu s presn\u00fdm uveden\u00edm poradia a postupnosti opatren\u00ed, a\u017e po poradie prep\u00ednania patch-k\u00e1blov medzi portami.<\/p>\n

F\u00e1za 3<\/b> \u2013 Vykon\u00e1vanie pr\u00e1c v skrink\u00e1ch, ktor\u00e9 neovplyv\u0148uj\u00fa v\u00fdrobu. Hodnotenie a korekcia doby prestojov pre nasleduj\u00face f\u00e1zy pr\u00e1c.<\/p>\n

F\u00e1za 4<\/b> \u2013 Vykon\u00e1vanie pr\u00e1c v skrink\u00e1ch, ktor\u00e9 priamo ovplyv\u0148uj\u00fa v\u00fdrobu. Hodnotenie a korekcia doby prestojov pre fin\u00e1lnu f\u00e1zu pr\u00e1c.<\/p>\n

F\u00e1za 5<\/b> \u2013 Vykon\u00e1vanie pr\u00e1c v serverovni pri prep\u00ednan\u00ed zost\u00e1vaj\u00faceho vybavenia. Spustenie na smerovan\u00ed na novom jadre.<\/p>\n

F\u00e1za 6<\/b> \u2013 Postupn\u00e9 prep\u00ednanie jadra syst\u00e9mu zo star\u00fdch sie\u0165ov\u00fdch konfigur\u00e1ci\u00ed na nov\u00e9 pre hladk\u00fd prechod cel\u00e9ho komplexu syst\u00e9mu (VLAN, smerovanie a pod.). V tejto f\u00e1ze sme pripojili v\u0161etk\u00fdch pou\u017e\u00edvate\u013eov a preniesli v\u0161etky slu\u017eby na nov\u00e9 vybavenie, skontrolovali spr\u00e1vnos\u0165 pripojenia, uistili sa, \u017ee \u017eiadne z firemn\u00fdch slu\u017eieb neboli preru\u0161en\u00e9, a garantovali, \u017ee v pr\u00edpade ak\u00fdchko\u013evek probl\u00e9mov bud\u00fa priamo s\u00favisie\u0165 s jadrom, \u010do u\u013eah\u010dilo odstra\u0148ovanie mo\u017en\u00fdch por\u00fach a fin\u00e1lne nastavenie.\u00a0<\/p>\n

\u00daprava kabel\u00e1\u017ee<\/h2>\n

\nProjekt sa uk\u00e1zal by\u0165 n\u00e1ro\u010dn\u00fdm aj kv\u00f4li zlo\u017eit\u00fdm p\u00f4vodn\u00fdm podmienkam.\u00a0<\/p>\n

Po prv\u00e9, je to obrovsk\u00e9 mno\u017estvo uzlov a \u010dast\u00ed siete, so zlo\u017eitou topol\u00f3giou a klasifik\u00e1ciou k\u00e1blov pod\u013ea ich \u00fa\u010delu. Tak\u00e9to \"borov\u00e9\" sa museli vy\u0165ahova\u0165 zo skr\u00ed\u0148 a s prec\u00edznos\u0165ou \"upravova\u0165\", aby sme sa zorientovali, ktor\u00fd k\u00e1bel kam vedie.\u00a0<\/p>\n

Vyzeralo to pribli\u017ene takto:<\/p>\n

\"Network-as-a-Service
\ntakto:<\/p>\n

\"Network-as-a-Service
\nalebo takto:\u00a0<\/p>\n

\"Network-as-a-Service
\nPo druh\u00e9, pre ka\u017ed\u00fa podobn\u00fa \u00falohu bolo potrebn\u00e9 pripravi\u0165 s\u00fabor s popisom procesu. \u201eZoberieme k\u00e1bel X z portu 1 star\u00e9ho zariadenia, zapoj\u00edme ho do portu 18 nov\u00e9ho zariadenia.\u201c Znie to jednoducho, ale ke\u010f m\u00e1\u0161 v zdrojov\u00fdch \u00fadajoch 48 plne obsaden\u00fdch portov a taktie\u017e ch\u00fdba mo\u017enos\u0165 odst\u00e1vky (pam\u00e4t\u00e1me si na 24x7x365), jedin\u00fdm v\u00fdchodiskom je pracova\u0165 po blokoch. \u010c\u00edm viac k\u00e1blov sa d\u00e1 vytiahnu\u0165 zo star\u00e9ho zariadenia naraz, t\u00fdm r\u00fdchlej\u0161ie ich mo\u017eno upravi\u0165 a zasun\u00fa\u0165 do nov\u00e9ho sie\u0165ov\u00e9ho \u201e\u017eeleza\u201c, \u010d\u00edm sa vyhne preru\u0161eniam a odst\u00e1vkam v pr\u00e1ci siete.\u00a0<\/p>\n

Preto sme v pr\u00edpravnej f\u00e1ze vykonali rozdelenie siete do blokov \u2013 ka\u017ed\u00fd z nich sa t\u00fdkal ur\u010dit\u00e9ho VLAN. Ka\u017ed\u00fd port (alebo ich podmno\u017eina) na starom zariaden\u00ed predstavoval niektor\u00fd z VLAN v novej topol\u00f3gii siete. Skupinovali sme ich takto: na prv\u00fdch portoch prep\u00edna\u010da sa nach\u00e1dzali pou\u017e\u00edvate\u013esk\u00e9 siete, v strede \u2013 v\u00fdrobn\u00e9 siete, a na posledn\u00fdch \u2013 pr\u00edstupov\u00e9 body a uplinky.\u00a0<\/p>\n

Tak\u00fd pr\u00edstup umo\u017enil vy\u0165ahova\u0165 a upravova\u0165 zo star\u00e9ho zariadenia naraz nie 1 k\u00e1bel, ale 10-15. To nieko\u013ekokr\u00e1t ur\u00fdchlilo pracovn\u00fd proces.\u00a0\u00a0<\/p>\n

Mimochodom, takto vyzeraj\u00fa k\u00e1ble v skriniach po \u00faprave:\u00a0<\/p>\n

\"Network-as-a-Service
\nalebo napr\u00edklad takto:\u00a0<\/p>\n

\"Network-as-a-Service
\nPo dokon\u010den\u00ed 2. etapy sme si urobili prest\u00e1vku na anal\u00fdzu ch\u00fdb a dynamiky projektu. Napr\u00edklad sa hne\u010f uk\u00e1zali drobn\u00e9 nedostatky z d\u00f4vodu nepresnost\u00ed v poskytnut\u00fdch sch\u00e9mach siete (nepresn\u00fd konektor na sch\u00e9me \u2013 nespr\u00e1vne zak\u00fapen\u00fd patch cord a potreba jeho v\u00fdmeny).\u00a0<\/p>\n

Prest\u00e1vka bola nevyhnutn\u00e1, preto\u017ee pri pr\u00e1ci so serverom bola aj mal\u00e1 chyba v procese nepr\u00edpustn\u00e1. Ak je cie\u013eom zabezpe\u010di\u0165 \u010das odst\u00e1vky na \u00faseku siete nie viac ako 5 min\u00fat, nemalo sa to prekro\u010di\u0165. Ak\u00e9ko\u013evek mo\u017en\u00e9 odch\u00fdlky od pl\u00e1nu mali by\u0165 schva\u013eovan\u00e9 s klientom.\u00a0<\/p>\n

Av\u0161ak predbe\u017en\u00e9 pl\u00e1novanie a rozdelenie projektu do blokov umo\u017enili dodr\u017ea\u0165 pl\u00e1novan\u00fd \u010das odst\u00e1vky na v\u0161etk\u00fdch \u00fasekoch, a v mnoh\u00fdch pr\u00edpadoch sa dokonca obi\u0161lo bez neho.\u00a0<\/p>\n

V\u00fdzva doby \u2013 projekt pod COVID-om\u00a0<\/h2>\n

\nBez \u010fal\u0161\u00edch komplik\u00e1ci\u00ed sa v\u0161ak neobi\u0161lo. Samozrejme, jedn\u00fdm z prek\u00e1\u017eok bol koronav\u00edrus.\u00a0<\/p>\n

Pr\u00e1ce se zkomplikovaly, kdy\u017e za\u010dala pandemie, a nebylo mo\u017en\u00e9, aby se na m\u00edst\u011b prac\u00ed na pozemku klienta z\u00fa\u010dastnili v\u0161ichni specialist\u00e9 zapojen\u00ed do procesu. Na m\u00edsto byli p\u0159ipu\u0161t\u011bni pouze zam\u011bstnanci mont\u00e1\u017en\u00ed organizace, a kontrola prob\u00edhala p\u0159es m\u00edstnost v Zoomu \u2013 byli tam s\u00ed\u0165ov\u00fd in\u017een\u00fdr ze strany Linxdatacenter, j\u00e1 jako projektov\u00fd vedouc\u00ed, s\u00ed\u0165ov\u00fd in\u017een\u00fdr ze strany klienta, odpov\u011bdn\u00fd za realizaci prac\u00ed, a t\u00fdm prov\u00e1d\u011bj\u00edc\u00ed mont\u00e1\u017en\u00ed pr\u00e1ce.<\/p>\n

B\u011bhem prac\u00ed vznikaly neo\u010dek\u00e1van\u00e9 probl\u00e9my, a museli jsme prov\u00e1d\u011bt \u00fapravy za chodu. D\u00edky tomu se n\u00e1m poda\u0159ilo rychle p\u0159edch\u00e1zet vlivu lidsk\u00e9ho faktoru (chyby v sch\u00e9matu, chyby v ur\u010den\u00ed stavu aktivity rozhran\u00ed atd.).<\/p>\n

A\u010dkoliv se na za\u010d\u00e1tku projektu zd\u00e1l vzd\u00e1len\u00fd form\u00e1t pr\u00e1ce nezvykl\u00fd, relativn\u011b rychle jsme se p\u0159izp\u016fsobili nov\u00fdm podm\u00ednk\u00e1m a dostali se na fin\u00e1ln\u00ed f\u00e1zi prac\u00ed.\u00a0<\/p>\n

Spustili jsme do\u010dasnou konfiguraci nastaven\u00ed s\u00edt\u011b pro paraleln\u00ed pr\u00e1ci dvou s\u00ed\u0165ov\u00fdch jader \u2013 star\u00e9ho a nov\u00e9ho \u2013 za \u00fa\u010delem zaji\u0161t\u011bn\u00ed plynul\u00e9ho p\u0159echodu. Uk\u00e1zalo se v\u0161ak, \u017ee jedna zbyte\u010dn\u00e1 \u0159\u00e1dka nebyla odstran\u011bna z konfigura\u010dn\u00edho souboru nov\u00e9ho j\u00e1dra, a p\u0159echod se tud\u00ed\u017e neuskute\u010dnil. To n\u00e1s donutilo str\u00e1vit ur\u010dit\u00e9 \u010dasov\u00e9 obdob\u00ed hled\u00e1n\u00edm probl\u00e9mu.\u00a0<\/p>\n

Zjistilo se, \u017ee hlavn\u00ed provoz byl p\u0159en\u00e1\u0161en spr\u00e1vn\u011b, a \u0159\u00edd\u00edc\u00ed provoz nedosahoval uzlu p\u0159es nov\u00e9 j\u00e1dro. D\u00edky jasn\u00e9mu rozd\u011blen\u00ed projektu na f\u00e1ze se n\u00e1m poda\u0159ilo pom\u011brn\u011b rychle identifikovat \u010d\u00e1st s\u00edt\u011b, kde do\u0161lo k pot\u00ed\u017e\u00edm, zjistit p\u0159\u00ed\u010dinu a odstranit ji.\u00a0<\/p>\n

A v\u00fdsledkem<\/h2>\n

\nTechnick\u00e9 z\u00e1v\u011bry projektu\u00a0<\/i><\/p>\n

P\u0159edev\u0161\u00edm bylo vytvo\u0159eno nov\u00e9 j\u00e1dro nov\u00e9 s\u00edt\u011b podniku, pro co\u017e jsme postavili fyzick\u00e1\/logick\u00e1 kruhov\u00e1 zapojen\u00ed. U\u010dinili jsme to tak, aby ka\u017ed\u00fd switch v s\u00edti m\u011bl \u201edruh\u00e9 rameno\u201c. Ve star\u00e9 s\u00edti bylo mnoho switch\u016f p\u0159ipojeno k j\u00e1dru jednou trasou, jedn\u00edm ramenem (uplinkem). Pokud do\u0161lo k jeho p\u0159eru\u0161en\u00ed, switch se stal zcela nedostupn\u00fdm. A pokud bylo p\u0159es jeden uplink p\u0159ipojeno n\u011bkolik switch\u016f, hav\u00e1rie vy\u0159adila z provozu cel\u00fd odd\u011blen\u00ed nebo v\u00fdrobn\u00ed linku podniku.\u00a0<\/p>\n

V nov\u00e9 s\u00edti dokonce ani pom\u011brn\u011b z\u00e1va\u017en\u00fd s\u00ed\u0165ov\u00fd incident nem\u016f\u017ee za \u017e\u00e1dn\u00e9ho sc\u00e9n\u00e1\u0159e \u201epolo\u017eit\u201c celou s\u00ed\u0165 nebo v\u00fdznamnou \u010d\u00e1st jej\u00ed.\u00a0<\/p>\n

90% v\u0161etk\u00fdch sie\u0165ov\u00fdch zariaden\u00ed bolo aktualizovan\u00fdch, mediakonvertory (prevodn\u00edky sign\u00e1lu) boli vyraden\u00e9 z prev\u00e1dzky a zru\u0161en\u00e1 potreba samostatn\u00fdch nap\u00e1jac\u00edch liniek pre nap\u00e1janie zariaden\u00ed pripojen\u00edm k PoE prep\u00edna\u010dom, kde nap\u00e1janie sa realizuje prostredn\u00edctvom Ethernetov\u00fdch k\u00e1blov.\u00a0<\/p>\n

Taktie\u017e boli ozna\u010den\u00e9 v\u0161etky optick\u00e9 spojenia v serverovni a v skriniach na miestach \u2013 na v\u0161etk\u00fdch k\u013e\u00fa\u010dov\u00fdch uzloch zlo\u017eenia. To umo\u017enilo pripravi\u0165 topologick\u00fa sch\u00e9mu zariaden\u00ed a pripojen\u00ed v sieti, ktor\u00e1 odr\u00e1\u017ea jej aktu\u00e1lny stav.\u00a0<\/p>\n

Sch\u00e9ma siete<\/i>
\n\"Network-as-a-Service
\nNajd\u00f4le\u017eitej\u0161\u00ed v\u00fdsledok z technick\u00e9ho h\u013eadiska: dostato\u010dne rozsiahle infrastruktur\u00e1lne pr\u00e1ce boli vykonan\u00e9 r\u00fdchlo, bez naru\u0161enia \u010dinnosti podniku a takmer nepostrehnute\u013ene pre jeho zamestnancov.\u00a0<\/p>\n

Obchodn\u00e9 v\u00fdsledky projektu<\/i><\/p>\n

Pod\u013ea m\u00f4jho n\u00e1zoru, tento projekt je zauj\u00edmav\u00fd predov\u0161etk\u00fdm nie z technick\u00e9ho, ale organiza\u010dn\u00e9ho h\u013eadiska. Zlo\u017eitosti spo\u010d\u00edvali najm\u00e4 v pl\u00e1novan\u00ed a premyslen\u00ed krokov na realiz\u00e1ciu projektov\u00fdch \u00faloh.\u00a0<\/p>\n

\u00daspech projektu umo\u017e\u0148uje hovori\u0165 o tom, \u017ee na\u0161a iniciat\u00edva na rozvoj sie\u0165ov\u00e9ho smerovania v r\u00e1mci portf\u00f3lia slu\u017eieb Linxdatacenter je spr\u00e1vny smer rozvoja spolo\u010dnosti. Odpovedn\u00fd pr\u00edstup k riadeniu projektov, spr\u00e1vna strat\u00e9gia a jasn\u00e9 pl\u00e1novanie n\u00e1m umo\u017enili vykona\u0165 pr\u00e1cu na po\u017eadovanej \u00farovni.\u00a0<\/p>\n

Potvrdenie kvality pr\u00e1ce \u2013 \u017eiados\u0165 od klienta na pokra\u010dovanie poskytovania slu\u017eieb v moderniz\u00e1cii siete na jeho \u010fal\u0161\u00edch miestach v Rusku.
\n
Zdroj: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041a\u0430\u043a \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u043e\u0435 \u043e\u0431\u043e\u0440\u0443\u0434\u043e\u0432\u0430\u043d\u0438\u0435 \u043d\u0430 \u043a\u0440\u0443\u043f\u043d\u043e\u043c \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0438 \u0431\u0435\u0437 \u043e\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0441\u0442\u0432\u0430? \u041e \u043c\u0430\u0441\u0448\u0442\u0430\u0431\u043d\u043e\u043c \u043f\u0440\u043e\u0435\u043a\u0442\u0435 \u0432 \u0440\u0435\u0436\u0438\u043c\u0435 \u00ab\u043e\u043f\u0435\u0440\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0442\u043a\u0440\u044b\u0442\u043e\u043c \u0441\u0435\u0440\u0434\u0446\u0435\u00bb \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442 \u043c\u0435\u043d\u0435\u0434\u0436\u0435\u0440 \u043f\u043e \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044e \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u043c\u0438 Linxdatacenter \u041e\u043b\u0435\u0433 \u0424\u0435\u0434\u043e\u0440\u043e\u0432.\u00a0 \u0412 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043b\u0435\u0442 \u043c\u044b \u043e\u0442\u043c\u0435\u0447\u0430\u0435\u043c \u043f\u043e\u0432\u044b\u0448\u0435\u043d\u043d\u044b\u0439 \u0441\u043f\u0440\u043e\u0441 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a\u043e\u0432 \u043d\u0430 \u0443\u0441\u043b\u0443\u0433\u0438, \u0441\u0432\u044f\u0437\u0430\u043d\u043d\u044b\u0435 \u0441 \u0441\u0435\u0442\u0435\u0432\u044b\u043c \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u043e\u043c \u0418\u0422-\u0438\u043d\u0444\u0440\u0430\u0441\u0442\u0440\u0443\u043a\u0442\u0443\u0440\u044b. \u041f\u043e\u0442\u0440\u0435\u0431\u043d\u043e\u0441\u0442\u044c \u0432 \u0441\u0432\u044f\u0437\u043d\u043e\u0441\u0442\u0438 \u0418\u0422-\u0441\u0438\u0441\u0442\u0435\u043c, \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432, \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439, \u0437\u0430\u0434\u0430\u0447\u0438 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0430 \u0438 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0433\u043e \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0431\u0438\u0437\u043d\u0435\u0441\u043e\u043c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":95644,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-95643","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Sie\u0165 ako slu\u017eba pre ve\u013ek\u00e9 podniky: netradi\u010dn\u00fd pr\u00edpad | ProHoster","description":"Ako aktualizova\u0165 sie\u0165.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Network-as-a-Service \u0434\u043b\u044f \u043a\u0440\u0443\u043f\u043d\u043e\u0433\u043e \u043f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u044f: \u043d\u0435\u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043d\u044b\u0439 \u043a\u0435\u0439\u0441 | ProHoster","og:description":"\u041a\u0430\u043a \u043e\u0431\u043d\u043e\u0432\u0438\u0442\u044c \u0441\u0435\u0442\u0435\u0432\u043e\u0435.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/network-as-a-service-dlya-krupnogo-predpriyatiya-nestandartnyj-kejs","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-10-01T11:42:18+00:00","article:modified_time":"2020-10-01T11:42:18+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"95643","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 11:01:22","updated":"2026-02-08 20:40:13","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/95643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=95643"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/95643\/revisions"}],"predecessor-version":[{"id":158014,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/95643\/revisions\/158014"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/95644"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=95643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=95643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=95643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}