Scribd Logo
Hochladen

Willkommen bei Scribd!

  • ZT Docker Cheat Sheet

    Hochgeladen von

    Midhun K
    54 Ansichten1 Seite
    - Chef, Puppet, Ansible, and NetCONF/RestConf are open-source configuration management tools that allow provisioning and managing remote servers and network devices. - Chef and Puppet use Ruby domains specific languages (DSLs) while Ansible uses YAML. NetCONF and RestConf are based on YANG data models and use HTTP/REST. - Each tool has pros like being agentless (Ansible), easy to use (Ansible), or standard based (NetCONF, RestConf) but also cons like needing agents (Puppet, Chef), steep learning curves (Puppet, Chef, NetCONF), or partial API support (RestConf).

    Originalbeschreibung:

    docker

    Originaltitel

    Zt Docker Cheat Sheet

    Copyright

    © © All Rights Reserved

    Verfügbare Formate

    PDF, TXT oder online auf Scribd lesen

    Stufen Sie dieses Dokument als nützlich ein?

    Sind diese Inhalte unangemessen?

    Dieses Dokument melden
    - Chef, Puppet, Ansible, and NetCONF/RestConf are open-source configuration management tools that allow provisioning and managing remote servers and network devices. - Chef and Puppet use Ruby domains specific languages (DSLs) while Ansible uses YAML. NetCONF and RestConf are based on YANG data models and use HTTP/REST. - Each tool has pros like being agentless (Ansible), easy to use (Ansible), or standard based (NetCONF, RestConf) but also cons like needing agents (Puppet, Chef), steep learning curves (Puppet, Chef, NetCONF), or partial API support (RestConf).

    Copyright:

    © All Rights Reserved
    Als PDF, TXT herunterladen oder online auf Scribd lesen
    Markieren Sie unangemessene Inhalte
    54 Ansichten1 Seite

    ZT Docker Cheat Sheet

    Hochgeladen von

    Midhun K
    - Chef, Puppet, Ansible, and NetCONF/RestConf are open-source configuration management tools that allow provisioning and managing remote servers and network devices. - Chef and Puppet use Ruby domains specific languages (DSLs) while Ansible uses YAML. NetCONF and RestConf are based on YANG data models and use HTTP/REST. - Each tool has pros like being agentless (Ansible), easy to use (Ansible), or standard based (NetCONF, RestConf) but also cons like needing agents (Puppet, Chef), steep learning curves (Puppet, Chef, NetCONF), or partial API support (RestConf).

    Copyright:

    © All Rights Reserved
    Als PDF, TXT herunterladen oder online auf Scribd lesen
    Markieren Sie unangemessene Inhalte
    von 1

    Chef, Puppet, Ansible, NetCONF, RestConf one pager

    About Southbound interface Provisioning language Pros Cons Other


    • Does not require an agent on the
    managed device
    Open-Source tool to install and • Easy to learn YML • At times hard to debug failures
    provision remote servers and SSH YML • Repository of sample playbooks • Refer to documentation needed
    switches in a repeated fashion on git since open-source changes
    • Variable structure to pass
    parameters

    • Requires an agent on the


    • Rich collection of "recopies"
    device being managed
    Open-Source configuration • Strong version control on Git
    • Steep learning curve, if you are
    management tool, focused on ip and SSH with knife Ruby • Programmatic control and
    not familiar with Ruby
    developer or DevOps flexibility
    • May need large code bases and
    complicated Env.

    • Requires an agent on the


    • Mature and well established device being managed
    Ruby (Domain Scripting
    Oldest standard for configuration • Simple install and setup • Ruby/DSL based with higher
    Language (DSL)) which is close
    management. Open-source tool • Complete Web UI learning curve
    to JSON
    • Strong reporting • Code can grow large due to
    DSL

    Easy way to manage a device html i.e.: • Easy to program


    • Requires exposure of API on
    that supports REST and YANG GET • Mature interface to exchange
    the device
    defined data. Commands are http or shttp http://192.168.3.20:8080/open/v1 information youTube
    • Often partial API availability
    over HTTP transport, either from /system1213 • Return values are XML formatted
    a browser or curl and easy to read and parse
    • Data model different from
    NetCONF was originally intended
    • Open Standard and somewhat device to device
    Install, manipulate, and delete
    Multiple: SSH, Simple Object well defined • Require a management box
    the configuration of network XML or JSON formatted Yang
    Access (SOAP), or Transport • Consistent across multiple and not easy to assemble
    devices, hence the name value set
    Layer Security (TLS) devises formatted data models to pass
    NetCONF. It is intended to
    • No CLI dependence back and forth
    exchange YANG data model

    Das könnte Ihnen auch gefallen