Skip to content

simp/pupmod-simp-rsync

Repository files navigation

License CII Best Practices Puppet Forge Puppet Forge Downloads Build Status

This is a SIMP module

This module is a component of the System Integrity Management Platform, a compliance-management framework built on Puppet.

If you find any issues, they can be submitted to our JIRA.

Please read our Contribution Guide.

Module Description

This module configures rsync for sharing large files that would be problematic to share using the native Puppet fileserving type.

Setup

Configuring Host as Server and Client

By default, in the 'simp' configuration scenario, an rsync server is configured on the primary Puppet server. In some configurations, it may be necessary to have supplemental rsync servers to sync files to clients (one example: PE MoM and Compile Master architecture).

To configure a Compile Master (or other node) to function as both a server and a client (of the primary server), setup hiera for the node:

rsync::server::global::port: 8873
rsync::server::trusted_nets:
  - <client_net>
  - <client_net>

This will configure an rsync server that utilizes stunnel for connections from the client_nets listed. To configure clients to utilize this new server, set their hieradata:

simp_options::rsync: 'fqdn.rsync.server'

to override the standard 'true' boolean value.

NOTE: If not using stunnel for the server/client connections, both values for rsync::server::trusted_nets and rsync::server::global::trusted_nets will need to match, as well as the trusted_nets values for any rsync::server::section resources. These all default to '127.0.0.1' for stunnel usage.

Reference

Please refer to the REFERENCE.md.

Limitations

SIMP Puppet modules are generally intended for use on Red Hat Enterprise Linux and compatible distributions, such as CentOS. Please see the metadata.json file for the most up-to-date list of supported operating systems, Puppet versions, and module dependencies.

Development

Please read our Contribution Guide.

Visit the project homepage on GitHub, and look at our issues on JIRA.