Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

03/28/18 - APPC Project Weekly Minutes

Participants:Randa Maher; Patrick Brady; Scott Seabolt; Shubhada Vaze; Former user (Deleted); Takamune ChoRamya Balaji; Vidhya Nerella; Veer RajasekharActions from last meeting:

  • Scott SeaboltAaron Hay to work together to pull together some lab diagrams for WindRiver lab setup for APPC usage (clustered vs non-clustered environments)
    • Update: 2-21-18: Information started to be populated here: APPC WindRiver Lab
    • Update: 3/21/18: Pending; however, note that all IP info is provided on wiki, diagram will be added later as time permits give other higher priority items.
  • Aaron Hay to deploy an instance of vDNS VNF in lab.
    • Update: 3/14/18: Worked with Stephen and Eddie, but issue in APPC env. Got Heat templates from Marco, but ssh plublic key not getting integrated with public instance and can't get into them. Reaching out to Marco for assistance.
    • Update: 3/21/18: Have not heard back from Marco; Randa will follow-up with Marco.
    • Update: 3/28/18: Marco deployed vDNS in our lab (VMs are named zdfw1…); however, done using Heat templates, so AAI is not populated with VNF information. Will consider this item CLOSED. AAI data will be tracked separately.
      Image Added
  • 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.
  • Randa Maher setup call to discuss testing in WindRiver APPC dev lab after we get Beijing successfully deployed.
    • Update: 3/28/18: Discussions started, but until we have a working Beijing environment
  • Takamune Cho will bring up CDT using docker from Nexus to validate it deploys correctly.
    • Update: 3/28/18: CLOSED. Scott validated that you can access the CDT UI. Amaresh working to configure it to point to APPC instance.
  • Aaron Hay and Scott Seabolt will deploy APPC WindRiver lab with Beijing release today.
    • Update: 3/28/18: CLOSED; an intance with Beijing was deployed in the singleton lab
  • ry303t will check with Dan to see if he wants to put AAF bundles in CCSDK since all SDNx and APPC both plan to use it.
    • Update: 3/28/18: Query sent to Dan, but no response yet; however, given timeframe we will pull dependency from AAF. I'm going to consider this CLOSED.

New Actions Items:

Agenda & Notes:

  • M4 Ramya to identify the minimum VNF AAI data that is needed to validate ScaleOut. The work around that was provided only addressed the template model name. 

Agenda & Notes:

  • M4 review planned for 3/29 with TSC
  • Status on outstanding M4 items:
    • ODL Upgrade
      • Still having isues with feature installs freezing with no error messages; SDNC probably did not see this issue since they only install a small number of feature (5 or 6) compared to APPC's 28, plus APPC is using bundle wrapping.
      • Additional problem encoured today is a method APPC uses from CCSDK from their AAI services appears to have been removed. High Priority JIRA opened (CCSDK-229)
    • AAF Integration
      • We are still waiting on AAF-91 to submit their changes and make image available, so APPC cannot complete until that happens
    • OpenEcomp name space change (APPC-13)
      • Dependency on SDC to complete. Waiting on following to be available in Nexus.  <artifactId>openecomp-tosca-datatype</artifactId>
    • Code Coverage
      • Currently at 48.8%; will not hit 50% by Code Freeze on 3/29. Need more time.
  • Sprint 4 was closed; anything not completed was moved to Sprint 5 or put into backlog
  • WindRiver Dev lab
    • CDT configuration
      • Enviroment.ts is the name of the properties file.
      • All endpoints(URLS/ports) are supposed to be configured there.
    • DMaaP status?
      • Scott still working on this with Sunil; DMaaP sitll not useable in Beijing.
  • Vacations:
    • I will be out next week: 4/2 - 4/6; Scott will run the call next Wed., 4/4/18
  • Concern raised..
    • Code changes being introduced under junit or Sonar Jira's are extending beyond what is actually needed and some of these changes have broken run time functionaliy. How can we safeguard against this? Unless you have a very high degree of confidence and are extremely familiar with APPC code and functions, you should not be attempting to refactor the code.  Run time breaks are very difficult and virtually impossible to catch in a code reviews.