Blog

Who is interested?


Orinoco Release Launched

More information here

  • Anuket resources are very thin so hard to get anyone to work on the project
  • Review of the project within Anuket – Some do not need release managers (Thoth), Some are not active, Some need releases (Functest, VinePerf, CIRV, Kuberef) and finally the reference docs. 
  • TSC could serve as a release manager with a stronger community
  • We should support projects which do not follow the Anuket release model
  • There are different categories of the projects
    • Projects that do not need releases (Thoth)
    • Inactive projects should just be archived
    • Reference docs – need minimal release support (set dates and gather requirements)
      • Set the dates for the release - TSC
      • Release plan - sub-project teams/PTL
      • Release tags in Jira and GitHub - TSC
      • Associate Issues with the GitHub project plan - PTL
      • Proofreading - PTL
      • Release branch creation - TSC
      • Readthedocs branch creation - TSC
      • Sub-project release highlights - PTL
      • Blogpost, release announcement - TSC
    • Test projects
      • Set the dates for the release - TSC
      • Release plan - sub-project teams/PTL
      • Release tags in Jira and GitHub - TSC
      • Associate Issues with the GitHub project plan - PTL
      • Documentation done - PTL/Team
    • Keep two releases per year
    • Update the release framework tasks with the slimmed down version 
  • Next steps:


This page collects the CNF requirements in RA2, RC2 and in CNCF CNF Conformance / CNF Testbed.

The original analyzis page for introducing the CNF requirements in RA2: Analyzis of CNCF CNF Testsuite tests for RA2

CNF Testsuite points.yaml

 pr-s


CNF TestsuiteCNF ConformanceRA2RA2RC2What to do?

increase_decrease_capacity

essentialra2.app.038

should

→ must (3352)

shouldAdd a link to CNF Testsuite.
Make a must in RA2 and RC2

helm_chart_published


ra2.app.011mustshould

helm_chart_valid


ra2.app.012mustshould

helm_deploy






rollback






rolling_update


ra2.app.013mustmust

rolling_version_change






rolling_downgrade


ra2.app.014mustmust

cni_compatibility


ra2.app.015mustmust

alpha_k8s_apis


ra2.app.016must (not)must (not)

reasonable_image_size


ra2.app.039should (not)should (not)

reasonable_startup_time


ra2.app.040should (not)should (not)

single_process_type

essential
missingmisssingIt is unclear if this is a realistic requirement. There is an ongoing discussion in CNF Testsuite about this. I propose to leave this out until this is clarified.

service_discovery






shared_database






specialized_init_systems






node_drain

essentialra2.app.017must (not)must (not)

volume_hostpath_not_found






no_local_volume_configuration


ra2.app.025must (not)must (not)

elastic_volumes






database_persistence






pod_network_latency


ra2.app.018must (not)must (not)

disk_fill






pod_delete


ra2.app.019must (not)must (not)

pod_memory_hog


ra2.app.020must (not)must (not)

pod_io_stress


ra2.app.021must (not)must (not)

pod_network_corruption


ra2.app.022must (not)must (not)

pod_network_duplication


ra2.app.023must (not)must (not)

pod_dns_errors


ra2.app.024must (not)must (not)

liveness

essentialra2.app.026mustmust

readiness

essentialra2.app.027mustmust

log_output

essentialra2.app.046should → must (3352)
missingChange it to must in RA2, add to RC2

prometheus_traffic






routed_logs






open_metrics






tracing






container_sock_mounts

essentialra2.app.028must (not)must (not)Add reference to CNF Testbed to RA2

privileged_containers

essentialra2.app.041

should → must (3352)
should (not)

Change it to must RA2 and RC2.

external_ips






non_root_user


ra2.app.042

shouldshould (not)

Change it to must RA2 and RC2.

privilege_escalation


ra2.app.043shouldshould (not)





selinux_options

essentialra2.app.048mustmissingAdd to RC2

sysctls






application_credentials


ra2.app.029must (not)must (not)

host_network


ra2.app.030must (not)must (not)

service_account_mapping






ingress_egress_blocked






insecure_capabilities






non_root_containers

essentialra2.app.044should → must (3352)
shouldChange to must in RA2, add to RC2

host_pid_ipc_privileges


ra2.app.031must (not)must (not)

linux_hardening






