TL;DR: Are 389-admin-console / 389-ds-console just the java GUI admin tools, in which case I don't need them on the server?
Hopefully I can simply spin up a new 389DS on a machine that is upgraded (from scratch) to 7, set up MMR and let it consume everything off one of the existing replicas, then take one of the old ones out of service, rinse and repeat until they're all done.
Having been many years since settings these up, I am for all intents and purposes having to relearn everything.
Various guides to installing 389DS on CentOS 7 indicate some packages aren't available that I would need. Some of these have become available via either 'epel' or 'updates', but I'm still missing some.
Have:
389-admin.x86_64 1.1.38-1.el7 epel
389-adminutil.x86_64 1.1.21-2.el7 epel
389-adminutil-devel.x86_64 1.1.21-2.el7 epel
389-console.noarch 1.1.9-1.el7 epel
389-ds-base.x86_64 1.3.4.0-26.el7_2 updates
389-ds-base-devel.x86_64 1.3.4.0-26.el7_2 updates
389-ds-base-libs.x86_64 1.3.4.0-26.el7_2 updates
idm-console-framework.noarch 1.1.14-1.el7 epel
Don't have:
389-admin-console
389-ds-console
What exactly do these missing packages provide, and will I be fine without them? From the descriptions on rpmfind.net it sounds like these are just the java admin consoles, which I don't really need since I normally do everything from consoles installed on my workstation instead - though it would be nice to have them so we at least have the option of someone running them with an X tunnel if they don't have them installed locally, but that's not mission critical.
-- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
