/
APPC Meeting Minutes - (Jun'18 - Dec'18 )

APPC Meeting Minutes - (Jun'18 - Dec'18 )

Mar 06, 2019

6/6/18 - APPC Project Weekly Minutes

Participants: @Randa Maher; @Mayank Gupta; @Patrick Brady; Scott Seabolt; @Aaron Hay;  @Ryan Young; @Arash Hekmat; @Lathishbabu Ganesan; @Rebecca Lantz (Ericsson); @shashikanth.vh; @Shubhada Vaze; @Takamune Cho; Vidhya Nerella; 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.

New Actions Items:

  • @Aaron Hay provide a demo on OOM APPC deployment.

  • Randa: Clean up JIRA queries in M1 planning template for R1 (check R2) - they don't show correct list. 

Agenda & Notes:

  • Key Beijing Dates:

    • Release Signoff - 6/7

    • Press Release - 6/12

  • Beijing - AAF OOM support - document workaround: Done: AAF Integration with APPC

  • CDT

    • https://gerrit.onap.org/r/#/c/50587/ - Why is Mayank changing the port after we validated our changes?

      • Looks like this is a needed change; someone changed the port originally defined in OOM project.  Patrick will review Mayank's input and +1 if agrees

  • Intent to participate for Casablanca as an active contributor ? calling for input

    • If you plan to participate in the Casablanca release as a contributor, please send PTL an email.

  • Retrospective: https://lf-onap.atlassian.net/wiki/display/DW/ONAP+Beijing+Retrospective+and+Lesson+Learned - input during meeting

    • What didn't go so well....

      • OOM - too much overhead due to duplication of configs

      • CCSDK dependency impacting ability to delivery well as we would have liked; getting ODL in the last sprint was a big challenge and limited what we could do.

      • Security guidelines from security team coming very late and making it difficult for teams to delivery - scope creep

      • Appc client library - disconnect on requirements - not enough time to do pairwise testing prior to M4 to uncover these disconnects

      • WindRiver lab stability - lost our VMs a few times; but most definitely improved since Amsterdam (good support for Steven Gooch, WindRiver is a great assest)

      • Network slowness - very slow to download docker images - sometimes it's LF, sometimes WindRiver - a lot of lost time

      • Too many code break with some of the contribution

        • Tighten down on Gerrit submits that refactor the code; submitter will need to provide evidence of run time testing.

        • Long term: automated regression suite that run to ensure no run time brake

      • IM service that easily accessible to broader community

        • IRC is still a problem for some

        • Can RocketChat be the solution? Issue: it's only http, not https

        • Skype for Business is a possible opinion

    • Things that went well

      • after all the Karaf issues, it ended up working - big challenge, but we conquered

      • cross team testing and collaboration when a lot better this release; was easier to get people on to help

      • Great teaming with SDNC, OOM, and Integration teams.

      • Good support & quick response from @Stephen Gooch when we had requests and issues in our WindRiver Dev env. Getting additional capacity was also very beneficial to allow multiple deployment types and releases to be tested.

      • Having our own Developer lab was very valuable!!!

      • Great management by team to document their testing

      • Investing in getting our own Jmeter test was a big payoff!!

        • TODO: Expand documentation to get people using jmeter to setup a runtime environment to test changes

        • Connect local appc instance to connect to AAI, VNF, etc.. in the windriver

        • Testing with JMeter

      • Participation from various members & companies (Nokia, TechM, ATT)  to help us get our code coverage!!!

  • Casablanca (theme "Ease of Deploy-ability"?)

    • Non-negotiable - these must be done.

    • Contributions being made to Casablanca

      • Support for Reboot LCM action

        • Difference between Reboot and Restart (already available in Beijing)

          • Restart does an os-stop then an os-start outlined in the API documentation above and outline in the conversation below:

            • Stop: - The action to stop a running server.

            • Start: - The action to start a stopped server.

          • Reboot server:

            • Valid values are HARD and SOFT.

              • A SOFT reboot attempts a graceful shutdown and restart of the server.

              • A HARD reboot attempts a forced shutdown and restart of the server. The HARD reboot corresponds to the power cycles of the server.

      • Various defect fixes

    • Additional items to address "Deploy ability" - …team capacity will determine what can be scoped in

      • Removal of CDT proxy - find long term solution via ODL config change (see APPC-885)

      • Improve OOM deployment  (have dependency on OOM project)

        • What improvements can we make independent of OOM - move configs to shared memory (maybe not needed if we do Ryan's proposed feature? (Aaron)

      • Any other thoughts on improving deploy ability?

        • upgrade all of our properties to use configuration admin (a function of ODL/OSGI) - @Ryan Young to open a Story for tracking

          • benefit to change properties and it be dynamic, i.e., no need to restart APPC, this will also address the limitation we have with OOM, which does not allow restart, you have to rebuild the pod

    • Other items under discussion-pipeline…team capacity will determine what can be scoped in

      • Support for auto scale out - discussions being led by @Scott Blandford and @Lauren Lewis

      • CDT tool evolution/convergence with SNDC proposal to align on one controller tool

      • Secure DMaaP topics (have dependency on DMaaP)

 

6/13/18 - APPC Project Weekly Minutes

Participants: @Randa Maher, @Patrick Brady, @Aaron Hay, @Takamune Cho, @Shubhada Vaze, @Scott Seabolt, Paul Miller,

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

  • Randa: Clean up JIRA queries in M1 planning template for R1 (check R2) - they don't show correct list.-CLOSED

New Actions Items:

Agenda & Notes:

  • 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 (Ericsson), @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

      •  

      • 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

      • 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

      • 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

 

7/11/18 - APPC Project Weekly Minutes

Participants: @Randa Maher, @Takamune Cho, @Scott Seabolt, @Patrick Brady, @Jeff Hartley, @Ryan Young, @Joss Armstrong, @Lathishbabu Ganesan, @Michael Zinnikas. 

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

  • @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.

New Actions Items:

  • Setup working session with Latish and Joss to demo ConfigScaleOut in WindRiver dev lab.Prime: Scott,

Agenda & Notes:

Comments