resource_policies

essentialra2.app.032mustmust (not)

immutable_file_systems


ra2.app.033mustmust (not)

hostpath_mounts

essentialra2.app.007should (not)shouldChange to must in RA2, add to RC2

default_namespace






latest_tag

essential

ra2.app.049

ra2.app.034

should (not)
must (not)
034: mustremove ra2.app.049

required_labels


ra2.app.045shouldshould

versioned_tag






nodeport_not_used


ra2.app.036must (not)must (not)

hostport_not_used

essentialra2.app.047should (not) → must (3352)
missingMake it must in RA2, add to RC2

hardcoded_ip_addresses_in_k8s_runtime_configuration

essentialra2.app.035must (not)must (not)

secrets_used






immutable_configmap


ra2.app.037mustmust


ra2.app.034must



ra2.app.038shouldshould


ra2.app.001??? → remove (3352)mustIt is not really clear what this requirement is and it is not tested in CNF Testbed
I propose to remove this.


ra2.app.002???  → remove (3352)mustIt is not clear what is the requirement here. Is this about host mounts? This is not tested by CNF Testbed
I propose to remove this


ra2.app.003???  → remove (3352)mustIt is not clear what is the requirement here. This is not tested by CNF Testbed
I propose to remove this


ra2.app.004???  → remove (3352)must

It is not clear what is the requirement here. Kubernetes sets the pod name by default. This is not tested by CNF Testbed

I propose to remove this.



ra2.app.005???  → remove (3352)must

It is not really clear what this requirement is and it is not tested in CNF Testbed

I propose to remove this.



ra2.app.006mustmust


ra2.app.007should (not)must


ra2.app.008must (not)must (not)


ra2.app.009mustmust


ra2.app.010mustmustThis in a littlebit of contradiction with ra2.app.016 I propose to modify it to a should.

Nile, the latest version of Anuket was released to the public on January 4, 2023, with add cloud native requirements and testing functionality!

Anuket Overview

Anuket is an LF Networking project occupies a unique position in the telecom industry incorporating both operator infrastructure specifications, implementations, and open source infrastructure test suite development, all under a single initiative. The community has subject matter expert representatives from telco operators and their technology suppliers, which means that it is well positioned to address the “real world” challenges of the telecommunications industry. If you or anyone you know would like to contribute to any of these important activities, the Anuket website is a great place to start.

Leadership

Anuket members, per its Charter, elected the 2023 Technology Steering Committee and Co-chairs: Scott Steele and Gergely Csatari. On behalf of outgoing 2022 TSC Co-chairs, Gergely and myself, we would like to thank all Anuket contributors for their fantastic efforts in 2022 and wish the new TSC and the new Co-chairs all the best in their 2023 work!

Anuket Nile Release

Numerous Anuket projects and work streams continued to strengthen container-based open infrastructure specifications and implementations – an area that is increasingly important to the telco industry. Some of the accomplishments include:

  • ViNePerf - The ViNePerf project continued development efforts to automate test setup and benchmarking of container networking with various CNI plug-ins (Multus, Cillium) and kernel acceleration (AF_XDP, eBPF), with the help of a Student Volunteer and an Intern from the LFN program.
  • Thoth - The Thoth project continues to focus on implementing E2E AI for NFV use case scenarios. The newly established NICIP project is a jointly organized data generation competition with ITU.  Thoth is also cooperating on AI frameworks such as Mindspore, and starting the R&D effort needed to create data anonymization tools to allow telecom companies to share without the fear of exposing actual customer data.

 

On the requirements side

  • Reference Model (RM) changes (major):
  • Infrastructure LCM Automation – re-edited and updated to improve readability and to ensure alignment with multi-cloud models
  • Security sections updated to reflect (and refer to) evolving 5G security standards and best practices
  • Added energy consumption metrics and related requirements
  • Reference Architecture 1 (RA1) OpenStack changes:
  • New chapter based on RC1 content integrates conformance and establishes the link between architecture requirements and tests, providing the mechanism to validate the cloud infrastructure against the set of defined requirements.
  • Chapter 1 has been restructured with the addition of a bibliography and an abbreviations table.
  • The whole document has been reviewed to ease the creation of version 2 of NG.133 GSMA document.
  • 133 v2 has been officially published the 9thof December.


  • Updates have been made for the support of containerized applicationsand Cyborg accelerators drivers.
  • Reference Conformance 2 (RC2) has been updated to align with the latest versions of Kubernetes and Functest.
    1. Added specific test references supporting workloads by referencing the CNCF CNF testsuite.


