Bug #14266
closedproxy-puppet - import classes to foreman takes ages
Description
Hello,
I am currently working on a project to refactor our foreman infrastructur. For that I was setting up a continuous deployment with r10k and mcollective. Now I am at the point to import the deployed puppet environments into foreman. I found some nice cli command which do my work (foreman-rake/hammer-cli). But the biggest problem which I found out that it takes ages to import 50 modules for 10 environments (at least for me).
I have already tried many different thinks:
- used a special proxy running on a bare metal machine just for importing classes
- tested current stable
- tested 1.11-rc2
It is always the same behavior, after adding/scanning 2-3 environments on the proxy the foreman-proxy is getting slower and slower and slower. The first environment takes ~120 seconds to scan, the second takes ~200 seconds and than is getting slower and slower. The 5th environment already takes ~35 minutes and I can see in the DEBUG output the proxy need 14 seconds for scanning on file. After adding some more environments the proxy needs up to 30 seconds to scan just ONE puppet file.
My question is: Is this a known behavior? Can I adjust some settings to make this class scanning faster?
regards,
Mike F.