ABI stability of internal DBs

[Stefan (metze) Metzmacher]

Am 07.07.2010 07:51, schrieb Volker Lendecke:
> 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?

No, only for things which need to be accessed by other applications.

For internal things we just need to support for 2 versions of a protocol
or db format,
how we do that doesn't matter...

metze


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20100707/28900379/attachment.pgp>