Project

General

Profile

Bug #8601

use cloudinit like user data in vsphere compute ressource

Added by Karim Boumedhel almost 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources - VMware
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

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


Related issues

Related to Foreman - Bug #10305: cloudinit like user data in vsphere compute ressource: missing partClosed2015-04-29

Associated revisions

Revision 5b1f7529 (diff)
Added by Karim Boumedhel over 6 years ago

Fixes #8601 - Cloudinit userdata in VMware

Revision c81ea296 (diff)
Added by Karim Boumedhel over 6 years ago

Fixes #8601 - Cloudinit userdata in VMware

(cherry picked from commit 5b1f7529284e9e62d9f8f08977b543d4a7b93f21)

History

#1 Updated by Dominic Cleal over 6 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 ()

#2 Updated by Karim Boumedhel over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Dominic Cleal over 6 years ago

  • Legacy Backlogs Release (now unused) set to 28

#4 Updated by Dominic Cleal over 6 years ago

  • Related to Bug #10305: cloudinit like user data in vsphere compute ressource: missing part added

#5 Updated by Lukas Zapletal almost 4 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.

https://github.com/fog/fog-vsphere/blob/master/lib/fog/vsphere/requests/compute/cloudinit_to_customspec.rb

https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.wssdk.apiref.doc/vim.vm.customization.Specification.html

Also available in: Atom PDF