In the coming releases, Hybrid, Multi-Cloud model and AI/ML utilisation, will be the focus of Anuket work in the upcoming releases, reflecting a growing global interest in more sophisticated operating models for telecommunication operators facing the challenges of real-life 5G/Edge/IoT implementations.

NameEarliest time to start the TSC in UTCLatest time to start the TSC in UTCMeeting Window in Hours
8:0016:008
12:00 (if needed), 13:00 (preferred)01:00 +112
Pankaj Goyal 14:000500 +115
12:0016:0015
1:0015:0014
Georg Kunz 08:0016:008
Walter Kozlowski 20:00 (21:00 April - Oct)13:00 (next day) (14:00 April - Oct)17

In 2022, the Anuket Project continued its two release cadence with Moselle delivered in June and Nile following in December. As has been true for the last few years, Anuket has been focused on developing reference models, architectures and specifications in support of infrastructure for virtualized (CNF/VNF) telecom workloads.  The requirements have continued to evolve to cover more use cases in the Reference Model (RM), and align these use cases with changes in upstream communities in the Reference Architectures for OpenStack (RA1) and Kubernetes (RA2). The application requirement specification for the Reference Architecture for Kubernetes matches with the CNCF CNF Conformance program to avoid the fragmentation of conformance programs in the industry, while fostering continued collaboration with the CNCF community. Taking the Reference Model and the Reference Architecture for OpenStack, in 2022 the Reference Conformance for OpenStack has also been released as a GSMA Permanent Release document. We are working with the GSMA on a planned release of the Reference Architecture for Kubernetes (RA2) in 2023.  On top of the enhancement of collaboration with GSMA we plan to continue to evolve our specifications by adding new use cases, aligning with adjacent communities, such as Nephio, O-RAN and Sylva, and further increase the quality and coverage of our Reference Architecture for Kubernetes and conformance projects.  

On the testing side of the project, Functest, the testing framework that supports the conformance and Anuket Assured programs maintains continuous release updates in synch with the upstream OpenStack and Kubernetes releases.  The ViNePerf project continued development efforts to automate test setup and benchmarking of  container networking with various CNI plug-ins (Multus, Cillium) and kernel acceleration (AF_XDP, eBPF), with the help of a Student Volunteer and an Intern from the LF program. 

We also plan to continue the work we started in 2022 to increase the consumability of our project and our deliverables by enhancing our documentation, testing tools and web presence.


Intro

The target of this conspiracy to make Anuket more easy to understand for someone who is not involved in the project.

We would like to achieve this by tuning the already existing documentation created for the project. This includes applying consistent templates, linking the documents together in a meaningful way and many more listed in here.

This page is created to help the conspirators.

Current conspirators

Project management and communication

What is where


anuket-doc-structure



 

  • Problem statement from
  • We have a defined scope here: About Anuket
  • Conclusions
    • We do not need to change the scope
    • We would need to have a survery on Anuket among the industry actors about the role and adoption of Anuket.



Active Anuket repos

This is a list of active Anuket repos in the July of 2022


LocationIs active
airshipGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
apexGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
apex-os-net-configGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
apex-puppet-tripleoGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
apex-tripleo-heat-templatesGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
armbandGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
autoGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
availabilityGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
bambooGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
barometerGerrityes
bottlenecksGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
calipsoGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
cirvGerrityes
cirv-hdvGerrit
cirv-rapidGerrit
cirv-sdvGerrit
cirv-spirentGerrit
cloverGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
compass-containersGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
compass4nfvGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
conductorGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
container4nfvGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
copperGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
cperfGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
cranGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
daisyGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
doctorGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
dominoGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
dovetailGerrit

Dan Xu 

  • is archived
  • Gerrit must be set as RO
dovetail-webportalGerrit

Dan Xu 

  • is archived
  • Gerrit must be set as RO
dpaccGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
edgecloudGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
enfvGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
escalatorGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
fastpathmetricsGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
fdsGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
fuelGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
functestGerrityes
functest-kubernetesGerrityes
functest-requirementsGerrityes
functest-xtestingGerrityes
genesisGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
genesisreqGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
infraGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
inspectorGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
ipv6Gerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
joidGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
kuberefGerrityes
kvmfornfvGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
laasGerrityes
laas-reflabGerrityes
lsoapiGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
modelsGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
moonGerrit
movieGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
multisiteGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
netreadyGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
nfvbenchGerrityes
octopusGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
onosfwGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
openretrieverGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
operaGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
opnfvdocsGerrityes
opnfvtscGerrit

Cedric Ollivier  :

  • not used
  • Gerrit must be set as RO
orchestraGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
oscarGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
ovn4nfvGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
ovn4nfv-k8s-pluginGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
ovnoGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
ovsnfvGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
parserGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
pharosGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
pharos-toolsGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
pinpointGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
policytestGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
predictionGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
promiseGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
puppet-barometerGerrit
qtipGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
relengGerrityes
releng-anteaterGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
releng-testresultsGerrityes
releng-utilsGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
releng-xciGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
releng-xci-scenariosGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
rocketGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
rsGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
samplevnfGerrityes
sandboxGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
sandbox-zuul-configGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
sandbox-zuul-untrustedGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
sdnvpnGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
securedlabGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
securityscanningGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
sfcGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
snapsGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
spark-model-runnerGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
stor4nfvGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
storperfGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
testGerrit

Cedric Ollivier  :

  • LFN sandbox ??
  • must be deleted
test/testGerrit

Cedric Ollivier  :

  • LFN sandbox ??
  • must be deleted
test/test1Gerrit

Cedric Ollivier  :

  • LFN sandbox ??
  • must be deleted
test2Gerrit

Cedric Ollivier  :

  • LFN sandbox ??
  • must be deleted
thothGerrit

yes

vesGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
vineperfGerrityes
vnf_forwarding_graphGerrit
Cedric Ollivier  :
  • is archived
  • Gerrit must be set as RO
vswitchperfGerrit
yardstickGerrit

Cedric Ollivier  :

  • is archived
  • Gerrit must be set as RO
CNTTGitHub

Gergely Csatari :

  • This was moved to anuket-project/anuket-specification and it is active
 anuket-project/sphinxcontrib-relative-link-correctorGitHub

Cedric Ollivier

  • this shouldn't be hosted in CNTT.
  • Why not use the contributor's repo?

Gergely Csatari 

  • It was created to support CNTT doc compilation from md not relevant anymore. I can move it to an other home if Anuket does not want it.
sphinxcontrib-readme-to-indexGitHub

Cedric Ollivier 

  • this shouldn't be hosted in CNTT.
  • Why not use the contributor's repo?

Gergely Csatari 

  • It was created to support CNTT doc compilation from md not relevant anymore. I can move it to an other home if Anuket does not want it.
sphinxcontrib-direct-copyGitHub

Cedric Ollivier 

  • this shouldn't be hosted in CNTT.
  • Why not use the contributor's repo?

Gergely Csatari 

  • It was created to support CNTT doc compilation from md not relevant anymore. I can move it to an other home if Anuket does not want it.
NetreadyGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO if it's not done already
  • this Gitlab repo mustn't have been created and must be removed asap
SnapsGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO if it's not done already
  • this Gitlab repo mustn't have been created and must be removed asap
SfcGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
SdnvpnGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
QtipGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
PromiseGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
PredictionGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
ParserGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Ovn4nfv K8s PluginGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Ovn4nfvGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
OpenretrieverGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
OnosfwGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
OctopusGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
MultisiteGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
LsoapiGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
KvmfornfvGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Ipv6GitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
InspectorGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
GenesisreqGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
GenesisGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Compass4nfvGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Compass ContainersGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
YardstickGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
VESGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
FastPathMetricsGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap

Emma Foley this was the SFQM project repo, renamed to Barometer circa 2016

EscalatorGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
DPACCGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
DominoGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
DaisyGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
CPerfGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
CopperGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
OperaGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
VNF Forwarding GraphGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
JOIDGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
OVSNFVGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
CNTTGitLab

Cedric Ollivier :

  • this repo is obsolete which is a big concern!
  • at worst this repo must be automatically synced as we have done for OPNFV projects in Github
  • I would have recommended not to create it until any TSC desicion.
BottlenecksGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
AvailabilityGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
AutoGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
FastDataStacksGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Apex-Puppet-TripleOGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
FuelGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
ApexGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
ArmbandGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Pharos-ToolsGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
Stor4NFVGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
DoctorGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
VinePerfGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
PharosGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
relengGitLab

Cedric Ollivier :

  • no point as Releng depends on Gerrit
  • this Gitlab repo mustn't have been created and must be removed asap
vswitchperfGitLab

Cedric Ollivier :

  • is archived (see vineperf)
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
storperfGitLab

Cedric Ollivier :

  • is archived
  • Gerrit must be set as RO
  • this Gitlab repo must be removed asap
samplevnfGitLab
opnfvdocsGitLab
nfvbenchGitLabcurrently mirror of gerrit
laas-reflabGitLabcurrently mirror of gerrit
laasGitLabcurrently mirror of gerrit
kuberefGitLabcurrently mirror of gerrit
functest-xtestingGitLab

Cedric Ollivier :

  • basically mislead the enduser (it would remain in Gerrit) and the contributor doesn't have any right there
  • this Gitlab repo mustn't have been created and must be removed asap
functest-kubernetesGitLab

Cedric Ollivier :

  • basically mislead the enduser (it would remain in Gerrit) and the contributor doesn't have any right there
  • this Gitlab repo mustn't have been created and must be removed asap
functestGitLab

Cedric Ollivier :

  • basically mislead the enduser (it would remain in Gerrit) and the contributor doesn't have any right there
  • this Gitlab repo mustn't have been created and must be removed asap
dovetail-webportalGitLab

Cedric Ollivier :

  • is it still active (last change was done many months ago) ?
  • this Gitlab repo could be removed

Dan Xu :

  • It's mirror of Gerrit
  • Not active, could be removed
dovetailGitLab

Cedric Ollivier :

  • is it still active (last change was done many months ago) ?
  • this Gitlab repo could be removed

Dan Xu :

  • It's mirror of Gerrit
  • Not active, could be removed
cirv-spirentGitLab

Cedric Ollivier :

  • is it still active (last change was done many months ago) ?
  • this Gitlab repo could be removed
cirv-sdvGitLab

Cedric Ollivier :

  • is it still active (last change was done many months ago) ?
  • this Gitlab repo could be removed
cirv-rapidGitLab

Cedric Ollivier :

  • is it still active (last change was done many months ago) ?
  • this Gitlab repo could be removed
cirv-hdvGitLab

Cedric Ollivier :

  • is it still active (last change was done many months ago) ?
  • this Gitlab repo could be removed
cirvGitLab

Cedric Ollivier :

  • is it still active (last change was done many months ago) ?
  • this Gitlab repo could be removed
BarometerGitLabcurrently mirror of gerrit
CalipsoGitLab

Cedric Ollivier :

  • was archived before any GitLab discussion
  • Gerrit must be set as RO
  • this Gitlab repo mustn't have been created and must be removed asap
AirshipGitLab

Cedric Ollivier :

  • is archived
  • Gerrit must be set as RO
  • this Gitlab repo must be removed asap

Toc

Logistics

  • Conference time: November 15 – 16, 2022
  • Conference place: Seattle, WA
  • CFP deadline: Friday, July 8 at 11:59 PM PDT

Proposal template

  • Speaker info:
    • Primary Speaker Full Name
    • Primary Speaker Company
    • Primary Speaker Job Title
    • Primary Speaker Email
    • Primary Speaker Country of Residence
    • Primary Speaker Biography (provide a biography that includes your employer (if any), ongoing projects and your previous speaking experience)
    • Primary Speaker Twitter Handle
    • Primary Speaker LinkedIn Profile
    • What gender does the primary speaker identify with?
    • Does the primary speaker identify as a person of color? 
    • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below.
  • Select a Track
  • Type of Submission

  • What Skill Level is this Best Suited for?
  • Abstract Title (If your talk is selected, the Abstract Title you choose will be the Title shown in the conference schedule; often what attendees use as a starting point to determine if they will be interested in the talk. Choose your title carefully - make sure that it accurately describes what your talk will cover. )
  • Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).)
  • Audience (Describe who the audience is and what you expect them to gain from your presentation.)
  • Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)
  • Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)
  • Have you given this presentation before?
  • If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?
  • Additional Details & Speaker Agreements
  • Travel Funding
  • Code of Conduct
  • Slide Deadline Agreement

