[Thincrust-devel] USER STORIES --type
Bryan Kearney
bkearney at redhat.com
Fri Sep 12 17:17:31 UTC 2008
Joey Boggs wrote:
> Bryan Kearney wrote:
>> David Huff wrote:
>>> Bryan Kearney wrote:
>>>> Joey Boggs wrote:
>>>>> Only allows 1 disk in a kickstart currently, anymore will fail.
>>>>> Working on the virt-convert scenarios next.
>>>>
>>>> I testted it and got the error below. Couple of comments
>>>>
>>>> 1) If I specify the --appliancetype then is the format, vmem, and
>>>> vcpu items ignored? Huff, based on our chats yesterday should this
>>>> be --type
>>>> (to prep for package, ovf, vmware etc)
>>>>
>>>
>>> So I started to summarize our conversation from yesterday, where we
>>> decided that there should be a --type flag that sets/overrides all
>>> other options for that type. Below are some of my thoughts form the
>>> discussion.....
>>>
>>> Valid types would be, KVM, XEN, VMARE, EC2.
>> So, type is hypervisor? Is so, then packging should be libvirt? That
>> is kinda wierd since libvirt can (in some cases) abstract out hypervisor.
>>> Overwritten options are, DISK FORMAT, META-DATA FORMAT, VMEM, VCPU,
>>> PACKAGE TYPE
>>> Package formats can be: TAR, ZIP, OVF, other
>>>
>>> When I started thinking about implementation I started confusing
>>> myself, the existing tools in this arena are:
>>> VIRT-CONVERT - converts vmware to libvirt calls qemu-img
>>> VIRT-PACK - converts libvirt to vmware[1]
>>
>> In the latest release notes, it was mentioned that this would go into
>> virt-convert.
>>
>
> Is anyone already working on this?
I do not know.. can you follow up with them on that?
-- bk
More information about the Thincrust-devel
mailing list