Bug 1298438

Summary:	[RFE] revisit subscription-manager's caching behavior
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Snyder <csnyder>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:	John Sefler <jsefler>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	6.8	CC:	jgalipea, vrjain
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 11:49:35 UTC	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 Chris Snyder 2016-01-14 05:51:17 UTC

I think it is a good idea to revisit the caching in subman to maybe move to python-rhsm. The caching behavior seems to be on network bound operations. Furthermore it seems to have the most utility when the connection to the server is broken in someway (that is when most of the caches are used). Its almost like we are testing the connection object that is passed into the cache objects and returning the contents of said cache object if the connection object fails the test (the update from/to the server).

The suggestion is to move the caching to be part of python-rhsm. I would also like to add that it would be very nice for these modifications to include a method of determining the source of the returned value for all cached resources (basically it would be neat to have a method that would return the source of the last result).

These improvements could include a separate connection object that caches all interactions with the server but does not necessarily need to.

Comment 2 vritant 2016-08-01 20:33:09 UTC

Increasing the scope of this RFE, in order to not tie us to a specific implementation or purpose. basically, we need to redesign subscription-manager caching.

Comment 3 Jan Kurik 2017-12-06 11:49:35 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/