Draft proposals

How to find a way to a harmonized and collaborative CNF conformance verification?

  • Status: Submitted
  • Speaker info: Georg Kunz , Gergely Csatari 
  • Select a Track
  • Type of Submission

  • What Skill Level is this Best Suited for?
  • Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).)

    Cloud infrastructure and workload verification has a history in the telecom industry. As the workloads are dealing with extreme amount of traffic and/or extreme low latency requirements it is natural that they are more sensitive to their cloud platform than other applications. To decrease the cost of integration and expensive surprises during deployment there is a need to agree on what a telecom application can expect from its runtime environment and there is a need to certify if the applications expectations are correct and the platform can fullfill the expectations. Anuket defines a set of application requirements in its Kubernetes based Reference Architecture and plans to build the certification for it in its Anuket Assured certification program while CNCF announced in the 2022 KubeCon EU their CNF Certification program. While Anuket RA2 defines an opinionated Kubernetes distribution and its workload requirements ensure that the CNF is able to run in the distribution, the CNF Certification tests the adherence to cloud native principles. For a CNF vendor the ideal situation would be to run only one set of open source CNF certification tests, but due to the different targets of these certifications this is not the case today.
    In this presentation Georg and Gergely will discuss how these two communities could work together to achieve a good collaboration between the initiatives, how to draw the limit of the testings scope and how to minimalize the testing overhead for CNF vendors. For this the presenters will invite a set of key community members to disucss what is the common denominator of the tests and focus on the distinguishing parts.
  • Audience (Describe who the audience is and what you expect them to gain from your presentation.)

CNF vendors and network operators who are using the CNF-s and paying the integration bill.

  • Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

Due to the flexibility of cloud platforms and the sensitivity of CNF-s the integration of CNF-s and their platforms is a continuous issue. The industry tries to address this with different conformance programs. This panel is about the collaboration of these certification programs.

  • Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

We plan to invite some key contributors form the CNCF CNF Certification program, Anuket Assured and Anuket RC2 programs and initiate a discussion in the last part of the presentation.

  • Have you given this presentation before?

No

  • If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?

Yes

  • Additional Details & Speaker Agreements
  • Travel Funding
  • Code of Conduct
  • Slide Deadline Agreement
  • Panelists (4+1): Georg Kunz (Rihab), Gergely Csatari , Heather, Taylor (tentative), Olivier Smith  

How difficult can be to define a Kubernetes reference stack for CNF-s?

  • Status: submitted
  • Speaker info: Gergely Csatari , Riccardo Gasparetto Stori 
    • Primary Speaker Full Name
    • Primary Speaker Company
    • Primary Speaker Job Title
    • Primary Speaker Email
    • Primary Speaker Country of Residence
    • Primary Speaker Biography (provide a biography that includes your employer (if any), ongoing projects and your previous speaking experience)
    • Primary Speaker Twitter Handle
    • Primary Speaker LinkedIn Profile
    • What gender does the primary speaker identify with?
    • Does the primary speaker identify as a person of color? 
    • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below.
  • Select a Track
  • Type of Submission

  • What Skill Level is this Best Suited for?
  • Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).)

“Anuket specifications are a family of LFN initiatives to design, implement and test the conformance for Telco Cloud infrastructures. The aim of the specification work is to decrease the time and money needed to integrate Telco Cloud infrastructures and their workloads (Network Functions). Anuket specifications consist of a technology agnostic Reference Model (RM) and two technology-specific Reference Architectures and Reference Implementations, for OpenStack and Kubernetes, aligning with the Anuket Reference Model. In this talk Riccardo and Gergely will describe how RA2, the Kubernetes based Reference Architecture is enabling Telecommunications Providers and Vendors to deploy Containerised Network Functions (CNFs) on Kubernetes efficiently, and what’s new in Moselle, the current Anuket release, and what are the plans for the next one, Nile.”

  • Audience (Describe who the audience is and what you expect them to gain from your presentation.)

Architects in telecom network operators and in CNF and cloud platform vendors.

  • Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

This talk is a generic information sharing about Anuket RA2, a release update on its Moselle additions and information about the plans for Nile. 

  • Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

