Closed huanganqing closed 6 years ago
Yes, you have to remove those components as these are not valid for an HDP3 blueprint.
You have to edit the blueprint_dynamic
variable https://github.com/hortonworks/ansible-hortonworks/blob/master/playbooks/group_vars/all#L161 - this is also to customize the blueprint to how you'd want your cluster to be.
You can find some examples in the group_vars
folder: https://github.com/hortonworks/ansible-hortonworks/tree/master/playbooks/group_vars
At some point in future, I'll try to make this more nicer (like include one of the files rather than manually edit the variable / copy past the text).
Thanks.
###########################
cluster configuration
###########################
cluster_name: 'WS-HDP'
ambari_version: '2.7.0.0' # must be the 4-part full version number
hdp_version: '3.0.0.0' # must be the 4-part full version number hdp_build_number: 'auto' # the HDP build number from docs.hortonworks.com (if set to 'auto', Ansible will try to get it from the repository)
hdf_version: '3.2.0.0' # must be the 4-part full version number hdf_build_number: 'auto' # the HDF build number from docs.hortonworks.com (if set to 'auto', Ansible will try to get it from the repository)
hdpsearch_version: '3.0.0' # must be the full version number hdpsearch_build_number: '100' # the HDP Search build number from docs.hortonworks.com (hardcoded to 100 for the moment)
repo_base_url: 'http://public-repo-1.hortonworks.com' # change this if using a Local Repository
playbooks/check_dynamic_blueprint.yml
Is there any way to get around this ? Thanks.