2019-04-25 AAI Developers Meeting

Keong Lim

OPEN

From https://lists.onap.org/g/onap-discuss/topic/31317665

It is an payload issue with in the following PUT request

PUT /aai/v11/network/generic-vnfs/generic-vnf/example-vnf-id-val-92494/relationship-list/relationship

You currently have the payload as following:

{
                "related-to": "vserver",
                "relationship-data": [
                                {
                                                "relationship-key": "cloud-region.cloud-region-id",
                                                "relationship-value": "example-cloud-region-id-val-56689"
                                },
                                {
                                                "relationship-key": "tenant.tenant-id",
                                                "relationship-value": "example-tenant-id-val-51834"
                                },
                                {
                                                "relationship-key": "vserver.vserver-id",
                                                "relationship-value": "example-vserver-id-val-51834"
                                }
                ]
}

You are missing the cloud-owner which is part of the key so you should have sent the payload as below:

{
                "related-to": "vserver",
                "relationship-data": [
                                {
                                                "relationship-key": "cloud-region.cloud-region-id",
                                                "relationship-value": "example-cloud-region-id-val-56689"
                                },
                                {
                                                "relationship-key": "cloud-region.cloud-owner",
                                                "relationship-value": "example-cloud-owner-val-45051"
                                },
                                {
                                                "relationship-key": "tenant.tenant-id",
                                                "relationship-value": "example-tenant-id-val-51834"
                                },
                                {
                                                "relationship-key": "vserver.vserver-id",
                                                "relationship-value": "example-vserver-id-val-51834"
                                }
                ]
}

In order to avoid these kind of issues in the future, there is a much simpler way to create the relationship with the following payload:

{
                "related-to": "vserver",
                "related-link": "/cloud-infrastructure/cloud-regions/cloud-region/example-cloud-owner-val-45051/example-cloud-region-id-val-56689/tenants/tenant/example-tenant-id-val-51834/vservers/vserver/example-vserver-id-val-51834"
}

Discussion:

• The cloud-region schema element is unusual in that it has a two-part key i.e. "cloud-owner" and "cloud-region-id". There are not many other usages of it ("ctag-pool" , "service-capability" and "route-target" are three others, out of over 100 other schema elements)
• Is it possible to enhance the error message to indicate that part of the key value is missing from the relationship-data?
• Is it time to deprecate the relationship-data and switch over to using the related-link only?
• Is there any modeling guidance that would steer new designs away from using multi-part key for schema elements?
• Are there other caveats to using the multi-part key design for schema elements?

Venkata Harish Kajur

IN PROGRESS

IN PROGRESS

Former user (Deleted)

IN PROGRESS

Is there a guide for the description of the error message and the error codes? How are new error states (message + code) added?

• William LaMont will send James Forsyth the output of a script that formats the error.properties file to make a wiki page and readthedocs
• James Forsyth should commit that script and create a wiki for the error properties
  

Paul-Ionut Vaduva

IN PROGRESS

Reduction in size is mostly onf aai-common image as that based on ubuntu.

2/7 - Move the base image to be a part of ONAP Build, maybe aai-common repo

• Venkata Harish Kajur will create a Jira for it in Dublin Release
• Using the Jira AAI-1033 to push the aai-common Dockerfile

Move the aai-common Dockerfile RUN into the resources, traversal, graphadmin, cacher, schema service microservice

26th Mar: Also AAI-2235 - Getting issue details... STATUS

Build the aai-common and haproxy images using alpine in the integration lab.

Dmitri from CIA team is working on the images from aai-common alpine to build our microservices and work on testing those changes now

IN PROGRESS

Some of our top level OOM deployment artifacts are not unique (i.e. don’t take namespace into account as all other deployables), is that intentional?

Lets move this to El Alto for now.

Venkata Harish Kajur will create an Jira task and remove this item from agenda

• Venkata Harish Kajur will look into which secrets and configmaps in the oom that we are not using the proper release name as the prefix

IN PROGRESS

Under OOF Homing and Allocation Service (HAS) section, Dileep Ranganathan wrote about Project Specific enhancements:

Optimize - AAI cache

• Use MUSIC or any other alternative in memory caching like Redis etc?
• Optimize flavor retrieval from A&AI and Cache the information if necessary

See also OPTFRA-268 - Getting issue details... STATUS / OPTFRA-291 - Getting issue details... STATUS

Similarly to the "AAI too slow for Holmes" item below, this introduction of extra caching of AAI data is a worrisome development and sad indictment of the performance of the system architecture.

For holmes, we could possibly create a custom query to address it.

What can we do about this?

Would the AAI Cacher AAI-1337 - Getting issue details... STATUS help to improve performance?

IN PROGRESS

