[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.05-62-gd073771

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cluster Project".


The branch, master has been updated
       via  d073771dd925558714cbaf1ab3624f9a42d0a12c (commit)
      from  86eb6e11bea697f6a55009f74e010db09d6a1540 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d073771dd925558714cbaf1ab3624f9a42d0a12c
Author: Christine Caulfield <ccaulfie redhat com>
Date:   Thu Jul 10 15:18:12 2008 +0100

    [CONFIG] Add a man page for confdb2ldif
    and make the program do as the man page says.
    Signed-off-by: Christine Caulfield <ccaulfie redhat com>


Summary of changes:
 config/tools/ldap/confdb2ldif.c |    4 +-
 config/tools/man/Makefile       |    2 +-
 config/tools/man/confdb2ldif.8  |   64 +++++++++++++++++++++++++++++++++++++++
 3 files changed, 67 insertions(+), 3 deletions(-)
 create mode 100644 config/tools/man/confdb2ldif.8

diff --git a/config/tools/ldap/confdb2ldif.c b/config/tools/ldap/confdb2ldif.c
index d173d00..ab80dae 100644
--- a/config/tools/ldap/confdb2ldif.c
+++ b/config/tools/ldap/confdb2ldif.c
@@ -167,7 +167,7 @@ int main(int argc, char *argv[])
 		fprintf(stderr, "     %s dc=mycompany,dc=com\n", argv[0]);
 		fprintf(stderr, "     %s dc=mycompany,dc=com rhcluster\n", argv[0]);
 		fprintf(stderr, "\n");
-		fprintf(stderr, "objdb root defaults to 'cn=cluster'\n");
+		fprintf(stderr, "objdb root defaults to 'cluster'\n");
 		fprintf(stderr, "\n");
 		return 0;
@@ -190,7 +190,7 @@ int main(int argc, char *argv[])
 		exit (1);
-	result = confdb_object_find(handle, OBJECT_PARENT_HANDLE, "cluster", strlen("cluster"), &cluster_handle);
+	result = confdb_object_find(handle, OBJECT_PARENT_HANDLE, clusterroot, strlen(clusterroot), &cluster_handle);
 	if (result != SA_AIS_OK) {
 		printf ("Could not object_find \"cluster\": %d\n", result);
 		exit (1);
diff --git a/config/tools/man/Makefile b/config/tools/man/Makefile
index 149e93a..8fe29bf 100644
--- a/config/tools/man/Makefile
+++ b/config/tools/man/Makefile
@@ -1,4 +1,4 @@
-TARGET= ccs_test.8
+TARGET= ccs_test.8 confdb2ldif.8
 include ../../../make/defines.mk
 include $(OBJDIR)/make/man.mk
diff --git a/config/tools/man/confdb2ldif.8 b/config/tools/man/confdb2ldif.8
new file mode 100644
index 0000000..2964eec
--- /dev/null
+++ b/config/tools/man/confdb2ldif.8
@@ -0,0 +1,64 @@
+.TH confdb2ldif 8
+confdb2ldif - Create an LDIF file from a cluster configuration
+.B confdb2ldap <basedn> [<config object base>]
+\fBconfdb2ldif\fP reads the cluster configuration from the openais object database
+and generates an LDIF file suitable for importing into an LDAP database. The LDIF
+file is written to standard output.
+This is the base DN of the LDAP server into which the configuration will be imported.
+confdb2ldif will create a "cn=cluster" object below this to contain the cluster configuration.
+The base DN is usually derived from the host's domain name. So if the host is ldapsrv.mycorp.com
+then the base DN could be dc=mycorp,dc=com.
+\fB[<config object base>]\fP
+Configuration object in the objdb to start from. This defaults to "cluster" and 
+there should rarely be any need to change it.
+\fBconfdb2ldif\fP uses the openais libconfdb to read the configuration. The default way to
+do this is run against a running aisexec to read the live configuration. 
+It is possible to generate an LDIF file from a non-running system by using the standalone feature of openais's libconfdb.
+eg to read the configuration from /etc/cluster/cluster.conf, use the following command:
+OPENAIS_DEFAULT_CONFIG_IFACE=xmlconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com
+or to do it from CCS
+OPENAIS_DEFAULT_CONFIG_IFACE=ccsconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com
+The LDIF file is written to stdout and so can be saved or piped straight into ldapmodify if required.
+It's important that the 99cluster.ldif schema file has been loaded into the LDAP server
+before adding the contents of this generated LDIF file.
+confdb2ldif dc=mycorp,dc=com | ldapmodify -x -a -D"cn=Directory Manager" -c -v -W
+\fBconfdb2ldif\fP parses the cluster configuration without checking it against the loaded
+schema. So if there are attributes in the config file that are not known to the schema, 
+parts of the load will fail. It is important to check the results of feeding the
+output into ldapmodify. In particular aisexec logging operations will not convert
+into LDIF because they rely on duplicate keys.
+libconfdb(3), openais(8), cluster.conf(5)

Cluster Project

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]