Base Users Guide:
Prev	Appendix E. Kickstart Nodes Reference	Next

E.1. Rocks Base Nodes

E.1.1. 411-base

The packages and other common elements of the 411 Secure Information Service.

Parent Nodes:

base

Sets up the 411 Secure Information Service for clients. The 411 service will automatically configure itself when a file is published. Also puts all current 411 files from the frontend into the kickstart file for services that cannot tolerate a single 411 failure. Note that 411 can never guarentee full absolute success at any single time. It only offers consistancy over the long term.

Parent Nodes:

client

E.1.3. 411-server

Sets up the 411 Secure Information Service for Master nodes. Creates the RSA public and private keys for the cluster, and configures Apache for 411.

Parent Nodes:

server

E.1.4. apache

Apache HTTP Server

Parent Nodes:

server

E.1.5. auto-kickstart

Force a kickstart on power fail or system crash.

Parent Nodes:

base

E.1.6. autofs

AutoFS for automounting home directories over NFS or the loopback device.

Parent Nodes:

base

E.1.7. autofs-client

AutoFS Client

Parent Nodes:

client

E.1.8. autofs-server

AutoFS server

Parent Nodes:

server

E.1.9. base

Base class for all Rocks nodes. This should include compute nodes, frontend nodes, standalone laptops, computer labs, graphics nodes, nfs servers To achieve this level of flexibility this base class should have edges only to those classes that implement the core of Rocks.

Parent Nodes:

Children Nodes:

E.1.10. bootstrap-dummy

Dummy terminal node for bootstrap-packages subgraph

Parent Nodes:

bootstrap-packages-base

E.1.11. bootstrap-packages-base

Additional packages that may be needed on a server that was not originally built with Rocks. Tested on Native CentOS installed build machine.

Parent Nodes:

devel-appliance

Children Nodes:

bootstrap-dummy

E.1.12. ca

Sets up keys for the frontend Certificate Authority

Parent Nodes:

security-server

E.1.13. cdr

CDR Tools (burnings, iso, ripping, mp3 enconding)

Parent Nodes:

devel

E.1.14. central

A Rocks Cluster Central server. Can kickstart other servers over the network. Also contains general Apache security setup.

Parent Nodes:

security-server

E.1.15. client

The 'client node' in the graph. This file is used as a connection point for other XML configuration nodes.

Parent Nodes:

Children Nodes:

E.1.16. client-firewall

Client node firewall rules

Parent Nodes:

client

E.1.17. client-rootpw

Parent Nodes:

client

E.1.18. compilers

Parent Nodes:

devel

Children Nodes:

c-development
fortran-development

E.1.19. compute

Compute Appliance Node. You should create your own extend-compute.xml file to add functionality to this appliance type.

Children Nodes:

compute-appliance

E.1.20. compute-appliance

Rocks Cluster Compute Node.

Parent Nodes:

compute

Children Nodes:

client

E.1.21. custom-partition

Parent Nodes:

base

Children Nodes:

partition

E.1.22. devel

Parent Nodes:

Children Nodes:

E.1.23. devel-server

Add Development Appliance Definition to the Frontend

Parent Nodes:

devel-appliance
server

E.1.24. dhcp-client

DHCP Client

Parent Nodes:

client

E.1.25. dhcp-server

Setup the DHCP server for the cluster

Parent Nodes:

server

E.1.26. disk-stamp

