Skip to content

Latest commit

 

History

History
60 lines (40 loc) · 2.14 KB

STEMCELLS.md

File metadata and controls

60 lines (40 loc) · 2.14 KB
Raw

Stemcell Compatibility

Development is being done against the Openstack stemcell. If, for some reason, another type of stemcell is needed, support can be expanded.

Current Agent configurations support ConfigDrive only, but CDROM could be added relatively easily. HTTP, File, and InstanceMetadata are unlikely to be added.

These are all presumed to be run against some valid Libvirt provider. Thus, there is a chance that the Azure stemcell will work under Libvirt running on KVM. Hypothetically.

Note that, when trying to identify stemcells, every single one ran under Libvirt/QEMU except for Warden which ships as a GZipped TAR file.

Ultimately, Openstack was settled upon (for no particular technical reason).

vSphere was hard to confirm due to the initial stemcell password being something different.

Openstack

Use --ops-file=manifests/openstack-stemcell.yml in the BOSH Directory deployment. (Note that this is the current default.)

stemcell:
  formats: [ "openstack-qcow2", "openstack-raw" ]
  type: ConfigDrive
  label: "config-2"
  metadata_path: "ec2/latest/meta-data.json"
  userdata_path: "ec2/latest/user-data"

Source

Azure

Use --ops-file=manifests/azure-stemcell.yml in the BOSH Directory deployment.

NOTE: The label is too long for current config disk capabilities.

stemcell:
  formats: [ "azure-vhd" ]
  type: ConfigDrive
  label: azure_cfg_dsk
  metadata_path: "configs/MetaData"
  userdata_path: "configs/UserData"

Source

vSphere

Use --ops-file=manifests/vsphere-stemcell.yml in the BOSH Directory deployment.

NOTE: When tested with a vSphere stemcell, the CPI failed unable to attach /dev/sr0.

stemcell:
  formats: [ "vsphere-ova", "vsphere-ovf" ]
  type: CDROM
  filename: env

Source