Bin Yang and Lianhao Lu (Deactivated) wrote in MULTICLOUD-274 - Getting issue details... STATUS :

HPA telemetry data collection and make it persistent in A&AI, from which OOF can leverage during its decision making process.

1.  Multi-cloud to collect the data from time-series data services like Prometheus (http://prometheus.io) or openstack Gnocchi, and push them to A&AI based on the data recording & aggregation rules.

and

The reason why we propose here is that VES mechanism doesn't store the telemetry data into A&AI. And OOF now can only get those kind of data from A&AI.

Some concerns:

• how much additional load will this place on AAI?
• will AAI cope with this load?
• is AAI suitable for "time-series data"?
• is "telemetry data" considered to be "active & available inventory"?
• should OOF access the telemetry/time-series data via other means (not AAI)?
• AAI API latency (4~6 second per request as benchmarked in CMCC lab) could be a problem

IN PROGRESS

Looking at AAI usage in OOF - HPA guide for integration testing by Dileep Ranganathan, wondering whether there is a better way to bootstrap AAI test data?

Generating AAI data

Note: Required only if the Multicloud has no real cloud-regions and HPA discovery cannot happen.

If Multicloud team has data for creating the Cloud-region and doesn't have the HPA, then please update the existing data with the flavors with HPA.

1. Import the postman collection CASABLANCA_AAI_postman.json
2. To add/remove HPA Capabilities edit the flavors section in the body of PUT Cloud-Region{x}
3. Once all the necessary Use postman to add the complex and cloud regions in the order specified below
   (snip screenshot of specific sequence)
4. Use the GET requests to verify the data.
   (snip screenshot of specific sequence)

Similarly, Scott Seabolt and J / Joss Armstrong wrote for APPC Sample A&AI Data Setup for vLB/vDNS for APPC Consumption and Script to load vLB into AAI:

The below put_vLB.sh script can be used to submit the vLB data to A&AI in order to run ConfigScaleOut use case. This script and referenced JSON files are used on an AAI instance where the cloud-region and tenant are already defined.

Similarly:

• TEST-133 - Getting issue details... STATUS
• INT-705 - Getting issue details... STATUS
• vCPE Use Case Tutorial: Design and Deploy based on ONAP

Related AAI-1948 - Getting issue details... STATUS on the brittleness of the ReadTheDocs links to data files.

One for VIM: How-To: Register a VIM/Cloud Instance to ONAP and AAI-1928 - Getting issue details... STATUS

Potential issues:

• fragility of static import data file w.r.t. schema changes and version upgrades for each ONAP release?
• how "common" is this knowledge, i.e. what to load, where to get it, who else should be using it, etc?
• should it be automated/scripted, rather than manual steps to bootstrap?
• should it be a simulator program or test harness, rather than a static data file?
• should it reside within AAI CI/CD jobs for maintenance and upgrade of schema versions?
• who maintains the data itself? Is there a "data repository" which can be delegated to other teams, e.g. like documentation repository links in git?
• how many other teams have similar private stashes of AAI bootstrap data?
• does it need to be published at a stable URL to avoid linkrot?

IN PROGRESS

Dénes Németh wrote in AAI-1104 - Getting issue details... STATUS :

In think it would be good to answer what is the meaning of the field (collection of PEMs of the CA xor URL)

Questions:

1. Is AAI intended to strictly prescribe how the fields are used and what contents are in the values?
2. Or does AAI simply reflect the wishes of all the client projects that use it to store and retrieve data?

Even if (1) is true, AAI is not really in any position to enforce how clients use the data, so really (2) is always true and we need to consult the original producers of the data and the ultimate consumers of the data to document their intended meanings.

How do we push to have documentation on the purpose and meaning of the fields in AAI?

Where does all this documentation go?

Should the documentation be backed up by validation code?

See also discussion about AAI in 2018-11-28 ExtAPI Meeting notes

29th Nov: Started on new wiki page AAI Schema Producer-Consumer Pairings

18th Apr: Can we have this documentation go into ONAP in a generic way?

24th Apr: See also questions about "sw-version" in https://wiki.onap.org/display/DW/5G+-+PNF+Plug+and+Play?focusedCommentId=63996633#comment-63996633

IN PROGRESS

Now raised in JIRA AAI-2386 - Getting issue details... STATUS

Keong Lim

IN PROGRESS

• if I had some AAI data with attributes that are strings but nominally contain date/timestamps, is there a way to query for a particular range of values?

• is there a way to do partial match? regex?
  PUT /aai/v13/query?format=raw

  {"gremlin": "g.V().has('aai-ts', org.janusgraph.core.attribute.Text.textContains('URL'))"}

  https://github.com/JanusGraph/janusgraph/blob/master/janusgraph-core/src/main/java/org/janusgraph/core/attribute/Text.java

• Invite Arul Nambi and CT Paterson to next week's dev call to talk about how sparky/elastic does partial/range matches

Keong Lim

FREEMAN, BRIAN D asked on Re: Backup and Restore Solution: ONAP-OOM :

what would be the approach to backup an entire ONAP instance particualarly SDC, AAI, SDNC data ? would it be a script with all the references to the helm deploy releases or something that does a helm list and then for each entry does  the ark backup ?

What is the AAI strategy for backup and restore?

What is the overall ONAP strategy for backup and restore?

Should it be unified with the data migration strategy as per "Hbase to Cassandra migration" on 2018-11-14 AAI Meeting Notes?

• James Forsythwill raise the topic of having backups and restore functionality in ONAP - if it is feasible, on the roadmap and what others PTL think

Jimmy didn't directly raise the topic but there was movement - Keong Lim asked "if istio service mesh is a no-go, is there a replacement for secure onap communications?
is backup/restore/upgradability included in s3p?"

Michael O'Brien replied that a reference tool set for backup and restore was introduced in Casablanca:  Backup and Restore Solution: ONAP-OOM

Mike Elliott said he would look at Brian's question, AAI will provide support as needed.

Former user (Deleted)

ON HOLD

There are 2 types of logging in the services

• one read from EELFManager
• the other Logger log = Logger.getLogger( ...

Is that correct? Shouldn't there be just 1 type?

1st Nov:

After Casablanca release investigate logging guidelines and figure out what library to use in order to unify logging within A&AI

26th Nov: See also ONAP Application Logging Specification - Post Dublin

29th Nov: how does this fit with LOG-877 - Getting issue details... STATUS ?

Former user (Deleted)

IN PROGRESS

Could we disable unused (i.e. not integrated) A&AI web services, so that the deployment is faster and the resource footprint is smaller? e.g. Champ (any other ws?)

Motivation: Decrease the resource footprint for A&AI (ONAP) deployments

Idea: we could support 2 different deployments 1. full (normal) deployment and 2. barebones deployment. The point of the "barebone" deployment would be to deploy only the essential services necessary for proper functioning of A&AI (leaving out services like cacher, sparky, graphadmin, having 1 cassandra node instead of 3 or 5 etc).

In order to reduce hardware/cloud costs (mainly the memory footprint) it could be beneficial to support a minimalistic A&AI deployment.

1st Nov:

Venkata Harish Kajur Former user (Deleted) - investigate how to disable/enable charts in A&AI so we can create a core group of pods which handle the use-cases and than extended group will all the services. Consider a group of unused/unintegrated services (like Champ). Consider other possible groups (like GUI?)

• James Forsythcreates a JIRA ticket to define the list of AAI subprojects and create the categories (essential, full "experience") for the OOM deployment AAI-2025 - Getting issue details... STATUS

IN PROGRESS

IN PROGRESS

AAI-1989 - Getting issue details... STATUS

APPC-1245 - Getting issue details... STATUS : Takamune Cho pointed to inherited CCSDK functions, so added a new case to follow-up there too

POLICY-1278 - Getting issue details... STATUS

VID-355 - Getting issue details... STATUS : ittay has provided an update with 2 known queries used.

CCSDK-962 - Getting issue details... STATUS : Raised to Dan Timoney based on info about APPC component.

Need to replace custom queries currently in use by these systems (and others?) in Dublin toward the retirement of the named-query API in Dublin

1. Coordination with the ROBOT team needed for data population
2. Coordinate with each team (POLICY, VID...) to have the specific data for each named-query

Christopher Shang is leading the effort to deprecate named queries in e-Comp.

Next steps: get data from teams in order to prepare for testing the change from named queries to custom queries.

See also AAI Named Queries

James Forsyth

Former user (Deleted)

31st Jan 2019:

The schema-service is ready. Currently it provides file-sharing capabilities in terms of schema/edgerule files.

In order for GraphGraph to take advantage of the schema parsing/processing in schema-service additional abstractions have to be implemented on top of the crude file2string functionality currently in schema-service.

• Venkata Harish Kajurwill ask Manisha Aggarwalif the current functionality of the schema-service is the final version for Dublin and if there will be further enhancements in next releases. 
  

GraphGraph needs the following functionality:

Venkata Harish Kajur  and Manisha Aggarwal What is missing in schema service that is needed in graphgraph is the following:

• rest call to get available schemas
• list of all schema nodes/items (like vserver, tenant, p-interfaces..) for example on a REST path /schemas/{schema}/nodes
• all relevant attributes of a given node/item for example on REST path /schemas/{schema}/nodes/{node}
• edges/relationships with their attributes between schema nodes/items (for example on REST path /schemas/{schema}/edges where you specify a "from" "to" schema items as query params)
• subgraph of the schema, where you specify 1. initial (root) items/node (like tenant or vserver) 2. schema version and 3. number of parent/cousin/child hops from the initial item/node
• all paths in a given schema graph between 2 items/nodes (like vserver and tenant) for a given schema version
• edges in the schema graph should be composed of edges in the schema file + edges created from the edgerules file
• edges should contain basic attributes when delivered via the subgraph call (like parent/child relationship and important properties from edgerules) and have additional (or all) attributes when queries via /schemas/{schema}/edges REST endpoint.

20. Mar 2019:

Open questions for schema-service:

1. what is the current implemented functionality?
2. what are the business use-cases in ONAP for schema-service? Description of functionality in relation to other services/projects is needed. In other words who needs it and why?
3. if no business use-cases can be formulated we should consider removing schema-service from A&AI and replacing it with standard file-sharing mechanisms.

21st Mar 2019:

Based on William Reehil comments

https://wiki.onap.org/display/DW/AAI+Schema+Service?focusedCommentId=45299262#comment-45299262 what is "our future proposed functionality"?

James Forsyth

IN PROGRESS

New requirement to have our csit run as part of oom test environment in windriver

Long term goal: one robot test case per endpoint that can run as part of e2e test

AAI R4 Integration Sanity Test Plans

See also Contributing To AAI Best Practise

4th March: AAI-2208 - Getting issue details... STATUS / https://gerrit.onap.org/r/#/c/79583/

13th March: Success! First commit merged, more to follow!

20th March: Second commit merged https://gerrit.onap.org/r/#/c/82623/

ON HOLD

AAF will generate certificates to the be used by the containers at startup; AAI services should use the run-time generated certs instead of the ones that are in the repos or oom charts.

In dublin the services will mount a volume with certificates. This is on the roadmap for Dublin as a feature.

• is this for all service and/or HAProxy?
• Where are the certificates coming from (OOM/gerrit/generated by AAF)
  
  

• James Forsythwill ask Jonathan Gatham when the certificate init image is going to be available in ONAP and wether it is documented 31 Jan 2019 

Benjamin Cheung

Chesla Wechsler

David Perez Caparros

Former user (Deleted)

Matthieu Geerebaert

ON HOLD

Potentially breaking change: AAI-2096 - Getting issue details... STATUS / blocked by ONAPARC-409 - Getting issue details... STATUS

See also:

• Proposal to Change AAI PNF Entity to use PNF-ID as key
• AAI R4 Use Case and Functional Requirements Impacts
• Suggestion in comment Re: AAI REST API Documentation - Dublin

Questions:

• how to minimise impact of the transition from pnf-name as unique to pnf-id as unique key?
  • would the v14 URL be different from the v15 URL? would both paths be equally supported for GET/PUT/etc?
• what forwards-compatibility or backwards-compatibility will be supported?
• how to migrate forwards or backwards database versions, ONAP versions, etc, across this transition?
• who is going to implement it? Test it?
• what is the impact of this not going ahead?

• William LaMont will check for existing migration utility that handles this use case (changing the key from one existing attribute to another). Changes to pnf object in all oxm versions would be needed, and a migration similar to what was done in UrlMigration but limited to pnf node-type to update the aai-uri, and a schema mode to add an index on pnf-id.
• James Forsyth will socialize the breaking change on the PNF in the next PTL call so clients can prepare to do a search for ?pnf-name=${pnf-name} instead of /pnfs/pnf/${pnf-name}. They also need to handle doing the PUT operation differently - Added to PTL agenda PTL 2019-02-19
  

Keong Lim

Mike Elliott wrote in OOM Meeting Notes - 2018-12-5

f. AAI team wanted to get notified of AAI Cassandra issues automatically
                i. Can we setup a Nagios or equivalent to monitor both rancher/k8 and the applications for rancher/k8 issues ?

Keep an eye out for new issues!

This should be part of a larger A&AI monitoring and failure prevention initiative!

ON HOLD

Technical solution to either decommission the proxy or make design changes to AAF to enable client side certificates.

After VF2F we will know if this is a requirement in Dublin. We discuss after this date.

question raised: MSB - would client authentication be supported?

15th Dec: https://wiki.onap.org/display/DW/Pluggable+Security#PluggableSecurity-7.10Identifiedandsupportedpatternsandfeatures

• James Forsythcreates a task for encryption of communication between A&AI services and Cassandra 24 Jan 2019
  
• Tian Lee and Steve Blimkie to report on the Amdocs managed A&AI microservice wheter they support criteria from the Dublin S3P requirements 31 Jan 2019