Skip to content

provision-controller.rst

Latest commit

 

History

History
121 lines (92 loc) · 4.27 KB

provision-controller.rst

File metadata and controls

121 lines (92 loc) · 4.27 KB
title:Provision a Deis PaaS Controller
description:Guide to provisioning a Deis controller, the brains of a Deis private PaaS.
keywords:tutorial, guide, walkthrough, howto, deis, sysadmins, operations

Provision a Controller

The controller is the brains of a Deis platform. There are two ways to provision a controller: automatically or manually.

Automatic Provisioning

The community maintains shell scripts that automate the provisioning of Deis controllers on different cloud providers. In addition to launching the controller itself, these scripts also use optimized base images, generate SSH keys, firewall configs and other cloud infrastructure per Deis best practices.

You can find instructions on automatic provisioning for:

Please note that even with automatic provisioning, you will still have to add the controller to the admins group.

Manual Provisioning

If you want your controller on bare metal, a different cloud provider, or would just rather provision things manually --no problem! Just remember with manual provisioning, you are in charge of:

  • Ensuring system requirements are met
  • SSH key generation and distribution
  • Network configuration

Important

System Requirements Most controllers require at least 2GB of system memory and 100GB of storage

The general process for manual provisioning involves:

  1. Boot a target host that meets system requirements
  2. Make sure the target host is accessible over SSH from your workstation
  3. Use knife bootstrap to provision the controller on the target host

Here is an example knife bootstrap command:

$ knife bootstrap 198.51.100.22 \
>  --bootstrap-version 11.6.2 \
>  --ssh-user ubuntu \
>  --sudo \
>  --identity-file ~/.ssh/id_rsa \
>  --node-name deis-controller \
>  --run-list "recipe[deis::controller]"
Bootstrapping Chef on 198.51.100.22
198.51.100.22 --2013-11-20 15:03:46--  https://www.opscode.com/chef/install.sh
198.51.100.22 HTTP request sent, awaiting response... 200 OK
198.51.100.22 Length: 6790 (6.6K) [application/x-sh]
198.51.100.22 Saving to: `STDOUT'
198.51.100.22
...
198.51.100.22 Chef Client finished, 74 resources updated
198.51.100.22

Please note the knife bootstrap command can take several minutes to complete.

Add Controller to Admins Group

Whether you used automatic or manual provisioning, you must add "deis-controller" to the "admins" group on the Chef Server.

Hosted Chef

For Hosted Chef, visit the OpsCode management interface to add "deis-controller" to the "admins" group. These steps describe specifically how to add users to groups in the management interface.

Open Source Chef

For Open Source Chef, use the knife cli tool. First, set the EDITOR environment variable to your favourite text editor:

$ export EDITOR=vim

Now issue the command to edit the "deis-controller" user.

$ knife client edit deis-controller

and update the 'admin' key to 'true'. The updated content should look similar to this.

{
  "name": "deis-controller",
  "public_key": "-----BEGIN PUBLIC KEY-----\nMaa...QAB\n-----END PUBLIC KEY-----\n",
  "admin": true,
  "json_class": "Chef::ApiClient",
  "chef_type": "client"
}

Save and close the file. The "deis-controller" user is now in the "admins" group.

Important

If you skip adding "deis-controller" to the Chef "admins" group, you will receive errors when scaling down nodes, as the controller will not have permission to delete "client" and "node" records from the Chef Server.