rocks add appliance {appliance} [graph=string] [membership=string] [node=string] [os=string] [public=bool]
Add an appliance specification to the database.
arguments
The appliance name (e.g., 'compute', 'frontend', 'nas').
parameters
The directory name of the graph XML files. The default is 'default'.
The full membership name of the appliance. This name will be displayed in the appliances menu by insert-ethers (e.g., 'NAS Appliance'). If not supplied, the membership name is set to the appliance name.
The name of the root XML node (e.g., 'compute', 'nas', 'viz-tile'). If not supplied, the node name is set to the appliance name.
The OS that the appliance type can support. Some appliances can support both linux and sunos, where as others can support only one of the two. Acceptable values are 'linux' or 'sunos'. Defaults to 'linux'
True means this appliance will be displayed by 'insert-ethers' in the Appliance menu. The default is 'yes'.
examples
rocks add appliance attr {appliance} {attr} {value} [attr=string] [value=string]
Adds an attribute to an appliance and sets the associated values
arguments
Name of appliance
Name of the attribute
Value of the attribute
parameters
same as attr argument
same as value argument
examples
Sets the sge attribution to False for compute appliances
same as above
rocks add appliance route {os} {address} {gateway} [netmask=string]
Add a route for an appliance type in the cluster
arguments
The OS type (e.g., 'linux', 'sunos', etc.). This argument is required.
Host or network address
Network or device gateway
parameters
Specifies the netmask for a network route. For a host route this is not required and assumed to be 255.255.255.255
rocks add attr {attr} {value} [attr=string] [value=string]
Adds a global attribute for all nodes
arguments
Name of the attribute
Value of the attribute
parameters
same as attr argument
same as value argument
examples
Adds the sge attribution and sets it to False.
related commands
rocks add bootaction [action=string] [args=string] [kernel=string] [ramdisk=string]
Add a bootaction specification to the system.
parameters
Label name for the bootaction. You can see the bootaction label names by executing: 'rocks list bootaction [host(s)]'.
The second line for a pxelinux definition (e.g., ks ramdisk_size=150000 lang= devfs=nomount pxe kssendmac selinux=0)
The name of the kernel that is associated with this boot action.
The name of the ramdisk that is associated with this boot action.
examples
Add the 'os' bootaction.
Add the 'memtest' bootaction.
rocks add distribution {distribution}
Add a distribution specification to the database.
arguments
Name of the new distribution.
examples
Adds the distribution named "rocks-dist" into the database.
rocks add firewall {category=index} [action=string] [chain=string] [network=string] [output-network=string] [protocol=string] [rulename=string] [rulesrc=string] [service=string]
Add a firewall rule to the a category in cluster.
arguments
[global,os,appliance,host]=index. Must precede all other a=b parameters Apply rule to index (member) of category. e.g. os=linux, appliance=login, or host=compute-0-0. global, global=, and global=global all refer to the global category
parameters
The iptables 'action' this rule should be applied to (e.g., ACCEPT, REJECT, DROP).
The iptables 'chain' this rule should be applied to (e.g., INPUT, OUTPUT, FORWARD).
The network this rule should be applied to. This is a named network (e.g., 'private') and must be one listed by the command 'rocks list network'. To have this firewall rule apply to all networks, specify the keyword 'all'.
The output network this rule should be applied to. This is a named network (e.g., 'private') and must be one listed by the command 'rocks list network'.
The protocol associated with the rule. For example, "tcp" or "udp". To have this firewall rule apply to all protocols, specify the keyword 'all'.
User-defined name of rule. Required. Firewall rules are ordered lexicographically.
system or custom. Default is 'custom'. Rules defined as 'system' are not dumped with rocks dump firewall.
The service identifier, port number or port range. For example "www", 8080 or 0:1024. To have this firewall rule apply to all services, specify the keyword 'all'.
examples
Accept TCP packets for the ssh service on the public network on the INPUT chain and apply the "-m state --state NEW" flags to the rule. Apply the rule to login appliances (appliance=login) Name the rule ACCEPT-SSH If 'eth1' is associated with the public network, this will be translated as the following iptables rule: "-A INPUT -i eth1 -p tcp --dport ssh -m state --state NEW -j ACCEPT"
Accept all protocols and all services on the private network on the INPUT chain. Apply this rule to all nodes in the cluster (global) If 'eth0' is the private network, then this will be translated as the following iptables rule: "-A INPUT -i eth0 -j ACCEPT"
DROP all non-matched packets Apply this rule to host compute-0-0 (host=compute-0-0) rule will be named ZZDRACONIAN This will drop all non-matched packets that have not been previously accepted Known as a draconian firewall rule.
rocks add host {host} [cpus=int] [membership=string] [os=string] [rack=int] [rank=int]
Add an new host to the cluster.
arguments
A single host name. If the hostname is of the standard form of basename-rack-rank the default values for the membership, rack, and rank parameters are taken from the hostname.
parameters
Number of CPUs (cores) in the given host. If not provided the default of 1 CPU is inserted into the database.
Appliance membership name. If not provided and the host name is of the standard form the membership is taken from the basename of the host.
The operating system name. The default is: linux.
The number of the rack where the machine is located. The convention in Rocks is to start numbering at 0. If not provided and the host name is of the standard form the rack number is taken from the host name.
The position of the machine in the rack. The convention in Rocks is to number from the bottom of the rack to the top starting at 0. If not provided and the host name is of the standard form the rank number is taken from the host name.
examples
Adds the host "compute-0-0" to the database with 1 CPU, a membership name of "compute", a rack number of 0, and rank of 1.
Adds the host "frontend" to the database with 1 CPU, a membership name of "Frontend", a rack number of 0, and rank of 1.
related commands
rocks add host alias {host} {name} [name=string]
Adds an alias to a host
arguments
Host name of machine
The alias name for the host.
parameters
Can be used in place of the name argument.
examples
Adds the alias 'c-0-0' to the host 'compute-0-0'.
Same as above.
rocks add host attr {host} {attr} {value} [attr=string] [value=string]
Adds an attribute to a host and sets the associated values
arguments
Host name of machine
Name of the attribute
Value of the attribute
parameters
same as attr argument
same as value argument
examples
Sets the number of cpus of compute-0-0 to 2
same as above
related commands
rocks add host bonded {host} [channel=string] [interfaces=string] [ip=string] [name=string] [network=string]
Add a channel bonded interface for a host
arguments
Host name of machine
parameters
The channel name (e.g., "bond0").
The physical interfaces that will be bonded. The interfaces can be a comma-separated list (e.g., "eth0,eth1") or a space-separated list (e.g., "eth0 eth1").
The IP address to assign to the bonded interface.
The host name associated with the bonded interface. If name is not specified, then the interface get the internal host name (e.g., compute-0-0).
The network to be assigned to this interface. This is a named network (e.g., 'private') and must be listable by the command 'rocks list network'.
examples
Adds a bonded interface named "bond0" to compute-0-0 by bonding the physical interfaces eth0 and eth1, it assigns the IP address 10.1.255.254 to bond0 and it associates this interface to the private network.
rocks add host interface {host} {iface} [iface=string] [ip=string] [mac=string] [module=string] [name=string] [subnet=string] [vlan=string]
Adds an interface to a host and sets the associated values
arguments
Host name of machine
The interface name on the host (e.g., 'eth0', 'eth1')
parameters
Can be used in place of the iface argument.
The IP address to assign to the interface (e.g., '192.168.1.254')
The MAC address of the interface (e.g., '00:11:22:33:44:55')
The device driver name (or module) of the interface (e.g., 'e1000')
The name to assign to the interface
The name of the subnet to assign to the interface (e.g., 'private')
The VLAN ID to assign the interface
examples
same as above
rocks add host key {host} [key=string]
Add a public key for a host. One use of this public key is to authenticate messages sent from remote services.
arguments
Host name of machine
parameters
A public key. This can be the actual key or it can be a path name to a file that contains a public key (e.g., /tmp/public.key).
rocks add host route {host} {address} {gateway} [netmask=string]
Add a route for a host
arguments
Host name of machine
Host or network address
Network or device gateway
parameters
Specifies the netmask for a network route. For a host route this is not required and assumed to be 255.255.255.255
rocks add host sec_attr {host} [attr=string] [crypted=boolean] [enc=string] [value=string]
Add a secure attribute to the database. The user also has the option of not supplying the value on the command line. The command will prompt the user to enter the secure attribute value, and will not echo this value on screen. If the user chooses to enter the value for the secure attribute by prompt, then the value entered must be in an unencrypted form.
arguments
Host name of machine
parameters
Name of the attribute
Is "value" already crypted or not
Encryption scheme to use to crypt the value. Currently supported values are "sha", "crypt", "portable".
Value of the attribute
examples
Sets a secure attribute called db_pw to the crypted value of "DatabasePassword" using the sha1 encoding schema.
Same as above
rocks add network {name} {subnet} {netmask} [dnszone=string] [mtu=string] [netmask=string] [servedns=boolean] [subnet=string]
Add a network to the database. By default both the "public" and "private" networks are already defined by Rocks.
arguments
Name of the new network.
The IP network address for the new network.
The IP network mask for the new network.
parameters
The Domain name or the DNS Zone name to use for all hosts of this particular subnet. Default is set to the name of the subnet
The MTU for the new network. Default is 1500.
Can be used in place of the netmask argument.
Parameter to decide whether this zone will be served by the nameserver on the frontend.
Can be used in place of the subnet argument.
examples
Adds the optiputer network address of 192.168.1.0/255.255.255.0.
Same as above, but set the MTU to 9000.
rocks add os attr {os} {attr} {value} [attr=string] [value=string]
Adds an attribute to an os and sets the associated values
arguments
Name of os
Name of the attribute
Value of the attribute
parameters
same as attr argument
same as value argument
examples
Sets the sge attribution to False for linux nodes
rocks add os route {os} {address} {gateway} [netmask=string]
Add a route for an OS type
arguments
The OS type (e.g., 'linux', 'sunos', etc.). This argument is required.
Host or network address
Network or device gateway
parameters
Specifies the netmask for a network route. For a host route this is not required and assumed to be 255.255.255.255
rocks add roll [roll...] [clean=bool]
Add Roll ISO images to this machine's roll directory. This command copies all files in the ISOs to a directory under /export/rocks/install/rolls.
arguments
A list of Roll ISO images to add to /export/rocks/install/rolls. If no list is supplied, then if a roll is mounted on /mnt/cdrom, it will be copied into /export/rocks/install/rolls.
parameters
If set, then remove all files from any existing rolls of the same name, version, and architecture before copying the contents of the Rolls onto the local disk. This parameter should not be set when adding multi-CD Rolls such as the OS Roll, but should be set when adding single Roll CDs such as the Grid Roll.
examples
Adds the Kernel Roll to local Roll directory. Before the Roll is added the old Kernel Roll packages are removed from the Roll directory.
Added the Kernel, PVFS, and Ganglia Rolls to the local Roll directory.
related commands
rocks add route {address} {gateway} [netmask=string]
Add a route for all hosts in the cluster
arguments
Host or network address
Network (e.g., IP address), subnet name (e.g., 'private', 'public'), or a device gateway (e.g., 'eth0).
parameters
Specifies the netmask for a network route. For a host route this is not required and assumed to be 255.255.255.255
rocks add sec_attr {attr} [crypted=boolean] [enc=string] [value=string]
Add a secure attribute to the database. The user also has the option of not supplying the value on the command line. The command will prompt the user to enter the secure attribute value, and will not echo this value on screen. If the user chooses to enter the value for the secure attribute by prompt, then the value entered must be in an unencrypted form.
arguments
Name of the attribute
parameters
Is "value" already crypted or not
Encryption scheme to use to crypt the value. Currently supported values are "sha", "crypt", "portable".
Value of the attribute
examples
Sets a secure attribute called db_pw to the crypted value of "DatabasePassword" using the sha1 encoding schema.
Same as above
rocks add var {service} {component} {value} [appliance=string] [component=string] [service=string] [value=string]
Add variables to the Rocks key/value database. Variables are defined as quad of (Appliance, Service, Component, Value). Within a node XML file, values can be retrieved as <var name="Service_Component"/>.
arguments
Defines the service name. e.g., service=Kickstart.
Defines the component name. e.g. component=PublicDNS.
Defines the value for the variable.
parameters
If supplied, restricts to the named appliance. See 'rocks list appliance' for a listing of appliances.
Can be used in place of component argument.
Can be used in place of service argument.
Can be used in place of value argument.
examples
Add the variable name <var name="Condor_Master"/> to 'localhost'.
Same as above.
Add the variable name <var name="Condor_Master"/> to 'localhost' and associate it with only compute appliances.