diff options
| author | Rob Crittenden <rcritten@redhat.com> | 2010-08-27 13:40:37 -0400 |
|---|---|---|
| committer | Rob Crittenden <rcritten@redhat.com> | 2010-08-27 13:40:37 -0400 |
| commit | 678b59b6ff96c4025d758ac7d8552b1185e04c4e (patch) | |
| tree | 1beffcaa3e524dab2dc9bdf1a2aac0f936402001 /install/README.schema | |
| parent | 4b6b710ba6ce75ffcb9ced43acee0d55adb6163c (diff) | |
| download | freeipa-678b59b6ff96c4025d758ac7d8552b1185e04c4e.tar.gz freeipa-678b59b6ff96c4025d758ac7d8552b1185e04c4e.tar.xz freeipa-678b59b6ff96c4025d758ac7d8552b1185e04c4e.zip | |
Add some basic rules for adding new schema
Diffstat (limited to 'install/README.schema')
| -rw-r--r-- | install/README.schema | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/install/README.schema b/install/README.schema new file mode 100644 index 000000000..686e8379e --- /dev/null +++ b/install/README.schema @@ -0,0 +1,15 @@ +Ground rules on adding new schema + +Brand new schema, particularly when written specifically for IPA, should be +added in share/*.ldif. Any new files need to be explicitly loaded in +ipaserver/install/dsinstance.py. These simply get copied directly into +the new instance schema directory. + +Existing schema (e.g. in an LDAP draft) may either be added as a separate +ldif in share or as an update in the updates directory. The advantage of +adding the schema as an update is if 389-ds ever adds the schema then the +installation won't fail due to existing schema failing to load during +bootstrap. + +If the new schema requires a new container then this should be added +to install/bootstrap-template.ldif. |