Bug #8601
closed
use cloudinit like user data in vsphere compute ressource
Description
as a vsphere user, i would like to use the customisationspec feature of vsphere from foreman
that means applying a user_data template and have it applied when deploying a vmware vm from template
changes need to be done at the following level
-rbvmomi to pass additional options
-foreman to handle user_data and pass it to setComputePowerUp in app/models/concerns/orchestration/compute.rb
note rbvmomi will need some slight modifications as the current code doesnt make use of all the customspec options. Still, no modifications is currently required there nor at fog
Updated by Dominic Cleal almost 10 years ago
- Status changed from New to Ready For Testing
- Assignee set to Karim Boumedhel
- Pull request https://github.com/theforeman/foreman/pull/2000 added
- Pull request deleted (
)
Updated by Karim Boumedhel over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 5b1f7529284e9e62d9f8f08977b543d4a7b93f21.
Updated by Dominic Cleal over 9 years ago
- Translation missing: en.field_release set to 28
Updated by Dominic Cleal over 9 years ago
- Related to Bug #10305: cloudinit like user data in vsphere compute ressource: missing part added
Updated by Lukas Zapletal almost 7 years ago
For googlers:
VMWare has actually special cloud-init limited scope support, it
does not pass the cloud-init into the image as-is, but rather converts
it into individual actions referred as Custom Spec in VMWare docs.
Only some fields are converted, the rest is unused. It does not accept
"call home" wget/curl call therefore VMWare VMs initialized with
cloud-init stays in build mode forever. This is known limitation.