Participate in the hallway track after the session.

  • Have you given this presentation before?

A very similar about the previous release.

  • If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?

Yes

  • Additional Details & Speaker Agreements
  • Travel Funding
  • Code of Conduct
  • Slide Deadline Agreement

Working towards a shared model for Telecom Cloud Infrastructure, an Overview of Anuket

  • Status: submitted
  • Speaker info: Beth Cohen and Gergely Csatari 
  • Select a Track
  • Type of Submission

  • What Skill Level is this Best Suited for?
  • Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).):

Anuket grew out of a marriage of a requirements task force (CNTT) and a infrastructure test project (OPNFV).   The idea is to create a  single project that not only defines the reference requirements for infrastructure, but also creates and supports the code needed to test and valid these infrastructures,  As you can imagine, it is an LFN project with a difficult mission. In this session, the co-chairs of the Anuket TSC will explain the structure of Anuket sub-projects, the activities in these different sub-projects and how all of this works towards the mission. The presentation will cover release highlights from the latest Moselle release and provide some insights to the targets for the ongoing Nile release.

  • Audience (Describe who the audience is and what you expect them to gain from your presentation.)

Anuket is a project that was designed to be a joint effort by and for Telecom vendors and operators.  This session will allow those who are Anuket curious to learn more about it a and those always wanted to ask what Anuket was but never had the chance.

  • Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

Actors in the telecom industry need better understanding of the mission of Anuket and how the project works to make this mission reality.  Anuket is a project that supports other projects in LFN and across the Open Standards community in general.

  • Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

This is intended as a fully interactive session with lots of opportunities for the audience to participate and ask questions.

  • Have you given this presentation before?

No

  • If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite? Yes
  • Additional Details & Speaker Agreements
  • Travel Funding
  • Code of Conduct
  • Slide Deadline Agreement


Day 0, 1 and 2 in the life of an Edge Computing Deployment

  • Speaker info: Beth Cohen and Gergely Csatari Ildiko Vancsa 
  • Select a Track
  • Type of Submission

  • What Skill Level is this Best Suited for?
  • Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).):

Theory and use cases are important, but what happens when the rubber hits the road, or in other words, when your edge infrastructure is ready to be deployed and run in production.  During this session we will look at the dependencies and requirements for successfully launching and managing edge architectures in the field. Grouped around the Telecom concept of what happens over the three "days" it takes to take an edge infrastructure from development to deployment and into production. Starting from “Day 0”, the preparation/development phase before the deployment so to speak, and moving into “Day 1”, the actual deployment into the field, followed by “Day 2” or Day N (depending on who you talk to) which includes the management of the systems in production, each step calls for different components that interrelate with each other. 

    • Day-0: "product development". Focus on bootstrapping, develop templates
    • Day-1: "service delivery". Instantiate/customize templates according to customer needs and deploy them. Validation.
    • Day-2: "production/operations"
  • Audience (Describe who the audience is and what you expect them to gain from your presentation.)

Any person who is serious about Edge and operating an edge deployment in production.

  • Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

The Open Source community tends to focus  on Day 0 or requirements, but increasingly the telecom industry is looking for community to standardize operations and deployment activities.  While the nomenclature is borrowed from the  telecommunications industry, but the steps are applicable on a much wider scale and many more industries

  • Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

This is intended as a fully interactive session with lots of opportunities for the audience to participate and ask questions.

  • Have you given this presentation before?

No

  • If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite? Yes
  • Additional Details & Speaker Agreements
  • Travel Funding
  • Code of Conduct
  • Slide Deadline Agreement

