chrisroberts / vagabond

Advocating idleness and work-shyness
Other
233 stars 25 forks source link

FATAL: Node name is required when running vagabond up #15

Closed jaypipes closed 11 years ago

jaypipes commented 11 years ago

Hi again,

When I run bundle exec vagabond up, I'm getting this:

jpipes@uberbox:~/repos/att-cloud/chef-repo$ bundle exec vagabond up
WARNING: Local chef server is not currently running!
FATAL: Node name is required!

The Vagabondfile I'm using is here:

{
  :nodes => {
    :controller => {
      :template => "ubuntu_1204",
      :run_list => []
    },
    :compute_worker => {
      :template => "ubuntu_1204",
      :run_list => []
    },
    :ops => {
      :template => "ubuntu_1204",
      :run_list => []
    }
  },
  :clusters => {

  },
  :local_chef_server => {
    :zero => false,
    :berkshelf => true,
    :librarian => false,
    :enabled => true,
    :auto_upload => true
  },
  :sudo => true
}

I tried adding :node_name => "chef" to the :local_chef_server section, but got same error... any suggestions?

Thanks in advance! -jay

chrisroberts commented 11 years ago

The up command expects the name of the thing you want to start. So you would use one of the keys within the :nodes hash. Something like:

$ bundle exec vagabond up controller

If you want to kick on a bunch of them all at once in a single command, you can use the cluster. In the clusters hash, you can fill it out:

:clusters => {
  :my_cluster => ['controller', 'compute_worker', 'ops']
}

and then you can start all of them:

$ bundle exec vagabond cluster my_cluster
jaypipes commented 11 years ago

Doh, got it. Thanks!