This repository has been archived by the owner on Sep 18, 2020. It is now read-only.
Add support for additional disks, big nodes, update channel and Parallels #309
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes it can be desirable to configure additional disks,
more memory and more CPUs to the nodes. In a constrained
environment with a multi-node cluster, there might not be enough
resources to assign larger memory/cpu resources to all the nodes.
These changes support two node configurations, as well as
configuring all nodes with additional virtual disks.
Create big nodes
In addition to the normal nodes, you can
also add additional nodes with a larger
memory/cpu configuration.
$num_big_instances = 1
$vm_big_memory = 8192
$vm_big_cpus = 2
Additional disks
$num_data_disks = 3
$data_disk_size = 10 # GBytes
Specify the coreos update channel:
$update_channel = "alpha"
Add .virtualbox/ to .gitignore
Add Parallels support
Set the memory size and number of cpus for Parallels,
as well as setting the download path.
Change Vagrant file config.vm.provider order
so that VirtualBox is first, which makes it
the default provider (assuming it works), and
the util.rb reflects that assumption. In general,
setting VAGRANT_DEFAULT_PROVIDER is the best way
to be deterministic about what provider is used.