-
Bug
-
Resolution: Done
-
High
-
Amsterdam Release
-
None
Turn on the screen recorder in next manual vFW testing - and post to the ONAP wiki
at
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos#RunningtheONAPDemos-ONAPDeploymentVideos
For consumption by any other integration developer so they can reproduce the vFW with/without any documented workarounds.
This JIRA needs to block the Amsterdam release - it only requires a full E2E recording
I can make an AWS S3 folder available temporarily - if video size is an issue - and/or reduce the resolution/size
For example in 1.0 we distributed deployment, testing and closed-loop videos for HEAT and later for OOM (K8S) .
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos#RunningtheONAPDemos-ONAPDeploymentVideos
We need a recorded session of the E2E vFirewall use case for all 6 steps
see steps on
in demo.sh init (customer create, service model create) in vid deploy service model in vid create service instance in vid add vnf to service instance in demo.sh preload in vid vf-module creation in demo.sh appc
video examples
We can then also link under
https://wiki.onap.org/display/DW/Integration+Test+Labs
posted to
https://lists.onap.org/pipermail/onap-discuss/2017-November/006224.html
https://lists.onap.org/pipermail/onap-tsc/2017-November/003900.html
- blocks
-
INT-106 Stabilizing the ONAP master branch
- Closed
-
INT-342 preload step in ONAP demo setup fails
- Closed
-
INT-284 Proper Release Management for Deployments
- Closed
-
INT-300 CI-CD For ONAP master branch
- Closed
- relates to
-
DOC-176 Link into wiki content for ONAP usage - vFirewall use case + videos
- Closed
-
LOG-266 F2F: ONAP CI/CD using OOM Kubernetes
- Closed
-
INT-334 Finalize Heat Template for Amsterdam Release
- Closed
- links to