Marathon app. A unit of configuration in Marathon. During normal operation, one service “instance” maps to one Marathon app, but during deploys there may be more than one app. Apps contain Tasks.
A shortname used to describe a PaaSTA cluster. Use `paasta list-clusters` to see them all.
Logical collection of Mesos tasks that comprise a Marathon app. service name + instancename = Marathon app name. Examples: main, canary.
An haproxy/SmartStack concept grouping backends that listen on a particular port. A namespace may route to many healthy Marathon instances. By default, the namespace in which a Marathon job appears is its instancename.
A machine running a Mesos Master process, responsible for coordination but not responsible for actually running Marathon or Tron jobs. There are several Masters, coordinating as a quorum via Zookeeper.
A machine running a Mesos Slave process, responsible for running Marathon or Tron jobs as assigned by the Mesos Master.
A python library for interacting with soa-configs.
The brand name for Airbnb’s Nerve + Synapse service discovery solution.
A local haproxy daemon that runs on yocalhost
Marathon task. A process (usually inside a Docker container) running on a machine (a Mesos Slave). One or more Tasks constitutes an App.
A git repo for centralized service configs.
An ip that both on-metal and containers can use to connect to other services.
A distributed key/value store used by Mesos for coordination and persistence.