Creating new VM nodes, is this vagrant or puppet? -


i have 8-cpu server , installed centos 7 on it. dynamically , programmatically spin , down vm nodes work, ex. hadoop nodes.

is technology use vagrant or puppet, or else? have played around vagrant, appears every new node requires new directory in file system, can't spin new vm far can tell api call, think. , doesn't there's real api vagrant, machine-readable output. , if understand properly, puppet deals configuration management pre-existing nodes.

is either of these correct technology use or there else more fitting want do?

yes, can use vagrant spin new vm. configuration of particular vm can done using puppet. take at: https://www.vagrantup.com/docs/provisioning/puppet_apply.html

and if you're problem having separate directories each vm, you're looking multimachine setup: https://www.vagrantup.com/docs/multi-machine/

for example using multiserver setup take @ https://github.com/mlambrichs/graphite-vagrant/blob/master/vagrantfile in config directory you'll find yaml file defines array can use loop on different vm's.


Comments

Popular posts from this blog

javascript - jQuery: Add class depending on URL in the best way -

caching - How to check if a url path exists in the service worker cache -

Redirect to a HTTPS version using .htaccess -