From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Command Line Cluster Configuration Tools
Date: Fri, 19 Sep 2008 11:43:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0809191142360.21806@trider-g7> (raw)
In-Reply-To: <48C775AD.7080806@redhat.com>
On Wed, 10 Sep 2008, Christine Caulfield wrote:
> Kevin Anderson wrote:
>> Hi all,
>>
>> Now that we are removing ccsd from the mix for cluster 3.x, what are we
>> doing about all of the command line cluster configuration capabilities
>> we had in ccs_tool? What is the new command to add/delete nodes,
>> propagate configuration? I would also like to have command line ways to
>> add resources to the configuration. Basically, anything you can do with
>> vi and XML knowledge, we need a scriptable method of doing the same
>> operation.
>>
>> Thoughts?
>>
>
> ccs_tool with it's addnode (etc) subcommands still exists. It writes
> directly to cluster.conf as it always did.
>
> Fabio had the good sense to #ifdef the ccsd update parts of that code so
> that they are only active when LEGACY_CODE is defined. So if you still
> have ccsd then 'ccs_tool addnode' will tell it to distribute the new
> version.
>
> I don't know anything about the new distribution system (I never did
> managed to get ricci compiled!) but we might need to add hooks for that
> into the ccs_tool editconf functions for compatibility.
Once the new system is in place and distributed we can readd propagation
capabilities to ccs_tool and invoke whatever will be
"cman_tool reload-conf" feature.
Fabio
--
I'm going to make him an offer he can't refuse.
next prev parent reply other threads:[~2008-09-19 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 19:48 [Cluster-devel] Command Line Cluster Configuration Tools Kevin Anderson
2008-09-10 7:22 ` Christine Caulfield
2008-09-11 17:23 ` Ryan McCabe
2008-09-12 8:05 ` Christine Caulfield
2008-09-19 9:43 ` Fabio M. Di Nitto [this message]
2008-09-19 9:46 ` Fabio M. 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=Pine.LNX.4.64.0809191142360.21806@trider-g7 \
--to=fdinitto@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).