Difference between revisions of "Set up Puppet"
(→Project Plan) |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
== Project Description == | == Project Description == | ||
| + | |||
| + | Puppet is an automation and configuration management tool, which provides system administrators centralized architecture that allows | ||
| + | for consistent and scalable system management across platforms. | ||
| + | |||
| + | |||
| + | |||
Relevant link(s) for online resources | Relevant link(s) for online resources | ||
1) Puppettables.com [http://www.puppetlabs.com/] | 1) Puppettables.com [http://www.puppetlabs.com/] | ||
| − | |||
== Project Leader(s) == | == Project Leader(s) == | ||
| Line 22: | Line 27: | ||
== Project Details == | == Project Details == | ||
| − | + | Why we need puppet? | |
| + | |||
| + | Imagine if you are an administrator for data center that have over 500 systems, where you need to change configuration often, how easy is it to do that? hah! easy? it is very hard to go to every system and do the changes. That is where puppets is to help you for centralized management. | ||
| + | All the configuration is done at the puppet master, and then the clients will receive the changes. | ||
| + | |||
| + | All clients will communicate with puppet master periodically to see if there are any changes for respective configuration, and download the latest configuration and make sure it is synchronize with that configuration.Once the configuration applied, it will report to the puppet master asking if there are anything need to changed. | ||
| + | |||
| + | |||
| + | [[Image:filename|thumb|widthpx| ]] | ||
| + | |||
| + | The pictures below shows how puppet master and client interact. | ||
| + | |||
| + | [[File:puppet.png]] | ||
== Project Plan == | == Project Plan == | ||
| Line 28: | Line 45: | ||
Goals for each release: | Goals for each release: | ||
* 0.1 | * 0.1 | ||
| + | 1) Initial set up. | ||
| + | Download the required software and setup in the testing server/client | ||
| + | |||
* 0.2 | * 0.2 | ||
| + | |||
| + | 1) Install it in the ARM farm and testing. | ||
| + | |||
* 0.3 | * 0.3 | ||
| + | |||
| + | 1) final Release and make it available for software developers. | ||
== Project News == | == Project News == | ||
Latest revision as of 12:58, 14 October 2010
Contents
Project Name
Set up Puppet
Project Description
Puppet is an automation and configuration management tool, which provides system administrators centralized architecture that allows for consistent and scalable system management across platforms.
Relevant link(s) for online resources
1) Puppettables.com [1]
Project Leader(s)
Pirathapan Sivalingam [2]
Project Contributor(s)
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki
NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.
Project Details
Why we need puppet?
Imagine if you are an administrator for data center that have over 500 systems, where you need to change configuration often, how easy is it to do that? hah! easy? it is very hard to go to every system and do the changes. That is where puppets is to help you for centralized management. All the configuration is done at the puppet master, and then the clients will receive the changes.
All clients will communicate with puppet master periodically to see if there are any changes for respective configuration, and download the latest configuration and make sure it is synchronize with that configuration.Once the configuration applied, it will report to the puppet master asking if there are anything need to changed.
The pictures below shows how puppet master and client interact.
Project Plan
Goals for each release:
- 0.1
1) Initial set up.
Download the required software and setup in the testing server/client
- 0.2
1) Install it in the ARM farm and testing.
- 0.3
1) final Release and make it available for software developers.
Project News
This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.
Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.
