5G SBP Use Case - Application Centric Connectivity

This page serves as the working document for the Use Case as it is developed. All contributors are asked to add contributions to the project on this page. The table below may be modified in anyway to fit the needs of the project. Meeting notes along with meeting recording links are captured at the bottom of the page.

Dec 3, 2024

• Review solution benefits, key attributes, User Stories

• Start outlining BOM/SBOM

• Start outlining Outreach for potential end-users

Nov 12, 2024

Meeting Recording

• Review Architecture slides for Machine Builder Use Case

• Articulate problem scenarios and solution benefits and value props based on architectures

  • Benefits

    • Cost savings - cloud services cost reductions, storage, less proprietry logic

    • Speed - real time

    • Accuracy

    • Plug and Play → Kansas City example. Is there a demo available? Or specs that can be shared?

    • Data doesn’t move

    • same system services multiple verticals and Use Cases (telco, oil/gas, metro/smart city, nautical, IoT applications….)

    • Reduces data duplication

    • Data not centralized. Data is on virtual layer vs physical data. No transfer of data.

    • Deployment advantages

      • starting point - virtual datalake

    • Security advantages

  • What are the generic attribute(s) that can be used cross-vertically?

    • Processing at the edge (AI is a driver)

    • Day 0 - a plug and play solution that would make the starting point a virtual data lake or a virtual cloud where queries can be run against the edge. User story is updated in above table.

    • Day 2- to move data express an SQL query of what is needed. User story is updated in above table.

• Next Meeting

  • Nov 19, 2024 is Member Summit. Meeting canceled

  • Dec 3, 2024 is next scheduled call. Do we want to meet before that? Nov26? (Thanksgiving week in the US)

Nov 5, 2024

Recording

• Moshe to recruit resource/expert with Machine Builder. Michael Bachelor - https://www.linkedin.com/in/michaelbachelor/

• Jennifer Kennedy will take lead role for IBM starting next meeting.

Proposed steps forward

• Create universal benefit/capabilities statements that can be used to socialize with dev community and create demand/interest

• Figure out skills needed to start planning dev work

• Team resource assessment and likely sources for communication and reach out

• Minimal Viable Product phases

  • Mimic existing environment- this is the real-life problem. (base lab)

  • Determine how to solve the problem using the base lab

  • Demonstate cataloging of code, and documentation/playbook/whirepaper

Thoughts on Outreach-

• Outreach- Recruit interested parties - pitch to Nephio and ONAP. 10-15 min. presentation on who might benefit from these use cases? Who do we reach the Target audience?- AT&T, Verizon, T-Mobile, DT, Orange, Bell Canada, banks/inventment firms, edge providers, health insurance providers, Microsoft, Google, IBM

Action Items:

• @Moshe Shadmon to draft Architecture Proposal(s) - problem scenario(s) in block diagram here: https://lf-networking.atlassian.net/wiki/x/CJPv and provide 1st draft of BOM/SBOM based on proposed architecture- due Nov 19, 2024

• @LJ Illuzzi to create outreach in https://lf-networking.atlassian.net/wiki/x/CJPv with key LF/LFN project contacts.

Oct 22, 2024

Recording

@LJ Illuzzi @Ranny Haiby @Muddasar Ahmed @Kendall Perez @Ali Hussain

• Muddasar to reach out to the community to level-set on use cases and project value

Oct 8, 2024 

Recording

Machine Builder paper- AnyLog for Machine Builders.pdf

Smart City Use Case- https://lfedge.org/wp-content/uploads/sites/24/2024/08/LFEdge_-Sabetha_Case-Study.pdf

AnyLog - ORAN.pdf

Update EdgeLake/Machine Builder wiki with Use Cases, attributes

Aug 27, 2024

Recording

• Moche Use cases;

  • smart city

  • Machine Builder- optimization, predictive maintenance

  • Action Item: Create separate wiki pages (llike previous) and fill in details for these new use cases.

    • Disaster Recovery

    • Enterprise

    • Localization

    • Service Provider

    • EdgeLake/Machine Builder

• What do you see as the lifecycle for these scenarios?  Something like this?
  
  

  1. Proposal

  2. Recruit interested parties - pitch to Nephio and ONAP. 10-15 min. presentation on who might benefit from these use cases? Who do we reach the Target audience?- AT&T, Verizon, T-Mobile, DT, Orange, Bell Canada, banks/inventment firms, edge providers, health insurance providers, Microsoft, Google, IBM

  3. Find a Sponsor User

  4. Work on the solution

  5. Acceptance

• Situation complication resolution

• SCIPAB

Aug 13, 2024 

Recording, Transcript, and Chat

• Joe suggests find sponsors/users to help drive requirements and confirm that the project output meets those requirements. Build an architecture that can be deployed in all 3 environments

• Use Case- run workloads, unchanged, across muliple cloud domains. Build once; deploy anywhere.

• Scenarios:

  • Service provider

  • Enterprise

  • Internationalization/Localization
    
    

  • Disaster recovery

