This is a rabbit hole that should not be considered unless you have a good understanding of the systems that will be implemented. While I did learn a lot about the frappe framework and install scripts I was not able to get it working properly without rewriting 30% of install.py as the install script wants to update the repo every time unless run in a test mode.
When run in the test mode parts of the productions environment are not setup. On top of that ansible and python report the OS differently (redhat/scientific) and systemd on SL7 uses mariadb.service and not mysql.service. However a mysql.service start script was install using a mariadb.pid so it can be stopped properly by the scripts.
Needless to say I am not pursuing this any further.
BUT running the scrips with the modifications obviously install some dependencies that were breaking the standard bench install so I went back and tried again and was able to get a demo site running through bench.
Overall not to happy with how the scrips assume that there is nothing else running on the machine and broke my other services by blindly overwriting config files (although the nginx.conf was backed up) and causing me to have to go back and reconfigure nearly all important services on my system.
Yes I did see that it was my fault for running it on a production server at my small business.
However, after the dependencies were installed by my modified easy-install scripts, bench installed and configured properly (the first bench errors I could not figure out). Now that I have played with bench a little bit I recommend it over the easy-install scripts.
I am currently evaluating ERPnext for my business and if I find that it will work for me I will be creating a rental module for it that I will make open source. Also I will take a look at the bench dependency scripts and make sure they work for SL7 as that is the platform I use the most.
Thank you Frappe/ERPnext teams for all the work on this project.