Chapter 8. Separating Data from Code Using Hiera
Working through the first seven chapters, you have used the basic structural elements of Puppet in numerous examples and contexts. There has been a quick demonstration of the more advanced language features, and you have a good idea of what distinguishes the manifest writing process in Puppet 4 from the earlier releases.
For all their expressive power, manifests do have some limitations. A manifest that is designed by the principles taught up to this point mixes logic with data. Logic is not only evident in control structures such as if
and else
, but it also just emerges from the network of classes and defines that include and instantiate one another.
However, you cannot configure a machine by just including some generic classes. Many properties of a given system are individual and must be passed as parameters. This can have maintenance implications for a manifest that must accommodate a large number of nodes. This chapter will teach you how to bring order back to such complex code bases. We will also explain how many larger sites structure the codebase as a whole. These will be our final steps in this Puppet Essentials collection:
- Understanding the need for separate data storage
- Structuring configuration data in a hierarchy
- Retrieving and using Hiera values in manifests
- Converting resources to data
- A practical example
- Debugging Hiera lookups
- Implementing the Roles and Profiles Pattern
- TypeScript Essentials
- 深入理解Bootstrap
- 微服務設計原理與架構
- Hadoop+Spark大數據分析實戰
- 征服RIA
- HTML5+CSS3+JavaScript Web開發案例教程(在線實訓版)
- Getting Started with Laravel 4
- 組態軟件技術與應用
- Quantum Computing and Blockchain in Business
- Python機器學習之金融風險管理
- BeagleBone Robotic Projects(Second Edition)
- C語言程序設計實訓教程與水平考試指導
- Arduino電子設計實戰指南:零基礎篇
- PHP典型模塊與項目實戰大全
- Java程序設計(項目教學版)