Oddthesis jboss-cloud → 1.0.0.Beta2

Comments and changes to this ticket

• You flagged this item as spam.
  

  Deleted User January 23rd, 2009 @ 08:36 AM

  • Title changed from “Allow to run appliances on ESXi/VI3” to “VMware support”

  We want to run our appliances in an enterprise environment, this should be the priority. Unfortunately there are some differences in disk formats between VMware ESX/ESXi and Server/Player/Fusion/Workstation, so we simply can't use the same image in different environments.

  Maybe we should provide more Rake tasks to select which environment we want use?

  We should use SCSI image disks rather than IDE. IDE is disks we can run only on Server/Player/Fusion/Workstation.

  Should we provide ability to modify some other configuration options for VMware appliances (e.g. networking, type of networking)?

• You flagged this item as spam.
  

  Deleted User January 24th, 2009 @ 02:50 AM

  We should support both environments (ESX/ESXi and Server/Player/Fusion/Workstation). My name proposal for these environments is as follows (to better distinguish those two):

  • Server/Player/Fusion/Workstation as personal environment
  • ESX/ESXi as enterprise environment

  Differences between those environments:

  • Enterprise environments uses only SCSI disks. Best performance SCSI controller is lsilogic, we we'll use it.
  • Networking. Personal type could use NAT networking name. This is the default name for such networking and it should work out-of-box. We don't know network name in enterprise environments.

  There should be two rake task types:

  1. rake appliance:APPLIANCE_NAME:vmware:personal
  2. rake appliance:APPLIANCE_NAME:vmware:enterprise

  For first environment we can build IDE disk types. This is exactly what we're doing right now.

  At this time qemu-img which is used for creation disks for our appliances creates only IDE disks. I've searched for a solution to convert these disks to a SCSI. I haven't found a real good solution, just partial.

  There is a patch on QEMU forums that enables creating SCSI disks. It isn't applied to base qemu :/ So I've tried to apply to latest src.rpm of qemu on fedora, without success. I ran into this bug. Fortunately there is a src.rpm in updates-testing.

• You flagged this item as spam.
  

  Deleted User January 24th, 2009 @ 03:37 AM

  • Tag changed from “appliance, task, vmware” to “appliance, python-virtinst, qemu, task, vmware”
  • State changed from “new” to “open”

  I have updated patch for SCSI disk support from QEMU forums to 0.9.1 version of qemu. The qemu build was successful.

  • qemu-0.9.1-qemu-img-scsi.patch 5.8 KB

• You flagged this item as spam.
  

  Deleted User January 24th, 2009 @ 04:54 AM

  After install patched qemu-img and some changes in lib/python-virtinst I have successfully created a SCSCI disk. Patch added.

  After downloading VMware Virtual Disk Development Kit and using vmware-vdiskmanager I have successfully converted created disk to a ESX format.

  • python-virtinst-scsi-disk-conversion.patch 2 KB

• You flagged this item as spam.
  

  Deleted User January 30th, 2009 @ 02:03 AM

  For now the solution is: leave the appliance as before for personal VMware products, but add a SCSI disk for enterprise products. Maybe in the future we'll use only lsilogic disk, but needs more time to test personal environments.

  Currently working on adding support for SCSI kernel drivers to appliance image.

• You flagged this item as spam.
  

  Deleted User January 30th, 2009 @ 02:28 AM

  After install latest devel packages of appliance-tools (http://koji.fedoraproject.org/ko...) and livecd-tools (http://koji.fedoraproject.org/ko...) I was able to run appliance on VMware ESXi.

  It is required to add scsi_mod.scan=sync to add to kernel command line to boot without pb (more: https://bugzilla.redhat.com/show...).

• You flagged this item as spam.
  

  Deleted User February 3rd, 2009 @ 12:46 AM

  • Milestone set to “1.0.0.Beta2”

• You flagged this item as spam.
  

  Deleted User February 3rd, 2009 @ 06:30 AM

  • State changed from “open” to “resolved”

  Appliances are working on VMware Server and VMware ESXi. Closing.