ExternalVendorCode/onefuzz
1
0
Fork 0
mirror of https://github.com/microsoft/onefuzz.git synced 2025-06-12 01:58:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

add definitions for pool, node, and scaleset (#17)

Browse Source 
* add defs for pool, node, and scaleset
This commit is contained in:
bmc-msft
2020-09-22 10:40:59 -04:00
committed by GitHub
parent 7d27b6a008
commit a28538a151
1 changed files with 30 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/terminology.md
View File

@ -59,4 +59,33 @@ An
Each fuzzing task has a set of required and potentially optional containers that
are used in a specific context.
[More info on Containers](containers.md)
[More info on Containers](containers.md)
## Pool
A pool is a group of nodes to run [Tasks](#task). Pools enable users to
specify which group of [nodes](#node) their task should run on.
Pools are defined by:
* `name`: the Name of the pool
* `os`: The operating system of the node (`linux` or `windows`)
3. `arch`: The CPU architecture of the nodes (only `x86_64` for now)
4. `managed`: Is the pool made up of OneFuzz managed [scalsets](#scaleset)
## Scaleset
A scaleset is an [Azure Virtual Machine
Scaleset](https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview),
of which the entire lifecycle is managed by OneFuzz. All of the VMs in the
scaleset are automatically setup to connect to the OneFuzz instance as a
[Node](#node).
Scalesets can run on almost any [Azure VM
Image](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/cli-ps-findimage)
(use the URN for the image) or [user-provided OS images](custom-images.md).
## Node
A single compute host to run tasks. Right now, these are only VMs in a
[scaleset](#scaleset), though support for on-prem or third-party cloud-hosted
nodes will be available in the future.