{"id":35972,"date":"2019-10-31T22:08:54","date_gmt":"2019-10-31T19:08:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie\/"},"modified":"2019-10-31T22:08:54","modified_gmt":"2019-10-31T19:08:54","slug":"avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie","title":{"rendered":"Automatiz\u00e1l\u00e1s a legkisebbeknek. Nulla r\u00e9sz. Tervez\u00e9s","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

A SDSM has ended, but the uncontrollable desire to write remains. <\/p>\n

\"Automatiz\u00e1l\u00e1s<\/a><\/noindex><\/p>\n

For many years, our brother suffered from routine work, crossing his fingers before each commit and losing sleep due to nightly rollbacks.
\nBut dark times come to an end.<\/p>\n

With this article, I will start a series on how tudasd velem. Rem\u00e9lem, hogy ez a cikk seg\u00edtett nektek a dolgaikban. Szeretn\u00e9m hinni, hogy miut\u00e1n elolvast\u00e1tok, annyit tanultatok, mint \u00e9n, mik\u00f6zben minden olyan dologgal foglalkoztam, amir\u0151l besz\u00e9ltem benne.<\/i> automation is perceived.
\nAlong the way, we will discuss automation stages, variable storage, design formalization, RestAPI, NETCONF, YANG, YDK, and we will be doing a lot of programming.
\nFor me<\/i> it means that a) this is not an objective truth, b) it is not an unequivocally better approach, c) my view may change even from the first to the last article \u2014 to be honest, from the draft stage to publication, I rewrote everything completely twice. <\/p>\n

<\/a><\/noindex><\/p>\n

Tartalom<\/h1>\n

<\/p>\n

    \n
  1. C\u00e9lok<\/b>\n
      \n
    1. The network is like a single organism<\/li>\n
    2. Configuration testing<\/li>\n
    3. Verzi\u00f3kezel\u00e9s<\/li>\n
    4. Monitoring and self-healing of services<\/li>\n<\/ol>\n

      \n <\/li>\n

    5. Tools<\/b>\n
        \n
      1. Inventory system<\/li>\n
      2. IP space management system<\/li>\n
      3. Network service description system<\/li>\n
      4. Device initialization mechanism<\/li>\n
      5. Vendor-agnostic configuration model<\/li>\n
      6. Vendor-specific driver interface<\/li>\n
      7. Configuration delivery mechanism to the device<\/li>\n
      8. CI\/CD<\/li>\n
      9. Backup mechanism and anomaly detection<\/li>\n
      10. Monitoring system<\/li>\n<\/ol>\n

        \n <\/li>\n

      11. Z\u00e1r\u00e1s<\/b>\n <\/li>\n<\/ol>\n

        \nI will try to lead the ADSM format a bit differently from SDSM. There will still be substantial numbered articles appearing, and between them, I will publish brief notes from daily experiences. I will try to battle my perfectionism here and not polish each of them too much. <\/p>\n

        How funny it is to have to walk the same path a second time.<\/p>\n

        Initially, I had to write articles about networks myself because there weren't any on the Russian-speaking internet.<\/p>\n

        Now I couldn't find a comprehensive document that systematized approaches to automation and examined the aforementioned technologies through simple practical examples.<\/p>\n

        I might be wrong, so feel free to throw links to useful resources. However, this won't change my determination to write, because the main goal is still to learn something myself, and making life easier for others is a nice bonus that enhances the spread of knowledge.\n<\/p><\/blockquote>\n

        We will attempt to take a medium-sized data center, LAN DC, and work through the entire automation scheme.
        \nI will do some things almost for the first time together with you. <\/p>\n

        A le\u00edr\u00e1sban szerepl\u0151 \u00f6tletekben \u00e9s eszk\u00f6z\u00f6kben nem leszek eredeti. Dmitrij Figolj sz\u00e1m\u00e1ra kiv\u00e1l\u00f3 csatorn\u00e1ja van a t\u00e9m\u00e1ban folytatott k\u00f6zvet\u00edt\u00e9sekhez.<\/a><\/noindex>.
        \n A cikkek sok szempontb\u00f3l metszik egym\u00e1st. \n<\/p><\/blockquote>\n

        A LAN DC 4 adatk\u00f6zponttal, k\u00f6r\u00fclbel\u00fcl 250 switch-csel, f\u00e9l tucat routerrel \u00e9s p\u00e1r t\u0171zfallal rendelkezik.
        \nNem Facebook, de elegend\u0151 ahhoz, hogy m\u00e9lyen elgondolkodjunk az automatiz\u00e1l\u00e1sr\u00f3l.
        \nAz a v\u00e9lem\u00e9ny terjedt el, hogy ha t\u00f6bb mint 1 eszk\u00f6z\u00f6d van, m\u00e1r sz\u00fcks\u00e9ges az automatiz\u00e1l\u00e1s.
        \nVal\u00f3j\u00e1ban neh\u00e9z elk\u00e9pzelni, hogy valaki mostan\u00e1ban \u00e9lhet an\u00e9lk\u00fcl, hogy legal\u00e1bb egy csomag scriptet ne haszn\u00e1ljon.
        \nB\u00e1r hallottam olyan c\u00e9gekr\u0151l, ahol az IP-c\u00edmek nyilv\u00e1ntart\u00e1sa Excelben t\u00f6rt\u00e9nik, \u00e9s az ezer h\u00e1l\u00f3zati eszk\u00f6z mindegyik\u00e9t manu\u00e1lisan \u00e1ll\u00edtj\u00e1k be, k\u00fcl\u00f6n\u00e1ll\u00f3 konfigur\u00e1ci\u00f3kkal. Ezt persze modern m\u0171v\u00e9szetk\u00e9nt lehetne el\u0151adni, de egy m\u00e9rn\u00f6k \u00e9rz\u00e9sei biztosan megs\u00e9rt\u0151dn\u00e9nek. <\/p>\n

        C\u00e9lok<\/h1>\n

        \nMost maxim\u00e1lisan absztrakt c\u00e9lokat fogunk kit\u0171zni:<\/p>\n