| Ethan Lynn | c918a20 | 2018-11-05 14:41:16 +0800 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 |
| 2 | .. International License. http://creativecommons.org/licenses/by/4.0 |
| 3 | .. Copyright (c) 2017-2018 VMware Inc. |
| 4 | |
| 5 | ================================================= |
| 6 | MultiCloud Plugin for VMware Integrated OpenStack |
| 7 | ================================================= |
| 8 | |
| 9 | |
| 10 | Supported features |
| 11 | ~~~~~~~~~~~~~~~~~~ |
| 12 | |
| 13 | Northbound APIs for SO |
| 14 | ---------------------- |
| 15 | |
| 16 | MultiCloud VIO Plugin supports OpenStack services proxy APIs since the beginning, and later |
| 17 | in Casablanca release, VIO plugin supports infra_workload API for SO. Use cases like vFW/vDNS |
| 18 | will leverage these APIs to instantiate VNFs. |
| 19 | |
| 20 | Northbound APIs for VF-C |
| 21 | ------------------------ |
| 22 | |
| 23 | MultiCloud VIP Plugin supports VF-C by legacy Open-O APIs, and these APIs evolved according |
| 24 | to the requirements of VF-C and use cases. VoLTE use case leverage these APIs to instantiate |
| 25 | VNFs. |
| 26 | |
| 27 | Support Placement Policies for OOF |
| 28 | ---------------------------------- |
| 29 | |
| 30 | Since Beijing release, to help OOF to make better placement decision, MultiCloud expose a capacity |
| 31 | check API. |
| 32 | |
| 33 | Support OpenStack Resources Discovery |
| 34 | ------------------------------------- |
| 35 | |
| 36 | When onboarding new VMware OpenStack through ESR UI, VIO plugin could discover current OpenStack |
| 37 | Resources like flavors/images/networks/hypervisors, and update them in A&AI. |
| 38 | |
| 39 | Support HPA Discovery |
| 40 | --------------------- |
| 41 | |
| 42 | The HPA information will be automatically discovered and registered during VIM onboarding process. |
| 43 | |
| 44 | Support Cloud Agnostic Placement Policies |
| 45 | ----------------------------------------- |
| 46 | |
| 47 | The cloud agnostic information like Guarantee/Burstable QoS will be automatically discovered and |
| 48 | registered during VIM onboarding process. |
| 49 | |
| 50 | Support Auto-Healing Close Loop |
| 51 | ------------------------------- |
| 52 | |
| 53 | Leveraging VESAgent for meter collectrion and healthy report, VIO plugin supports |
| 54 | the auto-healing/auto-scaling scenarios in ONAP. |
| 55 | |
| 56 | Support Events Federation |
| 57 | ------------------------- |
| 58 | |
| 59 | Federate the events of VIM layer with ONAP message bus, it provide direct help to HA fencing and improve the |
| 60 | efficiency of VM recover with performance verification. |
| 61 | |
| 62 | |
| 63 | Supported Use Cases |
| 64 | ~~~~~~~~~~~~~~~~~~~ |
| 65 | |
| 66 | **vFW/vDNS** |
| 67 | |
| 68 | |
| 69 | **vCPE** |
| 70 | |
| 71 | |
| 72 | **VoLTE** |
| 73 | |
| 74 | |
| 75 | |
| 76 | Cloud Agnostic Placement Policy Enablement |
| 77 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 78 | |
| 79 | Currently two types of cloud agnostic intent policies are supported by VIO plugin, Guaranteed QoS and Burstable QoS. |
| 80 | VIO plugin will register them when VIM onboard and OOF could make better placement decision based on these policies. |
| 81 | |
| 82 | **Enable on it on flavors** |
| 83 | |
| 84 | Discovering these kind of features are through flavor's extra-specs, when you set `quota:cpu_reservation_percent=100` |
| 85 | and `quota:memory_reservation_percent=100` in flavor, it will be recognized as `Guaranteed QoS` supported platform. |
| 86 | When you choose other percentage for CPU and memory reservation, it will be recognized as `Burstable QoS` supported platform. |
| 87 | Related information will be registered to A&AI. |
| 88 | |
| 89 | .. include:: Multicloud-Fake_Cloud-Guide.rst |