/
1H/2025 - Top Priorities

1H/2025 - Top Priorities

  • CNF Test suite code cleanup/refactoring, hardening, and test cleanup (6 votes)

  • Multiple releases containing code cleanup, maintenance, fixes, etc.

    • Still a lot remaining in this area (in particular with gates, Github actions, pipeline)

    • 71 commits

    • image-20250717-152515.png

       

  • Support fixes and enhancements for project Sylva (5 votes)

  • Cedric and Martin provided significant support to Sylva Validation teams

    • Enhancements and bug fixes during period when validation using CNTi test suite was in early stages

    • CNTi test suite is now mandatory in each Sylva Validation (a good sign that our tooling is of value)

  • Identify and establish new collaboration with other communities, vendors, operators (5 votes)

  • free5GC collaboration has been discussed and general positive view that collaboration could benefit both projects (very little work done so far)

  • AWS has started to participate

  • China Mobile has expressed possible interest

  • Titan.ium has contributed issues and has done some internal testing using the CNTi test suite

  • Good opportunities but challenge with smaller community

 

 

A

B 

C

D

E

F

G

H

I

Martin

2

 

 

2

 

 

1

 

 

Cedric

1

 

1

2

1

 

 

 

 

Olivier

1

3

 

1

 

 

 

 

 

Rich

1

2

 

1

 

 

 

 

1

Total

5

5

1

6

1

0

1

0

1

 

The CNTi Community identified, discussed, and then voted on our 1H/2025 priorities based on the following:

Potential CNTi priorities for 1H/2025 are listed below. Voting is now open (see bottom of this wiki page) and we expect to finalize by Tuesday Feb 7th, 2025.

A. Support fixes and enhancements for project Sylva (Existing consumers of the CNTi Test Suite)

How does this help CNTi: Drives further alignment for use of vendor neutral best practices across cloud native communities.
How can we measure if we have been successful: If CNTi test suite results become part of Sylva validation (not just optional)

B. Identify and establish new collaboration with other communities, vendors, operators

How does this help CNTi: Expands contributors and stakeholders and helps drive use of vendor neutral best practices across cloud native communities.
How can we measure if we have been successful: If we have at least one new collaboration, vendor, or CSP

C. Test CNF Test suite against proprietary 5G CNFs (can come via Sylva and/or CNTi beta certification)

How does this help CNTi: Ensures the CNTi test suite works as expected across all available tests.
How can we measure if we have been successful: If at least one proprietary CNF executing and passing all tests.

D. CNF Test suite code cleanup/refactoring, hardening, and test cleanup

How does this help CNTi: Increase quality, security, and reliability of the CNTi test suite.
How can we measure if we have been successful: DISCUSS metric/KPI/etc that we might use.

E. Support of CNF deployment using K8s operators (could potentially be an opportunity to work with Nephio community)

How does this help CNTi: Provide support for CNFs that have more complex deployment/lifecycle management needs.
How can we measure if we have been successful: DISCUSS

F. Explore similar projects for CNF testing (e.g. RedHat or others open-source communities) for purposes of identifying new tests or exploring possible synergies.

How does this help CNTi: Look for established best practices and tests that can be leveraged to expand CNTi tools and/or find ways to grow community with collaboration.
How can we measure if we have been successful? If we implement new tests and/or establish a new collaboration.

G. Extend CNTi Testsuite usage in other projects, not necessarily telecom-related

How does this help CNTi: Expands the applicability and value of CNTi beyond networking. Telecos have other areas in their digital architectures (BSS/OSS) as well as network edge that could benefit from use of cloud native paradigms and best practices.
How can we measure if we have been successful: If we find new consumers and/or contributors for teleco areas outside networking.

H. Implement triaging of issues (important as we scale)

How does this help CNTi: Would help us to organize and prioritize issues that are worked on.
How can we measure if we have been successful? DISCUSS

I. Refocus our efforts on Best Practices and Testing Tools (less or no efforts on Certification).

How does this help CNTi?
MM: Best Practices must be in our focus. How we do it must evolve.
CO: Fully agrees.
OS: Best Practices motivate the tests we have or add to the test suite. Certification, IMO, will only be of value if the operator community shows an interest and sees value in certification.
CO: Agrees
RL: Agrees, Best Practices must be a focus.
More than one think certification may not be our focus going forward.
How can we measure if we have been successful?

 

PRIORITY VOTING

Each member of CNTi community has a total of 5 points to assign to the above priorities. All points can be used to vote for one item or multiple.

Assign a total of 5 points under your initials:

Martin M: A(2), D(2), G(1)

Cedric O: A(1) C(1) D(2) E(1)

Olivier S: A(1), B(3), D(1)

Rich L: A(1) B(2) D(1) I(1)

Add your name if not listed and you would like to vote on 1H/2025 priorities for CNTi. Thanks!