Lusheng Ji | d7350c6 | 2017-10-13 22:49:06 +0000 | [diff] [blame] | 1 | CDAP |
Lusheng Ji | bd11574 | 2017-10-13 19:18:52 +0000 | [diff] [blame] | 2 | ====================== |
Lusheng Ji | f82a6c4 | 2017-10-13 17:56:38 +0000 | [diff] [blame] | 3 | |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 4 | Note: This blueprint is intended to be deployed, automatically, as part of the |
| 5 | DCAE bootstrap process, and is not normally invoked manually. |
Lusheng Ji | f82a6c4 | 2017-10-13 17:56:38 +0000 | [diff] [blame] | 6 | |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 7 | The ONAP DCAEGEN2 CDAP blueprint deploys a 7 node Cask Data Application |
| 8 | Platform (CDAP) cluster (version 4.1.x), for running data analysis |
| 9 | applications. The template for the blueprint is at |
| 10 | ``blueprints/cdapbp7.yaml-template`` in the ONAP |
| 11 | ``dcaegen2.platform.blueprints`` project. The ``02`` VM in the cluster |
| 12 | will be the CDAP master. |
Lusheng Ji | f82a6c4 | 2017-10-13 17:56:38 +0000 | [diff] [blame] | 13 | |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 14 | Blueprint Input Parameters |
Lusheng Ji | bd11574 | 2017-10-13 19:18:52 +0000 | [diff] [blame] | 15 | --------------------- |
Lusheng Ji | f82a6c4 | 2017-10-13 17:56:38 +0000 | [diff] [blame] | 16 | |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 17 | This blueprint has the following required input parameters: |
Lusheng Ji | f82a6c4 | 2017-10-13 17:56:38 +0000 | [diff] [blame] | 18 | |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 19 | * ``ubuntu1604image_id`` |
Lusheng Ji | f82a6c4 | 2017-10-13 17:56:38 +0000 | [diff] [blame] | 20 | |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 21 | This is the OpenStack image ID of the Ubuntu 16.04 VM image that will be |
| 22 | used to launch the 7 VMs making up the cluster. |
Lusheng Ji | f82a6c4 | 2017-10-13 17:56:38 +0000 | [diff] [blame] | 23 | |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 24 | * ``flavor_id`` |
| 25 | |
| 26 | This is the OpenStack flavor ID specifying the amount of memory, disk, and |
| 27 | CPU available to each VM in the cluster. While the required values will be |
| 28 | largely application dependent, a minimum of 32 Gigabytes of memory is |
| 29 | strongly recommended. |
| 30 | |
| 31 | * ``security_group`` |
| 32 | |
| 33 | This is the OpenStack security group specifying permitted inbound and |
| 34 | outbound IP connectivity to the VMs in the cluster. |
| 35 | |
| 36 | * ``public_net`` |
| 37 | |
| 38 | This is the name of the OpenStack network from which floating IP addresses |
| 39 | for the VMs in the cluster will be allocated. |
| 40 | |
| 41 | * ``private_net`` |
| 42 | |
| 43 | This is the name of the OpenStack network from which fixed IP addresses for |
| 44 | the VMs in the cluster will be allocated. |
| 45 | |
| 46 | * ``openstack`` |
| 47 | |
| 48 | This is the JSON object / YAML associative array providing values necessary |
| 49 | for accessing OpenStack. The keys are: |
| 50 | |
| 51 | * ``auth_url`` |
| 52 | |
| 53 | The URL for accessing the OpenStack Identity V2 API. (The version of |
| 54 | Cloudify currently being used, and the associated OpenStack plugin do |
| 55 | not currently support Identity V3). |
| 56 | |
| 57 | * ``tenant_name`` |
| 58 | |
| 59 | The name of the OpenStack tenant/project where the VMs will be launched. |
| 60 | |
| 61 | * ``region`` |
| 62 | |
| 63 | The name of the OpenStack region within the deployment. In smaller |
| 64 | OpenStack deployments, where there is only one region, the region is |
| 65 | often named ``RegionOne``. |
| 66 | |
| 67 | * ``username`` |
| 68 | |
| 69 | The name of the OpenStack user used as a credential for accessing |
| 70 | OpenStack. |
| 71 | |
| 72 | * ``password`` |
| 73 | |
| 74 | The password of the OpenStack user. (The version of Cloudify currently |
| 75 | being used does not provide a mechanism for encrypting this value). |
| 76 | |
| 77 | * ``keypair`` |
| 78 | |
| 79 | The name of the ssh "key pair", within OpenStack, that will be given access, |
| 80 | via the ubuntu login, to the VMs. Note: OpenStack actually stores only the |
| 81 | public key. |
| 82 | |
| 83 | * ``key_filename`` |
| 84 | |
| 85 | The full file path, on the Cloudify Manager VM used to deploy this blueprint, |
| 86 | of the ssh private key file corresponding to the ``keypair`` input parameter. |
| 87 | |
| 88 | * ``location_domain`` |
| 89 | |
| 90 | The DNS domain/zone for DNS entries associated with the VMs in the cluster. |
| 91 | If, for example, location_domain is ``dcae.example.com`` then the FQDN for |
| 92 | a VM with hostname ``abcd`` would be ``abcd.dcae.example.com`` and a DNS |
| 93 | lookup of that FQDN would lead an A (or AAAA) record giving the floating |
| 94 | IP address assigned to that VM. |
| 95 | |
| 96 | * ``location_prefix`` |
| 97 | |
| 98 | The hostname prefix for hostnames of VMs in the cluster. The hostnames |
| 99 | assigned to the VMs are created by concatenating this prefix with a suffix |
| 100 | identifying the individual VMs in the cluster (``cdap00``, ``cdap01``, ..., |
| 101 | ``cdap06``). If the location prefix is ``jupiter`` then the hostname of |
| 102 | the CDAP master in the cluster would be ``jupitercdap02``. |
| 103 | |
| 104 | * ``codesource_url`` and ``codesource_version`` |
| 105 | |
| 106 | ``codesource_url`` is the base URL for downloading DCAE specific project |
| 107 | installation scripts. The intent is that this URL may be environment |
| 108 | dependent, (for example it may, for security reasons, point to an internal |
| 109 | mirror). This is used in combination with the ``codesource_version`` input |
| 110 | parameter to determine the URL for downloading the scripts. There are 2 |
| 111 | scripts used by this blueprint - ``cdap-init.sh`` and |
| 112 | ``instconsulagentub16.sh`` These scripts are part of the |
| 113 | dcaegen2.deployments ONAP project. This blueprint assumes that curl/wget |
| 114 | can find these scripts at |
Lusheng Ji | 776ddf5 | 2017-10-17 11:57:09 -0400 | [diff] [blame] | 115 | *codesource_url/codesource_version*\ ``/cloud_init/cdap-init.sh`` and |
| 116 | *codesource_url/codesource_version*\ ``/cloud_init/instconsulagentub16.sh`` |
Andrew Gauld | 8a47174 | 2017-10-16 14:22:20 -0400 | [diff] [blame] | 117 | respectively. For example, if codesource_url is |
| 118 | ``https://mymirror.example.com`` and codesource_version is ``rel1.0``, |
| 119 | then the installation scripts would be expected to be stored under |
| 120 | ``https://mymirror.example.com/rel1.0/raw/cloud_init/`` |
| 121 | |
| 122 | This blueprint has the following optional inputs: |
| 123 | |
| 124 | * ``location_id`` (default ``solutioning-central``) |
| 125 | |
| 126 | The name of the Consul cluster to register this CDAP cluster with. |
| 127 | |
| 128 | * ``cdap_cluster_name`` (default ``cdap``) |
| 129 | |
| 130 | The name of the service to register this cluster as, in Consul. |