Hi all, I edited the Auto wiki use case page<https://wiki.opnfv.org/display/AUTO/Auto+Use+Cases> to capture what I mentioned on today’s call. See below. I can provide a walk-thru of progress toward the cloud-native stack described below next week, and the roadmap for integrating ONAP subsystems as described. I welcome any expressions of interest in or support of this work in the Models and VES projects. It’s also part of our broader effort to develop stacks that support edge cloud use cases, with integration of key ONAP subsystems as needed for semi-autonomous local cloud operation (related to what was, and still is ;-) proposed for the Edge<https://wiki.opnfv.org/display/PROJ/Multi-Access+Edge> and Armada<https://wiki.opnfv.org/display/PROJ/Armada> projects, proceeding for cloud-native under the Models and VES projects in the meantime).
Hybrid Cloud for R1 ONAP Deployment and Hybrid VNF Use Cases The diagram below (see link<https://wiki.opnfv.org/display/AUTO/Auto+Use+Cases>) illustrates two local cloud stacks (OpenStack, and cloud-native) which when used in combination represent one type of "hybrid cloud" environment. Hybrid clouds may be necessary to deploy VNFs that are partially cloud-native, i.e. include some VNFCs that are deployed in VMs under cloud control planes such as OpenStack. Work on a k8s-based cloud-native stack as illustrated below (the k8s nodes) is underway in the Models<https://wiki.opnfv.org/display/models/Models+Home> project, as part of a broader work on cloud-native stack options (see the tools<https://github.com/opnfv/models/tree/master/tools> folder in the Models repo). That k8s-based stack will be used as the local cloud control plane into which three key ONAP subsystems will be integrated: monitoring (VES), closed-loop control (DCAE, Policy), and orchestration (Multi-VIM, initially represented by Cloudify in standalone mode). See the VES Project Plan<https://wiki.opnfv.org/display/ves/Project+Plan> for info on how this relates to the Fraser release goals for VES. The other stack shown below is based on OpenStack Helm but could be any OpenStack-based OPNFV distribution. An OpenStack Helm based stack is expected to be ready to test with Auto early in 2018 (WIP in OpenStack), and the hybrid cloud use cases thus sometime after that. In the meantime, we can make progress with the cloud-native stack and establish the basic ONAP subsystem integration and test approaches described above. Thanks, Bryan Sullivan | AT&T
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
