- [Show pagesource]
- [Old revisions]
- [[unknown link type]]
- []
This is an old revision of the document!
Table of Contents
Client side
1. add puppet to your /etc/hosts
10.0.4.60 puppet puppet.starlab.cz
or
212.20.102.91 puppet puppet.starlab.cz
xen-jpcomp:~# puppetd --server puppet --test info: Creating a new SSL key for xen-jpcomp.jpcomp.cz info: Caching certificate for ca info: Creating a new SSL certificate request for xen-jpcomp.jpcomp.cz info: Certificate Request fingerprint (md5): AA:A6:EA:69:9A:35:91:C2:EA:8B:CF:B4:70:8E:2E:4B Exiting; no certificate found and waitforcert is disabled
server side
The service seems to be running properly netstat's output - port 8140
tcp 0 0 0.0.0.0:8140 0.0.0.0:* LISTEN 22428/ruby1.8
Hey! We have a new client
root@ibm:~# puppetca --list "xen-jpcomp.jpcomp.cz" (AA:A6:EA:69:9A:35:91:C2:EA:8B:CF:B4:70:8E:2E:4B)
So sign it!
puppetca --sign xen-jpcomp.jpcomp.cz notice: Signed certificate request for xen-jpcomp.jpcomp.cz notice: Removing file Puppet::SSL::CertificateRequest xen-jpcomp.jpcomp.cz at '/path/to.pem'
Client side again
linux/puppet.1415301474.txt.gz · Last modified: 2014/11/06 20:17 by admin