diff options
| author | Todd Willey <xtoddx@gmail.com> | 2012-01-08 12:51:35 -0500 |
|---|---|---|
| committer | Todd Willey <xtoddx@gmail.com> | 2012-01-08 15:36:56 -0500 |
| commit | e231a055c2a73f82597b0b2a690f2fb28472a99f (patch) | |
| tree | 161c832dde50c4596a8098c1c8e8d3ef1bf1e19a /tools/enable-pre-commit-hook.sh | |
| parent | 410d8e8b3191021513648e98ed11980dfe968ab9 (diff) | |
| download | nova-e231a055c2a73f82597b0b2a690f2fb28472a99f.tar.gz nova-e231a055c2a73f82597b0b2a690f2fb28472a99f.tar.xz nova-e231a055c2a73f82597b0b2a690f2fb28472a99f.zip | |
Isolate certain images on certain hosts.
This implements a [hosts] <=> [images] mapping in the simple scheduler
that partitions your host resources into the part that services a
particular image set, and the general cloud. This is useful, for
example, if you want to specify a set of hosts to run utility VMs
(cloudpipe, bastion, etc) that you don't want consuming resources from
your generally available pool.
When specifying a host with --isolated_hosts flags (comma-separated
list) those hosts will only run the images specified in
--isolated_images, and will not run any other images. The isolated
images will not run on any other hosts.
You can specify --skip_isolated_core_check to allow overcommitting of
the isolated hosts. This allows utility vms that are not cpu bound to
avoid the resource cheks the scheduler usually performs (based off of
--max_cores).
Change-Id: Ib2db5a605cb7560a169af9ff2a6dadb649da9c1d
Diffstat (limited to 'tools/enable-pre-commit-hook.sh')
0 files changed, 0 insertions, 0 deletions
