Low Update: See AWS support in https://wiki.onap.org/display/DW/Cloud+Native+Deployment#CloudNativeDeployment-AmazonAWS
Overall epic on migrating our design time heat templates to cloudFormation as well as runtime orchestration plugin abstractions for AWS on top of the existing OpenStack.
Part of getting another infrastructure provider like AWS to work with ONAP will be in identifying and decoupling southbound logic from any particular cloud provider using an extensible plugin architecture on the SBI interface.
see
https://wiki.onap.org/display/DW/ONAP+on+AWS
https://wiki.onap.org/pages/viewpage.action?pageId=3247262
https://wiki.onap.org/pages/viewpage.action?pageId=5735532
https://wiki.onap.org/pages/viewpage.action?pageId=4719246
https://wiki.onap.org/pages/viewpage.action?pageId=3246809
https://wiki.onap.org/pages/viewpage.action?pageId=3247305
ami-b8f3f3c3 : onap-oom-k8s-10
- duplicates
-
INT-120
Deployment Status Sanity - Daily auto E2E verification status of the build
-
- Closed
-
-
LOG-320
CD: OOM deployment templates for public cloud (Arm, CloudFormation, Heat)
-
- Closed
-
-
LOG-332
Deployment CI/CD Integration Jenkins job using OOM-K8S - to validate branch
-
- Closed
-
-
LOG-277 F2F: ONAP on Amazon AWS EC2 VM
-
- Closed
-
- links to