CREDITS

The core Framework Wave was originally developed by Vidyasagara Guntaka and his team at Brocade Communications Systems, Inc. Majority of the code was developed as part of a n-master controller that managed / controlled Brocade VCS fabrics. Core portions of the code predates Brocade VCS Fabrics. Brocade shipped 48 node clusters based on this framework. The framework is capable of n-master clustering / federation with distributed persistence among many other neat features.

The framework was used in Storage Virtualzation, Network Virtualization among many other areas. It was used to simulate multi core Cavium network processors due to its versatile distributed and multi threaded message bus and interfaces.

A complete list of features will run into more than hundred lines.

Around December of 2013, Brocade decided to donate the code to open source community under Apache License 2.0 as part of the committment when it joined OpenDayLight project as a Platinum member.

Brocade donated source code can be accessed from here

Only the Wave (the core framework) that has no Networking / Storage specifics is absorbed into this repository and further developed.

Vidyasagara Guntaka maintains this repository on GitHub further developing the Wave framework. He is Currently coding C++ and Java variants of the framework and has Python and Go variants in sight so that the micro services running in Wave cluster can be polyglot.

LICENSE

---

This code is being made available to the pulbic under Apache License, Version 2.0

C++

---

CODE LAYOUT

Wave/C++
├── application
├── build
├── postboot
├── projects
├── resourcegenerator
└── source

• source
  • contains almost all of the Wave Framework code.
• application
  • contains various top level Applications created with the Wave Code.
• projects
  • contains various IDE specific setups (ex. eclipse etc)
• resourcegenerator
  • contains the source code for Wave Resource ID generation from XML files.
  • Wave has good localization / internationalization support in terms of Resource IDs. Error messages etc., need not be hard coded into source files.
• postboot
  • Another utility internally used by Wave code.
• build
  • When the code is built, it creates various levels of directories for object files and libraries etc.,
  • It also contains dynamiclly generated code (ex. Resource IDs).
  • The layout will be based on OS and Architecture type
  • The Debug and Optimized versions based on gmake options will be placed in different directories

BUILDING THE C++ CODE

The following build instructions are provided from Linux build host perspective. (In general tested on Fedora distributions).

1. Make sure that all of the dependencies listed in the installation command mentioned in the file Wave/source/PREREQUISITES If all of the dependencies are not installed, there will be compilation errors.
2. cd to Wave/application
3. Issue the following command
   • gmake -j 10
   • change arguments to -j in the above command based on number of cpus available for compilation.
4. If you prefer non verbose compilation, you can issue the following command prior to issuing the gmake command
   • export MAKEFLAGS=-s

JAVA

---

Stay tuned ...