This repository was 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
Open
dab-q wants to merge 5 commits into
Open
Add support for additional disks, big nodes, update channel and Parallels#309dab-q wants to merge 5 commits into
dab-q wants to merge 5 commits into
Conversation
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
- Each node can be configured with additional disks.
$num_data_disks = 3
$data_disk_size = 10 # GBytes
Specify the coreos update channel:
$update_channel = "alpha"
Also 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.
Author
|
We are using coreos-vagrant for a developer environment for a https://github.com/rook/rook installation, and we need additional disks on each VM for Rook/Ceph to consume. We are also running some additional software that has larger memory and CPU requirements, but we only need one node in the cluster to be able to support it, so having several 1CPU/2GB nodes and one 2CPU/6GB nodes works well in a constrained resource environment like a MacBook Pro laptop. |
added 4 commits
December 5, 2017 10:56
We've seen some instances of the kernel rebooting due to a kenel paging request in the network RX code, coming from the virtio_net module. Switch the second nic, which is the private network, to be an emulation of an Intel NIC, avoiding the virtio_net code. Only the second NIC is changed, the first NIC is left as a virtio_net NIC. That NIC is only used for host<->VM communications, and changing it to an Intel NIC messes up the NIC configuration, and leaving it as a virtio_net driver keeps things working. (The NIC order was getting changed, causing CoreOS to configure the wrong interface for the private network.)
Change VirtualBox NIC
This reverts commit 6181371. This change has been causing problems and unintended consequences, such as affecting coreos NIC configuration when running with parallels, even though this should have only changed things with Virtualbox. And while it seems to have fixed the stability issues when running with linux/virtualbox, it is not working the same with mac/virtualbox.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.