Attachments (including meeting recording)
private group aai-dev on Rocketchat server: http://onap-integration.eastus.cloudapp.azure.com:3000/group/aai-dev
|1||Maven plugin for consistent code style|
Also added to Contributing To AAI Best Practise
Please test and review.
|2||Return codes and messages for WS|
|3||AAI ESR Questions||THIRILOSHINI KRISHNAKUMAR|
|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?|
|5||Purpose of fields in AAI|
Dénes Németh wrote in - AAI-1104Getting 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)
1. Is AAI intended to strictly prescribe how the fields are used and what contents are in the values?
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
|6||AAI test data bootstrap||Keong Lim|
Similarly, Scott Seabolt and J Armstrong / Joss Armstrong wrote for APPC Sample A&AI Data Setup for vLB/vDNS for APPC Consumption and Script to load vLB into AAI:
One for VIM: How-To: Register a VIM/Cloud Instance to ONAP and - AAI-1928Getting issue details... STATUS
|7||AAI too slow for OOF/HAS||Keong Lim|
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.
What can we do about this?
|8||MultiCloud usage of AAI for HPA telemetry/time-series data to OOF|
HPA telemetry data collection and make it persistent in A&AI, from which OOF can leverage during its decision making process.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.
|9||Orchestration Scenarios for VNFs|
Comments on Orchestration Scenarios related to AAI:
and Fernando Oliveira replied:
For the first question: I think that A&AI needs to maintain the VNF instance ↔ VNFM instance and the NS instance ↔ NFVO instance relationship for subsequent life cycle operations, i.e. a scale or heal operation. The path would be something like Event (VNF Instance, Busy) → DCAE (policy for VNF instance) → Policy Evaluation (VNF instance, Scale-out) → SO (VNF instance, Scale-out) → A&AI (find VNFM instance for the VNF instance) → SO (VNF instance, VNFM instance, Scale-out) → SOL003 Adapter (VNFM instance, VNF instance, Scale-out) → VNFM instance (VNF Instance, Scale-out).
As I understand, ESR has "esr-vnfm-list", which has an "esr-vnfm", which has "esr-system-info-list", which has "esr-system-info", which has a "relationship-list" that can contain relationships to "generic-vnf" and other AAI objects.
The "generic-vnf" object also contains "self-link", "ipv4OamAddress", "ipv4OamGatewayAddress", etc, which links the AAI object back to its "source-of-truth" external-system.
Is there some new data, new schema or new API that is required on top of this?
Fernando Oliveira; Apologies for my lack of knowledge, but a few comments:
Bo Lv can comment more on the current ESR capabilities, but I believe there are only 3 kinds of systems so far: EMS, VNFM and third-party SDNC.
ESR could be extended to handle VNFO as another kind of system.
Fernando Oliveira : I created JIRA stories:
for various parts of the scenario.
Bharath Thiruveedula is this item related to your question for Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVO?
Keong Lim it is related to the question
|10||AAI too slow for Holmes|
|1st Nov 2018|
The problem for caching is how to know when to update the cached data. Even though the access time may be fast for Holmes, the risk is using out-of-date data, so the correlations will be wrong anyway. Also, duplicating the AAI data outside of AAI is probably a bad architectural decision. Making AAI faster for these use cases would be better.
Has there been a performance analysis of where the time is spent? Could it help to use ElasticSearch (e.g. as in sparky)? Should Holmes have a batch interface to get more AAI data in fewer calls? Or a better correlation API that results in fewer calls?
|11||CSIT / CSIT on OOM|
|21st Feb 2019|
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
See also Contributing To AAI Best Practise
|12||Shared Cassandra Database|
|14th Feb 2019|
|13||Change PNF to use pnf-id as unique key|
|21st Feb 2019|
|7th Feb 2019|
|15||Image footprint reduction as part of CIA project|
|7th Feb 2019|
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
|31th 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.
|17||New AAF Certificates at startup||Jimmy Forsyth|
|24th Jan 2019|
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.
|18||AAI Backup and Restore|
|10th Jan 2019|
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?
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?"
Mike Elliott said he would look at Brian's question, AAI will provide support as needed.
|19||aai-cassandra performance issues||Keong Lim|
|10th Jan 2019|
Michael O'Brien has documented performance issues in aai-cassandra:
hector has discovered that the stress test jar (liveness probe?) in aai-cassandra is hammering the cpu/ram/hd on the vm that aai is on - this breaks the etcd cluster (not the latency/network issues we suspected that may cause pod rescheduling)
Is there something that should be tweaked in AAI config? Or documentation on the recommended setup to run the VM?
I'll come to the next AAI meet (conflicts with pomba meet) -
20190108 work continues to find the cause - I see 7 vCore spikes on cassandra as well as a saturated logstash on that particular vm - we are no longer a DaemonSet (13 instances on a 13+1 cluster) - I will reduce the current ReplicaSet from 5 to 2 or 1 until I can label the nodes and/or find out what is causing ls to saturate - Prudence Au and Sanjay Agraharam mentioned cassandra - I have seen cs high on several "top" sessions - will post screen caps - bottom line is correlation - I have a 2nd cluster where I can just run aai,dmaap and log
On-hold for 3 weeks (end of January) - if until then no performance issues reported agenda item will be closed
|20||get notified of AAI Cassandra issues automatically|
|24th Jan 2019|
f. AAI team wanted to get notified of AAI Cassandra issues automatically
Keep an eye out for new issues!
Question: Keong Lim should this be part of a larger A&AI monitoring and failure prevention initiative
|21||Modeling team R4 discussion, including extra AAI attributes in a model-driven way|
|15th Nov 2018|
Modelling team having Service Instance thoughts by Chesla Wechsler, which will affect AAI schema.
Also referred from comments on ONAP R4+ Service Modeling Discussion Calls
9)“vhn-portal-url”?“Bandwidth”,"QoS","SLA",etc, attribtutes that not all the services need but still need to be stored in certain service instance: stored as a schemaless field on the service-instance vertex (Chesla will follow up) (my concerns: according to the call, is that ok if we set a "global-type of service" and a "customized-type of service", then mapped it with internal descriptor, and A&AI's model only stores global type in service instance's schema, but stores the customer-faced attributes of service in a schemaless way? Chesla Wechsler Kevin Scaggs Andy Mayer)
See also Modeling 2018-11-13
The service-instance already uses a "metadata" relationship, which can store an arbitrary list of key-value pairs, but perhaps AAI should extend the use of the "properties" element, which is also an arbitrary list of name-value pairs or the "extra-properties" element, which is also an arbitrary list of name-value pairs.
15th Nov: Having seen Chesla's presentation, it should be called "Model-driven schema" rather than "schemaless" behaviour, since the idea is that the changes are controlled by SDC modelling. Seems aligned to the eventual goal in AAI Schema Service Use Case Proposals and AAI Schema Service.
|22||2 Types of logging in A&AI WS|
|1st Nov 2018|
There are 2 types of logging in the services
Is that correct? Shouldn't there be just 1 type?
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
Disable unused web services
(see also Helm chart requested values)
|20th Dec 2018|
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.
Venkata Harish Kajur and Pavel Paroulek - 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?)
|1st Nov 2018|
|25||AAI HAProxy and 2-way-TLS|
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?
|26||named-query replacements||James Forsyth|
|31th Jan 2019|
- APPC-1245Getting issue details... STATUS : Takamune Cho pointed to inherited CCSDK functions, so added a new case to follow-up there too
- VID-355Getting issue details... STATUS : Ittay Stern has provided an update with 2 known queries used.
- CCSDK-962Getting 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
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