{"id":37551,"date":"2019-10-31T22:18:16","date_gmt":"2019-10-31T19:18:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/govorim-o-devops-na-ponyatnom-yazyke\/"},"modified":"2019-10-31T22:18:16","modified_gmt":"2019-10-31T19:18:16","slug":"govorim-o-devops-na-ponyatnom-yazyke","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/govorim-o-devops-na-ponyatnom-yazyke","title":{"rendered":"Flasim p\u00ebr DevOps n\u00eb nj\u00eb gjuh\u00eb t\u00eb kuptueshme","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

A \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb kap\u00ebsh thelbin, duke folur p\u00ebr DevOps? Ne kemi mbledhur p\u00ebr ju analogji t\u00eb dukshme, formulime godit\u00ebse dhe k\u00ebshilla nga ekspert\u00eb q\u00eb do t'ju ndihmojn\u00eb t\u00eb arrini thelbin edhe p\u00ebr ata q\u00eb nuk jan\u00eb specialist\u00eb. N\u00eb fund, nj\u00eb bonus \u2013 DevOps-in e punonj\u00ebsve t\u00eb Red Hat.<\/p>\n

\"Flasim
\n
\nTermi DevOps u shfaq 10 vjet m\u00eb par\u00eb dhe ka kaluar nga nj\u00eb hashtag n\u00eb Twitter n\u00eb nj\u00eb l\u00ebvizje kulturore t\u00eb fuqishme n\u00eb bot\u00ebn e IT-s\u00eb, nj\u00eb filozofi reale q\u00eb inkurajon zhvilluesit t\u00eb arrijn\u00eb rezultate m\u00eb shpejt, t\u00eb eksperimentojn\u00eb dhe t\u00eb p\u00ebrparojn\u00eb me metod\u00ebn e iteracioneve. DevOps \u00ebsht\u00eb b\u00ebr\u00eb nj\u00eb koncept i pandash\u00ebm me transformimin digjital. Por si\u00e7 ndodh shpesh me terminologjin\u00eb e IT-s\u00eb, gjat\u00eb nj\u00eb dekade DevOps ka mbledhur shum\u00eb definicione, interpretime dhe keqkuptime mbi vete.
\n<\/a><\/noindex>
\nPrandaj, shpesh her\u00eb p\u00ebr DevOps mund t\u00eb d\u00ebgjosh pyetje si, a \u00ebsht\u00eb e nj\u00ebjta gj\u00eb me agile? Apo \u00ebsht\u00eb nj\u00eb metodologji e ve\u00e7ant\u00eb? Apo \u00ebsht\u00eb vet\u00ebm nj\u00eb sinonim tjet\u00ebr p\u00ebr fjal\u00ebn \"bashk\u00ebpunim\"?<\/p>\n

DevOps p\u00ebrfshin shum\u00eb koncepte t\u00eb ndryshme (d\u00ebrges\u00eb t\u00eb vazhdueshme, integrim t\u00eb vazhduesh\u00ebm, automatizim etj.), prandaj t\u00eb nxjerr\u00ebsh thelbin mund t\u00eb jet\u00eb e v\u00ebshtir\u00eb, sidomos kur je i interesuar p\u00ebr tem\u00ebn. Megjithat\u00eb, kjo aft\u00ebsi \u00ebsht\u00eb shum\u00eb e dobishme, pavar\u00ebsisht n\u00ebse p\u00ebrpiqeni t\u00eb komunikoni idet\u00eb tuaja me menaxhimin ose thjesht po tregoni p\u00ebr pun\u00ebn tuaj ndokujt nga familja ose shok\u00ebt. Prandaj, deri at\u00ebher\u00eb, do t\u00eb largohemi nga nuancat terminologjike t\u00eb DevOps dhe do t\u00eb p\u00ebrqendrohemi n\u00eb pamjen e p\u00ebrgjithshme.<\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb DevOps: 6 definime dhe analogji<\/h3>\n

\nNe i kemi k\u00ebrkuar specialist\u00ebve t\u00eb shpjegojn\u00eb thelbin e DevOps sa m\u00eb thjesht dhe shkurt, n\u00eb m\u00ebnyr\u00eb q\u00eb vler\u00ebsimi i saj t\u00eb b\u00ebhet i qart\u00eb p\u00ebr lexuesin me \u00e7do nivel p\u00ebrgatitjeje teknike. Si rezultat i k\u00ebtyre bisedave, ne zgjodh\u00ebm analogjit\u00eb m\u00eb t\u00eb dukshme dhe formulimet godit\u00ebse, t\u00eb cilat do t'ju ndihmojn\u00eb t\u00eb nd\u00ebrtoni rr\u00ebfimin tuaj p\u00ebr DevOps.<\/p>\n

1. DevOps \u2013 \u00ebsht\u00eb nj\u00eb l\u00ebvizje kulturore<\/h4>\n

\n\"DevOps \u2013 \u00ebsht\u00eb nj\u00eb l\u00ebvizje kulturore, n\u00eb t\u00eb cil\u00ebn t\u00eb dy pal\u00ebt (zhvilluesit e softuerit dhe specialist\u00ebt e operacioneve t\u00eb sistemeve IT) pranojn\u00eb se softueri nuk ka vler\u00eb reale deri sa dikush t\u00eb filloj\u00eb ta p\u00ebrdor\u00eb at\u00eb: klient\u00eb, konsumator\u00eb, punonj\u00ebs, \u00ebsht\u00eb e pap\u00ebrcaktuar, \u2013 thot\u00eb Evelina Oehrlich, analiste e lart\u00eb-hetuese n\u00eb Institutin DevOps. \u2013 Prandaj, k\u00ebto dy pal\u00eb s\u00eb bashku ofrojn\u00eb d\u00ebrges\u00ebn e shpejt\u00eb dhe cil\u00ebsore t\u00eb softuerit.\"<\/p>\n

2. DevOps \u2013 ajo q\u00eb fuqizon zhvilluesit<\/h4>\n

\n\u00abDevOps u jep zhvilluesve fuqin\u00eb p\u00ebr t\u00eb menaxhuar aplikacionet, p\u00ebr t'i nisur ato dhe p\u00ebr t\u00eb menaxhuar dor\u00ebzimin nga fillimi deri n\u00eb fund\u00bb<\/b><\/p>\n

\u00abZakonisht flitet p\u00ebr DevOps si nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb p\u00ebrshpejtuar dor\u00ebzimin e aplikacioneve n\u00eb prodhim p\u00ebrmes krijimit dhe zbatimit t\u00eb proceseve automatike, \u2013 thot\u00eb Jai Schniepp, drejtori p\u00ebr platformat DevOps t\u00eb kompanis\u00eb s\u00eb sigurimeve Liberty Mutual. \u2013 Por p\u00ebr mua \u00ebsht\u00eb nj\u00eb gj\u00eb shum\u00eb m\u00eb themelore. DevOps i jep zhvilluesve fuqin\u00eb p\u00ebr t\u00eb menaxhuar aplikacionet ose pjes\u00eb t\u00eb caktuara t\u00eb softuerit, p\u00ebr t'i nisur ato dhe p\u00ebr t\u00eb menaxhuar dor\u00ebzimin nga fillimi deri n\u00eb fund. DevOps eleminon konfuzionin me p\u00ebrgjegj\u00ebsit\u00eb dhe drejton t\u00eb gjith\u00eb pjes\u00ebmarr\u00ebsit n\u00eb proces drejt krijimit t\u00eb nj\u00eb infrastrukture t\u00eb automatizuar dhe t\u00eb menaxhuar nga zhvilluesi.\u00bb<\/p>\n

3. DevOps \u00ebsht\u00eb bashk\u00ebpunim n\u00eb krijimin dhe dor\u00ebzimin e aplikacioneve<\/h4>\n

\n\u00abN\u00eb terma t\u00eb thjesht\u00eb, DevOps \u00ebsht\u00eb nj\u00eb qasje p\u00ebr prodhimin dhe dor\u00ebzimin e softuerit, kur t\u00eb gjith\u00eb punojn\u00eb s\u00eb bashku\u00bb, \u2013 thekson Gur Staff, president dhe lider i automatizimit t\u00eb biznesit digital n\u00eb kompanin\u00eb BMC.<\/p>\n

4. DevOps \u00ebsht\u00eb nj\u00eb linj\u00eb prodhimi<\/h4>\n

\n\u00abMontimi n\u00eb linj\u00eb \u00ebsht\u00eb i mundur vet\u00ebm n\u00ebse t\u00eb gjitha pjes\u00ebt i p\u00ebrshtaten nj\u00ebra-tjetr\u00ebs\u00bb.<\/b><\/p>\n

\u00abDo ta krahasoja DevOps me nj\u00eb linj\u00eb prodhimi automjetesh, \u2013 vazhdon Gur Staff. \u2013 Ideja \u00ebsht\u00eb t\u00eb projektohen dhe prodhohen t\u00eb gjitha pjes\u00ebt paraprakisht, n\u00eb m\u00ebnyr\u00eb q\u00eb m\u00eb pas t\u00eb mund t\u00eb assemblehen pa nevoj\u00ebn p\u00ebr p\u00ebrshtatje individuale. Montimi n\u00eb linj\u00eb \u00ebsht\u00eb i mundur vet\u00ebm n\u00ebse t\u00eb gjitha pjes\u00ebt i p\u00ebrshtaten nj\u00ebra-tjetr\u00ebs. Ata q\u00eb projektuan dhe prodhuan motorin duhet t\u00eb mendojn\u00eb se si ta bashkangjisin at\u00eb n\u00eb karrocerin\u00eb ose korniz\u00ebn. Ata q\u00eb prodhojn\u00eb frenat duhet t\u00eb mendojn\u00eb p\u00ebr rrotat, dhe k\u00ebshtu me radh\u00eb. Po ashtu duhet t\u00eb jet\u00eb edhe me softin. <\/p>\n

Zhvilluesi q\u00eb krijon logjik\u00ebn e biznesit ose nd\u00ebrfaqen e p\u00ebrdoruesit duhet t\u00eb mendoj\u00eb p\u00ebr baz\u00ebn e t\u00eb dh\u00ebnave q\u00eb ruan informacion mbi klient\u00ebt, p\u00ebr masat e siguris\u00eb p\u00ebr mbrojtjen e t\u00eb dh\u00ebnave t\u00eb p\u00ebrdoruesve, si dhe p\u00ebr m\u00ebnyr\u00ebn se si do t\u00eb funksionoj\u00eb gjith\u00e7ka kur sh\u00ebrbimi t\u00eb filloj\u00eb t\u00eb sh\u00ebrbej\u00eb nj\u00eb audienc\u00eb t\u00eb madhe, ndoshta madje edhe miliona p\u00ebrdorues.\u00bb<\/p>\n

\u00abT\u00eb b\u00ebsh q\u00eb njer\u00ebzit t\u00eb bashk\u00ebpunojn\u00eb dhe t\u00eb mendojn\u00eb p\u00ebr ato pjes\u00eb t\u00eb pun\u00ebs q\u00eb kryhen nga t\u00eb tjer\u00ebt, dhe jo t\u00eb p\u00ebrqendrohen ekskluzivisht n\u00eb detyrat e tyre, \u00ebsht\u00eb pengesa m\u00eb e madhe q\u00eb duhet tejkaluar. N\u00ebse \u00ebsht\u00eb e suksesshme, ju keni nj\u00eb mund\u00ebsi t\u00eb shk\u00eblqyer p\u00ebr transformimin digjital\u00bb, shton Gur Staf.<\/p>\n

5. DevOps \u00ebsht\u00eb kombinimi i duhur i njer\u00ebzve, proceseve dhe automatizimit<\/h4>\n

\nJane Groll, drejtoresha ekzekutive e Institutit DevOps, ofroi nj\u00eb analogji t\u00eb shk\u00eblqyer p\u00ebr t\u00eb shpjeguar DevOps. Sipas saj, \u00abDevOps \u00ebsht\u00eb si nj\u00eb recet\u00eb gatimi, ku ka tri kategori kryesore p\u00ebrb\u00ebr\u00ebsish: njer\u00ebzit, proceset dhe automatizimi. Shumica e k\u00ebtyre p\u00ebrb\u00ebr\u00ebsve mund t\u00eb merren nga fusha dhe burime t\u00eb tjera: Lean, Agile, SRE, CI\/CD, ITIL, lider\u00ebsia, kultura, mjetet. Sekreti i DevOps, si \u00e7do recet\u00eb e mir\u00eb, \u00ebsht\u00eb se si t'i p\u00ebrzini sakt\u00ebsisht p\u00ebrb\u00ebr\u00ebsit dhe t\u00eb b\u00ebni q\u00eb ata t\u00eb rritin shpejt\u00ebsin\u00eb dhe efikasitetin e pun\u00ebs n\u00eb zhvillimin dhe l\u00ebshimin e aplikacioneve\u00bb.<\/p>\n

6. DevOps \u00ebsht\u00eb kur programuesit punojn\u00eb si nj\u00eb ekip Formula 1<\/h4>\n

\n\u00abGarimi planifikohet jo nga starti n\u00eb finish, por anasjelltas, nga finishi n\u00eb start\u00bb.<\/b><\/p>\n

\u00abDuke folur p\u00ebr at\u00eb \u00e7far\u00eb t\u00eb pritet nga iniciativ\u00ebn DevOps, un\u00eb jap si shembull nj\u00eb ekip garash NASCAR ose Formula 1,\u00bb thot\u00eb Chris Short, menaxheri kryesor i marketingut t\u00eb platformave cloud n\u00eb Red Hat dhe botues i buletinit DevOps\u2019ish. \u00abE gjith\u00eb q\u00ebllimi i nj\u00eb ekipi t\u00eb till\u00eb \u00ebsht\u00eb: t\u00eb arrij\u00eb pozitat m\u00eb t\u00eb larta t\u00eb mundshme n\u00eb p\u00ebrfundim t\u00eb gar\u00ebs, duke marr\u00eb parasysh burimet e disponueshme p\u00ebr ekipin dhe sfidat e p\u00ebrballuara. N\u00eb k\u00ebt\u00eb kuptim, gara planifikohet jo nga starti n\u00eb finish, por anasjelltas, nga finishi n\u00eb start. N\u00eb fillim vendoset nj\u00eb q\u00ebllim ambicioz dhe pastaj p\u00ebrcaktohen rrug\u00ebt p\u00ebr ta arritur at\u00eb. M\u00eb pas, ato ndahen n\u00eb n\u00ebnprojekte dhe delegohen an\u00ebtar\u00ebve t\u00eb ekipit\u00bb.<\/p>\n

\u00abGjat\u00eb jav\u00ebs para gar\u00ebs, ekipi p\u00ebrmir\u00ebson pit-stopin. Pjes\u00ebmarr\u00ebsit b\u00ebn\u00eb trajtime fizike dhe kardiovaskulare p\u00ebr t'u mbajtur n\u00eb form\u00eb n\u00eb dit\u00ebn e shterrshme t\u00eb garave. Pjes\u00ebn tjet\u00ebr e ekipit punon p\u00ebr t\u00eb koordinuar veprimet n\u00eb rast t\u00eb ndonj\u00eb problemi q\u00eb mund t\u00eb lind\u00eb gjat\u00eb gar\u00ebs. Po ashtu, ekipi i zhvilluesve duhet t\u00eb st\u00ebrvis\u00eb aft\u00ebsit\u00eb e l\u00ebshimit t\u00eb shpesht\u00eb t\u00eb versioneve t\u00eb reja. Me k\u00ebto aft\u00ebsi dhe nj\u00eb sistem sigurie t\u00eb besuesh\u00ebm, l\u00ebshimi i versioneve t\u00eb reja n\u00eb prodhim ndodh m\u00eb shpesh. N\u00eb k\u00ebt\u00eb kuptim, rritja e shpejt\u00ebsis\u00eb n\u00ebnkupton rritjen e siguris\u00eb, - thot\u00eb Short.<\/p>\n

\u00abNuk \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb b\u00ebsh \u2018gj\u00ebrat e duhura\u2019, - shton Short, - por t\u00eb eliminosh sa m\u00eb shum\u00eb gj\u00ebra q\u00eb q\u00ebndrojn\u00eb n\u00eb rrug\u00ebn e rezultatit t\u00eb d\u00ebshiruar. Collaboroni dhe adaptohuni n\u00eb p\u00ebrputhje me reagimet q\u00eb merrni n\u00eb koh\u00eb reale. Programoni p\u00ebr anomali dhe punoni p\u00ebr t\u00eb p\u00ebrmir\u00ebsuar cil\u00ebsin\u00eb p\u00ebr t\u00eb minimizuar ndikimin e tyre n\u00eb p\u00ebrparimin drejt q\u00ebllimit. Kjo \u00ebsht\u00eb pik\u00ebrisht ajo q\u00eb na pret n\u00eb bot\u00ebn DevOps\u00bb.<\/p>\n

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

Si t\u00eb shkall\u00ebzojm\u00eb DevOps: 10 k\u00ebshilla nga ekspert\u00ebt<\/h3>\n

\nDevOps i thjesht\u00eb dhe DevOps n\u00eb mas\u00eb jan\u00eb dy gj\u00ebra krejt\u00ebsisht t\u00eb ndryshme. Ne do t\u00eb tregojm\u00eb se si t\u00eb kaloni barrierat nga i pari n\u00eb t\u00eb dytin.<\/b><\/p>\n

P\u00ebr shum\u00eb organizata, rruga drejt DevOps fillon leht\u00eb dhe k\u00ebndsh\u00ebm. Krijohen ekipe t\u00eb vogla pasionante, proceset e vjetra z\u00ebvend\u00ebsohen me t\u00eb reja dhe sukseset e para nuk vonojn\u00eb t\u00eb vijn\u00eb.<\/p>\n

Fatkeq\u00ebsisht, kjo \u00ebsht\u00eb vet\u00ebm nj\u00eb shk\u00eblqim fals, iluzion progresi, si\u00e7 thot\u00eb Ben Grinnell, drejtori menaxhues dhe drejtuesi i fush\u00ebs s\u00eb teknologjive dixhitale n\u00eb firm\u00ebn e konsulenc\u00ebs North Highland. Fitorja e hershme, sigurisht, jep shpres\u00eb, por nuk ndihmon n\u00eb arritjen e q\u00ebllimit p\u00ebrfundimtar, at\u00eb t\u00eb p\u00ebrdorimit masiv t\u00eb DevOps n\u00eb organizat\u00eb.<\/p>\n

\u00cbsht\u00eb e leht\u00eb t\u00eb shihet se si po formohet nj\u00eb kultur\u00eb ndarjeje n\u00eb \u2018ne\u2019 dhe \u2018ata\u2019.<\/b><\/p>\n

\u00abShum\u00eb shpesh organizatat fillojn\u00eb projekte pionier\u00eb me mendimin se do t\u00eb pave\u00e7ojn\u00eb rrug\u00ebn p\u00ebr DevOps-in masiv, pa menduar n\u00ebse t\u00eb tjer\u00ebt do t\u00eb duan dhe do t\u00eb jen\u00eb n\u00eb gjendje ta ndjekin k\u00ebt\u00eb rrug\u00eb\u00bb, shpjegon Ben Grinnell. \u00abEkipet p\u00ebr t\u00eb realizuar k\u00ebto projekte zakonisht p\u00ebrb\u00ebhen nga \u201cviking\u00ebt\u201d vet\u00ebbesues, t\u00eb cil\u00ebt kan\u00eb b\u00ebr\u00eb di\u00e7ka t\u00eb ngjashme diku tjet\u00ebr, por jan\u00eb t\u00eb rinjt\u00eb n\u00eb organizat\u00ebn tuaj. N\u00eb k\u00ebt\u00eb koh\u00eb, ata inkurajohet t\u00eb thyejn\u00eb dhe shkat\u00ebrrojn\u00eb rregullat q\u00eb mbeten t\u00eb detyrueshme p\u00ebr t\u00eb gjith\u00eb t\u00eb tjer\u00ebt. \u00cbsht\u00eb e leht\u00eb t\u00eb shikohet se si rezulton nj\u00eb kultur\u00eb ndarjeje n\u00eb \u201cne\u201d dhe \u201cata\u201d, e cila pengon transferimin e njohurive dhe aft\u00ebsive\u00bb.<\/p>\n

\u00abDhe ky problem kulturor \u00ebsht\u00eb vet\u00ebm nj\u00eb nga arsyet pse DevOps \u00ebsht\u00eb i v\u00ebshtir\u00eb p\u00ebr t'u shkall\u00ebzuar. Ekipet DevOps p\u00ebrballen me rritjen e v\u00ebshtir\u00ebsive teknike, tipike p\u00ebr kompanit\u00eb q\u00eb po rriten shpejt dhe q\u00eb kan\u00eb b\u00ebr\u00eb nj\u00eb bast n\u00eb teknologjit\u00eb IT\u00bb, thot\u00eb Steve Newman, themelues dhe kryetar i bordit t\u00eb kompanis\u00eb Scalyr.<\/p>\n

\u00abN\u00eb bot\u00ebn e sotme sh\u00ebrbimet ndryshojn\u00eb menj\u00ebher\u00eb sapo shfaqet nevoja. T\u00eb realizosh dhe implementosh funksionalitete t\u00eb reja \u00ebsht\u00eb padyshim e shk\u00eblqyer, por t\u00eb koordinosh k\u00ebt\u00eb proces dhe t\u00eb zgjidh\u00ebsh problemet e p\u00ebrfshira \u00ebsht\u00eb nj\u00eb v\u00ebshtir\u00ebsi serioze\u00bb, shton Steve Newman. \u00abN\u00eb organizatat me rritje shum\u00eb t\u00eb shpejt\u00eb, inxhinier\u00ebt n\u00eb ekipet nd\u00ebr-funksionale luftojn\u00eb p\u00ebr t\u00eb ruajtur mund\u00ebsin\u00eb p\u00ebr t\u00eb ndjekur ndryshimet dhe efektet e k\u00ebtyre ndryshimeve n\u00eb nivelin e var\u00ebsive. M\u00eb shum\u00eb, inxhinier\u00ebt nuk jan\u00eb aspak t\u00eb lumtur kur u hiqet kjo mund\u00ebsi dhe rezultati \u00ebsht\u00eb se u b\u00ebhet m\u00eb e v\u00ebshtir\u00eb p\u00ebr t\u00eb kuptuar natyr\u00ebn e problemeve q\u00eb ndodhin\u00bb.<\/p>\n

Si t\u00eb tejkaloni k\u00ebto v\u00ebshtir\u00ebsi t\u00eb p\u00ebrmendura dhe t\u00eb kaloni n\u00eb p\u00ebrdorimin masiv t\u00eb DevOps n\u00eb nj\u00eb organizat\u00eb t\u00eb madhe? Ekspert\u00ebt rekomandojn\u00eb t\u00eb jeni t\u00eb duruar, edhe n\u00ebse q\u00ebllimi juaj p\u00ebrfundimtar \u00ebsht\u00eb t\u00eb p\u00ebrshpejtoni ciklin e zhvillimit t\u00eb software-it dhe proceset biznesore.<\/b><\/p>\n

1. Mbani mend se ndryshimet n\u00eb kultur\u00eb k\u00ebrkojn\u00eb koh\u00eb.<\/h4>\n

\nJayne Groll, drejtoresha ekzekutive e Institutit DevOps:<\/b> Sipas mendimit tim, zgjerimi i DevOps duhet t\u00eb jet\u00eb po aq gradual dhe iterativ sa zhvillimi agile (dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn mas\u00eb t\u00eb prek\u00eb kultur\u00ebn). N\u00eb Agile dhe DevOps, fokusimi \u00ebsht\u00eb n\u00eb grupe t\u00eb vogla. Por nd\u00ebrsa numri i grupeve rritet dhe integrimi i tyre vijon, kemi gjithnj\u00eb e m\u00eb shum\u00eb njer\u00ebz q\u00eb aplikojn\u00eb metoda t\u00eb reja pune, dhe si pasoj\u00eb, ndodhi nj\u00eb transformim kulturor n\u00eb shkall\u00eb t\u00eb gjer\u00eb.<\/p>\n

2. Kushtoni mjaftuesh\u00ebm koh\u00eb planifikimit dhe zgjedhjes s\u00eb platform\u00ebs<\/h4>\n

\nEran Kinsbruner, evangjelist teknik i kompanis\u00eb Perfecto:<\/b> \u00abP\u00ebr t\u00eb arritur shkall\u00ebzimin, ekipet DevOps n\u00eb fillim duhet t\u00eb m\u00ebsojn\u00eb t\u00eb kombinojn\u00eb proceset tradicionale, mjetet dhe aft\u00ebsit\u00eb, dhe pastaj t\u00eb rrisin ngadal\u00eb secil\u00ebn faz\u00eb t\u00eb ve\u00e7ant\u00eb t\u00eb DevOps dhe ta stabilizojn\u00eb at\u00eb. Gjith\u00e7ka fillon me planifikimin e kujdessh\u00ebm t\u00eb historive t\u00eb p\u00ebrdoruesve dhe flukseve t\u00eb krijimit t\u00eb vler\u00ebs, pas s\u00eb cil\u00ebs vjen faza e programimit t\u00eb softuerit dhe kontrollit t\u00eb versioneve p\u00ebrmes zhvillimit t\u00eb bazuar n\u00eb trunk ose qasjeve t\u00eb tjera m\u00eb t\u00eb p\u00ebrshtatshme p\u00ebr deg\u00ebzimin dhe bashkimin e kodit.\u00bb<\/p>\n

\u00abM\u00eb pas vjen faza e integrimit dhe testimit, ku k\u00ebrkohet tashm\u00eb nj\u00eb platform\u00eb e shkall\u00ebzuar p\u00ebr automatizimin. N\u00eb k\u00ebt\u00eb pik\u00eb, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme p\u00ebr ekipet DevOps t\u00eb zgjedhin platform\u00ebn e duhur q\u00eb do t\u00eb p\u00ebrshtatej me nivelin e tyre t\u00eb aft\u00ebsive dhe synimet p\u00ebrfundimtare t\u00eb projektit. <\/p>\n

Faza e ardhshme \u00ebsht\u00eb shp\u00ebrndarja n\u00eb ambientin e prodhimit, e cila duhet t\u00eb jet\u00eb plot\u00ebsisht e automatizuar duke p\u00ebrdorur mjetet e orkestrimit dhe konteiner\u00ebve. N\u00eb k\u00ebt\u00eb proces, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kemi ambiente t\u00eb virtualizuara n\u00eb t\u00eb gjitha fazat e DevOps (simulator p\u00ebr ambientin e prodhimit, ambient t\u00eb kontrollit t\u00eb cil\u00ebsis\u00eb dhe, n\u00eb fakt, ambientin e prodhimit) dhe gjithmon\u00eb t\u00eb p\u00ebrdorim p\u00ebr provat t\u00eb dh\u00ebnat m\u00eb t\u00eb fundit, p\u00ebr t\u00eb marr\u00eb p\u00ebrfundime t\u00eb sakta. Analitika duhet t\u00eb jet\u00eb inteligjente dhe e aft\u00eb t\u00eb p\u00ebrpunoj\u00eb t\u00eb dh\u00ebnat e m\u00ebdha me nj\u00eb kthim t\u00eb shpejt\u00eb dhe efikas.<\/p>\n

3. \u00c7liro nga p\u00ebrgjegj\u00ebsia e ndjenj\u00ebs s\u00eb fajit<\/h4>\n

\nGordon Haff, evangjelist i RedHat:<\/b> \u00abKrijimi i nj\u00eb sistemi dhe atmosfere q\u00eb lejon dhe inkurajon eksperimente, mund\u00ebson realizimin e ashtuquajturave d\u00ebshtime t\u00eb suksesshme n\u00eb zhvillimin agjil t\u00eb softuerit. Kjo nuk do t\u00eb thot\u00eb q\u00eb askush nuk merr m\u00eb p\u00ebrgjegj\u00ebsi p\u00ebr d\u00ebshtimet. N\u00eb t\u00eb v\u00ebrtet\u00eb, p\u00ebrcaktimi i p\u00ebrgjegj\u00ebsit b\u00ebhet edhe m\u00eb i leht\u00eb, pasi \u201ct\u00eb jesh p\u00ebrgjegj\u00ebs\u201d tani nuk do t\u00eb thot\u00eb \u201ct\u00eb jesh fajtor p\u00ebr aksidentin\u201d. Pra, e thella e p\u00ebrgjegj\u00ebsis\u00eb ndryshon n\u00eb m\u00ebnyr\u00eb cil\u00ebsore. N\u00eb k\u00ebt\u00eb kuptim, kat\u00ebr faktor\u00ebt b\u00ebhen jasht\u00ebzakonisht t\u00eb r\u00ebnd\u00ebsish\u00ebm: shkalla e d\u00ebshtimit, qasjet, proceset e prodhimit dhe stimulimi\u00bb. (M\u00eb shum\u00eb rreth k\u00ebtyre faktor\u00ebve mund t\u00eb lexoni n\u00eb artikullin e Gordon Huff: \u00abM\u00ebsimet DevOps: 4 aspekte t\u00eb eksperimenteve t\u00eb sh\u00ebndetshme\u00bb.)<\/p>\n

4. Hapur rrug\u00ebn p\u00ebrpara<\/h4>\n

\nBen Grinnell, drejtor menaxhues dhe kryesues i teknologjive digjitale n\u00eb firm\u00ebn konsultuese North Highland:<\/b> \u00abP\u00ebr t\u00eb arritur shkall\u00ebzim, rekomandoj q\u00eb s\u00eb bashku me projektet pionier\u00eb t\u00eb nisni nj\u00eb program \u201cpastrimi rruge\u201d. Q\u00ebllimi i k\u00ebtij programi \u00ebsht\u00eb t\u00eb heq\u00eb mbeturinat q\u00eb mbeten pas pionier\u00ebve t\u00eb DevOps, si\u00e7 jan\u00eb rregullat e skaduara dhe gj\u00ebra t\u00eb tjera t\u00eb ngjashme, n\u00eb m\u00ebnyr\u00eb q\u00eb rruga p\u00ebrpara t\u00eb mbetet e hapur\u00bb.<\/p>\n

\u00abJepni mb\u00ebshtetje organizative njer\u00ebzve dhe jepni nxitje p\u00ebrmes komunikimit q\u00eb shkon shum\u00eb p\u00ebrtej grupit t\u00eb pionier\u00ebve, duke festuar gjer\u00ebsisht sukseset e metodave t\u00eb reja t\u00eb pun\u00ebs. Trajnoni njer\u00ebzit q\u00eb jan\u00eb t\u00eb angazhuar n\u00eb val\u00ebn e ardhshme t\u00eb projekteve t\u00eb DevOps dhe q\u00eb jan\u00eb t\u00eb shqet\u00ebsuar sepse po p\u00ebrdorin DevOps p\u00ebr her\u00eb t\u00eb par\u00eb. Dhe mbani mend se k\u00ebta njer\u00ebz jan\u00eb shum\u00eb ndryshe nga pionier\u00ebt\u00bb.<\/p>\n

5. B\u00ebni mjetet m\u00eb demokratike<\/h4>\n

\nSteve Newman, themelues dhe kryetar i bordit t\u00eb kompanis\u00eb Scalyr:<\/b> \u00abMjetet nuk duhet t\u00eb fshihen nga njer\u00ebzit, dhe ato duhet t\u00eb jen\u00eb relativisht t\u00eb thjeshta p\u00ebr t'u m\u00ebsuar p\u00ebr \u00e7do kush q\u00eb \u00ebsht\u00eb i gatsh\u00ebm t\u00eb investoj\u00eb koh\u00eb n\u00eb to. N\u00ebse mund\u00ebsia p\u00ebr t\u00eb k\u00ebrkuar regjistrat u jepet vet\u00ebm tre njer\u00ebzve, \u201ct\u00eb certifikuar\u201d p\u00ebr t\u00eb punuar me ndonj\u00eb mjet, do t\u00eb keni gjithmon\u00eb maksimumi tre persona q\u00eb mund t\u00eb p\u00ebrballen me problemin p\u00ebrkat\u00ebs, madje edhe n\u00ebse keni nj\u00eb ambient t\u00eb shum\u00ebfisht\u00eb llogarit\u00ebs. Me fjal\u00eb t\u00eb tjera, k\u00ebtu formohet nj\u00eb ngushtic\u00eb, q\u00eb mund t\u00eb ket\u00eb pasoja serioze (p\u00ebr biznesin)\u00bb.<\/p>\n

6. Krijoni kushte ideale p\u00ebr pun\u00ebn e ekipit<\/h4>\n

\nTom Clark, udh\u00ebheq\u00ebs i sektorit Common Platform n\u00eb kompanin\u00eb televizive ITV:<\/b> \u00abMund t\u00eb b\u00ebni \u00e7far\u00ebdo, por jo t\u00eb gjitha nj\u00ebher\u00ebsh. Prandaj, vendosni q\u00ebllime t\u00eb m\u00ebdha, filloni nga e vogla dhe l\u00ebvizni p\u00ebrpara me iteracione t\u00eb shpejta. Me kalimin e koh\u00ebs, do t\u00eb fitoni reputacionin e nj\u00eb ekipi q\u00eb arrin rezultatet, k\u00ebshtu q\u00eb t\u00eb tjer\u00ebt gjithashtu do t\u00eb duan t\u00eb p\u00ebrdorin metodat tuaja. Dhe mos u p\u00ebrpiqni t\u00eb krijoni nj\u00eb ekip me performanc\u00eb t\u00eb lart\u00eb. N\u00eb vend t\u00eb k\u00ebsaj, siguroni njer\u00ebzve kushte perfekte p\u00ebr pun\u00eb dhe efikasiteti do t\u00eb vij\u00eb vet\u00eb\u00bb.<\/p>\n

7. Mos harroni ligjin e Conway-it dhe tabelat Kanban<\/h4>\n

\nLogan Daigle, drejtor i dor\u00ebzimit t\u00eb softuerit dhe strategjis\u00eb DevOps n\u00eb CollabNetVersionOne:<\/b> \u00ab\u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptojm\u00eb pasojat e ligjit t\u00eb Conway-it. N\u00eb p\u00ebrmbledhjen time t\u00eb lir\u00eb, ky ligj thot\u00eb se produktet q\u00eb krijojm\u00eb dhe proceset q\u00eb p\u00ebrdorim, p\u00ebrfshir\u00eb DevOps, rezultojn\u00eb t\u00eb strukturuara ashtu si organizata jon\u00eb\u00bb.<\/p>\n

\u00abN\u00ebse organizata ka nj\u00eb ndarje t\u00eb lart\u00eb dhe menaxhimi kalon shum\u00eb her\u00eb nga dora n\u00eb dor\u00eb gjat\u00eb planifikimit, krijimit dhe l\u00ebshimit t\u00eb softuerit, efekti i shkall\u00ebzimit do t\u00eb jet\u00eb zero ose jokoh\u00eb. N\u00ebse organizata formon ekipe nd\u00ebr-funksionale rreth produkteve q\u00eb financohen me orientim ndaj tregut, at\u00ebher\u00eb mund\u00ebsit\u00eb p\u00ebr sukses rriten ndjesh\u00ebm\u00bb.<\/p>\n

\u00abNj\u00eb aspekt tjet\u00ebr i r\u00ebnd\u00ebsish\u00ebm i shkall\u00ebzimit \u00ebsht\u00eb t\u00eb shfaqni n\u00eb tabelat Kanban t\u00eb gjitha pun\u00ebt q\u00eb jan\u00eb n\u00eb proces (WIP, work in progress). Kur n\u00eb organizat\u00eb ka nj\u00eb vend ku njer\u00ebzit mund t\u00eb shohin k\u00ebto gj\u00ebra, kjo nxit shum\u00eb bashk\u00ebpunimin, gj\u00eb q\u00eb ka nj\u00eb efekt pozitiv n\u00eb shkall\u00ebzim\u00bb.<\/p>\n

8. K\u00ebrkoni plag\u00ebt e vjetra<\/h4>\n

\nManuel Pais, konsultant p\u00ebr DevOps dhe bashkautor i librit 'Team Topologies':<\/b> \u00abT\u00eb nxjerr\u00ebsh praktikat DevOps jasht\u00eb vet\u00eb DevOps dhe t\u00eb p\u00ebrpiqesh t'i aplikosh ato n\u00eb funksione t\u00eb tjera v\u00ebshtir\u00eb se mund t\u00eb quhet nj\u00eb qasje optimale. Kjo padyshim do t\u00eb jap\u00eb nj\u00eb efekt t\u00eb caktuar (p\u00ebr shembull, p\u00ebrmes automatizimit t\u00eb menaxhimit manual), por mund t\u00eb arrihet shum\u00eb m\u00eb tep\u00ebr n\u00ebse fillon me kuptimin e proceseve t\u00eb dor\u00ebzimit dhe reagimit\u00bb.<\/p>\n

\u00abN\u00ebse n\u00eb sistemin IT t\u00eb organizat\u00ebs ka shenja t\u00eb vjetra \u2013 procedura dhe mekanizma menaxhimi q\u00eb jan\u00eb zbatuar si rezultat i incidenteve t\u00eb kaluara, por kan\u00eb humbur relevanc\u00ebn (p\u00ebr shkak t\u00eb ndryshimeve n\u00eb produkte, teknologji ose procese), at\u00ebher\u00eb ata patjet\u00ebr duhet t\u00eb hiqen ose t\u00eb sheshohen, e jo t\u00eb automatizohen procese joefektive ose t\u00eb panevojshme\u00bb.<\/p>\n

9. Mos krijoni variante DevOps<\/h4>\n

\nAntony Edwards, drejtor i prodhimit n\u00eb kompanin\u00eb Eggplant:<\/b> \u00abDevOps \u00ebsht\u00eb nj\u00eb term shum\u00eb i paqart\u00eb, ndaj \u00e7do ekipse merr versionin e vet t\u00eb DevOps. Nuk ka gj\u00eb m\u00eb t\u00eb keqe se sa kur n\u00eb nj\u00eb organizat\u00eb krijohen 20 variacione t\u00eb DevOps q\u00eb nuk p\u00ebrputhen mir\u00eb me nj\u00ebra-tjetr\u00ebn. Nuk duhet q\u00eb \u00e7do grup zhvilluesish t\u00eb ket\u00eb nj\u00eb nd\u00ebrfaqe t\u00eb ve\u00e7ant\u00eb mes zhvillimit dhe menaxhimit t\u00eb produktit. Ashtu si nuk duhet q\u00eb produktet t\u00eb ken\u00eb pritshm\u00ebri unike p\u00ebr m\u00ebnyr\u00ebn e trajtimit t\u00eb feedback-ut kur transferohen n\u00eb simulimin e mjedisit t\u00eb prodhimit. P\u00ebrndryshe, asnj\u00ebher\u00eb nuk do t\u00eb mund t\u00eb shkall\u00ebzoni DevOps\u00bb.<\/p>\n

10. Predikoni vler\u00ebn e DevOps p\u00ebr biznesin<\/h4>\n

\nSteve Newman, themelues dhe kryetar i bordit t\u00eb kompanis\u00eb Scalyr:<\/b> \u00abPunoni p\u00ebr njohjen e vler\u00ebs s\u00eb DevOps. M\u00ebsoni dhe mos hezitoni t\u00eb flisni p\u00ebr p\u00ebrfitimin e asaj q\u00eb b\u00ebni. DevOps kursen jasht\u00ebzakonisht koh\u00eb dhe para (mjafton t\u00eb mendoni: m\u00eb pak ndalesa, koh\u00eb m\u00eb e shkurt\u00ebr rikuperimi), dhe ekipet DevOps duhet t\u00eb theksojn\u00eb (dhe t\u00eb predikojn\u00eb) r\u00ebnd\u00ebsin\u00eb e k\u00ebtyre nismave p\u00ebr suksesin e biznesit. K\u00ebshtu, do t\u00eb mund t\u00eb zgjeroni radhet e p\u00ebrkrah\u00ebsve dhe t\u00eb forconi ndikimin e DevOps n\u00eb organizat\u00eb\u00bb.<\/p>\n

BONUS<\/h3>\n

\nN\u00eb Red Hat Forum Russia<\/a><\/noindex> M\u00eb 13 Shtator do t\u00eb vij\u00eb DevOps-i yn\u00eb \u2013 po, Red Hat, si prodhues i softuerit, ka ekipet dhe praktikat e veta t\u00eb DevOps.<\/b><\/p>\n

Inxhinieri yn\u00eb Mark Birger, i cili merret me zhvillimin e sh\u00ebrbimeve t\u00eb automatizimit t\u00eb brendsh\u00ebm p\u00ebr grupe t\u00eb tjera n\u00eb t\u00eb gjith\u00eb organizat\u00ebn, do t\u00eb tregoj\u00eb historin\u00eb e tij n\u00eb nj\u00eb gjuh\u00eb t\u00eb past\u00ebr ruse \u2013 si ekipi DevOps i Red Hat migroi aplikacionet nga ambientet virtuale t\u00eb menaxhuara nga Ansible n\u00eb nj\u00eb format t\u00eb plot\u00eb kontejner\u00ebsh n\u00eb platform\u00ebn OpenShift.<\/p>\n

Por kjo nuk \u00ebsht\u00eb gjith\u00e7ka:<\/b><\/p>\n

Pas pas q\u00eb organizatat transferuan ngarkesat e pun\u00ebs n\u00eb kontejner\u00eb, metodat tradicionale t\u00eb monitorimit t\u00eb aplikacioneve mund t\u00eb mos funksionojn\u00eb. N\u00eb raportin e dyt\u00eb, ne do t\u00eb shpjegojm\u00eb motivimin ton\u00eb p\u00ebr ndryshimin e m\u00ebnyr\u00ebs s\u00eb regjistrimit dhe do t\u00eb tregojm\u00eb vazhdimin e rrug\u00ebs q\u00eb na \u00e7oi n\u00eb metodat moderne t\u00eb regjistrimit dhe monitorimit.
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0422\u0440\u0443\u0434\u043d\u043e \u0443\u043b\u043e\u0432\u0438\u0442\u044c \u0433\u043b\u0430\u0432\u043d\u043e\u0435, \u0433\u043e\u0432\u043e\u0440\u044f \u043e DevOps? \u041c\u044b \u0441\u043e\u0431\u0440\u0430\u043b\u0438 \u0434\u043b\u044f \u0432\u0430\u0441 \u044f\u0440\u043a\u0438\u0435 \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0438, \u0443\u0434\u0430\u0440\u043d\u044b\u0435 \u0444\u043e\u0440\u043c\u0443\u043b\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0441\u043e\u0432\u0435\u0442\u044b \u043e\u0442 \u044d\u043a\u0441\u043f\u0435\u0440\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0434\u043e\u0439\u0442\u0438 \u0434\u043e \u0441\u0443\u0442\u0438 \u0434\u0430\u0436\u0435 \u043d\u0435\u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u0430\u043c. \u0412 \u043a\u043e\u043d\u0446\u0435 \u0431\u043e\u043d\u0443\u0441 \u2013 \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0439 DevOps \u0441\u043e\u0442\u0440\u0443\u0434\u043d\u0438\u043a\u043e\u0432 Red Hat. \u0422\u0435\u0440\u043c\u0438\u043d DevOps \u0432\u043e\u0437\u043d\u0438\u043a 10 \u043b\u0435\u0442 \u043d\u0430\u0437\u0430\u0434 \u0438 \u043f\u0440\u043e\u0448\u0435\u043b \u043f\u0443\u0442\u044c \u043e\u0442 \u0445\u044d\u0448\u0442\u0435\u0433\u0430 \u0432 \u0422\u0432\u0438\u0442\u0442\u0435\u0440\u0435 \u0434\u043e \u043c\u043e\u0449\u043d\u043e\u0433\u043e \u043a\u0443\u043b\u044c\u0442\u0443\u0440\u043d\u043e\u0433\u043e \u0434\u0432\u0438\u0436\u0435\u043d\u0438\u044f \u0432 \u043c\u0438\u0440\u0435 \u0418\u0422, \u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u0439 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28183,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-37551","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\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\n","aioseo_head_json":{"title":"\ud83e\udd47Flasim p\u00ebr DevOps n\u00eb nj\u00eb gjuh\u00eb t\u00eb kuptueshme | ProHoster","description":"\u00cbsht\u00eb e v\u00ebshtir\u00eb t\u00eb kap\u00ebsh thelbin, duke folur p\u00ebr DevOps? Ne kemi mbledhur p\u00ebr ju analogji t\u00eb qarta, formulime godit\u00ebse dhe k\u00ebshilla nga ekspert\u00ebt q\u00eb do t'ju ndihmojn\u00eb t\u00eb arrini thelbin edhe p\u00ebr ata q\u00eb nuk jan\u00eb specialist\u00eb.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/news\/govorim-o-devops-na-ponyatnom-yazyke","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\udd47\u0413\u043e\u0432\u043e\u0440\u0438\u043c \u043e DevOps \u043d\u0430 \u043f\u043e\u043d\u044f\u0442\u043d\u043e\u043c \u044f\u0437\u044b\u043a\u0435 | ProHoster","og:description":"\u0422\u0440\u0443\u0434\u043d\u043e \u0443\u043b\u043e\u0432\u0438\u0442\u044c \u0433\u043b\u0430\u0432\u043d\u043e\u0435, \u0433\u043e\u0432\u043e\u0440\u044f \u043e DevOps? \u041c\u044b \u0441\u043e\u0431\u0440\u0430\u043b\u0438 \u0434\u043b\u044f \u0432\u0430\u0441 \u044f\u0440\u043a\u0438\u0435 \u0430\u043d\u0430\u043b\u043e\u0433\u0438\u0438, \u0443\u0434\u0430\u0440\u043d\u044b\u0435 \u0444\u043e\u0440\u043c\u0443\u043b\u0438\u0440\u043e\u0432\u043a\u0438 \u0438 \u0441\u043e\u0432\u0435\u0442\u044b \u043e\u0442 \u044d\u043a\u0441\u043f\u0435\u0440\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u043c\u043e\u0433\u0443\u0442 \u0434\u043e\u0439\u0442\u0438 \u0434\u043e \u0441\u0443\u0442\u0438 \u0434\u0430\u0436\u0435 \u043d\u0435\u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u0430\u043c.","og:url":"https:\/\/prohoster.info\/sq\/blog\/news\/govorim-o-devops-na-ponyatnom-yazyke","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":"2019-10-31T19:18:16+00:00","article:modified_time":"2019-10-31T19:18:16+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37551","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":"2026-01-23 18:20:51","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:24:25","updated":"2026-01-23 18:20:51","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37551","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=37551"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37551\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28183"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37551"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37551"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37551"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}