Bug 5229 - Allow for inheritance when deploying Log Settings
Summary: Allow for inheritance when deploying Log Settings
Status: VERIFIED FIXED
Alias: None
Product: Identity Designer
Classification: Identity Manager
Component: Configuration Management (show other bugs)
Version: 1.0.0 Designer
Hardware: Other Other
: P1 - Urgent : Major (vote)
Target Milestone: 1.0 M5
Assignee: Mike Simpson
QA Contact: Tim Pew
URL:
Whiteboard:
Keywords: Built, Provo
Depends on:
Blocks:
 
Reported: 2005-01-13 15:12 UTC by Brent Thurgood
Modified: 2011-06-03 19:03 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brent Thurgood 2005-01-13 15:12:53 UTC 
DETAILED DESCRIPTION:
The driver log settings can be inherited from the Driver Set. The deploy code 
needs to take this into account. 

BUILD NUMBER: 
Oses/CONFIG: 
STEPS TO REPRO: 
RESULTS:
EXPECTED: 
WORKAROUNDS: 
CUSTOMER IMPACT: 


NTS entered defects should also include:
Additional debug info like screenshots, screencams, log files, trace files,
packet traces, memory coredump location.
Accurate customer information so that proper prioritizing of the defect is
possible (mainly for NTS defects)
Comment 1 Brent Thurgood 2005-05-04 19:45:44 UTC 
Deploy handles inheritance if the Driver getter methods return null for the 
various settings. However we do not display inheritance to the user well in 
the GUI. 

We also need to be able to remove the settings from the Driver object in 
eDirectory if they are inherited. Right now the deploy code only sets values 
it does not remove values that are already set.
Comment 2 Brent Thurgood 2005-05-20 01:54:14 UTC 
 Deploy handles inheritance correctly but we need to make sure the GUI is able 
to handle it. This defect is a reminder that when the GUI is setup for 
inheritance that we verify deploy with inheritance works. It does not need to 
be M4.
Comment 3 Brent Thurgood 2005-06-20 20:57:28 UTC 
Change Driver Trace config page to handle inheritanceof Trace Level, Trace 
File and Trace file size limit. 

It would be acceptable to handle inheritance for all 3 with one inherit check 
box. 

When inherited the config page should set the appropriate values to null. The 
deploy code will then be able to detect whether the values should be inherited 
or not.
Comment 4 Mike Simpson 2005-06-21 14:50:50 UTC 
Brent, I have finished this implementation. Here are the details: I added 
parameter support so we can actually preserve the Trace settings on a driver 
when the "use driverset trace settings" is selected. I implemented the 
following static method in the DriverMiscPage class for your query convenience:

public static boolean isUsingDriverSetTraceSettings(Driver driver)

If there is a problem with doing it this way, let me know. I thought this 
would be the most convenient way to preserve old settings just in case a user 
wanted to revert.

M
Comment 5 Howard Vanfleet 2005-06-24 19:47:07 UTC 
Build:20050621
Comment 6 Bill Street 2007-04-30 16:37:38 UTC 
Marking closed/resolved fixed bugs public view.
Comment 7 Bill Street 2007-04-30 16:40:18 UTC 
Marking closed/resolved fixed bugs public view.