Puppet Modules

 • Modules are self-contained bundles of code and data with a specific directory structure

• These reusable, shareable units of Puppet code are a basic building block for Puppet

• Modules must have a valid name and be located in modulepath

• Puppet automatically loads all content from every module in modulepath making classes, defined types, and plug-ins (such as custom types or facts) available

• You can download and install modules written by Puppet or the Puppet community from the Puppet Forge


Module Structure

• Modules have a specific directory structure that allows Puppet to find and automatically load classes, defined types, facts, custom types and providers, functions, and tasks

• Module names should contain only lowercase letters, numbers, and underscores, and should begin with a lowercase letter

• Each manifest in a module’s manifests folder should contain only one class or defined type

• You can serve files in a module’s files directory to agent nodes

• Any ERB or EPP template can be rendered in a manifest


Exercise  - Puppet Modules

 Go to master terminal window and run the following command

cd /etc/puppet/modules

puppet module generate reuseable-module

 This will start guiding you how to create your module. Leave source code repository blank and generate the meta data required for module.

 Go to the master terminal and under folder /etc/puppet/modules/reuseable-module. You will see a lot of files that support the development of your module

 Go to the folder /etc/puppet/modules/reuseable-module/manifests. In that you will see an init.pp. Edit this file

nano init.pp

class reuseable-module {

notify {“This is the reusable module”: }

}

 Go to the master terminal and /etc/puppet/modules/reusable-module/tests. Edit the init.pp file in this folder

include reuseable-module

 Close the file and go to tests folder under the module reusable-module and open init.pp and apply from this folder

include reuseable-module

puppet apply init.pp

 Next we will download a module from Puppet Forge and apply it to agent

 Go to Puppet Forge and search for module apache. Download it to /etc/puppet/modules folder on Puppet Master by using following command

puppet module install puppetlabs-apache --version 2.3.0

 This will create 3 folders – apache, concat and stdlib under your modules folders

 Go back to your reusable-module and under manifests open the init.pp file and add the following code to the class

include apache

 Now go to the test folder and run

puppet apply init.pp

 This will install apache on the master

Comments

Post a Comment

Popular posts from this blog

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 and services.
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 without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more