[SEBA-994] Add BNGPORTMapping Synchronization workflow in fabric-crossconnect documentation
Change-Id: Ibdc14c9c364e38d5537d0a95d0fe7ba3e1cf5111
diff --git a/VERSION b/VERSION
index e9307ca..50ffc5a 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-2.0.2
+2.0.3
diff --git a/docs/README.md b/docs/README.md
index 39afecc..803564b 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -18,6 +18,7 @@
- `BNGPortMapping` represents the other half of a vlan crossconnect. Fields include the following:
- `s_tag` the vlan_id that will be connected. In addition to specifying a single vlan_id, the keyword `ANY` may be used, or a range (`123-456`) may be used.
- `switch_port` port number on the switch
+ - `old_s_tag` Field for tracking old s-tag of bngportmapping instance
`FabricCrossconnectServiceInstance` and `BNGPortMapping` work together to create the vlan crossconnect tuple, linked by a common `s-tag`.
@@ -85,7 +86,7 @@
### BNGPortMapping
-No specific processing is performed if a `BNGPortMapping` is created, updated, or deleted, as the workflow is driven by `FabricCrossconnectServiceInstance`. Responding to changes in `BNGPortMapping` is future work. For now it is suggested that if you need to change one, afterward you touch any `FabricCrossconnectServiceInstance` that may be affected, causing them to resynchronize.
+When a `BNGPortMapping` is created, updated, or deleted, the synchronizer will make a REST API call to ONOS. Appropriate xconnects are removed from ONOS and parallely new bng data and rules are pushed to ONOS.
### Event Steps