ABI stability of internal DBs

Volker Lendecke Volker.Lendecke at SerNet.DE
Tue Jul 6 23:51:59 MDT 2010

On Wed, Jul 07, 2010 at 07:29:15AM +0200, Stefan (metze) Metzmacher wrote:
> So you can add new nodes to a cluster and turn the upgrade on once you've
> upgraded all nodes to the new software.
> We may need a capability struct which contains the supported db formats
> and features
> the whole "system" supports and decide if we can upgrade to the latest
> db format and features.
> In the non clustered case it's simple, the "system" would support the
> latest features.
> In the clustered case it would be the union of all nodes.
> This is a bit similar to AD, where all DCs have to support a specific
> functional level,
> before you can raise it for the whole domain or forest.

Ok, so you are proposing that for all our internal databases
like locking.tdb we create stable APIs like libwbclient,
along with the messaging protocols, which need to be
encapsulated similarly?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20100707/7ad77141/attachment.pgp>

More information about the samba-technical mailing list