| Title | Raised By | Status | Last discussed | Notes |
---|
1 | 4th July meeting canceled | | Status |
---|
colour | GreenBlue |
---|
title | OpenDone |
---|
|
| 11th July 2019 | Developers call on 4th July is canceled due to public holiday in US. |
2 | AAI Alpine conversion | Dmitry Puzikov (Deactivated) | Status |
---|
colour | GreenYellow |
---|
title | OpenIn Progress |
---|
|
| 11th July 2019 | After some delay we were able to deploy ONAP with minimized AAI images and perform - ONAP robot healthdist tests and test model-loader manually.
- All AAI related robot tests and model-loader tests were passed successfully.
- Please, find detailed report in JIRA: https://jira.onap.org/browse/INT-1023
|
3 | New UI Features / Historical Tracking | William Reehil | |
| The AT&T team has done an exciting POC at a sprint-a-thon event that they would like to share with the community. |
4 | Alternative meeting system | | |
| Just in case Zoom problems continue, try this instead: https://meet.jit.si/onapaaiKenny Paul would Jitsi be suitable for LF to adopt as well?
|
5 | Review El Alto proposals | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
|
| AAI Epics/Stories in JIRA: Jira Legacy |
---|
server | System Jira |
---|
jqlQuery | project=AAI and issuetype in (Epic,Story) and fixVersion = "El Alto Release" order by key desc |
---|
count | true |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
|
6 | Problems deleting logical-link | | Status |
---|
colour | GreenYellow |
---|
title | OpenIn Progress |
---|
|
| 11th July 2019 | Just wondering if there is a bug here worth raising in JIRA? In a Dublin-based ONAP system, we have this logical-link object: Code Block |
---|
GET: {{aai-2}}/aai/v16/network/logical-links/logical-link/cross-link-2?depth=all
{
"link-name": "cross-link-2",
"in-maint": false,
"link-type": "cross-link",
"resource-version": "1559987176986",
"operational-status": "up",
"relationship-list": {
"relationship": [
{
"related-to": "p-interface",
"relationship-label": "tosca.relationships.network.LinksTo",
"related-link": "/aai/v16/network/pnfs/pnf/11.11.11.11/p-interfaces/p-interface/nodeId-11.11.11.11-ltpId-159",
"relationship-data": [
{
"relationship-key": "pnf.pnf-name",
"relationship-value": "11.11.11.11"
},
{
"relationship-key": "p-interface.interface-name",
"relationship-value": "nodeId-11.11.11.11-ltpId-159"
}
],
"related-to-property": [
{
"property-key": "p-interface.prov-status"
}
]
},
{
"related-to": "p-interface",
"relationship-label": "tosca.relationships.network.LinksTo",
"related-link": "/aai/v16/network/pnfs/pnf/10.10.10.10/p-interfaces/p-interface/nodeId-10.10.10.10-ltpId-58",
"relationship-data": [
{
"relationship-key": "pnf.pnf-name",
"relationship-value": "10.10.10.10"
},
{
"relationship-key": "p-interface.interface-name",
"relationship-value": "nodeId-10.10.10.10-ltpId-58"
}
],
"related-to-property": [
{
"property-key": "p-interface.prov-status"
}
]
},
{
"related-to": "ext-aai-network",
"relationship-label": "org.onap.relationships.inventory.BelongsTo",
"related-link": "/aai/v16/network/ext-aai-networks/ext-aai-network/VDF-ext-net",
"relationship-data": [
{
"relationship-key": "ext-aai-network.aai-id",
"relationship-value": "VDF-ext-net"
}
]
}
]
}
}
|
On attempting to DELETE the logical-link, we get an error preventing it: Code Block |
---|
Delete: {{aai-2}}/aai/v16/network/logical-links/logical-link/cross-link-2?resource-version=1559987176986
{
"requestError": {
"serviceException": {
"messageId": "SVC3100",
"text": "Unsupported operation %1 (msg=%2) (ec=%3)",
"variables": [
"DELETE",
"Node cannot be deleted:Object is being reference by additional objects preventing it from being deleted. Please clean up references from the following types [logical-link, pnf]",
"ERR.5.4.6110",
"network/logical-links/logical-link/cross-link-2"
]
}
}
}
|
The logical-link is related to p-interface and ext-aai-network, so why is the error message about logical-link to pnf? From a look at edge-rules, there does not seem to be any "prevent-delete" properties that should apply to logical-link at all.
As workaround, we do a PUT with an empty relationship-list, to clear out the relationship data, then a subsequent DELETE works without error. What is going here? | 7 | Queries about BYOQ DSL | | | 11th July: Could it be a side-effect from the bug reported in Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2507 |
---|
| ? In that case, the relationship is logical-link to ext-aai-network to pnf? |
7 | Queries about BYOQ DSL | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 11th July 2019 | Referring to DSL API (BYOQ - Bring Your Own Query) Q1. The "Getting Started" section shows: Code Block |
---|
PUT /aai/v$/dsl?format={format} |
but the "Optional Query Parameters" section shows: Code Block |
---|
PUT /aai/v$/query?format={resource OR resource_and_url}&depth=0 |
The /dsl/ path results in an error . Should it all be using /query/ instead?Q2. The "Payload" section shows: {
"dsl" :"customer> service-subscription( 'service-type' , 'example-service-type' ) > service-instance > generic-vnf*( 'vnf-type' , 'example-vnf-type' )( 'model-version-id-local' , '1.0' )
"
}
but calling the /query/ without a "start" parameter gives an error. Should the payload always contain a "start" parameter?: Code Block |
---|
{
"requestError": {
"serviceException": {
"messageId": "SVC3000",
"text": "Invalid input performing %1 on %2 (msg=%3) (ec=%4)",
"variables": [
"PUT",
"v16/dsl",
"Invalid input performing %1 on %2:Unrecognized AAI object dsl",
"ERR.5.2.3000"
]
}
}
} |
Should it all be using /query/ instead?
11th July: Venkata Harish Kajur pushed a fix to HAProxy config for Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2509 |
---|
| . It seems the /dsl/ call was being routed to AAI-Resources by default instead of AAI-Traversal. Keong Lim to re-test.
|
8 | Problem Accessing AAI GUI from | THIRILOSHINI KRISHNAKUMAR | Status |
---|
| |
---|
colour | Yellow |
---|
title | In PROGRESS |
---|
|
|
| Message was sent to onap-discuss list a couple of weeks ago. Would like to get someone to look at it and continue the investigation. |
9 | 2 Types of logging in A&AI WS | | | 1st Nov 2018 | 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 Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-877 |
---|
|
? 28th May: Stela Stoykova is fixing Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2462 |
---|
|
. Are there more that should be done for El Alto? |
10 | AAI Standalone UI Access/setup | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 2019-05-23 | Francis Paquette James Forsyth Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2418 |
---|
|
- In casablanca environment without Sparky-fe, how we are able to access the AAI-UI?
- In standalone AAI setup, how can i access the AAI UI? i am running the resources, traversal, elastic-search, search-data-service and sparky-be. but not able to access the UI, need to run any other services to access the UI?
tried with below URL, http://<IP>:9517/services/aai/webapp/index.html response: Whitelabel Error PageThis application has no explicit mapping for /error, so you are seeing this as a fallback. Tue May 21 05:07:26 UTC 2019 There was an unexpected error (type=Not Found, status=404). No message available |
11 | AAI schema UML diagram | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 2019-05-23 | https://lists.onap.org/g/onap-discuss/topic/31619985 See also: Gerrit review for swagger template https://gerrit.onap.org/r/#/c/87941/ Meeting recording attached to previous week 2019-05-16 AAI Developers Meeting See also wiki and sub-pages: Reverse-engineering AAI data model to Papyrus information model 13th June: Presentation from DDF in Stockholm: https://wiki.lfnetworking.org/display/LN/2019+June+Event+Topic+Proposals?preview=/15630468/15631379/AAIDataModeling-20190613.pdf 13th June: Video of presentation from DDF in Stockholm: https://wiki.lfnetworking.org/download/attachments/15630468/AAI-DataModelVisualization-20190613.mp4?version=1&modificationDate=1560421344046&api=v2 |
12 | Optimise ad-hoc retrieval of any resource with any of its cousin relationships | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 2019-05-23 | Raised as JIRA case Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2437 |
---|
|
Gerrit review https://gerrit.onap.org/r/#/c/87940/ Would like to gather opinions on the implementation (see the comments in the JIRA case). The query has been tested in my dev environment but unsure if the query is done the best way. - soumyais invited to a future session to discuss further
|
13 | Dublin Branching | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 2019-05-09 | El Alto runs Jun - Sep - technical debt and S3P/deployability release Frankfurt starts in Sep As of now, master will accept feature development for Frankfurt We tag dublin at release time (early June) The Dublin branch becomes El Alto (similar to a Dublin Maintenance Release) El Alto changes will be cherry picked back to master |
14 | GraphGraph demo | Former user (Deleted) | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 2nd May 2019 | A 5-10 minute demo of GraphGraph Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-531 |
---|
|
. Feedback needed! |
15 | AAI Modeling Multi-part key for schema elements | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 25th Apr 2019 | From https://lists.onap.org/g/onap-discuss/topic/31317665 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?
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2391 |
---|
|
- 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?
- Can we get feedback from Chandra Cinthalaon the key design for multi-part keys and whether this will be more common going forward?
From: CINTHALA, CHANDRA [mailto:cc1196@att.com] Sent: Tuesday, April 30, 2019 12:16 AM To: Keong Lim <Keong.Lim@huawei.com>; FORSYTH, JAMES <jf2512@att.com> Cc: AGGARWAL, MANISHA <amanisha@att.com> Subject: Re: [confluence] Keong Lim has assigned tasks to you in "2019-05-02 AAI Developers Meeting"
Keong,
I think we have no plans to deprecate the relation-data option the in the A&AI relationship payload. It's another option for the client to specify the relationship.
Thanks Chandra
- See also email from Marco Platania in https://lists.onap.org/g/onap-discuss/topic/31385256
|
16 | Return codes and messages for WS | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 25th Apr 2019 | 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
|
17 | AAI test data bootstrap | Keong Lim | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 25th Apr 2019 | 3rd May: See also AAI Simulator in Policy: https://gerrit.onap.org/r/gitweb?p=policy/models.git;a=blob;f=models-interactions/model-simulators/src/main/java/org/onap/policy/simulators/AaiSimulatorJaxRs.java;hb=HEAD . Was recently updated for custom query https://gerrit.onap.org/r/#/q/pramod+custom and contains hard-coded AAI data/schema. Maybe discuss with Pamela Dragosh about how this data is maintained? 25th Apr: Wiki page OOF - HPA guide for integration testing updated for https://gerrit.onap.org/r/#/c/86588/ 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: Related Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-1948 |
---|
|
on the brittleness of the ReadTheDocs links to data files. One for VIM: How-To: Register a VIM/Cloud Instance to ONAP and Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-1928 |
---|
|
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?
Possible solution/action: - Look at the examples API and possibly enhance it to get the desired behavior
- Collect all the known data samples, commit to test-config repo, update the teams/wiki to point to test-config repo instead of keeping private stash of AAI data
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2399 |
---|
|
|
18 | Purpose of fields in AAI | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 18th April 2019 | Dénes Németh wrote in Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-1104 |
---|
|
: 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://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/5G+-+PNF+Plug+and+Play?focusedCommentId=63996633#comment-6399663316367935
|
19 | range query | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 7th Feb 2019 | - Invite Arul Nambi and CT Paterson to next week's dev call to talk about how sparky/elastic does partial/range matches
|
20 | 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. - 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: - what is the current implemented functionality?
- 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?
- 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://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/AAI+Schema+Service?focusedCommentId=45299262#comment-4529926216325457 what is "our future proposed functionality"? |
21 | New AAF Certificates at startup | Jimmy Forsyth | | 24th Jan 2019 | Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2476 |
---|
|
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)
12th June 2019: Jonathan Gathman demonstrated aaf-hello functionality at DDF event |
22 | Change PNF to use pnf-id as unique key | | | 7th March 2019 | Potentially breaking change: Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-2096 |
---|
|
/ blocked by Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | ONAPARC-409 |
---|
|
See also: 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
|
23 | 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 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! |
24 | 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 |
25 | AAI too slow for OOF/HAS | Keong Lim | | 25th Apr 2019 | 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 Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OPTFRA-268 |
---|
|
/ Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OPTFRA-291 |
---|
|
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 Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | AAI-1337 |
---|
|
help to improve performance? |
26 | MultiCloud usage of AAI for HPA telemetry/time-series data to OOF | | | 18th April 2019 | Bin Yang and Lianhao Lu (Deactivated) wrote in Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | MULTICLOUD-274 |
---|
|
: HPA telemetry data collection and make it persistent in A&AI, from which OOF can leverage during its decision making process. and 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
|
27 | 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? - 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. |