Bug 281631

Summary: Pass in schema and config LDIF files to setup
Product: [Retired] 389 Reporter: Rich Megginson <rmeggins>
Component: Install/UninstallAssignee: Rich Megginson <rmeggins>
Status: CLOSED CURRENTRELEASE QA Contact: Viktor Ashirov <vashirov>
Severity: low Docs Contact:
Priority: medium    
Version: 1.1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-07 16:35:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 240316, 427409    
Attachments:
Description Flags
diffs
none
cvs commit log none

Description Rich Megginson 2007-09-06 22:57:29 UTC 
We should allow the user to pass in additional schema files and additional
config entries during setup to allow e.g. custom schema with the
InstallLdifFile, or the creation of additional suffixes/databases, or
replication configuration, or whatever.
Comment 1 Rich Megginson 2007-09-06 23:01:16 UTC 
Created attachment 189321 [details]
diffs
Comment 2 Noriko Hosoi 2007-09-06 23:30:04 UTC 
Looks good to me.
Comment 3 Rich Megginson 2007-09-07 15:03:17 UTC 
Created attachment 190001 [details]
cvs commit log

Reviewed by: nhosoi (Thanks!)
Files: see diff
Branch: HEAD
Fix Description: 1) Allow multi-valued parameters in .inf files and command
line.  These values will be represented internally as an array ref.  No
existing parameters allow being multi-valued (e.g. you can't use Suffix=o=foo
and Suffix=o=bar)
2) Add two new .inf parameters - SchemaFile and ConfigFile.  The files listed
in SchemaFile will be copied into the schema subdirectory of the new instance,
so they must already be named appropriately (e.g. 60foo.ldif).	The files
listed in ConfigFile must be LDIF files with one or more whole entries to be
added to the initial dse.ldif.	These could be additional suffixes/databases to
create, plugin configuration, replication configuration, or anything else.
Right now, if you have an LDIF file that relies on custom schema, you cannot
use the InstallLdifFile directive during setup.  SchemaFile allows you to do
that.
Platforms tested: RHEL5
Flag Day: no
Doc impact: Will need to document the two additional parameters.