From: Kevin Anderson <kanderso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Command Line Cluster Configuration Tools
Date: Tue, 09 Sep 2008 14:48:26 -0500 [thread overview]
Message-ID: <1220989706.4295.35.camel@dhcp80-204.msp.redhat.com> (raw)
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?
Kevin
next reply other threads:[~2008-09-09 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 19:48 Kevin Anderson [this message]
2008-09-10 7:22 ` [Cluster-devel] Command Line Cluster Configuration Tools 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
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=1220989706.4295.35.camel@dhcp80-204.msp.redhat.com \
--to=kanderso@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).