* Adding "windows" label to Windows node.
Additional steps to add label to Windows Nodes. This will allow admin to filter Windows node when creating a service like this.
`docker service create --constraint engine.labels.os==windows --name winonly microsoft/nanoserver` The same steps are on this article: https://success.docker.com/article/how-can-i-assign-a-service-to-windows-nodes-only
* wrong environment variable fixed.
Replace all occurrences of
```foo
{% raw %}
bar
{% endraw %}
```
(which generates spurious empty lines in the rendered pre block) with
{% raw %}
```foo
bar
```
{% endraw %}
Also, fix some occurrences where the raw section is too large and
prevented interpretation of Jekyll directives.
This is the syntax used in the documentation of Jekyll itself:
https://raw.githubusercontent.com/jekyll/jekyll/master/docs/_docs/templates.md
FTR, done with two perl substitutions:
'^([\t ]*```[^\n]*
)([ \t]*\{% raw %\}[^\n]*
)' '$2$1'
and
'^([ \t]*\{% endraw %\}[^\n]*
)([\t ]*```[^\n]*
)' '$2$1'
and manually tweaks. A mechanical check would be most useful.
Signed-off-by: Akim Demaille <akim.demaille@docker.com>
* HRM and Window Servers
Note:- Windows Server doesn't support Swarm Mode Routing Mesh yet (not considering Windows Server version 1709 which will be out soon). This means the hrm service is exposed only through the manager node's ip (since Windows Server cannot be a manager node). Therefore the DNS entry for the host name ('wordpress.example.org' in this example) should be mapped to the manager node and not to any of the Windows worker nodes.
* HRM with Windows Server
HRM with Windows Server
* Reword lots of instances of 'will'
* Reword lots of instances of won't
* Reword lots of instances of we'll
* Eradicate you'll
* Eradicate 'be able to' type of phrases
* Eradicate 'unable to' type of phrases
* Eradicate 'has / have to' type of phrases
* Eradicate 'note that' type of phrases
* Eradicate 'in order to' type of phrases
* Redirect to official Chef and Puppet docs
* Eradicate gratuitous 'please'
* Reduce use of e.g.
* Reduce use of i.e.
* Reduce use of N.B.
* Get rid of 'sexagesimal' and correct some errors
Added:
Note that, when planning for host storage, workflows based around `docker pull` through UCP will result in higher storage requirements on manager nodes, since `docker pull` through UCP results in the image being pulled on all nodes.
This has become an issue for some customers who did not plan to make additional storage available on UCP managers.
* Added Language regarding FW Ports
Added additional language regarding system requirements and firewall ports to UCP installation.
* Update url to be relative instead of absolute
Maria Bermudez