Gitiles
Code Review Sign In
gerrit.opencord.org / voltha-go / c2c73ff343984b55f36eac1016f78af7307b14af
commitc2c73ff343984b55f36eac1016f78af7307b14af[log] [tgz]
authorKent Hagerman <khagerma@ciena.com>Wed Nov 20 16:22:32 2019 -0500
committerkhenaidoo Nursimulu <knursimu@ciena.com>Thu Nov 21 20:36:07 2019 +0000
treee979966b9d34b84b91025c378c01380f7117b0bb
parent91482648070246dbf77e56e80a78687c121f0ddf [diff]
Adding ro-core exclusive api calls to the rw-core.

VOL-2257

There were 10 calls implemented in the ro-core that weren't in the rw-core:
GetVoltha
ListCoreInstances
GetCoreInstance
ListDeviceFlowGroups
ListDeviceTypes
GetDeviceType
ListDeviceGroups
GetDeviceGroup
GetImages
GetMeterStatsOfLogicalDevice

Of these, 5 were stubs: (which were copied over anyways)
ListCoreInstances
GetCoreInstance
ListDeviceGroups
GetDeviceGroup
GetMeterStatsOfLogicalDevice

Altered ListDeviceTypes() and GetDeviceType() to pull from AdapterManager.deviceTypeToAdapterMap rather than going directly to the DB.
Also changed gRPC api calls that returned nil, error to return &type{}, error; and unified returns of this form.

Change-Id: Ib86163bdf6809e84d44632792766c4633534da1b
2 files changed
tree: e979966b9d34b84b91025c378c01380f7117b0bb
  1. .gitignore
  2. .gitreview
  3. BUILD.md
  4. Makefile
  5. README.md
  6. VERSION
  7. cli/
  8. common/
  9. compose/
  10. db/
  11. docker/
  12. go.mod
  13. go.sum
  14. python/
  15. quickstart.md
  16. ro_core/
  17. rw_core/
  18. tests/
  19. vendor/
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?

While we are still at the early phase of development, you can 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.