Bug 798287 - Replace Aeolus with Cloud Engine
Summary: Replace Aeolus with Cloud Engine
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Tomas Sedovic
QA Contact: pushpesh sharma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 14:28 UTC by Tomas Sedovic
Modified: 2014-08-04 22:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 22:47:46 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Tomas Sedovic 2012-02-28 14:28:56 UTC 
Description of problem:
Make sure all occurences of "Aeolus" or "Conductor" are replaced with "CloudForms Cloud Engine"
Comment 1 Tomas Sedovic 2012-02-28 15:23:34 UTC 
A lot of project name mentions was in pages that we're no longer using anyway. This patch removes them:

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/009220.html
Comment 3 Tomas Sedovic 2012-03-13 16:06:56 UTC 
Pushed: 47774c12ed25ce03873106025a994efe09021bd9
Comment 5 wes hayutin 2012-03-30 19:02:24 UTC 
assigning to Pushpesh
Comment 6 pushpesh sharma 2012-04-04 13:36:48 UTC 
I didn't find any instances of "aeolus" in latest web-UI.Marking this bug as verified.

[root@qe-blade-01 ~]# rpm -qa|grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.1-1.el6.noarch
aeolus-conductor-doc-0.8.7-1.el6.noarch
aeolus-all-0.8.7-1.el6.noarch
aeolus-conductor-daemons-0.8.7-1.el6.noarch
aeolus-configure-2.5.2-1.el6.noarch
aeolus-conductor-0.8.7-1.el6.noarch
Comment 7 errata-xmlrpc 2012-05-15 22:47:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html
Note You need to log in before you can comment on or make changes to this bug.