[Cluster-devel] Command Line Cluster Configuration Tools

[Cluster-devel] Command Line Cluster Configuration Tools

[Kevin Anderson]

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
  

[Cluster-devel] Command Line Cluster Configuration Tools

[Christine Caulfield]

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.

-- 

Chrissie

[Cluster-devel] Command Line Cluster Configuration Tools

[Ryan McCabe]

On Wed, Sep 10, 2008 at 08:22:21AM +0100, Christine Caulfield wrote:
> 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.

Where did you pull the ricci src from? The current source with the
configuration distribution tool is at fedorahosted now
(http://git.fedorahosted.org/git/conga.git). If that is still not
working for you, could you let me know?

I'll write something up about how to distribute the configuration files
with it.


Ryan

[Cluster-devel] Command Line Cluster Configuration Tools

[Christine Caulfield]

Ryan McCabe wrote:
> On Wed, Sep 10, 2008 at 08:22:21AM +0100, Christine Caulfield wrote:
>> 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.
> 
> Where did you pull the ricci src from? The current source with the
> configuration distribution tool is at fedorahosted now
> (http://git.fedorahosted.org/git/conga.git). If that is still not
> working for you, could you let me know?

OK, my fault probably. I deleted my existing git tree and cloned a new
one and it's fine. I had tried make clean/configure and all those things.

I blame git ... as usual ;)

> I'll write something up about how to distribute the configuration files
> with it.
> 

Thanks
-- 

Chrissie

[Cluster-devel] Command Line Cluster Configuration Tools

[Fabio M. Di Nitto]

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.

[Cluster-devel] Command Line Cluster Configuration Tools

[Fabio M. Di Nitto]

On Tue, 9 Sep 2008, Kevin Anderson wrote:

> Hi all,
>
> 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?

I think this will be possible once Lon lands the xml translator for ldap 
that will collect all available config options in one single place. With a 
bit of magic on the schema, we could parse it to create a command line of 
somekind without hardcoding everything like it is now.

Fabio

--
I'm going to make him an offer he can't refuse.