You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/operations/provision-controller.rst
+21-15Lines changed: 21 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ Automatic Provisioning
14
14
The community maintains shell scripts that automate the provisioning
15
15
of Deis controllers on different cloud providers.
16
16
In addition to launching the controller itself, these scripts also
17
-
use optimized base images,
18
-
generate SSH keys, firewall configs and other cloud infrastructure
17
+
use optimized base images,
18
+
generate SSH keys, firewall configs and other cloud infrastructure
19
19
per Deis best practices.
20
20
21
21
You can find instructions on automatic provisioning for:
@@ -29,16 +29,16 @@ Please note that even with automatic provisioning, you will still have to
29
29
30
30
Manual Provisioning
31
31
-------------------
32
-
If you want your controller on bare metal, a different cloud provider,
33
-
or would just rather provision things manually --no problem!
32
+
If you want your controller on bare metal, a different cloud provider,
33
+
or would just rather provision things manually --no problem!
34
34
Just remember with manual provisioning, you are in charge of:
35
35
36
36
* Ensuring system requirements are met
37
37
* SSH key generation and distribution
38
38
* Network configuration
39
39
40
40
.. important:: System Requirements
41
-
Most controllers require at least 2GB of system memory and 100GB of storage
41
+
Most controllers require at least 2GB of system memory and 100GB of storage
42
42
43
43
The general process for manual provisioning involves:
44
44
@@ -76,40 +76,46 @@ you must add "deis-controller" to the "admins" group on the Chef Server.
76
76
77
77
Hosted Chef
78
78
~~~~~~~~~~~
79
-
Users using Hosted Chef can perform these `steps` to add deis-controller to admin group.
79
+
For Hosted Chef, visit the `OpsCode management interface`_ to add
80
+
"deis-controller" to the "admins" group. These `steps`_ describe specifically
81
+
how to add users to groups in the management interface.
80
82
81
83
Open Source Chef
82
84
~~~~~~~~~~~~~~~~
83
85
84
-
For opensource chef one can use knife cli tool. First, set the EDITOR environment variable to your favourite text editor.
86
+
For Open Source Chef, use the knife cli tool. First, set the EDITOR environment
87
+
variable to your favourite text editor:
85
88
86
89
``$ export EDITOR=vim``
87
90
88
-
Now issue the command to edit ``deis-controller`` user.
91
+
Now issue the command to edit the "deis-controller" user.
89
92
90
93
``$ knife client edit deis-controller``
91
94
92
95
and update the 'admin' key to 'true'. The updated content should look similar to this.
93
96
94
-
.. code-block:: console
97
+
.. code-block:: json
95
98
96
-
{
99
+
{
97
100
"name": "deis-controller",
98
-
"public_key": "-----BEGIN PUBLIC KEY-----\nMaaBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwzKA3YNTw0qD8hcPiJpT\naYSpJI0sQF4u6/WpE4HAlGRHpjpoG/QwtuA4sosW+ebNXDbxKhDoQxsHnz97jDuZ\n4nvnTdaJRGygXABEkuUG68cV7asdGzn76bRT3GNa4LD+ekqJON7nCA/K8V3AZ1P4\nWfnPc/RfmK3InQC92w1xsX2hpZ/qzeL3Y+jxaJ7SnGgm9Q5O7PnDObNW4exzo6936\nkZFCdmQIdVfy4sGASc8ep6NW8ZHuej8vcCdFKJut9QV3S8kDl1XF2sG2DV4qMbC/\nalFRnZUy0TckSgm3fiqfi89u2bbSlfzrTHv2NU9xaYDv7QQpFoZ62PKG9SdJ9R5G\nUwIDAQAB\n-----END PUBLIC KEY-----\n",
101
+
"public_key": "-----BEGIN PUBLIC KEY-----\nMaa...QAB\n-----END PUBLIC KEY-----\n",
99
102
"admin": true,
100
103
"json_class": "Chef::ApiClient",
101
104
"chef_type": "client"
102
-
}
105
+
}
103
106
104
-
Save and close the file. The user is now in admin group.
107
+
Save and close the file. The "deis-controller" user is now in the "admins" group.
105
108
106
-
If you skip this step, you will receive errors when scaling down nodes as the
107
-
controller will not have permissions to delete "client" and "node" records from the Chef Server.
109
+
.. important::
110
+
If you skip adding "deis-controller" to the Chef "admins" group, you will
111
+
receive errors when scaling down nodes, as the controller will not have
112
+
permission to delete "client" and "node" records from the Chef Server.
0 commit comments