From 48d88b48a08091340f16add2f505101948c8a9d9 Mon Sep 17 00:00:00 2001 From: Sol Jerome Date: Thu, 27 Jan 2011 09:52:28 -0600 Subject: doc: Remove references to documentation already in sphinx Signed-off-by: Sol Jerome --- doc/development/testing.txt | 20 ++++++++++++++------ doc/unsorted/index.txt | 5 ----- 2 files changed, 14 insertions(+), 11 deletions(-) diff --git a/doc/development/testing.txt b/doc/development/testing.txt index 45b1cbefc..1f0842053 100644 --- a/doc/development/testing.txt +++ b/doc/development/testing.txt @@ -32,7 +32,10 @@ Server Testing 1. Ensure that the server produces the same configurations for clients - * Before the upgrade, generate all client configurations using the buildall subcommand of bcfg2-info. This subcommand takes a directory argument; it will generate one client configuration in each file, naming each according to the client name. + * Before the upgrade, generate all client configurations using the + buildall subcommand of bcfg2-info. This subcommand takes a directory + argument; it will generate one client configuration in each file, + naming each according to the client name. .. code-block:: sh @@ -44,11 +47,16 @@ Server Testing Generated config for fs13.bgl.mcs.anl.gov in 1.47958016396 seconds ... - Take notice of any messages produced during configuration generation. These generally reflect minor issues in the configuration specification. Ideally, they should be fixed. + Take notice of any messages produced during configuration generation. + These generally reflect minor issues in the configuration specification. + Ideally, they should be fixed. * Upgrade the server software - * Generate all client configurations in a second location using the new software. Any tracebacks reflect bugs, and should be filed in the ticketing system. Any new messages should be carefully examined. - * Compare each file in the old directory to those in the new directory using ``bcfg2-admin compare -r /old/directory /new/directory`` + * Generate all client configurations in a second location using the + new software. Any tracebacks reflect bugs, and should be filed in + the ticketing system. Any new messages should be carefully examined. + * Compare each file in the old directory to those in the new directory + using ``bcfg2-admin compare -r /old/directory /new/directory`` .. code-block:: sh @@ -62,7 +70,8 @@ Server Testing ConfigFile /bin/whatami differs (in bundle softenv) Entry: login1.bgl.mcs.anl.gov.xml bad - This can be used to compare configurations for single clients, or different clients. + This can be used to compare configurations for single clients, or + different clients. 2. Compare old and new group diagrams (using ``bcfg2-admin viz``) @@ -71,4 +80,3 @@ Client Testing Run the client in dry-run and non-dry-run mode; ensure that multiple runs produce consistent results. - diff --git a/doc/unsorted/index.txt b/doc/unsorted/index.txt index 90e6b1a9d..a369ee1b3 100644 --- a/doc/unsorted/index.txt +++ b/doc/unsorted/index.txt @@ -15,14 +15,9 @@ list below. * `Plugins/Snapshots` * `PrecompiledPackages` -* `Publications` -* `QuickStart2` -* `QuickStart3` * `SchemaEvolution` * `SecurityDevPlan` * `ServerSideOverview` -* `UpgradeTesting` -* `VimSnippetSupport` .. toctree:: :maxdepth: 2 -- cgit v1.2.3-1-g7c22