- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with Confluence
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
This is a puppet module to install and handle upgrades of Atlassian Confluence. Confluence is team collaboration software.
This module installs/upgrades Atlassian Confluence. The Confluence module also manages the Confluence configuration files with Puppet.
- Confluence require a Java Developers Kit (JDK) or Java Run-time Environment (JRE) platform to be installed on your server's operating system. Oracle JDK / JRE (formerly Sun JDK / JRE) versions 1.7 and 1.8 are currently supported by Atlassian.
- Confluence requires a relational database to store its configuration data. Unfortunatly it is not possible to do the initial configuration (Database setup) of confluence with puppet (See issue #3 - No database support ). The configuration needs to be done via the web GUI.
If installing to an existing Confluence instance, it is your responsibility to backup your database. We also recommend that you backup your Confluence home directory and that you align your current Confluence version with the version you intend to use with puppet Confluence module.
You must have your database setup with the account user that Confluence will use. This can be done using the puppetlabs-postgresql and puppetlabs-mysql modules.
When using this module to upgrade Confluence, please make sure you have a database/Confluence home backup.
The following resources are potentially effected by this module:
- confluence user
- confluence init script
- setenv.sh
- confluence-init.properties
- server.xml
This puppet module will automatically download the Confluence tar.gz from Atlassian and extracts it into /opt/confluence/atlassian-confluence-$version. The default Confluence home is /home/confluence.
class { 'confluence':
javahome => '/opt/java',
}
This module also allows for direct customization of the JVM, following atlassians recommendations
This is especially useful for setting properties such as http/https proxy settings. Support has also been added for reverse proxying confluence via apache or nginx.
class { 'confluence':
version => '5.7.1',
installdir => '/opt/atlassian/atlassian-confluence',
homedir => '/opt/atlassian/application-data/confluence-home',
javahome => '/opt/java',
java_opts => '-Dhttp.proxyHost=proxy.example.com -Dhttp.proxyPort=3128 -Dhttps.proxyHost=secure-proxy.example.com -Dhttps.proxyPort=3128'
tomcat_proxy => {
scheme => 'https',
proxyName => 'confluence.example.co.za',
proxyPort => '443',
},
}
This example is used in production for 2000+ users in an traditional enterprise environment. Your mileage may vary.
confluence::user: 'confluence'
confluence::group: 'confluence'
confluence::shell: '/bin/bash'
confluence::dbserver: 'dbvip.example.co.za'
confluence::version: '5.7.1'
confluence::installdir: '/opt/atlassian/atlassian-confluence'
confluence::homedir: '/opt/atlassian/application-data/confluence-home'
confluence::javahome: '/opt/java'
confluence::java_opts: '-Dhttp.proxyHost=proxy.example.co.za -Dhttp.proxyPort=8080 -Dhttps.proxyHost=proxy.example.co.za -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts=localhost\|127.0.0.1\|172.*.*.*\|10.*.*.*\|*.example.co.za -XX:+UseLargePages'
confluence::manage_service: false
confluence::tomcat_port: '8090'
confluence::jvm_xms: '4G'
confluence::jvm_xmx: '8G'
confluence::jvm_permgen: '512m'
confluence::download_url: 'http://webserver.example.co.za/pub/software/development-tools/atlassian'
confluence::tomcat_proxy:
scheme: 'https'
proxyName: 'webvip.example.co.za'
proxyPort: '443'
confluence
: Main class, manages the installation and configuration of Confluence.
confluence::install
: Installs Confluence binariesconfluence::config
: Modifies Confluence/tomcat configuration filesconfluence::service
: Manage the Confluence serviceconfluence::facts
: Class to get the running version of confluenceconfluence::params
: Default params
Specify the java home directory. No assumptions are made re the location of java and therefor this option is required. Default: undef
The version of confluence to install. Default: '5.5.6'
The format of the file confluence will be installed from. Default: 'tar.gz'
The installation directory of the confluence binaries. Default: '/opt/confluence'
The home directory of confluence. Configuration files are stored here. Default: '/home/confluence'
The user that confluence should run as, as well as the ownership of confluence related files. Default: 'confluence'
The group that confluence files should be owned by. Default: 'confluence'
Specify a uid of the confluence user. Default: undef
Specify a gid of the confluence user. Default: undef
Specify the shell of the confluence user. Default: undef
Whether or not to manage the confluence user. Default: true
Specify context path, defaults to ''. If modified, Once Confluence has started, go to the administration area and click General Configuration. Append the new context path to your base URL.
The initial memory allocation pool for a Java Virtual Machine. Default: '256m'
Maximum memory allocation pool for a Java Virtual Machine. Default: '1024m'
Increase max permgen size for a Java Virtual Machine. Default: '256m'
Additional java options can be specified here. Default: ''
Reverse https proxy configuration. See customization section for more detail. Default: {}
Port to listen on, defaults to '8090'
Defaults to '150'
Defaults to '100'
Any additional tomcat params for server.xml. Takes same format as
tomcat_proxy
. Default: {}
Enable crowd single sign on configuration as described in https://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+Confluence#IntegratingCrowdwithAtlassianConfluence-2.2EnableSSOintegrationwithCrowd(Optional)
Set crowd application name
Set crowd application password
Set crowd application login url, where to login into crowd (e.g. https://crowd.example.com/console/)
Set crowd application services url, e.g. https://crowd.example.com/services/
Set crowd base url, e.g. https://crowd.example.com/
Some more crowd.properties for SSO, see atlassian documentation for details
Some more crowd.properties for SSO, see atlassian documentation for details
Some more crowd.properties for SSO, see atlassian documentation for details
Some more crowd.properties for SSO, see atlassian documentation for details
Should we use augeas to manage server.xml or a template file. Defaults to 'augeas'. Operating systems that do not have a support version of Augeas such as Ubuntu 12.04 can use 'template'.
Default: 'http://www.atlassian.com/software/confluence/downloads/binary/'
iThe md5 checksum of the archive file. Only supported with
deploy_module => archive
. Defaults to 'undef'
Should puppet manage this service? Default: true
Module to use for downloading and extracting archive file. Supports puppet-archive and puppet-staging. Defaults to 'archive'. Archive supports md5 hash checking and Staging supports S3 buckets.
If the Confluence service is managed outside of puppet the stop_confluence paramater can be used to shut down confluence for upgrades. Defaults to 'service confluence stop && sleep 15'
Enable external facts for confluence version. Defaults to present.
- Puppet 3.4+
- Puppet Enterprise
The puppetlabs repositories can be found at: http://yum.puppetlabs.com/ and http://apt.puppetlabs.com/
- RedHat / CentOS 5/6/7
- Ubuntu 12.04 / 14.04
- Debian 7
Operating Systems without an Augueas version >= 1 such as Ubuntu 12.04 must use the paramater:
manage_server_xml => 'template',
We plan to support other Linux distributions and possibly Windows in the near future.
See CONTRIBUTING.md
See CONTRIBUTORS