On Mon, Jan 21, 2013 at 03:41:16PM -0600, Taylor, Jonn wrote:
> On 01/20/2013 08:18 PM, Martin Schwenke wrote:
>> On Mon, 14 Jan 2013 17:27:52 -0600, "Christopher R. Hertel"
>> <email@example.com> wrote:
>>> On 01/14/2013 05:06 PM, Amitay Isaacs wrote:
>>>> CTDB branch 1.13 (CTDB version 1.44) is now completely defunct and should
>>>> not be used. I would prefer to do regular releases of CTDB 2.x (time
>>>> permitting). Currently 2.x releases are done from master which makes it
>>>> easier to manage.
>>> With my vendor hat on (and you know what color that is), I need to be able
>>> to identify a release of CTDB to ship with products. I can back-port fixes,
>>> as needed, but I need a foundation from which to work.
>> There isn't much (any?) feature development being done. Most of
>> the changes we're making are bug fixes, performance improvements or
>> code cleanups to improve maintainability.
> What are the plans for CTDB to be used on a AD DC cluster on the new
> 4.0? I currently am running a 2 node cluster (samba 3.6+CTDB, DRDB
> active/active on CentOS5) that I would like to upgrade to 4.0 with
> AD but the notes say that this is not recommended.
This is not a ctdb issue. ldb needs to be made ctdb-aware,
so that it can run its databases in a cluster. I am not
aware of anybody actively working on it, but to get a fully
HA AD DC as you have it in mind it is necessary.
With best regards,
-- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:firstname.lastname@example.org
It's very unlikely to happen.
Someone should have multiple AD DC's with replication,
instead of using a ctdb cluster.
Not sure I am explaining what needs to happen.
I want to have 2 AD DC's but with a common CTDB clustered file system for sharing files, not the DC part.
(In reply to comment #2)
> Not sure I am explaining what needs to happen.
> I want to have 2 AD DC's but with a common CTDB clustered file system for
> sharing files, not the DC part.
Then split the file server from the AD server, you could use LXC.
Closing as WONTFIX. For the AD DC there is the well-defined replication protocol. And as we recommend anyway to run DCs on machines or VMs separate from the file services, right now there is no direct need to make ldb cluster-aware.