Added scripted install and added to install.md

[StevenMercurio]

I added a setup script that automates a lot of the install and leaves room for updates that not only can install but perform ongoing updates. Later I can create puppet manifests based on this.

[curt-matthews]

How about changing that script to an Ansible playbook?

[StevenMercurio]

I don't have ansible. When I get time the next step was going to be automating the provisioning AND install via Sat6/puppet which is where ALL my other builds/configs are and what I have the most progress done to date in. I will do it in my blade server lab first then test (99.999% sure it's just going to work) in AWS using the AWS CF image and my AWS Sat6.2.13 capsule server via the site-to-site VPN.

[curt-matthews]

You would need to create a new project for all of the puppet stuff. We have a project for Ansible automation of CloudForms. I will try to find some time to convert your bash script to an Ansible playbook.

[StevenMercurio]

For Sat6 shops that is not going to be any use unless you are talking a local "scp in and run" that does it and does not need tower which if its 100% local would be fine.

I was planning to do the same thing I do for all the other RH products which is get Sat6 to build it and it's IDM integration to auto-reg to IDM/DNS then just go in and do all the config work including any and all content imports it they exist all at once. If CF had a CLI like hammer I'd just automate the entire config end to end like I did with Sat6 building Sat6, RHV-H, RHV-M, and IDM servers

I have also started creating a full RPM and puppet based install of the upstream MIQ project. I started creating RPMs for all the gems and things and puppet code will do the heavy lifting. We need a solid fully versioned 100% local sourceable MIQ install (updates and creations of RPMs will all be 1000% automated) that ppl in my group can use to create additional cloud provider code on.