1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
---
title: "Installing from source"
layout: default
---
# Installing from source
[leiningen]: https://github.com/technomancy/leiningen#installation
[configure_postgres]: ./configure.markdown#using-postgresql
[configure_heap]: ./configure.markdown#configuring-the-java-heap-size
[module]: ./install_via_module.markdown
[postgres_ssl]: ./postgres_ssl.markdown
[packages]: ./install_from_packages.markdown
[running_tests]: ./CONTRIBUTING.md#running-the-tests
> **Note:** If you are running Puppet Enterprise version 3.0 or later, you do
> not need to install PuppetDB, as it is already installed as part of PE.
This page describes how to install PuppetDB from source code, and how to run
PuppetDB directly from source without installing.
If possible, we recommend installing PuppetDB
[with the puppetlabs-puppetdb module][module] or [from packages][packages];
either approach will be easier than installing from source. However, if you are
testing a new version, developing PuppetDB, or installing it on a system not
supported with official packages, you will need to install PuppetDB from source.
## Step 1: Installation prerequisites
Use your system's package tools to ensure that the following prerequisites are installed:
* (Optional) Puppet Server 2.x or newer
* A working Puppet agent or server setup (for ssl-setup to succeed)
* Facter, version 3 or newer
* JDK 8 or newer
* [Leiningen][]
* Git (for checking out the source code)
* Rake (version 0.9.6 or newer)
## Step 2, option A: Install from source
Install Leiningen:
$ mkdir ~/bin && cd ~/bin
$ curl -L 'https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein' -o lein --tlsv1
$ chmod ugo+x lein
$ ./lein
# symlink lein to somewhere in your $PATH
$ sudo ln -s /full/path/to/bin/lein /usr/local/bin
Run the following commands to build a distribution tarball from source:
$ mkdir -p ~/git && cd ~/git
$ git clone git://github.com/puppetlabs/puppetdb
$ git checkout stable # Or a particular tag you wish to install
$ cd puppetdb
$ lein install
$ lein with-profile ezbake ezbake stage
$ cd target/staging
$ rake package:bootstrap
$ rake package:tar
Now unpack the tarball to prepare for installation:
$ cd pkg
$ tar -xzf puppetdb-*.tar.gz
$ cd puppetdb-*
To perform a full installation of the service and the PuppetDB-termini code
(usually the best choice when running PuppetDB on the same host as the Puppet
Server):
$ sudo bash install.sh all
Otherwise, for service only:
$ sudo bash install.sh service
Or for terminus code only:
$ sudo bash install.sh termini
## Step 2, option B: Run directly from source
While installing from source is useful for simply running a development version
for testing, for development it's better to be able to run **directly** from
source, without any installation step.
Run the following commands:
$ mkdir -p ~/git && cd ~/git
$ git clone git://github.com/puppetlabs/puppetdb
$ cd puppetdb
# Download the dependencies
$ lein deps
This will let you develop on PuppetDB and see your changes by simply editing the
code and restarting the server. It will not create an init script or default
configuration directory. To start the PuppetDB service when running from source,
you will need to run the following:
$ lein run services -c /path/to/config.ini
A sample config file is provided in the root of the source repo:
`config.sample.ini`. You can also provide a conf.d-style directory instead of a
flat config file.
Next, you will need to [setup some test users][running_tests] to run the tests locally
## Step 3: Configure a database
In most cases you should
[set up a PostgreSQL server and configure PuppetDB to use it][configure_postgres].
You may also need to [adjust the maximum heap size][configure_heap].
You can change PuppetDB's database at any time while the service is shut down,
but note that changing the database does not migrate PuppetDB's data, so the new
database will be empty.
If your PostgreSQL node is on a separate server than PuppetDB, you should
[configure an SSL connection][postgres_ssl], otherwise your database
communication will happen in plaintext over the network. This can be made
much simpler by installing using the [PuppetDB module][module].
## Step 4: Start the PuppetDB service
If you _installed_ PuppetDB from source, you can start PuppetDB by running the
following:
$ sudo service puppetdb start
And if Puppet is installed, you can permanently enable PuppetDB by running:
$ sudo puppet resource service puppetdb ensure=running enable=true
If you are running PuppetDB from source, you should start it as follows:
# From the directory in which PuppetDB's source is stored:
$ lein run services -c /path/to/config.ini
> PuppetDB is now fully functional and ready to receive catalogs and facts from
> any number of Puppet Servers.
## Finish: Connect Puppet to PuppetDB
[You should now configure your Puppet Server(s) to connect to PuppetDB](./connect_puppet_server.markdown).
If you use a standalone Puppet site,
[you should configure every node to connect to PuppetDB](./connect_puppet_apply.markdown).
|
