From f2b694b7abc5332adb6b5fe356e1c1bfb1a90f94 Mon Sep 17 00:00:00 2001 From: Cory Wright Date: 2010年8月13日 11:19:43 -0400 Subject: [PATCH] Fixed a few typos in the deployment guide (s/ring_builder/ring-builder/g) --- bin/swift-ring-builder | 24 ++++++++++++------------ doc/source/deployment_guide.rst | 8 ++++---- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/bin/swift-ring-builder b/bin/swift-ring-builder index 6c12fb582e..877590da2e 100755 --- a/bin/swift-ring-builder +++ b/bin/swift-ring-builder @@ -111,28 +111,28 @@ SEARCH_VALUE_HELP = ''' '''.strip() CREATE_HELP = ''' -ring_builder create +swift-ring-builder create Creates with 2^ partitions and . is number of hours to restrict moving a partition more than once. '''.strip() SEARCH_HELP = ''' -ring_builder search +swift-ring-builder search Shows information about matching devices. %(SEARCH_VALUE_HELP)s '''.strip() % globals() ADD_HELP = ''' -ring_builder add z-:/_ +swift-ring-builder add z-:/_ Adds a device to the ring with the given information. No partitions will be assigned to the new device until after running 'rebalance'. This is so you can make multiple device changes and rebalance them all just once. '''.strip() SET_WEIGHT_HELP = ''' -ring_builder set_weight +swift-ring-builder set_weight Resets the device's weight. No partitions will be reassigned to or from the device until after running 'rebalance'. This is so you can make multiple device changes and rebalance them all just once. @@ -141,7 +141,7 @@ ring_builder set_weight '''.strip() % globals() SET_INFO_HELP = ''' -ring_builder set_info +swift-ring-builder set_info :/_ Resets the device's information. This information isn't used to assign partitions, so you can use 'write_ring' afterward to rewrite the current @@ -154,7 +154,7 @@ ring_builder set_info '''.strip() % globals() REMOVE_HELP = ''' -ring_builder remove +swift-ring-builder remove Removes the device(s) from the ring. This should normally just be used for a device that has failed. For a device you wish to decommission, it's best to set its weight to 0, wait for it to drain all its data, then use this @@ -166,7 +166,7 @@ ring_builder remove '''.strip() % globals() SET_MIN_PART_HOURS_HELP = ''' -ring_builder set_min_part_hours +swift-ring-builder set_min_part_hours Changes the to the given . This should be set to however long a full replication/update cycle takes. We're working on a way to determine this more easily than scanning logs. @@ -176,11 +176,11 @@ ring_builder set_min_part_hours if __name__ == '__main__': if len(argv) < 2: print ''' -ring_builder %(MAJOR_VERSION)s.%(MINOR_VERSION)s +swift-ring-builder %(MAJOR_VERSION)s.%(MINOR_VERSION)s %(CREATE_HELP)s -ring_builder +swift-ring-builder Shows information about the ring and the devices within. %(SEARCH_HELP)s @@ -193,14 +193,14 @@ ring_builder %(REMOVE_HELP)s -ring_builder rebalance +swift-ring-builder rebalance Attempts to rebalance the ring by reassigning partitions that haven't been recently reassigned. -ring_builder validate +swift-ring-builder validate Just runs the validation routines on the ring. -ring_builder write_ring +swift-ring-builder write_ring Just rewrites the distributable ring file. This is done automatically after a successful rebalance, so really this is only useful after one or more 'set_info' calls when no rebalance is needed but you want to send out the diff --git a/doc/source/deployment_guide.rst b/doc/source/deployment_guide.rst index d1453f9ef3..8c222b18ac 100644 --- a/doc/source/deployment_guide.rst +++ b/doc/source/deployment_guide.rst @@ -92,7 +92,7 @@ by number, beginning with 1. You can now start building the ring with:: - swift-ring_builder create + swift-ring-builder create This will start the ring build process creating the with 2^ partitions. is the time in hours before a @@ -100,7 +100,7 @@ specific partition can be moved in succession (24 is a good value for this). Devices can be added to the ring with:: - swift-ring_builder add z-:/_ + swift-ring-builder add z-:/_ This will add a device to the ring where is the name of the builder file that was created previously, is the number of the zone @@ -114,7 +114,7 @@ Add each device that will be initially in the cluster. Once all of the devices are added to the ring, run:: - swift_ring_builder rebalance + swift-ring-builder rebalance This will distribute the partitions across the drives in the ring. It is important whenever making changes to the ring to make all the changes @@ -126,7 +126,7 @@ The above process should be done to make a ring for each storage serivce changes to the ring, so it is very important that these be kept and backed up. The resulting .tar.gz ring file should be pushed to all of the servers in the cluster. For more information about building rings, running -swift_ring_builder with no options will display help text with available +swift-ring-builder with no options will display help text with available commands and options. More information on how the ring works internally can be found in the :doc:`Ring Overview `.

AltStyle によって変換されたページ (->オリジナル) /