Recording:
...
| 1 | Vetting DSL Queries | Will discuss strategies AAI will employ to protect itself from rogue queries. | ||||||||||||||||||||||||||||||||
| 2 | AAI History | Philip Blackwood | Discuss and review Scenarios for using historical inventory and topology | |||||||||||||||||||||||||||||||
| 3 | Casablanca to Dublin Migration | Ankit Bhatt | 3rd July: raised
| |||||||||||||||||||||||||||||||
| 4 | Build styles | We have too many ways to build and deploy artifacts, which makes it difficult and time-consuming. Some of our artifacts are not backward compatible and we need to move everything up to released versions. | ||||||||||||||||||||||||||||||||
| 5 | Alternative meeting system | Just in case Zoom problems continue, try this instead: | 6 | Global JJB issue |
| Code Block |
|---|
09:59:26 ERROR: git-review 1.24 requires argparse, which is not installed.
09:59:26 ERROR: openstacksdk 0.31.1 has requirement ipaddress>=1.0.17; python_version < "3.3", but you'll have ipaddress 1.0.16 which is incompatible.
09:59:26 ERROR: openstacksdk 0.31.1 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: pyasn1-modules 0.2.5 has requirement pyasn1<0.5.0,>=0.4.1, but you'll have pyasn1 0.1.9 which is incompatible.
09:59:26 ERROR: python-heatclient 1.16.2 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: oslo-config 6.10.0 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: yq 2.7.2 has requirement PyYAML>=3.11, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: requests 2.22.0 has requirement idna<2.9,>=2.5, but you'll have idna 2.4 which is incompatible.
09:59:26 ERROR: oslo-serialization 2.29.1 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
09:59:26 ERROR: cliff 2.15.0 has requirement PyYAML>=3.12, but you'll have pyyaml 3.10 which is incompatible.
...
09:59:57 [aai-aai-common-maven-stage-master] $ /w/tools/hudson.tasks.Maven_MavenInstallation/mvn35/bin/mvn -f -s /tmp/settings6002355141556927426.xml -gs /tmp/global-settings1115787293230334266.xml -DGERRIT_BRANCH=master -DPROJECT=aai/aai-common -DMVN=/w/tools/hudson.tasks.Maven_MavenInstallation/mvn35/bin/mvn -DSTREAM=master -DARCHIVE_ARTIFACTS= -DGERRIT_PROJECT=aai/aai-common -Dsha1=origin/master -DMAVEN_OPTS= -DGERRIT_REFSPEC=refs/heads/master -DM2_HOME=/w/tools/hudson.tasks.Maven_MavenInstallation/mvn35 -DSTAGING_PROFILE_ID=176c31dfe190a -DMAVEN_VERSIONS_PLUGIN=true -DMAVEN_PARAMS= -DnewVersion=1.5.2 versions:set versions:update-child-modules versions:commit -B
09:59:57 POM file specified with the -f/--file command line argument does not exist
...
10:00:11 [INFO] Downloading from EvoSuite: http://www.evosuite.org/m2/org/codehaus/mojo/maven-metadata.xml
10:00:11 [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
10:00:11 [WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
10:00:11 [INFO] Downloading from EvoSuite: http://www.evosuite.org/m2/org/codehaus/mojo/versions-maven-plugin/maven-metadata.xml
10:00:11 [WARNING] Could not transfer metadata org.codehaus.mojo:versions-maven-plugin/maven-metadata.xml from/to EvoSuite (http://www.evosuite.org/m2): Connect to www.evosuite.org:80 [www.evosuite.org/5.9.82.144] failed: Connection refused (Connection refused)
|
this instead:
The AT&T team has done an exciting POC at a sprint-a-thon event that they would like to share with the community.
ATT wants to contribute additional UI views to ONAP, want to discuss path forward
sparky-be expired certificate - status
- James Forsyth will add note to known issues using info provided by Reneal Rogersand Francis Paquette and make sure dublin docs branch is synced.
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2489
- opened because the docs are not syncing even though dublin matches masterJira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key DOC-486 - Francis Paquette will work
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-2490
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
The new DSL documentation page looks good: DSL API (BYOQ - Bring Your Own Query)
Looking forward to further discussion and experimentation!
data when we become aware of the issue.
Sonatype's maven-staging-plugin will be disabled and we need to implement new LF jenkins jobs before mid-July
Repos and do they use oparent:
./model-loader/pom.xml true ./graphgraph/pom.xml false ./graphadmin/pom.xml true ./esr-server/pom.xml true ./sparky-be/pom.xml true ./rest-client/pom.xml true ./aai-common/pom.xml true ./data-router/pom.xml false ./chameleon/pom.xml false ./sparky-fe/pom.xml false ./event-client/pom.xml true ./gallifrey/pom.xml false ./resources/pom.xml true ./router-core/pom.xml true ./gizmo/pom.xml true ./logging-service/pom.xml true ./babel/pom.xml true ./champ/pom.xml true ./traversal/pom.xml true ./spike/pom.xml true ./esr-gui/pom.xml true ./search-data-service/pom.xml false ./cacher/pom.xml true ./schema-service/pom.xml true ./validation/pom.xml true
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
JIRA Epic/Story count: Jira Legacy server System Jira jqlQuery project = AAI AND issuetype in (Epic,Story) AND fixVersion = "El Alto Release" ORDER BY created DESC count true serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
- No 2 way TLS in Dublin; James Forsyth will socialize early in El Alto, Due
- pnf-id change pushed to El Alto during Architecture review AAI R4 Architecture Review - 5 Mar 2019
- API version update for El Alto should be co-ordinated for earlier in the cycle
- needs a checklist of things to be updated, including yang classes
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2351
- needs a checklist of things to be updated, including yang classes
Want to share in the community potential selenium changes for the sparky UI
(bumped up, is it still relevant?)
Understanding the architecture of AAI is not easy - hard to understand how the code is laid out and how things flow. Need documention which will describe how the microservices are connected, which repos support which functions, etc. Former user (Deleted) says that he had to reverse engineer the dependencies to see how the repos are connected. Recommended to focus on the resources repo for understanding the core function of AAI.
(bumped up, is it still relevant?)
https://wiki.onap.org/display/DW/Best+Practices
- The Docker and Kubernetes engines may run as root until such time as the products support non-root execution.
- Applications may run as root within a container.
- The process ID of a container must not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID.
- Containers may run with root privileges.
- Project containers that run as the root ID must document this in the release notes along with the functionality that requires the container to run as the root ID.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Container Image Minimization Guidelines
James Forsyth will ask integration team if we can use the AAI tenant space in windriver environment
A 5-10 minute demo of GraphGraph.
Feedback needed!
JIRA Issue Count (in AAI project):
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
JIRA Issue Count (talking about AAI):
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Dublin artifacts are released and jjb jobs are updated to drop casablanca jobs and replace with dublin
We will change the sonar and clm jobs to use the dublin branch
- James Forsyth will see how other teams manage merging release bug/security/late feature change back to master
- James Forsythwill start a document with best practices and requirements for merging changes to the aai/oom submodule
- Team needs to document (perhaps change the AAI guide for OOM setup) the change to use the submodule in OOM
When is this going to be finished ARC AAI Component Description - Dublin ?
Note: I have no idea what it is, I just was asked to inquire
- Encourage our clients to migrate off named query
- Trying for Silver badge and Level 2 on Security; 50% code coverage on repos
- Resiliency and fault tolerance; meeting notice never published,
- CSIT on OOM needs to cover more of the services
- Volumed run-time generated certificates are possible
-
James Forsyth will open Jira tickets to update the keystores in the master branches of the mS that use https
-
Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
- GraphGraph is coming, depends on expanding schema-service API
- RestClient updates are potentially being contributed by community members
- code coverage to 55% for Dublin
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2219
Champ slipped below 55% with latest commit.
- Tian Lee will do babel, model-loader, champ, gizmo, event-client, spike, rest-client, validation
- Arul Nambi will do sparky-be, search-data-service, data-router, logging-service, router-core
- James Forsyth create ticket for El Alto for sparky, rolling back because of sonar failure
- Venkata Harish Kajur will check aai-common, resources, traversal, graphadmin, cacher, schema-service (which probably already have the setting)
- Add thresholds to all repos that are above 55% so it doesn't happen again
- For setting the threshold on each repo, set it to the current percentage, so if it's is at 62.7%, set the threshold to 0.62
-
<jacoco.line.coverage.limit>0.68</jacoco.line.coverage.limit>
Sonar job for Dublin has been changed to using line coverage.
Code Block <execution> <id>default-check</id> <goals> <goal>check</goal> </goals> <configuration> <dataFile>${project.build.directory}/coverage-reports/jacoco.exec</dataFile> <rules> <!-- implementation is needed only for Maven 2 --> <rule implementation="org.jacoco.maven.RuleConfiguration"> <element>BUNDLE</element> <limits> <limit implementation="org.jacoco.report.check.Limit"> <counter>LINE</counter> <value>COVEREDRATIO</value> <minimum>${jacoco.line.coverage.limit}</minimum> </limit> </limits> </rule> </rules> </configuration> </execution>
Open Action Items
- James Forsyth Document nodes wiki and add explanation about presence of the v15 file. Should add v14-v15 changes to release notes.
- James Forsyth will see how other teams manage merging release bug/security/late feature change back to master for Dublin release.
...