Attachments (including meeting recording)
...
Title | Responsible | Status | Last discussed | Notes | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | New AAF Certificates at startup | Jimmy Forsyth |
| 17th 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 roapdmap for Dublin as a feature. | ||||||||||||||||||||||||||||||||||||||||||||||
2 | AAI Backup and Restore |
| 10th Jan 2019 | 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?
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. | |||||||||||||||||||||||||||||||||||||||||||||||
3 | Dublin use-cases |
| 10th Jan 2019 | BBS Broadband Service Use Case (Dublin) Change Management Dublin Extensions Edge Automation Functional Requirements for Dublin OpenSource Access Manager (OSAM) Use Case K8S based Cloud Region Support
The Dublin use-cases for review are Release 4 (Dublin) Use Cases and functional requirements On AAI weekly call on Wednesday Chandra Cinthala will report on his progress in analyzing the use-cases. | |||||||||||||||||||||||||||||||||||||||||||||||
4 | CCVPN Extension Dublin |
| 20th Dec 2018 | During the VF2F we have presented the CCVPN Use Case extension for Dublin Release. In particular, we have defined the E-LAN Service (EP-LAN. EVP-LAN) sub-Use Case. More details can be found at this page (the presentation given to the Use Case SubCommittee and during the VF2F can also be found in that page). We have also created 2 additional pages where we describe the: In the former page, we have identified Option 2 (for Service Creation) and Option A (for Service Modification) as the “ideal” implementation. The Impacts in the latter page are based on such an assumption. We would be grateful if you could help us with the assessment for A&AI and if you could confirm the project commitment to CCVPN. 14th Dec: Regarding the Options and Impact assessment linked above:
As far as I know, the ServiceComposite pattern hasn't even exited the Modelling team's discussions for R3 or R4 workshops Hui Deng : This would seem like a stretch goal given the impacts on all the downstream clients of AAI, if it would require reworking any existing schema elements. However, if you are looking for a zero-impact method of implementation, the EdgeRules already contain service-instance-to-service-instance relationship with label "org.onap.relationships.inventory.ComposedOf", so AAI can do the composite data with this relationship.
Update 3rd January 2019 from CFL comment:
| |||||||||||||||||||||||||||||||||||||||||||||||
5 | AAI behaviour in error conditions | Just raised
Moved from AAI Weekly Status Meeting. | |||||||||||||||||||||||||||||||||||||||||||||||||
6 | 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 LOG Meeting Minutes 2019-01-15
On-hold for 3 weeks (end of January) - if until then no performance issues reported agenda item will be closed | ||||||||||||||||||||||||||||||||||||||||||||||
7 | get notified of AAI Casandra issues automatically |
| Mike Elliott wrote in OOM Meeting Notes - 2018-12-5 f. AAI team wanted to get notified of AAI Casandra issues automatically Keep an eye out for new issues! | ||||||||||||||||||||||||||||||||||||||||||||||||
8 | Purpose of fields in AAI |
| Dénes Németh wrote in
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? 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 | ||||||||||||||||||||||||||||||||||||||||||||||||
9 | Postel's Law / Robustness Principle for AAI data inputs | Keong Lim |
| 6th Dec 2018 | While helping UUI team to debug a family of related issues such as
vs
Initially, I thought this could be due to XML-to-JSON translation error, but it could also have been a copy-paste from the output of a GET, e.g.
In the spirit of Postel's Law ("be liberal in what you accept"), could/should AAI accept both variations of the input data above? There could be additional validation that the element name inside the request body matches the element name in the URL of the API (similar validation is already performed for the key ID value). It would also allow for simple methods of data transfer/migration, where AAI output is directly accepted as AAI input. 7th Dec: As per Jimmy's comment below, the difference between the "Not Accepted Input" and "Expected Input Format" is the behaviour controlled by "SerializationFeature.WRAP_ROOT_VALUE" as described in:
| ||||||||||||||||||||||||||||||||||||||||||||||
10 | Copyright license header restricted to 1 company |
| In the copyright /** * ============LICENSE_START======================================================= * org.onap.aai * ================================================================================ * Copyright © 2017-2018 AT&T Intellectual Property. All rights reserved. If there is a company other than AT&T the build fails saying the license header is wrong | ||||||||||||||||||||||||||||||||||||||||||||||||
11 | Return codes and messages for WS |
| Is there a guide for the description of the error message and the error codes? How are new error states (message + code) added? | ||||||||||||||||||||||||||||||||||||||||||||||||
12 | OOM Artifacts |
| 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? | ||||||||||||||||||||||||||||||||||||||||||||||||
13 | AAI test data bootstrap | Keong Lim |
| 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?
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:
Similarly:
Related
One for VIM: How-To: Register a VIM/Cloud Instance to ONAP and
Potential issues:
| |||||||||||||||||||||||||||||||||||||||||||||||
14 | AAI too slow for OOF/HAS | Keong Lim |
| Under OOF Homing and Allocation Service (HAS) section, Dileep Ranganathan wrote about Project Specific enhancements:
See also
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? Would the AAI Cacher
| |||||||||||||||||||||||||||||||||||||||||||||||
15 | MultiCloud usage of AAI for HPA telemetry/time-series data to OOF |
| Bin Yang and Lianhao Lu (Deactivated) wrote in
HPA telemetry data collection and make it persistent in A&AI, from which OOF can leverage during its decision making process.and
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:
| ||||||||||||||||||||||||||||||||||||||||||||||||
16 | AAI-BBS for Dublin |
| Started collating proposed changes in wiki AAI-BBS Proposals for Dublin Release Investigating code proposal 1: In AAI, when the "orchestration-status", "service-instance-location-id", "input-params" for a Service Instance changes, notify ExtAPI so it does not need to poll AAI Is it already covered by spike? If so, how to consume the events? If not, how to make AAI publish new events to DMaaP? | ||||||||||||||||||||||||||||||||||||||||||||||||
17 | Orchestration Scenarios for VNFs |
| Comments on Orchestration Scenarios related to AAI: Viswanath Kumar Skand Priya / kspviswa said:
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. | ||||||||||||||||||||||||||||||||||||||||||||||||
18 | 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. | |||||||||||||||||||||||||||||||||||||||||||||||
19 | AAI too slow for Holmes |
| 1st Nov 2018 | Guangrong Fu mentioned AAI in Baseline Measurements based on Testing Results:
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? 31st Oct: https://lists.onap.org/g/onap-discuss/topic/27805753 1st Nov:
Would the AAI Cacher
| |||||||||||||||||||||||||||||||||||||||||||||||
20 | 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? 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
| |||||||||||||||||||||||||||||||||||||||||||||||
21 | 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. 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?)
| |||||||||||||||||||||||||||||||||||||||||||||||
22 | AAI Champ |
| 1st Nov 2018 |
| |||||||||||||||||||||||||||||||||||||||||||||||
23 | AAI HAProxy and 2-way-TLS |
| 29th Nov | 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?
| |||||||||||||||||||||||||||||||||||||||||||||||
24 | named-query replacements | James Forsyth |
| 17th Jan 2019 |
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
| ||||||||||||||||||||||||||||||||||||||||||||||
25 | Spring Boot Upgrade |
| 17th Jan 2019 | https://spring.io/blog/2018/11/29/spring-boot-1-5-18-available-now - support for 1.5.x spring boot will end in Aug 2019 so we should consider upgrading. We should update to spring 2.X.X. On the meeting on the 10th Jan discuss if anyone has anything against it, if not then James Forsyth creates a JIRA item for Dublin for upgrading the spring in all A&AI repositories. Conclusion:
|
...