Open sherl0cks opened 8 years ago
In my head, this use case is targeted at scenarios where a company wants to host the files internally for network or security reasons. Therefore, I'm not really concerned about how the web server is stood up, but rather making sure that the playbook knows how to work with a simple web server.
what i spoke about was convenience stuff rather a nice to have, going by assumption that customer already has the repo running in some HTTP server inside his org then I did have that handled in my original playbook https://github.com/kameshsampath/ansible-middleware-playbooks-orig/blob/master/provisioning/vars/common_vars.yml , where i did have a software_repo
which handles the scenario of fileserver install, i used a shared folder there but the unarchive task can hook up to the http as well I did try both the cases and works like a charm. In our case we can do a this when the customer install type is not CSP
if you see the Packer it spins a http server from the within directory where we start the packer build command, a thought is to have something similar so that when our playbook starts it runs a small http server from the control machine from where the distros could be served, a nice to have is we could still automate all downloads all required bundles form our CSP using a separate playbook inside a specific directory and make it served form Control Machine
Shall we do something similar for our file server install ?