Bug 695556

The biggest change is that there are now two applications the user will interact with.

RHUI Installer - This is largely what the previous iteration of "RHUI Tools" was. It will look very similar to the previous setup: a series of questions for various files that ultimately produces configuration RPMs that are installed on each piece (RHUA, CDS, Load Balancer - all of those are the same). The amount of questions asked is significantly smaller since it's acting as much more of an installer than before. It's simply enough to get the pieces up and running (just not doing anything).

RHUI Manager* - This is brand new to RHUI and, well, large. It's an interactive shell that provides the ability to configure a running RHUI. Configuration includes:
- Red Hat content certificate upload (either initially or when we issue a new one with more entitlements)
- Red Hat repository import. Using the content cert as the basis, the user can select one or more products within to import and be managed by the RHUI.
- Custom repository creation. This is entirely new to RHUI itself and was never previously supported. Users can create repositories and upload their own content to them. Additionally, these repositories will be protected, requiring clients to use entitlement certificates in the same way they do to access Red Hat provided content.
- Content Delivery Server (CDS) management, including the registration, unregistration, and selection of which repos to deploy to which CDS instances.
- Creation of entitlement certificates, allowing both Red Hat provided repositories and any custom repositories to be included in their creation.
- Client configuration RPM creation.

* We're still deciding on the actual name, whether the overall umbrella for both apps is "RHUI Tools" which is then made up of Installer and Manager, or if we just call the manager piece "RHUI Tools". I'll update the bug when I get a final decision.

I'll leave it up to you to figure out the best way to split these up. There's probably a model for install v. usage that you follow for docs, which is what I think this would fall under.