Clean up implemented specs

Per discussion in the most recent Infrastructure team meeting:

http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-06-06-19.03.html

...the following specifications should be considered completed and
so are being moved into the implemented subsection of the index:

    complete-reviewable-release-automation
    ethercalc
    neutral-governance-website
    publish-election-repo
    releases-openstack-org
    shade

These specs had some parts which were not completed for various
reasons and became out of scope, so have been adjusted slightly to
stop mentioning the missing features and moved into implemented:

    deploy-stackviz
    unified_mirrors

Change-Id: Ia603a1f752e0c8acb43ed323864267c2b69bdf03

doc/source/index.rst

@@ -35,23 +35,15 @@ permits.
    :glob:
    :maxdepth: 1
 
-   specs/complete-reviewable-release-automation
    specs/deploy-ci-dashboard
-   specs/deploy-stackviz
-   specs/ethercalc
    specs/jenkins-job-builder_2.0.0-api-changes
-   specs/neutral-governance-website
    specs/nodepool-drivers
    specs/pholio
-   specs/publish-election-repo
    specs/puppet-module-functional-testing
    specs/refstack_dot_org
-   specs/releases-openstack-org
-   specs/shade
    specs/stackalytics
    specs/storyboard_worklists_boards
    specs/translation_check_site
-   specs/unified_mirrors
    specs/wiki_modernization
 
 Help Wanted
@@ -91,24 +83,32 @@ for historical purposes.
    specs/branch-automation
    specs/centralize-release-tagging
    specs/code-search
+   specs/complete-reviewable-release-automation
    specs/config-repo-split
+   specs/deploy-stackviz
    specs/dib-nodepool
    specs/doc-publishing
+   specs/ethercalc
    specs/firehose
    specs/gerrit-2.11
    specs/infra-cloud
    specs/migrate_askbot
    specs/migrate_to_zanata
+   specs/neutral-governance-website
    specs/newton-on-xenial
    specs/nodepool-workers
    specs/nodepool-zookeeper-workers
    specs/openstackci
    specs/public_hiera
+   specs/publish-election-repo
    specs/puppet-modules
+   specs/releases-openstack-org
    specs/server_base_template_refactor
+   specs/shade
    specs/test-metrics-db
    specs/translation_setup
    specs/trystack-site
+   specs/unified_mirrors
 
 Abandoned Design Specifications
 ===============================

specs/deploy-stackviz.rst

@@ -41,11 +41,11 @@ npm dependencies will be downloaded and installed, and the static site will
 be built. To accomplish this, a new Nodepool DIB element will be made for
 the creation of the repository and building of the static site.
 
-Second, copy and configure the static site on the logs server. Additional data
+Second, copy the site into logs uploaded to the logs server. Additional data
 processing at this step will include installing the python processing module
 (stackviz-export) and parsing subunit and dstat.csv logs. A configuration file
 will be generated for each patch, which will allow the developer to browse a
-Stackviz site on the logs server using their patch's data.
+Stackviz site within each set of logs using their patch's data.
 
 Alternatives
 ------------

specs/unified_mirrors.rst

@@ -25,7 +25,7 @@ hosted at the root directory of the webserver. This prevents us from reusing
 the host for different package mirrors.
 
 At the same time, there is new demand for different mirrors, including (but
-not restricted to) pypi-wheel, npm, bower, rubygems, and maven's nexus.
+not restricted to) pypi-wheel, EPEL, UCA...
 
 Proposed Change
 ===============
@@ -38,8 +38,8 @@ paths similar to the following:
 
 * http://mirror.<region>.<provider>.openstack.org/pypi
 * http://mirror.<region>.<provider>.openstack.org/wheel
-* http://mirror.<region>.<provider>.openstack.org/npm
+* http://mirror.<region>.<provider>.openstack.org/centos
-* http://mirror.<region>.<provider>.openstack.org/gem
+* http://mirror.<region>.<provider>.openstack.org/ubuntu
 
 In order to reduce the complexity and storage requirements of the
 mirror hosts, the mirror content will be written into AFS.  When
@@ -78,9 +78,8 @@ Implementation
 Assignee(s)
 -----------
 
-* Michael Krotscheck (Mirror Rename, NPM Mirror)
+* Michael Krotscheck (Mirror Rename)
 * Greg Haynes (Wheel Mirror)
-* Emilien Macchi (Ruby Mirror)
 
 Support from infra root will be required to provision servers, rsync
 packages, and update DNS records.
@@ -136,26 +135,6 @@ mirror. Goal: http://mirror.<region>.<cloud>.openstack.org/wheel
 4. Our nodepool slaves should be instructed to use the new wheel mirror in
    addition to our pypi mirror.
 
-The following work will need to be completed in order to create an npm mirror.
-Goal: http://mirror.<region>.<cloud>.openstack.org/npm
-
-1. A new npm_mirror.pp manifest should be added to mirror_update.pp,
-   to provide an npm mirror replication service (using
-   registry-static) hosted in AFS.
-2. NodeJS and NPM will be added to our nodepool slaves. This is to simplify the
-   next step.
-3. The nodepool slaves should be instructed to use the new npm mirror, where
-   necessary.
-
-The following work will need to be completed in order to create a gem mirror.
-Goal: http://mirror.<region>.<cloud>.openstack.org/gem
-
-1. A new rubygems_mirror.pp manifest should be added to
-   mirror_update.pp, to provide a rubygems replication service (using
-   rubygems-mirror) hosted in AFS.
-2. The nodepool slaves should be instructed to use the new gem mirror, where
-   necessary.
-
 Repositories
 ------------
 
@@ -197,6 +176,4 @@ Manual testing of the new mirrors should be performed before they are used.
 Dependencies
 ============
 
-This adds a dependency to the registry-static project, an npm static mirroring
+There are no dependencies.
-script. It also adds a dependency to the rubygems-mirror project, a static gem
-mirroring service.