commit	95142d5167993ab4ab6fbdd4ff01639b285b1c52	[log] [tgz]
author	nikesh.krishnan <nikesh.krishnan@radisys.com>	Fri Feb 24 15:32:11 2023 +0530
committer	Mahir Gunyel <mahir.gunyel@netsia.com>	Wed Mar 08 19:33:37 2023 +0000
tree	4b0f85065baa68c4503183b3a198b9232e487928
parent	9a0ed007e78504375cc4b507aaf794318d91b8ea [diff]

go routines removed but writing to kafka is still done via go routines




<Please press edit button to view in proper formatting>
The go routines related to port , device , transition state and kafka writing was removed from the voltha core and the PONC scale test performance was compared with the voltha core keeping the go routines intact.
The tests were carried out for an average of 5 runs with :
NUM_OLTS=6
NUM_ONUS_PER_PON=32
STACK_COUNT=1
NUM_PON_PORTS=16
The table below shows the performance in different cases:


| Test suite                            | with go routine                                          | without go routine(only port and device op goroutine removed) | without go routine(port and device op go routine removed,tansition state processing,kafka writing is in go routine) | without go routine(port and device operation ,transition state processing and kafka writing go routine removed) | without go routine(port and device op and tansition state processing go routine removed ,only kafka writing is in go routine) |
|---------------------------------------|----------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
|                                       |                                                          |                                                               |                                                                                                                     |                                                                                                                 |                                                                                                                               |
| vOLTHA Scale Test                     | 04 minutes : 36 seconds : 957.5999999999767 milliseconds | 04 minutes : 30 seconds : 233.79999999998836 milliseconds     | 04 minutes : 33 seconds : 859.5999999999767 milliseconds                                                            | 05 minutes : 47 seconds : 175.20000000001164 milliseconds                                                       | 04 minutes : 34 seconds : 200 milliseconds                                                                                    |
| vOLTHA Scale Test.Activate OLTs       | 02 minutes : 15 seconds : 440.3999999999942 milliseconds | 02 minutes : 02 seconds : 861.8000000000029 milliseconds      | 02 minutes : 12 seconds : 925.6000000000058 milliseconds                                                            | 02 minutes : 16 seconds : 199.39999999999418 milliseconds                                                       | 02 minutes : 11 seconds : 800 milliseconds<br/>                                                                               |
| vOLTHA Scale Test.Onos Checks         | 11 seconds : 191.39999999999964 milliseconds             | 10 seconds : 976.3999999999996 milliseconds                   | 11 seconds : 552.6000000000004 milliseconds                                                                         | 10 seconds : 826.3999999999996 milliseconds                                                                     | 12 seconds : 00 milliseconds                                                                                                  |
| vOLTHA Scale Test.Activate Onus       | 02 minutes : 10 seconds : 314.1999999999971 milliseconds | 02 minutes : 07 seconds : 102.80000000000291 milliseconds     | 02 minutes : 09 seconds : 381.3999999999942 milliseconds                                                            | 03 minutes : 20 seconds : 149.39999999999418 milliseconds                                                       | 02 minutes : 11 seconds : 00 milliseconds                                                                                     |
| vOLTHA Scale Test.Activate Onus.Scale | 02 minutes : 09 seconds : 207 milliseconds               | 02 minutes : 06 seconds : 858.8000000000029 milliseconds      | 02 minutes : 07 seconds : 153 milliseconds                                                                          | 03 minutes : 17 seconds : 63 milliseconds                                                                       | 02 minutes : 08 seconds : 400 milliseconds<br/>                                                                               |

Change-Id: I7a7ed75be37065094c2f6b3524101e76a6a795ea

9 files changed

tree: 4b0f85065baa68c4503183b3a198b9232e487928

README.md

VOLTHA

What is Voltha?

Voltha aims to provide a layer of abstraction on top of legacy and next generation access network equipment for the purpose of control and management. Its initial focus is on PON (GPON, EPON, NG PON 2), but it aims to go beyond to eventually cover other access technologies (xDSL, Docsis, G.FAST, dedicated Ethernet, fixed wireless).

Key concepts of Voltha:

Network as a Switch: It makes a set of connected access network devices to look like a(n abstract) programmable flow device, a L2/L3/L4 switch. Examples:
- PON as a Switch
- PON + access backhaul as a Switch
- xDSL service as a Switch
Evolution to virtualization: it can work with a variety of (access) network technologies and devices, including legacy, fully virtualized (in the sense of separation of hardware and software), and in between. Voltha can run on a decice, on general purpose servers in the central office, or in data centers.
Unified OAM abstraction: it provides unified, vendor- and technology agnostic handling of device management tasks, such as service lifecycle, device lifecycle (including discovery, upgrade), system monitoring, alarms, troubleshooting, security, etc.
Cloud/DevOps bridge to modernization: it does all above while also treating the abstracted network functions as software services manageable much like other software components in the cloud, i.e., containers.

Why Voltha?

Control and management in the access network space is a mess. Each access technology brings its own bag of protocols, and on top of that vendors have their own interpretation/extension of the same standards. Compounding the problem is that these vendor- and technology specific differences ooze way up into the centralized OSS systems of the service provider, creating a lot of inefficiencies.

Ideally, all vendor equipment for the same access technology should provide an identical interface for control and management. Moreover, there shall be much higher synergies across technologies. While we wait for vendors to unite, Voltha provides an increment to that direction, by confining the differences to the locality of access and hiding them from the upper layers of the OSS stack.

How can you work with Voltha?

You can start by reading the published documentation.
Another great way is to check out the BUILD.md file to see how you can build it, run it, test it, etc.

How can you help?

Contributions, small and large, are welcome. Minor contributions and bug fixes are always welcome in form of pull requests. For larger work, the best is to check in with the existing developers to see where help is most needed and to make sure your solution is compatible with the general philosophy of Voltha. Please check out the contributing page on the documentation.