Merge "Updating the summary file"
diff --git a/SUMMARY.md b/SUMMARY.md
index 0a270ce..20c4ea7 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -80,7 +80,7 @@
* Operate
* [Disable/Enable an ONU](profiles/seba/operate/onu-ops.md)
* [Edit a Whitelist entry](profiles/seba/operate/whitelist-ops.md)
- * [Disable/Delete an OLT](profiles/seba/operate/olt-ops.md)
+ * [Delete an OLT](profiles/seba/operate/olt-ops.md)
* [Fix configuration errors](profiles/seba/operate/config-ops.md)
* [Add a cross-connect in the AGG switch](profiles/seba/operate/agg-ops.md)
* [Try a new version of *](profiles/seba/operate/k8s-helm-ops.md)
diff --git a/images/gui.png b/images/gui.png
new file mode 100644
index 0000000..4057a1c
--- /dev/null
+++ b/images/gui.png
Binary files differ
diff --git a/operating_cord/gui.md b/operating_cord/gui.md
index 6a5db25..cf46522 100644
--- a/operating_cord/gui.md
+++ b/operating_cord/gui.md
@@ -35,3 +35,16 @@
```
This command opens the GUI in your default browser.
+
+## Using the GUI
+
+The GUI lets you explore the data model and gives immediate feedback on the state
+of the system through real time notifications.
+
+Some basic features:
+
+1. **Navigation**: Each item represent a service, click on it to see a list of models in that service
+2. **Search Box**: Full text search in the data model. Can't find something? Here's a good place to start from
+3. **Service Status**: Reports the status of each service and it's current version.
+
+
diff --git a/profiles/seba/operate/olt-ops.md b/profiles/seba/operate/olt-ops.md
index a4317c1..e54fd95 100644
--- a/profiles/seba/operate/olt-ops.md
+++ b/profiles/seba/operate/olt-ops.md
@@ -1 +1,32 @@
# OLT Operations
+
+For information on how to add an OLT, please refere to the
+[POD specific configuration](../configuration.md#olt-provisioning) page.
+
+## Remove on OLT
+
+In order to remove the OLT it is mandatory that no active subscribers are using it.
+
+You have two options:
+
+- [removing the subscribers](./olt-ops.md#remove-subscriber)
+- [changing their state to pre-provisioned](./olt-ops.md#change-subscriber-status)
+
+once the subscribers are gone you can navigate to `vOLT -> OLT Devices` and remove
+the device by clicking on the red `X` icon on the left side of the table.
+
+
+
+### Remove subscriber
+
+To remove a subscriber just visit `RCORD -> RCORD Subscribers` and click on the
+red `X` icon on the left side of the table.
+
+
+
+### Change subscriber status
+
+To change the Subscriber status, go to `RCORD -> RCORD Subscribers` and enter the
+detail view by clicking on the magnifier icon. Then change its state to `Pre Provisioned`
+
+
\ No newline at end of file
diff --git a/profiles/seba/operate/onu-ops.md b/profiles/seba/operate/onu-ops.md
index 6186438..a54b73e 100644
--- a/profiles/seba/operate/onu-ops.md
+++ b/profiles/seba/operate/onu-ops.md
@@ -1 +1,17 @@
# ONU Operations
+
+ONUs can be managed from the corresponding view in XOS,
+it is located under `vOLT -> ONU Devices`
+
+
+
+From this view you can view all the ONUs known to the system, remove them or go
+to the details page (clicking on the magnifier icon)
+
+## Enable/Disable an ONU
+
+Once you are in the ONU details view, you can just change it's `Admin State`
+to enable or disable the device.
+
+
+
diff --git a/profiles/seba/operate/screenshots/olt_table_view.png b/profiles/seba/operate/screenshots/olt_table_view.png
new file mode 100644
index 0000000..0d32958
--- /dev/null
+++ b/profiles/seba/operate/screenshots/olt_table_view.png
Binary files differ
diff --git a/profiles/seba/operate/screenshots/onu_detail_view.png b/profiles/seba/operate/screenshots/onu_detail_view.png
new file mode 100644
index 0000000..de205fb
--- /dev/null
+++ b/profiles/seba/operate/screenshots/onu_detail_view.png
Binary files differ
diff --git a/profiles/seba/operate/screenshots/onu_table_view.png b/profiles/seba/operate/screenshots/onu_table_view.png
new file mode 100644
index 0000000..40744db
--- /dev/null
+++ b/profiles/seba/operate/screenshots/onu_table_view.png
Binary files differ
diff --git a/profiles/seba/operate/screenshots/subscribers_detail_view.png b/profiles/seba/operate/screenshots/subscribers_detail_view.png
new file mode 100644
index 0000000..a5ac219
--- /dev/null
+++ b/profiles/seba/operate/screenshots/subscribers_detail_view.png
Binary files differ
diff --git a/profiles/seba/operate/screenshots/subscribers_table_view.png b/profiles/seba/operate/screenshots/subscribers_table_view.png
new file mode 100644
index 0000000..95e0073
--- /dev/null
+++ b/profiles/seba/operate/screenshots/subscribers_table_view.png
Binary files differ
diff --git a/profiles/seba/operate/screenshots/whitelist_table_view.png b/profiles/seba/operate/screenshots/whitelist_table_view.png
new file mode 100644
index 0000000..a55f6d7
--- /dev/null
+++ b/profiles/seba/operate/screenshots/whitelist_table_view.png
Binary files differ
diff --git a/profiles/seba/operate/whitelist-ops.md b/profiles/seba/operate/whitelist-ops.md
index c1335fe..54ffbc4 100644
--- a/profiles/seba/operate/whitelist-ops.md
+++ b/profiles/seba/operate/whitelist-ops.md
@@ -1 +1,11 @@
# Whitelist Operations
+
+The whitelist entries can be removed and modified from this page.
+
+`Att Workflow Driver -> ONU Whitelist`
+
+
+
+For more information about the whitelist, please refer to the
+[Configure AT&T workflow](../workflows/att-configure.md#whitelist-population) page.
+
diff --git a/profiles/seba/workflows/att-configure.md b/profiles/seba/workflows/att-configure.md
index 056c2c9..4426858 100644
--- a/profiles/seba/workflows/att-configure.md
+++ b/profiles/seba/workflows/att-configure.md
@@ -1,10 +1,13 @@
# Configure AT&T Workflow
-We assume your POD is already configured as per[this instructions](../configuration.md)
+We assume your POD is already configured as per [this instructions](../configuration.md)
(you need to complete only the first section)
## Whitelist population
+> NOTE: the whitelist can be populated at any time.
+> It doesn't need to be done upfront.
+
To configure the ONU whitelist, you can use this TOSCA:
```yaml
@@ -37,74 +40,30 @@
For instructions on how to push TOSCA into a CORD POD, please
refer to this [guide](../../../xos-tosca/README.md).
-## Pre-provision subscribers
+### Where to find the required informations
-You can `pre-provision` subscribers using this TOSCA:
+#### Serial Number
-```yaml
-tosca_definitions_version: tosca_simple_yaml_1_0
-imports:
- - custom_types/rcordsubscriber.yaml
+To locate the ONU serial number you can open the ONU detail view (`vOLT -> ONU Devices`).
-description: Pre-provsion a subscriber
+
-topology_template:
- node_templates:
+> NOTE: most of the time the serial number is also printed on the physical device.
- # Pre-provision the subscriber the subscriber
- my_house:
- type: tosca.nodes.RCORDSubscriber
- properties:
- name: My House
- status: pre-provisioned
- c_tag: 111
- onu_device: BRCM22222222
- nas_port_id : "PON 1/1/03/1:1.1.1"
- circuit_id: foo
-```
+#### Pon Port ID
-For instructions on how to push TOSCA into a CORD POD, please
-refer to this [guide](../../../xos-tosca/README.md).
+The `pon_port_id` can be found from the ONU detail view, by selecting the `PON Port`
+tab:
-## OLT Activation
+
-Once the system knows about whitelisted ONUs and subscribers,
-you can activate the OLT:
+#### Device ID
-```yaml
-tosca_definitions_version: tosca_simple_yaml_1_0
-imports:
- - custom_types/oltdevice.yaml
- - custom_types/voltservice.yaml
-description: Create a simulated OLT Device in VOLTHA
-topology_template:
- node_templates:
+The `device_id` can easily be found in the OLT list view. Note the `device_id` is
+the openflow ID of the logical device exposed to ONOS, and not the serial number
+of the device.
- service#volt:
- type: tosca.nodes.VOLTService
- properties:
- name: volt
- must-exist: true
-
- olt_device:
- type: tosca.nodes.OLTDevice
- properties:
- name: ONF OLT
- device_type: openolt
- host: 10.90.0.114
- port: 9191
- switch_datapath_id: of:0000000000000001
- switch_port: "1"
- outer_tpid: "0x8100"
- uplink: "128"
- requirements:
- - volt_service:
- node: service#volt
- relationship: tosca.relationships.BelongsToOne
-```
-
-For instructions on how to push TOSCA into a CORD POD, please
-refer to this [guide](../../../xos-tosca/README.md).
+
## Device monitoring
diff --git a/profiles/seba/workflows/screenshots/olt_device_id.png b/profiles/seba/workflows/screenshots/olt_device_id.png
new file mode 100644
index 0000000..3e004ec
--- /dev/null
+++ b/profiles/seba/workflows/screenshots/olt_device_id.png
Binary files differ
diff --git a/profiles/seba/workflows/screenshots/onu_sn.png b/profiles/seba/workflows/screenshots/onu_sn.png
new file mode 100644
index 0000000..878e180
--- /dev/null
+++ b/profiles/seba/workflows/screenshots/onu_sn.png
Binary files differ
diff --git a/profiles/seba/workflows/screenshots/pon_port.png b/profiles/seba/workflows/screenshots/pon_port.png
new file mode 100644
index 0000000..4263d59
--- /dev/null
+++ b/profiles/seba/workflows/screenshots/pon_port.png
Binary files differ
