Puppet Enterprise installation - puppet-enterprise-2.5.0-el-5-x86_64
# Java 1.6
[root@linux64-puppet-server ~]# /tmp/jdk-6u23-linux-x64.bin
[root@linux64-puppet-server ~]# echo “export PATH=/opt/jdk1.6.0_23/bin:$PATH” >> ~/.bashrc
[root@linux64-puppet-server ~]# source ~/.bashrc
[root@linux64-puppet-server ~]# which java
/opt/jdk1.6.0_23/bin/java
java -version
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode)
# MySQL 5.1
[root@linux64-puppet-server ~]# rpm -Uvh /tmp/MySQL-shared-compat-5.5.25-1.rhel5.x86_64.rpm
[root@linux64-puppet-server ~]# rpm -Uvh /tmp/MySQL-client-community-5.5.25-1.rhel5.x86_64.rpm
[root@linux64-puppet-server ~]# rpm -Uvh /tmp/MySQL-server-community-5.5.25-1.rhel5.x86_64.rpm
[root@linux64-puppet-server ~]# /usr/bin/mysqladmin -u root password '********'
# Puppet Enterprise Master
[root@linux64-puppet-server ~]# cd /opt
[root@linux64-puppet-server opt]# tar zxvf /tmp/puppet-enterprise-2.5.0-el-5-x86_64.tar.gz
# make sure puppet prerequisites get installed
[root@linux64-puppet-server ~]# rpm –Uvh /opt/puppet-enterprise-2.5.0-el-5-x86_64/packages/el-5-x86_64/pe-virtual-java-1.0-1.pe.el5.noarch.rpm
[root@linux64-puppet-server ~]# cd puppet-enterprise-2.5.0-el-5-x86_64
[root@linux64-puppet-server puppet-enterprise-2.5.0-el-5-x86_64
]# ./puppet-enterprise-installer
]# ./puppet-enterprise-installer
=================================================================================================================================================
Puppet Enterprise v2.5.0 installer
Puppet Enterprise documentation can be found at http://links.puppetlabs.com/puppet_enterprise_2.5_documentation
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 1: SELECT AND CONFIGURE ROLES
This installer will offer to install the puppet master, console, cloud provisioner, and puppet agent roles.
-> puppet master
The puppet master serves configurations to a group of puppet agent nodes. This role also provides MCollective's message queue and client
interface. It should be installed on a robust, dedicated server.
?? Install puppet master? [y/N] y
-> cloud provisioner
The cloud provisioner can create and bootstrap new machine instances and add them to your Puppet infrastructure. It should be installed on
a trusted node where site administrators have shell access.
?? Install the cloud provisioner? [y/N]
-> console
The console is a web interface for viewing reports, classifying nodes, directly managing resources, controlling Puppet runs, and invoking
MCollective agents. It should usually be installed on the puppet master server, but can also installed separately.
?? Install the console? [Y/n]
-> puppet agent
The puppet agent role is automatically installed with the console, puppet master, and cloud provisioner roles.
?? The puppet master's certificate will contain a unique name ("certname"); this should be the main DNS name at which it can be reliably
reached. Puppet master's certname? [Default: linux64-puppet-server] linux64-puppet-server.domain.com
?? The puppet master's certificate can contain DNS aliases; agent nodes will only trust the master if they reach it at its certname or one of
these official aliases. Puppet master's DNS aliases (comma-separated list)? [Default:
linux64-puppet-server,linux64-puppet-server.domain.com,puppet,puppet.domain.com]
?? Admin email address (will be used as account name) for accessing the console interface? pptadmin@domain.com
?? Password for user pptadmin@domain.com (minimum 8 characters)?
Confirm Password:
?? The console requires a MySQL database server. Install a new database server from your operating system's repository? [Y/n] n
The console requires a MySQL database and a user account able to edit it.
?? Is your existing MySQL server running on a remote host? [y/N]
?? The console requires a database user with all privileges on both the console and inventory service databases as well as an auth user with
its own database. Create the users and databases automatically? [Y/n]
?? To set up the console users and databases, the root MySQL password is required. What password does the 'root' user have on the database
server?
Confirm Password:
The console requires an SMTP server to email account information to users.
?? What is the name of your SMTP server? smtp.domain.com
?? Console database name? [Default: console]
?? Console database user? [Default: console]
?? Database user password (minimum 4 characters)?
Confirm Password:
?? What is the name of the authentication database? [Default: console_auth]
?? What is the name of the user authentication database user? [Default: console_auth]
?? What is the password for console_auth (the user authentication database user)?
Confirm Password:
-> Convenience Links
The selected Puppet software will be installed into "/opt/puppet", which may not be included in your default shell PATH. For ease of use,
this installer can create symbolic links to these executables in "/usr/local/bin".
?? Create symbolic links to Puppet executables in "/usr/local/bin"? [Y/n]
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 2: CONFIRM PLAN
You have selected to install the following components (and their dependencies)
* Puppet Master
* Console
* Puppet Agent
?? Perform installation? [Y/n]
## Saved answers to file: ./answers.lastrun.linux64-puppet-server
=================================================================================================================================================
## Saved answers to file: /etc/puppetlabs/installer/answers.install
Warning: overwriting /etc/puppetlabs/facter/facts.d/puppet_enterprise_installer.txt
Creating Backup: /etc/puppetlabs/facter/facts.d/puppet_enterprise_installer.txt.bak
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 3: INSTALL PACKAGES
## Installing packages from files...
Preparing... ########################################### [100%]
1:pe-ruby-libs ########################################### [ 3%]
2:pe-ruby ########################################### [ 5%]
3:pe-httpd ########################################### [ 8%]
4:pe-ruby-mysql ########################################### [ 10%]
5:pe-facter ########################################### [ 13%]
6:pe-ruby-irb ########################################### [ 15%]
7:pe-ruby-rdoc ########################################### [ 18%]
8:pe-rubygems ########################################### [ 20%]
9:pe-rubygem-stomp ########################################### [ 23%]
10:pe-rubygem-rake ########################################### [ 25%]
11:pe-mcollective-common ########################################### [ 28%]
12:pe-rubygem-rack ########################################### [ 30%]
13:pe-httpd-passenger ########################################### [ 33%]
14:pe-rubygem-activesuppor########################################### [ 35%]
15:pe-rubygem-activerecord########################################### [ 38%]
16:pe-ruby-shadow ########################################### [ 40%]
17:pe-puppet ########################################### [ 43%]
18:pe-rubygem-hiera ########################################### [ 45%]
19:pe-augeas-libs ########################################### [ 48%]
20:pe-augeas ########################################### [ 50%]
21:pe-rubygem-hiera-puppet########################################### [ 52%]
22:pe-puppet-server ########################################### [ 55%]
23:pe-mcollective ########################################### [ 58%]
24:pe-mcollective-client ########################################### [ 60%]
25:pe-rubygem-stomp-doc ########################################### [ 63%]
26:pe-ruby-augeas ########################################### [ 65%]
27:pe-ruby-ldap ########################################### [ 68%]
28:pe-ruby-ri ########################################### [ 70%]
29:pe-mod_ssl ########################################### [ 73%]
30:pe-memcached ########################################### [ 75%]
31:pe-libevent ########################################### [ 78%]
32:pe-activemq ########################################### [ 80%]
33:pe-puppet-dashboard ########################################### [ 83%]
34:pe-rubygem-sinatra ########################################### [ 85%]
35:pe-console-auth ########################################### [ 88%]
36:pe-rubygem-ar-extension########################################### [ 90%]
37:pe-rubygem-dalli ########################################### [ 93%]
38:pe-live-management ########################################### [ 95%]
39:pe-puppet-dashboard-bas########################################### [ 98%]
40:pe-rubygem-tilt ########################################### [100%]
## Setting up puppet master...
## Checking the agent certificate name detection...
## Setting up puppet agent...
## Setting up the console...
## Starting http server for puppet master and console.
## Creating symbolic links in "/usr/local/bin"...
Generating collective password...
Running puppet apply to configure MCollective ...
MCollective configuration is complete ...
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 4: DONE
Thanks for installing Puppet Enterprise!
Puppet Enterprise has been installed to "/opt/puppet," and its configuration files are located in "/etc/puppetlabs".
## Answers from this session saved to './answers.lastrun.mt-olinux64-b03'
=================================================================================================================================================
The console can be reached at the following URI:
If you have a firewall running, please ensure the following TCP ports are open: 8140, 61613, 443
WARNING: This system has 8388608 bytes allocated for MySQL's innodb_buffer_pool_size, which is below the recommended minimum of 80 MB.
Although this node will be a fully functional console, it may experience problems with database migrations during upgrades. Increasing the
buffer pool size as described at http://links.puppetlabs.com/innodb_buffer_pool_size will help avoid this problem.
# answer.install for unattended Puppet Enterprise Master installation
[root@linux64-puppet-server ~]# cat /etc/puppetlabs/installer/answers.install
q_install=y
q_puppet_cloud_install=n
q_puppet_enterpriseconsole_auth_database_name=console_auth
q_puppet_enterpriseconsole_auth_database_password=********
q_puppet_enterpriseconsole_auth_database_user=console_auth
q_puppet_enterpriseconsole_auth_password=********
q_puppet_enterpriseconsole_auth_user_email=pptadmin@domain.com
q_puppet_enterpriseconsole_database_install=n
q_puppet_enterpriseconsole_database_name=console
q_puppet_enterpriseconsole_database_password=********
q_puppet_enterpriseconsole_database_remote=n
q_puppet_enterpriseconsole_database_root_password=root
q_puppet_enterpriseconsole_database_user=console
q_puppet_enterpriseconsole_httpd_port=443
q_puppet_enterpriseconsole_install=y
q_puppet_enterpriseconsole_inventory_hostname=linux64-puppet-server.domain.com
q_puppet_enterpriseconsole_inventory_port=8140
q_puppet_enterpriseconsole_master_hostname=linux64-puppet-server.domain.com
q_puppet_enterpriseconsole_setup_db=y
q_puppet_enterpriseconsole_smtp_host=smtp.domain.com
q_puppet_enterpriseconsole_smtp_password=
q_puppet_enterpriseconsole_smtp_port=25
q_puppet_enterpriseconsole_smtp_use_tls=n
q_puppet_enterpriseconsole_smtp_user_auth=n
q_puppet_enterpriseconsole_smtp_username=
q_puppet_symlinks_install=y
q_puppetagent_certname=linux64-puppet-server.domain.com
q_puppetagent_install=y
q_puppetagent_server=linux64-puppet-server.domain.com
q_puppetca_install=y
q_puppetmaster_certname=linux64-puppet-server.domain.com
q_puppetmaster_dnsaltnames=linux64-puppet-server,linux64-puppet-server.domain.com,puppet,puppet.domain.com
q_puppetmaster_enterpriseconsole_hostname=localhost
q_puppetmaster_enterpriseconsole_port=443
q_puppetmaster_forward_facts=n
q_puppetmaster_install=y
q_vendor_packages_install=n
# Puppet Enterprise Agent
[root@linux64-puppet-agent ~]# cd /opt
[root@linux64-puppet-agent opt]# tar zxvf puppet-enterprise-2.5.0-el-5-x86_64.tar.gz[root@linux64-puppet-agent ~]# rpm –Uvh /opt/puppet-enterprise-2.5.0-el-5-x86_64/packages/el-5-x86_64/pe-virtual-java-1.0-1.pe.el5.noarch.rpm
# make sure puppet prerequisites get installed
[root@linux64-puppet-agent ~]# cd puppet-enterprise-2.5.0-el-5-x86_64
[root@linux64-puppet-agent puppet-enterprise-2.5.0-el-5-x86_64
]# ./puppet-enterprise-installer
]# ./puppet-enterprise-installer
=================================================================================================================================================
Puppet Enterprise v2.5.0 installer
Puppet Enterprise documentation can be found at http://links.puppetlabs.com/puppet_enterprise_2.5_documentation
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 1: SELECT AND CONFIGURE ROLES
This installer will offer to install the puppet master, console, cloud provisioner, and puppet agent roles.
-> puppet master
The puppet master serves configurations to a group of puppet agent nodes. This role also provides MCollective's message queue and client
interface. It should be installed on a robust, dedicated server.
?? Install puppet master? [y/N]
-> cloud provisioner
The cloud provisioner can create and bootstrap new machine instances and add them to your Puppet infrastructure. It should be installed on
a trusted node where site administrators have shell access.
?? Install the cloud provisioner? [y/N]
-> console
The console is a web interface for viewing reports, classifying nodes, directly managing resources, controlling Puppet runs, and invoking
MCollective agents. It should usually be installed on the puppet master server, but can also installed separately.
?? Install the console? [y/N]
-> puppet agent
The puppet agent applies configurations from the puppet master and submits reports and inventory information. It should be installed on
every node you plan to manage with Puppet.
?? Install puppet agent? [Y/n]
?? Puppet agent needs a unique name ("certname") for its certificate; this can be an arbitrary string. Certname for this node? [Default:
linux64-puppet-agent] linux64-puppet-agent.domain.com
?? Puppet master hostname to connect to? [Default: puppet]
?? The installer couldn’t reach the puppet master server at puppet. If this server name is correct, please check your DNS configuration to
Enter ‘r’ if you need to re-enter the puppet master’s name; otherwise, enter ‘c’ to continue. [c/r] r
?? Puppet master hostname to connect to? [Default: puppet] linux64-puppet-server.domain.com
-> Convenience Links
The selected Puppet software will be installed into "/opt/puppet", which may not be included in your default shell PATH. For ease of use,
this installer can create symbolic links to these executables in "/usr/local/bin".
?? Create symbolic links to Puppet executables in "/usr/local/bin"? [Y/n]
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 2: CONFIRM PLAN
You have selected to install the following components (and their dependencies)
* Puppet Agent
?? Perform installation? [Y/n]
## Saved answers to file: ./answers.lastrun.linux64-puppet-agent
=================================================================================================================================================
## Saved answers to file: /etc/puppetlabs/installer/answers.install
Created: /etc/puppetlabs/facter/facts.d
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 3: INSTALL PACKAGES
## Installing packages from files...
Preparing... ########################################### [100%]
1:pe-puppet-enterprise-re########################################### [ 5%]
2:pe-ruby-libs ########################################### [ 10%]
3:pe-ruby ########################################### [ 15%]
4:pe-facter ########################################### [ 20%]
5:pe-ruby-irb ########################################### [ 25%]
6:pe-ruby-rdoc ########################################### [ 30%]
7:pe-rubygems ########################################### [ 35%]
8:pe-rubygem-stomp ########################################### [ 40%]
9:pe-mcollective-common ########################################### [ 45%]
10:pe-ruby-shadow ########################################### [ 50%]
11:pe-puppet ########################################### [ 55%]
12:pe-rubygem-hiera ########################################### [ 60%]
13:pe-augeas-libs ########################################### [ 65%]
14:pe-augeas ########################################### [ 70%]
15:pe-mcollective ########################################### [ 75%]
16:pe-ruby-augeas ########################################### [ 80%]
17:pe-rubygem-hiera-puppet########################################### [ 85%]
18:pe-rubygem-stomp-doc ########################################### [ 90%]
19:pe-ruby-ldap ########################################### [ 95%]
20:pe-ruby-ri ########################################### [100%]
## Checking the agent certificate name detection...
## Setting up puppet agent...
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
## Creating symbolic links in "/usr/local/bin"...
-------------------------------------------------------------------------------------------------------------------------------------------------
STEP 4: DONE
Thanks for installing Puppet Enterprise!
Puppet Enterprise has been installed to "/opt/puppet," and its configuration files are located in "/etc/puppetlabs".
## Answers from this session saved to './answers.lastrun.mt-olinux64-b04'
=================================================================================================================================================
If you have a firewall running, please ensure outbound connections to linux64-puppet-server.domain.com are allowed via the following TCP ports:
8140, 61613
# answer.install for unattended Puppet Enterprise Agent installation
[root@linux64-puppet-agent ~]# cat /etc/puppetlabs/installer/answers.install
q_fail_on_unsuccessful_master_lookup=y
q_install=y
q_puppet_cloud_install=n
q_puppet_enterpriseconsole_install=n
q_puppet_symlinks_install=y
q_puppetagent_certname=linux64-puppet-agent.domain.com
q_puppetagent_install=y
q_puppetagent_server=linux64-puppet-server.domain.com
q_puppetca_install=n
q_puppetmaster_install=n
q_vendor_packages_install=n
# Troubleshooting for Puppet Enterprise Live Management on Red Hat 5
broker.ts (default path /etc/puppetlabs/activemq/broker.ts) should not exist on Puppet Enterprise Master host
[root@linux64-puppet-server ~]# uname -a
Linux linux64-puppet-server 2.6.32-100.0.19.el5 #1 SMP Fri Sep 17 17:51:41 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Linux linux64-puppet-server 2.6.32-100.0.19.el5 #1 SMP Fri Sep 17 17:51:41 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@linux64-puppet-server ~]# crontab -l
# HEADER: This file was autogenerated at Thu Apr 19 16:31:46 -0400 2012 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: pe-mcollective-metadata
0,15,30,45 * * * * /opt/puppet/sbin/refresh-mcollective-metadata
# Puppet Name: report_baseline
0 20 * * * PATH=/opt/puppet/bin:/bin:/usr/bin:/usr/sbin:/usr/local/bin /opt/puppet/bin/puppet inspect
3 * * * * /opt/puppet/remove_broker_ts.sh
[root@linux64-puppet-server ~]# cat /opt/puppet/remove_broker_ts.sh
#!/bin/sh
if [ -e "/etc/puppetlabs/activemq/broker.ts" ]; then
/bin/rm -f /etc/puppetlabs/activemq/broker.ts
service pe-activemq start
fi
# Puppet Enterprise Console
# Puppet Enterprise Live Management
You can play one, five, or ten consecutive Keno video games utilizing the numbers you selected by clicking Play 1, Play 5, or Play 10. Play Now Step right a lot as} the table and begin rolling the dice! For instance, you can to|you presumably can} bet that the subsequent roll of the dice shall be a 6. You can even bet that a sure number would be rolled 1xbet korea first, corresponding to betting a 6 shall be rolled earlier than a 7. People who write critiques have possession to edit or delete them at any time, and they’ll be displayed lengthy as|so long as} an account is lively. Played $57.50 price after which obtained a message closing the account as I had beforehand requested self exclusion .
ReplyDelete