Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

Rolfes second doc branch #1736

Closed
wants to merge 13 commits into from

Conversation

rolfedh
Copy link

@rolfedh rolfedh commented Feb 2, 2016

Please review this WIP topic. The goal of the topic is to demonstrate a minimal HA Swarm cluster on a VCS. In this case we happen to be using AWS, but I've tried to keep that in the background. I'm having trouble with the following command not returning control to the command line, and would appreciate your help solving that issue.

Your comments and feedback are welcome.

Thanks in advance.

Rolfe

Rolfe Dlugy-Hegwer added 2 commits February 1, 2016 23:57
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>

## Create your hosts

Here, you create five Linux hosts that are part of the "Docker Swarm Example" security group and install Docker Engine on each one.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it looks like you've moved installing the engine out of "here", and into the next section

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

@amitshukla amitshukla added this to the 1.1.0 milestone Feb 2, 2016
| HTTP | TCP | 80 | 0.0.0.0/0 | Container images |
| Custom TCP Rule | TCP | 2375 | 172.30.0.0/24 | Non-TLS traffic |
| Custom TCP Rule | TCP | 8500 | 172.30.0.0/24 | Consul discovery |
| Custom TCP Rule | TCP | 4000 | 172.30.0.0/24 | Swarm HA managers |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be worth explicitly noting that this network setup means we don't need to secure the Engine, Swarm, and Consul ports, as they're only accessible from within the private network - possibly during the setup steps below.

Someone scanning it may miss it, and we really don't want more unencrypted Docker ports out there (we have way too many already)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not quite sure what you'd like to see done. But I've updated the content.

Rolfe Dlugy-Hegwer added 11 commits February 2, 2016 22:00
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
Signed-off-by: Rolfe Dlugy-Hegwer <rollfedh-contractor@docker.com>
@SvenDowideit
Copy link
Contributor

I'm going to carry this PR and then we'll iterate on it tomorrow in a new PR.

@SvenDowideit
Copy link
Contributor

replaced by #1753 , closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants