Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Introduce File Server Install #11

Open
sherl0cks opened this issue Apr 23, 2016 · 3 comments
Open

Introduce File Server Install #11

sherl0cks opened this issue Apr 23, 2016 · 3 comments

Comments

@sherl0cks
Copy link
Contributor

No description provided.

@kameshsampath
Copy link
Contributor

kameshsampath commented May 9, 2016

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 ?

@sherl0cks
Copy link
Contributor Author

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.

@kameshsampath
Copy link
Contributor

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

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

No branches or pull requests

2 participants