|
4 | 4 |
|
5 | 5 | To use AWS, we need to sign up an AWS account on Amazon's Web site.
|
6 | 6 | An AWS account allows us to login to the AWS Console Web interface to
|
7 |
| -create IAM users and user groups. Usually, we create a user group with |
| 7 | +create IAM users and user groups. Usually, we create a user group with |
8 | 8 | privileges required to run PaddlePaddle, and we create users for
|
9 | 9 | those who are going to run PaddlePaddle and add these users into the
|
10 |
| -group. IAM users can identify themselves using password and tokens, |
| 10 | +group. IAM users can identify themselves using password and tokens, |
11 | 11 | where passwords allows users to log in to the AWS Console, and tokens
|
12 | 12 | make it easy for users to submit and inspect jobs from the command
|
13 | 13 | line.
|
@@ -360,7 +360,7 @@ In one time of distributed training, user will confirm the PaddlePaddle node num
|
360 | 360 |
|
361 | 361 | ####Create PaddlePaddle Node
|
362 | 362 |
|
363 |
| -After Kubernetes master gets the request, it will parse the yaml file and create several pods (defined by PaddlePaddle's node number), Kubernetes will allocate these pods onto cluster's node. A pod represents a PaddlePaddle node, when pod is successfully allocated onto one physical/virtual machine, Kubernetes will startup the container in the pod, and this container will use the environment variables in yaml file and start up `paddle pserver` and `paddle trainer` processes. |
| 363 | +After Kubernetes master gets the request, it will parse the yaml file and create several pods (defined by PaddlePaddle's node number), Kubernetes will allocate these pods onto cluster's node. A pod represents a PaddlePaddle node, when pod is successfully allocated onto one physical/virtual machine, Kubernetes will startup the container in the pod, and this container will use the environment variables in yaml file and start up `paddle pserver` and `paddle trainer` processes. |
364 | 364 |
|
365 | 365 |
|
366 | 366 | ####Start up Training
|
@@ -661,6 +661,6 @@ Sometimes we might need to create or manage the cluster on AWS manually with lim
|
661 | 661 | ### Some Presumptions
|
662 | 662 |
|
663 | 663 | * Instances run on CoreOS, the official IAM.
|
664 |
| -* Kubernetes node use instance storage, no EBS get mounted. Etcd is running on additional node. |
| 664 | +* Kubernetes node use instance storage, no EBS get mounted. Etcd is running on additional node. |
665 | 665 | * For networking, we use Flannel network at this moment, we will use Calico solution later on.
|
666 | 666 | * When you create a service with Type=LoadBalancer, Kubernetes will create and ELB, and create a security group for the ELB.
|
0 commit comments