389-devel February 2019

389-devel@lists.fedoraproject.org

9 participants
28 discussions

Start a nNew thread

please review: PR 50241 - Improve task logging
by Mark Reynolds 24 Feb '19

24 Feb '19

https://pagure.io/389-ds-base/pull-request/50241

1 0

please review: PR 50239 - failed modrdn can corrupt entry cache
by Mark Reynolds 22 Feb '19

22 Feb '19

https://pagure.io/389-ds-base/pull-request/50239

1 0

please review: Ticket 50236 - memberOf should be more robust
by Mark Reynolds 21 Feb '19

21 Feb '19

https://pagure.io/389-ds-base/pull-request/50237

1 0

Pleas review
by Anuj Borah 20 Feb '19

20 Feb '19

Hi all, Please review bellow PRs: https://pagure.io/389-ds-base/pull-request/50180 https://pagure.io/389-ds-base/pull-request/50168 Its pending from long time. Regards Anuj Borah

1 0

Please review 50224 deprecate _s functions
by William Brown 14 Feb '19

14 Feb '19

https://pagure.io/389-ds-base/pull-request/50226# -- Sincerely, William

1 0

creating a universal class to replace "Entry"
by Anuj Borah 12 Feb '19

12 Feb '19

Hi, As 'Entry' is not allowed to use now , In replace of Entry we are suggested to use UserAccounts and UserAccount which is very limited to some object classes . (['account','posixaccount','inetOrgPerson','organizationalPerson']) What if we need to create some entry with other object classes rather than those fixed in UserAccounts and UserAccount like bellow : --------------------------------------------- Role Entry: topo.standalone.add_s( Entry(('cn=new managed role,dc=example,dc=com', { 'objectclass': ['top', 'ldapsubentry', 'nsroledefinition', 'nssimpleroledefinition', 'nsmanagedroledefinition'], 'description': 'This is the new managed role configuration', 'cn': 'new managed role', }))) -------------------------------------------------- Sub suffix: topo.standalone.add_s( Entry(('dc=subexample, dc=example, dc=com', { 'objectclass': ['top', 'dcobject'], 'dc': 'subexample', }))) ---------------------------------------------------------- Other Entry: topo.standalone.add_s( Entry(('cn=CCOS, ou=People, dc=example, dc=com', { 'objectclass': ['top', 'LDAPSubentry', 'cosSuperDefinition', 'cosClassicDefinition'], 'cosTemplateDn': ['ou=MailSchemeClasses, ou=COS, dc=example, dc=com'], 'cosSpecifier': 'emailclass', 'cosAttribute': ['mailquota', 'multiLineDescription override'], 'cn': 'ccos' }))) -------------------------------------- For above kind of entries there is no way we can create them without using "Entry" or using UserAccounts and UserAccount. To deal with this problem i have created one universal class that can be used to create any kind of entry which may be a user , role, or sub suffix. Take a look bellow . class UniversalEntry(DSLdapObject): def __init__(self, instance, objectclasses, rdn, dn): super(UniversalEntry, self).__init__(instance, dn) self._rdn_attribute = rdn self._create_objectclasses = objectclasses and this one can be used for above examples: ----------------------------------------- properties = { 'description': 'This is the new managed role configuration', 'cn': 'new managed role', } user = UniversalEntry(topo.standalone, ['top', 'ldapsubentry', 'nsroledefinition', 'nssimpleroledefinition','nsmanagedroledefinition'], 'cn','cn=new managed role,dc=example,dc=com') user.create(properties=properties) --------------------------------------------------- properties = {'dc': 'subexample'} user = UniversalEntry(topo.standalone, ['top', 'dcobject'], 'dc', 'dc=subexample, dc=example, dc=com') user.create(properties=properties) --------------------------------------------- properties = { 'cosTemplateDn': ['ou=MailSchemeClasses, ou=COS, dc=example, dc=com'], 'cosSpecifier': 'emailclass', 'cosAttribute': ['mailquota', 'multiLineDescription override'], 'cn': 'ccos' } user = UniversalEntry(topo.standalone, ['top', 'LDAPSubentry', 'cosSuperDefinition', 'cosClassicDefinition'], 'cn', 'cn=CCOS, ou=People, dc=example, dc=com') ------------------------------------------------ This way we will be able to create any kind of entry whether it may be user/role/sub suffix or anything . Please let me know what other changes i have to do to make more sophisticated. Regards Anuj Borah

3 4

Please review: 50208: detect dse.ldif in lib389
by William Brown 10 Feb '19

10 Feb '19

https://pagure.io/389-ds-base/pull-request/50213 https://pagure.io/389-ds-base/issue/50208 — Sincerely, William Brown Software Engineer, 389 Directory Server SUSE Labs

1 0

389 DS nightly 2019-02-10 - 90% PASS
by vashirov＠redhat.com 09 Feb '19

09 Feb '19

https://fedorapeople.org/groups/389ds/ci/nightly/2019/02/10/report-389-ds-b…

1 0

Please review: better diagnostics on autosize failure
by William Brown 07 Feb '19

07 Feb '19

https://pagure.io/389-ds-base/issue/49575 https://pagure.io/389-ds-base/pull-request/50210 — Sincerely, William Brown Software Engineer, 389 Directory Server SUSE Labs

1 0

Backport lib389 modify to 1.4.0
by William Brown 07 Feb '19

07 Feb '19

https://pagure.io/389-ds-base/pull-request/50209 -- Sincerely, William

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel February 2019