You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Release 2 target date is November 30th 2019.

Define area of focus

  1. Virtual meeting to start to have a session to discuss all of the agenda items.
  2. Different patches from different blueprints need to be up-streamed.
  3. Need a consistent framework
  4. New blueprints have been committed for R2.
  5. Want to increase standards on Release 2.
  6. June 19th should be a topic to discuss R2 in mini summit.
  7. Validation Project test layers and test cases
  8. Incubation Self Certification in R2?

Release 2 Requirements

  1. High Level Overall Requirements
  2. CI, Blueprint Validation Lab Sub-Committee Requirements
    1. Present Pod Topology document.
    2. Peering w/LF Jenkins.
    3. Push logs through Nexus.

    4. Usage of topics for release

      1. Releases >= 1.0 (e.g. 1.xyz, 2.xyz etc) are reserved for BP that have been approved as Core by the TSC (considered ‘GA’ quality).

      2. Releases <1.0 (e.g. 0.xyz etc) are reserved for projects that have not reached the Akraino Core level (i.e. anything that is in Incubation (‘alpha’ quality) and Mature (‘beta’ quality).

    5. Enforcement of Static Code Analysis through SonarCloud (SaaS), WIP LF Release Engineering & Security Subcommittee.

  3. Security Sub-Committee Requirements
  4. Blueprint Validation Framework Feature Project Requirements
  5. Documentation Sub-Committee Requirements
  6. API Sub-Committee Requirements
  7. Community Sub-Committee Requirements
  8. Process Sub-Committee Requirements
  9. Upstream Sub-Committee Requirements


06/17-19/2019 Technical Mini-Summit

Day 3, Wednesday,  

Room: Fantasy Island

Time

Topics, Zoom Link

10:45 am - 12:00 pm

Akraino Release 2.0 Planning

10:45-11:15 - CI Sub-committee R2 inputs, goals, & Planning - Cesar Berho

 Presentation


11:15- 11:45 - Community Sub-committee R2 inputs, goals & Planning - Tapio Tallgren

Going forward, we had the idea to present all the Release 1 projects in the community call and record the presentations. This way we would have documentation about the status of all of the projects available. All of the Release 1 projects are listed below and also on the page https://wiki.akraino.org/display/AK/Technical+Community.

I would appreciate if the PTLs would sign up on that page, otherwise I will have to find volunteers. Suggest we start the process on July 11th.


11:45- 12:15 - TSC Goals for R2 - Kandan Kathirvel & Tina Tsou 

1:00 pm - 3:30 pm

Akraino Release 2.0 Planning

1:00-1:30 - Security Sub-committee R2 inputs, goals & Planning - Ken Yi

1:30-2:00 - Documentation Sub-committee R2 Inputs, goals & Planning - sujata tibrewala


2:00-2:30 - Upstream Sub-committee R2 inputs, goals & Planning -Wenjing Chu

Upstream Dependency Matrix and Upstream Project Information needs to be updated at SEBA OS and ONAP different features.


2:30-3:00 - API Sub-committee R2 inputs, goals & Planning -Vikram Siwach

Akraino BP API Standards

a)Community whitepaper ( AI: API SC)

b)Explore possibility of actionable plan with O-RAN, ETSI MEC, LF Edge projects, etc.,

Do a joint press release to publicly annonce plans ( AI: API/Community/TSC Chair/Co-Chair/Marketing subcommittee)


3:00 -3:30 - Process Sub-committee R2 inputs, goals & Planning - Andrew Wilkinson



  • No labels