Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 839512

Summary: [RFE] Add pagination on Hardware profile page.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: dajohnso
Target Milestone: rcKeywords: FutureFeature
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:
Attachments:
Description Flags
hardware profile page none

Description Aziza Karol 2012-07-12 07:26:28 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
Currently  all the hardware profiles is listed in one page only. see attached screenshot.


Expected results:
limit hardware profile list to 15  or so per page.

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-0.11.0-0.20120711193423gitd22a075.fc16.noarch
rubygem-aeolus-cli-0.6.0-0.20120711153513gite2a391a.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120711153448git05a815a.fc16.noarch
aeolus-conductor-daemons-0.11.0-0.20120711193423gitd22a075.fc16.noarch
aeolus-configure-2.7.0-0.20120711153505gite93c068.fc16.noarch
aeolus-all-0.11.0-0.20120711193423gitd22a075.fc16.noarch
aeolus-conductor-doc-0.11.0-0.20120711193423gitd22a075.fc16.noarch
aeolus-conductor-devel-0.11.0-0.20120711193423gitd22a075.fc16.noarch

Comment 1 Aziza Karol 2012-07-12 07:27:11 UTC
Created attachment 597723 [details]
hardware profile page

Comment 2 Dave Johnson 2012-07-12 19:45:27 UTC
hmm, not sure if there is any requirement for it or not... the major driver for adding pagination on the other pages was performance issues I believe.  Leaving open for development consideration.