Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pe_agent provision from local cache #131

Open
cdenneen opened this issue Mar 22, 2017 · 1 comment
Open

pe_agent provision from local cache #131

cdenneen opened this issue Mar 22, 2017 · 1 comment

Comments

@cdenneen
Copy link

Is there a way to install from download_file location rather than contacting master? Would be beneficial when offline or off VPN with no connectivity to master and don't want to have to spin up a master in vagrant... makes pe_build useful for installing latest PE version on agent to do local applies with. (beats having to deal with latest boxes on atlas with 4.3.2 on them)

@Sharpie
Copy link
Member

Sharpie commented Mar 31, 2017

This currently isn't supported by the pe_agent provisioner as it just calls through to the pe_repo module on the master. Looking at the top-level class in pe_repo, the staging directory where tarballs are stored is hard-coded to /opt/puppetlabs/server/data/staging and isn't exposed as a parameter. So it's not possible to configure pe_repo for a shared tarball cache.

The other option would be to add some logic to the provisioner to download and copy repo files outside of the provisioner --- but the code paths that handle that for pe_bootstrap aren't set up to handle agent version numbers. So, this is probably blocked on getting #97 done first so that pe_build is aware of PE version/agent version combinations instead of delegating that entirely to the pe_repo module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants