luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Merge pull request #110 from bensojona/b-documentation-fixes 

Documentation fixes
This commit is contained in:
Chris Bednarski 2015-09-24 17:50:23 -07:00
parent fce6a5f7c7 95a3258672
commit 6b04a6b250
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/internals/architecture.html.md
View File

@ -37,7 +37,7 @@ clarify what is being discussed:
Example Drivers include Docker, Qemu, Java, and static binaries.
* **Task** - A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
which allow Nomad to be flexible in the types of tasks it supports. Tasks
which allow Nomad to be flexible in the types of tasks it supports. Tasks
specify their driver, configuration for the driver, constraints, and resources required.
* **Client** - A Client of Nomad is a machine that tasks can be run on. All clients run the

2
website/source/docs/internals/gossip.html.md
View File

@ -22,7 +22,7 @@ to learn about them without having to go spelunking through the source code.
## 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
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

4
website/source/intro/vs/kubernetes.html.md
View File

@ -25,8 +25,8 @@ common drivers.
Kubernetes is designed as a collection of more than a half-dozen interoperating
services which together provide the full functionality. Coordination and
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
like scheduling. Kubernetes supports running in a high available
which are consumed by other services that provide higher level APIs for features
like scheduling. Kubernetes supports running in a highly available
configuration but is operationally complex to setup.
Nomad is architecturally much simpler. Nomad is a single binary, both for clients

4
website/source/intro/vs/mesos.html.md
View File

@ -16,8 +16,8 @@ depends on ZooKeeper to provide both coordination and storage.
There are many different frameworks that integrate with Mesos,
popular general purpose ones include Aurora and Marathon.
These frameworks allow users to submit jobs and implement scheduling
logic. These frameworks depend on Mesos for resource management,
and external systems like ZooKeeper to provide coordination and storage.
logic. They depend on Mesos for resource management, and external
systems like ZooKeeper to provide coordination and storage.
Nomad is architecturally much simpler. Nomad is a single binary, both for clients
and servers, and requires no external services for coordination or storage.