389-ds-base

#51045 Schema: Future design and improvements
Closed: wontfix by spichugi. Opened by firstyear.

Closed: wontfix
Reopen Issue

Issue Description

Recently we have identified a number of barriers and issues with the design of our schema system. While the schema system has been functional for sometime, some modern changes have caused challenges at scale and with future proofing and improvement efforts. The schema system has a lot of history in 389, and this shows in how various improvements have grown organically into it.

Some examples of issues we are encountering:

  • Management of schema upgrades with containers
  • Merging user provided schema with system schema
  • Schema replication and consistency between servers
  • Preventing some schema elements loading from the system schema
  • Probably others I have forgotten.

As a result, @tbordaz and I think we should discuss and consider how we might improve the schema system to handle future cases for 389.

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue priority set to: critical
- Issue set to the milestone: 1.4.5
- Issue tagged with: Schema

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4098

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None

Schema

None
None
Low
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.