Good night,
It is possible to use the smart proxy just as TFTP, DNS, DHCP, and Puppet CA
?
The infrastructure topology that I'm riding is in the attached image.
The idea is to make the cloud2, have a controlling smart proxy servers and
also to the AC network 192.168.131.0/24 segment.
However, I wish the servers would use the classes in puppet published in
foreman.cloud1.domain.local, it is possible to use classes that are the
foreman, through the proxy smart?
We do something similar-ish to this, works fine, but split even more.
The caveat is that if you have two different puppet masters with the same
named classes, they should be the same classes (or take the same
parameters). Otherwise when you import it will keep overwriting your old
required parameter list.
Example… puppet 1 has a class called 'apache'. it takes two params,
interface and rooturl. puppet2 has a class also called apache that takes
three params, interface, rooturl and an additional one called 'port'.
Importing from puppet1 will override the puppet2 definition, and vice
versa. If you keep your puppet classes in sync between puppet1 and puppet2,
it won't be a problem. Otherwise you should call the puppet class
apache-cloud1 or some other hackish thing. 
On Wednesday, January 8, 2014 6:44:45 PM UTC-8, Eduardo Terzella wrote:
Good night,
It is possible to use the smart proxy just as TFTP, DNS, DHCP, and Puppet
CA?The infrastructure topology that I’m riding is in the attached image.
The idea is to make the cloud2, have a controlling smart proxy servers and
also to the AC network 192.168.131.0/24 segment.However, I wish the servers would use the classes in puppet published in
foreman.cloud1.domain.local, it is possible to use classes that are the
foreman, through the proxy smart?
