I have a requirement to setup VM boxes across multiple host machines and this has to be initiated from a single master host. To elaborate bit more, I will have VM templates with different configurations (created as say a VgrantFile) and the master host should initiate connection to the child host and bring up the VM based on a specific template.
Can I use Vagrant for this ? Appreciate if you can suggest alternatives.
Regards
Best I found according to your description:
https://github.com/fjsanpedro/vagrant-nodemaster
https://github.com/fjsanpedro/vagrant-node
Related
I am trying to make my vagrant box accessible over internet for quick customer review. I tried to get it working over noip but somehow it did not work and I don't even know why. My networking knowledge is quite beginner level and now even more confused.
Do I have to use vagrants bridged network option to do that ?
How would you do that. Should be pretty common to allow access for that purpose
vagrant share is the feature you're looking
Vagrant Share allows you to share your Vagrant environment with anyone
in the world, enabling collaboration directly in your Vagrant
environment in almost any network environment with just a single
command: vagrant share.
Just make sure you dont tie your webserver to localhost or the hostname as vagrant will give you a temporary url to access the instance
I have 2 VM running, one is giving me a local server on an address like www.x.com (FREE BSD 64bit), which I can access from my browsers locally.
My question is, if I use another VM to test with windows and IE, how can I access my www.x.com given from my other running VM with the second VM? That means, from IE?
Is that possible?
Thanks a lot, this would help me a lot, I have to deploy to our testing servers everytime I want to test something on IE and is quite annoying!
Possible, of course. To connect to your VM both from host system and another VM you can set bridget networking for both VMs (BTW, maybe you already using network bridge). There are also other possibilities, but bridget network is easiest way, IMHO.
I am running Windows 7 on my desktop at work and I am signed in to a regular user account on the VPN. To develop software, we are to normally open a Dev VM and work from in there however recently I've been assigned a task to research Docker and Mongo DB. I have very limited access to what I can install on the main machine.
Here lies my problem:
Is it possible for me to connect to a MongoDB instance inside a container inside the docker machine from Windows and make changes? I would ideally like to use a GUI tool such as Mongo Management Studio to make changes to a Mongo database within a container.
By inspecting the Mongo container, it has the ports listed as: 0.0.0.0:32768 -> 27017/tcp
and docker-machine ip (vm name) returns 192.168.99.111.
I have commented out the 127.0.0.1 binding host ip within the mongod.conf file also.
From what I have researched so far, most users resolve their problem by connecting to their docker-machine IP with the port they've set with -p or been given with -P. Unfortunately for me, trying to connect with 192.168.99.111:32768 does not work.
I am pretty stumped and quite new to this environment. I am able to get inside the container with bash and manipulate the database there however I'm wondering if I can do this within Windows.
Thank you if anyone can help.
After reading Smutje's advice to ping the VM IP and testing it out to no avail, I attempted to find a pingable IP which would hopefully move me closer to my goal.
By doing "ifconfig" within the Boot2Docker VM (but not inside the container), I was able to locate another IP listed under eth0. This IP looks something like 134.36.xxx.xxx to me and is pingable. With the Mongo container running I can now access the database from within Mongo Management Studio by connecting to 134.36.xxx.xxx:32768 and manipulate the data from there.
If you have the option of choosing the operating system for your dev VM, go with Ubuntu and setup docker with all of the the containers you want to test on that. Either way, you will need to have a VM for testing docker on windows since it uses VirtualBox if i'm not mistaken. Instead, setup an Ubuntu VM and do all of your testing on that.
I've done some read-up on Vagrant with Chef-Server v/s Vagrant with Chef-solo and have found blogs talking about the usage of the same. I've failed to find anybody summarizing the advantages of either approach. So, here's my question.
I understand that Vagrant cannot spin up virtual machines on a remote machine. This means running "vagrant up" on a particular machine will spin up VMs on that machine alone.
First of all, is this understanding right?
If yes, what’s the point of using a chef server to provision the server?
I feel that if I’m using Vagrant, using chef solo is the way to go and chef
server isn’t adding any value.
Do you think I’m missing something?
Vagrant is used for spin up VMs and you can provision those VMs with the help of chef recipes or via any other provisioning method. https://docs.vagrantup.com/v2/provisioning/index.html
Now, Difference between Chef Server and Chef-Solo:
Chef Server works in Client Server Architecture. You can control or manage all your nodes (VMs launched by Vagrant) with the help of Chef Server. In a particular VM, you can search for other nodes with the help of Chef Server.
Chef-Solo works in Solo mode means, you can provision only single node and you can not get any information about the other nodes. However several techniques exists to overcome such situations like chef-solo-search.
Initially, i set up 2 machines (Ubuntu 12.04, x64) on vSphere server.
The name and ip of these two machines were
host ip
vm-cluster-node1 10.211.55.100
vm-cluster-node2 10.211.55.101
I have installed cloudera manager in vm-cluster-node1.
Then i cloned second one (vm-cluster-node2) to create 2 more hosts, and changed the ip and names as:
host ip
vm-cluster-node3 10.211.55.102
vm-cluster-node4 10.211.55.103
But the problem is, when i add these all 4 machines from cloudera, no matter how many times i try, i can only see two machines in hosts tab. later i realized that, if i refresh the web-page, i can see 2 machines only, but the second machine is switched between vm-cluster-node2, vm-cluster-node3 and vm-cluster-node4.
to illustrate, i have included images to make things clear.
So, as far i've understood, the cloudera manager is not able to resolve the hosts cloned from same source as different machines. Even though the host-names and IPs have been changed. So is there anything that is common in these machines and this problem is occurring?
SOLVED
The problem was that the three nodes/hosts have same HOST ID. This can be changed in /etc/hosts/cloudera-scm-agent file with CMF_AGENT_ARGS="--host_id new_host_id"