Skip to content
This repository has been archived by the owner on May 18, 2021. It is now read-only.

Tutorial Part 7

Jump to bottom
hgschmie edited this page Oct 30, 2014 · 2 revisions

Previous: Installing and starting the coordinator and the agent

Odds and ends

Adding the new coordinator to the airship configuration

Airship can manage multiple environments. The airship coordinator and agent have been installed into the environment called local which is also the default environment.

airship environment show
* local

The newly installed coordinator can be added as the environment into which the actual services will be installed:

airship environment add main http://localhost:28888/

airship environment show
  local
* main

The default environment can be changed with the airship environment use command or switched on a per command basis using -e <environment name>.

The airship agent command shows the agents for the different environments:

airship -e local agent
uuid  host       machine  status  type   location
loca  localhost  local    ONLINE  local  /local/agent

airship -e main agent
uuid  host       machine          status  type     location
1b5c  127.0.0.1  localhost:28889  ONLINE  unknown  /agent/local-agent

Service login

Airship supports the airship ssh command which allows logging into the machine that runs a specific service and setting up a remote shell in the working directory of a service

airship -e local show
uuid  host       machine  status   binary                    config                
22d9  localhost  local    RUNNING  airship-coordinator:0.13  @local-coordinator:1
1b5c  localhost  local    RUNNING  airship-agent:0.13        @local-agent:1

airship -e local ssh -u 22d9
% ls
authorized-keys  etc  expected-state  var

The resulting shell is in the working directory of the local coordinator.

  • etc/... - This is a symbolic link to the etc directory created from the local-coordinator configuration. It contains the configuration files from the local-coordinator configuration bundle.
  • var/log/launcher.log - The log file for the application launcher. For airship 0.13 and below, this also contains the captured output of the service itself.
  • var/log/server.log - Only available after version 0.13 where it contains the captured output of the service itself.
  • var/log/http-request.log - For the coordinator and agent (and other services that use the airlift service framework), this contains the HTTP access log of the integrated HTTP server.

Airship does not provide any mechanisms to rotate or expire log files.

This concludes the tutorial. The next steps to explore are

  • install airship enabled services into the main environment
  • Use a remote repository server
  • Add new agents running on other machines to the main environment
Clone this wiki locally