manage installation and configuration of Apache Traffic Server.
Currently supported modes: Forward, Reverse and mixed. Supported Platforms: Debian/Ubuntu, FreeBSD: partially. Solaris/Illumos: untested.
It allows to seperately configure plugins, SSL certs and Remap Rules. Storage is configured globally.
This plugin assumes that you have current version of Apache Traffic Server in your packagemanager's repositories. See fpm for a project that allows you to easily create packages.
include trafficserverInstalling Traffic Server, enabling SSL.
class { 'trafficserver':
ssl => true,
}Install it in some weird prefix:
class { 'trafficserver':
prefix => '/opt/es',
sysconfdir => '/etc/es/trafficserver',
}Install it, assign a couple of disks:
class { 'trafficserver':
prefix => '/opt/es',
sysconfdir => '/etc/es/trafficserver',
user => 'ats-cache'
storage => [ '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdf' ],
}Maybe you would prefer to keep cache in a directory on one disk:
class { 'trafficserver':
storage => { /var/cache/trafficserver => 512M },
}Don't install Traffic Server, just configure it:
class { 'trafficserver':
install => false,
}Configure gzip plugin:
trafficserver::config::plugin { 'gzip':
args => '/etc/es/trafficserver/gzip.config'
}Configure stats_over_http plugin. Really, this should be some default:
trafficserver::config::plugin { 'stats_over_http': }Configure balancer plugin. Don't use plugin class. Configure a couple of balancer map:
$balancer_map = [
'http://example1.com',
'http://example2.com'
]
$balancer_algo = [
'roundrobin',
'hash,url'
]
$balancer_backend = {
'serv1.example1.com' => 'serv2.example1.com',
's1.example2.com' => 's2.example2.com',
}
trafficserver::config::remap { 'example_balancer':
balancer_map => $balancer_map,
balancer_backend => $balancer_backend,
balancer_algo => $balancer_algo,
}If you set up multiple load-balance web page, like this example, care to the order of each fields. Here, http://example1.com is going to be load-balance with roundrobin algorithm between serv1.example1.com and serv2.example1.com. And http://example2.com is going to be load-balance with hash,url algorithm between s1.example2.com and s2.example2.com.
Configure a couple of remaps:
$map = {
'http://example.com' => 'http://backend-web01',
'http://example.org' => 'http://backend-web21',
'http://example.net' => 'http://backend-web42',
}
$rev_map = {
'http://backend-web01' => 'http://example.com',
'http://backend-web21' => 'http://example.org',
'http://backend-web42' => 'http://example.net',
}
$redirect = {
'http://example.co.uk' => 'http://example.com/uk',
}
trafficserver::config::remap { 'example_maps':
map => $map,
rev_map => $rev_map,
redirect => $redirect,
}Similarily to remap, we can can setup multiple SSL virtual hosts.
There are two ways to specify more than one virtual host. We can either make multiple calls to trafficserver::config::ssl:
$www = {
'ssl_cert_name' => '/etc/ssl/certs/www.example.com.crt',
'ssl_key_name' => '/etc/ssl/certs/mail.example.com.key',
}
$mail = {
'ssl_cert_name' => '/etc/ssl/certs/mail.example.com.crt',
'ssl_key_name' => '/etc/ssl/keys/mail.example.com.key',
}
trafficserver::config::ssl { 'www.example.com':
ssl_host => $www
}
trafficserver::config::ssl { 'mail.example.com':
ssl_host => $mail
}or we pass it an array:
example_com = [{
'ssl_cert_name' => '/etc/ssl/certs/www.example.com.crt',
'ssl_key_name' => '/etc/ssl/certs/mail.example.com.key',
},{
'ssl_cert_name' => '/etc/ssl/certs/mail.example.com.crt',
'ssl_key_name' => '/etc/ssl/keys/mail.example.com.key',
}]
trafficserver::config::ssl { '*.example.com':
ssl_hosts => $example_com
}- Right now,
@actions/@flters/etc.. in remap rules are not supported. - Add reload hook for storage on FreeBSD device changes
The version in Modulefile should be bumped according to semver during development, i.e.: The first commit after the release should already bump the version, as master at this point differs from the latest release.
When cutting a new release, please
- make sure that all tests pass
- make sure that the documentation is up-to-date
- verify that all dependencies are correct, and up-to-date
- create a new, signed tag and a package, using
rake release:
igalic@levix ~/src/bw/puppet-trafficserver (git)-[master] % rake release
git tag -s 1.3.2 -m 't&r 1.3.2'
...
git checkout 1.3.2
Note: checking out '1.3.2'.
...
HEAD is now at ff9aaae... Most awesomest feature ever. SHIPIT!
puppet module build .
Notice: Building /home/igalic/src/bw/puppet-trafficserver for release
Module built: /home/igalic/src/bw/puppet-trafficserver/pkg/brainsware-trafficserver-1.3.2.tar.gz
igalic@levix ~/src/bw/puppet-trafficserver (git)-[1.3.2] %
- push the tag,
igalic@levix ~/src/bw/puppet-trafficserver (git)-[1.3.2] % git push --tags origin
- and finally upload the new package
Apache Software License 2.0
You can send us questions via mail [email protected], or reach us IRC: igalic hangs out in #puppet
Please log tickets and issues at our Project's issue tracker
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent