-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accelerating Cloud Native in Telco whitepaper (v1) #272
Conversation
The first iteration of the whitepaper "Accelerating Cloud Native in Telco" on the Challenges of Cloud Native Telco Transformation today and how to overcome them - A CSP perspective Co-authored-by: Daniel Bernier <[email protected]> Co-authored-by: Roger Lupien <[email protected]> Co-authored-by: Mohammad Zebetian <[email protected]> Co-authored-by: Vuk Gojnic <[email protected]> Co-authored-by: Horatiu Vlad <[email protected]> Co-authored-by: Nathan Rader <[email protected]> Co-authored-by: Johanna Heinonen <[email protected]> Co-authored-by: Philippe Ensarguet <[email protected]> Co-authored-by: Guillaume Nevicato <[email protected]> Co-authored-by: Ashan Senevirathne <[email protected]> Co-authored-by: Josua Hiller <[email protected]> Co-authored-by: Andrei Ivanov <[email protected]> Co-authored-by: Sana Tariq <[email protected]> Co-authored-by: Tom Kivlin <[email protected]> Co-authored-by: Riccardo Gasparetto Stori <[email protected]> @vukg @tomkivlin Signed-off-by: Taylor Carpenter <[email protected]>
adding date and version Signed-off-by: Taylor Carpenter <[email protected]>
this is only for convenience and will be updated again after the PR is merged. Please see the markdown version in the PR for the latest version Signed-off-by: Taylor Carpenter <[email protected]>
Co-authored-by: Pankaj Goyal <[email protected]> Co-authored-by: Nikolay Nikolaev <[email protected]> Co-authored-by: Victor Morales <[email protected]> Signed-off-by: Taylor Carpenter <[email protected]>
- Reformulated the introduction to make compliance statements mutual for vendor + CSP - Added an explicit reference to x86 HW as mainstream HW. Co-authored-by: Jeffrey Saelens <[email protected]> Signed-off-by: Vuk Gojnic <[email protected]>
phrasing for benefiting CSPs and vendors updated Signed-off-by: Taylor Carpenter <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The paper looks good overall, I added a few comments and suggestions in line.
Thanks,
Ildikó
Co-authored-by: Victor Morales <[email protected]> Signed-off-by: Taylor Carpenter <[email protected]>
…in introduction (#287) * Update Accelerating_Cloud_Native_in_Telco.md * Update Accelerating_Cloud_Native_in_Telco.md Fixing linux instead of Linus in the preamble + proposing a last sentence in the introduction to state that Kubernetes is the de facto runtime environment for hosting the CNF. Kubernetes as such is listed later on in the doc, but as mentioned in the thread with ildikov it may worth mentioning it. Signed-off-by: Philippe Ensarguet <[email protected]> --------- Signed-off-by: Philippe Ensarguet <[email protected]> Signed-off-by: Taylor Carpenter <[email protected]> Co-authored-by: Taylor Carpenter <[email protected]>
* Added Cloud Native Infrastructure definitions * Update Accelerating_Cloud_Native_in_Telco.md * Update Accelerating_Cloud_Native_in_Telco.md * Update Accelerating_Cloud_Native_in_Telco.md * Update Accelerating_Cloud_Native_in_Telco.md * Update Accelerating_Cloud_Native_in_Telco.md
Co-authored-by: Ildiko Vancsa <[email protected]> Co-authored-by: Victor Morales <[email protected]> Signed-off-by: Taylor Carpenter <[email protected]>
Signed-off-by: Taylor Carpenter <[email protected]> Co-authored-by: Taylor Carpenter <[email protected]>
Co-authored-by: Lucina Stricko <[email protected]> Signed-off-by: Taylor Carpenter <[email protected]>
* GitOps annex and references Adding some information on GitOps since it is references in the whitepaper Signed-off-by: Taylor Carpenter <[email protected]> * Update Accelerating_Cloud_Native_in_Telco.md grammar Signed-off-by: Taylor Carpenter <[email protected]> * GitOps components a few components of GitOps Signed-off-by: Taylor Carpenter <[email protected]> * Apply suggestions from code review Co-authored-by: Lucina Stricko <[email protected]> Signed-off-by: Taylor Carpenter <[email protected]> * Apply suggestions from code review Co-authored-by: Lucina Stricko <[email protected]> Signed-off-by: Taylor Carpenter <[email protected]> --------- Signed-off-by: Taylor Carpenter <[email protected]> Co-authored-by: Lucina Stricko <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
* Delete doc/whitepaper/DRAFT-whitepaper - Accelerating_Cloud_Native_in_Telco.pdf Signed-off-by: Taylor Carpenter <[email protected]> * PDF version of whitepaper PDF version created at https://dillinger.io/ from the raw markdown Signed-off-by: Taylor Carpenter <[email protected]> --------- Signed-off-by: Taylor Carpenter <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my inputs for the document
and relying on “rolling upgrades” to deploy changes. This paradigm is applied in both the lifecycle management of applications and | ||
the cloud infrastructure. As a consequence, for example, Kubernetes cluster nodes can ordinarily have rather short uptime of several | ||
days to several weeks. This is in contrast with the traditional carrier-grade-driven focus on the uptime of individual system | ||
elements. Although large parts of CNFs do not have problems with that cloud native lifecycle approach, we are experiencing that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LCM is a separate topic , similarly Resilience (improve HA design) and Reliability . These all three should be placed as separate points for challenges .
human-readable open formats | ||
1. The application must be isolated with Namespaces and not use the default namespace | ||
|
||
1. **Resilience.** High-quality CNFs should be resilient to underlying infrastructure issues including complete failure, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sugges to add one item on "Testing framework" i.e idea is all points above can be tested in an automated fashion and how we can achieve it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add two more section on how to solve it
-
operational readiness
e.g in brownfield how we can integrate , co-exist it with existing tools and align with processess -
Commercial models
do local tuning is a great way for Telco clouds but with Edge/RAN it is important that we test once and deploy in a scalable manner , even those deployments need to be tested . so defining what are those models of scale are key to success .
For procurement, right TCO and most important automation at scale is vital here
The first iteration of the whitepaper "Accelerating Cloud Native in Telco" on the Challenges of Cloud Native Telco Transformation today and how to overcome them - A CSP perspective (PDF). The most up-to-date version is currently here https://github.com/cncf/cnf-wg/blob/whitepaper-accelerating-cloud-native-in-telco/doc/whitepaper/Accelerating_Cloud_Native_in_Telco.md
Contributors and co-authors include:
A PDF version is available, but may not be the most updated version. The markdown is the source of truth.