I would say this is more of a thing that should go into provisioners, unless you have a solid argument otherwise. I'm interested. Vagrant 0.6 should (if I can pack it all in!) enhance the provisioners functionality a bit more to make this an easy addition.

Hi Mitchell,
I am second to the request. It will help me with Multiple VM and different webservers on it and also with automatic provisioning chef server using vagrant :)

Alex,

You can already name your VM using this syntax to differentiate them in the Vagrant UI:

config.vm.customize do |vm|
  vm.name = "Anything Here"
end

As for setting the hostname, I still believe this can be done by a provisioner. Why can't you use chef to set the hostname?

Mitchell

Mitchell,
Thanks for the tip. Will name of the VM change the name of chef client?
With regards to hostname, do you mean something like this:"Dynamic hosts file using Chef" - http://bit.ly/9gwk5t

Also I am curios on your feedback to my first attempts to use vagrant and chef: "Quick way to bootstrap chef server with vagrant" - http://bit.ly/cymYtX

Regards,
Alex

Alex,

No, the name only affects the name that VirtualBox shows for it, not the hostname.

And yes, I suppose I am talking about something like what you linked but in a much less complicated way. I guess if you're using chef server you must set the hostname prior to running it. I have some ideas for working around this so I'll work on them, though they are still unrelated to this issue exactly.

Mitchell

Alex,

Also, I'll review your article in a bit and comment there =]

Thanks!

Well, come to think about it, perhaps this could be a good way of doing this:

config.chef.node_name = "somehost.example.com" in the Vagrantfile and then
just add a recipe to chef which sets the hostname base on that.

When I found this setting it was easier to do what I wanted. The default nodename was "client" which was kind of troublesome for me since all vagrant boxes got the recipes etc from the node "client" which isn't at all what I wanted. I was used to setting the fqdn on an ec2 node(through some userdata) and then just run chef against my chef server but with vagrant it works differently... but in reality this could actually be a nice way of setting the fqdn on an ec2 node as well.

Not sure when this was added, but this works for me to set the hostname:

 config.vm.host_name = 'foo.bar'

This was added as of 0.7.1. I changed my stance on the issue since the hostname is so crucial to many tools working properly, it made sense to add this.

Not sure when this was added, but this works for me to set the hostname:

 config.vm.host_name = 'foo.bar'

It should be hostname.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.