Remove irrelevant sections from COE spec

Some of the initial design proposals were changed
during the implementation phase, making
respective edits to the spec to align to the
same.

Change-Id: Ib3d9d0f688b121a883558c3dca66e0b4c7191a43
Signed-off-by: Faseela K <faseela.k@ericsson.com>

diff --git a/docs/specs/oxygen/coe-integration.rst b/docs/specs/oxygen/coe-integration.rst
index c512407d165a64e6a4939d93a22479294d30087c..5f1bd97a6e1b847e831c9b7d01ba2d78b47c33df 100644 (file)
--- a/docs/specs/oxygen/coe-integration.rst
+++ b/docs/specs/oxygen/coe-integration.rst
@@ -54,13 +54,6 @@ converting the COE related constructs to Netvirt constructs.
 Netvirt Changes
 ---------------
 
-DHCP Module
-^^^^^^^^^^^
-
-COE will be using DHCP dynamic allocation feature in Netvirt, which has some missing parts
-for the integration to work. DHCP module's bind service logic so far works only for neutron ports.
-This has to be enhanced to work for k8s pods as well.
-
 ARP Responder
 ^^^^^^^^^^^^^
 
@@ -135,13 +128,6 @@ No pipeline changes will be introduced as part of this feature.
 Workflow
 --------
 
-Configure DHCP Pool(Optional)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-#. netvirt/dhcpmanager: For an immediate solution, a flat dhcp pool will be precreated
-   manually, and IPs will be allocated for PODs from this pool.
-#. netvirt/dhcpmanager: For an immediate solution, a flat service pool will be precreated
-   manually, and IPs will be allocated for SERVICEs from this pool.
-
 Create Pod
 ^^^^^^^^^^
 #. coe/coe-northbound: User created a POD
@@ -162,18 +148,6 @@ Create Pod
 #. netvirt/vpnmanager: Whenever interface-state is created, vpnmanager will take care of
    populating all L3 related flows in OVS.
 
-Create Service
-^^^^^^^^^^^^^^
-
-#. netvirt/coe: When a pod is attached to a service, floating-ip-info has to be populated
-#. netvirt/natmanager: Listens on floating-ip-changes and do the NATing as it is done currently.
-
-Delete Service
-^^^^^^^^^^^^^^
-
-#. netvirt/coe: When a pod is removed from a service, corresponding floating-ip-info will be removed.
-#. netvirt/natmanager: Listens on floating-ip-changes and remove the NAT rules approporiately.
-
 Delete Pod
 ^^^^^^^^^^
 
@@ -245,31 +219,6 @@ This feature add the below new feature :
 REST API
 --------
 
-Creating DHCP Pool
-^^^^^^^^^^^^^^^^^^
-
-**URL:** restconf/config/dhcp_allocation_pool:dhcp_allocation_pool/
-
-**Sample JSON data**
-
-.. code-block:: json
-
-  {
-    "dhcp_allocation_pool:network": [
-     {
-        "dhcp_allocation_pool:allocation-pool": [
-          {
-            "dhcp_allocation_pool:subnet": "192.168.10.0/24",
-            "dhcp_allocation_pool:allocate-to": "192.168.10.50",
-            "dhcp_allocation_pool:gateway": "192.168.10.2",
-            "dhcp_allocation_pool:allocate-from": "192.168.10.3"
-           }
-        ],
-        "dhcp_allocation_pool:network-id": "pod-namespace"
-      }
-    ]
-  }
-
 Creating POD directly in COE
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -297,29 +246,6 @@ Creating POD directly in COE
     ]
   }
 
-Creating SERVICE directly in COE
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-**URL:** restconf/config/service:service-information
-
-**Sample JSON data**
-
-.. code-block:: json
-
-  {
-    "service:service-information": {
-      "service:services": [
-        {
-          "service:uid": "EeafFFB7-D9Fc-aAeD-FBc9-8Af8BFaacDD9",
-          "service:cluster-ip-address": "5.21.5.0",
-          "service:endpoints": [
-            "AFbcF0EB-Fc3f-acea-A438-5CFDfCEfbcb0"
-          ]
-        }
-      ]
-    }
-  }
-
 Assignee(s)
 -----------
 
@@ -346,9 +272,8 @@ Junits
 This feature will support following use cases:
 
 * TC 1: Create a POD within a node under a namespace
-* TC 2: Attach a POD to service
-* TC 3: Remove a POD from service
-* TC 4: Delete a POD from a namespace
+* TC 2: Delete a POD from a namespace
+* TC 3: All pods under the same namespace should be able to communicate with each other
 
 CSIT
 ----