Wish all of you have a happy and rich New Year~ There are quite a few of friends who polled for Multi Cloud weekly meeting in the past vacation weeks, where the top vote is “5:00 PM to 6:00PM PST Monday” and the second is “8:00 PM to 9:00PM PST Thursday”. I would like to get your attention here and collect your feedback if you feel too hard to fit into the identified slots before 5:00 PM to 6:00PM PST, Jan.7. We will schedule the meeting time then.
It is not easy to get a slot comfortable for everyone considering our ONAP community has so many contributors coming from different time zones. We treasure your attendance to Multi Cloud project weekly meetings. If the feedbacks show it is impossible to bring everyone into one single slot, we can switch the meeting schedule in odd and even weeks. Please refer to https://doodle.com/poll/4s5snzshutawrf3i for more details. You can also leave your vote/comments there for more people to know your preference and mitigate the gap together. Thanks for your understanding and support to this project. Xinhui Li PTL of Multi Cloud From: Xinhui Li <lxin...@vmware.com> Date: Friday, 8 December 2017 at 6:18 PM To: onap-discuss <onap-discuss@lists.onap.org> Cc: Kenny Paul <kp...@linuxfoundation.org> Subject: [onap-discuss][multicloud] Multi Cloud Project Weekly Promotions Hi, A reminder here, our Multi Cloud weekly meeting has been moved to 5:00 AM pacific time. I would like to remind you to finish the doodle poll https://doodle.com/poll/4s5snzshutawrf3i if you are interested at Multi Cloud project and do not poll yet. Moreover, I encourage you to leave comments on your poll about if you want keep the current time as option or you want some time fit for your specific time zone. The coming week is our ONAP Beijing Release Developer Forum. I would like to promote several topics/panels about Multi VIM/Cloud Project: (1) Multi Cloud Evolvement in R2 for Carrier Grade Support Tuesday, December 12 • 11:45am - 12:30pm, SC12-167-11 Multi VIM/Cloud team has successfully delivered R1. What is the right path and practical way to evolve forward and achieve the goal of carrier-grade in Beijing release? In this session, we will use a retrospective of R1 delivery cycle to elaborate an architectural design evolvement with consideration to both functional and non-functional perspectives for suggestions/comments. (2) Achieving ONAP S3P with Standardized Object Model of Multi-Clouds Tuesday, December 12 • 1:45pm - 2:30pm, Auditorium Today multi cloud objects and their hierarchical relationships are modeled in a cloud-specific way creating inconsistent modeling of similar features across multi clouds. The challenge is in both data management and interoperability among ONAP components such as onboarding, policy management, orchestration, optimization etc. This presentation discusses standardized Information Models for multi cloud objects (Physical/Logical DC, Tenant, Cluster, Host, VM, Container etc.) in terms of capabilities (platform awareness etc.), resource reservation/utilization and other parameters for current and future cloud implementations. It also discusses the hierarchical relationships between those multi cloud objects. It illustrates how policy, data management and optimization frameworks can benefit from this standardization through concrete examples thus addressing the challenges of ONAP R2 & beyond. (3) Enabling Workloads Orchestration in Containers via Multi Cloud Wednesday, December 13 • 4:15pm - 4:50pm, Auditorium Today ONAP OOM enables deployment of ONAP components as containerized micro services in a k8s cluster. On the other hand, workload deployment and orchestration in k8s clusters is expected to play an essential role in ONAP operational success. This presentation discusses an architectural vision of orchestrating workloads in container clusters via Multi Cloud. The key aspects for a comprehensive ONAP workloads orchestration are discussed, including deploying containerized workloads, e.g. VNFs [IETF NFVRG Talk], into k8s clusters on bare metal in edge cloud. ONAP Multi Cloud component serves as a single platform for deployment and orchestration of containerized workloads as well as classical VM-based workloads in true multiple infrastructures, including clouds, k8s on CaaS/cloud, k8s on bare metal, etc. It simplifies workload management and improves ONAP’s user experience. (4) Towards a Comprehensive ONAP Operations Management Solution December 11 • 5:00pm - 5:30pm SC12-175-38 Moreover, we will share one demo where VMware VIO 4.0 Cloud instance runs in the core data center hosting the ONAP components and vDNS VNF and a Wind River Titanium Cloud instance runs in the edge data center and hosts the vFW VNF. Xinhui Li PTL Multi Cloud
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
