2 [![Dependency Status][5]][2]
3 [![Project Chatroom][6]][3]
8 1. [Overview](#overview)
9 1. [Module Description](#module-description)
11 * [What `opendaylight` affects](#what-opendaylight-affects)
12 * [Beginning with `opendaylight`](#beginning-with-opendaylight)
14 * [Karaf Features](#karaf-features)
15 * [Install Method](#install-method)
17 * [Log Verbosity](#log-verbosity)
18 * [Enabling ODL OVSDB L3](#enabling-odl-ovsdb-l3)
19 * [Enabling ODL OVSDB HA](#enabling-odl-ovsdb-ha)
20 1. [Reference ](#reference)
21 1. [Limitations](#limitations)
22 1. [Development](#development)
23 1. [Release Notes/Contributors](#release-notescontributors)
27 Puppet module that installs and configures the [OpenDaylight Software Defined
28 Networking (SDN) controller][7].
32 Deploys OpenDaylight to various OSs either via an RPM or directly from the
33 ODL tarball release artifact.
35 All OpenDaylight configuration should be handled through the ODL Puppet
36 module's [params](#parameters). If you need a new knob, [please raise an
39 Both supported [install methods](#install-method) default to the latest
40 OpenDaylight release, which is currently [Beryllium][18].
44 ### What `opendaylight` affects
46 * Installs Java, which is required by ODL.
47 * Creates `odl:odl` user:group if they don't already exist.
48 * Installs [OpenDaylight][7].
49 * Installs a [systemd unitfile][9] or [Upstart config file][10] for
51 * Manipulates OpenDaylight's configuration files according to the params
52 passed to the `::opendaylight` class.
53 * Starts the `opendaylight` systemd or Upstart service.
55 ### Beginning with `opendaylight`
57 Getting started with the OpenDaylight Puppet module is as simple as declaring
58 the `::opendaylight` class.
60 The [vagrant-opendaylight][11] project provides an easy way to experiment
61 with [applying the ODL Puppet module][12] to CentOS 7, Fedora 22 and Fedora
65 [~/vagrant-opendaylight]$ vagrant status
66 Current machine states:
68 cent7 not created (libvirt)
69 cent7_rpm_he_sr4 not created (libvirt)
70 cent7_rpm_li_sr2 not created (libvirt)
71 cent7_rpm_be not created (libvirt)
72 cent7_ansible not created (libvirt)
73 cent7_ansible_be not created (libvirt)
74 cent7_ansible_path not created (libvirt)
75 cent7_pup_rpm not created (libvirt)
76 cent7_pup_custom_logs not created (libvirt)
77 cent7_pup_tb not created (libvirt)
78 f22_rpm_li not created (libvirt)
79 f22_ansible not created (libvirt)
80 f22_pup_rpm not created (libvirt)
81 f23_rpm_li not created (libvirt)
82 f23_rpm_li_sr1 not created (libvirt)
83 f23_rpm_li_sr2 not created (libvirt)
84 f23_rpm_li_sr3 not created (libvirt)
85 f23_rpm_be not created (libvirt)
86 f23_ansible not created (libvirt)
87 f23_pup_rpm not created (libvirt)
89 [~/vagrant-opendaylight]$ vagrant up cent7_pup_rpm
90 # A CentOS 7 VM is created and configured using the ODL Puppet mod's defaults
91 [~/vagrant-opendaylight]$ vagrant ssh cent7_pup_rpm
92 [vagrant@localhost ~]$ sudo systemctl is-active opendaylight
98 The most basic usage, passing no parameters to the OpenDaylight class, will
99 install and start OpenDaylight with a default configuration.
102 class { 'opendaylight':
108 To set extra Karaf features to be installed at OpenDaylight start time, pass
109 them in a list to the `extra_features` param. The extra features you pass will
110 typically be driven by the requirements of your ODL install. You'll almost
111 certainly need to pass some.
114 class { 'opendaylight':
115 extra_features => ['odl-ovsdb-plugin', 'odl-ovsdb-openstack'],
119 OpenDaylight normally installs a default set of Karaf features at boot. They
120 are recommended, so the ODL Puppet mod defaults to installing them. This can
121 be customized by overriding the `default_features` param. You shouldn't
122 normally need to do so.
125 class { 'opendaylight':
126 default_features => ['config', 'standard', 'region', 'package', 'kar', 'ssh', 'management'],
132 The `install_method` param, and the associated `tarball_url` and `unitfile_url`
133 params, are intended for use by developers who need to install a custom-built
134 version of OpenDaylight, or for automated build processes that need to consume
135 a tarball build artifact.
137 It's recommended that most people use the default RPM-based install.
139 If you do need to install from a tarball, simply pass `tarball` as the value
140 for `install_method` and optionally pass the URL to your tarball via the
141 `tarball_url` param. The default value for `tarball_url` points at
142 OpenDaylight's latest release. The `unitfile_url` param points at the
143 OpenDaylight systemd .service file used by the RPM and should (very likely)
144 not need to be overridden.
147 class { 'opendaylight':
148 install_method => 'tarball',
149 tarball_url => '<URL to your custom tarball>',
150 unitfile_url => '<URL to your custom unitfile>',
156 To change the port on which OpenDaylight's northbound listens for REST API
157 calls, use the `odl_rest_port` param.
161 class { 'opendaylight':
162 odl_rest_port => '8080',
168 It's possible to define custom logger verbosity levels via the `log_levels`
172 class { 'opendaylight':
173 log_levels => { 'org.opendaylight.ovsdb' => 'TRACE', 'org.opendaylight.ovsdb.lib' => 'INFO' },
177 ### Enabling ODL OVSDB L3
179 To enable the ODL OVSDB L3, use the `enable_l3` flag. It's disabled by default.
182 class { 'opendaylight':
187 ### Enable ODL OVSDB HA
189 To enable ODL OVSDB HA, use the `enable_ha` flag. It's disabled by default.
191 When `enable_ha` is set to true the `ha_node_ips` should be populated with the
192 IP addresses that ODL will listen on for each node in the OVSDB HA cluster and
193 `ha_node_index` should be set with the index of the IP address from
194 `ha_node_ips` for the particular node that puppet is configuring as part of the
198 class { 'opendaylight':
200 ha_node_ips => ['10.10.10.1', '10.10.10.1', '10.10.10.3'],
211 * `::opendaylight`: Main entry point to the module. All ODL knobs should be
212 managed through its params.
216 * `::opendaylight::params`: Contains default `opendaylight` class param values.
217 * `::opendaylight::install`: Installs ODL from an RPM or tarball.
218 * `::opendaylight::config`: Manages ODL config, including Karaf features and
220 * `::opendaylight::service`: Starts the OpenDaylight service.
226 ##### `default_features`
228 Sets the Karaf features to install by default. These should not normally need
231 Default: `['config', 'standard', 'region', 'package', 'kar', 'ssh', 'management']`
233 Valid options: A list of Karaf feature names as strings.
235 ##### `extra_features`
237 Specifies Karaf features to install in addition to the defaults listed in
240 You will likely need to customize this to your use-case.
244 Valid options: A list of Karaf feature names as strings.
246 ##### `install_method `
248 Specifies the install method by which to install OpenDaylight.
250 The RPM install method is less complex, more frequently consumed and
255 Valid options: The strings `'tarball'` or `'rpm'`.
257 ##### `odl_rest_port `
259 Specifies the port for the ODL northbound REST interface to listen on.
263 Valid options: A valid port number as a string or integer.
267 Custom OpenDaylight logger verbosity configuration.
271 Valid options: A hash of loggers to log levels.
274 { 'org.opendaylight.ovsdb' => 'TRACE', 'org.opendaylight.ovsdb.lib' => 'INFO' }
277 Valid log levels are TRACE, DEBUG, INFO, WARN, and ERROR.
279 The above example would add the following logging configuration to
280 `/opt/opendaylight/etc/org.ops4j.pax.logging.cfg`.
283 # Log level config added by puppet-opendaylight
284 log4j.logger.org.opendaylight.ovsdb = TRACE
286 # Log level config added by puppet-opendaylight
287 log4j.logger.org.opendaylight.ovsdb.lib = INFO
290 To view loggers and their verbosity levels, use `log:list` at the ODL Karaf shell.
293 opendaylight-user@root>log:list
295 ----------------------------------
297 org.opendaylight.ovsdb | TRACE
298 org.opendaylight.ovsdb.lib | INFO
301 The main log output file is `/opt/opendaylight/data/log/karaf.log`.
305 Enable or disable ODL OVSDB L3 forwarding.
309 Valid options: The strings `'yes'` or `'no'` or boolean values `true` and `false`.
311 The ODL OVSDB L3 config in `/opt/opendaylight/etc/custom.properties` is set to
312 the value of the `enable_l3` param.
317 class { 'opendaylight':
322 Would would result in
325 ovsdb.l3.fwd.enabled=yes
326 ovsdb.l3.arp.responder.disabled=no
331 Enable or disable ODL OVSDB High Availablity.
335 Valid options: The boolean values `true` and `false`.
337 Requires: `ha_node_ips`, `ha_node_index`
339 The ODL OVSDB Clustering and Jolokia XML for HA are configured and enabled.
343 Specifies the IPs that are part of the HA cluster enabled by `enable_ha`.
347 Valid options: An array of IP addresses `['10.10.10.1', '10.10.10.1', '10.10.10.3']`.
349 Required by: `enable_ha`
351 ##### `ha_node_index`
353 Specifies the index of the IP for the node being configured from the array `ha_node_ips`.
357 Valid options: Index of a member of the array `ha_node_ips`: `0`.
359 Required by: `enable_ha`, `ha_node_ips`
364 Specifies the ODL tarball to use when installing via the tarball install
367 Default: `'https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/distribution-karaf/0.3.2-Lithium-SR2/distribution-karaf-0.3.2-Lithium-SR2.tar.gz'`
369 Valid options: A valid URL to an ODL tarball as a string.
373 Specifies the ODL systemd .service file to use when installing via the tarball
376 It's very unlikely that you'll need to override this.
378 Default: `'https://github.com/dfarrell07/opendaylight-systemd/archive/master/opendaylight-unitfile.tar.gz'`
380 Valid options: A valid URL to an ODL systemd .service file (archived in a
381 tarball) as a string.
385 * Tested on Fedora 22, 23, CentOS 7 and Ubuntu 14.04.
386 * CentOS 7 is currently the most stable OS option.
387 * The RPM install method is likely more reliable than the tarball install
392 We welcome contributions and work to make them easy!
394 See [CONTRIBUTING.markdown][14] for details about how to contribute to the
395 OpenDaylight Puppet module.
397 ## Release Notes/Contributors
399 See the [CHANGELOG][15] or our [git tags][16] for information about releases.
400 See our [git commit history][17] for contributor information.
403 [1]: https://travis-ci.org/dfarrell07/puppet-opendaylight
404 [2]: https://gemnasium.com/dfarrell07/puppet-opendaylight
405 [3]: https://gitter.im/dfarrell07/puppet-opendaylight?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge
406 [4]: https://travis-ci.org/dfarrell07/puppet-opendaylight.svg
407 [5]: https://gemnasium.com/dfarrell07/puppet-opendaylight.svg
408 [6]: https://badges.gitter.im/Join%20Chat.svg
409 [7]: http://www.opendaylight.org/
410 [8]: https://github.com/dfarrell07/puppet-opendaylight/blob/master/CONTRIBUTING.markdown#issues
411 [9]: https://github.com/dfarrell07/opendaylight-systemd/
412 [10]: https://github.com/dfarrell07/puppet-opendaylight/blob/master/files/upstart.odl.conf
413 [11]: https://github.com/dfarrell07/vagrant-opendaylight/
414 [12]: https://github.com/dfarrell07/vagrant-opendaylight/tree/master/manifests
415 [13]: https://github.com/dfarrell07/puppet-opendaylight/issues/63
416 [14]: https://github.com/dfarrell07/puppet-opendaylight/blob/master/CONTRIBUTING.markdown
417 [15]: https://github.com/dfarrell07/puppet-opendaylight/blob/master/CHANGELOG
418 [16]: https://github.com/dfarrell07/puppet-opendaylight/releases
419 [17]: https://github.com/dfarrell07/puppet-opendaylight/commits/master
420 [18]: http://cbs.centos.org/repos/nfv7-opendaylight-42-release/x86_64/os/Packages/