June 20, 2007"> 8"> gnt-cluster"> Debian"> GNU"> GPL"> ]> 2006 2007 Google Inc. &dhdate; &dhucpackage; &dhsection; ganeti 1.2 &dhpackage; ganeti administration, cluster-wide &dhpackage; command arguments... The &dhpackage; is used for cluster-wide administration in the ganeti system. add-tags --from file tag Add tags to the cluster. If any of the tags contains invalid characters, the entire operation will abort. If the --from option is given, the list of tags will be extended with the contents of that file (each line becomes a tag). In this case, there is not need to pass tags on the command line (if you do, both sources will be used). A file name of - will be interpreted as stdin. command -n node command Executes a command on all nodes. If the option -n is not given, the command will be executed on all nodes, otherwise it will be executed only on the node(s) specified. Use the option multiple times for running it on multiple nodes, like: # gnt-cluster command -n node1.example.com -n node2.example.com date The command is constructed by concatenating all other command line arguments. For example, to list the contents of the /etc directory on all nodes, run: # gnt-cluster command ls -l /etc and the command which will be executed will be "ls -l /etc" copyfile -n node file Copies a file to all or to some nodes. The argument specifies the source file (on the current system), the -n argument specifies the target node, or nodes if the option is given multiple times. If -n is not given at all, the file will be copied to all nodes. Example: # gnt-cluster -n node1.example.com -n node2.example.com copyfile /tmp/test This will copy the file /tmp/test from the current node to the two named nodes. destroy Remove all configuration files related to the cluster, so that a gnt-cluster init can be done again afterwards. getmaster Displays the current master node. info Shows runtime cluster information: cluster name, architecture (32 or 64 bit), master node, node list and instance list. init -s secondary_ip -b bridge clustername This commands is only run once initially on the first node of the cluster. It will initialize the cluster configuration and setup ssh-keys and more. Note that the clustername is not any random name. It has to be resolvable to an IP address using DNS, and it is best if you give the fully-qualified domain name. The cluster can run in two modes: single-home or dual-homed. In the first case, all traffic (both public traffic, inter-node traffic and data replication traffic) goes over the same interface. In the dual-homed case, the data replication traffic goes over the second network. The -s option here marks the cluster as dual-homed and its parameter represents this node's address on the second network. If you initialise the cluster with -s, all nodes added must have a secondary IP as well. Note that for Ganeti it doesn't matter if the secondary network is actually a separate physical network, or is done using tunneling, etc. For performance reasons, it's recommended to use a separate network, of course. The -b option specifies the default bridge for instances. list-tags List the tags of the cluster. masterfailover Failover the master role to the current node. remove-tags --from file tag Remove tags from the cluster. If any of the tags are not existing on the cluster, the entire operation will abort. If the --from option is given, the list of tags will be extended with the contents of that file (each line becomes a tag). In this case, there is not need to pass tags on the command line (if you do, both sources will be used). A file name of - will be interpreted as stdin. rename -f name Renames the cluster and in the process updates the master IP address to the one the new name resolves to. At least one of either the name or the IP address must be different, otherwise the operation will be aborted. Note that since this command can be dangerous (especially when run over SSH), the command will require confirmation unless run with the -f option. verify Verify correctness of cluster configuration. This is safe with respect to running instances, and incurs no downtime of the instances. version Show the cluster version. &footer;