[EPIC] Refactor Lab Provisioner

[tima]

The following are notes for refactoring the lab provisioner into something that address is many known bugs, feature requests and projected growth of the lightbulb lab provisioner.

Lightbulb OS Support

• control: RHEL7 or CentOS7
• nodes: RHEL7, CentOS, Ubuntu (or Debian?) -- eventually Windows, VyOS

NOTE: This plan is currently missing an email feature. Also need to flesh out data structures for users (students and instructors), AMIs/regions and lab layouts. Need switch for pre-installing ansible core and/or Tower.

Lightbulb Provisioner Roles

• lightbulb-provisioner-aws (See #196)
• lightbulb-common-linux (See #194)
• lightbulb-control (See #195)
• lightbulb-instructor (See #195)

TBD/TODO

• Email Tower License file if provided (More here)
• Emailing of student inventories etc? Separate role or embed in playbook? Different means and provisioners? Bug Here
• Create IAM user(s) and assign to instance profile to facilitate dynamic inventory in Tower labs
  • Not sure we still need this or it's worth the effort.
• Suggest a different practice around passwords
  • How does this shakes out with all of the refactoring.
• Document pip install passlib
• Lab provisioner tags are not documented and seem excessive Remove?

Later

lightbulb-haproxy

• yum install what?
• configure with web nodes?
• ports for firewall to open?

Starter code? https://github.com/tima/8ball-service/tree/master/playbooks/roles/haproxy

lightbulb-provisioner-azure

provisioner-aws but using Azure services (See #197)

Lab Layouts

WIP (See #198)

[petebowden]

I'd be more than happy to help work on this migration, but I'm not sure where to begin? Have some of these tasks been completed in another fork?