Puppet Classes

 • Classes are named blocks of Puppet code that are stored in modules for later use and are not applied until they are invoked by name

• They can be added to a node’s catalog by either declaring them in your manifests or assigning them from an ENC

• Classes generally configure large or medium-sized chunks of functionality, such as all of the packages, config files, and services needed to run an application

• Classes are containers of different resources. Since Puppet 2.6 they can have parameters


Example of Class

class mysql ( root_password => 'default_value', port => '3306', ) 

{ package { 'mysql-server': ensure => present, } 

service { 'mysql': ensure => running, } [...] } 

Note : that when we define a class we just describe what it does and what parameters it has, we don't actually add it and its resources to the catalog.


Defining Classes

# A class with no parameters 

class base::linux 

{ file { '/etc/passwd': owner => 'root', group => 'root', mode => '0644', }

 file { '/etc/shadow': owner => 'root', group => 'root', mode => '0440', } 

}


Defining Classes

# A class with parameters 

class apache (String $version = 'latest') 

{ package {'httpd': ensure => $version, # Using the class parameter from above before => File['/etc/httpd.conf'], } 

file {'/etc/httpd.conf': ensure => file, owner => 'httpd', content => template('apache/httpd.conf.erb'), # Template from a module } 

service {'httpd': ensure => running, enable => true, subscribe => File['/etc/httpd.conf'], } 

}


Class Parameters & Variables

• Parameters allow a class to request external data. If a class needs to configure itself with data other than facts, that data should usually enter the class via a parameter

• Each class parameter can be used as a normal variable inside the class definition

• The values of these variables are not set with normal assignment statements or looked up from top or node scope; instead, they are set based on user input when the class is declared

• If a class parameter lacks a default value, the module’s user must set a value themselves

• You should supply defaults wherever possible

• Each parameter can be preceded by an optional data type

• If included, Puppet will check the parameter’s value at runtime to make sure that it has the right data type, and raise an error if the value is illegal

• If no data type is provided, the parameter will accept values of any data type

• The special variables $title and $name are both set to the class name automatically, so they can’t be used as parameters


Class Location

• Class definitions should be stored in modules. Puppet is automatically aware of classes in modules and can autoload them by name.

• Classes should be stored in their module’s manifests/ directory as one class per file, and each filename should reflect the name of its class

• A class definition statement isn’t an expression and can’t be used where a value is expected.

Comments

Post a Comment

Popular posts from this blog

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more