Bug 864109

Summary: [RFE] Remove `aeolus-restart-services`, `aeolus-check-services` and enhance `aeolus-services {start|stop|restart|status}`
Product: [Retired] CloudForms Cloud Engine Reporter: Aaron Weitekamp <aweiteka>
Component: aeolus-configureAssignee: Steve Linabery <slinaber>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: slinaber
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aaron Weitekamp 2012-10-08 15:13:57 UTC
Description of problem:
2 ways to restart services causes user confusion and code duplication. Also `aeolus-check-services` should be moved into `aeolus-services status`


Version-Release number of selected component (if applicable):
1.1
[root@qeblade40 aeolus-conductor]# rpm -qa |grep aeolus
aeolus-conductor-daemons-0.13.16-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-doc-0.13.16-1.el6cf.noarch
aeolus-conductor-0.13.16-1.el6cf.noarch
rubygem-aeolus-cli-0.7.3-1.el6cf.noarch
aeolus-all-0.13.16-1.el6cf.noarch
aeolus-configure-2.8.8-1.el6cf.noarch

Actual results:
`aeolus-restart-services` and `aeolus-check-services` don't follow pattern `aeolus-services {start|stop|restart|status}`

Expected results:
`aeolus-services {start|stop|restart|status}`

Comment 2 Steve Linabery 2012-10-30 15:05:00 UTC
https://github.com/aeolusproject/aeolus-configure/pull/15

3e0b592de618a5da86e86b7fb89583dec46cb01f on master