Enhancement: vmware OEM image #359

Closed
olliewalsh opened this Issue May 13, 2015 · 12 comments

Comments

Projects
None yet
8 participants
@olliewalsh

A vmware OEM image that includes the vmware tools OEM partition would be useful. A vmdk is not necessarily the ideal format for all deployments.

As a workaround I'm using a bare-metal coreos-install from the ISO then afterwards mount /dev/sda6 and drop in the contents of the OEM partition that I've extracted from the vmdk image.

@marineam

This comment has been minimized.

Show comment
Hide comment
@marineam

marineam May 13, 2015

We also have an ova: http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vmware_ova.ova

Between vmdk and ova that pretty much covers vmware I think. What sort of image are you looking for?

We also have an ova: http://alpha.release.core-os.net/amd64-usr/current/coreos_production_vmware_ova.ova

Between vmdk and ova that pretty much covers vmware I think. What sort of image are you looking for?

@marineam

This comment has been minimized.

Show comment
Hide comment
@marineam

marineam May 13, 2015

(the OVA should work with ESXi and all the fancier products)

(the OVA should work with ESXi and all the fancier products)

@olliewalsh

This comment has been minimized.

Show comment
Hide comment
@olliewalsh

olliewalsh May 13, 2015

Not always :-) In one particular deployment I'm presented with a bare VM to be reconfigured - I have full admin rights on the VM, but not on the ESXi/VCenter hosting it (so I can't deploy new VMs from OVA etc..).
The bare-metal/ISO approach seems like easiest option, if only there was an OEM image for vmware.

Not always :-) In one particular deployment I'm presented with a bare VM to be reconfigured - I have full admin rights on the VM, but not on the ESXi/VCenter hosting it (so I can't deploy new VMs from OVA etc..).
The bare-metal/ISO approach seems like easiest option, if only there was an OEM image for vmware.

@marineam

This comment has been minimized.

Show comment
Hide comment
@marineam

marineam May 13, 2015

Well, you can convert the vmdk to a raw disk image and write that to disk. coreos-install is just a wrapper around downloading and verifying images via gpg with a little extra to throw in a cloud config file. Not sure if your situation is common enough for us to provide both raw and vmdk images. You'll just need to do the conversion on some system that has a tool for the job like qemu-img

Well, you can convert the vmdk to a raw disk image and write that to disk. coreos-install is just a wrapper around downloading and verifying images via gpg with a little extra to throw in a cloud config file. Not sure if your situation is common enough for us to provide both raw and vmdk images. You'll just need to do the conversion on some system that has a tool for the job like qemu-img

@olliewalsh

This comment has been minimized.

Show comment
Hide comment
@olliewalsh

olliewalsh May 13, 2015

Modifying the vmdk image doesn't help in this case. I have a (virtual) disk to install to. I can't easily replace that disk with a different image (I could, but it would be much more effort).

As I said in the summary - it's relatively straightforward to workaround, just need to get the files from the vmdk and onto the OEM partition...

Not sure if your situation is common enough

Yea, I was wondering that. I doubt this is a extremely rare though. E.g where bare-metal infrastructure is virtualized everyone still thinks in terms of bare-metal hosts so it's ISOs or PXE for OS installs. Maybe I'm wrong...

Modifying the vmdk image doesn't help in this case. I have a (virtual) disk to install to. I can't easily replace that disk with a different image (I could, but it would be much more effort).

As I said in the summary - it's relatively straightforward to workaround, just need to get the files from the vmdk and onto the OEM partition...

Not sure if your situation is common enough

Yea, I was wondering that. I doubt this is a extremely rare though. E.g where bare-metal infrastructure is virtualized everyone still thinks in terms of bare-metal hosts so it's ISOs or PXE for OS installs. Maybe I'm wrong...

@mkuzmin

This comment has been minimized.

Show comment
Hide comment
@mkuzmin

mkuzmin Nov 24, 2015

vmware_image.bin.bz2 artifact with included VMware customizations would be very helpful for deploying to vSphere.
Right now we have to upload OVF-file, and then customize it. Much more robust solution would be creating a new VM from scratch, customize all hardware settings, boot from ISO, and install CoreOS to disk. HashiCorp Packer automates this procedure.

Unfortunately, calling

# coreos-install -d /dev/sda/ -V current -o vmware

fails with

/usr/bin/coreos-install: Image URL unavailable: http://stable.release.core-os.net/amd64-usr/current/coreos_production_vmware_image.bin.bz2

mkuzmin commented Nov 24, 2015

vmware_image.bin.bz2 artifact with included VMware customizations would be very helpful for deploying to vSphere.
Right now we have to upload OVF-file, and then customize it. Much more robust solution would be creating a new VM from scratch, customize all hardware settings, boot from ISO, and install CoreOS to disk. HashiCorp Packer automates this procedure.

