Please Help Test 389 Directory Server 1.2.7.2
by Rich Megginson
389-ds-base-1.2.7.2 is now in Testing. This release has some key fixes
for bugs in 1.2.7 and 1.2.7.1. Please help us test. The sooner we can
get this release tested, the sooner we can push it to Stable and make it
generally available. There is also a new 389-admin-1.1.13 package.
Installation
yum install 389-ds --enablerepo=updates-testing
# or for EPEL
yum install 389-ds --enablerepo=epel-testing
setup-ds-admin.pl
Upgrade
yum upgrade --enablerepo=updates-testing 389-ds-base 389-admin
# or for EPEL
yum upgrade --enablerepo=epel-testing 389-ds-base 389-admin
setup-ds-admin.pl -u
How to Give Feedback
The best way to provide feedback is via the Fedora Update system. Each
update is broken down by package and platform. For example, if you are
using Fedora 13, and you have successfully installed or upgraded all of
the packages, and the console and etc. works, then go to the links below
for Fedora 13 and provide feedback.
* 389-ds-base-1.2.7.2
** EL-5 - https://admin.fedoraproject.org/updates/389-ds-base-1.2.7.2-1.el5
** Fedora 13 -
https://admin.fedoraproject.org/updates/389-ds-base-1.2.7.2-1.fc13
** Fedora 14 -
https://admin.fedoraproject.org/updates/389-ds-base-1.2.7.2-1.fc14
scroll down to the bottom of the page, and click on the Add a comment >>
link
* select one of the Works for me or Does not work radio buttons, add
text, and click on the Add Comment button
If you are using a build on another platform, just send us an email to
389-users(a)lists.fedoraproject.org
Reporting Bugs
If you find a bug, or would like to see a new feature, you can enter it
here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
More Information
* Release Notes - http://port389.org/wiki/Release_Notes
* Install_Guide - http://port389.org/wiki/Install_Guide
* Download - http://port389.org/wiki/Download
13 years, 4 months
Request for feedback about strategy to migrating from old FDS to latest 389DS
by Hugo Etievant
hello,
I am working on a migration of LDAP server from an old
*Fedora-Directory/1.1.3* (B2008.269.213, OS : Fedora 8) to lastest
*389-Directory/1.2.6.1* (B2010.272.2313, OS : CentOS 5.5).
My actual architecture use Multi Master Replication protocol (2 nodes)
for data and configuration, Windows synchronization (with 1 Active
Directory) and some password policies.
For my data, i have 1 database (userRoot) with one suffix
(dc=myOrg,dc=myTLD).
List of possible strategies :
- choice 1 (server level) : applying patches until geting the last
version (i think it is not a good idea and my obsolete OS cannot be
upgraded for external reasons, i will start from scratch on latest CentOS) ?
- choice 2 (database level) : backuping up previous databases userRoot
and netscapeRoot and restoring them into new installed architecture (but
i think perhaps config database schema has changed between 1.1.3 and
1.2.6.1 server versions) ?
- choice 3 (data level) : exporting data in LDIF file (without
configuration and no assurance into operationals attributes export) and
importing it in new installed architecture after configuring it ?
my favorit LDAP tool (Apache Directory Studio) help me to export data
with operationals attributes, this request :
# baseObject : ou=myOrgUnit,dc=myOrg, dc=myTLD
# filter : (objectClass=*)
# attributes : * accountUnlockTime aci copiedFrom copyingFrom
createTimestamp creatorsName dncomp entrydn entryid hasSubordinates
ldapSchemas ldapSyntaxes modifiersName modifyTimestamp nsAccountLock
nsAIMStatusGraphic nsAIMStatusText nsBackendSuffix nscpEntryDN
nsds5ReplConflict nsICQStatusGraphic nsICQStatusText nsIdleTimeout
nsLookThroughLimit nsRole nsRoleDN nsSchemaCSN nsSizeLimit nsTimeLimit
nsUniqueId nsYIMStatusGraphic nsYIMStatusText numSubordinates parentid
passwordAllowChangeTime passwordExpirationTime passwordExpWarned
passwordGraceUserTime passwordHistory passwordRetryCount
pwdExpirationWarned pwdGraceUserTime pwdHistory pwdpolicysubentry
retryCountResetTime subschemaSubentry
but i am not sure that no op attrs are missed...
What can you advise me?
regards
--
*Hugo Étiévant *
INRP/SCI
**hugo.etievant(a)inrp.fr <mailto:hugo.etievant@inrp.fr>
13 years, 4 months