freeipa/install/updates/README

The update files are sorted before being processed because there are
cases where order matters (such as getting schema added first, creating
parent entries, etc).

Updates are applied in blocks of ten so that any entries that are dependant
on another can be added successfully without having to rely on the length
of the DN to get the sorting correct.

The file names should use the format #-<description>.update where # conforms
to this:

10 - 19: Configuration
20 - 29: 389-ds configuration, new indices
30 - 39: Structual elements of the DIT
40 - 49: Pre-loaded data
50 - 59: Cleanup existing data
60 - 69: AD Trust
70 - 79: Reserved
80 - 89: Reserved

These numbers aren't absolute, there may be reasons to put an update
into one place or another, but by adhereing to the scheme it will be
easier to find existing updates and know where to put new ones.
Name update files so they can be easily sorted. We want to process some updates in a particular order (schema, structural). Using an init-inspired ordering mechanism. 2009-03-23 14:20:43 -05:00			`The update files are sorted before being processed because there are`
			`cases where order matters (such as getting schema added first, creating`
			`parent entries, etc).`

Apply LDAP update files in blocks of 10, as originally designed. In order to have control over the order that updates are applied a numbering system was created for the update files. These values were not actually used. The updates were sorted by DN length and in most cases this was adequate for proper function. The exception was with roles where in some cases a role was added as a member of a permission before the role itself was added so the memberOf value was never created. Now updates are computed and applied in blocks of 10. https://fedorahosted.org/freeipa/ticket/3377 2013-04-10 11:05:29 -05:00			`Updates are applied in blocks of ten so that any entries that are dependant`
			`on another can be added successfully without having to rely on the length`
			`of the DN to get the sorting correct.`

			`The file names should use the format #-<description>.update where # conforms`
			`to this:`

Remove schema modifications from update files As schema is now handled by the schema updater, these entries are superfluous. https://fedorahosted.org/freeipa/ticket/3454 2013-04-26 08:32:10 -05:00			`10 - 19: Configuration`
Apply LDAP update files in blocks of 10, as originally designed. In order to have control over the order that updates are applied a numbering system was created for the update files. These values were not actually used. The updates were sorted by DN length and in most cases this was adequate for proper function. The exception was with roles where in some cases a role was added as a member of a permission before the role itself was added so the memberOf value was never created. Now updates are computed and applied in blocks of 10. https://fedorahosted.org/freeipa/ticket/3377 2013-04-10 11:05:29 -05:00			`20 - 29: 389-ds configuration, new indices`
			`30 - 39: Structual elements of the DIT`
			`40 - 49: Pre-loaded data`
			`50 - 59: Cleanup existing data`
			`60 - 69: AD Trust`
			`70 - 79: Reserved`
			`80 - 89: Reserved`

			`These numbers aren't absolute, there may be reasons to put an update`
			`into one place or another, but by adhereing to the scheme it will be`
			`easier to find existing updates and know where to put new ones.`