Unfortunately, calling

# coreos-install -d /dev/sda/ -V current -o vmware

fails with

/usr/bin/coreos-install: Image URL unavailable: http://stable.release.core-os.net/amd64-usr/current/coreos_production_vmware_image.bin.bz2
@mimmus

This comment has been minimized.

Show comment
Hide comment
@mimmus

mimmus Jun 30, 2016

I have same problem. Booting diskless could be useful on VMware too.

mimmus commented Jun 30, 2016

I have same problem. Booting diskless could be useful on VMware too.

@jonaz

This comment has been minimized.

Show comment
Hide comment
@jonaz

jonaz Jan 5, 2017

We have this problem aswell. Installing coreos with coreos-install use foreman for PXE and we would like to have vmware tools in our image.

jonaz commented Jan 5, 2017

We have this problem aswell. Installing coreos with coreos-install use foreman for PXE and we would like to have vmware tools in our image.

bgilbert added a commit to bgilbert/scripts that referenced this issue Jan 19, 2017

image_to_vm: Add vmware_raw image type
Allow "coreos-install -o vmware_raw" to install Container Linux with
the vmware OEM.

Use base DISK_LAYOUT to reduce the minimum disk size.

Fixes coreos/bugs#359.

@bgilbert bgilbert referenced this issue in coreos/scripts Jan 19, 2017

Merged

image_to_vm: Add vmware_raw image type #635

@pizzarabe

This comment has been minimized.

Show comment
Hide comment
@pizzarabe

pizzarabe Jan 31, 2017

What do we need to do, to get that? "Just" building a new image? The Installer already tries to install the image but of course there is no.

What do we need to do, to get that? "Just" building a new image? The Installer already tries to install the image but of course there is no.

@crawford

This comment has been minimized.

Show comment
Hide comment
@crawford

crawford Jan 31, 2017

Member

@pizzarabe nothing. If we decide the patch is acceptable, those images will be built as part of our release process. The install script would then just work.

Member

crawford commented Jan 31, 2017

@pizzarabe nothing. If we decide the patch is acceptable, those images will be built as part of our release process. The install script would then just work.

@crawford crawford added this to the Container Linux Alpha 1313.0.0 milestone Jan 31, 2017

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Feb 1, 2017

Member

We've added a new VM type, vmware_raw, which can installed with coreos-install -o vmware_raw. This should go out in the next alpha release.

Member

bgilbert commented Feb 1, 2017

We've added a new VM type, vmware_raw, which can installed with coreos-install -o vmware_raw. This should go out in the next alpha release.

@pizzarabe

This comment has been minimized.

Show comment
Hide comment
@pizzarabe

pizzarabe Feb 3, 2017

Nice, the latest alpha already got that (1312.0.0). Is there a way to build the vmware_raw Image also for the next stable release?

pizzarabe commented Feb 3, 2017

Nice, the latest alpha already got that (1312.0.0). Is there a way to build the vmware_raw Image also for the next stable release?

tunguyen9889 added a commit to tunguyen9889/scripts that referenced this issue Feb 6, 2017

image_to_vm: Add vmware_raw image type
Allow "coreos-install -o vmware_raw" to install Container Linux with
the vmware OEM.

Use base DISK_LAYOUT to reduce the minimum disk size.

Fixes coreos/bugs#359.

dm0- added a commit to dm0-/scripts that referenced this issue Feb 21, 2017

image_to_vm: Add vmware_raw image type
Allow "coreos-install -o vmware_raw" to install Container Linux with
the vmware OEM.

Use base DISK_LAYOUT to reduce the minimum disk size.

Fixes coreos/bugs#359.

@dm0- dm0- referenced this issue in coreos/scripts Feb 21, 2017

Merged

Build the vmware_raw format for stable #643

dm0- added a commit to dm0-/scripts that referenced this issue Feb 22, 2017

image_to_vm: Add vmware_raw image type
Allow "coreos-install -o vmware_raw" to install Container Linux with
the vmware OEM.

Use base DISK_LAYOUT to reduce the minimum disk size.

Fixes coreos/bugs#359.

dm0- added a commit to dm0-/scripts that referenced this issue Feb 22, 2017

image_to_vm: Add vmware_raw image type
Allow "coreos-install -o vmware_raw" to install Container Linux with
the vmware OEM.

Use base DISK_LAYOUT to reduce the minimum disk size.

Fixes coreos/bugs#359.

@mkuzmin mkuzmin referenced this issue in terraform-providers/terraform-provider-vsphere Jun 28, 2017

Closed

OVA upload support for vsphere provider #74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment