Bug 759563

Summary: FEAT: Hardware catalog should support additional friendly url types
Product: [Retired] Red Hat Hardware Certification Program Reporter: Rob Landry <rlandry>
Component: Hardware CatalogAssignee: Pengfei Xue <pxue>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: hwcert-catalog, wshen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://hardware.redhat.com/
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-07 02:54:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 750716, 761629, 761631    

Description Rob Landry 2011-12-02 17:26:29 UTC
Description of problem:

Currently the catalog only supports a single level of friendly urls; hardware.redhat.com/RHEL6 for example; this request is to allow for two levelsof supported friendly URLs into combinations; for example  ~/RHEL6/{Vendor} and ~/{Vendor}/RHEL6  Also, to enable minor release results; ~/RHEL5.4; and lastly support realtime as a keyword for MRG Realtime cert listing.

Comment 1 Pengfei Xue 2011-12-05 06:35:57 UTC
(In reply to comment #0)
> Description of problem:
> 
> Currently the catalog only supports a single level of friendly urls;
> hardware.redhat.com/RHEL6 for example; this request is to allow for two
> levelsof supported friendly URLs into combinations; for example 
> ~/RHEL6/{Vendor} and ~/{Vendor}/RHEL6  Also, to enable minor release results;
> ~/RHEL5.4; and lastly support realtime as a keyword for MRG Realtime cert
> listing.

changed the url rewrite rules, now it can support:
[one level url]
 ~/rhel6   major version
 ~/rhel6.1 major.minor version
 ~/rhemrg  real time 
 ~/dell    vendor 

[two levels url]
 ~/rhel6/dell       major version + vendor
 ~/dell/rhel6       vendor + major version
 ~/dell/proi        vendor + make
 ~/3dvision/rhel6.1 vendor + major.minor version
 ~/rhel6.1/3dvision major.minor version + vendor

Comment 2 Pengfei Xue 2011-12-05 06:39:38 UTC
Created attachment 540647 [details]
patch for friendly url

Comment 3 Rob Landry 2011-12-05 16:41:30 UTC
(In reply to comment #2)
> Created attachment 540647 [details]
> patch for friendly url

How will the patch work in the longer term as we look towards even more layers?

hardware.redhat.com/Dell/PowerEdge/RHEL7

hardware.redhat.com/Dell/PowerEdge/R915

hardware.redhat.com/ia64

Comment 4 Pengfei Xue 2011-12-06 09:19:32 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Created attachment 540647 [details]
> > patch for friendly url
> 
> How will the patch work in the longer term as we look towards even more layers?
> 
> hardware.redhat.com/Dell/PowerEdge/RHEL7
> 
> hardware.redhat.com/Dell/PowerEdge/R915
> 
> hardware.redhat.com/ia64

if url levels are up to 3 and the combination elements could be arch, vendor, make, model and rhel version, then we need another way to provide friendly url, such as redirect to a perl script which dose some complicated works.

Comment 5 Pengfei Xue 2011-12-09 07:07:32 UTC
Created attachment 544358 [details]
patch for friendly url

Comment 6 Pengfei Xue 2011-12-09 07:12:03 UTC
Created attachment 544360 [details]
url redirect

with this url redirect, we can support all the combinations of arch, model, rhel version, etc.

Comment 7 Pengfei Xue 2011-12-12 06:11:42 UTC
Created attachment 545593 [details]
new patch for friendly url

~/x86, return all the x86 arch certs

Comment 8 Pengfei Xue 2011-12-12 06:12:54 UTC
Created attachment 545594 [details]
urlmap.cgi

Comment 9 Rob Landry 2011-12-12 17:17:53 UTC
In practice will this retain the URL value of hardware.redhat.com/dell or does the user see the change over to urlcgi?value= ?

Comment 10 Pengfei Xue 2011-12-13 02:48:41 UTC
(In reply to comment #9)
> In practice will this retain the URL value of hardware.redhat.com/dell or does
> the user see the change over to urlcgi?value= ?

user can see the changed url, now we are using external explicit url redirect