Sent from my iPhone
On Sep 12, 2012, at 9:37 PM, "Marcus Sorensen" <shadow...@gmail.com> wrote: > I mainly wanted to send out some feelers to see if there was an > imminent branch merge or something. It depends how big of your patch. If it changes current code too much, may not get a chance to be merged into 4.0 branch. But I think this feature shouldn't be that disruptive, so send out your patch, the merge window is still open. > If not, I'll clean up mine a bit > and let people have a look. I haven't looked into changing the UI yet > at all, and since it seems there's a redesign in progress maybe I'll > hold off. The API pieces are all there and work in my test > environment. There are a few things I had to work around, for example > it seems we're missing java bindings for key libvirt calls, which I > implemented via host script instead if your version of libvirtd/virsh > supports it. We are using the latest libvirt java binding, if it doesn't include the API you want, better to send a patch libvirt mailing list also. Host script is ok in the current stage. > > A few questions: > > Is all KVM storage that's file based automatically qcow2 in Yes, if it's file based, then qcow2 will be used. > cloudstack? That would be NFS and local, are there others? It should NSF, local and sharedmount(for cluster file system, like gluster). > be simple for me to add those in and do some testing I think, although > qemu-img needs to be a specific, fairly recent version to support > qcow2 resizing. Which version of qemu-img are you using? Is it included in Ubuntu 12.04? > > Which reminds me, cloudstack no longer bundles or requires a custom > qemu-kvm package, correct? Seems like it did at one point. Yes, We don't need it any more. > > Wido, I've played with Ceph a bit and RBD, but it's been maybe a year. > Is resizing of the RADOS device handled well? Have you played at all > with resizing the block device file of a live VM and then issuing a > 'virsh blockresize'? > > > On Wed, Sep 12, 2012 at 6:36 PM, Edison Su <edison...@citrix.com> wrote: >> Patch is always welcome. Will you change UI also? Maybe we can't check in UI >> part at this moment, but at least, the backend code should be ok. >> >>> -----Original Message----- >>> From: Marcus Sorensen [mailto:shadow...@gmail.com] >>> Sent: Wednesday, September 12, 2012 4:36 PM >>> To: cloudstack-dev@incubator.apache.org >>> Subject: Re: [jira] [Updated] (CLOUDSTACK-67) Resizing >>> >>> I know everyone is working on the release,but is anyone working on >>> this? I've got a working implementation against KVM/CLVM. I'm not >>> super interested in setting up environments for all of the various >>> hypervisor/storage combos, but this could be used as a springboard for >>> the other types. >>> >>> On Mon, Sep 10, 2012 at 10:52 AM, Alex Huang (JIRA) <j...@apache.org> >>> wrote: >>>> >>>> [ https://issues.apache.org/jira/browse/CLOUDSTACK- >>> 67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] >>>> >>>> Alex Huang updated CLOUDSTACK-67: >>>> --------------------------------- >>>> >>>> Fix Version/s: 4.1.0 >>>> >>>>> Resizing >>>>> -------- >>>>> >>>>> Key: CLOUDSTACK-67 >>>>> URL: >>> https://issues.apache.org/jira/browse/CLOUDSTACK-67 >>>>> Project: CloudStack >>>>> Issue Type: Improvement >>>>> Reporter: XxYton >>>>> Fix For: 4.1.0 >>>>> >>>>> >>>>> Resizing of volumes and instances is not possible right now. >>>>> Instance resizing should be done without rebooting the VM if >>> supported by hypervisor. >>>> >>>> -- >>>> This message is automatically generated by JIRA. >>>> If you think it was sent incorrectly, please contact your JIRA >>> administrators >>>> For more information on JIRA, see: >>> http://www.atlassian.com/software/jira
