Skip to content

Support for additional disks, big nodes, update channel and Parallels#2

Open
dab-q wants to merge 1 commit intoupstream-masterfrom
pull-preview
Open

Support for additional disks, big nodes, update channel and Parallels#2
dab-q wants to merge 1 commit intoupstream-masterfrom
pull-preview

Conversation

@dab-q
Copy link

@dab-q dab-q commented Oct 17, 2017

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.
    $node_disks = 3
    $disk_size = 10 # in GB

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.

@dab-q dab-q requested review from jbw976 and thephred October 17, 2017 15:21
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.
@dab-q dab-q force-pushed the pull-preview branch 2 times, most recently from d0edb0b to 23db3df Compare October 17, 2017 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants