Deis Control Utility

deisctl is a command-line utility used to provision and operate a Deis cluster.

Installation

To install deisctl on Linux or Mac OS X, run this command:

$ curl -sSL http://deis.io/deisctl/install.sh | sudo sh

The installer puts deisctl in /usr/local/bin and downloads current Deis unit files to /var/lib/deis/units one time.

To change installation options, save the installer directly from one of these links:

Then run the downloaded file as a shell script. Append --help to see what options are available.

If you want to install from source, clone the repository and run

$ godep get .

Then, export the DEISCTL_UNITS environment variable so deisctl can find the units:

$ export DEISCTL_UNITS="$PATH_TO_DEISCTL/units"

Remote Configuration

While deisctl can be used locally on a CoreOS host, it is extremely useful as a tool for remote administration. This requires an SSH tunnel to one of your CoreOS hosts.

Test password-less SSH connectivity to a CoreOS host:

$ ssh [email protected] hostname
deis-1

Export the DEISCTL_TUNNEL environment variable:

$ export DEISCTL_TUNNEL=172.17.8.100

Provision a Deis Platform

The deisctl install platform command will schedule all of the Deis platform units. deisctl start platform activates these units.

$ deisctl install platform
● ▴ ■
■ ● ▴ Installing Deis...
▴ ■ ●

Scheduling data containers...
deis-database-data.service: loaded
deis-registry-data.service: loaded
deis-logger-data.service: loaded
Data containers scheduled.
Scheduling service containers...
[email protected]: loaded
[email protected]: loaded
[email protected]: loaded
[email protected]: loaded
[email protected]: loaded
[email protected]: loaded
[email protected]: loaded
Service containers scheduled.
Deis installed.
Please run `deisctl start platform` to boot up Deis.

$ deisctl start platform
● ▴ ■
■ ● ▴ Starting Deis...
▴ ■ ●

Launching data containers...
deis-database-data.service: exited
deis-registry-data.service: exited
deis-logger-data.service: exited
Data containers launched.
Launching service containers...
[email protected]: running
[email protected]: running
[email protected]: running
[email protected]: running
[email protected]: running
[email protected]: running
[email protected]: running
Deis started.

Note that the default start command activates 1 of each component. You can scale components with deisctl scale router=3, for example. The router is the only component that currently scales beyond 1 unit.

You can also use the deisctl uninstall command to destroy platform units:

$ deisctl uninstall platform

Destroying service containers...
[email protected]: inactive
[email protected]: inactive
[email protected]: inactive
[email protected]: inactive
[email protected]: inactive
[email protected]: inactive
[email protected]: inactive
Done.

To uninstall a specific component, use deisctl uninstall router.

Note that uninstalling platform units will not remove the data units or underlying data containers. Data must be destroyed manually.

Usage

The deisctl tool provides a number of other commands, including:

• deisctl list - list Deis platform components
• deisctl status <component> - retrieve Systemd status of a component
• deisctl journal <component> - retrieve Systemd journal output
• deisctl start <component> - start a platform component
• deisctl stop <component> - stop a platform component
• deisctl install <component> - install a single platform component
• deisctl uninstall <component> - uninstall a single platform component
• deisctl scale <component>=<num> - scale a component to the target number of units
• deisctl refresh-units - download latest unit files

Usage Examples

$ deisctl list
UNIT				MACHINE				LOAD	ACTIVE	SUB
[email protected]		f936b7a5.../172.17.8.100	loaded	active	running
[email protected]		f936b7a5.../172.17.8.100	loaded	active	running
[email protected]	f936b7a5.../172.17.8.100	loaded	active	running
deis-database-data.service	f936b7a5.../172.17.8.100	loaded	active	exited
[email protected]		f936b7a5.../172.17.8.100	loaded	active	running
deis-logger-data.service	f936b7a5.../172.17.8.100	loaded	active	exited
[email protected]		f936b7a5.../172.17.8.100	loaded	active	running
deis-registry-data.service	f936b7a5.../172.17.8.100	loaded	active	exited
[email protected]		f936b7a5.../172.17.8.100	loaded	active	running
[email protected]		f936b7a5.../172.17.8.100	loaded	active	running

