2008-03-17 17:04:49 -05:00
. \" A man page for ipa-replica-install
2012-05-16 17:11:11 -05:00
. \" Copyright (C) 2008-2012 Red Hat, Inc.
2010-09-10 16:51:08 -05:00
. \"
2010-12-09 06:59:11 -06:00
. \" This program is free software; you can redistribute it and/or modify
. \" it under the terms of the GNU General Public License as published by
. \" the Free Software Foundation, either version 3 of the License, or
. \" (at your option) any later version.
2010-09-10 16:51:08 -05:00
. \"
2008-03-17 17:04:49 -05:00
. \" This program is distributed in the hope that it will be useful, but
. \" WITHOUT ANY WARRANTY; without even the implied warranty of
. \" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
. \" General Public License for more details.
2010-09-10 16:51:08 -05:00
. \"
2010-12-09 06:59:11 -06:00
. \" You should have received a copy of the GNU General Public License
. \" along with this program. If not, see <http://www.gnu.org/licenses/>.
2010-09-10 16:51:08 -05:00
. \"
2008-03-17 17:04:49 -05:00
. \" Author: Rob Crittenden <rcritten@redhat.com>
2010-09-10 16:51:08 -05:00
. \"
2012-05-16 17:11:11 -05:00
.TH "ipa-replica-install" "1" "May 16 2012" "FreeIPA" "FreeIPA Manual Pages"
2008-03-17 17:04:49 -05:00
.SH "NAME"
ipa\- replica\- install \- Create an IPA replica
.SH "SYNOPSIS"
ipa\- replica\- install [\fI OPTION\fR ]... replica_file
.SH "DESCRIPTION"
Configures a new IPA server that is a replica of the server that generated it. Once it has been created it is an exact copy of the original IPA server and is an equal master. Changes made to any master are automatically replicated to other masters.
The replica_file is created using the ipa\- replica\- prepare utility.
2012-05-16 17:11:11 -05:00
If the installation fails you may need to run ipa\- server\- install \- \- uninstall before running ipa\- replica\- install again.
The installation will fail if the host you are installing the replica on exists as a host in IPA or an existing replication agreement exists (for example, from a previously failed installation).
2012-08-29 10:32:03 -05:00
A replica should only be installed on the same or higher version of IPA on the remote system.
2008-03-17 17:04:49 -05:00
.SH "OPTIONS"
2011-09-05 04:04:17 -05:00
.SS "BASIC OPTIONS"
2010-09-10 16:51:08 -05:00
.TP
2011-09-05 04:04:17 -05:00
\fB \- \- setup\- ca\fR
Install and configure a CA on this replica. If a CA is not configured then
certificate operations will be forwarded to a master with a CA installed.
2010-09-10 16:51:08 -05:00
.TP
2012-01-04 13:04:21 -06:00
\fB \- \- ip\- address\fR =\fI IP_ADDRESS\fR
2012-05-16 17:11:11 -05:00
The IP address of this server. If this address does not match the address the host resolves to and \- \- setup\- dns is not selected the installation will fail. If the server hostname is not resolvable, a record for the hostname and IP_ADDRESS is added to /etc/hosts.
2014-11-24 07:49:05 -06:00
This this option can be used multiple times to specify more IP addresses of the server (e.g. multihomed and/or dualstacked server).
2012-01-04 13:04:21 -06:00
.TP
2011-06-17 15:47:39 -05:00
\fB \- p\fR \fI DM_PASSWORD\fR , \fB \- \- password\fR =\fI DM_PASSWORD\fR
2008-06-04 14:37:12 -05:00
Directory Manager (existing master) password
2009-06-26 12:37:49 -05:00
.TP
2011-05-22 12:17:07 -05:00
\fB \- w\fR \fI ADMIN_PASSWORD\fR , \fB \- \- admin\- password\fR =\fI ADMIN_PASSWORD\fR
Admin user Kerberos password used for connection check
.TP
2013-03-27 07:48:01 -05:00
\fB \- \- mkhomedir\fR
Create home directories for users on their first login
.TP
2011-09-05 04:04:17 -05:00
\fB \- N\fR , \fB \- \- no\- ntp\fR
Do not configure NTP
.TP
\fB \- \- no\- ui\- redirect\fR
Do not automatically redirect to the Web UI.
.TP
2011-12-07 02:49:09 -06:00
\fB \- \- ssh\- trust\- dns\fR
Configure OpenSSH client to trust DNS SSHFP records.
.TP
2012-09-12 08:19:26 -05:00
\fB \- \- no\- ssh\fR
Do not configure OpenSSH client.
.TP
2011-12-07 02:49:09 -06:00
\fB \- \- no\- sshd\fR
Do not configure OpenSSH server.
.TP
2011-09-05 04:04:17 -05:00
\fB \- \- skip\- conncheck\fR
Skip connection check to remote master
.TP
\fB \- d\fR , \fB \- \- debug
Enable debug logging when more verbose output is needed
.TP
\fB \- U\fR , \fB \- \- unattended\fR
An unattended installation that will never prompt for user input
.SS "CERTIFICATE SYSTEM OPTIONS"
.TP
\fB \- \- no\- pkinit\fR
Disables pkinit setup steps
Fix schema replication from old masters
The new merged database will replicate with both the IPA and CA trees, so all
DS instances (IPA and CA on the existing master, and the merged one on the
replica) need to have the same schema.
Dogtag does all its schema modifications online. Those are replicated normally.
The basic IPA schema, however, is delivered in ldif files, which are not
replicated. The files are not present on old CA DS instances. Any schema
update that references objects in these files will fail.
The whole 99user.ldif (i.e. changes introduced dynamically over LDAP) is
replicated as a blob. If we updated the old master's CA schema dynamically
during replica install, it would conflict with updates done during the
installation: the one with the lower CSN would get lost.
Dogtag's spawn script recently grew a new flag, 'pki_clone_replicate_schema'.
Turning it off tells Dogtag to create its schema in the clone, where the IPA
modifications are taking place, so that it is not overwritten by the IPA schema
on replication.
The patch solves the problems by:
- In __spawn_instance, turning off the pki_clone_replicate_schema flag.
- Providing a script to copy the IPA schema files to the CA DS instance.
The script needs to be copied to old masters and run there.
- At replica CA install, checking if the schema is updated, and failing if not.
The --skip-schema-check option is added to ipa-{replica,ca}-install to
override the check.
All pre-3.1 CA servers in a domain will have to have the script run on them to
avoid schema replication errors.
https://fedorahosted.org/freeipa/ticket/3213
2012-10-24 03:37:16 -05:00
.TP
\fB \- \- skip\- schema\- check\fR
Skip check for updated CA DS schema on the remote master
2011-09-05 04:04:17 -05:00
.SS "DNS OPTIONS"
2011-06-17 15:47:39 -05:00
.TP
2009-06-26 12:37:49 -05:00
\fB \- \- setup\- dns\fR
2009-09-01 16:28:52 -05:00
Generate a DNS zone if it does not exist already and configure the DNS server.
This option requires that you either specify at least one DNS forwarder through
the \fB \- \- forwarder\fR option or use the \fB \- \- no\- forwarders\fR option.
2010-09-10 16:51:08 -05:00
.TP
2009-09-01 16:28:52 -05:00
\fB \- \- forwarder\fR =\fI IP_ADDRESS\fR
Add a DNS forwarder to the DNS configuration. You can use this option multiple
times to specify more forwarders, but at least one must be provided, unless
the \fB \- \- no\- forwarders\fR option is specified.
.TP
\fB \- \- no\- forwarders\fR
Do not add any DNS forwarders. Root DNS servers will be used instead.
2010-09-10 16:51:08 -05:00
.TP
2011-07-11 03:14:53 -05:00
\fB \- \- reverse\- zone\fR =\fI REVERSE_ZONE\fR
2014-11-24 07:49:05 -06:00
The reverse DNS zone to use. This option can be used multiple times to specify multiple reverse zones.
2011-07-11 03:14:53 -05:00
.TP
2011-05-04 03:09:44 -05:00
\fB \- \- no\- reverse\fR
2012-01-31 08:16:56 -06:00
Do not create new reverse DNS zone. If a reverse DNS zone already exists for the subnet, it will be used.
2011-05-04 03:09:44 -05:00
.TP
2010-09-10 16:51:08 -05:00
\fB \- \- no\- host\- dns\fR
Do not use DNS for hostname lookup during installation
2011-12-07 02:40:51 -06:00
.TP
\fB \- \- no\- dns\- sshfp\fR
Do not automatically create DNS SSHFP records.
2011-09-05 04:04:17 -05:00
2008-03-17 17:04:49 -05:00
.SH "EXIT STATUS"
0 if the command was successful
1 if an error occurred
2012-05-16 17:11:11 -05:00
3 if the host exists in the IPA server or a replication agreement to the remote master already exists