The Akraino Regional Controller provides a standardized way to install Akraino Blueprints on disparate, network connected, hardware. It is designed to be agnostic about what is being installed, and only concerns itself with providing a standard framework for running workflows associated with Blueprints, in order to perform the lifecycle management functions of a particular Blueprint. It does this via a REST-based API.
- Starting the Regional Controller
- Object Model / Flow of Operation
- How to load objects into the Regional Controller
- How to write Blueprints and Workflows
- Frequently Asked Questions
Project Technical Lead: TBD
Project Committers detail:
Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.
A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.
Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project. Candidates must self nominate by marking "Y" in the Self Nominate column below by TBD. Voting will take place TBD.
Only Committers for a project are eligible to vote for a project’s Project Technical Lead.
Please see Akraino Technical Community Document section 3.1.3 for more detailed information.
|Committer Bio||Committer Picture|
Self Nominate for PTL (Y/N)
Mike is a Principal Systems Architect at AT&T who has worked on Cloud since 2011 and has worked on Akraino since its inception inside AT&T.
Along with working in Cloud, Mike has, engineered parts of SONET provisioning systems, been the lead engineer at a startup, engineered CDN solutions, designed cloud storage solutions up to exabyte scale, and designed more than a few portals for more than a few systems. He is also a self proclaimed "human factors" enthusiast.
Use Case Details:
Companies Participating / Committers
Requested Release / Timeline
Akraino Regional Controller
The current Akraino Portal provides a user interface and a collection of workflows and services to execute the actions requested by the user. This proposal is to separate the workflows and services from the portal user interface so that actions can be performed through the portal, direct REST calls from an external orchestration tool, or a CLI that could be developed as part of a different feature project.
Impacted Blueprint Family - Network Cloud and Radio Edge Cloud
See attachment for additional details