X-Git-Url: https://code.grnet.gr/git/ganeti-local/blobdiff_plain/11c05c42db05ed0f492bb588c458d5e81cdcb867..d3b4cf9f4a83e9914c8235d6e3c4c819e929c2a9:/man/gnt-cluster.sgml diff --git a/man/gnt-cluster.sgml b/man/gnt-cluster.sgml index c8ec24b..17fc206 100644 --- a/man/gnt-cluster.sgml +++ b/man/gnt-cluster.sgml @@ -2,7 +2,7 @@ - December 12, 2007"> + February 12, 2009"> 8"> @@ -20,6 +20,8 @@ 2006 2007 + 2008 + 2009 Google Inc. &dhdate; @@ -28,7 +30,7 @@ &dhucpackage; &dhsection; - ganeti 1.2 + ganeti 2.0 &dhpackage; @@ -105,9 +107,9 @@ The command is executed serially on the selected nodes. If the master node is present in the list, the command will be executed last on the master. Regarding the other nodes, the - execution order is somewhat alphabetic (it's smarter so that + execution order is somewhat alphabetic, so that node2.example.com will be earlier than node10.example.com but - after node1.example.com). + after node1.example.com. @@ -208,13 +210,29 @@ init + -s secondary_ip + -b bridge - -t hypervisor-type + -g vg-name + --master-netdev vg-name + -m mac-prefix + --no-lvm-storage + + --file-storage-dir dir + + --enabled-hypervisors hypervisors + + -t hypervisor name + + --hypervisor-parameters hv-params + + --backend-parameters be-params + clustername @@ -228,8 +246,8 @@ 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. Also it is advisable to reserve a per-cluster - unique name, and not try to reuse one of the nodes' names. + domain name. This hostname must resolve to an IP address + reserved exclusively for this purpose. @@ -258,18 +276,6 @@ - The allows to set the hypervisor type of - the cluster. Available hypervisor types are: xen-3.0, fake and - xen-hvm3.1. The default is the xen-3.0 hypervisor. - Note that if you init the cluster with hypervisor-type - xen-hvm3.1 you also need to provide the cluster VNC password - file /etc/ganeti/vnc-cluster-password and - the HVM boot ISO image - /srv/ganeti/iso/hvm-install.iso because - instances created by the experimental HVM support require them. - - - The option will let you specify a volume group different than 'xenvg' for ganeti to use when creating instance disks. This volume group must have the same name on all nodes. Once the @@ -301,6 +307,124 @@ is initialized you can change this setup with the modify command. + + + The option allows you + set the directory to use for storing the instance disk + files when using file storage as backend for instance disks. + + + + The option allows you + to set the list of hypervisors that will be enabled for + this cluster. Instance hypervisors can only be choosen from + the list of enabled hypervisors. Currently, the following + hypervisors are available: + + + + + + xen-pvm + + + Xen PVM hypervisor + + + + + xen-hvm + + + Xen HVM hypervisor + + + + + kvm + + + Linux KVM hypervisor + + + + + fake + + + fake hypervisor for development/testing + + + + + + + + Either a single hypervisor name or a comma-separated list of + hypervisor names can be specified. If this option is not + specified, only the xen-pvm hypervisor is enabled by default. + + + + With the option, the default hypervisor + can be set. It has to be a member of the list of enabled + hypervisors. If not specified, the first entry on the list of + enabled hypervisors will be used by default. + + + + The option allows you to set + the default backend parameters for the cluster. The parameter + format is a comma-separated list of key=value pairs with the + following supported keys: + + + + + + vcpus + + + Number of VCPUs to set for an instance by default, must + be an integer, will be set to 1 if no specified. + + + + + memory + + + Amount of memory to allocate for an instance by default, + can be either an integer or an integer followed by a + unit (M for mebibytes and G for gibibytes are + supported), will be set to 128M if not specified. + + + + + auto_balance + + + Value of the auto_balance flag for instances to use by + default, will be set to true if not specified. + + + + + + + + The option allows you + to set default hypervisor specific parameters for the + cluster. The format of this option is the name of the + hypervisor, followed by a colon and a comma-separated list of + key=value pairs. The keys available for each hypervisors are + detailed int the + gnt-instance + 8 man page, in the + add command. + + @@ -330,8 +454,22 @@ modify + -g vg-name + --no-lvm-storage + + --enabled-hypervisors + hypervisors + + --hypervisor-parameters + hv-params + + --backend-parameters + be-params + + -C candidate_pool_size + @@ -339,12 +477,82 @@ - The and are + The , , + , + and + options are described in the init command. + + + The options specifies the + candidate_pool_size cluster parameter. This + is the number of nodes that the master will try to keep as + master_candidates. For more details about + this role and other node roles, see the + ganeti7 + . If you increase the size, the master will + automatically promote as many nodes as required and possible + to reach the intended number. + + + + + QUEUE + + + queue + drain + undrain + info + + + + + Change job queue properties. + + + + The option sets the drain flag on the + job queue. No new jobs will be accepted, but jobs already in + the queue will be processed. + + + + The will unset the drain flag on the + job queue. New jobs will be accepted. + + + + The option shows the properties of the + job queue. + + redist-conf + + redist-conf + --submit + + + + This command forces a full push of configuration files from + the master node to the other nodes in the cluster. This is + normally not needed, but can be run if the + verify complains about configuration + mismatches. + + + + The option is used to send the job + to the master daemon but not wait for its completion. The job + ID will be shown so that it can be examined via + gnt-job info. + + + + REMOVE-TAGS @@ -432,6 +640,7 @@ verify + --no-nplus1-mem @@ -439,6 +648,12 @@ respect to running instances, and incurs no downtime of the instances. + + + If the option is given, ganeti won't + check whether if it loses a node it can restart all the instances on + their secondaries (and report an error otherwise). +