Versions Compared

Key

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

...

Attendees:



START RECORDING

425b2b0a-557c-3c0c-b515-579789cceedb
https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/configuration/AAF_4.1_config.html
Will need to add the file for the haproxy in values.yaml since a limit on secrets meant we had to bake it into the haproxy container previously

New certificate expires 26 Mar 2020

 

James Forsyth will open Jira tickets to update the keystores in the master branches of the mS that use https

  •  

    Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core

    • GraphGraph is coming, depends on expanding schema-service API
    • RestClient updates are potentially being contributed by community members
    1sparky shows sonar failingJames Forsyth

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-2354


    2Bug Review

    JIRA Issue Count:

    Jira
    serverONAP JIRA
    jqlQueryproject = AAI AND issuetype = Bug and status not in (Closed, Delivered) ORDER BY fixVersion ASC, priority DESC, updated ASC
    counttrue
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    32
    Dublin Status 1James Forsyth
    • Encourage our clients to migrate off named query
      • To support Policy code change to custom queries
        Jira
        serverONAP JIRA
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyPOLICY-1266
        , could this be fixed?
        Jira
        serverONAP JIRA
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyAAI-2351
    • Trying for Silver badge and Level 2 on Security; 50% code coverage on repos
    • Resiliency and fault tolerance; meeting notice never published,
    3
    4Dublin Status 2 / OOM helm charts
    • Moving Helm charts into AAI repos
    •  Pavel Paroulek is the AAI contact for doing the helm chart migration, info passed along to Mike Elliot
    • Migration of the oom / aai charts to an new repo that we will have commit access to. Harish tried to preserve the history on the existing set of files, but there was no way to do it because the commit messages would violate the 50 character limit. So we will lose history on the commits and do the push as a new code drop.
    • Jessica found a way to do it
    • Not sure if this would be pushed into El Alto release
    54
    Dublin Status 3James Forsyth
    • Volumed run-time generated certificates are possible
     James Forsyth Our AAF-issued certificate expires at the end of May.

    subject=/C=US/O=ONAP/OU=aai@aai.onap.org/OU=OSAAF/CN=aai

    issuer=/C=US/O=ONAP/OU=OSAAF/CN=intermediateCA_1

    notAfter=May 31 12:19:59 2019 GMT

    Need to generate new cert that expires in June 2021 and publish in the Casablanca emergency maintenance release.
    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId
    keyTSC-120
    65
    Dublin Status 4James Forsyth
    • code coverage to 55% for Dublin
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyAAI-2219

    Champ slipped below 55% with latest commit.

    •  Tian Lee will do babel, model-loader, champ, gizmo, event-client, spike, rest-client, validation
    •  Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
    •  James Forsyth create ticket for El Alto for sparky, rolling back because of sonar failure
    •  Venkata Harish Kajur will check aai-common, resources, traversal, graphadmin, cacher, schema-service (which probably already have the setting)
    •  Add thresholds to all repos that are above 55% so it doesn't happen again
    •  For setting the threshold on each repo, set it to the current percentage, so if it's is at 62.7%, set the threshold to 0.62
    •  

       <jacoco.line.coverage.limit>0.68</jacoco.line.coverage.limit>

      Sonar job for Dublin has been changed to using line coverage.

      Code Block
        <execution>
                              <id>default-check</id>
                              <goals>
                                  <goal>check</goal>
                              </goals>
                              <configuration>
                                  <dataFile>${project.build.directory}/coverage-reports/jacoco.exec</dataFile>
                                  <rules>
                                      <!--  implementation is needed only for Maven 2  -->
                                      <rule implementation="org.jacoco.maven.RuleConfiguration">
                                          <element>BUNDLE</element>
                                          <limits>
                                              <limit implementation="org.jacoco.report.check.Limit">
                                                  <counter>LINE</counter>
                                                  <value>COVEREDRATIO</value>
                                                  <minimum>${jacoco.line.coverage.limit}</minimum>
                                              </limit>
                                          </limits>
                                      </rule>
                                  </rules>
                              </configuration>
                          </execution>


    76
    Dublin Use Cases

    Epic-of-epics:

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-2107

    5G Use Case (Dublin)

    BBS Broadband Service Use Case (Dublin)

    CCVPN Use Case (Dublin)

    Change Management Dublin Extensions

    Fine Grain Placement Service (F-GPS) Edge Automation (Dublin)

    OpenSource Access Manager (OSAM) Use Case

    K8S based Cloud Region Support

    Tony Noori from AT&T will identify the ONAP POC for system engineering for AAI modelling. This person will coordinate schema changes, watch the use case wiki, jira, perform gerrit reviews, etc.

    Analysis: AAI R4 Use Case and Functional Requirements Impacts

    JIRA Epics count:

    Jira
    serverONAP JIRA
    jqlQueryproject = AAI AND issuetype = Epic AND fixVersion = "Dublin Release" ORDER BY created DESC
    counttrue
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    87
    El Alto StatusJames Forsyth
    • No 2 way TLS in Dublin; James Forsyth will socialize early in El Alto, Due
    • pnf-id change pushed to El Alto during Architecture review AAI R4 Architecture Review - 5 Mar 2019
    • API version update for El Alto should be co-ordinated for earlier in the cycle
      • needs a checklist of things to be updated, including yang classes
        Jira
        serverONAP JIRA
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyAAI-2351


    JIRA Epics count:

    Jira
    serverONAP JIRA
    jqlQueryproject = AAI AND issuetype = Epic AND fixVersion = "El Alto Release" ORDER BY created DESC
    counttrue
    serverId425b2b0a-557c-3c0c-b515-579789cceedb

    98
    New business
    Please add new items below
    109
    Selenium Tests in SparkyArul NambiWant to share in the community potential selenium changes for the sparky UI
    1110
    Container Images

    Container Image Minimization Guidelines

    James Forsyth will ask integration team if we can use the AAI tenant space in windriver environment

    1211
    Run AAI containers as non-root user

    https://wiki.onap.org/display/DW/Best+Practices

    • The Docker and Kubernetes engines may run as root until such time as the products support non-root execution.
    • Applications may run as root within a container.
    • The process ID of a container must not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID.
    • Containers may run with root privileges.
    • Project containers that run as the root ID must document this in the release notes along with the functionality that requires the container to run as the root ID.

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-2172

    1312
    Dublin 5G Use Case

    Go to [usecase] Platform Evolution for Use Case Realization w/ SO, AAI, DCAE, SDC, VID, SDNC

    1413

    Traversal Nodes query documentation

    J. Ram Balasubramanian

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-2202
    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-2383

    •  Documentation on the search/nodes-query API is missing. James Forsyth needs to find it and publish it.
    •  @Keong will create a new Jira for El Alto for the documentation
    1415
    AAI achitecture documentation

    Understanding the architecture of AAI is not easy - hard to understand how the code is laid out and how things flow. Need documention which will describe how the microservices are connected, which repos support which functions, etc. Pavel Paroulek says that he had to reverse engineer the dependencies to see how the repos are connected. Recommended to focus on the resources repo for understanding the core function of AAI.

    1615
    API version documentation

    Is v15 API for Dublin release?

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-1811

    Why does schema-service now have v16 files?

    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-2161

    •  James Forsyth Document nodes wiki and add explanation about presence of the v15 file. Should add v14-v15 changes to release notes.
    1716
    Resources Nodes query documentation incomplete

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAAI-2384

    API Documentation needs update, as both of these URL paths are equally valid:

    • /aai/v13/nodes/{plural}/{singular}
    • /aai/v13/nodes/{singular}

    See also: https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/nodesQuery.html#api-uri

    • Add to the Dublin Release for the documentation of the singular nodes query
    1817
    AAI Dublin wiki updates

    Added pages to AAI in Dublin Release

    Please keep these procedures up-to-date with latest Dublin code.


    1918



    Open Action Items

    ...