Bug 1332270 - [RFE] Ability to quickly associate entitlements with consumers
Summary: [RFE] Ability to quickly associate entitlements with consumers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 0.9.51
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: vritant
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-02 17:47 UTC by smcdowel
Modified: 2016-07-22 14:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-22 14:51:49 UTC


Attachments (Terms of Use)

Description smcdowel 2016-05-02 17:47:53 UTC
Problem statement from Davis Wahl:
In brief, we need to be able to quickly associate entitlements with consumers, so that we can sort and group consumers by the entitlements they consume. 

While the consumer/entitlement endpoint does this, it can only target a single consumer, which means making 1 rest call per consumer -- which is prohibitively slow for non trivial #'s of consumers. 


From an email thread between Davis and Vritant:
Add an owner_id query parameter, so we can at least restrict the
total data in the set to match against to just the entitlements owned
by the owner

This exists in Candlepin 2.0, but we are requesting it be backported to 0.9.51 to unblock current work on RHN UI EOL stories.

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

Comment 2 Chris Snyder 2016-05-05 17:18:40 UTC
In candlepin-0.9.51-HOTFIX as of the below commit:

commit 72a0f63c92fe038cd25d689959bb8c8064e3e8f8
Author: Vritant Jain <vrjain>
Date:   Tue May 3 15:00:41 2016 -0400

    1332270: Ability to quickly associate entitlements with consumers



New build to follow shortly.

Comment 5 Barnaby Court 2016-07-22 14:51:49 UTC
Marking as closed per Candlepin procedures as a fix has been merged or it has been determined to not be an issue.


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