Fix a node name vs. UUID bug in instance import

[ganeti-local] / doc / walkthrough.rst

diff --git a/doc/walkthrough.rst b/doc/walkthrough.rst
index 6bbe9c5..9a6317e 100644 (file)
--- a/doc/walkthrough.rst
+++ b/doc/walkthrough.rst
@@ -16,8 +16,8 @@ a step-by-step example to managing instances and the cluster.
 
 Our simulated, example cluster will have three machines, named
 ``node1``, ``node2``, ``node3``. Note that in real life machines will
-usually FQDNs but here we use short names for brevity. We will use a
-secondary network for replication data, ``192.0.2.0/24``, with nodes
+usually have FQDNs but here we use short names for brevity. We will use
+a secondary network for replication data, ``192.0.2.0/24``, with nodes
 having the last octet the same as their index. The cluster name will be
 ``example-cluster``. All nodes have the same simulated hardware
 configuration, two disks of 750GB, 32GB of memory and 4 CPUs.
@@ -274,7 +274,7 @@ Creation
 At this point, Ganeti and the hardware seems to be functioning
 correctly, so we'll follow up with creating the instances manually::
 
-  $ gnt-instance add -t drbd -o debootstrap -s %256m% -n %node1%:%node2% %instance3%
+  $ gnt-instance add -t drbd -o debootstrap -s %256m% %instance3%
   Mon Oct 26 04:06:52 2009  - INFO: Selected nodes for instance instance1 via iallocator hail: node2, node3
   Mon Oct 26 04:06:53 2009 * creating instance disks...
   Mon Oct 26 04:06:57 2009 adding instance instance1 to cluster config
@@ -418,7 +418,7 @@ to it anymore::
 
 And now we can failover the instance::
 
-  $ gnt-instance failover --ignore-consistency %instance4%
+  $ gnt-instance failover %instance4%
   Failover will happen to image instance4. This requires a shutdown of
   the instance. Continue?
   y/[n]/?: %y%