Bug 844384 - [RFE] No options to filter the logs by group of users, deployable, image,pool family, front end realm, hardware profile
Summary: [RFE] No options to filter the logs by group of users, deployable, image,pool...
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Tzu-Mainn Chen
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-30 13:00 UTC by Rehana
Modified: 2020-03-27 18:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
filter (239.34 KB, image/png)
2012-07-30 13:00 UTC, Rehana
no flags Details

Description Rehana 2012-07-30 13:00:08 UTC
Created attachment 601260 [details]
filter

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.Move to monitor --> logs
3.Check the filter options (pfa:filter.png)
  
Actual results:
Observed that as per the user story/feature list given here 
URL https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Allow_Conductor_to_keep_a_history_of_deployment_activity it is expected to add all the mentioned filter options in the log page

Expected results:
all the filter options should be provided

Additional info:
 rpm -qa | grep aeolus
rubygem-aeolus-cli-0.6.0-0.20120723230034git2a28761.fc16.noarch
aeolus-conductor-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120723230037git05a815a.fc16.noarch
aeolus-conductor-doc-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch
aeolus-all-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch
aeolus-configure-2.7.0-0.20120723230032gitcc8302d.fc16.noarch
aeolus-conductor-daemons-0.11.0-0.20120725030008gitcdc50c9.fc16.noarch

Comment 1 Dave Johnson 2012-07-30 18:36:09 UTC
adding severity and flipping onto v1.1 as it relates to current user stories being implemented for v1.1


Note You need to log in before you can comment on or make changes to this bug.