devops:puppet
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| devops:puppet [2016/04/18 09:29] – [Classes Metaparameter] skipidar | devops:puppet [2023/11/01 07:15] (current) – ↷ Page moved from camunda:devops:puppet to devops:puppet skipidar | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Puppet ===== | ===== Puppet ===== | ||
| - | a | + | The Learning VM TUtorial is here: https:// |
| + | |||
| + | Te learning VM is available here: https:// | ||
| + | |||
| ==== Glossary ==== | ==== Glossary ==== | ||
| Line 184: | Line 188: | ||
| * Use **define** keyword instead of **class** | * Use **define** keyword instead of **class** | ||
| * **$title** is a special variable, which must be unique on a node and is mandatory | * **$title** is a special variable, which must be unique on a node and is mandatory | ||
| - | * | + | * Binding of parameter variables ($content, $password) to values happens in parallel, meaning that you cannot use the value of one parameter to set another. The exception is the $title variable. |
| Line 320: | Line 324: | ||
| defines the default node configuration. | defines the default node configuration. | ||
| + | ==== Node setup ==== | ||
| + | |||
| + | Puppet master provides a bash script for setting up nodes: | ||
| + | < | ||
| + | curl -k https://< | ||
| + | </ | ||
| + | |||
| + | Puppet MASTER keeps signed certificates of each Node, which is a part of the infrastructure. | ||
| + | To involve a node - sighn its certificate. | ||
| + | |||
| + | List all unsigned certificates of Nodes. Executable on master. | ||
| + | < | ||
| + | puppet cert list | ||
| + | </ | ||
| + | |||
| + | Sign a certificate of node named **webserver.learning.puppetlabs.vm ** | ||
| + | < | ||
| + | puppet cert sign webserver.learning.puppetlabs.vm | ||
| + | </ | ||
| ==== Variables ==== | ==== Variables ==== | ||
| Line 650: | Line 673: | ||
| yamldir = / | yamldir = / | ||
| </ | </ | ||
| + | |||
| + | |||
| + | |||
| + | ===== Orchestration ===== | ||
| + | |||
| + | Details are here: https:// | ||
| + | |||
| + | Orchestration allows to install dependent applications in the right order. | ||
| + | |||
| + | It works as following: | ||
| + | - setup the node to know the orchestrator | ||
| + | - create an Application, | ||
| + | - setup orchestrator user with the rights | ||
| + | - setup an **artificial, | ||
| + | - define, which node **produces** data to fill artificial, public resource. Which node consumes data from artificial, public resource. | ||
| + | - declare the resource | ||
| + | - in site.pp declare - which part of the application will be installed on which node. | ||
| + | |||
| + | {{http:// | ||
devops/puppet.1460971790.txt.gz · Last modified: (external edit)
