You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by si...@apache.org on 2019/09/04 04:38:23 UTC
[pulsar] branch master updated: [doc] Improve Pulsar deployment AWS
(#5093)
This is an automated email from the ASF dual-hosted git repository.
sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 16c15ed [doc] Improve Pulsar deployment AWS (#5093)
16c15ed is described below
commit 16c15edf4ffcbe7281165b6161e5a7a2433b07bb
Author: Monica-zy <44...@users.noreply.github.com>
AuthorDate: Wed Sep 4 12:38:18 2019 +0800
[doc] Improve Pulsar deployment AWS (#5093)
### Motivation
Improve the language and the overall descriptive style of the Pulsar Deployment document (deploy-aws section): http://pulsar.apache.org/docs/en/next/deploy-aws/
### Modifications
Adjust the tone, personal pronouns, voice also some typo errors of some sentences in the document.
---
site2/docs/deploy-aws.md | 83 +++++++++++++++++++++++-------------------------
1 file changed, 40 insertions(+), 43 deletions(-)
diff --git a/site2/docs/deploy-aws.md b/site2/docs/deploy-aws.md
index ab33285..62b0aab 100644
--- a/site2/docs/deploy-aws.md
+++ b/site2/docs/deploy-aws.md
@@ -6,17 +6,17 @@ sidebar_label: Amazon Web Services
> For instructions on deploying a single Pulsar cluster manually rather than using Terraform and Ansible, see [Deploying a Pulsar cluster on bare metal](deploy-bare-metal.md). For instructions on manually deploying a multi-cluster Pulsar instance, see [Deploying a Pulsar instance on bare metal](deploy-bare-metal-multi-cluster.md).
-One of the easiest ways to get a Pulsar [cluster](reference-terminology.md#cluster) running on [Amazon Web Services](https://aws.amazon.com/) (AWS) is to use the the [Terraform](https://terraform.io) infrastructure provisioning tool and the [Ansible](https://www.ansible.com) server automation tool. Terraform can create the resources necessary to run the Pulsar cluster---[EC2](https://aws.amazon.com/ec2/) instances, networking and security infrastructure, etc.---while Ansible can install [...]
+One of the easiest ways to get a Pulsar [cluster](reference-terminology.md#cluster) running on [Amazon Web Services](https://aws.amazon.com/) (AWS) is to use the [Terraform](https://terraform.io) infrastructure provisioning tool and the [Ansible](https://www.ansible.com) server automation tool. Terraform can create the resources necessary for running the Pulsar cluster---[EC2](https://aws.amazon.com/ec2/) instances, networking and security infrastructure, etc.---While Ansible can install [...]
## Requirements and setup
-In order install a Pulsar cluster on AWS using Terraform and Ansible, you'll need:
+In order to install a Pulsar cluster on AWS using Terraform and Ansible, you need to prepare the following things:
* An [AWS account](https://aws.amazon.com/account/) and the [`aws`](https://aws.amazon.com/cli/) command-line tool
* Python and [pip](https://pip.pypa.io/en/stable/)
* The [`terraform-inventory`](https://github.com/adammck/terraform-inventory) tool, which enables Ansible to use Terraform artifacts
-You'll also need to make sure that you're currently logged into your AWS account via the `aws` tool:
+You also need to make sure that you are currently logged into your AWS account via the `aws` tool:
```bash
$ aws configure
@@ -32,7 +32,7 @@ $ pip install ansible
You can install Terraform using the instructions [here](https://www.terraform.io/intro/getting-started/install.html).
-You'll also need to have the Terraform and Ansible configurations for Pulsar locally on your machine. They're contained in Pulsar's [GitHub repository](https://github.com/apache/pulsar), which you can fetch using Git:
+You also need to have the Terraform and Ansible configuration for Pulsar locally on your machine. You can find them in the [GitHub repository](https://github.com/apache/pulsar) of Pulsar, which you can fetch using Git commands:
```bash
$ git clone https://github.com/apache/pulsar
@@ -41,11 +41,11 @@ $ cd pulsar/deployment/terraform-ansible/aws
## SSH setup
-> If you already have an SSH key and would like to use it, you skip generating the SSH keys and update `private_key_file` setting
+> If you already have an SSH key and want to use it, you can skip the step of generating an SSH key and update `private_key_file` setting
> in `ansible.cfg` file and `public_key_path` setting in `terraform.tfvars` file.
>
-> For example, if you already had a private SSH key in `~/.ssh/pulsar_aws` and a public key in `~/.ssh/pulsar_aws.pub`,
-> you can do followings:
+> For example, if you already have a private SSH key in `~/.ssh/pulsar_aws` and a public key in `~/.ssh/pulsar_aws.pub`,
+> follow the steps below:
>
> 1. update `ansible.cfg` with following values:
>
@@ -59,35 +59,35 @@ $ cd pulsar/deployment/terraform-ansible/aws
> public_key_path=~/.ssh/pulsar_aws.pub
> ```
-In order to create the necessary AWS resources using Terraform, you'll need to create an SSH key. To create a private SSH key in `~/.ssh/id_rsa` and a public key in `~/.ssh/id_rsa.pub`:
+In order to create the necessary AWS resources using Terraform, you need to create an SSH key. Enter the following commands to create a private SSH key in `~/.ssh/id_rsa` and a public key in `~/.ssh/id_rsa.pub`:
```bash
$ ssh-keygen -t rsa
```
-Do *not* enter a passphrase (hit **Enter** when prompted instead). To verify that a key has been created:
+Do *not* enter a passphrase (hit **Enter** instead when the prompt comes out). Enter the following command to verify that a key has been created:
```bash
$ ls ~/.ssh
id_rsa id_rsa.pub
```
-## Creating AWS resources using Terraform
+## Create AWS resources using Terraform
-To get started building AWS resources with Terraform, you'll need to install all Terraform dependencies:
+To start building AWS resources with Terraform, you need to install all Terraform dependencies. Enter the follwing command:
```bash
$ terraform init
# This will create a .terraform folder
```
-Once you've done that, you can apply the default Terraform configuration:
+After that, you can apply the default Terraform configuration by entering this command:
```bash
$ terraform apply
```
-You should then see this prompt:
+Then you see this prompt below:
```bash
Do you want to perform these actions?
@@ -97,28 +97,28 @@ Do you want to perform these actions?
Enter a value:
```
-Type `yes` and hit **Enter**. Applying the configuration could take several minutes. When it's finished, you should see `Apply complete!` along with some other information, including the number of resources created.
+Type `yes` and hit **Enter**. Applying the configuration could take several minutes. When the configuration applying finishes, you can see `Apply complete!` along with some other information, including the number of resources created.
-### Applying a non-default configuration
+### Apply a non-default configuration
You can apply a non-default Terraform configuration by changing the values in the `terraform.tfvars` file. The following variables are available:
Variable name | Description | Default
:-------------|:------------|:-------
-`public_key_path` | The path of the public key that you've generated. | `~/.ssh/id_rsa.pub`
-`region` | The AWS region in which the Pulsar cluster will run | `us-west-2`
-`availability_zone` | The AWS availability zone in which the Pulsar cluster will run | `us-west-2a`
-`aws_ami` | The [Amazon Machine Image](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html) (AMI) that will be used by the cluster | `ami-9fa343e7`
+`public_key_path` | The path of the public key that you have generated. | `~/.ssh/id_rsa.pub`
+`region` | The AWS region in which the Pulsar cluster runs | `us-west-2`
+`availability_zone` | The AWS availability zone in which the Pulsar cluster runs | `us-west-2a`
+`aws_ami` | The [Amazon Machine Image](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html) (AMI) that the cluster uses | `ami-9fa343e7`
`num_zookeeper_nodes` | The number of [ZooKeeper](https://zookeeper.apache.org) nodes in the ZooKeeper cluster | 3
-`num_bookie_nodes` | The number of bookies that will run in the cluster | 3
-`num_broker_nodes` | The number of Pulsar brokers that will run in the cluster | 2
-`num_proxy_nodes` | The number of Pulsar proxies that will run in the cluster | 1
-`base_cidr_block` | The root [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) that will be used by network assets for the cluster | `10.0.0.0/16`
+`num_bookie_nodes` | The number of bookies that runs in the cluster | 3
+`num_broker_nodes` | The number of Pulsar brokers that runs in the cluster | 2
+`num_proxy_nodes` | The number of Pulsar proxies that runs in the cluster | 1
+`base_cidr_block` | The root [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) that network assets uses for the cluster | `10.0.0.0/16`
`instance_types` | The EC2 instance types to be used. This variable is a map with two keys: `zookeeper` for the ZooKeeper instances, `bookie` for the BookKeeper bookies and `broker` and `proxy` for Pulsar brokers and bookies | `t2.small` (ZooKeeper), `i3.xlarge` (BookKeeper) and `c5.2xlarge` (Brokers/Proxies)
### What is installed
-When you run the Ansible playbook, the following AWS resources will be used:
+When you run the Ansible playbook, the following AWS resources are used:
* 9 total [Elastic Compute Cloud](https://aws.amazon.com/ec2) (EC2) instances running the [ami-9fa343e7](https://access.redhat.com/articles/3135091) Amazon Machine Image (AMI), which runs [Red Hat Enterprise Linux (RHEL) 7.4](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/7.4_release_notes/index). By default, that includes:
* 3 small VMs for ZooKeeper ([t2.small](https://www.ec2instances.info/?selected=t2.small) instances)
@@ -131,23 +131,23 @@ When you run the Ansible playbook, the following AWS resources will be used:
* A [route table](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Route_Tables.html) for the Pulsar cluster's VPC
* A [subnet](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html) for the VPC
-All EC2 instances for the cluster will run in the [us-west-2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) region.
+All EC2 instances for the cluster run in the [us-west-2](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) region.
-### Fetching your Pulsar connection URL
+### Fetch your Pulsar connection URL
-When you apply the Terraform configuration by running `terraform apply`, Terraform will output a value for the `pulsar_service_url`. It should look something like this:
+When you apply the Terraform configuration by entering the command `terraform apply`, Terraform outputs a value for the `pulsar_service_url`. The value should look something like this:
```
pulsar://pulsar-elb-1800761694.us-west-2.elb.amazonaws.com:6650
```
-You can fetch that value at any time by running `terraform output pulsar_service_url` or parsing the `terraform.tstate` file (which is JSON, even though the filename doesn't reflect that):
+You can fetch that value at any time by entering the command `terraform output pulsar_service_url` or parsing the `terraform.tstate` file (which is JSON, even though the filename does not reflect that):
```bash
$ cat terraform.tfstate | jq .modules[0].outputs.pulsar_service_url.value
```
-### Destroying your cluster
+### Destroy your cluster
At any point, you can destroy all AWS resources associated with your cluster using Terraform's `destroy` command:
@@ -157,11 +157,9 @@ $ terraform destroy
## Setup Disks
-Before you run the Pulsar playbook, you want to mount the disks to the correct directories on those bookie nodes.
-Since different type of machines would have different disk layout, if you change the `instance_types` in your terraform
-config, you need to update the task defined in `setup-disk.yaml` file.
+Before you run the Pulsar playbook, you need to mount the disks to the correct directories on those bookie nodes. Since different type of machines have different disk layout, you need to update the task defined in `setup-disk.yaml` file after changing the `instance_types` in your terraform config,
-To setup disks on bookie nodes, use this command:
+To setup disks on bookie nodes, enter this command:
```bash
$ ansible-playbook \
@@ -170,13 +168,12 @@ $ ansible-playbook \
setup-disk.yaml
```
-After running this command, the disks will be mounted under `/mnt/journal` as journal disk, and `/mnt/storage` as ledger disk.
-It is important to run this command only once! If you attempt to run this command again after you have run Pulsar playbook,
-it might be potentially erase your disks again and cause the bookies to fail to start up.
+After that, the disks is mounted under `/mnt/journal` as journal disk, and `/mnt/storage` as ledger disk.
+Remember to enter this command just only once. If you attempt to enter this command again after you have run Pulsar playbook, your disks might potentially be erased again, causing the bookies to fail to start up.
-## Running the Pulsar playbook
+## Run the Pulsar playbook
-Once you've created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. To do so, use this command:
+Once you have created the necessary AWS resources using Terraform, you can install and run Pulsar on the Terraform-created EC2 instances using Ansible. To do so, enter this command:
```bash
$ ansible-playbook \
@@ -185,7 +182,7 @@ $ ansible-playbook \
../deploy-pulsar.yaml
```
-If you've created a private SSH key at a location different from `~/.ssh/id_rsa`, you can specify the different location using the `--private-key` flag:
+If you have created a private SSH key at a location different from `~/.ssh/id_rsa`, you can specify the different location using the `--private-key` flag in the following command:
```bash
$ ansible-playbook \
@@ -195,9 +192,9 @@ $ ansible-playbook \
../deploy-pulsar.yaml
```
-## Accessing the cluster
+## Access the cluster
-You can now access your running Pulsar using the unique Pulsar connection URL for your cluster, which you can obtain using the instructions [above](#fetching-your-pulsar-connection-url).
+You can now access your running Pulsar using the unique Pulsar connection URL for your cluster, which you can obtain following the instructions [above](#fetching-your-pulsar-connection-url).
For a quick demonstration of accessing the cluster, we can use the Python client for Pulsar and the Python shell. First, install the Pulsar Python module using pip:
@@ -211,7 +208,7 @@ Now, open up the Python shell using the `python` command:
$ python
```
-Once in the shell, run the following:
+Once you are in the shell, enter the following command:
```python
>>> import pulsar
@@ -222,5 +219,5 @@ Once in the shell, run the following:
>>> client.close()
```
-If all of these commands are successful, your cluster can now be used by Pulsar clients!
+If all of these commands are successful, Pulsar clients can now use your cluster!