-For Beijing Release, all the DCAE components are deployed in a single
-virtual machine.
-You must specify R2 to run R2 DCAE components.
-Is you are using R1 to get R1 ONAP, you must fill all the other
-DCAE parameters.
-Please refer to the Amsterdam documentation to fill these parameters.
+Depending on the set of DCAE compoennts to be deployed, you can select
+
+- R3 MVP - This profile includes a minimum set of DCAE components that will
+ support the vFW/vDNS, vCPE. and vVoLTE use cases. It will deploy the
+ following components: Consul server, Config Binding Service, Postgres
+ database, VES collector, TCA analytics, Holmes rule management, Holmes
+ engine management
+- R3 - This profile also deploys the rest of the DCAE platform. With R3
+ deployment profile, DCAE supports CLAMP and full control loop
+ functionalities. These additional components are: Cloudify Manager,
+ Deployment Handler, Policy Handler, Service Change Handler, Inventory API.
+- R3PLUS - This profile deploys the DCAE R2 stretch goal service components,
+ namely: PNF Registration Handler, SNMP Trap collector, HV-VES Collector,
+ Missing Heartbeat Detection analytics, Universal Mapper
+