Take a root partition, and make it ours! This is the key to determining, on reinstalls, if we should save partitions (because the stamp is there) or blow away all the paritions on the disk (because the stamp isn't there).

Parent Nodes:

base

E.1.27. dns-server

Configures a DNS nameserver for the cluster on the frontend. Both forward and reversed zones are defined using the database.

Parent Nodes:

server

E.1.28. do-partition

Parent Nodes:

partition

E.1.29. docbook

DOC Book support (needed to build rolls)

Parent Nodes:

devel

E.1.30. emacs

Emacs OS

Parent Nodes:

E.1.31. ethers-server-postshell

Intended to be run after postshell. Will re-source the probed-ethers.sh and then regenerate configs for the network interfaces, modprobe.conf. ethers-server.xml will have probed the interfaces to create probed-ethers.sh. A user can put "postshell" on the command line and then edit probed-ethers.sh to arbitrarily re-assign mac:interface definitions.

Parent Nodes:

postshell

E.1.32. fail2ban

Install fail2ban on node with public connection

Parent Nodes:

E.1.33. firewall

Default firewall rules for all appliances. Disable everything but SSH.

Parent Nodes:

base

E.1.34. fortran-development

Fortran

Parent Nodes:

compilers

E.1.35. foundation-base

Rocks Foundation Packages

Parent Nodes:

base

E.1.36. foundation-client

Rocks Foundation Packages

Parent Nodes:

client

E.1.37. foundation-server

Rocks Foundation Packages

Parent Nodes:

devel-appliance
server

E.1.38. google-otp

Google OTP Authentication Support

Parent Nodes:

E.1.39. google-otp-server

Google OTP Authentication Support Server Side

Parent Nodes:

server

E.1.40. grub

Boot loader support (GRand Unified Bootloader)

Parent Nodes:

base

E.1.41. grub-client

Boot loader configuration for cluster appliances.

Parent Nodes:

client

E.1.42. grub-server

Boot loader configuration for cluster frontends. Puts enough information on the command line to contact the central server on a reinstall.

Parent Nodes:

server

E.1.43. grub2-client

Boot loader configuration for cluster appliances. Grub2 edition

Parent Nodes:

client

E.1.44. homepage

Create a simple cluster home page

Parent Nodes:

server

E.1.45. i18n

Internationalization support

Parent Nodes:

base

E.1.46. insert-rolls

Populates the frontend database with initially selected rolls.

Parent Nodes:

server

E.1.47. install

Do everything needed to kickstart compute nodes or, generally speaking, everything needed to kickstart any node from this machine.

Parent Nodes:

server

E.1.48. ip-diag

TCP/IP Network diagnostic tools.

Parent Nodes:

base

E.1.49. ipmi-base

Common IPMI Support

Parent Nodes:

base

E.1.50. ipmi-client

Client Nodes

Parent Nodes:

client

E.1.51. ipmi-server

Server Nodes

Parent Nodes:

server

E.1.52. logrotate

Append rules to logrotate to prune files in /var/log

Parent Nodes:

base

E.1.53. mail

Mail support for the cluster.

Parent Nodes:

base

E.1.54. mail-client

Mail support for nodes in the cluster. These nodes do not accept mail for local delivery. They pass everything to a mail hub (generally the frontend).

Parent Nodes:

client

E.1.55. mail-server

Mail hub for the cluster. This node serves as the post-office for the whole cluster.

Parent Nodes:

server

E.1.56. md-rebuild

Moderate MD Raid Rebuild Speed

Parent Nodes:

base

E.1.57. mosh

MOSH - Mobile Shell from MIT

Parent Nodes:

base

E.1.58. nas

NAS Appliance Node. You should create your own extend-nas.xml file to add functionality to this appliance type.

Children Nodes:

E.1.59. nas-appliance

Rocks Cluster NAS Node.

Parent Nodes:

E.1.60. nas-exports

Rocks Cluster NAS Node export file system definitions

Parent Nodes:

E.1.61. nas-partition

Define a partitioning layout for NAS nodes.

Parent Nodes:

E.1.62. networking-client

Configure a node's network

Parent Nodes:

client

E.1.63. networking-server

Configure a node's network

Parent Nodes:

server

E.1.64. nfs-server

NFS Servers for /export

Parent Nodes:

server

E.1.65. node-certs

Place the root ssh public key from the installation machine on to the installed machine While we're at it suck over the SSL CA Cert/Key. This is a quick hack, we need a secure method for this to put our pants back on.

Parent Nodes:

client

E.1.66. ntp

Network Time Protocol

Parent Nodes:

base

E.1.67. ntp-client

Network Time Protocl

Parent Nodes:

client

E.1.68. ntp-server

Network Time Protocl

Parent Nodes:

server

E.1.69. null

An empty XML file.

Parent Nodes:

E.1.70. partition

Parent Nodes:

custom-partition

Children Nodes:

do-partition

E.1.71. partitions-save

Save the partition info from this node by sending a message back to the frontend. The frontend will store the partition info in the database

Parent Nodes:

client

E.1.72. partitions-save-server

Save the partition info for a server node by sending a message to the local host. This will store the partition info in the database. This file is a copy of 'partitions-save' which is connected to the 'client' graph. We need two files because of ordering: we want to save the partitions as early as possible on client nodes so we order 'partitions-save' off 'HEAD', but for server nodes, we need to wait for the database to be configured, so we order 'partitions-save-server' off 'TAIL'.

Parent Nodes:

server

E.1.73. postshell

Allow interaction after all post sections have run If postshell is on the command line, wait until /mnt/sysimage/tmp/postshell is removed interactively.

Parent Nodes:

base

Children Nodes:

ethers-server-postshell

E.1.74. profile-server

profile.d entries for servers in Rocks 7

Parent Nodes:

server

E.1.75. pxe

Provides pre-execution environment (PXE) support for frontend machines.

Parent Nodes:

server

E.1.76. pxeboot

PXE first configuration for client nodes

Parent Nodes:

client

E.1.77. resolv

Generates the resolv.conf file for slave nodes. We point to all nameservers listed in the PrivateDNSServers entry in the app_globals table in the database. This node used to be named copy-resolv.xml.

Parent Nodes:

client

E.1.78. rlo

Remote lights Out

Parent Nodes:

server

E.1.79. rocks-devel

Rocks Development

Parent Nodes:

devel-appliance
server

E.1.80. rocks-dist

Distribution building with rocks-dist

Parent Nodes:

devel-appliance
server

E.1.81. root

The root node that is used by rolls in order to tell 'kpp' which node should be the root of the traversed graph

Children Nodes:

server

E.1.82. routes-client

Set up static routes

Parent Nodes:

client

E.1.83. routes-server

Set up static routes on server

Parent Nodes:

server

E.1.84. rpc

RPC support

Parent Nodes:

base

E.1.85. rsh

Enable RSH

Parent Nodes:

client

E.1.86. screen-clusterinfo

Parent Nodes:

server

E.1.87. screen-network-misc

Parent Nodes:

server

E.1.88. screen-network-private

Parent Nodes:

server

E.1.89. screen-network-public

Parent Nodes:

server

E.1.90. screen-partitioning

Parent Nodes:

server

E.1.91. screen-root-password

Parent Nodes:

server

E.1.92. screen-timezone

Parent Nodes:

server

E.1.93. scripting

Parent Nodes:

base

Children Nodes:

perl-development
perl-modules
python-development
tcl-development

E.1.94. security

Security parent node for common security elements.

Parent Nodes:

base

Children Nodes:

E.1.95. selinux

Configure SELinux

Parent Nodes:

base

E.1.96. serf-client

serf

Parent Nodes:

client

E.1.97. serf-common

serf

Parent Nodes:

E.1.98. serf-server

serf

Parent Nodes:

server

E.1.99. server-firewall

Server node firewall rules

Parent Nodes:

server

E.1.100. server-rootpw

$Id: server-rootpw.xml,v 1.2 2011/06/21 23:26:04 anoop Exp $ Root Password for the frontend

Parent Nodes:

server

E.1.101. shared-memory

Configure the maximum size of a shared memory segment to be 3/4 of main memory

Parent Nodes:

client

E.1.102. snmp-client

SNMP Client machine.

Parent Nodes:

devel-appliance
server

E.1.103. snmp-server

SNMP Server. Open all the tables to the public and customize a couple site varialbe.

Parent Nodes:

base

E.1.104. ssh

Enable SSH

Parent Nodes:

security

E.1.105. ssh-client

SSH Config for compute nodes and other non-frontend appliances. We are using one key pair among all SSH servers in the cluster. This implies we do not care about Man-in-the-Middle attacks. We have subverted the protection for these attacks for several releases (broadcastSSH). This logic should not be in the ssh.xml node so the frontend will generate its own keypair.

Parent Nodes: