You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Vadim Kimlaychuk <Va...@Elion.ee> on 2014/12/01 08:48:10 UTC
RE: root resize support in the UI
It is interesting how, in genereal, this works for XenServer (for exmaple)? I do understand, that entire logic of CS is built around hypervisor capabilities. It does not do more than each specific hypervisor can offer. KVM do have "virt-resize" tool that can resize Linux partitions, but it will probably not work for Windows hosts anyway. So, to be honest, this UI feature should only be visible for Linux guests.
I don't know whether different approach to build and resize root partitions for all hypervisors exist? If it is not possible to do on hypervisor level, how does CS do this?
Vadim.
-----Original Message-----
From: Nux! [mailto:nux@li.nux.ro]
Sent: Sunday, November 30, 2014 2:03 PM
To: dev@cloudstack.apache.org
Subject: Re: root resize support in the UI
It's very possible Citrix customised that installation, what they do for their own customers is their own business. It was certainly possible to do it with 4.3, Marcus wrote some patches at some point to enable this functionality (KVM only, again).
The UI has always been considered more of a proof of concept, though it's a very much needed part of ACS, as such everyone is encouraged to use the API and build their own interfaces. I missed some important options and customers because I thought
GreenQloud, Exoscale etc will give you some credit as a new customer so you can check out their UI. They don't have as many options as the ACS one, but I found this to be a feature, customers shouldn't be exposed to too many options, they'll just get their noses caught in them. :)
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> To: dev@cloudstack.apache.org
> Sent: Sunday, 30 November, 2014 10:53:56
> Subject: RE: root resize support in the UI
> Lucian,
>
> I have seen CS 4.3 installation made by Citrix at our parnter and they have the
> same feature enabled for XenServer and VmWare. I wonder how does it work ?
> They have their own team of developers to make some extra features they need
> (like plugin for statistics and billing), but did they implement particularly
> this feature or Citrix did it - I don't know. It seems this part of code is
> not contributed back to community anyway. It would be nice to have it,
> especially together with "slieders" which are quite popular right now as I
> understood.
>
> Vadim.
>
> -----Original Message-----
> From: Nux! [mailto:nux@li.nux.ro]
> Sent: Saturday, November 29, 2014 9:48 PM
> To: dev@cloudstack.apache.org
> Subject: Re: root resize support in the UI
>
> Vadim,
>
> 1. Only KVM for now, due to lack of interest I guess 2. The root disk
> value needs to be equal or larger than that of the template, otherwise
> you end up with a broken disk, obviously. So go for minimal (say under
> 10G) templates that can resize themselves, such as the ones at
> http://dl.openvm.eu ;) 3. The backend API has been supporting this
> since 4.4.0, it's the UI that is lagging behind More details here
> https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
>> From: "Vadim Kimlaychuk" <Va...@Elion.ee>
>> To: dev@cloudstack.apache.org
>> Sent: Saturday, 29 November, 2014 15:17:16
>> Subject: RE: root resize support in the UI
>
>> Nux,
>>
>> Can you give more information about this functionality? I am particularly
>> interesting to show to the user this field, but don't know how it will work.
>> Particularly is interesting:
>> 1. Does it work for all hypervisors or just KVM?
>> 2. Does it depend on the template root partition (i.e. I have 10G
>> root at template and put 5G to desired. Will it work?) 3. This is
>> just UI patch, shouldn't it be activated at the backend as well ?
>>
>> Thanks,
>> Vadim
>> ________________________________________
>> From: Nux! [nux@li.nux.ro]
>> Sent: Saturday, November 29, 2014 12:37
>> To: dev@cloudstack.apache.org
>> Cc: Brian Federle
>> Subject: Re: root resize support in the UI
>>
>> BTW, the code needed to enable custom root size during instance
>> creation is very small, functionality is already there.
>> This patch is needed
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8
>> f ec09ba481fbd3b8c2a9e4d31ef06f113b037cb
>> , I tested it and it works fine.
>>
>> And this is the result: https://i.imgur.com/xrs0mu4.png
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Original Message -----
>>> From: "Nux!" <nu...@li.nux.ro>
>>> To: dev@cloudstack.apache.org
>>> Cc: "Brian Federle" <Br...@citrix.com>
>>> Sent: Saturday, 29 November, 2014 00:57:37
>>> Subject: Re: root resize support in the UI
>>
>>> Yes, you have a point.
>>>
>>> Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7992
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>> ----- Original Message -----
>>>> From: "Mike Tutkowski" <mi...@solidfire.com>
>>>> To: dev@cloudstack.apache.org
>>>> Cc: "Brian Federle" <Br...@citrix.com>
>>>> Sent: Saturday, 29 November, 2014 00:48:03
>>>> Subject: Re: root resize support in the UI
>>>
>>>> Well...I don't know...we kind of have features all over the place
>>>> that work for one hypervisor and not for another.
>>>>
>>>> If we're cool with that approach, this would be just one more area
>>>> where we have this kind of hypervisor-specific behavior (perhaps
>>>> all hypervisors support such an action in the future).
>>>>
>>>> On Fri, Nov 28, 2014 at 5:41 PM, Nux! <nu...@li.nux.ro> wrote:
>>>>
>>>>> Was thinking to just patch my local installation. Devs might not
>>>>> go too crazy over this idea since root resize is not supported
>>>>> across all hypervisors (KVM only atm).
>>>>>
>>>>> But if you think this has a chance to go official, I will open an issue.
>>>>>
>>>>> Thanks,
>>>>> Lucian
>>>>>
>>>>> --
>>>>> Sent from the Delta quadrant using Borg technology!
>>>>>
>>>>> Nux!
>>>>> www.nux.ro
>>>>>
>>>>> ----- Original Message -----
>>>>> > From: "Mike Tutkowski" <mi...@solidfire.com>
>>>>> > To: dev@cloudstack.apache.org, "Brian Federle"
>>>>> > <Brian.Federle@citrix.com
>>>>> >
>>>>> > Sent: Saturday, 29 November, 2014 00:27:14
>>>>> > Subject: Re: root resize support in the UI
>>>>>
>>>>> > Have you logged a JIRA ticket for this?
>>>>> >
>>>>> > Maybe Brian or one of the GUI people could pick up on it.
>>>>> >
>>>>> > On Fri, Nov 28, 2014 at 4:32 PM, Nux! <nu...@li.nux.ro> wrote:
>>>>> >
>>>>> >> Yeah, I was thinking of that, if it works for DATA, it should
>>>>> >> work for ROOT. But I am not a dev.
>>>>> >>
>>>>> >> Thoughts?
>>>>> >>
>>>>> >> --
>>>>> >> Sent from the Delta quadrant using Borg technology!
>>>>> >>
>>>>> >> Nux!
>>>>> >> www.nux.ro
>>>>> >>
>>>>> >> ----- Original Message -----
>>>>> >> > From: "Mike Tutkowski" <mi...@solidfire.com>
>>>>> >> > To: dev@cloudstack.apache.org
>>>>> >> > Sent: Friday, 28 November, 2014 19:57:27
>>>>> >> > Subject: Re: root resize support in the UI
>>>>> >>
>>>>> >> > For root disks, is it possible to just follow the existing
>>>>> >> > resize
>>>>> pattern
>>>>> >> > we have established in the UI for data disks?
>>>>> >> >
>>>>> >> > On Friday, November 28, 2014, Nux! <nu...@li.nux.ro> wrote:
>>>>> >> >
>>>>> >> >> Hello,
>>>>> >> >>
>>>>> >> >> Wonder if someone can help me with the $subject.
>>>>> >> >>
>>>>> >> >> I remember at some point (4.2?) a new feature showed up
>>>>> >> >> accidentally
>>>>> in
>>>>> >> >> the UI instance creation dialogues, it was concerning "root
>>>>> >> >> size",
>>>>> had a
>>>>> >> >> small box where the number in GB would be introduced.
>>>>> >> >> I'd like to take advantage of that now that this feature
>>>>> >> >> actually
>>>>> works,
>>>>> >> >> even if only in KVM. I'd love it if someone could point me
>>>>> >> >> to that
>>>>> >> piece of
>>>>> >> >> code (prolly just javascript).
>>>>> >> >>
>>>>> >> >> In addition to that, now that root resize works, can any one
>>>>> >> >> suggest
>>>>> >> how I
>>>>> >> >> might put a "resize" button in the Volumes section for the
>>>>> >> >> ROOT
>>>>> disks?
>>>>> >> >>
>>>>> >> >> Lucian
>>>>> >> >>
>>>>> >> >> --
>>>>> >> >> Sent from the Delta quadrant using Borg technology!
>>>>> >> >>
>>>>> >> >> Nux!
>>>>> >> >> www.nux.ro
>>>>> >> >>
>>>>> >> >
>>>>> >> >
>>>>> >> > --
>>>>> >> > *Mike Tutkowski*
>>>>> >> > *Senior CloudStack Developer, SolidFire Inc.*
>>>>> >> > e: mike.tutkowski@solidfire.com
>>>>> >> > o: 303.746.7302
>>>>> >> > Advancing the way the world uses the cloud
>>>>> >> > <http://solidfire.com/solution/overview/?video=play>*™*
>>>>> >>
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > *Mike Tutkowski*
>>>>> > *Senior CloudStack Developer, SolidFire Inc.*
>>>>> > e: mike.tutkowski@solidfire.com
>>>>> > o: 303.746.7302
>>>>> > Advancing the way the world uses the cloud
>>>>> > <http://solidfire.com/solution/overview/?video=play>*™*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Mike Tutkowski*
>>>> *Senior CloudStack Developer, SolidFire Inc.*
>>>> e: mike.tutkowski@solidfire.com
>>>> o: 303.746.7302
>>>> Advancing the way the world uses the cloud
> > > > <http://solidfire.com/solution/overview/?video=play>*™*
Re: root resize support in the UI
Posted by Andrija Panic <an...@gmail.com>.
Exactly my point - reside the damn drive with qemu-img and leave the rest
for the Admin :)
On 1 December 2014 at 09:11, Nux! <nu...@li.nux.ro> wrote:
> Guys,
>
> All that ACS does is to resize the ROOT disk (ie the whole /dev/vda or
> /dev/xvda), it does not care about partitions, filesystems or OSes inside
> it.
>
> Expanding the partitions and filesystems later on is left to the admin, or
> if you have cloud-init installed that will take care of it; it is also
> trivial to expand the partition and filesystem in Windows (Manage > Disk
> management).
>
> ACS has nothing to do with virt-resize, that's part of libguestfs (which
> btw can deal with Windows, too); ACS uses qemu-img [resize] in KVM.
>
> HTH
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Andrija Panic" <an...@gmail.com>
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 1 December, 2014 08:02:05
> > Subject: Re: root resize support in the UI
>
> > I think it would be usefull to have that resize feature for all guests
> > (Linux, Windows, etc) - but perhaps customizes the Resize function to
> > perform partition resize inside Linux (if we are deploying new VM from
> > Linux template) - or simply do not do anything inside guest OS, just
> resize
> > the drive - and let the client handle partition and file system
> resize...it
> > might be more clean implementation I guess...?
> >
> > On 1 December 2014 at 08:48, Vadim Kimlaychuk <Vadim.Kimlaychuk@elion.ee
> >
> > wrote:
> >
> >> It is interesting how, in genereal, this works for XenServer (for
> >> exmaple)? I do understand, that entire logic of CS is built around
> >> hypervisor capabilities. It does not do more than each specific
> hypervisor
> >> can offer. KVM do have "virt-resize" tool that can resize Linux
> partitions,
> >> but it will probably not work for Windows hosts anyway. So, to be
> honest,
> >> this UI feature should only be visible for Linux guests.
> >>
> >> I don't know whether different approach to build and resize root
> >> partitions for all hypervisors exist? If it is not possible to do on
> >> hypervisor level, how does CS do this?
> >>
> >> Vadim.
> >>
> >> -----Original Message-----
> >> From: Nux! [mailto:nux@li.nux.ro]
> >> Sent: Sunday, November 30, 2014 2:03 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: root resize support in the UI
> >>
> >> It's very possible Citrix customised that installation, what they do for
> >> their own customers is their own business. It was certainly possible to
> do
> >> it with 4.3, Marcus wrote some patches at some point to enable this
> >> functionality (KVM only, again).
> >>
> >> The UI has always been considered more of a proof of concept, though
> it's
> >> a very much needed part of ACS, as such everyone is encouraged to use
> the
> >> API and build their own interfaces. I missed some important options and
> >> customers because I thought
> >>
> >> GreenQloud, Exoscale etc will give you some credit as a new customer so
> >> you can check out their UI. They don't have as many options as the ACS
> one,
> >> but I found this to be a feature, customers shouldn't be exposed to too
> >> many options, they'll just get their noses caught in them. :)
> >>
> >> Lucian
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> ----- Original Message -----
> >> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> >> > To: dev@cloudstack.apache.org
> >> > Sent: Sunday, 30 November, 2014 10:53:56
> >> > Subject: RE: root resize support in the UI
> >>
> >> > Lucian,
> >> >
> >> > I have seen CS 4.3 installation made by Citrix at our parnter
> and
> >> they have the
> >> > same feature enabled for XenServer and VmWare. I wonder how
> does
> >> it work ?
> >> > They have their own team of developers to make some extra
> features
> >> they need
> >> > (like plugin for statistics and billing), but did they implement
> >> particularly
> >> > this feature or Citrix did it - I don't know. It seems this
> part
> >> of code is
> >> > not contributed back to community anyway. It would be nice to
> have
> >> it,
> >> > especially together with "slieders" which are quite popular
> right
> >> now as I
> >> > understood.
> >> >
> >> > Vadim.
> >> >
> >> > -----Original Message-----
> >> > From: Nux! [mailto:nux@li.nux.ro]
> >> > Sent: Saturday, November 29, 2014 9:48 PM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: root resize support in the UI
> >> >
> >> > Vadim,
> >> >
> >> > 1. Only KVM for now, due to lack of interest I guess 2. The root disk
> >> > value needs to be equal or larger than that of the template, otherwise
> >> > you end up with a broken disk, obviously. So go for minimal (say under
> >> > 10G) templates that can resize themselves, such as the ones at
> >> > http://dl.openvm.eu ;) 3. The backend API has been supporting this
> >> > since 4.4.0, it's the UI that is lagging behind More details here
> >> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >> >
> >> > Lucian
> >> >
> >> > --
> >> > Sent from the Delta quadrant using Borg technology!
> >> >
> >> > Nux!
> >> > www.nux.ro
> >> >
> >> > ----- Original Message -----
> >> >> From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> >> >> To: dev@cloudstack.apache.org
> >> >> Sent: Saturday, 29 November, 2014 15:17:16
> >> >> Subject: RE: root resize support in the UI
> >> >
> >> >> Nux,
> >> >>
> >> >> Can you give more information about this functionality? I am
> >> particularly
> >> >> interesting to show to the user this field, but don't know
> how
> >> it will work.
> >> >> Particularly is interesting:
> >> >> 1. Does it work for all hypervisors or just KVM?
> >> >> 2. Does it depend on the template root partition (i.e. I have 10G
> >> >> root at template and put 5G to desired. Will it work?) 3. This is
> >> >> just UI patch, shouldn't it be activated at the backend as well ?
> >> >>
> >> >> Thanks,
> >> >> Vadim
> >> >> ________________________________________
> >> >> From: Nux! [nux@li.nux.ro]
> >> >> Sent: Saturday, November 29, 2014 12:37
> >> >> To: dev@cloudstack.apache.org
> >> >> Cc: Brian Federle
> >> >> Subject: Re: root resize support in the UI
> >> >>
> >> >> BTW, the code needed to enable custom root size during instance
> >> >> creation is very small, functionality is already there.
> >> >> This patch is needed
> >> >>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8
> >> >> f ec09ba481fbd3b8c2a9e4d31ef06f113b037cb
> >> >> , I tested it and it works fine.
> >> >>
> >> >> And this is the result: https://i.imgur.com/xrs0mu4.png
> >> >>
> >> >> --
> >> >> Sent from the Delta quadrant using Borg technology!
> >> >>
> >> >> Nux!
> >> >> www.nux.ro
> >> >>
> >> >> ----- Original Message -----
> >> >>> From: "Nux!" <nu...@li.nux.ro>
> >> >>> To: dev@cloudstack.apache.org
> >> >>> Cc: "Brian Federle" <Br...@citrix.com>
> >> >>> Sent: Saturday, 29 November, 2014 00:57:37
> >> >>> Subject: Re: root resize support in the UI
> >> >>
> >> >>> Yes, you have a point.
> >> >>>
> >> >>> Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7992
> >> >>>
> >> >>> --
> >> >>> Sent from the Delta quadrant using Borg technology!
> >> >>>
> >> >>> Nux!
> >> >>> www.nux.ro
> >> >>>
> >> >>> ----- Original Message -----
> >> >>>> From: "Mike Tutkowski" <mi...@solidfire.com>
> >> >>>> To: dev@cloudstack.apache.org
> >> >>>> Cc: "Brian Federle" <Br...@citrix.com>
> >> >>>> Sent: Saturday, 29 November, 2014 00:48:03
> >> >>>> Subject: Re: root resize support in the UI
> >> >>>
> >> >>>> Well...I don't know...we kind of have features all over the place
> >> >>>> that work for one hypervisor and not for another.
> >> >>>>
> >> >>>> If we're cool with that approach, this would be just one more area
> >> >>>> where we have this kind of hypervisor-specific behavior (perhaps
> >> >>>> all hypervisors support such an action in the future).
> >> >>>>
> >> >>>> On Fri, Nov 28, 2014 at 5:41 PM, Nux! <nu...@li.nux.ro> wrote:
> >> >>>>
> >> >>>>> Was thinking to just patch my local installation. Devs might not
> >> >>>>> go too crazy over this idea since root resize is not supported
> >> >>>>> across all hypervisors (KVM only atm).
> >> >>>>>
> >> >>>>> But if you think this has a chance to go official, I will open an
> >> issue.
> >> >>>>>
> >> >>>>> Thanks,
> >> >>>>> Lucian
> >> >>>>>
> >> >>>>> --
> >> >>>>> Sent from the Delta quadrant using Borg technology!
> >> >>>>>
> >> >>>>> Nux!
> >> >>>>> www.nux.ro
> >> >>>>>
> >> >>>>> ----- Original Message -----
> >> >>>>> > From: "Mike Tutkowski" <mi...@solidfire.com>
> >> >>>>> > To: dev@cloudstack.apache.org, "Brian Federle"
> >> >>>>> > <Brian.Federle@citrix.com
> >> >>>>> >
> >> >>>>> > Sent: Saturday, 29 November, 2014 00:27:14
> >> >>>>> > Subject: Re: root resize support in the UI
> >> >>>>>
> >> >>>>> > Have you logged a JIRA ticket for this?
> >> >>>>> >
> >> >>>>> > Maybe Brian or one of the GUI people could pick up on it.
> >> >>>>> >
> >> >>>>> > On Fri, Nov 28, 2014 at 4:32 PM, Nux! <nu...@li.nux.ro> wrote:
> >> >>>>> >
> >> >>>>> >> Yeah, I was thinking of that, if it works for DATA, it should
> >> >>>>> >> work for ROOT. But I am not a dev.
> >> >>>>> >>
> >> >>>>> >> Thoughts?
> >> >>>>> >>
> >> >>>>> >> --
> >> >>>>> >> Sent from the Delta quadrant using Borg technology!
> >> >>>>> >>
> >> >>>>> >> Nux!
> >> >>>>> >> www.nux.ro
> >> >>>>> >>
> >> >>>>> >> ----- Original Message -----
> >> >>>>> >> > From: "Mike Tutkowski" <mi...@solidfire.com>
> >> >>>>> >> > To: dev@cloudstack.apache.org
> >> >>>>> >> > Sent: Friday, 28 November, 2014 19:57:27
> >> >>>>> >> > Subject: Re: root resize support in the UI
> >> >>>>> >>
> >> >>>>> >> > For root disks, is it possible to just follow the existing
> >> >>>>> >> > resize
> >> >>>>> pattern
> >> >>>>> >> > we have established in the UI for data disks?
> >> >>>>> >> >
> >> >>>>> >> > On Friday, November 28, 2014, Nux! <nu...@li.nux.ro> wrote:
> >> >>>>> >> >
> >> >>>>> >> >> Hello,
> >> >>>>> >> >>
> >> >>>>> >> >> Wonder if someone can help me with the $subject.
> >> >>>>> >> >>
> >> >>>>> >> >> I remember at some point (4.2?) a new feature showed up
> >> >>>>> >> >> accidentally
> >> >>>>> in
> >> >>>>> >> >> the UI instance creation dialogues, it was concerning "root
> >> >>>>> >> >> size",
> >> >>>>> had a
> >> >>>>> >> >> small box where the number in GB would be introduced.
> >> >>>>> >> >> I'd like to take advantage of that now that this feature
> >> >>>>> >> >> actually
> >> >>>>> works,
> >> >>>>> >> >> even if only in KVM. I'd love it if someone could point me
> >> >>>>> >> >> to that
> >> >>>>> >> piece of
> >> >>>>> >> >> code (prolly just javascript).
> >> >>>>> >> >>
> >> >>>>> >> >> In addition to that, now that root resize works, can any one
> >> >>>>> >> >> suggest
> >> >>>>> >> how I
> >> >>>>> >> >> might put a "resize" button in the Volumes section for the
> >> >>>>> >> >> ROOT
> >> >>>>> disks?
> >> >>>>> >> >>
> >> >>>>> >> >> Lucian
> >> >>>>> >> >>
> >> >>>>> >> >> --
> >> >>>>> >> >> Sent from the Delta quadrant using Borg technology!
> >> >>>>> >> >>
> >> >>>>> >> >> Nux!
> >> >>>>> >> >> www.nux.ro
> >> >>>>> >> >>
> >> >>>>> >> >
> >> >>>>> >> >
> >> >>>>> >> > --
> >> >>>>> >> > *Mike Tutkowski*
> >> >>>>> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> >>>>> >> > e: mike.tutkowski@solidfire.com
> >> >>>>> >> > o: 303.746.7302
> >> >>>>> >> > Advancing the way the world uses the cloud
> >> >>>>> >> > <http://solidfire.com/solution/overview/?video=play>*™*
> >> >>>>> >>
> >> >>>>> >
> >> >>>>> >
> >> >>>>> >
> >> >>>>> > --
> >> >>>>> > *Mike Tutkowski*
> >> >>>>> > *Senior CloudStack Developer, SolidFire Inc.*
> >> >>>>> > e: mike.tutkowski@solidfire.com
> >> >>>>> > o: 303.746.7302
> >> >>>>> > Advancing the way the world uses the cloud
> >> >>>>> > <http://solidfire.com/solution/overview/?video=play>*™*
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> *Mike Tutkowski*
> >> >>>> *Senior CloudStack Developer, SolidFire Inc.*
> >> >>>> e: mike.tutkowski@solidfire.com
> >> >>>> o: 303.746.7302
> >> >>>> Advancing the way the world uses the cloud
> >> > > > > <http://solidfire.com/solution/overview/?video=play>*™*
> >>
> >
> >
> >
> > --
> >
> > Andrija Panić
>
--
Andrija Panić
Re: root resize support in the UI
Posted by Nux! <nu...@li.nux.ro>.
Guys,
All that ACS does is to resize the ROOT disk (ie the whole /dev/vda or /dev/xvda), it does not care about partitions, filesystems or OSes inside it.
Expanding the partitions and filesystems later on is left to the admin, or if you have cloud-init installed that will take care of it; it is also trivial to expand the partition and filesystem in Windows (Manage > Disk management).
ACS has nothing to do with virt-resize, that's part of libguestfs (which btw can deal with Windows, too); ACS uses qemu-img [resize] in KVM.
HTH
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Andrija Panic" <an...@gmail.com>
> To: dev@cloudstack.apache.org
> Sent: Monday, 1 December, 2014 08:02:05
> Subject: Re: root resize support in the UI
> I think it would be usefull to have that resize feature for all guests
> (Linux, Windows, etc) - but perhaps customizes the Resize function to
> perform partition resize inside Linux (if we are deploying new VM from
> Linux template) - or simply do not do anything inside guest OS, just resize
> the drive - and let the client handle partition and file system resize...it
> might be more clean implementation I guess...?
>
> On 1 December 2014 at 08:48, Vadim Kimlaychuk <Va...@elion.ee>
> wrote:
>
>> It is interesting how, in genereal, this works for XenServer (for
>> exmaple)? I do understand, that entire logic of CS is built around
>> hypervisor capabilities. It does not do more than each specific hypervisor
>> can offer. KVM do have "virt-resize" tool that can resize Linux partitions,
>> but it will probably not work for Windows hosts anyway. So, to be honest,
>> this UI feature should only be visible for Linux guests.
>>
>> I don't know whether different approach to build and resize root
>> partitions for all hypervisors exist? If it is not possible to do on
>> hypervisor level, how does CS do this?
>>
>> Vadim.
>>
>> -----Original Message-----
>> From: Nux! [mailto:nux@li.nux.ro]
>> Sent: Sunday, November 30, 2014 2:03 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: root resize support in the UI
>>
>> It's very possible Citrix customised that installation, what they do for
>> their own customers is their own business. It was certainly possible to do
>> it with 4.3, Marcus wrote some patches at some point to enable this
>> functionality (KVM only, again).
>>
>> The UI has always been considered more of a proof of concept, though it's
>> a very much needed part of ACS, as such everyone is encouraged to use the
>> API and build their own interfaces. I missed some important options and
>> customers because I thought
>>
>> GreenQloud, Exoscale etc will give you some credit as a new customer so
>> you can check out their UI. They don't have as many options as the ACS one,
>> but I found this to be a feature, customers shouldn't be exposed to too
>> many options, they'll just get their noses caught in them. :)
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Original Message -----
>> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
>> > To: dev@cloudstack.apache.org
>> > Sent: Sunday, 30 November, 2014 10:53:56
>> > Subject: RE: root resize support in the UI
>>
>> > Lucian,
>> >
>> > I have seen CS 4.3 installation made by Citrix at our parnter and
>> they have the
>> > same feature enabled for XenServer and VmWare. I wonder how does
>> it work ?
>> > They have their own team of developers to make some extra features
>> they need
>> > (like plugin for statistics and billing), but did they implement
>> particularly
>> > this feature or Citrix did it - I don't know. It seems this part
>> of code is
>> > not contributed back to community anyway. It would be nice to have
>> it,
>> > especially together with "slieders" which are quite popular right
>> now as I
>> > understood.
>> >
>> > Vadim.
>> >
>> > -----Original Message-----
>> > From: Nux! [mailto:nux@li.nux.ro]
>> > Sent: Saturday, November 29, 2014 9:48 PM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: root resize support in the UI
>> >
>> > Vadim,
>> >
>> > 1. Only KVM for now, due to lack of interest I guess 2. The root disk
>> > value needs to be equal or larger than that of the template, otherwise
>> > you end up with a broken disk, obviously. So go for minimal (say under
>> > 10G) templates that can resize themselves, such as the ones at
>> > http://dl.openvm.eu ;) 3. The backend API has been supporting this
>> > since 4.4.0, it's the UI that is lagging behind More details here
>> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
>> >
>> > Lucian
>> >
>> > --
>> > Sent from the Delta quadrant using Borg technology!
>> >
>> > Nux!
>> > www.nux.ro
>> >
>> > ----- Original Message -----
>> >> From: "Vadim Kimlaychuk" <Va...@Elion.ee>
>> >> To: dev@cloudstack.apache.org
>> >> Sent: Saturday, 29 November, 2014 15:17:16
>> >> Subject: RE: root resize support in the UI
>> >
>> >> Nux,
>> >>
>> >> Can you give more information about this functionality? I am
>> particularly
>> >> interesting to show to the user this field, but don't know how
>> it will work.
>> >> Particularly is interesting:
>> >> 1. Does it work for all hypervisors or just KVM?
>> >> 2. Does it depend on the template root partition (i.e. I have 10G
>> >> root at template and put 5G to desired. Will it work?) 3. This is
>> >> just UI patch, shouldn't it be activated at the backend as well ?
>> >>
>> >> Thanks,
>> >> Vadim
>> >> ________________________________________
>> >> From: Nux! [nux@li.nux.ro]
>> >> Sent: Saturday, November 29, 2014 12:37
>> >> To: dev@cloudstack.apache.org
>> >> Cc: Brian Federle
>> >> Subject: Re: root resize support in the UI
>> >>
>> >> BTW, the code needed to enable custom root size during instance
>> >> creation is very small, functionality is already there.
>> >> This patch is needed
>> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8
>> >> f ec09ba481fbd3b8c2a9e4d31ef06f113b037cb
>> >> , I tested it and it works fine.
>> >>
>> >> And this is the result: https://i.imgur.com/xrs0mu4.png
>> >>
>> >> --
>> >> Sent from the Delta quadrant using Borg technology!
>> >>
>> >> Nux!
>> >> www.nux.ro
>> >>
>> >> ----- Original Message -----
>> >>> From: "Nux!" <nu...@li.nux.ro>
>> >>> To: dev@cloudstack.apache.org
>> >>> Cc: "Brian Federle" <Br...@citrix.com>
>> >>> Sent: Saturday, 29 November, 2014 00:57:37
>> >>> Subject: Re: root resize support in the UI
>> >>
>> >>> Yes, you have a point.
>> >>>
>> >>> Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7992
>> >>>
>> >>> --
>> >>> Sent from the Delta quadrant using Borg technology!
>> >>>
>> >>> Nux!
>> >>> www.nux.ro
>> >>>
>> >>> ----- Original Message -----
>> >>>> From: "Mike Tutkowski" <mi...@solidfire.com>
>> >>>> To: dev@cloudstack.apache.org
>> >>>> Cc: "Brian Federle" <Br...@citrix.com>
>> >>>> Sent: Saturday, 29 November, 2014 00:48:03
>> >>>> Subject: Re: root resize support in the UI
>> >>>
>> >>>> Well...I don't know...we kind of have features all over the place
>> >>>> that work for one hypervisor and not for another.
>> >>>>
>> >>>> If we're cool with that approach, this would be just one more area
>> >>>> where we have this kind of hypervisor-specific behavior (perhaps
>> >>>> all hypervisors support such an action in the future).
>> >>>>
>> >>>> On Fri, Nov 28, 2014 at 5:41 PM, Nux! <nu...@li.nux.ro> wrote:
>> >>>>
>> >>>>> Was thinking to just patch my local installation. Devs might not
>> >>>>> go too crazy over this idea since root resize is not supported
>> >>>>> across all hypervisors (KVM only atm).
>> >>>>>
>> >>>>> But if you think this has a chance to go official, I will open an
>> issue.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> Lucian
>> >>>>>
>> >>>>> --
>> >>>>> Sent from the Delta quadrant using Borg technology!
>> >>>>>
>> >>>>> Nux!
>> >>>>> www.nux.ro
>> >>>>>
>> >>>>> ----- Original Message -----
>> >>>>> > From: "Mike Tutkowski" <mi...@solidfire.com>
>> >>>>> > To: dev@cloudstack.apache.org, "Brian Federle"
>> >>>>> > <Brian.Federle@citrix.com
>> >>>>> >
>> >>>>> > Sent: Saturday, 29 November, 2014 00:27:14
>> >>>>> > Subject: Re: root resize support in the UI
>> >>>>>
>> >>>>> > Have you logged a JIRA ticket for this?
>> >>>>> >
>> >>>>> > Maybe Brian or one of the GUI people could pick up on it.
>> >>>>> >
>> >>>>> > On Fri, Nov 28, 2014 at 4:32 PM, Nux! <nu...@li.nux.ro> wrote:
>> >>>>> >
>> >>>>> >> Yeah, I was thinking of that, if it works for DATA, it should
>> >>>>> >> work for ROOT. But I am not a dev.
>> >>>>> >>
>> >>>>> >> Thoughts?
>> >>>>> >>
>> >>>>> >> --
>> >>>>> >> Sent from the Delta quadrant using Borg technology!
>> >>>>> >>
>> >>>>> >> Nux!
>> >>>>> >> www.nux.ro
>> >>>>> >>
>> >>>>> >> ----- Original Message -----
>> >>>>> >> > From: "Mike Tutkowski" <mi...@solidfire.com>
>> >>>>> >> > To: dev@cloudstack.apache.org
>> >>>>> >> > Sent: Friday, 28 November, 2014 19:57:27
>> >>>>> >> > Subject: Re: root resize support in the UI
>> >>>>> >>
>> >>>>> >> > For root disks, is it possible to just follow the existing
>> >>>>> >> > resize
>> >>>>> pattern
>> >>>>> >> > we have established in the UI for data disks?
>> >>>>> >> >
>> >>>>> >> > On Friday, November 28, 2014, Nux! <nu...@li.nux.ro> wrote:
>> >>>>> >> >
>> >>>>> >> >> Hello,
>> >>>>> >> >>
>> >>>>> >> >> Wonder if someone can help me with the $subject.
>> >>>>> >> >>
>> >>>>> >> >> I remember at some point (4.2?) a new feature showed up
>> >>>>> >> >> accidentally
>> >>>>> in
>> >>>>> >> >> the UI instance creation dialogues, it was concerning "root
>> >>>>> >> >> size",
>> >>>>> had a
>> >>>>> >> >> small box where the number in GB would be introduced.
>> >>>>> >> >> I'd like to take advantage of that now that this feature
>> >>>>> >> >> actually
>> >>>>> works,
>> >>>>> >> >> even if only in KVM. I'd love it if someone could point me
>> >>>>> >> >> to that
>> >>>>> >> piece of
>> >>>>> >> >> code (prolly just javascript).
>> >>>>> >> >>
>> >>>>> >> >> In addition to that, now that root resize works, can any one
>> >>>>> >> >> suggest
>> >>>>> >> how I
>> >>>>> >> >> might put a "resize" button in the Volumes section for the
>> >>>>> >> >> ROOT
>> >>>>> disks?
>> >>>>> >> >>
>> >>>>> >> >> Lucian
>> >>>>> >> >>
>> >>>>> >> >> --
>> >>>>> >> >> Sent from the Delta quadrant using Borg technology!
>> >>>>> >> >>
>> >>>>> >> >> Nux!
>> >>>>> >> >> www.nux.ro
>> >>>>> >> >>
>> >>>>> >> >
>> >>>>> >> >
>> >>>>> >> > --
>> >>>>> >> > *Mike Tutkowski*
>> >>>>> >> > *Senior CloudStack Developer, SolidFire Inc.*
>> >>>>> >> > e: mike.tutkowski@solidfire.com
>> >>>>> >> > o: 303.746.7302
>> >>>>> >> > Advancing the way the world uses the cloud
>> >>>>> >> > <http://solidfire.com/solution/overview/?video=play>*™*
>> >>>>> >>
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> > --
>> >>>>> > *Mike Tutkowski*
>> >>>>> > *Senior CloudStack Developer, SolidFire Inc.*
>> >>>>> > e: mike.tutkowski@solidfire.com
>> >>>>> > o: 303.746.7302
>> >>>>> > Advancing the way the world uses the cloud
>> >>>>> > <http://solidfire.com/solution/overview/?video=play>*™*
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> *Mike Tutkowski*
>> >>>> *Senior CloudStack Developer, SolidFire Inc.*
>> >>>> e: mike.tutkowski@solidfire.com
>> >>>> o: 303.746.7302
>> >>>> Advancing the way the world uses the cloud
>> > > > > <http://solidfire.com/solution/overview/?video=play>*™*
>>
>
>
>
> --
>
> Andrija Panić
Re: root resize support in the UI
Posted by Andrija Panic <an...@gmail.com>.
Matheww, offtopic - keep in mind that hostbill will make milion of computer
offerings and everything, so if you login to cloudstack - you will get lost
- at least per my latest experience with hostbill. Also we were told that
they store credit cards in their database - something you might not want.
On 1 December 2014 at 17:57, Logan Barfield <lb...@tqhosting.com> wrote:
> Just chiming in: I un-commented the Root Disk field in the Instance Wizard
> in our 4.4 deployment. Works fine with KVM / Ceph RBD.
>
> The logic we see is:
> A) If specified size is smaller than template size, throw an alert.
> B) If specified size is larger than template size then deploy root disk
> with specified size.
> C) If nothing is specified (default if the box isn't enabled) then deploy
> root disk with same size as template.
>
> This works with KVM and the RBD resize logic I committed a few months ago.
> I can't speak for how it works with Xen/VMware or other primary storage
> backends.
>
>
> Thank You,
>
> Logan Barfield
> Tranquil Hosting
>
> On Mon, Dec 1, 2014 at 11:34 AM, Matthew Midgett <
> cloudstck@trick-solutions.com.invalid> wrote:
>
> > 1+ from me for XenServer root disk resize for template deployments!
> >
> > I'm going with Nux on the single partition scheme and I want my root disk
> > under 2GB as most all of my deployments are minimal systems. This makes
> the
> > journey from sec storage to primary storage quite a bit faster. I need to
> > deploy and resize and be running in under 60 seconds if possible to keep
> my
> > users from sitting around waiting.
> >
> > I will be using hostbill in front of my ACS and they offer these sliders
> > for choosing how much resources you want. Users really like this and if
> > they deploy my 2gb template I'd like to be able to give them that 50GB
> disk
> > they ask for without using a data disk.
> >
> > If cloud-init can do this then I as a user would develop my templates
> > around the file system layout that it supports. EXT3,EXT4,BTRFS or
> LVM....I
> > honestly don't care for using LVM in a Virtual Machine, it's just one
> more
> > layer of complexity on a disk that doesn’t need to be there. Most all
> Linux
> > file systems can support online resize without LVM so I would consider
> not
> > using it to simplify cloud-init resize.
> >
> > Just my 2cents
> >
> > Matthew Midgett
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Nux! [mailto:nux@li.nux.ro]
> > Sent: Monday, December 01, 2014 7:06 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: root resize support in the UI
> >
> > Andrija,
> >
> > Absolutely, everyone has their own needs.
> >
> > The single partition works best for us (we also implemented it in
> physical
> > dedicated servers - makes p2v and v2p easy!) and it also seems to be the
> > choice of others (official fedora/centos/ubuntu templates are like this
> as
> > well).
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > ----- Original Message -----
> > > From: "Andrija Panic" <an...@gmail.com>
> > > To: dev@cloudstack.apache.org
> > > Sent: Monday, 1 December, 2014 11:42:29
> > > Subject: Re: root resize support in the UI
> >
> > > ok, Nux, so you suggest, single partition layout, with some predefined
> > > usage scenario...that is definitively an option for me.
> > > On the other hand, if you have slightly complicated templates - then
> > > the only way I see is to only resize the disk qith qemu-img...(not
> > > going inside VM)...
> > >
> > > So we need to decide on the user-case scenario we find most usefull...
> > >
> > > On 1 December 2014 at 12:30, Nux! <nu...@li.nux.ro> wrote:
> > >
> > >> Vadim,
> > >>
> > >> Currently the ROOT resize feature is not available for hypervisors
> > >> other than KVM. The developers working with these HVs are not
> > >> interested in this feature a.t.m.
> > >> Feel free to request this feature and stress them out. :)
> > >>
> > >> Based on this feature I now only use 1 template with 1 single
> > >> partition in it mounted as / which cloud-init will expand to maximum
> > during deployment.
> > >> Self-resizing can also be done in Windows quite easily.
> > >> I don't think it's acceptable to tell customer to deal with expanding
> > >> the partition himself, so this is automated.
> > >>
> > >> I do not use swap, but when it is a "must" I use a file based swap
> > >> (eg /var/swap.IMG). You could use another primary storage for swap,
> > >> but IMHO this just complicated things and it's not worth it.
> > >> Generally I try not to use multiple volumes for a VM, it makes life
> > easier.
> > >>
> > >> HTH
> > >> Lucian
> > >>
> > >> --
> > >> Sent from the Delta quadrant using Borg technology!
> > >>
> > >> Nux!
> > >> www.nux.ro
> > >>
> > >> ----- Original Message -----
> > >> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> > >> > To: dev@cloudstack.apache.org
> > >> > Sent: Monday, 1 December, 2014 11:09:24
> > >> > Subject: RE: root resize support in the UI
> > >>
> > >> > Andrija,
> > >> >
> > >> > You did understand me correctly. I wish that for the
> > >> > customer
> > >> disk offer could
> > >> > be customizable. And not just for KVM hypervisor.
> > >> Particularly now I am
> > >> > interested in Xen and VmWare.
> > >> > CS admin should not have set of templates that differs only on root
> > >> partition
> > >> > size. Swap partition can be (theoretically) located as another
> > >> > DATA
> > >> disk and
> > >> > be re-sizable with existing functionality.
> > >> > How hard is to achieve such a requirement? Are these
> > >> requirements something
> > >> > unusual and I should do it other way? For example we say
> > >> > to
> > >> the customer, that
> > >> > you have unallocated space if you select different size
> > >> > and
> > >> extend partition by
> > >> > yourself?
> > >> >
> > >> > Vadim.
> > >> >
> > >> > -----Original Message-----
> > >> > From: Andrija Panic [mailto:andrija.panic@gmail.com]
> > >> > Sent: Monday, December 01, 2014 12:06 PM
> > >> > To: dev@cloudstack.apache.org
> > >> > Subject: Re: root resize support in the UI
> > >> >
> > >> > Vadim, not sure if I understand corrrectly - but you have i.e. 10GB
> > >> template.
> > >> > you provision new VM with different size i.e. 50GB, and then after
> > >> > the
> > >> instance
> > >> > is UP and running - there is just 40GB of additional unalocated
> > >> > space
> > >> inside
> > >> > VM/disk, so admin need to resize partition and resize FS... ?
> > >> >
> > >> > I have been manually using qemu-img to resize some volumes (update
> > >> > the
> > >> size
> > >> > inside DB) and then boot VM and do "inside VM" work of resizing
> > stuff...
> > >> >
> > >> > If we only increase disk by qemu-img and update the DB - than no
> > >> > more admin-manual hacks needed - and we have consistent solution,
> > >> > that works
> > >> across
> > >> > all platforms.
> > >> >
> > >> > And to support resize inside differente OS-es by ACS (partitions
> > >> > and
> > >> FS) -
> > >> > seems pretty impossible for me, except for basic templates that
> > >> > have 1 partition, and i.e. no swap partition, etc...we loose
> > >> > consistency here completely...
> > >> >
> > >> >
> > >> > On 1 December 2014 at 10:33, Vadim Kimlaychuk
> > >> > <Vadim.Kimlaychuk@elion.ee
> > >> >
> > >> > wrote:
> > >> >
> > >> >> But that means user can not create desired volume during instance
> > >> set-up.
> > >> >> If we would like to have, for example, VM with disk offers from
> > >> >> 5-100Gb I need to create dozen of same templates that differ only
> > >> >> at
> > >> root size.
> > >> >>
> > >> >> Vadim.
> > >> >>
> > >> >> -----Original Message-----
> > >> >> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> > >> >> Sent: Monday, December 01, 2014 11:06 AM
> > >> >> To: dev@cloudstack.apache.org
> > >> >> Subject: Re: root resize support in the UI
> > >> >>
> > >> >> Exactly, there may be more than 1 partion on that 1 drive.. So
> > >> >> just increase disk size, and let administaror handle the "inside
> > >> >> VM" job
> > >> >>
> > >> >> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com>
> wrote:
> > >> >>
> > >> >> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> > >> >> > Vadim.Kimlaychuk@elion.ee>
> > >> >> > wrote:
> > >> >> >
> > >> >> > > I have done root partition resize under XenServer exactly as
> > >> >> > > you
> > >> >> > described
> > >> >> > > - resized drive and then using system tools on guest VM like
> > >> >> > > fdisk, lvextend and ext2resize changed the size of the root.
> > >> >> > > It seems that
> > >> >> > drive
> > >> >> > > resize on hypervisor level is all that is needed, because it
> > >> >> > > is far too complicated for hypervisor to be aware of all
> > >> >> > > different types of
> > >> >> > partition
> > >> >> > > layouts and file systems that might exist. Then upper layer
> > >> >> > > (like
> > >> >> > > CS) may take role of implementing different actions according
> > >> >> > > to guest type and file system that have being used for
> > >> >> > > particular guest. While OS type can be taken from template,
> > >> >> > > FS type and partition type is information that is not stored in
> > the database.
> > >> >> Without it implementation is not feasible.
> > >> >> > >
> > >> >> >
> > >> >> > It's not given that you want to resize a partition or which one,
> > >> >> > just because you resize the disk.
> > >> >> >
> > >> >> > Thus it's not feasible to assume that the orchestration layer
> > >> >> > should be capable of doing it.
> > >> >> >
> > >> >> > --
> > >> >> > Erik
> > >> >> >
> > >> >>
> > >> >>
> > >> >>
> > >> >> --
> > >> >>
> > >> >> Andrija Panić
> > >> >>
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > Andrija Panić
> > >>
> > >
> > >
> > >
> > > --
> > >
> > > Andrija Panić
> >
> >
>
--
Andrija Panić
Re: root resize support in the UI
Posted by Logan Barfield <lb...@tqhosting.com>.
Just chiming in: I un-commented the Root Disk field in the Instance Wizard
in our 4.4 deployment. Works fine with KVM / Ceph RBD.
The logic we see is:
A) If specified size is smaller than template size, throw an alert.
B) If specified size is larger than template size then deploy root disk
with specified size.
C) If nothing is specified (default if the box isn't enabled) then deploy
root disk with same size as template.
This works with KVM and the RBD resize logic I committed a few months ago.
I can't speak for how it works with Xen/VMware or other primary storage
backends.
Thank You,
Logan Barfield
Tranquil Hosting
On Mon, Dec 1, 2014 at 11:34 AM, Matthew Midgett <
cloudstck@trick-solutions.com.invalid> wrote:
> 1+ from me for XenServer root disk resize for template deployments!
>
> I'm going with Nux on the single partition scheme and I want my root disk
> under 2GB as most all of my deployments are minimal systems. This makes the
> journey from sec storage to primary storage quite a bit faster. I need to
> deploy and resize and be running in under 60 seconds if possible to keep my
> users from sitting around waiting.
>
> I will be using hostbill in front of my ACS and they offer these sliders
> for choosing how much resources you want. Users really like this and if
> they deploy my 2gb template I'd like to be able to give them that 50GB disk
> they ask for without using a data disk.
>
> If cloud-init can do this then I as a user would develop my templates
> around the file system layout that it supports. EXT3,EXT4,BTRFS or LVM....I
> honestly don't care for using LVM in a Virtual Machine, it's just one more
> layer of complexity on a disk that doesn’t need to be there. Most all Linux
> file systems can support online resize without LVM so I would consider not
> using it to simplify cloud-init resize.
>
> Just my 2cents
>
> Matthew Midgett
>
>
>
>
>
> -----Original Message-----
> From: Nux! [mailto:nux@li.nux.ro]
> Sent: Monday, December 01, 2014 7:06 AM
> To: dev@cloudstack.apache.org
> Subject: Re: root resize support in the UI
>
> Andrija,
>
> Absolutely, everyone has their own needs.
>
> The single partition works best for us (we also implemented it in physical
> dedicated servers - makes p2v and v2p easy!) and it also seems to be the
> choice of others (official fedora/centos/ubuntu templates are like this as
> well).
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Andrija Panic" <an...@gmail.com>
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 1 December, 2014 11:42:29
> > Subject: Re: root resize support in the UI
>
> > ok, Nux, so you suggest, single partition layout, with some predefined
> > usage scenario...that is definitively an option for me.
> > On the other hand, if you have slightly complicated templates - then
> > the only way I see is to only resize the disk qith qemu-img...(not
> > going inside VM)...
> >
> > So we need to decide on the user-case scenario we find most usefull...
> >
> > On 1 December 2014 at 12:30, Nux! <nu...@li.nux.ro> wrote:
> >
> >> Vadim,
> >>
> >> Currently the ROOT resize feature is not available for hypervisors
> >> other than KVM. The developers working with these HVs are not
> >> interested in this feature a.t.m.
> >> Feel free to request this feature and stress them out. :)
> >>
> >> Based on this feature I now only use 1 template with 1 single
> >> partition in it mounted as / which cloud-init will expand to maximum
> during deployment.
> >> Self-resizing can also be done in Windows quite easily.
> >> I don't think it's acceptable to tell customer to deal with expanding
> >> the partition himself, so this is automated.
> >>
> >> I do not use swap, but when it is a "must" I use a file based swap
> >> (eg /var/swap.IMG). You could use another primary storage for swap,
> >> but IMHO this just complicated things and it's not worth it.
> >> Generally I try not to use multiple volumes for a VM, it makes life
> easier.
> >>
> >> HTH
> >> Lucian
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> ----- Original Message -----
> >> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> >> > To: dev@cloudstack.apache.org
> >> > Sent: Monday, 1 December, 2014 11:09:24
> >> > Subject: RE: root resize support in the UI
> >>
> >> > Andrija,
> >> >
> >> > You did understand me correctly. I wish that for the
> >> > customer
> >> disk offer could
> >> > be customizable. And not just for KVM hypervisor.
> >> Particularly now I am
> >> > interested in Xen and VmWare.
> >> > CS admin should not have set of templates that differs only on root
> >> partition
> >> > size. Swap partition can be (theoretically) located as another
> >> > DATA
> >> disk and
> >> > be re-sizable with existing functionality.
> >> > How hard is to achieve such a requirement? Are these
> >> requirements something
> >> > unusual and I should do it other way? For example we say
> >> > to
> >> the customer, that
> >> > you have unallocated space if you select different size
> >> > and
> >> extend partition by
> >> > yourself?
> >> >
> >> > Vadim.
> >> >
> >> > -----Original Message-----
> >> > From: Andrija Panic [mailto:andrija.panic@gmail.com]
> >> > Sent: Monday, December 01, 2014 12:06 PM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: root resize support in the UI
> >> >
> >> > Vadim, not sure if I understand corrrectly - but you have i.e. 10GB
> >> template.
> >> > you provision new VM with different size i.e. 50GB, and then after
> >> > the
> >> instance
> >> > is UP and running - there is just 40GB of additional unalocated
> >> > space
> >> inside
> >> > VM/disk, so admin need to resize partition and resize FS... ?
> >> >
> >> > I have been manually using qemu-img to resize some volumes (update
> >> > the
> >> size
> >> > inside DB) and then boot VM and do "inside VM" work of resizing
> stuff...
> >> >
> >> > If we only increase disk by qemu-img and update the DB - than no
> >> > more admin-manual hacks needed - and we have consistent solution,
> >> > that works
> >> across
> >> > all platforms.
> >> >
> >> > And to support resize inside differente OS-es by ACS (partitions
> >> > and
> >> FS) -
> >> > seems pretty impossible for me, except for basic templates that
> >> > have 1 partition, and i.e. no swap partition, etc...we loose
> >> > consistency here completely...
> >> >
> >> >
> >> > On 1 December 2014 at 10:33, Vadim Kimlaychuk
> >> > <Vadim.Kimlaychuk@elion.ee
> >> >
> >> > wrote:
> >> >
> >> >> But that means user can not create desired volume during instance
> >> set-up.
> >> >> If we would like to have, for example, VM with disk offers from
> >> >> 5-100Gb I need to create dozen of same templates that differ only
> >> >> at
> >> root size.
> >> >>
> >> >> Vadim.
> >> >>
> >> >> -----Original Message-----
> >> >> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> >> >> Sent: Monday, December 01, 2014 11:06 AM
> >> >> To: dev@cloudstack.apache.org
> >> >> Subject: Re: root resize support in the UI
> >> >>
> >> >> Exactly, there may be more than 1 partion on that 1 drive.. So
> >> >> just increase disk size, and let administaror handle the "inside
> >> >> VM" job
> >> >>
> >> >> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
> >> >>
> >> >> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> >> >> > Vadim.Kimlaychuk@elion.ee>
> >> >> > wrote:
> >> >> >
> >> >> > > I have done root partition resize under XenServer exactly as
> >> >> > > you
> >> >> > described
> >> >> > > - resized drive and then using system tools on guest VM like
> >> >> > > fdisk, lvextend and ext2resize changed the size of the root.
> >> >> > > It seems that
> >> >> > drive
> >> >> > > resize on hypervisor level is all that is needed, because it
> >> >> > > is far too complicated for hypervisor to be aware of all
> >> >> > > different types of
> >> >> > partition
> >> >> > > layouts and file systems that might exist. Then upper layer
> >> >> > > (like
> >> >> > > CS) may take role of implementing different actions according
> >> >> > > to guest type and file system that have being used for
> >> >> > > particular guest. While OS type can be taken from template,
> >> >> > > FS type and partition type is information that is not stored in
> the database.
> >> >> Without it implementation is not feasible.
> >> >> > >
> >> >> >
> >> >> > It's not given that you want to resize a partition or which one,
> >> >> > just because you resize the disk.
> >> >> >
> >> >> > Thus it's not feasible to assume that the orchestration layer
> >> >> > should be capable of doing it.
> >> >> >
> >> >> > --
> >> >> > Erik
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> Andrija Panić
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Andrija Panić
> >>
> >
> >
> >
> > --
> >
> > Andrija Panić
>
>
RE: root resize support in the UI
Posted by Matthew Midgett <cl...@trick-solutions.com.INVALID>.
1+ from me for XenServer root disk resize for template deployments!
I'm going with Nux on the single partition scheme and I want my root disk under 2GB as most all of my deployments are minimal systems. This makes the journey from sec storage to primary storage quite a bit faster. I need to deploy and resize and be running in under 60 seconds if possible to keep my users from sitting around waiting.
I will be using hostbill in front of my ACS and they offer these sliders for choosing how much resources you want. Users really like this and if they deploy my 2gb template I'd like to be able to give them that 50GB disk they ask for without using a data disk.
If cloud-init can do this then I as a user would develop my templates around the file system layout that it supports. EXT3,EXT4,BTRFS or LVM....I honestly don't care for using LVM in a Virtual Machine, it's just one more layer of complexity on a disk that doesn’t need to be there. Most all Linux file systems can support online resize without LVM so I would consider not using it to simplify cloud-init resize.
Just my 2cents
Matthew Midgett
-----Original Message-----
From: Nux! [mailto:nux@li.nux.ro]
Sent: Monday, December 01, 2014 7:06 AM
To: dev@cloudstack.apache.org
Subject: Re: root resize support in the UI
Andrija,
Absolutely, everyone has their own needs.
The single partition works best for us (we also implemented it in physical dedicated servers - makes p2v and v2p easy!) and it also seems to be the choice of others (official fedora/centos/ubuntu templates are like this as well).
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Andrija Panic" <an...@gmail.com>
> To: dev@cloudstack.apache.org
> Sent: Monday, 1 December, 2014 11:42:29
> Subject: Re: root resize support in the UI
> ok, Nux, so you suggest, single partition layout, with some predefined
> usage scenario...that is definitively an option for me.
> On the other hand, if you have slightly complicated templates - then
> the only way I see is to only resize the disk qith qemu-img...(not
> going inside VM)...
>
> So we need to decide on the user-case scenario we find most usefull...
>
> On 1 December 2014 at 12:30, Nux! <nu...@li.nux.ro> wrote:
>
>> Vadim,
>>
>> Currently the ROOT resize feature is not available for hypervisors
>> other than KVM. The developers working with these HVs are not
>> interested in this feature a.t.m.
>> Feel free to request this feature and stress them out. :)
>>
>> Based on this feature I now only use 1 template with 1 single
>> partition in it mounted as / which cloud-init will expand to maximum during deployment.
>> Self-resizing can also be done in Windows quite easily.
>> I don't think it's acceptable to tell customer to deal with expanding
>> the partition himself, so this is automated.
>>
>> I do not use swap, but when it is a "must" I use a file based swap
>> (eg /var/swap.IMG). You could use another primary storage for swap,
>> but IMHO this just complicated things and it's not worth it.
>> Generally I try not to use multiple volumes for a VM, it makes life easier.
>>
>> HTH
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Original Message -----
>> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
>> > To: dev@cloudstack.apache.org
>> > Sent: Monday, 1 December, 2014 11:09:24
>> > Subject: RE: root resize support in the UI
>>
>> > Andrija,
>> >
>> > You did understand me correctly. I wish that for the
>> > customer
>> disk offer could
>> > be customizable. And not just for KVM hypervisor.
>> Particularly now I am
>> > interested in Xen and VmWare.
>> > CS admin should not have set of templates that differs only on root
>> partition
>> > size. Swap partition can be (theoretically) located as another
>> > DATA
>> disk and
>> > be re-sizable with existing functionality.
>> > How hard is to achieve such a requirement? Are these
>> requirements something
>> > unusual and I should do it other way? For example we say
>> > to
>> the customer, that
>> > you have unallocated space if you select different size
>> > and
>> extend partition by
>> > yourself?
>> >
>> > Vadim.
>> >
>> > -----Original Message-----
>> > From: Andrija Panic [mailto:andrija.panic@gmail.com]
>> > Sent: Monday, December 01, 2014 12:06 PM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: root resize support in the UI
>> >
>> > Vadim, not sure if I understand corrrectly - but you have i.e. 10GB
>> template.
>> > you provision new VM with different size i.e. 50GB, and then after
>> > the
>> instance
>> > is UP and running - there is just 40GB of additional unalocated
>> > space
>> inside
>> > VM/disk, so admin need to resize partition and resize FS... ?
>> >
>> > I have been manually using qemu-img to resize some volumes (update
>> > the
>> size
>> > inside DB) and then boot VM and do "inside VM" work of resizing stuff...
>> >
>> > If we only increase disk by qemu-img and update the DB - than no
>> > more admin-manual hacks needed - and we have consistent solution,
>> > that works
>> across
>> > all platforms.
>> >
>> > And to support resize inside differente OS-es by ACS (partitions
>> > and
>> FS) -
>> > seems pretty impossible for me, except for basic templates that
>> > have 1 partition, and i.e. no swap partition, etc...we loose
>> > consistency here completely...
>> >
>> >
>> > On 1 December 2014 at 10:33, Vadim Kimlaychuk
>> > <Vadim.Kimlaychuk@elion.ee
>> >
>> > wrote:
>> >
>> >> But that means user can not create desired volume during instance
>> set-up.
>> >> If we would like to have, for example, VM with disk offers from
>> >> 5-100Gb I need to create dozen of same templates that differ only
>> >> at
>> root size.
>> >>
>> >> Vadim.
>> >>
>> >> -----Original Message-----
>> >> From: Andrija Panic [mailto:andrija.panic@gmail.com]
>> >> Sent: Monday, December 01, 2014 11:06 AM
>> >> To: dev@cloudstack.apache.org
>> >> Subject: Re: root resize support in the UI
>> >>
>> >> Exactly, there may be more than 1 partion on that 1 drive.. So
>> >> just increase disk size, and let administaror handle the "inside
>> >> VM" job
>> >>
>> >> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
>> >>
>> >> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
>> >> > Vadim.Kimlaychuk@elion.ee>
>> >> > wrote:
>> >> >
>> >> > > I have done root partition resize under XenServer exactly as
>> >> > > you
>> >> > described
>> >> > > - resized drive and then using system tools on guest VM like
>> >> > > fdisk, lvextend and ext2resize changed the size of the root.
>> >> > > It seems that
>> >> > drive
>> >> > > resize on hypervisor level is all that is needed, because it
>> >> > > is far too complicated for hypervisor to be aware of all
>> >> > > different types of
>> >> > partition
>> >> > > layouts and file systems that might exist. Then upper layer
>> >> > > (like
>> >> > > CS) may take role of implementing different actions according
>> >> > > to guest type and file system that have being used for
>> >> > > particular guest. While OS type can be taken from template,
>> >> > > FS type and partition type is information that is not stored in the database.
>> >> Without it implementation is not feasible.
>> >> > >
>> >> >
>> >> > It's not given that you want to resize a partition or which one,
>> >> > just because you resize the disk.
>> >> >
>> >> > Thus it's not feasible to assume that the orchestration layer
>> >> > should be capable of doing it.
>> >> >
>> >> > --
>> >> > Erik
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Andrija Panić
>> >>
>> >
>> >
>> >
>> > --
>> >
>> > Andrija Panić
>>
>
>
>
> --
>
> Andrija Panić
Re: root resize support in the UI
Posted by Nux! <nu...@li.nux.ro>.
Andrija,
Absolutely, everyone has their own needs.
The single partition works best for us (we also implemented it in physical dedicated servers - makes p2v and v2p easy!) and it also seems to be the choice of others (official fedora/centos/ubuntu templates are like this as well).
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Andrija Panic" <an...@gmail.com>
> To: dev@cloudstack.apache.org
> Sent: Monday, 1 December, 2014 11:42:29
> Subject: Re: root resize support in the UI
> ok, Nux, so you suggest, single partition layout, with some predefined
> usage scenario...that is definitively an option for me.
> On the other hand, if you have slightly complicated templates - then the
> only way I see is to only resize the disk qith qemu-img...(not going inside
> VM)...
>
> So we need to decide on the user-case scenario we find most usefull...
>
> On 1 December 2014 at 12:30, Nux! <nu...@li.nux.ro> wrote:
>
>> Vadim,
>>
>> Currently the ROOT resize feature is not available for hypervisors other
>> than KVM. The developers working with these HVs are not interested in this
>> feature a.t.m.
>> Feel free to request this feature and stress them out. :)
>>
>> Based on this feature I now only use 1 template with 1 single partition in
>> it mounted as / which cloud-init will expand to maximum during deployment.
>> Self-resizing can also be done in Windows quite easily.
>> I don't think it's acceptable to tell customer to deal with expanding the
>> partition himself, so this is automated.
>>
>> I do not use swap, but when it is a "must" I use a file based swap (eg
>> /var/swap.IMG). You could use another primary storage for swap, but IMHO
>> this just complicated things and it's not worth it.
>> Generally I try not to use multiple volumes for a VM, it makes life easier.
>>
>> HTH
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Original Message -----
>> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
>> > To: dev@cloudstack.apache.org
>> > Sent: Monday, 1 December, 2014 11:09:24
>> > Subject: RE: root resize support in the UI
>>
>> > Andrija,
>> >
>> > You did understand me correctly. I wish that for the customer
>> disk offer could
>> > be customizable. And not just for KVM hypervisor.
>> Particularly now I am
>> > interested in Xen and VmWare.
>> > CS admin should not have set of templates that differs only on root
>> partition
>> > size. Swap partition can be (theoretically) located as another DATA
>> disk and
>> > be re-sizable with existing functionality.
>> > How hard is to achieve such a requirement? Are these
>> requirements something
>> > unusual and I should do it other way? For example we say to
>> the customer, that
>> > you have unallocated space if you select different size and
>> extend partition by
>> > yourself?
>> >
>> > Vadim.
>> >
>> > -----Original Message-----
>> > From: Andrija Panic [mailto:andrija.panic@gmail.com]
>> > Sent: Monday, December 01, 2014 12:06 PM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: root resize support in the UI
>> >
>> > Vadim, not sure if I understand corrrectly - but you have i.e. 10GB
>> template.
>> > you provision new VM with different size i.e. 50GB, and then after the
>> instance
>> > is UP and running - there is just 40GB of additional unalocated space
>> inside
>> > VM/disk, so admin need to resize partition and resize FS... ?
>> >
>> > I have been manually using qemu-img to resize some volumes (update the
>> size
>> > inside DB) and then boot VM and do "inside VM" work of resizing stuff...
>> >
>> > If we only increase disk by qemu-img and update the DB - than no more
>> > admin-manual hacks needed - and we have consistent solution, that works
>> across
>> > all platforms.
>> >
>> > And to support resize inside differente OS-es by ACS (partitions and
>> FS) -
>> > seems pretty impossible for me, except for basic templates that have 1
>> > partition, and i.e. no swap partition, etc...we loose consistency here
>> > completely...
>> >
>> >
>> > On 1 December 2014 at 10:33, Vadim Kimlaychuk <Vadim.Kimlaychuk@elion.ee
>> >
>> > wrote:
>> >
>> >> But that means user can not create desired volume during instance
>> set-up.
>> >> If we would like to have, for example, VM with disk offers from
>> >> 5-100Gb I need to create dozen of same templates that differ only at
>> root size.
>> >>
>> >> Vadim.
>> >>
>> >> -----Original Message-----
>> >> From: Andrija Panic [mailto:andrija.panic@gmail.com]
>> >> Sent: Monday, December 01, 2014 11:06 AM
>> >> To: dev@cloudstack.apache.org
>> >> Subject: Re: root resize support in the UI
>> >>
>> >> Exactly, there may be more than 1 partion on that 1 drive.. So just
>> >> increase disk size, and let administaror handle the "inside VM" job
>> >>
>> >> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
>> >>
>> >> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
>> >> > Vadim.Kimlaychuk@elion.ee>
>> >> > wrote:
>> >> >
>> >> > > I have done root partition resize under XenServer exactly as you
>> >> > described
>> >> > > - resized drive and then using system tools on guest VM like
>> >> > > fdisk, lvextend and ext2resize changed the size of the root. It
>> >> > > seems that
>> >> > drive
>> >> > > resize on hypervisor level is all that is needed, because it is
>> >> > > far too complicated for hypervisor to be aware of all different
>> >> > > types of
>> >> > partition
>> >> > > layouts and file systems that might exist. Then upper layer (like
>> >> > > CS) may take role of implementing different actions according to
>> >> > > guest type and file system that have being used for particular
>> >> > > guest. While OS type can be taken from template, FS type and
>> >> > > partition type is information that is not stored in the database.
>> >> Without it implementation is not feasible.
>> >> > >
>> >> >
>> >> > It's not given that you want to resize a partition or which one,
>> >> > just because you resize the disk.
>> >> >
>> >> > Thus it's not feasible to assume that the orchestration layer should
>> >> > be capable of doing it.
>> >> >
>> >> > --
>> >> > Erik
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Andrija Panić
>> >>
>> >
>> >
>> >
>> > --
>> >
>> > Andrija Panić
>>
>
>
>
> --
>
> Andrija Panić
Re: root resize support in the UI
Posted by Todd Pigram <to...@toddpigram.com>.
I would like to see this for XenServer implemented. I get around this by
having all my bare bone templates at 100GB...it would be nice not have to
change in the DB, then catch it in from the console to expand before CS
shuts it down.
On Mon, Dec 1, 2014 at 6:30 AM, Nux! <nu...@li.nux.ro> wrote:
> Vadim,
>
> Currently the ROOT resize feature is not available for hypervisors other
> than KVM. The developers working with these HVs are not interested in this
> feature a.t.m.
> Feel free to request this feature and stress them out. :)
>
> Based on this feature I now only use 1 template with 1 single partition in
> it mounted as / which cloud-init will expand to maximum during deployment.
> Self-resizing can also be done in Windows quite easily.
> I don't think it's acceptable to tell customer to deal with expanding the
> partition himself, so this is automated.
>
> I do not use swap, but when it is a "must" I use a file based swap (eg
> /var/swap.IMG). You could use another primary storage for swap, but IMHO
> this just complicated things and it's not worth it.
> Generally I try not to use multiple volumes for a VM, it makes life easier.
>
> HTH
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 1 December, 2014 11:09:24
> > Subject: RE: root resize support in the UI
>
> > Andrija,
> >
> > You did understand me correctly. I wish that for the customer
> disk offer could
> > be customizable. And not just for KVM hypervisor.
> Particularly now I am
> > interested in Xen and VmWare.
> > CS admin should not have set of templates that differs only on root
> partition
> > size. Swap partition can be (theoretically) located as another DATA
> disk and
> > be re-sizable with existing functionality.
> > How hard is to achieve such a requirement? Are these
> requirements something
> > unusual and I should do it other way? For example we say to
> the customer, that
> > you have unallocated space if you select different size and
> extend partition by
> > yourself?
> >
> > Vadim.
> >
> > -----Original Message-----
> > From: Andrija Panic [mailto:andrija.panic@gmail.com]
> > Sent: Monday, December 01, 2014 12:06 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: root resize support in the UI
> >
> > Vadim, not sure if I understand corrrectly - but you have i.e. 10GB
> template.
> > you provision new VM with different size i.e. 50GB, and then after the
> instance
> > is UP and running - there is just 40GB of additional unalocated space
> inside
> > VM/disk, so admin need to resize partition and resize FS... ?
> >
> > I have been manually using qemu-img to resize some volumes (update the
> size
> > inside DB) and then boot VM and do "inside VM" work of resizing stuff...
> >
> > If we only increase disk by qemu-img and update the DB - than no more
> > admin-manual hacks needed - and we have consistent solution, that works
> across
> > all platforms.
> >
> > And to support resize inside differente OS-es by ACS (partitions and
> FS) -
> > seems pretty impossible for me, except for basic templates that have 1
> > partition, and i.e. no swap partition, etc...we loose consistency here
> > completely...
> >
> >
> > On 1 December 2014 at 10:33, Vadim Kimlaychuk <Vadim.Kimlaychuk@elion.ee
> >
> > wrote:
> >
> >> But that means user can not create desired volume during instance
> set-up.
> >> If we would like to have, for example, VM with disk offers from
> >> 5-100Gb I need to create dozen of same templates that differ only at
> root size.
> >>
> >> Vadim.
> >>
> >> -----Original Message-----
> >> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> >> Sent: Monday, December 01, 2014 11:06 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: root resize support in the UI
> >>
> >> Exactly, there may be more than 1 partion on that 1 drive.. So just
> >> increase disk size, and let administaror handle the "inside VM" job
> >>
> >> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
> >>
> >> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> >> > Vadim.Kimlaychuk@elion.ee>
> >> > wrote:
> >> >
> >> > > I have done root partition resize under XenServer exactly as you
> >> > described
> >> > > - resized drive and then using system tools on guest VM like
> >> > > fdisk, lvextend and ext2resize changed the size of the root. It
> >> > > seems that
> >> > drive
> >> > > resize on hypervisor level is all that is needed, because it is
> >> > > far too complicated for hypervisor to be aware of all different
> >> > > types of
> >> > partition
> >> > > layouts and file systems that might exist. Then upper layer (like
> >> > > CS) may take role of implementing different actions according to
> >> > > guest type and file system that have being used for particular
> >> > > guest. While OS type can be taken from template, FS type and
> >> > > partition type is information that is not stored in the database.
> >> Without it implementation is not feasible.
> >> > >
> >> >
> >> > It's not given that you want to resize a partition or which one,
> >> > just because you resize the disk.
> >> >
> >> > Thus it's not feasible to assume that the orchestration layer should
> >> > be capable of doing it.
> >> >
> >> > --
> >> > Erik
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Andrija Panić
> >>
> >
> >
> >
> > --
> >
> > Andrija Panić
>
--
Todd Pigram
http://about.me/ToddPigram
www.linkedin.com/in/toddpigram/
@pigram86 on twitter
https://plus.google.com/+ToddPigram86
Mobile - 216-224-5769
Re: root resize support in the UI
Posted by Andrija Panic <an...@gmail.com>.
ok, Nux, so you suggest, single partition layout, with some predefined
usage scenario...that is definitively an option for me.
On the other hand, if you have slightly complicated templates - then the
only way I see is to only resize the disk qith qemu-img...(not going inside
VM)...
So we need to decide on the user-case scenario we find most usefull...
On 1 December 2014 at 12:30, Nux! <nu...@li.nux.ro> wrote:
> Vadim,
>
> Currently the ROOT resize feature is not available for hypervisors other
> than KVM. The developers working with these HVs are not interested in this
> feature a.t.m.
> Feel free to request this feature and stress them out. :)
>
> Based on this feature I now only use 1 template with 1 single partition in
> it mounted as / which cloud-init will expand to maximum during deployment.
> Self-resizing can also be done in Windows quite easily.
> I don't think it's acceptable to tell customer to deal with expanding the
> partition himself, so this is automated.
>
> I do not use swap, but when it is a "must" I use a file based swap (eg
> /var/swap.IMG). You could use another primary storage for swap, but IMHO
> this just complicated things and it's not worth it.
> Generally I try not to use multiple volumes for a VM, it makes life easier.
>
> HTH
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> > To: dev@cloudstack.apache.org
> > Sent: Monday, 1 December, 2014 11:09:24
> > Subject: RE: root resize support in the UI
>
> > Andrija,
> >
> > You did understand me correctly. I wish that for the customer
> disk offer could
> > be customizable. And not just for KVM hypervisor.
> Particularly now I am
> > interested in Xen and VmWare.
> > CS admin should not have set of templates that differs only on root
> partition
> > size. Swap partition can be (theoretically) located as another DATA
> disk and
> > be re-sizable with existing functionality.
> > How hard is to achieve such a requirement? Are these
> requirements something
> > unusual and I should do it other way? For example we say to
> the customer, that
> > you have unallocated space if you select different size and
> extend partition by
> > yourself?
> >
> > Vadim.
> >
> > -----Original Message-----
> > From: Andrija Panic [mailto:andrija.panic@gmail.com]
> > Sent: Monday, December 01, 2014 12:06 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: root resize support in the UI
> >
> > Vadim, not sure if I understand corrrectly - but you have i.e. 10GB
> template.
> > you provision new VM with different size i.e. 50GB, and then after the
> instance
> > is UP and running - there is just 40GB of additional unalocated space
> inside
> > VM/disk, so admin need to resize partition and resize FS... ?
> >
> > I have been manually using qemu-img to resize some volumes (update the
> size
> > inside DB) and then boot VM and do "inside VM" work of resizing stuff...
> >
> > If we only increase disk by qemu-img and update the DB - than no more
> > admin-manual hacks needed - and we have consistent solution, that works
> across
> > all platforms.
> >
> > And to support resize inside differente OS-es by ACS (partitions and
> FS) -
> > seems pretty impossible for me, except for basic templates that have 1
> > partition, and i.e. no swap partition, etc...we loose consistency here
> > completely...
> >
> >
> > On 1 December 2014 at 10:33, Vadim Kimlaychuk <Vadim.Kimlaychuk@elion.ee
> >
> > wrote:
> >
> >> But that means user can not create desired volume during instance
> set-up.
> >> If we would like to have, for example, VM with disk offers from
> >> 5-100Gb I need to create dozen of same templates that differ only at
> root size.
> >>
> >> Vadim.
> >>
> >> -----Original Message-----
> >> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> >> Sent: Monday, December 01, 2014 11:06 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: root resize support in the UI
> >>
> >> Exactly, there may be more than 1 partion on that 1 drive.. So just
> >> increase disk size, and let administaror handle the "inside VM" job
> >>
> >> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
> >>
> >> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> >> > Vadim.Kimlaychuk@elion.ee>
> >> > wrote:
> >> >
> >> > > I have done root partition resize under XenServer exactly as you
> >> > described
> >> > > - resized drive and then using system tools on guest VM like
> >> > > fdisk, lvextend and ext2resize changed the size of the root. It
> >> > > seems that
> >> > drive
> >> > > resize on hypervisor level is all that is needed, because it is
> >> > > far too complicated for hypervisor to be aware of all different
> >> > > types of
> >> > partition
> >> > > layouts and file systems that might exist. Then upper layer (like
> >> > > CS) may take role of implementing different actions according to
> >> > > guest type and file system that have being used for particular
> >> > > guest. While OS type can be taken from template, FS type and
> >> > > partition type is information that is not stored in the database.
> >> Without it implementation is not feasible.
> >> > >
> >> >
> >> > It's not given that you want to resize a partition or which one,
> >> > just because you resize the disk.
> >> >
> >> > Thus it's not feasible to assume that the orchestration layer should
> >> > be capable of doing it.
> >> >
> >> > --
> >> > Erik
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Andrija Panić
> >>
> >
> >
> >
> > --
> >
> > Andrija Panić
>
--
Andrija Panić
Re: root resize support in the UI
Posted by Nux! <nu...@li.nux.ro>.
Vadim,
Currently the ROOT resize feature is not available for hypervisors other than KVM. The developers working with these HVs are not interested in this feature a.t.m.
Feel free to request this feature and stress them out. :)
Based on this feature I now only use 1 template with 1 single partition in it mounted as / which cloud-init will expand to maximum during deployment. Self-resizing can also be done in Windows quite easily.
I don't think it's acceptable to tell customer to deal with expanding the partition himself, so this is automated.
I do not use swap, but when it is a "must" I use a file based swap (eg /var/swap.IMG). You could use another primary storage for swap, but IMHO this just complicated things and it's not worth it.
Generally I try not to use multiple volumes for a VM, it makes life easier.
HTH
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> To: dev@cloudstack.apache.org
> Sent: Monday, 1 December, 2014 11:09:24
> Subject: RE: root resize support in the UI
> Andrija,
>
> You did understand me correctly. I wish that for the customer disk offer could
> be customizable. And not just for KVM hypervisor. Particularly now I am
> interested in Xen and VmWare.
> CS admin should not have set of templates that differs only on root partition
> size. Swap partition can be (theoretically) located as another DATA disk and
> be re-sizable with existing functionality.
> How hard is to achieve such a requirement? Are these requirements something
> unusual and I should do it other way? For example we say to the customer, that
> you have unallocated space if you select different size and extend partition by
> yourself?
>
> Vadim.
>
> -----Original Message-----
> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> Sent: Monday, December 01, 2014 12:06 PM
> To: dev@cloudstack.apache.org
> Subject: Re: root resize support in the UI
>
> Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template.
> you provision new VM with different size i.e. 50GB, and then after the instance
> is UP and running - there is just 40GB of additional unalocated space inside
> VM/disk, so admin need to resize partition and resize FS... ?
>
> I have been manually using qemu-img to resize some volumes (update the size
> inside DB) and then boot VM and do "inside VM" work of resizing stuff...
>
> If we only increase disk by qemu-img and update the DB - than no more
> admin-manual hacks needed - and we have consistent solution, that works across
> all platforms.
>
> And to support resize inside differente OS-es by ACS (partitions and FS) -
> seems pretty impossible for me, except for basic templates that have 1
> partition, and i.e. no swap partition, etc...we loose consistency here
> completely...
>
>
> On 1 December 2014 at 10:33, Vadim Kimlaychuk <Va...@elion.ee>
> wrote:
>
>> But that means user can not create desired volume during instance set-up.
>> If we would like to have, for example, VM with disk offers from
>> 5-100Gb I need to create dozen of same templates that differ only at root size.
>>
>> Vadim.
>>
>> -----Original Message-----
>> From: Andrija Panic [mailto:andrija.panic@gmail.com]
>> Sent: Monday, December 01, 2014 11:06 AM
>> To: dev@cloudstack.apache.org
>> Subject: Re: root resize support in the UI
>>
>> Exactly, there may be more than 1 partion on that 1 drive.. So just
>> increase disk size, and let administaror handle the "inside VM" job
>>
>> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
>>
>> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
>> > Vadim.Kimlaychuk@elion.ee>
>> > wrote:
>> >
>> > > I have done root partition resize under XenServer exactly as you
>> > described
>> > > - resized drive and then using system tools on guest VM like
>> > > fdisk, lvextend and ext2resize changed the size of the root. It
>> > > seems that
>> > drive
>> > > resize on hypervisor level is all that is needed, because it is
>> > > far too complicated for hypervisor to be aware of all different
>> > > types of
>> > partition
>> > > layouts and file systems that might exist. Then upper layer (like
>> > > CS) may take role of implementing different actions according to
>> > > guest type and file system that have being used for particular
>> > > guest. While OS type can be taken from template, FS type and
>> > > partition type is information that is not stored in the database.
>> Without it implementation is not feasible.
>> > >
>> >
>> > It's not given that you want to resize a partition or which one,
>> > just because you resize the disk.
>> >
>> > Thus it's not feasible to assume that the orchestration layer should
>> > be capable of doing it.
>> >
>> > --
>> > Erik
>> >
>>
>>
>>
>> --
>>
>> Andrija Panić
>>
>
>
>
> --
>
> Andrija Panić
Re: root resize support in the UI
Posted by Erik Weber <te...@gmail.com>.
On Mon, Dec 1, 2014 at 12:09 PM, Vadim Kimlaychuk <Vadim.Kimlaychuk@elion.ee
> wrote:
> Andrija,
>
> You did understand me correctly. I wish that for the customer
> disk offer could be customizable. And not just for KVM hypervisor.
> Particularly now I am interested in Xen and VmWare.
> CS admin should not have set of templates that differs only on root
> partition size. Swap partition can be (theoretically) located as another
> DATA disk and be re-sizable with existing functionality.
> How hard is to achieve such a requirement? Are these
> requirements something unusual and I should do it other way? For example we
> say to the customer, that you have unallocated space if you select
> different size and extend partition by yourself?
>
It's not hard at all. You just need to find a developer that can spare the
time to implement it in CloudStack.
--
Erik
RE: root resize support in the UI
Posted by Vadim Kimlaychuk <Va...@Elion.ee>.
Andrija,
You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare.
CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality.
How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself?
Vadim.
-----Original Message-----
From: Andrija Panic [mailto:andrija.panic@gmail.com]
Sent: Monday, December 01, 2014 12:06 PM
To: dev@cloudstack.apache.org
Subject: Re: root resize support in the UI
Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template. you provision new VM with different size i.e. 50GB, and then after the instance is UP and running - there is just 40GB of additional unalocated space inside VM/disk, so admin need to resize partition and resize FS... ?
I have been manually using qemu-img to resize some volumes (update the size inside DB) and then boot VM and do "inside VM" work of resizing stuff...
If we only increase disk by qemu-img and update the DB - than no more admin-manual hacks needed - and we have consistent solution, that works across all platforms.
And to support resize inside differente OS-es by ACS (partitions and FS) - seems pretty impossible for me, except for basic templates that have 1 partition, and i.e. no swap partition, etc...we loose consistency here completely...
On 1 December 2014 at 10:33, Vadim Kimlaychuk <Va...@elion.ee>
wrote:
> But that means user can not create desired volume during instance set-up.
> If we would like to have, for example, VM with disk offers from
> 5-100Gb I need to create dozen of same templates that differ only at root size.
>
> Vadim.
>
> -----Original Message-----
> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> Sent: Monday, December 01, 2014 11:06 AM
> To: dev@cloudstack.apache.org
> Subject: Re: root resize support in the UI
>
> Exactly, there may be more than 1 partion on that 1 drive.. So just
> increase disk size, and let administaror handle the "inside VM" job
>
> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
>
> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> > Vadim.Kimlaychuk@elion.ee>
> > wrote:
> >
> > > I have done root partition resize under XenServer exactly as you
> > described
> > > - resized drive and then using system tools on guest VM like
> > > fdisk, lvextend and ext2resize changed the size of the root. It
> > > seems that
> > drive
> > > resize on hypervisor level is all that is needed, because it is
> > > far too complicated for hypervisor to be aware of all different
> > > types of
> > partition
> > > layouts and file systems that might exist. Then upper layer (like
> > > CS) may take role of implementing different actions according to
> > > guest type and file system that have being used for particular
> > > guest. While OS type can be taken from template, FS type and
> > > partition type is information that is not stored in the database.
> Without it implementation is not feasible.
> > >
> >
> > It's not given that you want to resize a partition or which one,
> > just because you resize the disk.
> >
> > Thus it's not feasible to assume that the orchestration layer should
> > be capable of doing it.
> >
> > --
> > Erik
> >
>
>
>
> --
>
> Andrija Panić
>
--
Andrija Panić
Re: root resize support in the UI
Posted by Andrija Panic <an...@gmail.com>.
Vadim, not sure if I understand corrrectly - but you have i.e. 10GB
template. you provision new VM with different size i.e. 50GB, and then
after the instance is UP and running - there is just 40GB of additional
unalocated space inside VM/disk, so admin need to resize partition and
resize FS... ?
I have been manually using qemu-img to resize some volumes (update the size
inside DB) and then boot VM and do "inside VM" work of resizing stuff...
If we only increase disk by qemu-img and update the DB - than no more
admin-manual hacks needed - and we have consistent solution, that works
across all platforms.
And to support resize inside differente OS-es by ACS (partitions and FS) -
seems pretty impossible for me, except for basic templates that have 1
partition, and i.e. no swap partition, etc...we loose consistency here
completely...
On 1 December 2014 at 10:33, Vadim Kimlaychuk <Va...@elion.ee>
wrote:
> But that means user can not create desired volume during instance set-up.
> If we would like to have, for example, VM with disk offers from 5-100Gb I
> need to create dozen of same templates that differ only at root size.
>
> Vadim.
>
> -----Original Message-----
> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> Sent: Monday, December 01, 2014 11:06 AM
> To: dev@cloudstack.apache.org
> Subject: Re: root resize support in the UI
>
> Exactly, there may be more than 1 partion on that 1 drive.. So just
> increase disk size, and let administaror handle the "inside VM" job
>
> On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
>
> > On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> > Vadim.Kimlaychuk@elion.ee>
> > wrote:
> >
> > > I have done root partition resize under XenServer exactly as you
> > described
> > > - resized drive and then using system tools on guest VM like fdisk,
> > > lvextend and ext2resize changed the size of the root. It seems that
> > drive
> > > resize on hypervisor level is all that is needed, because it is far
> > > too complicated for hypervisor to be aware of all different types of
> > partition
> > > layouts and file systems that might exist. Then upper layer (like
> > > CS) may take role of implementing different actions according to
> > > guest type and file system that have being used for particular
> > > guest. While OS type can be taken from template, FS type and
> > > partition type is information that is not stored in the database.
> Without it implementation is not feasible.
> > >
> >
> > It's not given that you want to resize a partition or which one, just
> > because you resize the disk.
> >
> > Thus it's not feasible to assume that the orchestration layer should
> > be capable of doing it.
> >
> > --
> > Erik
> >
>
>
>
> --
>
> Andrija Panić
>
--
Andrija Panić
RE: root resize support in the UI
Posted by Vadim Kimlaychuk <Va...@Elion.ee>.
But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size.
Vadim.
-----Original Message-----
From: Andrija Panic [mailto:andrija.panic@gmail.com]
Sent: Monday, December 01, 2014 11:06 AM
To: dev@cloudstack.apache.org
Subject: Re: root resize support in the UI
Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the "inside VM" job
On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
> On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> Vadim.Kimlaychuk@elion.ee>
> wrote:
>
> > I have done root partition resize under XenServer exactly as you
> described
> > - resized drive and then using system tools on guest VM like fdisk,
> > lvextend and ext2resize changed the size of the root. It seems that
> drive
> > resize on hypervisor level is all that is needed, because it is far
> > too complicated for hypervisor to be aware of all different types of
> partition
> > layouts and file systems that might exist. Then upper layer (like
> > CS) may take role of implementing different actions according to
> > guest type and file system that have being used for particular
> > guest. While OS type can be taken from template, FS type and
> > partition type is information that is not stored in the database. Without it implementation is not feasible.
> >
>
> It's not given that you want to resize a partition or which one, just
> because you resize the disk.
>
> Thus it's not feasible to assume that the orchestration layer should
> be capable of doing it.
>
> --
> Erik
>
--
Andrija Panić
Re: root resize support in the UI
Posted by Andrija Panic <an...@gmail.com>.
Exactly, there may be more than 1 partion on that 1 drive.. So just
increase disk size, and let administaror handle the "inside VM" job
On 1 December 2014 at 09:34, Erik Weber <te...@gmail.com> wrote:
> On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <
> Vadim.Kimlaychuk@elion.ee>
> wrote:
>
> > I have done root partition resize under XenServer exactly as you
> described
> > - resized drive and then using system tools on guest VM like fdisk,
> > lvextend and ext2resize changed the size of the root. It seems that
> drive
> > resize on hypervisor level is all that is needed, because it is far too
> > complicated for hypervisor to be aware of all different types of
> partition
> > layouts and file systems that might exist. Then upper layer (like CS) may
> > take role of implementing different actions according to guest type and
> > file system that have being used for particular guest. While OS type can
> > be taken from template, FS type and partition type is information that is
> > not stored in the database. Without it implementation is not feasible.
> >
>
> It's not given that you want to resize a partition or which one, just
> because you resize the disk.
>
> Thus it's not feasible to assume that the orchestration layer should be
> capable of doing it.
>
> --
> Erik
>
--
Andrija Panić
Re: root resize support in the UI
Posted by Erik Weber <te...@gmail.com>.
On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk <Va...@elion.ee>
wrote:
> I have done root partition resize under XenServer exactly as you described
> - resized drive and then using system tools on guest VM like fdisk,
> lvextend and ext2resize changed the size of the root. It seems that drive
> resize on hypervisor level is all that is needed, because it is far too
> complicated for hypervisor to be aware of all different types of partition
> layouts and file systems that might exist. Then upper layer (like CS) may
> take role of implementing different actions according to guest type and
> file system that have being used for particular guest. While OS type can
> be taken from template, FS type and partition type is information that is
> not stored in the database. Without it implementation is not feasible.
>
It's not given that you want to resize a partition or which one, just
because you resize the disk.
Thus it's not feasible to assume that the orchestration layer should be
capable of doing it.
--
Erik
RE: root resize support in the UI
Posted by Vadim Kimlaychuk <Va...@Elion.ee>.
I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible.
Vadim.
-----Original Message-----
From: Andrija Panic [mailto:andrija.panic@gmail.com]
Sent: Monday, December 01, 2014 10:02 AM
To: dev@cloudstack.apache.org
Subject: Re: root resize support in the UI
I think it would be usefull to have that resize feature for all guests (Linux, Windows, etc) - but perhaps customizes the Resize function to perform partition resize inside Linux (if we are deploying new VM from Linux template) - or simply do not do anything inside guest OS, just resize the drive - and let the client handle partition and file system resize...it might be more clean implementation I guess...?
On 1 December 2014 at 08:48, Vadim Kimlaychuk <Va...@elion.ee>
wrote:
> It is interesting how, in genereal, this works for XenServer (for
> exmaple)? I do understand, that entire logic of CS is built around
> hypervisor capabilities. It does not do more than each specific
> hypervisor can offer. KVM do have "virt-resize" tool that can resize
> Linux partitions, but it will probably not work for Windows hosts
> anyway. So, to be honest, this UI feature should only be visible for Linux guests.
>
> I don't know whether different approach to build and resize root
> partitions for all hypervisors exist? If it is not possible to do on
> hypervisor level, how does CS do this?
>
> Vadim.
>
> -----Original Message-----
> From: Nux! [mailto:nux@li.nux.ro]
> Sent: Sunday, November 30, 2014 2:03 PM
> To: dev@cloudstack.apache.org
> Subject: Re: root resize support in the UI
>
> It's very possible Citrix customised that installation, what they do
> for their own customers is their own business. It was certainly
> possible to do it with 4.3, Marcus wrote some patches at some point to
> enable this functionality (KVM only, again).
>
> The UI has always been considered more of a proof of concept, though
> it's a very much needed part of ACS, as such everyone is encouraged to
> use the API and build their own interfaces. I missed some important
> options and customers because I thought
>
> GreenQloud, Exoscale etc will give you some credit as a new customer
> so you can check out their UI. They don't have as many options as the
> ACS one, but I found this to be a feature, customers shouldn't be
> exposed to too many options, they'll just get their noses caught in
> them. :)
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> > To: dev@cloudstack.apache.org
> > Sent: Sunday, 30 November, 2014 10:53:56
> > Subject: RE: root resize support in the UI
>
> > Lucian,
> >
> > I have seen CS 4.3 installation made by Citrix at our parnter
> > and
> they have the
> > same feature enabled for XenServer and VmWare. I wonder how
> > does
> it work ?
> > They have their own team of developers to make some extra
> > features
> they need
> > (like plugin for statistics and billing), but did they
> > implement
> particularly
> > this feature or Citrix did it - I don't know. It seems this
> > part
> of code is
> > not contributed back to community anyway. It would be nice to
> > have
> it,
> > especially together with "slieders" which are quite popular
> > right
> now as I
> > understood.
> >
> > Vadim.
> >
> > -----Original Message-----
> > From: Nux! [mailto:nux@li.nux.ro]
> > Sent: Saturday, November 29, 2014 9:48 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: root resize support in the UI
> >
> > Vadim,
> >
> > 1. Only KVM for now, due to lack of interest I guess 2. The root
> > disk value needs to be equal or larger than that of the template,
> > otherwise you end up with a broken disk, obviously. So go for
> > minimal (say under
> > 10G) templates that can resize themselves, such as the ones at
> > http://dl.openvm.eu ;) 3. The backend API has been supporting this
> > since 4.4.0, it's the UI that is lagging behind More details here
> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >
> > Lucian
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > ----- Original Message -----
> >> From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> >> To: dev@cloudstack.apache.org
> >> Sent: Saturday, 29 November, 2014 15:17:16
> >> Subject: RE: root resize support in the UI
> >
> >> Nux,
> >>
> >> Can you give more information about this functionality? I
> >> am
> particularly
> >> interesting to show to the user this field, but don't know
> >> how
> it will work.
> >> Particularly is interesting:
> >> 1. Does it work for all hypervisors or just KVM?
> >> 2. Does it depend on the template root partition (i.e. I have 10G
> >> root at template and put 5G to desired. Will it work?) 3. This is
> >> just UI patch, shouldn't it be activated at the backend as well ?
> >>
> >> Thanks,
> >> Vadim
> >> ________________________________________
> >> From: Nux! [nux@li.nux.ro]
> >> Sent: Saturday, November 29, 2014 12:37
> >> To: dev@cloudstack.apache.org
> >> Cc: Brian Federle
> >> Subject: Re: root resize support in the UI
> >>
> >> BTW, the code needed to enable custom root size during instance
> >> creation is very small, functionality is already there.
> >> This patch is needed
> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h
> >> =8 f ec09ba481fbd3b8c2a9e4d31ef06f113b037cb
> >> , I tested it and it works fine.
> >>
> >> And this is the result: https://i.imgur.com/xrs0mu4.png
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> ----- Original Message -----
> >>> From: "Nux!" <nu...@li.nux.ro>
> >>> To: dev@cloudstack.apache.org
> >>> Cc: "Brian Federle" <Br...@citrix.com>
> >>> Sent: Saturday, 29 November, 2014 00:57:37
> >>> Subject: Re: root resize support in the UI
> >>
> >>> Yes, you have a point.
> >>>
> >>> Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7992
> >>>
> >>> --
> >>> Sent from the Delta quadrant using Borg technology!
> >>>
> >>> Nux!
> >>> www.nux.ro
> >>>
> >>> ----- Original Message -----
> >>>> From: "Mike Tutkowski" <mi...@solidfire.com>
> >>>> To: dev@cloudstack.apache.org
> >>>> Cc: "Brian Federle" <Br...@citrix.com>
> >>>> Sent: Saturday, 29 November, 2014 00:48:03
> >>>> Subject: Re: root resize support in the UI
> >>>
> >>>> Well...I don't know...we kind of have features all over the place
> >>>> that work for one hypervisor and not for another.
> >>>>
> >>>> If we're cool with that approach, this would be just one more
> >>>> area where we have this kind of hypervisor-specific behavior
> >>>> (perhaps all hypervisors support such an action in the future).
> >>>>
> >>>> On Fri, Nov 28, 2014 at 5:41 PM, Nux! <nu...@li.nux.ro> wrote:
> >>>>
> >>>>> Was thinking to just patch my local installation. Devs might not
> >>>>> go too crazy over this idea since root resize is not supported
> >>>>> across all hypervisors (KVM only atm).
> >>>>>
> >>>>> But if you think this has a chance to go official, I will open
> >>>>> an
> issue.
> >>>>>
> >>>>> Thanks,
> >>>>> Lucian
> >>>>>
> >>>>> --
> >>>>> Sent from the Delta quadrant using Borg technology!
> >>>>>
> >>>>> Nux!
> >>>>> www.nux.ro
> >>>>>
> >>>>> ----- Original Message -----
> >>>>> > From: "Mike Tutkowski" <mi...@solidfire.com>
> >>>>> > To: dev@cloudstack.apache.org, "Brian Federle"
> >>>>> > <Brian.Federle@citrix.com
> >>>>> >
> >>>>> > Sent: Saturday, 29 November, 2014 00:27:14
> >>>>> > Subject: Re: root resize support in the UI
> >>>>>
> >>>>> > Have you logged a JIRA ticket for this?
> >>>>> >
> >>>>> > Maybe Brian or one of the GUI people could pick up on it.
> >>>>> >
> >>>>> > On Fri, Nov 28, 2014 at 4:32 PM, Nux! <nu...@li.nux.ro> wrote:
> >>>>> >
> >>>>> >> Yeah, I was thinking of that, if it works for DATA, it should
> >>>>> >> work for ROOT. But I am not a dev.
> >>>>> >>
> >>>>> >> Thoughts?
> >>>>> >>
> >>>>> >> --
> >>>>> >> Sent from the Delta quadrant using Borg technology!
> >>>>> >>
> >>>>> >> Nux!
> >>>>> >> www.nux.ro
> >>>>> >>
> >>>>> >> ----- Original Message -----
> >>>>> >> > From: "Mike Tutkowski" <mi...@solidfire.com>
> >>>>> >> > To: dev@cloudstack.apache.org
> >>>>> >> > Sent: Friday, 28 November, 2014 19:57:27
> >>>>> >> > Subject: Re: root resize support in the UI
> >>>>> >>
> >>>>> >> > For root disks, is it possible to just follow the existing
> >>>>> >> > resize
> >>>>> pattern
> >>>>> >> > we have established in the UI for data disks?
> >>>>> >> >
> >>>>> >> > On Friday, November 28, 2014, Nux! <nu...@li.nux.ro> wrote:
> >>>>> >> >
> >>>>> >> >> Hello,
> >>>>> >> >>
> >>>>> >> >> Wonder if someone can help me with the $subject.
> >>>>> >> >>
> >>>>> >> >> I remember at some point (4.2?) a new feature showed up
> >>>>> >> >> accidentally
> >>>>> in
> >>>>> >> >> the UI instance creation dialogues, it was concerning
> >>>>> >> >> "root size",
> >>>>> had a
> >>>>> >> >> small box where the number in GB would be introduced.
> >>>>> >> >> I'd like to take advantage of that now that this feature
> >>>>> >> >> actually
> >>>>> works,
> >>>>> >> >> even if only in KVM. I'd love it if someone could point me
> >>>>> >> >> to that
> >>>>> >> piece of
> >>>>> >> >> code (prolly just javascript).
> >>>>> >> >>
> >>>>> >> >> In addition to that, now that root resize works, can any
> >>>>> >> >> one suggest
> >>>>> >> how I
> >>>>> >> >> might put a "resize" button in the Volumes section for the
> >>>>> >> >> ROOT
> >>>>> disks?
> >>>>> >> >>
> >>>>> >> >> Lucian
> >>>>> >> >>
> >>>>> >> >> --
> >>>>> >> >> Sent from the Delta quadrant using Borg technology!
> >>>>> >> >>
> >>>>> >> >> Nux!
> >>>>> >> >> www.nux.ro
> >>>>> >> >>
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > --
> >>>>> >> > *Mike Tutkowski*
> >>>>> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >>>>> >> > e: mike.tutkowski@solidfire.com
> >>>>> >> > o: 303.746.7302
> >>>>> >> > Advancing the way the world uses the cloud
> >>>>> >> > <http://solidfire.com/solution/overview/?video=play>*™*
> >>>>> >>
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > --
> >>>>> > *Mike Tutkowski*
> >>>>> > *Senior CloudStack Developer, SolidFire Inc.*
> >>>>> > e: mike.tutkowski@solidfire.com
> >>>>> > o: 303.746.7302
> >>>>> > Advancing the way the world uses the cloud
> >>>>> > <http://solidfire.com/solution/overview/?video=play>*™*
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> *Mike Tutkowski*
> >>>> *Senior CloudStack Developer, SolidFire Inc.*
> >>>> e: mike.tutkowski@solidfire.com
> >>>> o: 303.746.7302
> >>>> Advancing the way the world uses the cloud
> > > > > <http://solidfire.com/solution/overview/?video=play>*™*
>
--
Andrija Panić
Re: root resize support in the UI
Posted by Erik Weber <te...@gmail.com>.
On Mon, Dec 1, 2014 at 9:02 AM, Andrija Panic <an...@gmail.com>
wrote:
> I think it would be usefull to have that resize feature for all guests
> (Linux, Windows, etc) - but perhaps customizes the Resize function to
> perform partition resize inside Linux (if we are deploying new VM from
> Linux template) - or simply do not do anything inside guest OS, just resize
> the drive - and let the client handle partition and file system resize...it
> might be more clean implementation I guess...?
>
I believe cloud-init is capable of this?
--
Erik
Re: root resize support in the UI
Posted by Andrija Panic <an...@gmail.com>.
I think it would be usefull to have that resize feature for all guests
(Linux, Windows, etc) - but perhaps customizes the Resize function to
perform partition resize inside Linux (if we are deploying new VM from
Linux template) - or simply do not do anything inside guest OS, just resize
the drive - and let the client handle partition and file system resize...it
might be more clean implementation I guess...?
On 1 December 2014 at 08:48, Vadim Kimlaychuk <Va...@elion.ee>
wrote:
> It is interesting how, in genereal, this works for XenServer (for
> exmaple)? I do understand, that entire logic of CS is built around
> hypervisor capabilities. It does not do more than each specific hypervisor
> can offer. KVM do have "virt-resize" tool that can resize Linux partitions,
> but it will probably not work for Windows hosts anyway. So, to be honest,
> this UI feature should only be visible for Linux guests.
>
> I don't know whether different approach to build and resize root
> partitions for all hypervisors exist? If it is not possible to do on
> hypervisor level, how does CS do this?
>
> Vadim.
>
> -----Original Message-----
> From: Nux! [mailto:nux@li.nux.ro]
> Sent: Sunday, November 30, 2014 2:03 PM
> To: dev@cloudstack.apache.org
> Subject: Re: root resize support in the UI
>
> It's very possible Citrix customised that installation, what they do for
> their own customers is their own business. It was certainly possible to do
> it with 4.3, Marcus wrote some patches at some point to enable this
> functionality (KVM only, again).
>
> The UI has always been considered more of a proof of concept, though it's
> a very much needed part of ACS, as such everyone is encouraged to use the
> API and build their own interfaces. I missed some important options and
> customers because I thought
>
> GreenQloud, Exoscale etc will give you some credit as a new customer so
> you can check out their UI. They don't have as many options as the ACS one,
> but I found this to be a feature, customers shouldn't be exposed to too
> many options, they'll just get their noses caught in them. :)
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> > To: dev@cloudstack.apache.org
> > Sent: Sunday, 30 November, 2014 10:53:56
> > Subject: RE: root resize support in the UI
>
> > Lucian,
> >
> > I have seen CS 4.3 installation made by Citrix at our parnter and
> they have the
> > same feature enabled for XenServer and VmWare. I wonder how does
> it work ?
> > They have their own team of developers to make some extra features
> they need
> > (like plugin for statistics and billing), but did they implement
> particularly
> > this feature or Citrix did it - I don't know. It seems this part
> of code is
> > not contributed back to community anyway. It would be nice to have
> it,
> > especially together with "slieders" which are quite popular right
> now as I
> > understood.
> >
> > Vadim.
> >
> > -----Original Message-----
> > From: Nux! [mailto:nux@li.nux.ro]
> > Sent: Saturday, November 29, 2014 9:48 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: root resize support in the UI
> >
> > Vadim,
> >
> > 1. Only KVM for now, due to lack of interest I guess 2. The root disk
> > value needs to be equal or larger than that of the template, otherwise
> > you end up with a broken disk, obviously. So go for minimal (say under
> > 10G) templates that can resize themselves, such as the ones at
> > http://dl.openvm.eu ;) 3. The backend API has been supporting this
> > since 4.4.0, it's the UI that is lagging behind More details here
> > https://issues.apache.org/jira/browse/CLOUDSTACK-6181
> >
> > Lucian
> >
> > --
> > Sent from the Delta quadrant using Borg technology!
> >
> > Nux!
> > www.nux.ro
> >
> > ----- Original Message -----
> >> From: "Vadim Kimlaychuk" <Va...@Elion.ee>
> >> To: dev@cloudstack.apache.org
> >> Sent: Saturday, 29 November, 2014 15:17:16
> >> Subject: RE: root resize support in the UI
> >
> >> Nux,
> >>
> >> Can you give more information about this functionality? I am
> particularly
> >> interesting to show to the user this field, but don't know how
> it will work.
> >> Particularly is interesting:
> >> 1. Does it work for all hypervisors or just KVM?
> >> 2. Does it depend on the template root partition (i.e. I have 10G
> >> root at template and put 5G to desired. Will it work?) 3. This is
> >> just UI patch, shouldn't it be activated at the backend as well ?
> >>
> >> Thanks,
> >> Vadim
> >> ________________________________________
> >> From: Nux! [nux@li.nux.ro]
> >> Sent: Saturday, November 29, 2014 12:37
> >> To: dev@cloudstack.apache.org
> >> Cc: Brian Federle
> >> Subject: Re: root resize support in the UI
> >>
> >> BTW, the code needed to enable custom root size during instance
> >> creation is very small, functionality is already there.
> >> This patch is needed
> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8
> >> f ec09ba481fbd3b8c2a9e4d31ef06f113b037cb
> >> , I tested it and it works fine.
> >>
> >> And this is the result: https://i.imgur.com/xrs0mu4.png
> >>
> >> --
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >> Nux!
> >> www.nux.ro
> >>
> >> ----- Original Message -----
> >>> From: "Nux!" <nu...@li.nux.ro>
> >>> To: dev@cloudstack.apache.org
> >>> Cc: "Brian Federle" <Br...@citrix.com>
> >>> Sent: Saturday, 29 November, 2014 00:57:37
> >>> Subject: Re: root resize support in the UI
> >>
> >>> Yes, you have a point.
> >>>
> >>> Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7992
> >>>
> >>> --
> >>> Sent from the Delta quadrant using Borg technology!
> >>>
> >>> Nux!
> >>> www.nux.ro
> >>>
> >>> ----- Original Message -----
> >>>> From: "Mike Tutkowski" <mi...@solidfire.com>
> >>>> To: dev@cloudstack.apache.org
> >>>> Cc: "Brian Federle" <Br...@citrix.com>
> >>>> Sent: Saturday, 29 November, 2014 00:48:03
> >>>> Subject: Re: root resize support in the UI
> >>>
> >>>> Well...I don't know...we kind of have features all over the place
> >>>> that work for one hypervisor and not for another.
> >>>>
> >>>> If we're cool with that approach, this would be just one more area
> >>>> where we have this kind of hypervisor-specific behavior (perhaps
> >>>> all hypervisors support such an action in the future).
> >>>>
> >>>> On Fri, Nov 28, 2014 at 5:41 PM, Nux! <nu...@li.nux.ro> wrote:
> >>>>
> >>>>> Was thinking to just patch my local installation. Devs might not
> >>>>> go too crazy over this idea since root resize is not supported
> >>>>> across all hypervisors (KVM only atm).
> >>>>>
> >>>>> But if you think this has a chance to go official, I will open an
> issue.
> >>>>>
> >>>>> Thanks,
> >>>>> Lucian
> >>>>>
> >>>>> --
> >>>>> Sent from the Delta quadrant using Borg technology!
> >>>>>
> >>>>> Nux!
> >>>>> www.nux.ro
> >>>>>
> >>>>> ----- Original Message -----
> >>>>> > From: "Mike Tutkowski" <mi...@solidfire.com>
> >>>>> > To: dev@cloudstack.apache.org, "Brian Federle"
> >>>>> > <Brian.Federle@citrix.com
> >>>>> >
> >>>>> > Sent: Saturday, 29 November, 2014 00:27:14
> >>>>> > Subject: Re: root resize support in the UI
> >>>>>
> >>>>> > Have you logged a JIRA ticket for this?
> >>>>> >
> >>>>> > Maybe Brian or one of the GUI people could pick up on it.
> >>>>> >
> >>>>> > On Fri, Nov 28, 2014 at 4:32 PM, Nux! <nu...@li.nux.ro> wrote:
> >>>>> >
> >>>>> >> Yeah, I was thinking of that, if it works for DATA, it should
> >>>>> >> work for ROOT. But I am not a dev.
> >>>>> >>
> >>>>> >> Thoughts?
> >>>>> >>
> >>>>> >> --
> >>>>> >> Sent from the Delta quadrant using Borg technology!
> >>>>> >>
> >>>>> >> Nux!
> >>>>> >> www.nux.ro
> >>>>> >>
> >>>>> >> ----- Original Message -----
> >>>>> >> > From: "Mike Tutkowski" <mi...@solidfire.com>
> >>>>> >> > To: dev@cloudstack.apache.org
> >>>>> >> > Sent: Friday, 28 November, 2014 19:57:27
> >>>>> >> > Subject: Re: root resize support in the UI
> >>>>> >>
> >>>>> >> > For root disks, is it possible to just follow the existing
> >>>>> >> > resize
> >>>>> pattern
> >>>>> >> > we have established in the UI for data disks?
> >>>>> >> >
> >>>>> >> > On Friday, November 28, 2014, Nux! <nu...@li.nux.ro> wrote:
> >>>>> >> >
> >>>>> >> >> Hello,
> >>>>> >> >>
> >>>>> >> >> Wonder if someone can help me with the $subject.
> >>>>> >> >>
> >>>>> >> >> I remember at some point (4.2?) a new feature showed up
> >>>>> >> >> accidentally
> >>>>> in
> >>>>> >> >> the UI instance creation dialogues, it was concerning "root
> >>>>> >> >> size",
> >>>>> had a
> >>>>> >> >> small box where the number in GB would be introduced.
> >>>>> >> >> I'd like to take advantage of that now that this feature
> >>>>> >> >> actually
> >>>>> works,
> >>>>> >> >> even if only in KVM. I'd love it if someone could point me
> >>>>> >> >> to that
> >>>>> >> piece of
> >>>>> >> >> code (prolly just javascript).
> >>>>> >> >>
> >>>>> >> >> In addition to that, now that root resize works, can any one
> >>>>> >> >> suggest
> >>>>> >> how I
> >>>>> >> >> might put a "resize" button in the Volumes section for the
> >>>>> >> >> ROOT
> >>>>> disks?
> >>>>> >> >>
> >>>>> >> >> Lucian
> >>>>> >> >>
> >>>>> >> >> --
> >>>>> >> >> Sent from the Delta quadrant using Borg technology!
> >>>>> >> >>
> >>>>> >> >> Nux!
> >>>>> >> >> www.nux.ro
> >>>>> >> >>
> >>>>> >> >
> >>>>> >> >
> >>>>> >> > --
> >>>>> >> > *Mike Tutkowski*
> >>>>> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >>>>> >> > e: mike.tutkowski@solidfire.com
> >>>>> >> > o: 303.746.7302
> >>>>> >> > Advancing the way the world uses the cloud
> >>>>> >> > <http://solidfire.com/solution/overview/?video=play>*™*
> >>>>> >>
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > --
> >>>>> > *Mike Tutkowski*
> >>>>> > *Senior CloudStack Developer, SolidFire Inc.*
> >>>>> > e: mike.tutkowski@solidfire.com
> >>>>> > o: 303.746.7302
> >>>>> > Advancing the way the world uses the cloud
> >>>>> > <http://solidfire.com/solution/overview/?video=play>*™*
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> *Mike Tutkowski*
> >>>> *Senior CloudStack Developer, SolidFire Inc.*
> >>>> e: mike.tutkowski@solidfire.com
> >>>> o: 303.746.7302
> >>>> Advancing the way the world uses the cloud
> > > > > <http://solidfire.com/solution/overview/?video=play>*™*
>
--
Andrija Panić