Zacchaeus Puppet Template Examples
Suitable for ages 3+
TIP: If you have concerns about the hygiene of making crafts from toilet paper rolls, cut a piece of paper towel roll or gift wrap tube to about the length of a toilet paper roll and use that instead or roll your own tube using cardboard from old cereal boxes or poster board.
TIP: Add a popsicle stick handle to the toilet paper roll crafts to make a puppet.
DLTK's Bible Activities for Kids Zacchaeus Printable Activity Sheets. Click on the link of your choice (below) to print the template. Color as appropriate. Close the template window after printing to return to this screen. Set page margins to zero if you have trouble fitting the template on one page (FILE, PAGE SETUP or FILE, PRINTER SETUP in most browsers). Zacchaeus Climbs the Tree. Link includes free printable for color or b&w Zacchaeus. CKL night 2 craft idea Zacchaeus Climbs the Tree Zacchaeus Climbs the Tree. This 'toy' allows Zaccheus to rise on the string, up into the tree, when a child pulls the two strings gently back and forth. What a great use for this old-timey toy!
TIP: Glue a 2' circle made from cardboard or craft foam to the bottom of a toilet paper roll craft to make cute little pencil holders. (Thanks Monica!)
To turn any of the toilet paper roll crafts into a popsicle stick puppet (without using a toilet paper roll), simply fold the large rectangular template piece over a popsicle stick, pencil or Tongue Depressor and glue/tape on. Then glue/tape on the other pieces the same way you would have done for the toilet paper roll craft.
Toilet Paper Roll bowling: Make 5 toilet paper roll crafts (any theme) and arrange them like bowling pins, use a tennis ball to bowl them down. This makes a fun theme game at a party.
Binoculars(Camouflage)
Blue Oni (Setsubun Festival)
Candles (pretend):
Digimon
(there are over 10, so I won't list them all here)
Dinosaur - Dorothy
Dog - Wags
Easter Egg Holders:
Esau (Old Testament)
Farmer (boy)
Farmer (girl)
Gardener (boy)
Gardener (girl)
Gideon (Old Testament)
Holiday Teddy Bears:
Jack (from Jack and Jill)
Jack
(from Jack and the Beanstalk)
Jacob (Old Testament)
Jill (from Jack and Jill)
Lucha Libre
(Mexican Wrestler)
Marie (and the Orange Fish)
Nanook (Inuit Mythology)
Napkin Rings
Pokemon
(there are over 70, so I won't list them all here)
Red Oni (Setsubun Festival)
Sedna (Inuit Mythology)
The Three Bears
- Papa Bear (same as golf bear)
Wreaths (takes 14 to 16 toilet paper rolls per wreath)
Puppet is used to automate several routine sysadmin configuration tasks.
Puppet in an enterprise grade configuration management system.
It allows you to define the state of your IT infrastructure. Once it is defined, Puppet will automatically enforce the correct state on an on-going basis.
1. Puppet Architecture
Puppet typically has one server component and multiple agents. You have to designate a server on your network as puppet master, and each node on your network will have puppet agent installed on it.
The most common way to apply puppet configuration to a client is to use the puppet master daemon (puppetmasterd) and puppet client daemon (puppetd). You can also manually apply the manifests using puppet tool.
Configuration is defined on the puppet master, compiled and then pushed out to the puppet clients automatically when they connect.
Puppet supports a wide range of different platforms and operating systems, and it will automatically run the appropriate commands to apply your manifest in each environment.
A manifest is nothing but details about files, packages, configuration operations written in language that puppet can understand.
Each Puppet node contacts the puppet master, by default every 30 minutes, to confirm that its configuration is up to date. If the configuration is different or any new configuration is available, it is recompiled and then applied to the puppet node.
In this tutorial, we will explain how to create some basic manifests and apply to the clients using puppet tool.
Most of the system configuration can be viewed by using the puppet command line tool. All the configuration components are organized into resources. The resources are grouped into collections. Resources are made up of type, title and series of attributes.
2. Puppet Resource File Example
The following is a basic example on how to view a puppet resource. In this case, the puppet resource that we are viewing is a file (/etc/nsswitch).
Puppet comes with a number of resource types by default including types to manage files, services, packages, cron jobs, and filesystems, among others.
In the above example, file is the resource type and the /etc/nsswitch.conf is title of the resource to be managed.
Everything else is attributes of the resource type and values present on the attributes. You can also extend puppet to add your own resource types.
To view all the resource types available use the following command:
3. Puppet Manifest File Example
Let us take a look how to create a simple manifest file and execute the puppet command to apply the configuration to the server.
The following example creates a simple manifest file site.pp under /etc/puppet/manifests directory which will create a testfile under /var/tmp.
Initially, as we see below, we don’t have the test file.
The following is the resource declaration inside the manifest (site.pp) file:
For demo purposes, we are running the puppet master and agent on the same node.
When you run the puppet apply command for first time with –noop option, this will do a dry-run without actually applying the configuration.
The above you to see what new configuration will do without actually making changes to the node.
Now, execute the command without –noop option to really apply the configuration as shown below.
Once it is executed successfully, you will see the new temp file is created under /var/tmp/testfile with the contents defined in site.pp.
4. Control a Service on a Remote Node using Puppet
Here is an example to change service from stopped state to running state on the agent nodes.
When this configuration manifest is saved in the master server under a specific location under puppet configuration directory, the agent running on all the nodes contacts the master node and fetches the configuration and applies it on all the client nodes so this way the service would be started on all the agent nodes after the puppet configuration is executed successfully.
In this example, we will control the service multipathd. You can use puppet to control any services that are running on the system. For example, httpd, mysqld, etc.
Make sure the site.pp has the following values. If not, edit it accordingly.
First do a dry-run to make sure it works as expected.
Finally, apply the configuration file, which will start the service (in this example multipathd), if it is not already running.
5. Install a Package on a Remote Node using Puppet
You can do package installation on all the agent nodes remotely using puppet.
The following is a sample manifest file for package installation.
In this example, it will install Apache package httpd if it is not present on the remote site. As you see below, it installed the package.
Verify that the package is installed properly using rpm command.
6. Two Types of Puppet Collections
Resources can configure the characteristics of single configuration items on nodes. But, most services and applications are made up of multiple resources.
For example, a web server consists of the software package, users to run the software, and a variety of configuration, logging, and other files.
Resources collections allows you to gather the resources, assign them to collection and have the collection applied to the agent nodes.
There are 2 types of resource collection:
- Classes
- Definitions
7. Puppet Class Collection Example
A class is a collection of resources that represents single configuration item on your node whereas definition is collection of configuration items that have multiple representations on your node.
In the previous example after the package installation the services are not started by default. We can create a simple manifest with class to install the package and start the service after installation.
In the following example we specified the relationship between two resources using require attribute.
Zacchaeus Activities For Children
This ensure that the condition is met before the resource changes gets applied. In this case service httpd requires the httpd package to be installed first before it can attempt to bring up the services.
8. Puppet Definition Collection Example
A definition is a type of puppet resource collection.
Definitions should be used for configuration items that have multiple instances on a node.
Zacchaeus Coloring Page
For example, the httpd server may have multiple virtual hosts defined. You can create a definition to configure virtual hosts and pass in appropriate arguments to configure each. As long as each set of arguments was different, puppet would configure the new virtual host every time the definition was evaluated.
The following is an example of a simple manifest with a class and definition.
Execute the above puppet class and definition manifest as shown below.
9. Puppet Node Configuration File Example
So far we have seen defining resources and collections of resources in form of classes and definitions.
Now the next step is how to assign these resources and collections to clients.
Here is an example how the nodes are defined in node.pp.
Puppet uses this file to determine which class(contains resources) should go to which server, for example, on client 1 you want to run the class httpd which contains resources like httpd package, httpd service & on client 2 you want to run the class ngnix which contains resources like ngnix package, ngnix service & other ngnix configuration files.
The following sample nodes.pp file explains this:
Inside your node definition, you can add resources, classes and definitions.
Classes are added using the include function.
In puppetclient1.mydomain.net we have included httpd_class and in puppetclient2.mydomain.net we have included ngnix_class.
You can also include multiple class with a single include function. If no node definition is matched, then it takes the default values defined. In this case, if there is any other nodes it will just install perl packages if it is not present.
10. Import Puppet Manifest Files
The resources, classes, and definitions are stored in manifest files.
A special manifest file, called the site manifest, is at the core of our configuration.
When starting the Puppet master daemon, the site manifest file, by default located in /etc/puppet/manifests/site.pp, needs to be present.
Hand Puppet Template
In the above examples, we used site.pp just to explain how to apply the manifests.
In a real puppet environment your site.pp will have only the below contents and from this file the other files are imported for execution.
The following is the puppet manifest directory structure:
- /manifests/classes/ – Directory containing all classes
- /manifests/site.pp – the primary manifest file
- /manifests/templates.pp – Contains template nodes
- /manifests/nodes.pp – Contains node definitions
- /manifests/definitions/ – Contains all definitions
- /manifests/groups/ – Contains manifests configuring groups
- /manifests/os/ – Contains classes designed to configure nodes with particular operating systems
- /manifests/users/ – Contains manifests configuring users
- /manifest/files/ – Contains file server modules for Puppet distributable files