-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Cloud link to Azure topics #2713
Merged
Merged
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
697b86d
add Cloud link to Azure topics
063ce64
screen snaps, updates per latest on staging
7e45993
added link
7a4c5cd
resolved conflicts in TOC
3d545fc
added Azure accept EULA/enable subscription, more steps, snaps
67e2beb
fixed the comments to not break numbering
432f222
new snaps and review comments incorporated from Alberto and Ryan
6d057d1
added screen snaps, review comments, more steps
a6f9028
added screen snaps, detail to Azure create swarm
d397f53
new snap showing linked AWS as provider
516f12c
AWS screen snaps and detailed steps
9149e96
AWS swarm name rules clarification
94ea376
added x-refs to edition topics on config per reviews
de360fd
added connect screen snap w/production commands, AWS pricing
6c6f72a
added more code examples and clarification to swarm connect
04a28da
added more code examples for Azure and AWS
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
AWS screen snaps and detailed steps
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
- Loading branch information
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
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 |
---|---|---|
|
@@ -24,27 +24,65 @@ provider. | |
|
||
2. Click **Swarms** in the top navigation, then click **Create**. | ||
|
||
>**Tip:** Alternatively, you can select **+ -> Swarm** from the top navigation to get to the same page. | ||
Alternatively, you can select **+ -> Swarm** from the top navigation to get to the same page. | ||
|
||
3. Enter a name for the new swarm. | ||
3. Enter a name for the new swarm. | ||
|
||
4. Select a connected cloud services provider. | ||
Your Docker ID is pre-populated. In the example, our swarm name | ||
is "vote-swarm". | ||
|
||
<font style="color:red;">TBD: MAKE THIS SPECIFIC TO AWS AND ADD IMAGES THROUGHOUT</font> | ||
![](images/aws-create-swarm-1-name.png) | ||
|
||
<font style="color:red;">TBD from here down, Add info re: VPC for Region Advanced Settings, and other generic or AWS specific configurations. Generic configurations seem to be Swarm size and properties, along with manager and worker properties. (See Azure steps, which briefly cover these generic configs.)</font> | ||
>**Tip:** Use all lower case letters for swarm names. No spaces, capitalized letters, or special characters other than `.`, `_`, or `-` are allowed. | ||
|
||
5. Enter any additional provider-specific information, such as region. | ||
4. Select Amazon Web Services as the service provider, select a channel (`Stable` or `Edge`) from the drop-down menu, and provide an App name. | ||
|
||
> **Note:** For Amazon Web Services, the SSH keys that appear in this wizard are filtered by the region you select. Make sure that you have appropriate SSH keys available on the region you select. | ||
In this example, we'll use the `Stable` channel, and use "voting_app" as our application name. | ||
|
||
6. Choose how many swarm managers and swarm worker nodes to deploy. | ||
![](images/aws-create-swarm-0.png) | ||
|
||
5. Select a **Region** from the drop-down menu. | ||
|
||
> **Tip:** The SSH keys available to you in the next steps are | ||
filtered by the region you select here. Make sure that you have | ||
appropriate SSH keys available on the region you select. | ||
|
||
Optionally, click **Region Advanced Settings** to configure a | ||
[Virtual Private Cloud(VPC)](http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Introduction.html) on which to run this swarm. | ||
|
||
![](images/aws-create-swarm-3-region.png) | ||
|
||
For guidance on setting up a VPC, see [Recommended VPC and subnet setup](https://docs.docker.com/docker-for-aws/faqs/#can-i-use-my-existing-vpc) in the Docker for AWS topics. | ||
|
||
6. Choose how many swarm managers and swarm worker nodes to deploy. | ||
|
||
Here, we create one manager and two worker nodes. (This maps nicely to the [Swarm tutorial setup](/engine/swarm/swarm-tutorial/index.md) and the [voting app sample in Docker Labs](https://github.com/docker/labs/blob/master/beginner/chapters/votingapp.md).) | ||
|
||
![](images/cloud-create-swarm-4-size.png) | ||
|
||
7. Configure swarm properties. | ||
|
||
![](images/aws-create-swarm-5-properties.png) | ||
|
||
* Select a public SSH key for Docker Cloud to use to connect to the | ||
nodes on AWS. Public keys from the [key pairs you configured on AWS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) are provided in the drop-down menu. Only keys associated with the | ||
Region you selected (in step 5) are shown. | ||
|
||
* Choose whether to provide daily resource cleanup. | ||
|
||
* Enable or disable Cloudwatch for container logging. (It is enabled by default.) | ||
|
||
<font style="color:red;"> | ||
RYAN, ALBERTO:<br> | ||
Can you provide more detail here on what daily resource cleanup does and pros and cons of having this on/off?<br><br> | ||
Same for Cloudwatch for container logging, can you provide more detail? | ||
</font> | ||
|
||
7. Select the instance sizes for the managers, and for the workers. | ||
|
||
8. Select the SSH key to use to connect to the nodes. | ||
![](images/aws-create-swarm-6-manager-worker.png) | ||
|
||
The list contains any SSH keys that you have access to on your linked cloud services provider. Select the one for which you have the private key locally. | ||
<font style="color:red;">RYAN, ALBERTO: Should we add more detail on machine sizes?</font> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Here is a link to the instance options and pricing on Azure: https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/ Perhaps we could include a link. |
||
|
||
9. Click **Create**. | ||
|
||
|
@@ -54,9 +92,14 @@ provider. | |
when using Docker for AWS. (To learn more, see | ||
[Why Docker for AWS](/docker-for-aws/why.md).) | ||
|
||
> **Note**: At this time, you cannot add or remove nodes from a swarm from within Docker Cloud. To add new nodes or remove nodes from an existing swarm, | ||
log in to your AWS account, and add or delete nodes manually. (You can | ||
unregister or dissolve swarms directly from Docker Cloud.) | ||
This will take a few minutes. When the swarm is ready, its indicator on the Swarms page will show steady green. | ||
|
||
![](images/aws-create-swarm-7-list.png) | ||
|
||
> **Note**: At this time, you cannot add nodes to a swarm from | ||
within Docker Cloud. To add new nodes to an existing swarm, | ||
log in to your AWS account, and add nodes manually. (You can | ||
unregister or dissolve swarms directly from Docker Cloud.) | ||
|
||
## Where to go next | ||
|
||
|
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+66.7 KB
docker-cloud/cloud-swarm/images/aws-create-swarm-6-manager-worker.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed
BIN
-62.1 KB
docker-cloud/cloud-swarm/images/azure-create-swarm-7-list-callout.png
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified
BIN
+11.1 KB
(120%)
docker-cloud/cloud-swarm/images/azure-create-swarm-7-list.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Believe the primary advantage of leaving "daily resource cleanup" enabled is to avoid incurring charges for resources that you are no longer using. (cc: @alberto for confirmation)
Btw, here's the AWS doc on the topic: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_CleaningUp.html