Bug 1053334 - Using hwcert db data only for public view
Summary: Using hwcert db data only for public view
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Hardware Catalog
Version: 5.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Junhui Wang
QA Contact:
URL:
Whiteboard:
Depends On: 1053340 1053351 1054566 1058650 1063107 1063125 1065633
Blocks: 1045330
TreeView+ depends on / blocked
 
Reported: 2014-01-15 03:50 UTC by Tony Fu
Modified: 2015-02-01 23:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-14 05:28:25 UTC
Embargoed:


Attachments (Terms of Use)

Description Tony Fu 2014-01-15 03:50:50 UTC
Description of problem:



At the moment, catalog will need to fetch data from both bz database and hwcert database for most of actions and it can cause some performance issues.  We need to shift this to use data from hwcert database only eventually.

This bug is a tracker of using hwcert db data only for public view.

Comment 1 Tony Fu 2014-01-15 03:51:38 UTC
Further details

http://hwcert.pad.engineering.redhat.com/catalog-bz-separation

Comment 2 Huan Zhang 2014-01-15 08:28:44 UTC
In my opinion:
We should do the following steps:
1. db schema design
2. use ORM framework
3. compose utility methods(CRUD)
4. call those ORM CRUD from cigs
5. add switch for old db/new db

@tfu,
What do you think?

Comment 3 Tony Fu 2014-01-16 04:50:53 UTC
(In reply to Huan Zhang from comment #2)
> In my opinion:
> We should do the following steps:
> 1. db schema design
> 2. use ORM framework
> 3. compose utility methods(CRUD)
> 4. call those ORM CRUD from cigs
> 5. add switch for old db/new db
> 
> @tfu,
> What do you think?

I think introduce ORM for this release is a bit risk IMHO.  We probably need to do some prove of concept stuff before we can move it to production.

Comment 4 Tony Fu 2014-03-14 05:28:25 UTC
verified on live.


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