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 Jan. 16th. Voting will take place January 17th.
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 | Committer Company | Committer Contact Info | Committer Bio | Committer Picture | Self Nominate for PTL (Y/N) |
|---|---|---|---|---|---|
Arm | song.zhu@arm.com | Y | |||
| Arm | trevor.tao@arm.com | Y | |||
| Arm | bob.monkman@arm.com | Y | |||
| Huawei | ||||
Alexandru Avadanii | ENEA | alexandru.avadanii@enea.com |
Presentation:
Use Case:
Use Case Attributes | Description | Informational |
Type | New |
|
Industry Sector | Telco networks, especially network edge and edge cloud |
|
Business driver | The Integrated Edge Cloud (IEC) will enable new functionalities and business models on the network edge. The benefits of running applications on the network edge are - Better latencies for end users - Less load on network since more data can be processed locally - Fully utilize the computation power of the edge devices
|
|
Business use cases | The IEC has several deployment models that each support different business cases:
|
|
Business Cost - Initial Build | The cost of the IEC consists of the following parts: 1. The cost of remote edge end devices 2. The cost of the edge cloud servers and networking devices 3. The software maintenance cost 4. Other cost not so explicit right now
|
|
Business Cost - Operational | The IEC device software should be fully manageable remotely with automation. The automation should also support zero touch provisioning and management tools to keep operational cost lower. |
|
Operational need | The IEC must be fully operable remotely with automation. It should be able to recover from network failures by reverting to a known good network configuration. |
|
Security need | The solution should have granular access control and should support periodic scanning.
|
|
Regulations | The IEC should meet all the industry regulations of data privacy, security, and environmental conditions. |
|
Other restrictions | Depending on the IEC deployment scenarios and environment, there can be other requirements. |
|
Additional details | There are typical edge end applications running on the edge end devices which provides fast network functions and responses to the end users. |
|