Bug 1386077

1. Proposed title of this feature request  
Maintenance controls addition to GUI

2. Who is the customer behind the request?  
Account: Emergent 360 (5698072) 
TAM customer: No
SRM customer: No
Strategic: No

3. What is the nature and description of the request? 
The RFI is to expose and "unhide" from cron all the maintenance functions
(foreman-rake, etc) currently in cron and other places into a maintenance
and diagnostic section of the gui (possibly under monitor dropdown).  The
goal is to take all the maintenance scripts/actions and make them
tasks/jobs similar to those a user would create for VMs.  The user should
also be able to changge schedules so that jobs run at their off-peak hours
and run jobs manually.  This way if something is not running well or users
do a lot of changes (like remove a bunch of repos and went to free space
immediately) they can.  Ideally some text would be added to the GUI to
explain what each is and when/why to run it.  If certain things should not
be changed or attempts are made to change outside of reccomended parameters
warnings should be displayed.  Optionally using SAR data from the Sat6
server a "reballance" button chould look at SAR data to "auto-schedule" the
jobs to the least bustyiest time for the user.  Also a user can run these
jobs manually say before an update to help smooth the update.

4. Why does the customer need this? (List the business requirements here)  
This is needed for many reasone.  If a user remioves a bunch of repos and
needs the space right away (emergency or reg outage window to solve disk
space issue) they can run a rake to reclaim space.  If something is not
running right before opening a ticket the user can run some jobs manually
to chean things up and see if that helps (**It DID in my case!**).  Prior
to update/upgrade the commands can be manually run.  If asked by support
the user can run these from the GUI and Sat6 would log ALL this output like
it does for all other jobs.  For standardization: Sat6 is complex enough so
making the Sat6 server as close as possible to how you handle other
serversa helps.  Less "exceptions" or special things to learn reduces costs
in trainuing, etc.  Scheduling:  Red Hat can nopt possibly klnow when the
off-time is or best time is to schedule these tasks but a user does.
Sometimes the only way is via maintenance window and run them manually.
LOGGING: As all jobs/tasks are ,logged folding the maintanance tasks under
those APIs means less custom code and utilizes critical loggin APIs for
maintenabncs tasks which can help users AND support!

5. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
No.

6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
The sooner the better but a patch would just be a menu driver bash or
other script similar to "appliance_console" command in CFME.  ALL the jobs
that can bve trun sghould be there.  That is REALLY needed ASAP.  Short of
that at least a KB artcle or DOC page.

7. Is the sales team involved in this request and do they have any additional input?  
No.

8. List any affected packages or components.  
NA

9. Would the customer be able to assist in testing this functionality if implemented?  
ABSOLUTELY!   I would LOVE to get much more involved and help as much as
I can!