Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of shadowsor@gmail.com
 designates 209.85.212.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <C66C814C1ABFA8449FF65CB44953A8B4012CBB65BCC6@SJCPMAILBOX01.citrite.net>
References: <1303117737.56301.1347239587681.JavaMail.jiratomcat@arcas>
	<213077081.58493.1347295928670.JavaMail.jiratomcat@arcas>
	<CALFpzo7PivdhORn3K7FXUDCFyTYO_ggrGR_DZFyu93YLK4FX1Q@mail.gmail.com>
	<C66C814C1ABFA8449FF65CB44953A8B4012CBB65BCC6@SJCPMAILBOX01.citrite.net>
Date: Wed, 12 Sep 2012 22:36:46 -0600
Message-ID: 
 <CALFpzo4Sm5MOZC04=Q0C2EuOn6fDS8Kd_-vN9eYtk6N91uLhew@mail.gmail.com>
Subject: Re: [jira] [Updated] (CLOUDSTACK-67) Resizing
From: Marcus Sorensen <shadowsor@gmail.com>
To: cloudstack-dev@incubator.apache.org, wido <wido@widodh.nl>
Content-Type: text/plain; charset=ISO-8859-1

I mainly wanted to send out some feelers to see if there was an
imminent branch merge or something. 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.

A few questions:

Is all KVM storage that's file based automatically qcow2 in
cloudstack? That would be NFS and local, are there others?  It should
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 reminds me, cloudstack no longer bundles or requires a custom
qemu-kvm package, correct? Seems like it did at one point.

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.su@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:shadowsor@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) <jira@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