[Puppet Users] Puppet Site.pp hierarchy (multi-tenant) question

You probably have several difference choices that might have different
drawbacks or benefits depending on exactly how you're managing things.
One option that comes to mind is to use something like 'environments' to
define a different site.pp file for each tenant. Each tenant could "claim"
the machines under their control by setting a property on the console or in
the agent's puppet.conf like so:

[agent]
tenant = "teamA"

In your master's puppet.conf, something like this:

[master]
manifest = "/usr/local/etc/puppet/tenant/${tenant}/manifests/site.pp

And so Team A's site.pp would be at:
/usr/local/etc/puppet/tenant/teamA/manifests/site.pp

You could arrange the directory/manifest structure there any way you want.
This would be equally as valid:
[master]
manifest = "/usr/local/etc/puppet/manifests/${tenant}-site.pp

Any method of getting the 'tenant' global variable defined would work.
Which to choose is a matter of pereference. Some examples: a puppet.conf
definition, a custom fact, a piece of data pulled from Hiera... The
documentation on setting up environments might be of interest to you.
<http://docs.puppetlabs.com/guides/environment.html>

If you worry that 1 team will add node classification of another one, then
the only way is via enviroments, each enviroment will have it's own site.pp
if that's not the case, you can just put "include nodes.d" in the site.pp,
create a directory named "nodes.d" and then have different files for each
team.