Page History

...

• Participation - who will be contributing?
  • Shubhada - 50%
  • Patrick at 100%
  • Ryan at 100%
  • Taka at 100%
  • Scott is only consult for Casablanca; limited capacity
  • Aaron is 100%
  • Paul is consult on architecture
• Start planning sprint 0 & 1
  
  • Sprint 0  (6/13 - 6/27)
  • Sprint 1 (6/28 - 7/11)
  • Sprint 2 - (7/12 -  7/25)
• Casablanca
• Non-negotiable
• Upgrade to Karaf 4
  
  • APPC-938 (Patrick) - work with Ryan, target completion by end of Sprint 1
• ODL upgrade to Oxygen
  
  • Plan Sprint 2
• Migrate to MariaDB plus Galera
  • Assign to Aaron - put in Sprint 1
• S3P (Platform Maturity) - need guidance on targets for Casablanca
• Security
  • Badging
    • CII Passing we achieved 95%
    • CII Silver we had about 17%
  • Un-encrypted password in properties file
    
    • Need an ONAP strategy on how we handle this... need recommendation from Security subcommittee.. Taka will join security call to pose the question and come back with recommendation
  • Code Coverage - 60%? TBC
• Nexus IQ security items
  • More critical showing up.. need investigation
  • Randa to create story for tracking effort - DONE:
  • Sprint 3
• Resiliency - geo-red support
  • Level 3 ?
  • Aaron prime
• Scalability of DB
  • Aaron prime
• Documentation
• Contributions
  • Support for Reboot LCM action
  • Various defect fixes
• Additional items to address "Deployability" - …capacity will determine what can be scoped
• Removal of CDT proxy - find long term solution via ODL ? (see APPC-885)
  • anyone interested into investigating how this can be done with ODL?
• Improve OOM deployment  (have dependency on OOM project)
  • Couple of options discussed last week we can start investigating...
• Other items under discussion-pipeline…capacity will determine what can be scoped
• Support for auto scale out
• CDT tool evolution/convergence with SNDC proposal
• Secure DMaaP topics (have dependency on DMaaP)
• Misc...
  • CCSDK plans for Ansible - any impact for us? (Taka)
• Open issues to be worked out:
  • Labs for Casablanca?
    
    • Do we need more capacity?
    • How do we test geo-red ? do we need space in WindRiver and Tlab ?
  • Heat support -
    
    • What is the requirement for Casablanca?
  • Beijing to Casablanca - do we need to support upgrade vs fresh install?
    
    • Considerations - data migration...

6/27/18 - APPC Project Weekly Minutes

Participants: Randa Maher,Aaron Hay, Mayank Gupta Scott Seabolt, Patrick Brady, Ryan Young, Lathishbabu Ganesan,  Joss Armstrong, Jeff Hartley, Rebecca Lantz, Shubhada Vaze, Takamune Cho, Vidya Bijoor

Actions from last meeting:

• Patrick Brady to provide a knowledge share on the changes that upgrade to Nitrogen brings to APPC once he is done with the ODL upgrade.
  • 6/13/18 update: Patrick to review with Ryan, not sure it will have interest to all; better to write up a simple guide to refer back to.
• Aaron Hay provide a demo on OOM APPC deployment.
  • 6/13/18 update: further discussion needed with Aaron

New Actions Items:

• Randa to update Resources and Repositories for Casablanca
• Takamune Cho to investigate rationale for response of "unmet" to following question from CII Passing badge questionnaire.
  
  • The security mechanisms within the software produced by the project MUST use default keylengths that at least meet the NIST minimum requirements through the year 2030 (as stated in 2012). It MUST be possible to configure the software so that smaller keylengths are completely disabled.
• Need to setup RocketChat so that team can collaborate.
  
  • onap-appc channel created, but folks will need to create an account first so that I can add you to the channel
    

    • RocketChat URL:

    • Private Group: onap-appc

Agenda & Notes:

• Review planned scope, with special focus on:
  
  • Outstanding security items (https://bestpractices.coreinfrastructure.org/en/projects/1579#security)
    • Strong passwords - crypto - Taka will investigate - see action item above
    • Password Encryption - strategy is to use NFS mount to store certs and passwords; prioritize OOM first, then Heat (Ryan prime)
      • Need to also update deployment documentation
    • Nexus IQ - Criticals & Highs (Taka prime) -
    • CDT needs to use HTTPS - see story created by Patrick
  • ConfigScaleOut use case - work will be led by Ericsson (Joss and Latish - prime)
    
    • Scott Blandford and Lauren Lewis are leading the use case and requirements discussion
      • Scaling Use Case Extension
    • Need to get involved in weekly ScaleOut call hosted by Scott Blandford on Tuesdays at 9AM EST; also Control Loop call on Wed at 10AM would be another good call to participate in
      • TO DO: Randa add link to Control Loop recording from 6/27 meeting..
        
        • Recording has not been posted yet, but when it is, it will be here: 06-27-2018 Control Loop Sub Committee Weekly Meeting
    • Epic: APPC-1036
    • Team collaborators: Ryan Young and Scott Seabolt for AAI,  need to identify someone for client library...
    • 2 key areas of focus:
      • doing away with configuration data coming in payload; need to retrieve it from sources, namely AAI in this case. Need to collaborate with SO, AAI, and SDNC.
      • Controller Type: In the Manual use case, this was being explicitly set via VID, but in the auto use case, Multiple proposed option being discussed:
        
        • Use Consul to do service discovery, when a controller starts up have it register with Consul.  It should add tags for the VNF type/category(some link to the model) it supports.  SO can query Consul to see what controller services are up and what they support.  Choose the appropriate service endpoint based on the response from Consul  This option was abandoned in favor of policy pointed to via Service Model.
          
        • Use Policy to define the controller type - discussed today on Control Loop call....Listen to recording from today's Control Loop call to hear valuable discussion on this topic - see above.
        • Area of impact for APPC: APPC Client Library, need to support new approach, but also maintain backwards compatibility.....
• Review timeline (release calendar: Release Planning#CasablancaReleaseCalendar)
  
  • Development work runs from  June 28 - Sep 20 (assuming no date changes)
  • We work in 2 week sprints, so we have 6 sprints essentially
• Review resources
  • Welcome to Ericsson! Officially signed up to participate in Casablanca release with 2 folks: Joss and Latish