Building an Open Reference Cloud Native Platform for Telco Cloud -- Benefits Cost Saving Throughout whole process of development, testing and deployment.

  • Speaker info:
    • Primary Speaker Dan Xu
    • Primary Speaker Company Huawei Technologies Co., Ltd.
    • Primary Speaker Title: Software Engineer
    • Primary Speaker Email: xudan16@huawei.com
    • Primary Speaker Country of Residence China
    • Primary Speaker Biography (provide a biography that includes your employer
      • Dan Xu is working in Huawei Technologies Co., Ltd for more than 6 years. I used to work on LFN OPNFV community for about 4 years and was the PTL of project Dovetail. Then she contributed in EdgeGallery community to be the leader of its CI/CD development for about 2 years. This year she is back to LFN Anuket community as the PTL of RI2 task force to do the k8s and infrastructure deployment. Dan Xu has given presentations and lead discussions about Dovetail Projects in ETSI Plugtest and OPNFV Plugfest for several times.

         
    • Primary Speaker Twitter Handle: None
    • Primary Speaker LinkedIn profile: None
    • What gender does the primary speaker identify with? Female
    • Does the primary speaker identify as a person of color? Asian
    • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below. None
  • Select a Track
  • Type of Submission

  • What Skill Level is this Best Suited for?
  • Abstract Title
    • Cost Benefits of Building an Open Reference Cloud Native Platform for Telco Cloud

  • Abstract 
    • Kubernetes-based Reference Implementation (RI2) is a project in LFN Anuket which focuses on providing reference k8s based Telco Cloud infrastructures for Telco Providers, Telco Cloud vendors and CNF software vendors. As a bridge of providers and vendors, RI2 gives providers a reference platform to test and choose both commercial Cloud infrastructures and CNFs running on it. Also it serves as a reference platform for Cloud vendors and CNF vendors to develop and test against. With this bridge, both providers and vendors can reduce the time and cost for developing, testing and integrating Telco Cloud infrastructures and CNFs. In this session, Dan Xu and Scot will give an introduction about what RI2 is, how to use RI2 to deploy a reference k8s based Telco Cloud infrastructure on bare metal and virtual machine, what’s new in Anuket Nile release, and what benefits users can get from RI2. Also will give a demo about how to use the tool kuberef to setup the k8s infrastructure on Baremetal.

  • Audience 
    • All suppliers/operators that are considering the ways to reduce deployment costs of their cloud native Network/Network functions
  • Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem.
    • Adoption of the Anuket specifications will improve the Time to Install and Market for Operators and Suppliers 
  • Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)
  • Have you given this presentation before?

No

  • If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?

Yes

  • Additional Details & Speaker Agreements
  • Travel Funding
  • Code of Conduct
  • Slide Deadline Agreement

Cultural Transition: Open Source Across Telecom and Hyperscalers

  • Speaker info:
    • Primary Speaker Scot Steele
    • Primary Speaker Microsoft
    • Primary Speaker Sr. Program Manager
    • Primary Speaker scotsteele@microsoft.com
    • Primary Speaker USA
    • Primary Speaker Biography (provide a biography that includes your employer (if any), ongoing projects and your previous speaking experience)
    • Primary Speaker Twitter Handle
    • Primary Speaker www.linkedin.com/in/scotsteele
    • What gender does the primary speaker identify with? Male
    • Does the primary speaker identify as a person of color? No
    • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below. None
  • Select a Track
  • Type of Submission

  • What Skill Level is this Best Suited for?
  • Abstract Title Cultural Transition: Open Source Across Telecom and Hyperscalers
  • Abstract 

    As telecommunications is a backbone service to society the industry has been highly regulated since its inception. Thus Telcos must demonstrate a culture of high levels of operational availability, reliability, and recoverability in performance and cost management. Hyperscalers are relatively new entities in the communications space that leverage a more collaborative/adoptive culture with lesser concern for the operational efficiency. Open-Source specifications/code, and Hyperscaler partnerships can provide new features and greater capacities to their consumers with reduced time to market and lower capital costs. However, deltas between the operational efficiency culture of operators and the collaboration/adoption of hyperscalers could inhibit success on either side of the relationship. We posit that resolving conflict between cultures would allow consumer access to beneficial features that would improve the operator’s bottom line at a time when labor and cost challenges impact the industry’s overall growth and health.

    In this discussion, we ask the question “How can Open-Source impact and affect culture to support telco industry growth and health?” We will explore insights and possible paths through the lens of a significant and multi-faceted telco hyperscaler partnership.

  • Audience: anyone Involved with technology selection, deployment, management, and leadership in the telco industry
  • Benefits to the Ecosystem Transforming the culture of the industry to a more trusting, collaborative, and adoption mentality will provide numerous benefits to all participants through the improving the speed of development and adoption. This will generally support lower cost of implementation.
  • Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)
  • Have you given this presentation before? o
  • If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite? Yes
  • Additional Details & Speaker Agreements
  • Travel Funding
  • Code of Conduct
  • Slide Deadline Agreement