From: Patrick Caulfield <pcaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC] Killing ccs for good
Date: Tue, 30 Oct 2007 09:54:23 +0000 [thread overview]
Message-ID: <4726FF4F.6040501@redhat.com> (raw)
In-Reply-To: <1193145463.2719.6.camel@dhcp80-204.msp.redhat.com>
Kevin Anderson wrote:
> On Tue, 2007-10-23 at 09:33 +0200, Fabio Massimo Di Nitto wrote:
>> Hi everybody,
>>
>> a few months ago David tickled me with the idea of killing ccs, so I started
>> poking around for fun here and there and I think that I am at a point where
>> we can start looking at the work it has been done so far.
>>
>> What does killing ccs buy us?
>>
>> - remove of another daemon from the stack with everything that comes with it
>> (less code to handle, less open ports on the network, less stuff to
>> synchronize, etc.)
>> - the option to design a new more useful API.
>> - add your reason here.
>>
>> I created a git branch at git.fugedabout.it sandbox to work on this project:
>>
>> http://git.fugedabout.it/?p=people/fabbione/cluster-noccs.git;a=shortlog;h=noccs
>>
>> You want to remember that this is a test/private branch and it gets rebased once
>> in a while (breaking the classic git pull) and it is on a sandbox == *absolutely
>> no guarantee it will exists in forever*
>>
>> So far we have:
>>
>> - removed completely ccs/ from the tree.
>> - implemented a small libcman API that:
>> (high level)
>> - reads random cluster.conf files.
>> - loads them.
>> - query them.
>> (low level)
>> - handle config conversion from buf to conf and viceversa.
>> - download/upload the config from/to cman aisexec.
>> - implemented the basic bits in cman/aisexec.
>> - converted all services to use the new API (except rgmanager - see below)
>>
>> The libcman API is not final yet. There might be changes related to the way in
>> which we upload/download config. The API is missing a bunch of ccs_*
>> functionalities that would be seen as regression if missing (even tho i doubt
>> there are that many users out there).
>
> Some of the "hidden" features of ccs are the ability to create the
> configuration files through command line scripting. You could at least
> create a cluster and add nodes, although doesn't provide the ability to
> do everything the cluster.conf file. A command line interface to the
> cluster configuration that covers all aspects of the cluster.conf file
> would be needed before we can remove ccs from the system. One of the
> things missing from the ccs_tool are adding rgmanager services, am sure
> we are missing other features as well.
Actually the bit of ccs_tool reads and writes the XML file directly and will
need very minimal porting. The only ccs API it uses is to notify ccsd that the
config file has changed.
--
Patrick
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street,
Windsor, Berkshire, SL4 ITE, UK.
Registered in England and Wales under Company Registration No. 3798903
next prev parent reply other threads:[~2007-10-30 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 7:33 [Cluster-devel] [RFC] Killing ccs for good Fabio Massimo Di Nitto
2007-10-23 7:39 ` Fabio Massimo Di Nitto
2007-10-23 13:17 ` Kevin Anderson
2007-10-23 17:05 ` Fabio Massimo Di Nitto
2007-10-30 9:54 ` Patrick Caulfield [this message]
2007-10-23 14:34 ` David Teigland
2007-10-23 17:10 ` Fabio Massimo Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4726FF4F.6040501@redhat.com \
--to=pcaulfie@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).