÷ÈÓ°Ö±²¥

Embora a infraestrutura como c¨®digo seja uma t¨¦cnica relativamente antiga (que destacamos no Radar em 2011), ela se tornou extremamente importante na era moderna da nuvem, em que o ato de configurar a infraestrutura se tornou a aprova??o das instru??es de configura??o para uma plataforma em nuvem. Quando dizemos "como c¨®digo", queremos dizer que todas as boas pr¨¢ticas que aprendemos no mundo do software devem ser aplicadas ¨¤ infraestrutura. Uso do controle de origem, ades?o ao , modulariza??o, manuten??o e uso de testes e implanta??o automatizados s?o pr¨¢ticas fundamentais. Aquelas de n¨®s com profundo conhecimento de software e infraestrutura precisam ter empatia e apoiar colegas que ainda n?o o t¨ºm. Dizer "trate a infraestrutura como c¨®digo" n?o ¨¦ suficiente, precisamos garantir que os aprendizados conquistados com muito esfor?o no mundo do software sejam aplicados de forma consistente em todo o dom¨ªnio da infraestrutura.

We continue to highlight infrastructure as code. This technique treats infrastructure configuration in the same way as code; checking configuration into source control, then carefully pushing changes out to the data center.

The DevOps movement continues to grow, with developers and operations staff working closely together to solve the ¡°software last mile¡± problem. Infrastructure as code is a technique for treating infrastructure configuration in the same way as code; checking it into source control, then using it to push changes out to the data center. In addition to web server, application server and application configuration, we are seeing network configuration treated in the same way. Network switch, firewall and load balancer configuration can be infrastructure as code, and even changed at runtime.

The large number of hosts and devices in a modern datacenter or cloud deployment have made manually installing and configuring infrastructure unwise. Infrastructure as code is an approach whereby infrastructure configuration is scripted or described by files that are stored in version control, and changes are pushed out to the datacenter in a controlled manner. This parallels the discipline of source control and build promotion used in software development, hence ¡®as code¡¯. The two front-running open source tools for infrastructure automation are Chef and Puppet. They both use a textual DSL to script automation. Using this approach provides consistent and repeatable environment changes, reducing the manual effort involved, especially in troubleshooting environmental differences.