[c3-users] Unable to construct an c3.conf containing indirect cluster

Thomas Naughton naughtont at ornl.gov
Fri Mar 28 10:53:41 EDT 2008


Ok, my memory has been dusted off a bit now -- c3.conf man page was somewhat
helpful after *full* re-read.

The indirect clusters can reference other clusters, however, they do not
reference the c3.conf "block view" of the cluster, i.e., the internal block
names 'cluster db_servers' & 'cluster app_servers'.  Instead, they just
reference the nodes (headnode, optionally the compute nodes behind that
node), etc.

The circular issue to avoid comes from the fact that when cluster xtorc
references cluster fooTorc via an indirect block, if the config on fooTorc
again indirectly references xtorc, you'll loop.

So, I just tested a few things and feel reasonably confident from the
testing (didn't read code) that we're not doing exactly what he wants from
within the config file itself.  But you can reference the blocks from the
commandline in the machine defs area,

     $ cexec  db_servers: app_servers:   hostname

Or you can use the '--all' option to execute on all nodes on all clusters
in the config file (ignoring the cmdline machine defs).

Wow, I hope that made some since.


PS  I'm Cc'ing the c3-users list with this info (just my response) to have
     an archive of the notes.

   Thomas Naughton                                      naughtont at ornl.gov
   Research Associate                                   (865) 576-4184

>>> Nicolas Cros wrote:
>>>> Thomas
>>>> Thank you very much for your answer. I understand better the indirect 
>>>> cluster.
>>>> I can not use this feature in my case, as what i want to do is to include 
>>>> a cluster inside another one.
>>>> Say I have a cluster named 'db-servers', another 'app-servers' , and i 
>>>> want to create a cluster named "all", which redirects to cluster 
>>>> 'db-servers' and 'app-servers'
>>>>> Nicolas,
>>>>> There is an example in the C3.CONF(5) manual page. 
>>>>> http://www.csm.ornl.gov/torc/C3/Man/c3.conf.shtml
>>>>> The syntax is usually something like:
>>>>>      cluster torc {
>>>>>           :node0
>>>>>      }
>>>>> It is used as a reference to another cluster, and basically just 
>>>>> forwards
>>>>> the command to that remote machine, for it to then figure out how to
>>>>> connect to the nodes, i.e., via the '/etc/c3.conf' on that remote 
>>>>> cluster.
>>>>> I hope that helps.  Let us now if you're still having problems.
>>>>> --tjn
>>>>>   _________________________________________________________________________
>>>>>    Thomas Naughton naughtont at ornl.gov
>>>>>    Research Associate                                   (865) 576-4184
>>>>> On Thu, 20 Mar 2008, Nicolas Cros wrote:
>>>>>> Hello,
>>>>>> I'm not able to define an indirect cluster containing 2 clusters.
>>>>>> Do you have an example please ?
>>>>>> Here is my configuraiton file :
>>>>>> cluster dium-qt {
>>>>>>       dium-dev:dium-dev
>>>>>>       dium-sfr-qt
>>>>>>       dium-trm-qt
>>>>>>       dium-web-qt
>>>>>> }
>>>>>> cluster dium-qo {
>>>>>>       dium-dev:dium-dev
>>>>>>       dium-sfr-qo
>>>>>>       dium-trm-qo
>>>>>>       dium-web-qo
>>>>>> }
>>>>>> cluster dium {
>>>>>>       dium-dev:dium-dev
>>>>>>       :dium-qt
>>>>>>       :dium-qo
>>>>>> }
>>>>>> Thanks .
>>>>>> -- 
>>>>>> Nicolas.Cros at cls.fr             Collecte Localisation Satellites
>>>>>> Administrateur Systeme          8-10 rue Hermes
>>>>>> tel              Parc Technologique du Canal
>>>>>> fax              31520 Ramonville St Agne, France

More information about the c3-users mailing list