Hack2022 1st Prize: Difference between revisions
No edit summary |
|||
| Line 4: | Line 4: | ||
= Team= | = Team= | ||
Team DOMINO solution | Team DOMINO solution ( '''D'''ev'''O'''ps '''M'''EC '''IN'''fra '''O'''rchestration ) | ||
Oleg Berzin, Equinix, | |||
oberzin@equinix.com | Oleg Berzin, Equinix, | ||
Vivekanandan Muthukrishnan, Aarna Networks, | |||
vmuthukrishnan@aarnanetworks.com | [[Mailto:oberzin@equinix.com|oberzin@equinix.com]] | ||
Vivekanandan Muthukrishnan, Aarna Networks, | |||
[[Mailto:vmuthukrishnan@aarnanetworks.com|vmuthukrishnan@aarnanetworks.com]] | |||
= Introduction = | = Introduction = | ||
<p> | <p> | ||
In our solution we use Akraino Public Cloud Edge Interface (PCEI) blueprint and MEC Location API service to demonstrate orchestration of federated MEC infrastructure and services, including: | In our solution we use Akraino Public Cloud Edge Interface (PCEI) blueprint and MEC Location API service to demonstrate orchestration of federated MEC infrastructure and services, including: | ||
</p>•Bare metal, interconnection, virtual routing for MEC and Public Cloud IaaS/SaaS, across two operators/providers (a 5G operator and a MEC provider) | |||
•5G Control and User Plane Functions | |||
•Deployment and operation of end-to-end cloud native IoT application making use of 5G access and distributed both across geographic locations and across hybrid MEC (edge cloud) and Public Cloud (SaaS) infrastructure | |||
•By orchestrating, bare metal servers and their software stack, 5G control plane and user plane functions, interconnection between the 5G provider and MEC provider, connectivity to a public cloud as well as the IoT application and the MEC Location API service, we show how it is possible for providers to enable sharing of their services in a MEC Federation environment. | |||
= Use Case Description = | = Use Case Description = | ||
| Line 25: | Line 31: | ||
<p> | <p> | ||
•A practical use case showing a realization of ETSI MEC Federation architecture</p>•An introduction and a functioning demonstration of MEC Federation Data Plane | |||
•Implementation of the GSMA OPG Edge Node sharing scenario using MEC Federation | |||
•Implementation of ETSI MEC Location API Service and its integration with a MEC application | |||
•Implementation of a combined MEC Federation Broker and MEC Orchestrator with unique capabilities for infrastructure orchestration in multiple domains such as public cloud, edge/MEC cloud, network operator, 5G control plane and user plane cloud native function deployment as well as cloud native service and application deployment | |||
•Implementation of integrated Terraform Infrastructure-as-Code module into the orchestrator enabling DevOps infrastructure orchestration | |||
Revision as of 13:24, 24 October 2022
MEC Service Federation for Location-aware IoT withDevOps MEC Infra Orchestration
Team
Team DOMINO solution ( DevOps MEC INfra Orchestration )
Oleg Berzin, Equinix,
[[1]]
Vivekanandan Muthukrishnan, Aarna Networks,
[[2]]
Introduction
In our solution we use Akraino Public Cloud Edge Interface (PCEI) blueprint and MEC Location API service to demonstrate orchestration of federated MEC infrastructure and services, including:
•Bare metal, interconnection, virtual routing for MEC and Public Cloud IaaS/SaaS, across two operators/providers (a 5G operator and a MEC provider)
•5G Control and User Plane Functions
•Deployment and operation of end-to-end cloud native IoT application making use of 5G access and distributed both across geographic locations and across hybrid MEC (edge cloud) and Public Cloud (SaaS) infrastructure
•By orchestrating, bare metal servers and their software stack, 5G control plane and user plane functions, interconnection between the 5G provider and MEC provider, connectivity to a public cloud as well as the IoT application and the MEC Location API service, we show how it is possible for providers to enable sharing of their services in a MEC Federation environment.
Use Case Description
contributions and innovations
•A practical use case showing a realization of ETSI MEC Federation architecture
•An introduction and a functioning demonstration of MEC Federation Data Plane
•Implementation of the GSMA OPG Edge Node sharing scenario using MEC Federation
•Implementation of ETSI MEC Location API Service and its integration with a MEC application
•Implementation of a combined MEC Federation Broker and MEC Orchestrator with unique capabilities for infrastructure orchestration in multiple domains such as public cloud, edge/MEC cloud, network operator, 5G control plane and user plane cloud native function deployment as well as cloud native service and application deployment
•Implementation of integrated Terraform Infrastructure-as-Code module into the orchestrator enabling DevOps infrastructure orchestration