$ deisctl status controller
● [email protected] - deis-controller
   Loaded: loaded (/run/fleet/units/[email protected]; linked-runtime)
   Active: active (running) since Mon 2014-08-25 22:56:50 UTC; 15min ago
  Process: 22969 ExecStartPre=/bin/sh -c docker inspect deis-controller >/dev/null && docker rm -f deis-controller || true (code=exited, status=0/SUCCESS)
  Process: 22945 ExecStartPre=/bin/sh -c IMAGE=`/run/deis/bin/get_image /deis/controller`; docker history $IMAGE >/dev/null || docker pull $IMAGE (code=exited, status=0/SUCCESS)
 Main PID: 22979 (sh)
   CGroup: /system.slice/system-deis\x2dcontroller.slice/[email protected]
           ├─22979 /bin/sh -c IMAGE=`/run/deis/bin/get_image /deis/controller` && docker run --name deis-controller --rm -p 8000:8000 -e PUBLISH=8000 -e HOST=$COREOS_PRIVATE_IPV4 --volumes-from=deis-logger $IMAGE
           └─22999 docker run --name deis-controller --rm -p 8000:8000 -e PUBLISH=8000 -e HOST=172.17.8.100 --volumes-from=deis-logger deis/controller:latest

Aug 25 22:57:07 deis-1 sh[22979]: [2014-08-25 16:57:07,959: INFO/MainProcess] Connected to redis://172.17.8.100:6379/0
Aug 25 22:57:07 deis-1 sh[22979]: 2014-08-25 16:57:07 [121] [INFO] Booting worker with pid: 121
Aug 25 22:57:07 deis-1 sh[22979]: [2014-08-25 16:57:07,968: INFO/MainProcess] mingle: searching for neighbors
Aug 25 22:57:08 deis-1 sh[22979]: 2014-08-25 16:57:08 [122] [INFO] Booting worker with pid: 122
Aug 25 22:57:08 deis-1 sh[22979]: 2014-08-25 16:57:08 [123] [INFO] Booting worker with pid: 123
Aug 25 22:57:08 deis-1 sh[22979]: 2014-08-25 16:57:08 [124] [INFO] Booting worker with pid: 124
Aug 25 22:57:08 deis-1 sh[22979]: 2014-08-25 16:57:08 [125] [INFO] Booting worker with pid: 125
Aug 25 22:57:08 deis-1 sh[22979]: 2014-08-25 16:57:08 [126] [INFO] Booting worker with pid: 126
Aug 25 22:57:08 deis-1 sh[22979]: [2014-08-25 16:57:08,979: INFO/MainProcess] mingle: all alone
Aug 25 22:57:08 deis-1 sh[22979]: [2014-08-25 16:57:08,997: WARNING/MainProcess] celery@4378062f17a5 ready.

$ deisctl journal controller
...
Aug 25 22:57:08 deis-1 sh[22979]: 2014-08-25 16:57:08 [125] [INFO] Booting worker with pid: 125
Aug 25 22:57:08 deis-1 sh[22979]: 2014-08-25 16:57:08 [126] [INFO] Booting worker with pid: 126
Aug 25 22:57:08 deis-1 sh[22979]: [2014-08-25 16:57:08,979: INFO/MainProcess] mingle: all alone
Aug 25 22:57:08 deis-1 sh[22979]: [2014-08-25 16:57:08,997: WARNING/MainProcess] celery@4378062f17a5 ready.

$ deisctl stop controller
[email protected]: loaded

$ deisctl start controller
[email protected]: launched

$ deisctl scale router=3
[email protected]: loaded
[email protected]: loaded
[email protected]: loaded

$ deisctl start router
[email protected]: launched
[email protected]: launched
[email protected]: launched

License

Copyright 2014, OpDemand LLC

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.