Attachments (including meeting recording)
...
Title | Responsible | Status | Last discussed | Notes | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | ETSI SOL 005 | tElastic Search |
RE: Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVO Hi AAI team, Can you please review the patches regarding the SOL 005 | 18th April 2019 | Check with Jessica if we should merge the aai/oom changes now or is it still something they should be taking care of? | ||||||||||||||||||||||||||||||||||||||||||||||
2 | AAI Rolling Upgrade |
| 18th April 2019 | New helm upgrade change was made recently after code freeze Check at the TSC call if this is ok to make. | |||||||||||||||||||||||||||||||||||||||||||||||
3 | ETSI SOL 005 |
| 18th April 2019 | RE: Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVO Hi AAI team, Can you please review the patches regarding the SOL 005 requirements? Here are the gerrit links
Best Regards Bharath T 26th Mar: Also needs
| |||||||||||||||||||||||||||||||||||||||||||||||
24 | Return codes and messages for WS |
| 28th Feb 18th April 2019 | Is there a guide for the description of the error message and the error codes? How are new error states (message + code) added?
| |||||||||||||||||||||||||||||||||||||||||||||||
35 | Image footprint reduction as part of CIA project |
| 11th Feb 18th April 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
26th Mar: Also
| 4
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 | ||||||||||||||||||||||||||||||||||||||||||||||
6 | OOM Artifacts |
| 18th April 2019 | 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
| |||||||||||||||||||||||||||||||||||||||||||||||
57 | AAI too slow for OOF/HAS | Keong Lim |
| 18th April 2019 | 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. For holmes, we could possibly create a custom query to address it. What can we do about this? Would the AAI Cacher
| ||||||||||||||||||||||||||||||||||||||||||||||
68 | MultiCloud usage of AAI for HPA telemetry/time-series data to OOF |
| 18th April 2019 | 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:
| |||||||||||||||||||||||||||||||||||||||||||||||
79 | Orchestration Scenarios for VNFs |
| 18th April 2019 | 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. t 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 | |||||||||||||||||||||||||||||||||||||||||||||||
810 | AAI test data bootstrap | Keong Lim |
| 18th April 2019 | 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:
| 9
Possible solution: Look at the examples API and possibly enhance it to get the desired behavior | |||||||||||||||||||||||||||||||||||||||||||||
11 | Purpose of fields in AAI |
| 18th April 2019 | 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 | 10Where 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? | ||||||||||||||||||||||||||||||||||||||||||||||
12 | Bulk API returns failure if one of the PUT request fails | Chandrashekhar Thakare |
| 18th Apr 2019 | Now raised in JIRA
| ||||||||||||||||||||||||||||||||||||||||||||||
13 | range query |
| 7th Feb 2019 |
| |||||||||||||||||||||||||||||||||||||||||||||||
1114 | 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. | |||||||||||||||||||||||||||||||||||||||||||||||
1215 | 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
| |||||||||||||||||||||||||||||||||||||||||||||||
1316 | 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?)
| |||||||||||||||||||||||||||||||||||||||||||||||
1417 | AAI Champ |
| 1st Nov 2018 |
| |||||||||||||||||||||||||||||||||||||||||||||||
1518 | named-query replacements | James Forsyth |
| 31th 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 | ||||||||||||||||||||||||||||||||||||||||||||||
1619 | Schema-service roadmap |
| 21st Mar 2019 | 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.
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:
20. Mar 2019: Open questions for schema-service:
21st Mar 2019: Based on William Reehil comments https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/AAI+Schema+Service?focusedCommentId=45299262#comment-4529926216325457 what is "our future proposed functionality"? | |||||||||||||||||||||||||||||||||||||||||||||||
1720 | CSIT / CSIT on OOM |
| 21st March 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 AAI R4 Integration Sanity Test Plans See also Contributing To AAI Best Practise 4th March:
13th March: Success! First commit merged, more to follow! 20th March: Second commit merged https://gerrit.onap.org/r/#/c/82623/ | |||||||||||||||||||||||||||||||||||||||||||||||
1821 | 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.
| ||||||||||||||||||||||||||||||||||||||||||||||
1922 | Change PNF to use pnf-id as unique key |
| 7th March 2019 | Potentially breaking change:
See also:
Questions:
| |||||||||||||||||||||||||||||||||||||||||||||||
2023 | A&AI monitoring and failure prevention initiative |
| 24th Jan 2019 | Mike Elliott wrote in OOM Meeting Notes - 2018-12-5 f. AAI team wanted to get notified of AAI Cassandra issues automatically Keep an eye out for new issues! This should be part of a larger A&AI monitoring and failure prevention initiative! | |||||||||||||||||||||||||||||||||||||||||||||||
2124 | 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? 15th Dec: https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Pluggable+Security#PluggableSecurity-7.10Identifiedandsupportedpatternsandfeatures
| |||||||||||||||||||||||||||||||||||||||||||||||
2225 | AAI too slow for Holmes |
| 7th March 2019 |
Moved to AAI Performance Target to Support Holmes Alarm Processing | |||||||||||||||||||||||||||||||||||||||||||||||
2326 | aai-cassandra performance issues | Keong Lim |
| 10th Jan 2019 | Start again with shared Cassandra performance tuning. | ||||||||||||||||||||||||||||||||||||||||||||||
2427 | Shared Cassandra Database |
| 14th March 2019 | It's being merged. | |||||||||||||||||||||||||||||||||||||||||||||||
2528 | Modeling team R4 discussion, including extra AAI attributes in a model-driven way |
| 15th Nov 2018 | Schema service and modelling activities are on-going. | |||||||||||||||||||||||||||||||||||||||||||||||
2629 |