confdb2ldif(8)

1confdb2ldif(8)              System Manager's Manual             confdb2ldif(8)
2
3
4

NAME

6       confdb2ldif - Create an LDIF file from a cluster configuration
7
8

SYNOPSIS

10       confdb2ldap <basedn> [<config object base>]
11
12

DESCRIPTION

14       confdb2ldif  reads  the  cluster  configuration from the openais object
15       database and generates an LDIF file suitable for importing into an LDAP
16       database. The LDIF file is written to standard output.
17
18

OPTIONS

20       <basedn>
21              This is the base DN of the LDAP server into which the configura‐
22              tion will be imported.  confdb2ldif will create  a  "cn=cluster"
23              object  below  this  to  contain the cluster configuration.  The
24              base DN is usually derived from the host's domain  name.  So  if
25              the  host  is  ldapsrv.mycorp.com  then  the  base  DN  could be
26              dc=mycorp,dc=com.
27
28       [<config object base>]
29              Configuration object in the objdb to start from.  This  defaults
30              to "cluster" and there should rarely be any need to change it.
31
32

COMMENTS

34       confdb2ldif  uses  the openais libconfdb to read the configuration. The
35       default way to do this is run against a running  aisexec  to  read  the
36       live  configuration.   It  is  possible to generate an LDIF file from a
37       non-running system by using the standalone feature  of  openais's  lib‐
38       confdb.
39       eg  to  read  the configuration from /etc/cluster/cluster.conf, use the
40       following command:
41
42       OPENAIS_DEFAULT_CONFIG_IFACE=xmlconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com
43
44       or to do it from CCS
45
46       OPENAIS_DEFAULT_CONFIG_IFACE=ccsconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com
47
48       The LDIF file is written to  stdout  and  so  can  be  saved  or  piped
49       straight into ldapmodify if required.
50       It's important that the 99cluster.ldif schema file has been loaded into
51       the LDAP server before adding the contents of this generated LDIF file.
52
53

EXAMPLE

55       confdb2ldif dc=mycorp,dc=com | ldapmodify -x -a -D"cn=Directory Manager" -c -v -W
56
57

BUGS

59       confdb2ldif  parses  the  cluster  configuration  without  checking  it
60       against  the  loaded  schema.  So if there are attributes in the config
61       file that are not known to the schema, parts of the load will fail.  It
62       is  important  to check the results of feeding the output into ldapmod‐
63       ify. In particular aisexec logging operations  will  not  convert  into
64       LDIF because they rely on duplicate keys.
65
66
67