Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get vagrant $vm_mem value from environment #3792

Merged
merged 1 commit into from
Mar 5, 2015

Conversation

ryfow
Copy link
Contributor

@ryfow ryfow commented Feb 9, 2015

I'd like to put something in my environment similar to NUM_MINIONS to control the amount of memory Vagrant VMs get. I'm happy to submit a pull request, but would like feedback on the environment variable names to expedite things.

Some options would be: KUBERNETES_MEMORY, KUBERNETES_RAM, KUBE_MEMORY, KUBE_RAM.

Or, Master and Minion could be split up, lending variable names such as KUBERNETES_MASTER_MEMORY, KUBERNETES_MINION_MEMORY. If we're doing that, it's probably safe to drop the KUBERNETES_ on the thought MASTER_MEMORY is specific enough to Kubernetes.

@derekwaynecarr
Copy link
Member

I am good with this, and I see no reason to separate master and minion settings at this time.

Sent from my iPhone

On Jan 25, 2015, at 1:26 PM, Ryan Fowler notifications@github.com wrote:

I'd like to put something in my environment similar to NUM_MINIONS to control the amount of memory Vagrant VMs get. I'm happy to submit a pull request, but would like feedback on the environment variable names to expedite things.

Some options would be: KUBERNETES_MEMORY, KUBERNETES_RAM, KUBE_MEMORY, KUBE_RAM.

Or, Master and Minion could be split up, lending variable names such as KUBERNETES_MASTER_MEMORY, KUBERNETES_MINION_MEMORY. If we're doing that, it's probably safe to drop the KUBERNETES_ on the thought MASTER_MEMORY is specific enough to Kubernetes.


Reply to this email directly or view it on GitHub.

@JaysonRaymond
Copy link
Contributor

I added this locally to my Vagrantfile as:

Give VM 512MB of RAM by default

$vm_mem = (ENV['VM_MEM'] || 512).to_i

@goltermann goltermann added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jan 28, 2015
@erictune
Copy link
Member

erictune commented Mar 4, 2015

@derekwaynecarr you can commit this now!

@erictune
Copy link
Member

erictune commented Mar 4, 2015

but @ryfow would need to rebase first.

@ryfow ryfow force-pushed the vagrant-kubernetes-memory branch from 0739508 to 0d6ca95 Compare March 4, 2015 20:43
Has Vagrant try to read `KUBERNETES_MEMORY` environment varilable when setting
$vm_mem.

fixes kubernetes#3792
@ryfow ryfow force-pushed the vagrant-kubernetes-memory branch from 0d6ca95 to 749ae3d Compare March 4, 2015 20:45
@ryfow
Copy link
Contributor Author

ryfow commented Mar 4, 2015

I rebased and changed default to 1024.

On Wed, Mar 4, 2015 at 2:23 PM, Eric Tune notifications@github.com wrote:

but @ryfow https://github.com/ryfow would need to rebase first.


Reply to this email directly or view it on GitHub
#3792 (comment)
.

@derekwaynecarr
Copy link
Member

LGTM

derekwaynecarr added a commit that referenced this pull request Mar 5, 2015
Get vagrant $vm_mem value from environment
@derekwaynecarr derekwaynecarr merged commit c91d8e1 into kubernetes:master Mar 5, 2015
akram referenced this pull request in akram/kubernetes Apr 7, 2015
Has Vagrant try to read `KUBERNETES_MEMORY` environment varilable when setting
$vm_mem.

fixes #3792
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants