salt-cloud & setting hostname after salt is installed

[schlag ify]

Hi,

I am new to salt-cloud, and finally have it successfully provisioning Linux vm's, however the resulting vm's still have the template's hostname.   Is there a recommended way of having salt-cloud set the hostname for a newly provisioned vm?  

thanks

[schlag ify]

The resulting debug output of salt-cloud suggests that the newly provisioned vm should have its `id` grain updated with the new hostname, but then when I ssh into the vm the hostname is not available via grains (using 'salt-call grains.get id', nor does it show up in 'salt-call grains.items'), or anywhere on the system.   The vm retains the original hostname of the template, and no salt states can update the hostname if it's unavailable.

I have vmware tools installed, and have verified that it is running.   Any ideas??

[Robert Booth]

How I understand things working with salt-cloud is that the name you specify when executing salt-cloud will be used for the salt id on the new node. This will not update the local hostname.

(Following hasn't been tested yet. I'll try to test it today)

I would suggest creating a state file to update the hostname of the node to the minion id.

Put in your salt-cloud profile to run this state after it installs.

example.

Cloud profile file

ubuntubox:

  ...

  minion:

    startup_states: sls

    sls_list:

      - updatehostname

updatehostname.sls

"Update my name {{ grains['id'] }}":

  network.system:

    - name: {{ grains['id'] }}

    - enabled: True

    - hostname: {{ grains['id'] }}

    - apply_hostname: True

Hope this is what you were looking for.

[schlag ify]

thank you for your suggestions.   it turned out that i had an /etc/salt/minion file in place on my template from an older saltstack installation and the bootstrap script wasn't overwriting it.   your tips about startup_states and updatehostname.sls helped me get alot further.   much appreciated!