freeipa/install
Martin Kosek ef7b8ab764 Use default reverse zone consistently
When a new reverse zone is to be generated based on an IP address without
a network prefix length, we need to use some default value. While netaddr
library default ones (32b for IPv4 and 128b for IPv6) are not very sensible
we should use the defaults already applied in installers. That is 24b for
IPv6 and 64 for IPv6.

Test case has been added to cover the new default.

https://fedorahosted.org/freeipa/ticket/2461
2012-09-19 17:32:02 +02:00
..
certmonger Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
conf Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
html Fixed inconsistent image names. 2011-10-27 14:05:12 +00:00
migration Use DN objects instead of strings 2012-08-12 16:23:24 -04:00
po Update the pot file (translation source) 2012-09-12 22:04:16 -04:00
restart_scripts Use Dogtag 10 only when it is available 2012-09-17 18:43:59 -04:00
share Run the CLEANALLRUV task when deleting a replication agreement. 2012-09-17 17:48:25 +02:00
tools Use default reverse zone consistently 2012-09-19 17:32:02 +02:00
ui Fix integer validation when boundary value is empty string 2012-09-19 11:09:09 +02:00
updates Run the CLEANALLRUV task when deleting a replication agreement. 2012-09-17 17:48:25 +02:00
configure.ac Use certmonger to renew CA subsystem certificates 2012-07-30 13:39:08 +02:00
Makefile.am Use certmonger to renew CA subsystem certificates 2012-07-30 13:39:08 +02:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

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.