mirror of https://github.com/docker/docs.git
Changes from peer review
This commit is contained in:
art
Joao Fernandes
parent
bf82a6b706
commit
1ff6bcd429
|
|
@ -55,7 +55,7 @@ To create a Docker EE for IBM Cloud cluster from the CLI:
|
|||
| `--hardware` | If "dedicated" then the nodes are created on hosts with compute instances in the same account. | Shared | Optional |
|
||||
| `--manager-machine-type` | The machine type of the manager nodes: u1c.1x2, u1c.2x4, b1c.4x16, b1c.16x64, b1c.32x128, or b1c.56x242. More powerful machine types cost more, but deliver better performance. For example, u1c.2x4 is 2 cores and 4 GB memory, and b1c.56x242 is 56 cores and 242 GB memory. | b1c.4x16 | Optional |
|
||||
| `--worker-machine-type` | The machine type of the worker nodes: u1c.1x2, u1c.2x4, b1c.4x16, b1c.16x64, b1c.32x128, or b1c.56x242. More powerful machine types cost more, but deliver better performance. For example, u1c.2x4 is 2 cores and 4 GB memory, and b1c.56x242 is 56 cores and 242 GB memory. | u1c.1x2 | Optional |
|
||||
| `--disable-dtr-storage` | By default, the `bx d4ic create` command orders an IBM Cloud Swift API Object Storage account and creates a container named `dtr-container`. If you want to prevent this, include the `--disable-dtr-storage`. Note that you must then [set up IBM Cloud Object Storage](dtr-ibm-cos.md) yourself so that DTR works with your cluster. | Enabled by default. | Optional |
|
||||
| `--disable-dtr-storage` | By default, the `bx d4ic create` command orders an IBM Cloud Swift API Object Storage account and creates a container named `dtr-container`. If you want to prevent this, include the `--disable-dtr-storage`. Then, [set up IBM Cloud Object Storage](dtr-ibm-cos.md) yourself so that DTR works with your cluster. | Enabled by default. | Optional |
|
||||
|
||||
4. Create the cluster. Use the `--swarm-name` flag to name your cluster, and fill in the credentials, SSH, and Docker EE installation URL variables with the information that you retrieved before you began.
|
||||
|
||||
|
|
@ -68,9 +68,9 @@ To create a Docker EE for IBM Cloud cluster from the CLI:
|
|||
--docker-ee-url my_docker-ee-url
|
||||
```
|
||||
|
||||
> Tip to set environment variables
|
||||
> Set environment variables
|
||||
>
|
||||
> You can set your infrastructure API credentials and Docker EE installation URL as environment variables so that you do not have to include them as options when using `bx d4ic` commands. For example:
|
||||
> You can set your infrastructure API credentials and Docker EE installation URL as environment variables so that you do not need to include them as options when using `bx d4ic` commands. For example:
|
||||
>
|
||||
> export SOFTLAYER_USERNAME=user.name.1234567
|
||||
>
|
||||
|
|
@ -114,40 +114,40 @@ To create a Docker EE for IBM Cloud cluster from the CLI:
|
|||
|
||||
{% raw %}
|
||||
```bash
|
||||
$ bx d4ic show --swarm-name cluster-name --sl-user user.name.1234567 --sl-api-key api_key
|
||||
Getting swarm information...
|
||||
Infrastructure Details
|
||||
$ bx d4ic show --swarm-name cluster-name --sl-user user.name.1234567 --sl-api-key api_key
|
||||
Getting swarm information...
|
||||
Infrastructure Details
|
||||
|
||||
Swarm
|
||||
ID ID
|
||||
Name cluster-name
|
||||
Created By user.name.1234567
|
||||
Swarm
|
||||
ID ID
|
||||
Name cluster-name
|
||||
Created By user.name.1234567
|
||||
|
||||
Nodes
|
||||
ID Name Public IP Private IP CPU Memory Datacenter Infrakit Group
|
||||
46506407 cluster-name-mgr1 169.##.###.## 10.###.###.## 2 4096 wdc07 managers
|
||||
...
|
||||
Nodes
|
||||
ID Name Public IP Private IP CPU Memory Datacenter Infrakit Group
|
||||
46506407 cluster-name-mgr1 169.##.###.## 10.###.###.## 2 4096 wdc07 managers
|
||||
...
|
||||
|
||||
Load Balancers
|
||||
ID Name Address Type
|
||||
ID-string cluster-name-mgr cluster-name-mgr-1234567-wdc07.lb.bluemix.net mgr
|
||||
...
|
||||
Load Balancers
|
||||
ID Name Address Type
|
||||
ID-string cluster-name-mgr cluster-name-mgr-1234567-wdc07.lb.bluemix.net mgr
|
||||
...
|
||||
|
||||
Subnets
|
||||
ID Gateway Datacenter
|
||||
ID-number 10.###.###.## wdc07
|
||||
Subnets
|
||||
ID Gateway Datacenter
|
||||
ID-number 10.###.###.## wdc07
|
||||
|
||||
NFS Volumes
|
||||
ID ID-number
|
||||
Mount Address fsf-wdc0701b-fz.adn.networklayer.com:/ID_number/data01
|
||||
Datacenter wdc07
|
||||
Capacity 20
|
||||
Type ENDURANCE_FILE_STORAGE
|
||||
Tier Level 10_IOPS_PER_GB
|
||||
NFS Volumes
|
||||
ID ID-number
|
||||
Mount Address fsf-wdc0701b-fz.adn.networklayer.com:/ID_number/data01
|
||||
Datacenter wdc07
|
||||
Capacity 20
|
||||
Type ENDURANCE_FILE_STORAGE
|
||||
Tier Level 10_IOPS_PER_GB
|
||||
|
||||
OK
|
||||
```
|
||||
{% endraw %}
|
||||
OK
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
After creating the cluster, [log in to Docker UCP and download the Docker UCP client certificate bundle](#use-the-universal-control-plane).
|
||||
|
||||
|
|
@ -157,9 +157,9 @@ Docker EE for IBM Cloud uses [Docker Universal Control Plane (UCP)](/datacenter/
|
|||
|
||||
### Access UCP
|
||||
|
||||
Before you begin, [create a cluster](#create-swarms). Note its **Name**, **ID**, and **UCP Password**.
|
||||
Before you begin, [create a cluster](#create-swarms). If you have the clsuter **Name**, **ID**, and **UCP Password**, proceed to Step 2.
|
||||
|
||||
1. If you have the **Name**, **ID**, and **UCP Password**, proceed to Step 2. Retrieve your UCP password by using the cluster **Name** and **ID** that you made when you [created the cluster](#create-swarms).
|
||||
1. Retrieve your UCP password by using the cluster **Name** and **ID** that you made when you [created the cluster](#create-swarms).
|
||||
|
||||
```bash
|
||||
$ docker logs cluster-name_ID
|
||||
|
|
@ -169,7 +169,8 @@ Before you begin, [create a cluster](#create-swarms). Note its **Name**, **ID**,
|
|||
...
|
||||
```
|
||||
|
||||
**Tip**: If you need to get the **Name** and **ID** of your cluster, run `bx d4ic list --sl-user SOFTLAYER_USERNAME --sl-api-key SOFTLAYER_API_KEY`.
|
||||
If you need to get the **Name** and **ID** of your cluster, run `bx d4ic list --sl-user SOFTLAYER_USERNAME --sl-api-key SOFTLAYER_API_KEY`.
|
||||
{:.tip}
|
||||
|
||||
2. Retrieve the **UCP URL** address.
|
||||
|
||||
|
|
@ -188,7 +189,7 @@ Before you begin, [create a cluster](#create-swarms). Note its **Name**, **ID**,
|
|||
1. [Access UCP](#access-ucp).
|
||||
2. Under your user name (for example, **admin**), click **My Profile**.
|
||||
3. Click **Client Bundles** > **New Client Bundle**. A zip file is generated.
|
||||
4. In the GUI, you are now shown a label and public key. You can edit the label by clicking the pencil icon and giving it a name, e.g., _d4ic-ucp_.
|
||||
4. In the GUI, you are now shown a label and public key. You can edit the label by clicking the pencil icon and giving it a name, such as _d4ic-ucp_.
|
||||
5. In a terminal, navigate and unzip the client bundle.
|
||||
|
||||
```bash
|
||||
|
|
@ -243,7 +244,7 @@ To gather logging and metric data from your swarm, first [enable logging for the
|
|||
|
||||
Docker EE for IBM Cloud employs a flexible architecture and integration with IBM Cloud that you can use to leverage IBM Cloud resources and customize your swarm environment. Docker EE UCP exposes the standard Docker API, and as such, includes certain functions that instead should be done by using Docker EE for IBM Cloud capabilities.
|
||||
|
||||
> Self-healing capabilities so you don't have to modify cluster infrastructure.
|
||||
> Self-healing capabilities so you don't need to modify cluster infrastructure.
|
||||
>
|
||||
> Docker EE for IBM Cloud uses the InfraKit toolkit to support self-healing infrastructure. After you create the swarm, the cluster maintains that specified number of nodes. If a manager node fails, you do not need to promote a worker node to manager; the swarm self-recovers the manager node.
|
||||
>
|
||||
|
|
@ -271,7 +272,7 @@ For IBM Cloud account access management, consult the [IBM Cloud Identity and Acc
|
|||
|
||||
For Docker EE cluster access management, use the [UCP Access Control documentation](/datacenter/ucp/2.2/guides/access-control/).
|
||||
|
||||
## Secure public network access to swarms
|
||||
## Control public network access to swarms
|
||||
|
||||
By default, Docker EE for IBM Cloud uses [IBM Cloud Security Groups](https://console.bluemix.net/docs/infrastructure/security-groups/sg_index.html#getting-started-with-security-groups) to control access to your clusters by setting rules for incoming and outgoing traffic. You need to have [permissions in your IBM Cloud infrastructure account](faqs.md#what-ibm-cloud-infrastructure-permissions-do-i-need) to manage security groups so that you can provision clusters with security groups. There are two security groups: one for the DTR and worker nodes, and one for the manager nodes.
|
||||
|
||||
|
|
@ -279,11 +280,11 @@ The security group for DTR and worker nodes blocks all traffic on the public net
|
|||
|
||||
The security group for the manager nodes allows public network traffic to the manager nodes only through port 56422. To access the cluster's manager nodes:
|
||||
|
||||
1. Log in to the IBM Cloud CLI. If you have a federated ID, use the `--sso` option.
|
||||
1. Log in to the IBM Cloud CLI. If you have a federated ID, use the `--sso` option.
|
||||
|
||||
```bash
|
||||
$ bx login [--sso]
|
||||
```
|
||||
```bash
|
||||
$ bx login [--sso]
|
||||
```
|
||||
|
||||
2. Target the IBM Cloud org and space:
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ $ bx d4ic create --sl-user SOFTLAYER_USERNAME --sl-api-key SOFTLAYER_API_KEY --s
|
|||
| `--hardware` | If "dedicated" then the nodes are created on hosts with compute instances in the same account. | Shared | Optional |
|
||||
| `--manager-machine-type` | The machine type of the manager nodes: u1c.1x2, u1c.2x4, b1c.4x16, b1c.16x64, b1c.32x128, or b1c.56x242. Higher machine types cost more, but deliver better performance: for example, u1c.2x4 is 2 cores and 4 GB memory, and b1c.56x242 is 56 cores and 242 GB memory. | b1c.4x16 | Optional |
|
||||
| `--worker-machine-type` | The machine type of the worker nodes: u1c.1x2, u1c.2x4, b1c.4x16, b1c.16x64, b1c.32x128, or b1c.56x242. Higher machine types cost more, but deliver better performance: for example, u1c.2x4 is 2 cores and 4 GB memory, and b1c.56x242 is 56 cores and 242 GB memory. | u1c.1x2 | Optional |
|
||||
| `--disable-dtr-storage` | By default, the `bx d4ic create` command orders an IBM Cloud Swift API Object Storage account and creates a container named `dtr-container`. If you want to prevent this, include the `--disable-dtr-storage`. Note that you must then [set up IBM Cloud Object Storage](dtr-ibm-cos.md) yourself so that DTR works with your cluster. | Enabled by default. | Optional |
|
||||
| `--disable-dtr-storage` | By default, the `bx d4ic create` command orders an IBM Cloud Swift API Object Storage account and creates a container named `dtr-container`. If you want to prevent this, include the `--disable-dtr-storage`. Then, [set up IBM Cloud Object Storage](dtr-ibm-cos.md) yourself so that DTR works with your cluster. | Enabled by default. | Optional |
|
||||
| `--version` | The Docker EE version of the created cluster. For the beta, only the default version is available. | Default version | Optional |
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ title: Set up IBM Cloud Object Storage for Docker Trusted Registry
|
|||
|
||||
# Use DTR with Docker EE for IBM Cloud
|
||||
|
||||
To use [Docker Trusted Registry (DTR)](docs.docker.com/datacenter/dtr/2.4/guides/) with Docker EE for IBM Cloud, DTR stores images on [IBM Cloud Object Storage (COS)](https://ibm-public-cos.github.io/crs-docs/).
|
||||
To use [Docker Trusted Registry (DTR)](/datacenter/dtr/2.4/guides/) with Docker EE for IBM Cloud, DTR stores images on [IBM Cloud Object Storage (COS)](https://ibm-public-cos.github.io/crs-docs/).
|
||||
|
||||
> COS for DTR enabled by default
|
||||
>
|
||||
|
|
@ -239,7 +239,7 @@ Verify that DTR is set up properly by [pulling and pushing an image](/datacenter
|
|||
|
||||
3. For the object storage **Account Name** that you want to delete, click the cancel icon.
|
||||
|
||||
> Tip to find your object storage account name
|
||||
> Find your object storage account name
|
||||
>
|
||||
> You can see the name of the swarm associated with the object storage account in the description field.
|
||||
> Alternatively, you can find the object storage account name for your swarm by running `bx d4ic show --swarm-name my_swarm --sl-user user.name.1234567 --sl-api-key api_key`.
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@ Congrats! Your Docker EE for IBM Cloud cluster is provisioning. First, the manag
|
|||
|
||||
## Step 4: Use UCP
|
||||
|
||||
Check it out: Docker for IBM Cloud uses [Docker Universal Control Plane (UCP)](/datacenter/ucp/2.2/guides/) to help you manage your cluster through a simple interface!
|
||||
Check it out: Docker for IBM Cloud uses [Docker Universal Control Plane (UCP)](/datacenter/ucp/2.2/guides/) to help you manage your cluster through a simple web UI!
|
||||
|
||||
### Step 4a: Access UCP
|
||||
|
||||
|
|
@ -128,7 +128,7 @@ We're almost done! We just need to download the UCP certificate bundle so that y
|
|||
|
||||
2. Click **Client Bundles** > **New Client Bundle**. A zip file is generated.
|
||||
|
||||
3. In the GUI, you are shown a labeland public key. You can edit the label by clicking the pencil icon and giving it a name, such as _d4ic-ucp_.
|
||||
3. In the GUI, you see a label and public key. To edit the label, click the pencil icon and give it a name, such as _d4ic-ucp_.
|
||||
|
||||
4. In a terminal, navigate and unzip the client bundle:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue