xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-10-31 11:22:27 +00:00
Code Issues Releases Wiki Activity

Clean up the Hierarchy support Page

Browse Source 
Just clean up some small text issues when re-reading this page
This commit is contained in:
Victor Hu
2015-10-20 10:49:53 -04:00
parent bb5650db83
commit 4e74e0b683
1 changed files with 26 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
docs/source/advanced/hierarchy/introduction.rst
View File

@@ -1,50 +1,48 @@
Introduction
============
In large clusters, it is desirable to have more than one node (the Management
Node - MN) handle the installation and management of the compute nodes. We
call these additional nodes **service nodes (SN)**. The management node can
delegate all management operations needed by a compute node to the SN that is
managing that compute node. You can have one or more service nodes setting up
to install and manage groups of compute nodes.
When dealing with large clusters, it is desirable to have more than one node,
the xCAT Management Node (MN), handle the installation and management of the
Com[pute Nodes (CN). The concept of these additional "helper" nodes are called
**Service Nodes (SN)**. The Management Node can delegate all management
operations required by a compute node to the service node that is assigned to
manage that Compute Node. You can configure one or more Service Nodes to install
and manage a group of Compute Nodes.
Service Nodes
-------------
With xCAT, you have the choice of either having each service node
install/manage a specific set of compute nodes, or having a pool of service
nodes, any of which can respond to an installation request from a compute
node. (Service node pools must be aligned with the network broadcast domains,
because the way a compute node choose its SN for that boot is by whoever
With xCAT, you have the choice of either having each Service Node
install/manage a specific set of compute nodes, or having a pool of Service
Nodes, any of which can respond to an installation request from a compute
node. (Service Node pools must be aligned with the network broadcast domains,
because the way a compute node choose its Service Node for that boot is by whoever
responds to the DHCP request broadcast first.) You can also have a hybrid of
the 2 approaches, in which for each specific set of compute nodes you have 2
or more SNs in a pool.
or more Service Nodes in a pool.
Each SN runs an instance of xcatd, just like the MN does. The xcatd daemons
communicate with each other using the same XML/SSL protocol that the xCAT
client uses to communicate with xcatd on the MN.
Each Service Node runs an instance of xcatd, just like the Management Node does.
The ``xcatd`` daemons communicate with each other using the same XML/SSH protocol
that the xCAT clients use to communicate with ``xcatd`` on the Management Node.
Daemon-based Databases
----------------------
The service nodes need to communicate with the xCAT database on the Management
Node. They do this by using the remote client capability of the database (i.e.
they don't go through xcatd for that). Therefore the Management Node must be
running one of the daemon-based databases supported by xCAT (PostgreSQL,
MySQL).
The Service Nodes will need to communicate with the xCAT database on the Management
Node and do this by using the remote client capabilities of the database. Therefore,
the Management Node must be running one of the daemon-based databases supported by
xCAT (PostgreSQL, MySQL, MariaDB, etc).
The default SQLite database does not support remote clients and cannot be used
in hierarchical clusters. This document includes instructions for migrating
your cluster from SQLite to one of the other databases. Since the initial
install of xCAT will always set up SQLite, you must migrate to a database that
supports remote clients before installing your service nodes.
supports remote clients before installing your Service Nodes.
Setup
-----
xCAT will help you install your service nodes as well as install on the SNs
xCAT software and other required rpms such as perl, the database client, and
other pre-reqs. Service nodes require all the same software as the MN
(because it can do all of the same functions), except that there is a special
top level xCAT rpm for SNs called xCATsn vs. the xCAT rpm that is on the
Management Node. The xCATsn rpm tells the SN that the xcatd on it should
behave as an SN, not the MN.
xCAT will help you install your Service Nodes as well as install on the xCAT-SN
software and other required rpms and pre-reqs. Service Nodes require the same
software as installed on the Management Node with the exception of the top level
xCAT rpm. The Management Node installs the ``xCAT`` package while the Service Nodes
install the ``xCATsn`` package.