Hello,
You are describing a problem we run into every now and then. Your default
profile is what we call "mandatory" here, and then you have an edge case
where 99% of your servers have Postfix the same way, and a couple have it a
different way. Unfortunately that 99% means Postfix is not mandatory and so
can't live in your default profile.
If you use smart class inheritance to structure your roles you should be
able to remove most of the places you need to include postfix. Something
like this:
class role::base {
include profile::mandatory
include profile::somethingelse
include postifx
}
class role::anotherserver inherits role::base {
include profile::anotherprofile
}
class role::postfixrelay {
include profile::mandatory
include profile::postfixrelay
}
Or another way would be move the majority of your postfix business logic
out of Hiera (which as you describe is not working for you) and handle it
in a profile. The below code introduces a simple Enum on your profile to
control what "type" of postfix you want:
class profile::mail(
$type = 'normal',
) {
if ($type == 'normal') {
class { 'postfix':
... normal stuff ...
}
}
elsif ($type == 'relay') {
class { 'postfix':
... relay stuff ...
} else {
fail("Type '$type' is not supported")
}
}
$ cat /etc/puppet/hiera/networks/192.168.155.0.yaml
...
profile::mail::type: 'relay'
I personally would prefer the second option. It enforces the same postfix
config on almost all your servers (looking at your Hiera hierarchy there
are plenty of levels to make your servers' Postfix "different" from each
other). It's also easy to test with rspec.
-Luke
On Tuesday, 18 October 2016 18:56:59 UTC+1, Ugo Bellavance wrote:
>
> Hi,
>
> I am using camptocamp/postfix for my postfix configuration. I originally
> defined all my configs manifests but now I would like to change to using
> hiera. Unfortunately, this module doesn't support hiera for some of the
> configs, so I must define many parameters in the manifests. I wanted to
> use hiera for simplicity, but also because I have a very nice use case: I
> have one SMTP front-end with its own specific configs (anti-spam/virus),
> and a series of regular hosts. Traditionally, all hosts that are in the
> same subnet as the Exchange server would use it as relayhost and all the
> other hosts use the smtp front-ends. Therefore, here's what I did:
>
> hiera.yaml:
>
> ---
> :backends:
> # - regex
> - yaml
> :yaml:
> :datadir: /etc/puppet/hiera
> #:regex:
> # :datadir: /var/lib/hiera
> :hierarchy:
> - "host/%{fqdn}"
> - "domain/%{domain}"
> - "env/%{::environment}"
> - "os/%{operatingsystem}"
> - "osfamily/%{osfamily}"
> - "networks/%{network_ens192}"
> - "virtual/%{::virtual}"
> - common
>
> This way, I define the exchange server as relayhost for the exchange
> network in /etc/puppet/hiera/networks/192.168.155.0.yaml, and set the smtp
> frontend as relayhost in /etc/puppet/hiera/common.yaml.
>
> However, since I can't put all the settings in hiera, I must put some in
> the class declaration for the smtp frontends. When I declare the postfix
> class in both my default profile and in the smtp frontend profile, I get an
> error saying that the class cannot be declared twice (Class[Postfix] is
> already declared; cannot redeclare at
> /etc/puppet/manifests/nodes/smtp_postfix_servers.pp:19)
>
> Another solution would be to declare the profile in all my roles, but it's
> far from perfect.
>
> Is there a simple solution?
>
> I guess that I could do an if based on ipaddress in my default profile,
> but I wanted to use hiera as much as possible. Yes I created an issue to
> ask for full hiera support.
>
> Thanks,
>
> Ugo
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/0e4f3884-dffe-46cb-ba31-cdf003df044d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
