Update to new OPNFV Docs structure

JIRA: MODELS-2

Change-Id: I5d5601849803cf017bab882dc6eba931637b0770
Signed-off-by: Aimee Ukasick <aimeeu.opensource@gmail.com>

1 files changed, 0 insertions, 53 deletions

diff --git a/docs/design/definitions.rst b/docs/design/definitions.rst
deleted file mode 100644
index 426abda..0000000
--- a/docs/design/definitions.rst
+++ /dev/null
@@ -1,53 +0,0 @@
-.. This work is licensed under a
-.. Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) 2015-2017 AT&T Intellectual Property, Inc
-
-Definitions
-===========
-.. list-table:: Definitions
-   :widths: 15 85
-   :header-rows: 1
-
-   * - Term
-     - Meaning
-
-   * - State
-     - Information that can be used to convey or imply the state of something, e.g. an application, resource, entity, etc. This can include data held inside OPNFV components, "events" that have occurred.
-
-   * - YANG
-     - A data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol  (NETCONF), NETCONF remote procedure calls, and NETCONF notifications.
-
-
-Abbreviations
-=============
-.. list-table:: Abbreviations
-   :widths: 15 85
-   :header-rows: 1
-
-   * - Term
-     - Meaning
-
-   * - CRUD
-     - Create, Read, Update, Delete (database operation types)
-
-   * - FCAPS
-     - Fault, Configuration, Accounting, Performance, Security
-
-   * - NF
-     - Network Function
-
-   * - SFC
-     - Service Function Chaining
-
-   * - VNF
-     - Virtual Network Function
-
-   * - NFVI
-     - Network Function Virtualization Infrastructure
-
-   * - TOSCA
-     - Topology and Orchestration Specification for Cloud Applications
-
-   * - NETCONF
-     - Network Configuration Protocol