Date: Fri, 29 Mar 2024 14:17:26 +0000 (UTC) Message-ID: <19501664.30466.1711721846914@aws-us-west-2-lfn-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30465_511884754.1711721846914" ------=_Part_30465_511884754.1711721846914 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Detailed Description: Brief update cover CNTT Edge. After = reviewing the Reference Model, it was determined that the Reference Model m= et the Edge groups criteria in its current state. Proposals for chang= es to the CNTT reference architectures, both RA1 (OpenStack) and RA2 (Conta= iners) can be found at CNTT Edge - RA01 ( OpenStack = ) Architecture - Scenario. This will serve as the basis for the d= iscussion for the planning for the upcoming work that needs to be incorpora= ted into the next (Elbrus) release targeted for January. =
CNTT Edge - RA01 ( OpenStack ) Architecture - Scenario
Pankaj reviewed his outline and asked for comments. Beth: there ar= e two types of edge that are quite different. The far edge has very d= ifferent characteristics than the data center. Telco edge is more foc= used more on low latency than other use cases. O-RAN is a use case th= at is latency sensitive use case. SD WAN is a mixed use case, purpose= -built edge or uCPE based software. The controllers are located in th= e core cloud. Time sync is important O-RAN, RAN video processing,&nbs= p;UPF - User Plane Fn for packet routing, forwarding inspection, etc. = and possibly other use cases. We have not spent time characterizing a= ll the use cases yet. Use cases are a good way of mapping the Edge re= quirements, but we should not get bogged down in the details or create silo= s. We should create a set of profiles that abstract the use cases.&nb= sp; We cannot proscribe the HW, but at the far edge is much more dependent = on the HW. From an architecture view, we need to be able to support v= ery distributed profiles. We can simplify all the use cases wit= h the profiles.
You need to think in terms of cores, not racks. HA at the edge at = the minimum is two servers. There are situations where the Edge nodes= are impermanent and the HA is achieved by an adjacent node picking up the = workload. IoT is a good use case that fits this scenario. The c= ontrol plane is centralized to a certain extent, but the edge nots have to = have at least some autonomy to work independent of the control plane. = Ildiko: Don't try to define the edge, but it is ALWAYS connected to = some kind of centralized core. How much is controlled at the Edge and= how much is controlled at the core. Many parameters to take into con= sideration. Anyone that worked on Distributed Processing in the= 1980's would recall that the nodes were considered from 3 limitations: Pro= cessing, storage, bandwidth. These now apply to edge nodes. Terminolo= gy is difficult, 3 years in and we still don't have a shared definition of = the edge. The problem is that Edge is a super set of Cloud computing.= Telco Edge is both latency and network efficiency concerns.&nb= sp; Trevor: What are we trying to solve for the CNTT workstream? = ; Important question. We cannot boil the ocean.
Review of the chart that covers who owns what in the Edge. Workloa= d distribution, hybrid model of HW and SW. How can you deliver an SLA= in this model? Public and private cloud SLAs are very different.&nbs= p; Telco SLAs need to be much higher per customer expectations. Cloud= has the illusion of infinite resources, but when you scale you can use out= side locations. There is always a cost for flexibility. = p>
Multi-cloud is very important to the Edge use cases. There is alwa= ys overhead in multiple cloud scenario.