Conform with LFN doc rules

It hugely hacks docs to move away from submodules.
https://docs.opnfv.org/en/latest/how-to-use-docs/local-build-transition.html

It removes intern reports which can't be integrated in this new model.
All wrong links now deteted are updated.

Change-Id: I9dbebeed041d2e104e3b8e73483f656ba0ef5bb9
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
(cherry picked from commit 1a22e73c850c450305764c784c86dbc067e65dae)

2 files changed, 0 insertions, 337 deletions

diff --git a/docs/testing/developer/internship/vnf_catalog/conf.py b/docs/testing/developer/internship/vnf_catalog/conf.py
deleted file mode 100644
index fe3cdb722..000000000
--- a/docs/testing/developer/internship/vnf_catalog/conf.py
+++ /dev/null
@@ -1,177 +0,0 @@
-# -*- coding: utf-8 -*-
-#
-# Open Source VNF Catalog documentation build configuration file, created by
-# sphinx-quickstart on Wed Apr  4 06:07:56 2018.
-#
-# This file is execfile()d with the current directory set to its
-# containing dir.
-#
-# Note that not all possible configuration values are present in this
-# autogenerated file.
-#
-# All configuration values have a default; values that are commented out
-# serve to show the default.
-
-# If extensions (or modules to document with autodoc) are in another directory,
-# add these directories to sys.path here. If the directory is relative to the
-# documentation root, use os.path.abspath to make it absolute, like shown here.
-#
-# import os
-# import sys
-# sys.path.insert(0, os.path.abspath('.'))
-
-# -- General configuration ------------------------------------------------
-
-# If your documentation needs a minimal Sphinx version, state it here.
-#
-# needs_sphinx = '1.0'
-
-# Add any Sphinx extension module names here, as strings. They can be
-# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
-# ones.
-extensions = []
-
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
-
-# The suffix(es) of source filenames.
-# You can specify multiple suffix as a list of string:
-#
-# source_suffix = ['.rst', '.md']
-source_suffix = '.rst'
-
-# The master toctree document.
-master_doc = 'index'
-
-# General information about the project.
-project = u'Open Source VNF Catalog'
-copyright = u'2018, Functest <opnfv-tech-discuss@lists.opnfv.org>'
-author = u'Functest <opnfv-tech-discuss@lists.opnfv.org>'
-
-# The version info for the project you're documenting, acts as replacement for
-# |version| and |release|, also used in various other places throughout the
-# built documents.
-#
-# The short X.Y version.
-version = u'master'
-# The full version, including alpha/beta/rc tags.
-release = u'master'
-
-# The language for content autogenerated by Sphinx. Refer to documentation
-# for a list of supported languages.
-#
-# This is also used if you do content translation via gettext catalogs.
-# Usually you set "language" from the command line for these cases.
-language = None
-
-# List of patterns, relative to source directory, that match files and
-# directories to ignore when looking for source files.
-# This patterns also effect to html_static_path and html_extra_path
-exclude_patterns = []
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-# If true, `todo` and `todoList` produce output, else they produce nothing.
-todo_include_todos = False
-
-
-# -- Options for HTML output ----------------------------------------------
-
-# The theme to use for HTML and HTML Help pages.  See the documentation for
-# a list of builtin themes.
-#
-html_theme = 'sphinx_rtd_theme'
-
-# Theme options are theme-specific and customize the look and feel of a theme
-# further.  For a list of options available for each theme, see the
-# documentation.
-#
-# html_theme_options = {}
-
-# Add any paths that contain custom themes here, relative to this directory.
-# html_theme_path = []
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-# html_static_path = []
-
-# Custom sidebar templates, must be a dictionary that maps document names
-# to template names.
-#
-# This is required for the alabaster theme
-# refs: http://alabaster.readthedocs.io/en/latest/installation.html#sidebars
-html_sidebars = {
-    '**': [
-        'relations.html',  # needs 'show_related': True theme option to display
-        'searchbox.html',
-    ]
-}
-
-
-# -- Options for HTMLHelp output ------------------------------------------
-
-# Output file base name for HTML help builder.
-htmlhelp_basename = 'OpenSourceVNFCatalogdoc'
-
-
-# -- Options for LaTeX output ---------------------------------------------
-
-latex_elements = {
-    # The paper size ('letterpaper' or 'a4paper').
-    #
-    # 'papersize': 'letterpaper',
-
-    # The font size ('10pt', '11pt' or '12pt').
-    #
-    # 'pointsize': '10pt',
-
-    # Additional stuff for the LaTeX preamble.
-    #
-    # 'preamble': '',
-
-    # Latex figure (float) alignment
-    #
-    # 'figure_align': 'htbp',
-}
-
-# Grouping the document tree into LaTeX files. List of tuples
-# (source start file, target name, title,
-#  author, documentclass [howto, manual, or own class]).
-latex_documents = [
-    (master_doc,
-     'OpenSourceVNFCatalog.tex',
-     u'Open Source VNF Catalog Documentation',
-     u'Functest \\textless{}opnfv-tech-discuss@lists.opnfv.org\\textgreater{}',
-     'manual'),
-]
-
-
-# -- Options for manual page output ---------------------------------------
-
-# One entry per manual page. List of tuples
-# (source start file, name, description, authors, manual section).
-man_pages = [
-    (master_doc,
-     'opensourcevnfcatalog',
-     u'Open Source VNF Catalog Documentation',
-     [author],
-     1)
-]
-
-
-# -- Options for Texinfo output -------------------------------------------
-
-# Grouping the document tree into Texinfo files. List of tuples
-# (source start file, target name, title, author,
-#  dir menu entry, description, category)
-texinfo_documents = [
-    (master_doc,
-     'OpenSourceVNFCatalog',
-     u'Open Source VNF Catalog Documentation',
-     author,
-     'OpenSourceVNFCatalog',
-     'One line description of project.',
-     'Miscellaneous'),
-]
diff --git a/docs/testing/developer/internship/vnf_catalog/index.rst b/docs/testing/developer/internship/vnf_catalog/index.rst
deleted file mode 100644
index 634b728bd..000000000
--- a/docs/testing/developer/internship/vnf_catalog/index.rst
+++ /dev/null
@@ -1,160 +0,0 @@
-.. SPDX-License-Identifier: CC-BY-4.0
-
-=======================
-Open Source VNF Catalog
-=======================
-
-Author: Kumar Rishabh
-Mentors: B.Souville, M.Richomme, J.Lausuch
-
-Abstract
-========
-
-
-
-Version hissory
-===============
-
-+------------+----------+------------------+------------------------+
-| **Date**   | **Ver.** | **Author**       | **Comment**            |
-|            |          |                  |                        |
-+------------+----------+------------------+------------------------+
-| 2016-12-12 | 0.0.1    | Morgan Richomme  | Beginning of the       |
-|            |          | (Orange)         | Internship             |
-+------------+----------+------------------+------------------------+
-
-
-Overview:
-=========
-
-
-This project aims to create an Open Source catalog for reference and
-classification of Virtual Network Functions (VNFs)s available on
-Internet. The classification method proposed will be in sync with the
-requirements of Telcos active in NFV landscape. The project aims to have
-running web platform similar to [1] by the mid of internship (2nd week
-of March). By the penultimate month of internship I aim to have fully
-functional implementation of an Open Source VNF in functest.
-
-
-Problem Statement:
-------------------
-
-OPNFV aims to be the reference platform for development,
-standardization and integration of Open Source NFV components across
-various Open Source Platforms. It mainly deals with the infrastructure
-through the Network Function Virtualization Infrastructure (NFVI) and
-Virtual Infrastructure manager (VIM). The MANO (Management and
-orchestration) stacks have been introduced recently. VNFs are not
-directly in OPNFV scope, however VNFs are needed to test and qualify the
-infrastructure. In this regard having a common curated Open Source
-Reference VNF catalog would be of immense importance to community.
-
-Since major focus of OPNFV is Telcos, a curated platform targeted from
-industry point of view would be very useful. We plan to divide the
-entire project into three major phases(with some iterative improvements
-and overlaps)
-
-
-Curation Phase
---------------
-This phase pertains to studying various Open Source VNFs available and
-classification of them based on certain parameters. The parameters that
-I currently have in mind are:
-
- * Developer Metrics: These pertain to repo characteristics of VNF under
-   study
- * Usage Statistics - Activity, Number of Commits, stars
- * Maturity Statistics - For instance if an NFV community decides code
-   coverage is important for them, it shows the NFV community is serious
-   about taking the project forward
- * Technical Tagging: These are the tags that pertain to technical
-   characteristics of a VNF
- * Broad Use Cases - Whether the VNF fits strictly in IaaS, PaaS or
-   SaaS layer or is an hybrid of two/all.
- * Generic Use Cases - This in my opinion is the broadest
-   classification category. For instance a VNF could be built with a
-   broad idea of powering IOT devices at home or from usage perspective
-   of Telco Operators (vFW, vEPC, vIMS, vCDN, vAAA, vCPE,...).`[2]`_
- * Fields of Application
- * Library Status - Whether APIs are standardized, support RESTful
-   services.
- * Dependency Forwarding Graph - This is pretty complex tagging
-   mechanism. It essentially tries to establish a graph relationship
-   between the VNFs (elementary VNFs are used in Service Function
-   Chaining chains such as Firewall, DPI, content enrichment,..). In my
-   opinion this is useful immensely. This will allow users to go to
-   platform and ask a question like - “I have this X tech stack to
-   support, Y and Z are my use cases, which NFVs should I use to support
-   this.
- * Visitor Score - Based on `[1]`_ I plan to evolve a visitor score for
-   the platform. This will allow users to score an NFV on certain
-   parameters, may be post comments.
-
-**I plan to use the above three scores and evolve cumulative score which
-will be displayed next to each of the NFV on the platform.**
-
- * Platform building phase - This will involve erecting a Web Platform
-   which will be similar to this  `[1]`_. I am decently familiar with
-   Django and hence I will write the platform in Django. There are two
-   action plans that I have in mind right now. Either I can start writing
-   the platform simultaneously which will help keep track of my progress
-   or I can write the platform after 1.5 - 2 months into the internship.
-   Either way I aim to have the Web Platform ready by March 12.
- * Functest VNF implementation phase - This is the last phase that will
-   involve writing a fully functional implementation of an Open Source VNF
-   into Functest. I will undertake this after I am 3 months into the
-   internship. I have a decent familiarity with python and hence I think
-   it shouldn’t be too difficult. I need to decide how complex the VNFI
-   should undertake this exercise for (e.g. AAA such as free radius sounds
-   relatively easy, vCDN is much more challenging).
-   This will be decided in consent with my mentors.
-
-Schedule:
-=========
-I plan to take this project in 6 months time frame as I want to use it
-as a chance to read more about NFVs in particular and SDN in general
-
-
-+--------------------------+------------------------------------------+
-| **Date**                 | **Comment**                              |
-|                          |                                          |
-+--------------------------+------------------------------------------+
-| December 12 - January 12 | Study the above mentioned metrics        |
-|                          | Decide which of them are important for   |
-|                          | community (and which are not).           |
-+--------------------------+------------------------------------------+
-| January 12 - January 27  | Make a database for the above studied    |
-|                          | metrics and evolve it further based on   |
-|                          | Mentors’ input. + associated API         |
-+--------------------------+------------------------------------------+
-| January 27 - February 5  | Compile the data collected above and make|
-|                          | it public. Although I can keep everything|
-|                          | public from the beginning too. My        |
-|                          | rationale of not making the entire data  |
-|                          | public in initial stage as the errors    |
-|                          | caused by me could be misleading for     |
-|                          | developers.                              |
-+--------------------------+------------------------------------------+
-| February 5 - March 5     | Erect the Web Platform and release it    |
-|                          | for restricted group for alpha testing.  |
-+--------------------------+------------------------------------------+
-| March 5 - March 12       | Make it public. Release it to public for |
-|                          | beta testing. Fix Bugs.                  |
-+--------------------------+------------------------------------------+
-| March 12 - April 12      | Start working on implementation of an    |
-|                          | Open Source VNF in Functest.             |
-+--------------------------+------------------------------------------+
-| April 12 - May 12        | I will decided what to do here based on  |
-|                          | discussion with mentors.                 |
-+--------------------------+------------------------------------------+
-
-
-References:
-===========
-
-.. _`[1]` : Openhub: https://www.openhub.net/explore/projects
-
-.. _`[2]` : ETSI NFV White Paper: https://portal.etsi.org/Portals/0/TBpages/NFV/Docs/NFV_White_Paper3.pdf
-
-.. _`[3]` : https://wiki.opnfv.org/display/DEV/Intern+Project%3A+Open+Source+VNF+catalog