forked from hortonworks/ansible-hortonworks
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated all documentation to reflect the project name change.
- Loading branch information
1 parent
8efebb0
commit e30d339
Showing
7 changed files
with
51 additions
and
51 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| ansible-hdp installation guide | ||
| ansible-hortonworks installation guide | ||
| ------------------------------ | ||
|
|
||
| * These Ansible playbooks will build a Cloud environment on AWS. | ||
|
|
@@ -106,24 +106,24 @@ Ansible AWS modules use the boto Python library. Boto can manage credentials usi | |
|
|
||
| # Clone the repository | ||
|
|
||
| Upload the ansible-hdp repository to the build node / workstation, preferable under the home folder. | ||
| Upload the ansible-hortonworks repository to the build node / workstation, preferable under the home folder. | ||
|
|
||
| If the build node / workstation can directly download the repository, run the following: | ||
|
|
||
| ``` | ||
| cd && git clone https://github.com/hortonworks/ansible-hdp.git | ||
| cd && git clone https://github.com/hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
| If your GitHub SSH key is installed, you can use the SSH link: | ||
|
|
||
| ``` | ||
| cd && git clone [email protected]:hortonworks/ansible-hdp.git | ||
| cd && git clone [email protected]:hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
|
|
||
| # Set the AWS variables | ||
|
|
||
| Modify the file at `~/ansible-hdp/inventory/aws/group_vars/all` to set the AWS configuration. | ||
| Modify the file at `~/ansible-hortonworks/inventory/aws/group_vars/all` to set the AWS configuration. | ||
|
|
||
|
|
||
| ## cloud_config | ||
|
|
@@ -173,7 +173,7 @@ Set first the `CLOUD_TO_USE` environment variable to `aws`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=aws | ||
| cd ~/ansible-hdp*/ && bash build_cloud.sh | ||
| cd ~/ansible-hortonworks*/ && bash build_cloud.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
@@ -187,7 +187,7 @@ source ~/ansible/bin/activate | |
|
|
||
| ## cluster config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/all` to set the cluster configuration. | ||
|
|
||
| | Variable | Description | | ||
| | -------------------------- | ----------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -225,7 +225,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster c | |
|
|
||
| ## ambari-server config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
|
|
||
| | Variable | Description | | ||
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -270,7 +270,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the | |
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
| | blueprint_name | The name of the blueprint as it will be stored in Ambari. | | ||
| | blueprint_file | The path to the blueprint file that will be uploaded to Ambari. It can be an absolute path or relative to the `roles/ambari-blueprint/templates` folder. The blueprint file can also contain [Jinja2 Template](http://jinja.pocoo.org/docs/dev/templates/) variables. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hdp/inventory/aws/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hortonworks/inventory/aws/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
|
|
||
|
|
||
| # Install the cluster | ||
|
|
@@ -281,7 +281,7 @@ Make sure you set the `CLOUD_TO_USE` environment variable to `aws`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=aws | ||
| cd ~/ansible-hdp*/ && bash install_cluster.sh | ||
| cd ~/ansible-hortonworks*/ && bash install_cluster.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| ansible-hdp installation guide | ||
| ansible-hortonworks installation guide | ||
| ------------------------------ | ||
|
|
||
| * These Ansible playbooks will build a Cloud environment on Azure. | ||
|
|
@@ -113,24 +113,24 @@ This node must be able to connect to the cluster nodes via SSH and to the Azure | |
|
|
||
| # Clone the repository | ||
|
|
||
| Upload the ansible-hdp repository to the build node / workstation, preferable under the home folder. | ||
| Upload the ansible-hortonworks repository to the build node / workstation, preferable under the home folder. | ||
|
|
||
| If the build node / workstation can directly download the repository, run the following: | ||
|
|
||
| ``` | ||
| cd && git clone https://github.com/hortonworks/ansible-hdp.git | ||
| cd && git clone https://github.com/hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
| If your GitHub SSH key is installed, you can use the SSH link: | ||
|
|
||
| ``` | ||
| cd && git clone [email protected]:hortonworks/ansible-hdp.git | ||
| cd && git clone [email protected]:hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
|
|
||
| # Set the Azure variables | ||
|
|
||
| Modify the file at `~/ansible-hdp/inventory/azure/group_vars/all` to set the Azure configuration. | ||
| Modify the file at `~/ansible-hortonworks/inventory/azure/group_vars/all` to set the Azure configuration. | ||
|
|
||
|
|
||
| ## cloud_config | ||
|
|
@@ -179,7 +179,7 @@ Set first the `CLOUD_TO_USE` environment variable to `azure`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=azure | ||
| cd ~/ansible-hdp*/ && bash build_cloud.sh | ||
| cd ~/ansible-hortonworks*/ && bash build_cloud.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
@@ -193,7 +193,7 @@ source ~/ansible/bin/activate | |
|
|
||
| ## cluster config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/all` to set the cluster configuration. | ||
|
|
||
| | Variable | Description | | ||
| | -------------------------- | ----------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -231,7 +231,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster c | |
|
|
||
| ## ambari-server config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
|
|
||
| | Variable | Description | | ||
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -276,7 +276,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the | |
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
| | blueprint_name | The name of the blueprint as it will be stored in Ambari. | | ||
| | blueprint_file | The path to the blueprint file that will be uploaded to Ambari. It can be an absolute path or relative to the `roles/ambari-blueprint/templates` folder. The blueprint file can also contain [Jinja2 Template](http://jinja.pocoo.org/docs/dev/templates/) variables. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hdp/inventory/azure/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hortonworks/inventory/azure/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
|
|
||
|
|
||
| # Install the cluster | ||
|
|
@@ -287,7 +287,7 @@ Make sure you set the `CLOUD_TO_USE` environment variable to `azure`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=azure | ||
| cd ~/ansible-hdp*/ && bash install_cluster.sh | ||
| cd ~/ansible-hortonworks*/ && bash install_cluster.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| ansible-hdp installation guide | ||
| ansible-hortonworks installation guide | ||
| ------------------------------ | ||
|
|
||
| * These Ansible playbooks will build a Cloud environment on Google Compute Engine. | ||
|
|
@@ -166,24 +166,24 @@ This is based on Google's [guide](https://cloud.google.com/compute/docs/instance | |
|
|
||
| # Clone the repository | ||
|
|
||
| Upload the ansible-hdp repository to the build node / workstation, preferable under the home folder. | ||
| Upload the ansible-hortonworks repository to the build node / workstation, preferable under the home folder. | ||
|
|
||
| If the build node / workstation can directly download the repository, run the following: | ||
|
|
||
| ``` | ||
| cd && git clone https://github.com/hortonworks/ansible-hdp.git | ||
| cd && git clone https://github.com/hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
| If your GitHub SSH key is installed, you can use the SSH link: | ||
|
|
||
| ``` | ||
| cd && git clone [email protected]:hortonworks/ansible-hdp.git | ||
| cd && git clone [email protected]:hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
|
|
||
| # Set the GCE variables | ||
|
|
||
| Modify the file at `~/ansible-hdp/inventory/gce/group_vars/all` to set the GCE configuration. | ||
| Modify the file at `~/ansible-hortonworks/inventory/gce/group_vars/all` to set the GCE configuration. | ||
|
|
||
|
|
||
| ## cloud_config | ||
|
|
@@ -239,7 +239,7 @@ Set first the `CLOUD_TO_USE` environment variable to `gce`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=gce | ||
| cd ~/ansible-hdp*/ && bash build_cloud.sh | ||
| cd ~/ansible-hortonworks*/ && bash build_cloud.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
@@ -253,7 +253,7 @@ source ~/ansible/bin/activate | |
|
|
||
| ## cluster config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/all` to set the cluster configuration. | ||
|
|
||
| | Variable | Description | | ||
| | -------------------------- | ----------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -291,7 +291,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster c | |
|
|
||
| ## ambari-server config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
|
|
||
| | Variable | Description | | ||
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -336,7 +336,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the | |
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
| | blueprint_name | The name of the blueprint as it will be stored in Ambari. | | ||
| | blueprint_file | The path to the blueprint file that will be uploaded to Ambari. It can be an absolute path or relative to the `roles/ambari-blueprint/templates` folder. The blueprint file can also contain [Jinja2 Template](http://jinja.pocoo.org/docs/dev/templates/) variables. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hdp/inventory/gce/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hortonworks/inventory/gce/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
|
|
||
|
|
||
| # Install the cluster | ||
|
|
@@ -347,7 +347,7 @@ Make sure you set the `CLOUD_TO_USE` environment variable to `gce`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=gce | ||
| cd ~/ansible-hdp*/ && bash install_cluster.sh | ||
| cd ~/ansible-hortonworks*/ && bash install_cluster.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| ansible-hdp installation guide | ||
| ansible-hortonworks installation guide | ||
| ------------------------------ | ||
|
|
||
| * These Ansible playbooks will build a Cloud environment on a private OpenStack. | ||
|
|
@@ -132,24 +132,24 @@ As OpenStack environments are usually private, you might need to build such a no | |
|
|
||
| # Clone the repository | ||
|
|
||
| Upload the ansible-hdp repository to the build node / workstation, preferable under the home folder. | ||
| Upload the ansible-hortonworks repository to the build node / workstation, preferable under the home folder. | ||
|
|
||
| If the build node / workstation can directly download the repository, run the following: | ||
|
|
||
| ``` | ||
| cd && git clone https://github.com/hortonworks/ansible-hdp.git | ||
| cd && git clone https://github.com/hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
| If your GitHub SSH key is installed, you can use the SSH link: | ||
|
|
||
| ``` | ||
| cd && git clone [email protected]:hortonworks/ansible-hdp.git | ||
| cd && git clone [email protected]:hortonworks/ansible-hortonworks.git | ||
| ``` | ||
|
|
||
|
|
||
| # Set the OpenStack variables | ||
|
|
||
| Modify the file at `~/ansible-hdp/inventory/openstack/group_vars/all` to set the OpenStack configuration. | ||
| Modify the file at `~/ansible-hortonworks/inventory/openstack/group_vars/all` to set the OpenStack configuration. | ||
|
|
||
|
|
||
| ## cloud_config | ||
|
|
@@ -192,7 +192,7 @@ Set first the `CLOUD_TO_USE` environment variable to `openstack`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=openstack | ||
| cd ~/ansible-hdp*/ && bash build_cloud.sh | ||
| cd ~/ansible-hortonworks*/ && bash build_cloud.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
@@ -207,7 +207,7 @@ source ~/*-openrc.sh | |
|
|
||
| ## cluster config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/all` to set the cluster configuration. | ||
|
|
||
| | Variable | Description | | ||
| | -------------------------- | ----------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -245,7 +245,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/all` to set the cluster c | |
|
|
||
| ## ambari-server config file | ||
|
|
||
| Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
| Modify the file at `~/ansible-hortonworks/playbooks/group_vars/ambari-server` to set the Ambari Server specific configuration. | ||
|
|
||
| | Variable | Description | | ||
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
|
|
@@ -290,7 +290,7 @@ Modify the file at `~/ansible-hdp/playbooks/group_vars/ambari-server` to set the | |
| | ------------------------------ | ---------------------------------------------------------------------------------------------------------- | | ||
| | blueprint_name | The name of the blueprint as it will be stored in Ambari. | | ||
| | blueprint_file | The path to the blueprint file that will be uploaded to Ambari. It can be an absolute path or relative to the `roles/ambari-blueprint/templates` folder. The blueprint file can also contain [Jinja2 Template](http://jinja.pocoo.org/docs/dev/templates/) variables. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hdp/inventory/openstack/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
| | blueprint_dynamic | Settings for the dynamic blueprint template - only used if `blueprint_file` is set to `blueprint_dynamic.j2`. The role names must match the roles from the inventory setting file `~/ansible-hortonworks/inventory/openstack/group_vars/all`. The chosen components are split into two lists: clients and services. The chosen Component layout must respect Ambari Blueprint restrictions - for example if a single `NAMENODE` is configured, there must also be a `SECONDARY_NAMENODE` component. | | ||
|
|
||
|
|
||
| # Install the cluster | ||
|
|
@@ -301,7 +301,7 @@ Make sure you set the `CLOUD_TO_USE` environment variable to `openstack`. | |
|
|
||
| ``` | ||
| export CLOUD_TO_USE=openstack | ||
| cd ~/ansible-hdp*/ && bash install_cluster.sh | ||
| cd ~/ansible-hortonworks*/ && bash install_cluster.sh | ||
| ``` | ||
|
|
||
| You may need to load the environment variables if this is a new session: | ||
|
|
||
Oops, something went wrong.