cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Caleb Call <>
Subject Re: Customizing cloudstack
Date Fri, 10 Aug 2012 20:43:09 GMT
Correct, I've tested removing the compute offering and the instance that was using it continues
to run fine and I'm also able to shutdown, reboot, etc and it's fine.  It even retains the
compute offering name that was used that has since been deleted.  We're currently not doing
any billing (our cloudstack is all internal but we would like to eventually do some show back
or maybe charge back to the different departments and teams in the future) so I can't speak
to that, there also could be some other side effects I'm not currently seeing.


On Aug 10, 2012, at 5:46 AM, Nitin Mehta <> wrote:

> If I recall it correctly, it does allow you to delete even if some vm's are using it
and what that means is that the existing vms would still be using it but new vms cant be created
with the deleted compute offering. It's a soft delete and the usage should be able to calculate
metering for the deleted compute offering. If it doesn't then it's a bug.
> Thanks,
> -Nitin
> -----Original Message-----
> From: Tamas Monos [] 
> Sent: Friday, August 10, 2012 4:26 PM
> To:
> Subject: RE: Customizing cloudstack
> Hi,
> I'm not sure you can remove a compute offering while VMs are using it. Also usage has
references to the compute offering so if you can remove them that might break usage so you
might not be able to bill your customers properly.
> Regards
> Tamas Monos                                               DDI         +44(0)2034687012
> Chief Technical                                             Office    +44(0)2034687000
> Veber: The Hosting Specialists               Fax         +44(0)871 522 7057
> Follow us on Twitter: Follow us on Facebook:
> -----Original Message-----
> From: Caleb Call []
> Sent: 08 August 2012 23:32
> To:
> Subject: Customizing cloudstack
> Couple questions that pertain to customizing cloudstack to fit better into our environment.
 First question is related to DNS.  What needs to be done to make it so the DHCP addresses
that are assigned in cloudstack can be pushed back dynamically to our company DNS?  Is it
as simple as setting up an rndc key?  We'd like this functionality so that the self-service
part is truly self service and as automated as possible.  I would guess the changes would
need to be made on the virtual router, but how could we make it so any future routers that
are spun up pickup these changes as that possible?
> Second question has to do with modifying an instance's resources.  Is it possible to
resize an instance, say add additional memory without creating a new Compute Offering, maybe
using the API?  The one thought I had on doing this was to use the API, create a new computer
offering with the specs you want, stop the VM, assign this compute offering, start up the
VM, then remove the computer offering.  I'm sure there are issues with that, but it seems
odd that you can't just add memory or an extra CPU or <insert whatever> without creating
a whole new compute offering for existing instances.
> Thanks,
> Caleb

View raw message