Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
Date
Attendees
Goals
Discussion items
Item | Who | Notes |
---|
Testing AAI | | - Gerrit review -2 model loader exposed an issue (known issue for alpine)
- Updated to use alpine
- Paul couldn't spin up docker container
- Testing uncovered a missing library
- Trial and error will be needed to discover dependency errors
- It is difficult for somebody to do it without a test environment
- Use windriver env to setup minimal set of ONAP services (SDC, AAF, DMaaP)
- SDC can be simulated (it simulates the model loader)
- Better to have a DMaaP and an SDC instance
- Health dist on the end to end robot is a good indication
- James Forsyth Jimmy will send a link with the Robot framework with the end to end script we must execute
- The best thing is to setup WindRiver lab is resource constrained, Integration wants us to setup a minimal lab to do the end2end lab
- Abhay Pujari has been doing some work on setting up a lab instance in the windriver space
- Run model loader @steve will publish model loader instructions on the wiki
- Good test, it is 90% there
- It only requires AAI and AAF
- Steve's script starts all required resources
- End to end model distribution is the best way to test model distribution
- Second best is to use Steve's script
- Need everything to flow into AAI
- First test the image in the minimal environment
- Then take the images to the integration environment to run the vFW use case
- Sparky can run some flows/Gizmo, Champ, if they can start that is good.
- Log into the windriver VPN - GUI -
- Create JIRA ticket ticket under open lab
- Request access to AAI tenant and AAF
- Follow instructions on Openlab access for AAI devs
- Spin up a couple of VMs
- Large flavor
- Install AAI using OOM
- Use read the docs guide
- Suggestion from Jimmy: do not re-invent the wheel, leverage the WindRiver environment
|
Action items