[389-users] Re: Registering remote 389-DS instances in Console
On 08/24/2017 03:28 PM, Kirk MacDonald wrote: > > I would suggest adding something above the screenshot which shows the > properly configured 2 server 1 admin console scenario. Perhaps simply > a walkthrough of register-ds-admin.pl when invoked interactively, for > the relatively simple use case I was trying to execute. > > > What tripped me up was the point, highlighted in red. I was expecting > to be able to enter an LDAP URI: > ldap://host.domain:389/o=NetscapeRootsince I was looking to register a > remote server. > > > > The reality is that the script is basically asking what Configuration > Directory Server are you going to Register INTO, before what remote > server do you want to register. Since the script probably can’t tell > you that the local instance has/has not already been registered in the > local Configuration Directory Server (which is what I thought this > script would ONLY accomplish, initially), some more details in the > documentation at the URL you mention would have helped me. > Thanks Kirk, while it's too late for you, I will get this doc updated. Best regards, Mark > > > > > > # register-ds-admin.pl > > Beginning registration of the Directory Server > > > > == > > The Directory Server locates its configuration file (dse.ldif) at > /etc/dirsrv/slapd-ID, by default. If you have Directory Server(s) > which configuration file is put at the other location, you need to > input it to register the server. > > > > If you have such Directory Server, type the full path that stores the > configuration file. > > > > If you don't, type return. > > *[configuration directory path or return]:* > > > > == > > Do you want to use this server as Configuration Directory Server? > > > > Directory server identifier []: > > > > == > > Registering new Config DS: > > > > == > > Input the Directory Manager password on the server ldap1: > > > > == > > Please input the password for the Administrator User > uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot: > > > > == > > Beginning Admin Server reconfiguration . . . > > Creating Admin Server files and directories . . . > > Updating adm.conf . . . > > Updating admpw . . . > > Registering admin server with the configuration directory server . . . > > Updating adm.conf with information from configuration directory server > . . . > > Updating the configuration for the httpd engine . . . > > Restarting admin server . . . > > The admin server was successfully started. > > Admin server was successfully reconfigured and started. > > > > == > > Do you want to register a remote server with the local configuration > server (y/n)? y > > > > > > - Kirk > > > > *From:*Mark Reynolds [mailto:marey...@redhat.com] > *Sent:* Thursday, August 24, 2017 4:04 PM > *To:* Kirk MacDonald <kirk.macdon...@corp.eastlink.ca>; General > discussion list for the 389 Directory server project. > <389-users@lists.fedoraproject.org> > *Subject:* Re: [389-users] Re: Registering remote 389-DS instances in > Console > > > > > > On 08/24/2017 02:31 PM, Kirk MacDonald wrote: > > OK scratch that – it of course does work interactively. I was just > being thrown off by the fact one has to (re)config/specify the > local Admin instance each time. Later on in the interactive it > asks for the remote hosts. Silly me. > > Hi Kirk, > > Glad you got it working. > > Regarding: > http://www.port389.org/docs/389ds/design/console-remote-reg-design.html > , what can improved here? Better docs on the "interactive" mode, or > INF file mode? > > Thanks, > Mark > > > > -Kirk > > > > *From:* Kirk MacDonald [mailto:kirk.macdon...@corp.eastlink.ca] > *Sent:* Thursday, August 24, 2017 1:36 PM > *To:* Mark Reynolds <marey...@redhat.com> > <mailto:marey...@redhat.com>; General discussion list for the 389 > Directory server project. <389-users@lists.fedo
[389-users] Re: Registering remote 389-DS instances in Console
I would suggest adding something above the screenshot which shows the properly configured 2 server 1 admin console scenario. Perhaps simply a walkthrough of register-ds-admin.pl when invoked interactively, for the relatively simple use case I was trying to execute. What tripped me up was the point, highlighted in red. I was expecting to be able to enter an LDAP URI: ldap://host.domain:389/o=NetscapeRoot since I was looking to register a remote server. The reality is that the script is basically asking what Configuration Directory Server are you going to Register INTO, before what remote server do you want to register. Since the script probably can’t tell you that the local instance has/has not already been registered in the local Configuration Directory Server (which is what I thought this script would ONLY accomplish, initially), some more details in the documentation at the URL you mention would have helped me. # register-ds-admin.pl Beginning registration of the Directory Server == The Directory Server locates its configuration file (dse.ldif) at /etc/dirsrv/slapd-ID, by default. If you have Directory Server(s) which configuration file is put at the other location, you need to input it to register the server. If you have such Directory Server, type the full path that stores the configuration file. If you don't, type return. [configuration directory path or return]: == Do you want to use this server as Configuration Directory Server? Directory server identifier []: == Registering new Config DS: == Input the Directory Manager password on the server ldap1: == Please input the password for the Administrator User uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot: == Beginning Admin Server reconfiguration . . . Creating Admin Server files and directories . . . Updating adm.conf . . . Updating admpw . . . Registering admin server with the configuration directory server . . . Updating adm.conf with information from configuration directory server . . . Updating the configuration for the httpd engine . . . Restarting admin server . . . The admin server was successfully started. Admin server was successfully reconfigured and started. == Do you want to register a remote server with the local configuration server (y/n)? y - Kirk From: Mark Reynolds [mailto:marey...@redhat.com] Sent: Thursday, August 24, 2017 4:04 PM To: Kirk MacDonald <kirk.macdon...@corp.eastlink.ca>; General discussion list for the 389 Directory server project. <389-users@lists.fedoraproject.org> Subject: Re: [389-users] Re: Registering remote 389-DS instances in Console On 08/24/2017 02:31 PM, Kirk MacDonald wrote: OK scratch that – it of course does work interactively. I was just being thrown off by the fact one has to (re)config/specify the local Admin instance each time. Later on in the interactive it asks for the remote hosts. Silly me. Hi Kirk, Glad you got it working. Regarding: http://www.port389.org/docs/389ds/design/console-remote-reg-design.html , what can improved here? Better docs on the "interactive" mode, or INF file mode? Thanks, Mark -Kirk From: Kirk MacDonald [mailto:kirk.macdon...@corp.eastlink.ca] Sent: Thursday, August 24, 2017 1:36 PM To: Mark Reynolds <marey...@redhat.com><mailto:marey...@redhat.com>; General discussion list for the 389 Directory server project. <389-users@lists.fedoraproject.org><mailto:389-users@lists.fedoraproject.org> Subject: [389-users] Re: Registering remote 389-DS instances in Console Thanks for the reply. I am struggling with the script because it only seems to see local instances, when running the script interactively. - Kirk From: Mark Reynolds Sent: Thursday, August 24, 2017 1:30 PM To: General discussion list for the 389 Directory server project.; Kirk MacDonald Subject: Re: [389-users] Registering remote 389-DS instances in Console On 08/24/2017 11:30 AM, Kirk MacDonald wrote: I have built 3 new 389-DS instances (389-Directory/1.3.5.10 B2017.145.2037) on different services. Each has local Admin console. They are all in the same Administrative Domain. Perfect... Is the method to register the remote instances in each local Admin console what is described here: http://www.port389.org/docs/389ds/design/console-remote-reg-design.html ? Are you planning on using one central Admin/Config server? If so, you just need to registers
[389-users] Re: Registering remote 389-DS instances in Console
On 08/24/2017 02:31 PM, Kirk MacDonald wrote: > > OK scratch that – it of course does work interactively. I was just > being thrown off by the fact one has to (re)config/specify the local > Admin instance each time. Later on in the interactive it asks for the > remote hosts. Silly me. > Hi Kirk, Glad you got it working. Regarding: http://www.port389.org/docs/389ds/design/console-remote-reg-design.html , what can improved here? Better docs on the "interactive" mode, or INF file mode? Thanks, Mark > > > > -Kirk > > > > *From:* Kirk MacDonald [mailto:kirk.macdon...@corp.eastlink.ca] > *Sent:* Thursday, August 24, 2017 1:36 PM > *To:* Mark Reynolds <marey...@redhat.com>; General discussion list for > the 389 Directory server project. <389-users@lists.fedoraproject.org> > *Subject:* [389-users] Re: Registering remote 389-DS instances in Console > > > > Thanks for the reply. I am struggling with the script because it only > seems to see local instances, when running the script interactively. > > > > - Kirk > > *From: *Mark Reynolds > > *Sent: *Thursday, August 24, 2017 1:30 PM > > *To: *General discussion list for the 389 Directory server project.; > Kirk MacDonald > > *Subject: *Re: [389-users] Registering remote 389-DS instances in Console > > > > > > On 08/24/2017 11:30 AM, Kirk MacDonald wrote: > > I have built 3 new 389-DS instances (389-Directory/1.3.5.10 > B2017.145.2037) on different services. Each has local Admin > console. They are all in the same Administrative Domain. > > Perfect... > > > > Is the method to register the remote instances in each local Admin > console what is described here: > http://www.port389.org/docs/389ds/design/console-remote-reg-design.html > ? > > Are you planning on using one central Admin/Config server? If so, you > just need to registers the other 3 remote servers with your local > one. Done. > > If want to goto any admin server and see all the other servers then > you have to do the same thing on each host: Goto Server A, and > register B, C, D, goto Server B - register A, C, D, etc, etc. > > > > Or, is there a more “simplistic” approach that can be done via > each Admin console UI? > > Using the script is the easiest. There is no way to do it via the > console ui. > > Regards, > Mark > > > > Thanks, > > Kirk MacDonald > > Eastlink > > > > ___ > > 389-users mailing list -- 389-users@lists.fedoraproject.org > <mailto:389-users@lists.fedoraproject.org> > > To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org > <mailto:389-users-le...@lists.fedoraproject.org> > > > ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
[389-users] Re: Registering remote 389-DS instances in Console
OK scratch that – it of course does work interactively. I was just being thrown off by the fact one has to (re)config/specify the local Admin instance each time. Later on in the interactive it asks for the remote hosts. Silly me. -Kirk From: Kirk MacDonald [mailto:kirk.macdon...@corp.eastlink.ca] Sent: Thursday, August 24, 2017 1:36 PM To: Mark Reynolds <marey...@redhat.com>; General discussion list for the 389 Directory server project. <389-users@lists.fedoraproject.org> Subject: [389-users] Re: Registering remote 389-DS instances in Console Thanks for the reply. I am struggling with the script because it only seems to see local instances, when running the script interactively. - Kirk From: Mark Reynolds Sent: Thursday, August 24, 2017 1:30 PM To: General discussion list for the 389 Directory server project.; Kirk MacDonald Subject: Re: [389-users] Registering remote 389-DS instances in Console On 08/24/2017 11:30 AM, Kirk MacDonald wrote: I have built 3 new 389-DS instances (389-Directory/1.3.5.10 B2017.145.2037) on different services. Each has local Admin console. They are all in the same Administrative Domain. Perfect... Is the method to register the remote instances in each local Admin console what is described here: http://www.port389.org/docs/389ds/design/console-remote-reg-design.html ? Are you planning on using one central Admin/Config server? If so, you just need to registers the other 3 remote servers with your local one. Done. If want to goto any admin server and see all the other servers then you have to do the same thing on each host: Goto Server A, and register B, C, D, goto Server B - register A, C, D, etc, etc. Or, is there a more “simplistic” approach that can be done via each Admin console UI? Using the script is the easiest. There is no way to do it via the console ui. Regards, Mark Thanks, Kirk MacDonald Eastlink ___ 389-users mailing list -- 389-users@lists.fedoraproject.org<mailto:389-users@lists.fedoraproject.org> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org<mailto:389-users-le...@lists.fedoraproject.org> ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
[389-users] Re: Registering remote 389-DS instances in Console
Thanks for the reply. I am struggling with the script because it only seems to see local instances, when running the script interactively. - Kirk From: Mark Reynolds Sent: Thursday, August 24, 2017 1:30 PM To: General discussion list for the 389 Directory server project.; Kirk MacDonald Subject: Re: [389-users] Registering remote 389-DS instances in Console On 08/24/2017 11:30 AM, Kirk MacDonald wrote: I have built 3 new 389-DS instances (389-Directory/1.3.5.10 B2017.145.2037) on different services. Each has local Admin console. They are all in the same Administrative Domain. Perfect... Is the method to register the remote instances in each local Admin console what is described here: http://www.port389.org/docs/389ds/design/console-remote-reg-design.html ? Are you planning on using one central Admin/Config server? If so, you just need to registers the other 3 remote servers with your local one. Done. If want to goto any admin server and see all the other servers then you have to do the same thing on each host: Goto Server A, and register B, C, D, goto Server B - register A, C, D, etc, etc. Or, is there a more “simplistic” approach that can be done via each Admin console UI? Using the script is the easiest. There is no way to do it via the console ui. Regards, Mark Thanks, Kirk MacDonald Eastlink ___ 389-users mailing list -- 389-users@lists.fedoraproject.org<mailto:389-users@lists.fedoraproject.org> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org<mailto:389-users-le...@lists.fedoraproject.org> ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
[389-users] Re: Registering remote 389-DS instances in Console
On 08/24/2017 11:30 AM, Kirk MacDonald wrote: > > I have built 3 new 389-DS instances (389-Directory/1.3.5.10 > B2017.145.2037) on different services. Each has local Admin console. > They are all in the same Administrative Domain. > Perfect... > > > > Is the method to register the remote instances in each local Admin > console what is described here: > http://www.port389.org/docs/389ds/design/console-remote-reg-design.html ? > Are you planning on using one central Admin/Config server? If so, you just need to registers the other 3 remote servers with your local one. Done. If want to goto any admin server and see all the other servers then you have to do the same thing on each host: Goto Server A, and register B, C, D, goto Server B - register A, C, D, etc, etc. > > > > Or, is there a more “simplistic” approach that can be done via each > Admin console UI? > Using the script is the easiest. There is no way to do it via the console ui. Regards, Mark > > > > Thanks, > > Kirk MacDonald > > Eastlink > > > > ___ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
