Merge pull request #110 from bensojona/b-documentation-fixes
Documentation fixes
This commit is contained in:
commit
6b04a6b250
|
@ -22,7 +22,7 @@ to learn about them without having to go spelunking through the source code.
|
||||||
|
|
||||||
## Gossip in Nomad
|
## Gossip in Nomad
|
||||||
|
|
||||||
Named makes use of a single global WAN gossip pool that all servers participate in.
|
Nomad makes use of a single global WAN gossip pool that all servers participate in.
|
||||||
Membership information provided by the gossip pool allows servers to perform cross region
|
Membership information provided by the gossip pool allows servers to perform cross region
|
||||||
requests. The integrated failure detection allows Nomad to gracefully handle an entire region
|
requests. The integrated failure detection allows Nomad to gracefully handle an entire region
|
||||||
losing connectivity, or just a single server in a remote region. The gossip protocol
|
losing connectivity, or just a single server in a remote region. The gossip protocol
|
||||||
|
|
|
@ -25,8 +25,8 @@ common drivers.
|
||||||
Kubernetes is designed as a collection of more than a half-dozen interoperating
|
Kubernetes is designed as a collection of more than a half-dozen interoperating
|
||||||
services which together provide the full functionality. Coordination and
|
services which together provide the full functionality. Coordination and
|
||||||
storage is provided by etcd at the core. The state is wrapped by API controllers
|
storage is provided by etcd at the core. The state is wrapped by API controllers
|
||||||
which are consumed by other services that provide higher level APIs or features
|
which are consumed by other services that provide higher level APIs for features
|
||||||
like scheduling. Kubernetes supports running in a high available
|
like scheduling. Kubernetes supports running in a highly available
|
||||||
configuration but is operationally complex to setup.
|
configuration but is operationally complex to setup.
|
||||||
|
|
||||||
Nomad is architecturally much simpler. Nomad is a single binary, both for clients
|
Nomad is architecturally much simpler. Nomad is a single binary, both for clients
|
||||||
|
|
|
@ -16,8 +16,8 @@ depends on ZooKeeper to provide both coordination and storage.
|
||||||
There are many different frameworks that integrate with Mesos,
|
There are many different frameworks that integrate with Mesos,
|
||||||
popular general purpose ones include Aurora and Marathon.
|
popular general purpose ones include Aurora and Marathon.
|
||||||
These frameworks allow users to submit jobs and implement scheduling
|
These frameworks allow users to submit jobs and implement scheduling
|
||||||
logic. These frameworks depend on Mesos for resource management,
|
logic. They depend on Mesos for resource management, and external
|
||||||
and external systems like ZooKeeper to provide coordination and storage.
|
systems like ZooKeeper to provide coordination and storage.
|
||||||
|
|
||||||
Nomad is architecturally much simpler. Nomad is a single binary, both for clients
|
Nomad is architecturally much simpler. Nomad is a single binary, both for clients
|
||||||
and servers, and requires no external services for coordination or storage.
|
and servers, and requires no external services for coordination or storage.
|
||||||
|
|
Loading…
Reference in New Issue