• Action Items-

  • Add detail to scenarios @Joseph Pearson @Muddasar Ahmed 

  • Create writeups- what is the concept, where does it play @Joseph Pearson 

    • Target audience- AT&T, Verizon, T-Mobile, DT, Orange, Bell Canada, banks/inventment firms, edge providers, health insurance providers, Microsoft, Google, IBM

  • Vet scenarios

  • Align with SPs, sponsors

  • Reachout to vendors (Aarna, etc). Does this make sense from a packaging/deployment perspective for there products?

    • identify vendors/contacts

  • @moshe to provide Anylog whitepaper. Will post on the slack channel

Jun 11, 2024 Meeting Recording

• Separate industry Use Cases (Muddasar)

  • @Muddasar Ahmed to look at the demo video and extract some industry use cases

• Create User Stories:

  • Create a Lab for HW infrastructure

  • Bring in 2-3 components (Data Lake for example)

• Build component BOM open source and proprietary/commercial

• What can we do as far as demo for ONE Summit in Nov?

• Next Steps and Action Items:

  • @Muddasar Ahmed to look at the demo video and extract some industry use cases.

    • Extract business justications from Use Cases

  • @Mark Davidson (AnyLog) provide Whitepaper written for AnyLog

  • AnyLog working with Cisco to integrate with there 5G solutions. Explore what we can do with Cisco. Frank Brockner is LFN resource.

• Identify other open source components that can be used to glue the pieces together.

  • Edgelake

  • L3AF, L3AF wiki - observability

• Next Meeting?

May 21, 2024 Meeting Recording and Next Steps:

• Build the business justification

• Define requirements

• Validate among the group

• Reference Open Horizon project

• Identify other open source components that can be used to glue the pieces together.

  • Relevant to Edgelake Project (Moshe Shadmon (AnyLog))

  • Where can LFN projects play a role and enrich this Use Case?

    • Observability- L3AF, L3AF wiki

• What are the standards that we would use for the data models for the interfaces, and so on.

  • Insights into applicable existing standards that should be followed

• Next steps from 05/21 (below)

  • Is previous Whitepaper available? 5G and Telco whitepaper available (Mark). written around AnyLog

  • Ask Frank Brockner (Cisco) to particiapte @Muddasar Ahmed to reach out.

  • What can we do as far as demo for ONE Summit in Nov?

• Next Meeting is Jun 11, 2024 1600 UTC

Project summation from Joe Pearson 05/21:

Within the open horizon project we had been working together with Red Hat's scupper open source software
to deploy network infrastructure software components. And the reason why we're doing this is because we believed
we were trying to implement something I would describe as application, centric connectivity.

Day 1: So rather than the traditional approach which is, you have one group of people in an enterprise that may be responsible for setting up, let's say, a network underlay managing that, creating the policies. And then potentially, another group might create network overlays on top of that, and then the developers would jump in and create and deploy their applications and somehow work together with these other teams
to then somehow get the connectivity working with their applications. So in this case, when I'm talking about applications, I'm making a couple of assumptions, I'm assuming number one that the applications may be containerized because we're using a a cloud native approach. That means we may be deploying to a bare Linux host or a Kubernetes cluster somewhere. So the idea is, can we use a cloud native or edge native application centric approach that empowers developers to define the connectivity between components in a modern distributed application and then to automatically deploy those components so that when they reach their destination they're also automatically stood up with the appropriate connectivity as an overlay on top of whatever network exists and that would then necessarily require
any software based infrastructure, or maybe even hardware based infrastructure to also be deployed if it needs to traverse various network segments, let's say, to go from the edge to the cloud to a specific provider.

So in a nutshell when an application is deployed to bare Linux or Kubernetes how can we also create a dedicated overlay connecting the distributed application components? So that would be the primary goal that I would like to achieve.

Day 2: when that application's components need to be moved to a different environment for any reason, whether that's cloud or to a physical location on premises or whatever.
Let's also move the connectivity with the components that get moved, and see if we can do it with little to no downtime.

So those are the 2 high level goals that we would like to achieve.

And then, third, one of the ways in which we would potentially want this implemented is to manage the configuration of the application and the connectivity
through declarative intent. So with that in mind, the second bullet point link there to application centric connectivity.

Is a very simple video demo that Jeff Lou who's on the call created, and that we showed in the open horizon booth at one summit. And what that does is that uses the open horizon as the orchestration and application deployment piece along with scupper as the application gateway and connectivity piece. And then demonstrates how you can deploy an application, deploy the infrastructure, and then connect to various pieces, so that an application can connect securely to its other remote services that it uses. So it's a very simple, Demo, but it goes by very, very quickly. We showed this at one summit as a demonstrator, to show how we could conceivably accomplish this today, using some manual configuration and mostly open source components. Now, in the case of the demo to make it as simple as possible, we also used a commercial product in there, which is Ibm hybrid cloud mesh what I would like to do for the or this particular blueprint is to see are there other open source components that we can use and put in this and glue the pieces together? Are pieces and components of this fungible or swappable?
And if so, what are the standards that we would use for the data models for the interfaces, and so on.
And lastly, who would be stakeholders, and who would want to participate in this blueprint with us.

The intent here is to encompass both edge and hybrid cloud, meaning all potential cloud providers, public and private on premise data center deployments, as well as what we would typically think of as edge computing deployments.

Notes from LFN/LFE Joint TAC F2F meeting from May 1:  https://docs.google.com/document/d/146ghaxAXM8RcXFS0aSfheyYGqXDPuqqK2SYR4okYQz0/edit?usp=sharing