From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio M. Di Nitto Date: Fri, 19 Sep 2008 11:43:46 +0200 (CEST) Subject: [Cluster-devel] Command Line Cluster Configuration Tools In-Reply-To: <48C775AD.7080806@redhat.com> References: <1220989706.4295.35.camel@dhcp80-204.msp.redhat.com> <48C775AD.7080806@redhat.com> Message-ID: List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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.